Documentation Index
Fetch the complete documentation index at: https://grantmaster.dev/llms.txt
Use this file to discover all available pages before exploring further.
Canonical Rollout Status
Scope
Canonical status/event rollout across Grants, Projects, Compliance, Billing, Agents, and Extensions.Epic Status
| Epic | Goal | Status |
|---|---|---|
| Epic 1 | Canonical contract + vocabulary + mapping baseline | ✅ Complete |
| Epic 2 | Projection robustness, freshness, degraded-mode policy | ✅ Complete |
| Epic 3 | Producer migration (grant.lifecycle.*, expense.audit.*, agent.run.*) | ✅ Complete |
| Epic 4 | Consumer cutover and shared UI status primitives | ✅ Complete |
| Epic 5 | Polling reduction + projection health visibility + fallback hardening | ✅ Complete |
| Epic 6 | Canonical coverage guardrails (critical event map CI gate) | ✅ Complete |
Completion Notes
- Canonical status vocabulary fixed to
pending,progress,blocked,completed,failed. - Core features read canonical projections via shared selectors and hooks.
- Projection freshness and health are surfaced in Grants/Projects/Compliance/Billing/Agents/Extensions.
- Extension and agent runtime paths enforce degraded-mode behavior when projections are stale.
- Cross-consumer integration tests cover grant lifecycle, expense audit, and agent run event families.
- Coverage tests enforce that critical event families stay mapped in canonical contract evolution.