id: T006 name: P1 Feature Implementation - Next Phase status: complete # Acceptance criteria met (Tier A 100%, Tier B 100% > 50% threshold) created: 2025-12-08 owner: peerB goal: Implement 14 P1 features across chainfire/flaredb/iam description: | Now phase complete (T001-T005). Enter Next phase per roadmap. Focus: chainfire/flaredb/iam feature completion before new components. Prioritization criteria: 1. Operational readiness (health/metrics for K8s deployment) 2. Integration value (enables other components) 3. User-facing impact (can users actually use the system?) acceptance: - All Tier A items complete (operational readiness) - At least 50% of Tier B items complete - No regressions in existing tests steps: # Tier A - Operational Readiness (Week 1) - COMPLETE - step: S1 action: Chainfire health checks priority: P1-TierA status: complete complexity: small estimate: 1 day component: chainfire notes: tonic-health service on API + agent ports - step: S2 action: Chainfire Prometheus metrics priority: P1-TierA status: complete complexity: small estimate: 1-2 days component: chainfire notes: metrics-exporter-prometheus on port 9091 - step: S3 action: FlareDB health check service priority: P1-TierA status: complete complexity: small estimate: 1 day component: flaredb notes: tonic-health for KvRaw/KvCas services - step: S4 action: Chainfire transaction responses priority: P1-TierA status: complete complexity: small estimate: 1-2 days component: chainfire notes: TxnOpResponse with Put/Delete/Range results # Tier B - Feature Completeness (Week 2-3) - step: S5 action: IAM audit integration priority: P1-TierB status: complete complexity: small estimate: 2 days component: iam notes: AuditLogger in IamAuthzService, logs authz_allowed/denied events - step: S6 action: FlareDB client raw_scan priority: P1-TierB status: complete complexity: small estimate: 1-2 days component: flaredb notes: raw_scan() method added to RdbClient - step: S7 action: IAM group management priority: P1-TierB status: complete complexity: medium estimate: 3-5 days component: iam notes: GroupStore with add/remove/list members, reverse index for groups - step: S8 action: IAM group expansion in authz priority: P1-TierB status: complete complexity: medium estimate: 3-5 days component: iam notes: PolicyEvaluator.with_group_store() for group binding expansion # Tier C - Advanced Features (Week 3-4) - step: S9 action: FlareDB CLI tool priority: P1-TierC status: pending complexity: medium estimate: 3-5 days component: flaredb notes: Replace "Hello World" stub with functional CLI - step: S10 action: Chainfire StorageBackend trait priority: P1-TierC status: pending complexity: medium estimate: 3-5 days component: chainfire notes: Per-spec abstraction, enables alternative backends - step: S11 action: Chainfire point-in-time reads priority: P1-TierC status: pending complexity: medium estimate: 3-5 days component: chainfire notes: Revision parameter for historical queries - step: S12 action: FlareDB auto region splitting priority: P1-TierC status: pending complexity: medium estimate: 3-5 days component: flaredb notes: Automatic scaling without manual intervention - step: S13 action: FlareDB snapshot transfer priority: P1-TierC status: pending complexity: medium estimate: 3-5 days component: flaredb notes: Test InstallSnapshot for HA scenarios - step: S14 action: IAM OIDC principal mapping priority: P1-TierC status: pending complexity: medium estimate: 3 days component: iam notes: End-to-end external identity flow parallel_track: | While T006 proceeds, PlasmaVMC implementation planning can begin. PlasmaVMC spec (T005) complete - ready for scaffolding. notes: | Phase: Now → Next transition This task represents the "Next" phase from roadmap. Target: 3-4 weeks for Tier A+B, 1-2 additional weeks for Tier C. Suggest: Start with S1-S4 (Tier A) for operational baseline. outcome: | COMPLETE: 2025-12-08 Tier A: 4/4 complete (S1-S4) Tier B: 4/4 complete (S5-S8) - exceeds 50% acceptance threshold Tier C: 0/6 pending - deferred to backlog (T006-B) All acceptance criteria met. Remaining Tier C items moved to backlog for later prioritization.