Week 1
Repo & vocabulary freeze
Create the repository, website, issue map, manifest schema, share schema, and audit vocabulary. Establish the terminology that agents and developers will use everywhere.
Implementation plan
Ship the usable vertical slice first, add proofs later.
The roadmap prioritizes a working file-sharing system with basic evidence before adding frontier cryptography, advanced privacy modes, or post-quantum protection.
First 30 days
Initial sprint plan
Four focused weeks that deliver a complete file-sharing vertical slice with evidence and reachability.
Week 2
Storage & evidence baseline
Implement chunking, deterministic manifests, append-only audit events, and export bundle scaffolding. This is the foundation every other feature builds on.
Week 3
Share lifecycle
Issue share links, enforce expiry, support resumable transfers, and emit final delivery receipts. The core user-facing flow becomes functional.
Week 4
Reachability slice
Add UPnP/NAT-PMP attempts, a signed external probe, and the encrypted relay fallback. The system can now be reached from outside the local network.
Extended timeline
Beyond the MVP
After the vertical slice ships, these tracks add depth without breaking the core system.
Month 2
Evidence hardening
Merkle audit log integrity, verifiable deletion with crypto-shredding, and human-readable evidence cards for the admin UI.
Month 3
Privacy & policy
Metadata aliases, size bucketing, consent tracking, regulatory-compliant export bundles, and optional differential privacy for exposed metadata.
Month 4+
Frontier additions
Post-quantum hybrid key exchange, optional ZK delivery proofs, cross-device sync, and oblivious access modes for high-sensitivity data.
Build sequence
Exact implementation order
1. Chunk store + deterministic manifests
2. Audit log + checkpoints
3. Share links + expiry
4. Resumable transfer + segment receipts
5. UPnP/NAT-PMP + signed probe
6. Encrypted relay fallback
7. Explanation cards + export bundles
8. Hybrid PQ interfaces + reproducible builds