id:
cap-context-engine · owner: finaya-platformDescrição
11 tabelas, 15 clientes seed, deep_context jsonb versionado
Enterprise Architecture derivado
RACI
Accountable:
PLATFORM_ARCHITECT declaradoResponsible: PLATFORM_ENGINEERConsulted: CYBER_LEADMaturidade (1–5)
people4process3technology4information5
Dispara (triggers)
cap-architecture-engine →Data access (Entity:CRUD)
ClientContext:CUArrangementContext:CUDeepContext:CImportância (proxy)
1
consumidores×2 + fan-out
Governança do catálogo 6 capabilities
✓ todas as capabilities com dono têm accountable declarado
✓ nenhuma entidade com dono ambíguo (2+ criadores)
Sustentação operacional
FTE/ano
0.2
Runtime USD/mês
50
Custo aprox/ano (USD)
30600
FTE × 150k + runtime × 12
Demand evidence
- finway-evolution: reuso pattern
- crefisa-psti: context graph requirement
History (transições)
4/4filtrar stages:
| Stage | Timestamp | Rationale |
|---|---|---|
| discovered | 2026-04-15T00:00:00Z | Sprint 2 spec |
| candidate | 2026-04-20T00:00:00Z | ADR-040 |
| experimental | 2026-04-27T00:00:00Z | Sprint 5 build |
| adopted | 2026-05-04T00:00:00Z | Bloco 36 |
Audit log (CockpitFeed)
0 eventos carregadosSprint 97 · cursor-paginated · canonical em CockpitFeedNenhum evento desta capability no buffer atual. Eventos antigos podem ter expirado pela retention policy (capability.promoted: 30d).
✓ fim do buffer · eventos mais antigos podem ter expirado
Bench scenarios
0 runs recentesSprint 112 · scenario_id = cap-context-engine · ring buffer (500)↓ CSV 30dver todos no bench →Sem runs do scenario cap-context-engine no buffer atual. Rodar via
POST /api/bench/event ou CI nightly.ADRs relacionadas
1 ADRsSprint 122 · expand inline para PDFContext Engine v0
11 tabelas + 15 clientes seed + deep_context jsonb versionado
Edição
Edita description, owner, sustentação, promotion_adr e demand_evidence. Para promover stage, use o flow board.