oc·fleet
v1 · design partnersoc · fleet
managed agent + pledge
§ roadmap

What shipped, what's in flight, what's planned.

No dates we can't keep. We list the work in milestone-shaped buckets and update this page when buckets close. Design partners move items from 'planned' to 'in flight' by asking for them — adapter prioritization in particular is partner-driven.

v1.0 · launched 2026-04-28

public marketing surface, BIP-322 sign-in via the family auth host, dashboard preview for design partners, /api/contact via Resend, OG image, status page, CI + Vercel deploy.

  1. marketing pages with real copy

    /why, /integrations, /pricing, /reputation, /security, /charter, /about, /contact, /changelog, /status

    done
  2. BIP-322 sign-in routed to ochk.io

    consumer pattern · OC_AUTH_PUBLIC_JWK + OC_AUTH_ISSUER · no DB on fleet

    done
  3. in-repo dashboard mockup components

    real React, not bitmaps · embedded on /, /why, /reputation, /dashboard

    done
  4. CI + post-deploy healthcheck

    type-check + build + audit + curl-on-deploy

    done

v1.1 · shipped 2026-04-28

operator dashboard, real Stripe + Lightning checkout (env-driven), four more integration detail pages, language sweep correcting envelope semantics across the site.

  1. full operator dashboard

    /agents · /agents/new · /agents/[id] tabs · /audit · /billing · /team · /settings · auth-gated

    done
  2. real checkout, env-driven

    stripe (USD) · btcpay server (sats) · webhooks with raw-body signature verification · graceful sales fallback when env missing

    done
  3. integration detail pages

    anthropic · openai · vercel-ai · langgraph · each honest about adapter status

    done
  4. OC Stamp dogfooding language

    receipts named correctly as agent-action envelopes (kind 30084, oc-stamp shape) · oc-stamp anchor pipeline named over raw OTS

    done

v1.2 · shipped 2026-05-03

four agent-stack adapter packages published to npm, console.ochk.io rebranded to fleet.ochk.io across the family, real Postgres persistence wired up, federation/multisig spec drafted.

  1. four adapter packages on npm

    @orangecheck/agent-anthropic · agent-openai · agent-vercel · agent-langgraph · all v0.2.0 · all MIT

    done
  2. console.ochk.io → fleet.ochk.io rebrand

    family-wide rename · 10 repos · 6 npm packages bumped · Vercel project renamed · GitHub repo renamed

    done
  3. real backend persistence

    Postgres via Supabase pooler · Drizzle ORM · projects, members, delegations, actions, subdelegations, revocations, audit_bundles, invoices, api_tokens, webhook_endpoints all wired · /api/health/deep probes the live DB

    done
  4. subdelegation cron coverage

    cron workers (republish-nostr, retry-webhooks, upgrade-ots) handle subdelegations alongside delegations · ensures envelope-class symmetry in the audit pipeline

    done
  5. federation / Fedimint principal spec drafted

    principal.alg = federation · M-of-N guardian quorum · oc-agent-protocol spec/federation-v1.2 branch · /api/delegations/federation handler implemented

    in flight

v1.3 · in flight

wallet adapter wired into the dashboard signing flows, federation /signin path against the v1.2 spec, OIDC SSO + SCIM for the /team surface.

  1. wallet adapter wired into /agents/new + /reputation/compose

    consumes @orangecheck/wallet-adapter · real BIP-322 sign in user wallet · no key handling in fleet

    in flight
  2. federation /signin guardian collection UX

    M-of-N guardian quorum collection · sub-scope checking · backed by /api/delegations/federation

    next
  3. OIDC SSO + SCIM provisioning for /team

    corporate-IdP login on top of the BIP-322 binding · BIP-322 stays source of truth

    next

v2 · planned

pledge bonded-reputation premium tier, SOC 2 Type 1 report, lighthouse customer case studies.

  1. pledge premium tier

    /agents/[id] reputation tab · /a/[address] public profiles already shipping · pledge composer wired to wallet · sponsor / witness flows

    next
  2. SOC 2 Type 1 attestation

    in progress · Enterprise tier customers receive the report

    next
  3. 2 lighthouse customers in case-study form on /

    design-partner cohort exits via the case study

    planned

beyond v2

open-ended — driven by where the protocol family takes us and what design partners ask for.

  1. self-hosted managed-component bundle

    enterprise-tier customers run the OTS aggregator + audit-bundle service in their own VPC

    planned
  2. cross-family compositions surfaced in-product

    OC Vote governance over an agent fleet · OC Lock confidential payloads on agent receipts · OC Attest sybil-resistance on agent-to-agent calls

    planned
  3. Public proof gallery

    browse any address's authority + reputation history · independent of fleet.ochk.io reachability

    planned

Want a planned item moved up?

Adapter prioritization, federation flows, dashboard surfaces — these are all design-partner-driven. If your team needs something on this list now, ask. Items move from planned to in flight when a named design partner asks for them.

apply to design-partner cohort →