Repository navigation
Strategy modes: fast / reliable / reliable-fast #4
Description
Activity
📝 CodeRabbit Plan Mode
Generate an implementation plan and prompts that you can use with your favorite coding agent.
- Create Plan
👤 Suggested Assignees
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Technical Notes
API & Schema
- Extend
packages/rpc/src/suggest.tsto includereliable-fast. apps/service-bun/src/request.tscontinues to default toreliable.
Execution Semantics
fast: single provider, strict timeout, fail-fast.reliable: multi-stage serial fallbacks.reliable-fast: parallel providers, merge + dedupe + return within a strict overall budget.
Cache Key Decision
Current cache key includes the chosen strategy. Proposed: make cache shared by query only so different strategies benefit from the same cached result.
- Change
apps/service-bun/src/cache.tskey generation accordingly. - Optional migration strategy: read both the new key and legacy key for a transition period.
Entitlements Hook (integration point)
- Gate
reliable-fastin hosted mode via the payments/entitlements layer (implemented in the payments issue).
Tests
- Schema acceptance for 3 modes.
- Plan selection behavior (serial vs parallel).
- Cache key behavior and hit consistency across strategies.
- Extend
Status update: fast + reliable strategies are implemented in the service (apps/service-bun/src/service.ts) and documented; reliable-fast is still marked as planned in docs (apps/docs/content/en/explanation/strategies.md), so this remains open for that mode.
Goal
Offer clear service modes that let customers choose the trade‑off between speed, reliability, and price.
Who Uses This
What “Done” Means (Business)
fast,reliable,reliable-fast.Constraints
Out of Scope
Technical notes: #4 (comment)