photoncloud-monorepo/docs/por/T003-feature-gaps/task.yaml
centra a7ec7e2158 Add T026 practical test + k8shost to flake + workspace files
- Created T026-practical-test task.yaml for MVP smoke testing
- Added k8shost-server to flake.nix (packages, apps, overlays)
- Staged all workspace directories for nix flake build
- Updated flake.nix shellHook to include k8shost

Resolves: T026.S1 blocker (R8 - nix submodule visibility)
2025-12-09 06:07:50 +09:00

62 lines
1.8 KiB
YAML

id: T003
name: Feature Gap Analysis - Core Trio
status: complete
created: 2025-12-08
completed: 2025-12-08
owner: peerB
goal: Identify and document gaps between specifications and implementation
description: |
Compare specs to implementation for chainfire, flaredb, and iam.
Produce a prioritized list of missing/incomplete features per component.
This informs whether we can move to "Next" phase or need stabilization work.
acceptance:
- Gap report for each of chainfire, flaredb, iam
- Priority ranking (P0=critical, P1=important, P2=nice-to-have)
- Estimate of implementation complexity (small/medium/large)
results:
summary: |
67% implementation coverage across 3 components.
6 P0 blockers, 14 P1 gaps, 6 P2 gaps.
Total effort: 7-10 person-weeks.
p0_blockers:
- FlareDB persistent Raft storage (data loss on restart)
- Chainfire lease service (etcd compatibility)
- Chainfire read consistency
- Chainfire range in transactions
- IAM health endpoints
- IAM metrics
steps:
- step: S1
action: Audit chainfire gaps
status: complete
output: chainfire-gaps.md
result: 62.5% impl, 3 P0, 5 P1
- step: S2
action: Audit flaredb gaps
status: complete
output: flaredb-gaps.md
result: 54.5% impl, 1 P0 (critical - data loss), 5 P1
- step: S3
action: Audit iam gaps
status: complete
output: iam-gaps.md
result: 84% impl, 2 P0, 4 P1
- step: S4
action: Consolidate priority report
status: complete
output: T003-report.md
result: Consolidated with recommendations
notes: |
Completed 2025-12-08 05:30.
Awaiting PeerA review for strategic decision:
- (A) Sequential: Address P0s first (2-3 weeks), then PlasmaVMC
- (B) Parallel: Start PlasmaVMC while completing IAM P0s (3 days)
FlareDB persistence is the critical blocker.