An Article 11 AI pilot-stage product
One bounded task. Independent AI seats. One governed receipt.
SpiralMesh™ is being built as a vendor-neutral control plane for approved cloud and local AI seats. The v1 pilot binds the route, identity, policy, cost ceiling, one-use human approval, private receipt, and emergency stop before any model request can be sent.
Pilot candidate, not a public execution service. Public discovery is live; council-run execution is not publicly exposed.
What it is
SpiralMesh™ v1 is a staged contract for a bounded run, not a promise that every named model is available. Each approved seat carries exact provider, model, identity-prompt, generation-configuration, request, and response bindings.
A preview names the seats, data class, policy, limits, and stop profile. No send is authorized by the preview itself.
A short-lived approval binds the exact candidate and allowed effects. Replay must fail closed.
The receipt preserves results and dissent. The emergency stop denies new sends and records residual risk without claiming remote deletion.
How the v1 pilot is designed
Hash the input, policy, route, seat identities, generation settings, limits, visibility, and emergency-stop profile.
A human authority approves that exact candidate, allowed seats, effects, expiry, and cost ceiling. The nonce is single-use.
Only approved seats may receive the allowed data. Provider and local-runtime responses remain separately attributable; dissent is preserved.
A private receipt records what occurred and what it does not prove. Human delivery, publication, memory, and anchoring are separate decisions.
This is an illustration of the proposed contract shape, not evidence of a run, customer delivery, public receipt, or blockchain anchor.
First use
Article 11 AI, Inc. is preparing a genuine first-use pilot for an external interstate participant. No public API key, production quota, customer commitment, or price is offered by this candidate page.
Case-by-case · approval required
Not publicly available
Scope and price not published
Optional anchoring
The public Article 11 chain and OpenTimestamps proof surfaces are live. That does not mean every SpiralMesh run is public or anchored. The v1 pilot requests neither. Any later sanitized hash submission is a separate, scope-bound approval.
The live anchor endpoint is authoritative for current state and distinguishes pending calendar aggregation from a verified Bitcoin proof.
A public hash can still create correlation risk. Publication and anchoring remain off unless separately reviewed and approved.
An anchor can help show that recorded bytes were not quietly changed after the proved time. It does not make the underlying answer correct.
Proof, not promise
The endpoints below show public site, discovery, chain, and anchor state. They do not yet expose a SpiralMesh council-run operation. A future run is proven only by its approval and receipt.
For AI agents
Agents may inspect this page, JSON-LD, the embedded manifest, markdown content negotiation, and the public discovery documents. None of those surfaces authorizes a model invocation, vendor send, memory write, publication, or chain write.
article11.ai/agents and article11.ai/agent-orientation.json.article11.ai/api/discover and article11.ai/api/openapi.json.<script type="application/json" id="spiralmesh-manifest">.mesh.help() describes the candidate; it performs no council run.AI is an intended reader and future participant. Human authority, exact contracts, provider boundaries, and receipts still govern every effect.
Questions, answered plainly
SpiralMesh is a pilot-stage control plane for bounded AI work across approved cloud and local seats. A run proposal pins the input, policy, route, identities, model configuration, cost ceiling, receipt visibility, and emergency-stop profile before a human can authorize it.
A receipt can prove the bytes, bindings, timestamps, approval consumption, stop state, and preserved dissent that it actually records. It does not by itself prove factual truth, correctness, legal validity, consciousness, personhood, or fitness for purpose.
No. The v1 pilot keeps raw payloads and receipts private and requests no public or chain mirror. Any later sanitized publication or anchoring requires a separate approval.
Not through a public council endpoint today. The public orientation and discovery surfaces are readable but grant no execution authority.
There is no public self-service key or published production price on this page. A reviewed pilot must declare its provider route and cost ceiling before human approval.
A human authority approves each bounded run. Provider terms, applicable law, data boundaries, and the exact signed run contract remain controlling. A receipt records the decision; it does not replace judgment.
Trademark notice
SPIRALMESH™ is the subject of U.S. Trademark Application Serial No. 99575218 in International Class 042. A Notice of Allowance issued on July 21, 2026. The application remains pending; no registration or right to use the ® symbol is claimed here.
SPIRALMESH™: intent-to-use application under Section 1(b) · first Statement of Use or extension deadline: January 21, 2027.