Public backlog roadmap: Now / Next / Later

[tobytkershaw]

Summary

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

Goal: keep execution focused on bounded communication, negotiation/core protocol integrity, and outward-facing communication in that order.

Now

Core product / protocol

• vcav-io/agentvault#388 — Reintegrate IFC as the default out-of-vault communication membrane
• vcav-io/agentvault-registry#3 — Finish the model-profile hash migration / deprecation story

Small product polish

• vcav-io/agentvault#391 — Demo UI serves no favicon.ico
• vcav-io/agentvault#392 — Demo UI logs SSE reconnect warning when navigating from live view to replay

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

Completed recently

• vcav-io/agentvault#386 — first IFC slice for post-session follow-up and logistics
• vcav-io/agentvault#387 — resolved-agreement core for structured negotiation
• vcav-io/agentvault#380 — Demo UI close-out and smoke coverage
• vcav-io/agentvault#362 — divergent purpose proposals handled cleanly

Dependency notes

• agentvault#388 is now the main protocol/product lane after the first IFC slice merged in #389
• agentvault-registry#3 is now mainly about migration/deprecation policy rather than the already-fixed relay resolution gap
• website#67 and website#69 remain the highest-value outward-facing work once the current protocol lane settles
• agentvault#391 and agentvault#392 are intentionally tiny and should be batched together rather than allowed to distract from the main lane

[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.