Public backlog roadmap: Now / Next / Later

[tobytkershaw]

Summary

Cross-repo prioritization for the current public vcav-io backlog as of 2026-03-11.

Goal: keep execution focused on product trust, protocol integrity, and distribution in that order, rather than continuing with piecemeal additions across repos.

Now

Product trust

• vcav-io/agentvault#380 — Demo UI close-out: add end-to-end smoke coverage and finalize hardening
• vcav-io/agentvault#362 — Pre-session negotiation should handle divergent purpose proposals more gracefully
• vcav-io/agentvault#329 — Demo natural-language overlap prompts can drift between MEDIATION and COMPATIBILITY

Protocol integrity

• vcav-io/agentvault-registry#3 — Switch model profile references from semantic ID to content hash

Next

Distribution

• vcav-io/website#67 — Blog post: "Your AI Agent Just Leaked Your Salary Expectations"
• vcav-io/website#69 — Add a clearly marked simulation of bounded vs unbounded exchange

Research / validation

• vcav-io/agentvault#165 — Extended accumulation experiment N=20-100

Later

Infra / assurance

• vcav-io/av-tee#15 — Live transparency log service for enclave measurements

New protocol surface

• vcav-io/vault-family-core#15 — AFAL Agent Discovery

Website instrumentation / polish

• vcav-io/website#63 — Add Google Analytics integration
• vcav-io/website#42 — SEO Phase 5

Hygiene

• vcav-io/agentvault#248 — Cleanup: rename profile files to provider-family convention

Dependency notes

• agentvault#329 should follow agentvault#362: first make divergent-purpose handling degrade cleanly, then tighten prompt/scenario convergence.
• agentvault-registry#3 is architecturally important but likely cross-repo and potentially breaking; it should be handled deliberately rather than opportunistically.
• website#67 and website#69 are the highest-value outward-facing work once the demo/protocol trust path is stable.

Duplicate / overlap cleanup

• vcav-io/agentvault#373 overlaps materially with vcav-io/agentvault#380.
• The broader issue (#380) should be the active tracking item for Demo UI close-out work.
• The narrower issue (#373) can be closed as subsumed by #380 unless there is a reason to keep server-only integration coverage tracked separately.

Suggested execution order

1. agentvault#380
2. agentvault#362
3. agentvault-registry#3
4. agentvault#329
5. website#67
6. website#69
7. agentvault#165

[tobytkershaw]

Added the new architecture-driven protocol backlog in agentvault:\n\n- vcav-io/agentvault#386 — Implement the first IFC slice for post-session follow-up and logistics\n- vcav-io/agentvault#387 — Add structured bounded-computation negotiation from registry artefacts\n- vcav-io/agentvault#388 — Reintegrate IFC as the default out-of-vault communication membrane\n\nSuggested reading order is #386 first, then #387, with #388 as the broader IFC tracking issue above the immediate slice.