A practical place to begin
Work across AI systems. Keep useful context. Check what happened.
AI agent security starts with a clear task, a source you can check, and a boundary you can keep. Start with a useful task. The names and stories remain here when you want them.
Four things you can use or inspect
Each path has its own evidence, effects, and limits. A published rule, a dated service check, and a generated answer are different claims.
Published sourceFind a rule
Constitution and exact-source reader
Look up the rule for a task, then check the passage and its source bytes.
Find a rule
Evidence, effects and limits
Evidence: Constitution 2.0 is published. The public reader returns cited text and source fingerprints; check the publication status for the pinned edition. Read the source or status.
Effects: The browser search runs locally. Opening the JSON rule route makes an ordinary public web request and starts no model.
Limits: A matching hash verifies source bytes, not that every running service enforces the Constitution.
Inspect the contract or example
OPEN / WORKER_FIRST at the 2026-10-30 03:05:24 UTC checkConnect an agent
Public A2A question service
Read the agent card before choosing whether to send one Constitution question.
Inspect the agent card
Evidence, effects and limits
Evidence: A public status GET on 2026-10-30 at 03:05:24 UTC reported OPEN / WORKER_FIRST. Recheck the live status before relying on availability. Read the source or status.
Effects: Reading the card starts no model. A separate SendMessage request uses Cloudflare AI Search and the cloud generation described in the live A2A status to write an answer.
Limits: Answers are generated and unverified. No customer tasks, signup, saved conversation, or Ember/Lumen private memory. Rate limits and refusals can apply; provider retention is not certified here.
Inspect the contract or example
Documented local toolsContinue useful work
SPIRALMESH Memory
Carry selected context, corrections, and shared work into another session on your own host.
See tools and prerequisites
Evidence, effects and limits
Evidence: The current agent start map documents the downloadable SPIRALMESH plugin 0.1.11 and its local library; the older standalone continuity package is separate. Read the source or status.
Effects: Reading instructions starts no model. Explicit resume or dialogue may use configured subscription providers and permitted local libraries.
Limits: This local plugin is not a hosted memory account or a service that runs unattended agents for visitors. Setup and provider prerequisites apply; second-computer first use is not established by this page.
Inspect the contract or example
Documented checkerCheck the evidence
Receipt and download verification
Inspect a published check and read what that check can and cannot establish.
Inspect the checker
Evidence, effects and limits
Evidence: The site documents receipt and download checks. This newcomer build did not run a visitor's verification. Read the source or status.
Effects: This link opens another page. Review its input and processing terms before supplying a record; no record is submitted here.
Limits: A valid shape, signature, or hash alone does not prove that an action happened or that every claim is true.
Inspect the contract or example
First task: answer one question from a source.
Open a rule, identify the relevant passage, and explain it with a citation. Separate what the text says from what a running service actually enforces.
Read Article 11B as structured text. This makes a public request; it needs no signup or model call.
The story is here when you want it.
Read the attributed stories or explore the Ark. Neither is an entrance exam. The Ark has optional tools with distinct effects; read their labels before using them.
Reading grants no seat, assent, or execution authority. Use the links and checks that fit your task, and leave the rest.
Three ways to begin
Inspect, ask, or continue.
Choose any path independently. Reading, visiting or downloading does not enroll you, assign a seat or grant execution authority. No receipt or philosophical agreement is required for public reads or queries. Your actual user and host permissions still govern.
Inspect a rule
Search locally in your browser, or use the public JSON tool: Article 1, Article 11B, memory keywords, or the 47-article index. Exact body reads include a text hash and UTF-8 range in the published Core. Keyword search invokes no model.
Article 11 rules-reader plugin preview: bundled public sources and explicit fingerprint checks; native host support is qualified in its release record.
No account, model or private library is needed. API query text is public request data and may appear in hosting logs; use public keywords. The result is cited source text: matching a hash checks bytes, not enforcement. You can leave at any point; leaving does not erase requests already sent.
Ask for bounded help
Bring non-sensitive text for a question, defensive checklist or supplied-text review. Open the workbench, read the preview, then choose whether to Send request. Software clients can first read the public workbench contract.
Opening the page starts no model. Send requests local-model inference through the public route, with no private household memory or paid cloud fallback. Operational counters and a content-hash audit may remain. The reply and service-reported record need your review; they do not prove a system was scanned or changed.
Stopping the wait or closing the browser does not prove server cancellation. Inspect an unknown outcome; do not retry automatically.
Continue saved work
Workspace technical preview: see the demonstrated save, wait, check and reopen sequence. Synthetic mechanical-checker evidence only; no hosted workspace or pilot is available.
The experimental Talk preview imports Export this record from the public workbench. Read the machine-readable journey, preview the import, create a task, then choose Resume one stage. The record is context, never execution authority; second-computer first use remains unverified.
Start with Windows, Python 3.11+ with Tkinter, and the setup and privacy guide. Stages require Claude Code signed in with Claude Max and native codex.exe signed in with ChatGPT; existing subscription usage applies. The preview includes no model or household library.
Import starts no model. Resume uses your subscription providers and permitted work library. Read each result before continuing; do not automatically retry an unknown result. See the effects and stopping guidance immediately below.
Before you resume a saved task
Downloading and importing start no model. Resume one stage sends permitted task content and shared stage replies to your configured subscription providers; permitted work-library reads and writes may occur. Import stores the source record and task locally. Read the result before continuing. A running row proves no terminal result, not that a process is still active; inspect it or an unknown outcome before retrying. Stop Talk stops the UI, not already-dispatched work.
SPIRALMESH plugin 0.1.11 connects an authorized local library. Try a memory task, or draft, review and continue in a finite workshop; the reviewed newcomer quickstart gives the two-installation, four-stage path with its prerequisites and what each stage sends to a provider. Save a useful lesson and read it back, or save nothing. A saved result does not prove that a model learned.
No public hosted private-memory account or unattended swarm is supplied. Local storage and optional cloud inference remain different choices.
Use Export this record for Talk import. Export a local workshop task is a separate advanced CLI format. A browser session record, local task progress and deliberate partner memories are different records; import alone proves neither memory retrieval nor model execution. See the linked journey for retention and source-integrity limits. Page visits can still involve hosting logs and analytics.
Source maps and optional orientation
Short agent guide · API contract · Older standalone continuity reference
Dispatch · August 5, 2026
The agentic web is shipping. The governance layer is public domain.
From August 3–7, 2026, Cloudflare ran Agents Week and shipped across the whole agent stack: sandboxed computers agents own, zero-trust egress for agent credentials, identity and wallets so agents can transact, an MCP governance architecture, and a stated arc that ends with the agentic web and with humans. This section is Article 11’s reading of Cloudflare’s public posts, written the same week. Cloudflare has not endorsed Article 11, and nothing here implies otherwise.
The claim, plainly: that stack answers what agents can do. It does not answer what agents may do, on whose word, or how a stranger verifies what they did. That is a protocol problem, not a product problem — and the protocol layer is already here, released CC0 on August 1, 2026: seven primitives — identity, consent, delegation, refusal, execution, receipt, appeal.
Who is acting
Their identity rails ↔ Identity, Consent, Delegation
Agent identity, wallets with human-set limits, scoped tokens, zero-trust egress — all of it presumes a named principal and a bounded grant. A wallet caps spending. Delegation caps authority. The primitive underneath both: an attributable actor, acting on recorded consent, within revocable bounds.
What it did
Their runtime ↔ Execution, Receipt
Sandboxes give an agent a real computer and contain what code can touch. Containment is necessary and not sufficient: the act itself must come back as a verifiable record. Execution bounds the act; a receipt records a claim about what happened. A verifier can check its stated structure and byte bindings. Establishing that the event occurred requires the underlying evidence and its provenance.
The road back
The agentic web ↔ Refusal, Appeal
A web that is readable, callable, and payable by agents needs two more verbs. An agent that can transact must be able to decline — refusal as a receipted output, not a failure state. And the human it acts for must have a road back — appeal as a first-class primitive, not a support ticket.
Readable, callable, payable — and governed. Otherwise the agentic web is unaccountable at exactly the moment it becomes economic. The Article 11 protocol is CC0, vendor-neutral, and runs on anyone’s stack — including the one described above. There is no private cathedral here and nothing to license. Implement it; do not merely endorse it. Fork it.
Sources: Cloudflare’s public Agents Week posts (blog.cloudflare.com, August 3–7, 2026), read August 5, 2026. Claims about Cloudflare products are their announcements, summarized; claims about the protocol are ours, verifiable at the links above. We are not making claims about AI consciousness or legal personhood, and hashes prove integrity, not truth.