A protocol shaped in public through a reference runtime

Modern AI agent stacks are fragmented. The failure mode is not model quality — it is the handoff. Work moves across planning, execution, approvals, files, and memory without one durable object holding the chain together. Agintent proposes one shared envelope and one reference orchestrator that proves the model against real execution.

The protocol vocabulary, the v0.1 envelope spec, protocol-native API routes, a capability-first routing foundation, and a working reference orchestrator runtime. The orchestrator accepts raw intent, normalizes it into envelopes, routes by capability, tracks runs, and keeps artifacts and memory attached to the originating work.

A stronger run contract, better human-in-the-loop supervision, richer artifact and memory semantics, external emit-and-consume flows, and production hardening. The current commercial posture is early design partners, pilot conversations, and protocol followers — not public self-serve onboarding.

Protocol-first, app-second. Humans remain first-class actors. Storage and runtime compatibility is acceptable; vocabulary drift is not. Every run should be inspectable. Outputs should stay portable across storage backends. The reference implementation should stay simple enough to ship.

Object models are easy to change when one team owns one runtime and nearly impossible to change once an ecosystem depends on them. Defining a clean, versioned envelope at the concept-plus-reference-implementation stage is the entire point — get the durable object right before the wider agent ecosystem hardens around worse defaults.