Lattice

Upgrade bay

Dock 2027 without a rewrite.

Each slot implements Adapter Protocol 1.0. Flip a node on and the ship pulse grows a step — the four 2026 rails stay put. This is how Lattice absorbs whatever actually ships next year: agents, stablecoin settlement, vectors, edge inference, passkeys, traces.

  • Compute · beside Vercel

    Agent Runtime

    Available

    A ship agent that watches GitHub, opens Vercel previews, and can roll forward when checks pass.

    Sits beside Vercel. Same Adapter Protocol 1.0 events — no new deploy target required.

    Inspect

  • Payments · beside Stripe

    Stablecoin Rails

    Available

    USDC-class settlement next to Stripe. Cards stay; a second payout path docks on the same webhook bus.

    Strangler pattern: Stripe remains Checkout. New settlement events share pay.webhook so the data plane does not fork.

    Inspect

  • Data · beside Supabase

    Vector Mesh

    Available

    Embeddings and retrieval in the same Postgres project. Queries stay SQL; recall becomes a capability.

    Extends Supabase rather than replacing it. pipeline_events gain an embedding column; old rows stay valid.

    Inspect

  • Compute · beside Vercel

    Edge Inference

    Available

    On-request model calls at the CDN edge — scoring, classify, or draft without a new origin.

    Invoked from Vercel functions. If the model vendor changes in 2027, only this node swaps.

    Inspect

  • Identity · beside Supabase

    Passkey Mesh

    Available

    WebAuthn and wallet-grade identity beside Supabase Auth. Sessions stay; the factor upgrades.

    auth.session remains the lattice event. New factors bind without migrating user ids.

    Inspect

  • Observe · beside GitHub

    Ship Tracer

    Available

    One trace from commit to deploy to charge to row. The lattice becomes auditable without extra dashboards.

    Subscribes to every core node's events. Drop it in; it does not own a rail of its own.

    Inspect