Skip to main content

Nav Continuity Layer: Capability Map

CAPABILITY MAP
════════════════════════════════════════════════════════════

  CAPABILITY                   MATURITY     GAP?
  ──────────────────────────   ────────     ────
  Extracting Learnings         ████░ (3)
  Agent Receipts               ███░░ (2)
  Session Boot Scripting       ░░░░░ (0)    CRITICAL GAP
  Multi-Repo State Reading     █░░░░ (1)    GAP
  Context Injection            ██░░░ (2)

════════════════════════════════════════════════════════════

Maturity Levels​

  • Extracting Learnings: Level 3 (Defined) - We have VVFL and skill loops.
  • Agent Receipts: Level 2 (Repeatable) - Standardized via agent-receipt-schema.md.
  • Session Boot Scripting: Level 0 (Not Built) - Hooking into the pre-session boot locally.
  • Multi-Repo State Reading: Level 1 (Ad-hoc) - Manually done by humans currently.

Investment Strategy​

  • File aggregation/parsing scripts: Core. Build internally.
  • Hook framework: Supporting. Leverage existing .claude/hooks or .agents/skills orchestrator mechanisms.

Questions​

Which capability in the nav continuity layer map is the hardest to replicate — and does that make it the moat?

  • Which capabilities are table-stakes (must have) vs differentiators (competitive edge) — and is the build order aligned?
  • If a new competitor entered with 10x engineering resources, which capabilities would they copy first and which would they build differently?
  • Which capability gap, once closed, would unlock the most other capabilities?