UNIHODL · Agent Handoff SDK · Roadmap

The honest gap list.

v1.0 is a real protocol, not a marketing artifact — but it has 13 known gaps. We track them in the open. If you’re evaluating UNIHODL for production, read this page before the spec.

Why publish the gaps?

Engineering buyers trust roadmaps that admit what’s missing. Hidden gaps are how protocols lose enterprise deals quietly. Listed gaps are how protocols win them with no surprises in week 4 of integration.

Shipped in v1.0

v1.0 · shipped

  • v1.0 core: tokens, hydration, MCP server, JWKS

    Resume token mint, audience-bound JWTs with EdDSA, /v1/sessions/{id}/hydrate with prompt-ready format, MCP server over stdio, public JWKS for token validation. Reference integrations for Claude / Gemini / OpenAI Agents / LangGraph.

v1.1 (Q3 2026)

v1.1 · q3 2026

  • Typed schema for write endpoints

    write:notes and write:next_step are listed as scopes but the request body schemas for POST /sessions/{id}/notes and the next_step mutation aren't fully specified. Risk: agents dump unstructured text and the typed reasoning graph degrades. v1.1 adds canonical typed-node append schema.

  • Optimistic concurrency on writes

    Two agents holding tokens against the same session, both calling write:next_step — who wins? v1.1 introduces If-Match: <fingerprint> headers and a rejected_by_concurrency error code so callers can retry against fresh state.

  • Full webhook payload + signing spec

    session.held, session.shared, session.resumed, session.handed_off events are listed, but payload shapes, HMAC signing keys, and replay protection (timestamp + nonce window) aren't specified. v1.1 adopts the Svix/Stripe webhook model: per-endpoint secret, X-Unihodl-Signature header, 5-minute replay window.

  • Per-session hydration counter (defense-in-depth)

    max_hydrations is enforced per-token. A leaked token can replay max_hydrations times before revocation propagates. v1.1 adds an additional per-session counter and a workspace-level circuit breaker if hydrations spike.

  • Explicit session immutability model

    Each HOLD must produce an immutable, fingerprinted snapshot — never accumulate against the same session_id silently. v1.0 implementation matches this; v1.1 adds the explicit invariant to the spec plus a sessions.parent / sessions.children chain so a thread of resumed work is queryable.

  • Published token-cost budgets per format

    max_tokens_estimate hint exists, but the spec should publish typical token costs at default policies (median 850, p95 3.4k, p99 12k) so callers can plan. v1.1 ships measured benchmarks with a public leaderboard.

  • SLA and uptime claim

    Agent-hot-path infrastructure needs a public uptime claim. v1.1 ships a status page at status.unihodl.app and commits to 99.9% best-effort SLA on the Pro tier, 99.99% on Enterprise. Status page is read by an OpenStatus probe network.

  • User revocation cascade

    When a user uninstalls the extension or deletes their account, all outstanding tokens auto-revoke. v1.1 wires the cascade into /hydrate preflight: a deleted user's token returns invalid_token immediately, regardless of exp.

  • Full MCP tool schemas + discovery

    MCP server advertises tools [hold, resume, hand_off] and resources unihodl://session/{id}, but full input_schema / output_schema for every tool plus resource list semantics aren't fully published. v1.1 ships the complete MCP manifest and a tested integration matrix with Claude Desktop, Cursor, Cline, Continue.

v1.2 (Q4 2026)

v1.2 · q4 2026

  • Calibration story for reasoning_thread.confidence

    Nodes can carry confidence: 0.78. Where does the score come from — on-device Gemini Nano? Heuristic? Without a calibration claim agents will treat it as authoritative and silently-wrong confidence is worse than no confidence. v1.2 ships a calibration whitepaper, a confidence_source field on every node, and a published Brier score on a held-out set.

  • Cross-org handoff trust boundary

    delegator object signals consent for human-to-human handoff but the org-level attestation flow for B2B handoffs (Sarah@CompanyA → consultant@CompanyB) isn't specified. v1.2 ships an org-attestation step plus an OAuth-style cross-tenant consent screen.

  • GDPR data residency + DSAR

    EU enterprise will ask: where is the unredacted session stored? v1.2 ships region-pinned hosting (eu-west-1 dedicated tier), right-to-erasure cascading to all tokens and audit records, and a self-serve DSAR export.

Researching

researching

  • Public pricing & metering shape

    Per-hydration? Per-session? Per-seat? Out of strict spec scope but blocking GTM. Direction: 1k hydrations / month free, $0.001 / hydration above, plus a per-seat audit-log access tier. Final shape lands when v1.0 graduates from public preview.

See a gap we missed? Email developers@unihodl.app — we add it here, not in a private doc.

← SDK overview · Read the v1.0 spec →