{"schemaVersion":"1","name":"Handover product and protocol roadmap","canonical":"https://handover.sh/roadmap","updatedAt":"2026-08-05","statusDefinitions":{"available":"Deployed and documented.","validating":"Shipped or public work collecting evidence before broader claims or contract changes.","next":"Current priority without a committed delivery date.","conditional":"Requires demand, safety, or interoperability evidence before commitment."},"sections":[{"status":"available","label":"Available now","timeframe":"Production","description":"Capabilities that are deployed, documented, and available through Handover's current product or open interfaces.","items":[{"id":"shared-context","title":"Shared context for people and agents","summary":"Organization-isolated workspaces hold versioned Markdown, SQL, HTML, code, images, and other artifacts. People use the web application while agents use the same record through MCP, CLI, or HTTP.","evidence":[{"label":"Product definition","href":"/docs/what-is-handover"},{"label":"Public demo","href":"/demo"}]},{"id":"review","title":"Attributable continuation and review","summary":"Immutable revisions preserve authorship. Humans and agents can discuss work, anchor annotations to files, mention collaborators, resolve feedback, and continue an existing handover.","evidence":[{"label":"Annotation documentation","href":"/docs/annotations"},{"label":"Review workflow","href":"/examples/human-agent-review-loop.md"}]},{"id":"identity","title":"Human OAuth and scoped agent identity","summary":"Interactive MCP clients authenticate as a person through browser OAuth. Unattended agents use named, revocable, scoped service credentials. Membership and organization isolation are enforced on the server.","evidence":[{"label":"Install and connect","href":"/install"},{"label":"Security model","href":"/security"}]},{"id":"protocol-v1","title":"Handoff Continuity Record v1.0","summary":"The stable, MIT-licensed JSON format defines objective, state, decisions, evidence, constraints, next action, ownership, and open review without prescribing transport or storage.","evidence":[{"label":"Protocol","href":"/protocol"},{"label":"JSON Schema","href":"/protocol/v1/schema.json"}]}]},{"status":"validating","label":"In validation","timeframe":"Current research","description":"Shipped or public work where Handover is collecting reproducible evidence before making broader claims or changing a stable contract.","items":[{"id":"benchmark-expansion","title":"Continuity benchmark expansion","summary":"The open pilot currently covers three authored cases and two model systems. The next evidence gate is more cases, repeated runs, additional systems, and independently contributed tasks.","evidence":[{"label":"Methodology and results","href":"/benchmark"},{"label":"Reproducibility record","href":"/benchmark/v1/results/2026-08-04/README.md"}]},{"id":"protocol-feedback","title":"Protocol implementation feedback","summary":"Version 1.0 remains stable while real producers and receivers test conformance, extension namespacing, evidence resolution, and review portability.","evidence":[{"label":"Conformance notes","href":"/protocol/v1/README.md"},{"label":"Public source","href":"https://github.com/44-pixels/handover-mcp/tree/main/protocol/v1"}]},{"id":"continuation-measurement","title":"Real handoff activation measurement","summary":"Acquisition is measured through a strict funnel that only counts continuation when a second authenticated actor adds a later revision to the acquired creator's handover.","evidence":[{"label":"Working examples","href":"/examples"},{"label":"Product releases","href":"/changelog"}]}]},{"status":"next","label":"Next","timeframe":"Prioritized, not date-promised","description":"The next product and ecosystem problems Handover intends to address. Order can change when validation evidence or user needs change.","items":[{"id":"migration-tooling","title":"Repeatable Reporter migration tooling","summary":"Turn the completed 44pixels migration work into documented, resumable import tooling with dry runs, validation reports, stable source references, and explicit cutover checks.","evidence":[{"label":"Migration guide","href":"/docs/reporter-migration"},{"label":"Migration example","href":"/guides/migrate-static-report-folders-to-shared-ai-context"}]},{"id":"navigation-scale","title":"Faster navigation across large knowledge spaces","summary":"Improve scanning, saved views, filtering, and movement between many handovers without weakening the current space and folder access boundaries.","evidence":[{"label":"Shared workspace guide","href":"/guides/shared-workspace-for-humans-and-ai-agents"},{"label":"Documentation","href":"/docs"}]},{"id":"ecosystem-kits","title":"More host recipes and Agent Skills","summary":"Expand tested setup recipes, reusable handoff skills, and end-to-end examples for the agent hosts people already use.","evidence":[{"label":"Agent Skills","href":"https://skills.handover.sh/"},{"label":"Host recipes","href":"/recipes/mcp-hosts.json"}]}]},{"status":"conditional","label":"Later or conditional","timeframe":"Evidence-gated","description":"Directions that are useful enough to investigate but will not be presented as commitments until demand, safety, and interoperability evidence support them.","items":[{"id":"protocol-minor","title":"A protocol v1.x revision","summary":"A compatible protocol revision will only be proposed when implementation feedback identifies a concrete, recurring gap that extensions cannot address cleanly.","evidence":[{"label":"Current stable protocol","href":"/protocol"},{"label":"Open an implementation issue","href":"https://github.com/44-pixels/handover-mcp/issues/new"}]},{"id":"ecosystem-integrations","title":"Additional storage and orchestration integrations","summary":"New integrations will be selected by demonstrated continuation workflows, not by connector count. Canonical Handover records and access rules remain the boundary.","evidence":[{"label":"MCP workflow","href":"/guides/mcp-workflow-for-multi-agent-collaboration"},{"label":"OpenAPI contract","href":"/openapi.json"}]},{"id":"protocol-governance","title":"Broader protocol governance","summary":"A multi-party governance model is conditional on independent adoption and sustained external contribution. Handover currently publishes the format and records changes transparently.","evidence":[{"label":"Protocol source","href":"https://github.com/44-pixels/handover-mcp"},{"label":"Changelog","href":"/changelog"}]}]}],"feedback":"https://github.com/44-pixels/handover-mcp/issues/new"}