From 92783d9b3daba397c09c8f936ab75a8cdf896f5b Mon Sep 17 00:00:00 2001 From: Andrew Harvard Date: Fri, 9 Oct 2026 17:19:56 -0400 Subject: [PATCH 1/8] Name AI agents up front in the README intro The opening said "people and systems" and only named AI agents in the audience paragraph, and never said the demos are driven by talking to an agent. Borrow the intro page's "Why build it?" paragraph and its definition of GAP so the README and the site describe the problem and the protocol the same way, and say how you try the demos. Co-Authored-By: Claude Opus 5.5 --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4bc49fd..1592631 100644 --- a/README.md +++ b/README.md @@ -2,13 +2,13 @@ [![Specification status: draft, no published version yet](https://img.shields.io/badge/specification-draft-orange)][draft] [![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue)](LICENSE) -People and systems pass content to other people and systems without the exact version, the profile that defines it, the sources it used, or the decision that authorized its release. The recipient must reconstruct those facts from other tools and conversations or act without them. +Content moves between tools, people, and AI agents. The answers to "was this approved?" and "why does it say this?" usually stay behind, in a review thread or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. -**Governed Artifact Protocol (GAP)** defines records for released structured content. A release proof connects one content version to its profile revision, release authorization, and any declared source references. Consumers can verify which version was released and who authorized it without recreating the original workflow. They can verify a referenced source only when they can retrieve it under their own access and trust rules. +**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. A release proof connects one content version to its profile revision, release authorization, and any declared source references. A person or an AI agent receiving a release can verify which version was released and who authorized it without recreating the original workflow. They can verify a referenced source only when they can retrieve it under their own access and trust rules. GAP is for people building and operating applications where a person or an AI agent creates, authorizes, or consumes structured content. Each application chooses its interface, storage, permissions, and review policy. -**GAP is a working draft, with no published specification version yet.** The demos test it on synthetic data. +**GAP is a working draft, with no published specification version yet.** The demos test it on synthetic data; you try them by talking to an AI agent connected to a local MCP server. **Quick links:** [Documentation][docs] · [Working draft][draft] · [Run the demos][run-demos] @@ -58,7 +58,7 @@ Three independently written demo applications exercise the draft in different do | [Issue tracking][issue-tracking] | One Save can create, authorize, and release a ticket version when the actor holds the required permissions. Working-copy edits stay separate. | | [Research publishing][research] | A fictional paper on gummy worms telling stories in zero gravity pins its cited papers, peer review, and editor notes. Revisions and a source correction precede signed editorial approval and one final publication. | -All three run in one local, single-user Model Context Protocol (MCP) server on synthetic data, using JSON workspaces. GAP itself is transport-agnostic; MCP is the demos' chosen interface. No database, cloud account, or internal service is required. The demos are evaluation code with partial requirement coverage; they do not provide production security boundaries or demonstrate exchange between independently built systems. +All three run in one local, single-user Model Context Protocol (MCP) server on synthetic data, using JSON workspaces. You connect an AI agent through an MCP client and follow a walkthrough in plain conversation. GAP itself is transport-agnostic; MCP is the demos' chosen interface. No database, cloud account, or internal service is required. The demos are evaluation code with partial requirement coverage; they do not provide production security boundaries or demonstrate exchange between independently built systems. [Run the demos][run-demos] explains setup. [How the demos work][demo-tools] lists the application tools and the steps and decisions each performs. For implementation details, see [`demo/README.md`](demo/README.md) and [the demo architecture](demo/ARCHITECTURE.md). The [evaluation guide][evaluation] helps map your own workflow and estimate implementation and maintenance work. From 5dbf6f5cad08f36b9eb09407d11df4e32d3fc2c1 Mon Sep 17 00:00:00 2001 From: Andrew Harvard Date: Fri, 9 Oct 2026 17:26:20 -0400 Subject: [PATCH 2/8] Ask what content was based on and who signed off on it "Was this approved?" collided with the draft's approval decision, and "why does it say this?" read as a request for the author's reasoning. Ask the two questions a receiver can actually get answered, in the same words on the README and the intro page. Drop the status line's note about talking to an agent and say it once, plainly, in the demo section. Co-Authored-By: Claude Opus 5.5 --- README.md | 6 +++--- documentation/docs/intro/index.mdx | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 1592631..cc10a57 100644 --- a/README.md +++ b/README.md @@ -2,13 +2,13 @@ [![Specification status: draft, no published version yet](https://img.shields.io/badge/specification-draft-orange)][draft] [![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue)](LICENSE) -Content moves between tools, people, and AI agents. The answers to "was this approved?" and "why does it say this?" usually stay behind, in a review thread or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. +Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. **Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. A release proof connects one content version to its profile revision, release authorization, and any declared source references. A person or an AI agent receiving a release can verify which version was released and who authorized it without recreating the original workflow. They can verify a referenced source only when they can retrieve it under their own access and trust rules. GAP is for people building and operating applications where a person or an AI agent creates, authorizes, or consumes structured content. Each application chooses its interface, storage, permissions, and review policy. -**GAP is a working draft, with no published specification version yet.** The demos test it on synthetic data; you try them by talking to an AI agent connected to a local MCP server. +**GAP is a working draft, with no published specification version yet.** The demos test it on synthetic data. **Quick links:** [Documentation][docs] · [Working draft][draft] · [Run the demos][run-demos] @@ -58,7 +58,7 @@ Three independently written demo applications exercise the draft in different do | [Issue tracking][issue-tracking] | One Save can create, authorize, and release a ticket version when the actor holds the required permissions. Working-copy edits stay separate. | | [Research publishing][research] | A fictional paper on gummy worms telling stories in zero gravity pins its cited papers, peer review, and editor notes. Revisions and a source correction precede signed editorial approval and one final publication. | -All three run in one local, single-user Model Context Protocol (MCP) server on synthetic data, using JSON workspaces. You connect an AI agent through an MCP client and follow a walkthrough in plain conversation. GAP itself is transport-agnostic; MCP is the demos' chosen interface. No database, cloud account, or internal service is required. The demos are evaluation code with partial requirement coverage; they do not provide production security boundaries or demonstrate exchange between independently built systems. +All three run in one local, single-user Model Context Protocol (MCP) server on synthetic data, using JSON workspaces. Each walkthrough is a conversation with an AI agent connected to that server. GAP itself is transport-agnostic; MCP is the demos' chosen interface. No database, cloud account, or internal service is required. The demos are evaluation code with partial requirement coverage; they do not provide production security boundaries or demonstrate exchange between independently built systems. [Run the demos][run-demos] explains setup. [How the demos work][demo-tools] lists the application tools and the steps and decisions each performs. For implementation details, see [`demo/README.md`](demo/README.md) and [the demo architecture](demo/ARCHITECTURE.md). The [evaluation guide][evaluation] helps map your own workflow and estimate implementation and maintenance work. diff --git a/documentation/docs/intro/index.mdx b/documentation/docs/intro/index.mdx index 83ba87d..d1b5cb6 100644 --- a/documentation/docs/intro/index.mdx +++ b/documentation/docs/intro/index.mdx @@ -14,7 +14,7 @@ A shared set of rules that applications follow as content is created, reviewed, ## Why build it? -Content moves between tools, people, and AI agents. The answers to "was this approved?" and "why does it say this?" usually stay behind, in a review thread or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. +Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. [Why GAP?](why-gap.md) follows one change and shows what its records tell the next reader. From 62c1162db74341d235b4b7fe323658654eb0fc83 Mon Sep 17 00:00:00 2001 From: Andrew Harvard Date: Fri, 9 Oct 2026 17:30:08 -0400 Subject: [PATCH 3/8] Name agent sessions where release context gets left behind A review thread is where "who signed off on it?" usually lives; an agent session is where "what was this based on?" often ends. List both, on the README and the intro page, so the places match the questions and the tools, people, and AI agents named before them. Co-Authored-By: Claude Opus 5.5 --- README.md | 4 ++-- documentation/docs/intro/index.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index cc10a57..0edb5ea 100644 --- a/README.md +++ b/README.md @@ -2,9 +2,9 @@ [![Specification status: draft, no published version yet](https://img.shields.io/badge/specification-draft-orange)][draft] [![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue)](LICENSE) -Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. +Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread, an agent session, or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. -**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. A release proof connects one content version to its profile revision, release authorization, and any declared source references. A person or an AI agent receiving a release can verify which version was released and who authorized it without recreating the original workflow. They can verify a referenced source only when they can retrieve it under their own access and trust rules. +**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Those records travel with each released version as a release proof. A person or an AI agent receiving it can check which version was released, who authorized it, and which sources it names, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. GAP is for people building and operating applications where a person or an AI agent creates, authorizes, or consumes structured content. Each application chooses its interface, storage, permissions, and review policy. diff --git a/documentation/docs/intro/index.mdx b/documentation/docs/intro/index.mdx index d1b5cb6..eb18cfa 100644 --- a/documentation/docs/intro/index.mdx +++ b/documentation/docs/intro/index.mdx @@ -14,7 +14,7 @@ A shared set of rules that applications follow as content is created, reviewed, ## Why build it? -Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. +Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread, an agent session, or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. [Why GAP?](why-gap.md) follows one change and shows what its records tell the next reader. From 4f563783b1c6742a0c875dc1946cfd169e8c01aa Mon Sep 17 00:00:00 2001 From: Andrew Harvard Date: Fri, 9 Oct 2026 17:32:05 -0400 Subject: [PATCH 4/8] Describe the release records as a context packet in the intro The intro doesn't need the formal term yet. Call the records a context packet that travels with each release, as "Why GAP?" does, and leave "release proof" to "How GAP works," where it is defined. Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0edb5ea..977d1df 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread, an agent session, or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. -**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Those records travel with each released version as a release proof. A person or an AI agent receiving it can check which version was released, who authorized it, and which sources it names, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. +**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Think of them as a context packet that travels with each released version. A person or an AI agent receiving it can check which version was released, who authorized it, and which sources it names, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. GAP is for people building and operating applications where a person or an AI agent creates, authorizes, or consumes structured content. Each application chooses its interface, storage, permissions, and review policy. From 5fd2be1e158013f99d71cf72c36a16f428c437cf Mon Sep 17 00:00:00 2001 From: Andrew Harvard Date: Fri, 9 Oct 2026 17:33:37 -0400 Subject: [PATCH 5/8] State that the records travel as a context packet MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "Think of them as…" told the reader what to do instead of saying what happens. Say that records of the rules, sources, and decisions travel with each released version as a context packet. Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 977d1df..b4e372e 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread, an agent session, or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. -**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Think of them as a context packet that travels with each released version. A person or an AI agent receiving it can check which version was released, who authorized it, and which sources it names, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. +**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Records of all three travel with each released version as a context packet. A person or an AI agent receiving it can check which version was released, who authorized it, and which sources it names, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. GAP is for people building and operating applications where a person or an AI agent creates, authorizes, or consumes structured content. Each application chooses its interface, storage, permissions, and review policy. From dd06557de2511556674401468ec7986edb38542c Mon Sep 17 00:00:00 2001 From: Andrew Harvard Date: Fri, 9 Oct 2026 17:36:04 -0400 Subject: [PATCH 6/8] Describe the release records as a packet of context "As a context packet" read like a term the reader had to learn. Make it a plain comparison; the guides introduce the term later. Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b4e372e..e543d91 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread, an agent session, or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. -**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Records of all three travel with each released version as a context packet. A person or an AI agent receiving it can check which version was released, who authorized it, and which sources it names, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. +**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Records of all three travel with each released version, like a packet of context. A person or an AI agent receiving it can check which version was released, who authorized it, and which sources it names, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. GAP is for people building and operating applications where a person or an AI agent creates, authorizes, or consumes structured content. Each application chooses its interface, storage, permissions, and review policy. From 032a09509a10c7c839be8a7071965be5bd009182 Mon Sep 17 00:00:00 2001 From: Andrew Harvard Date: Fri, 9 Oct 2026 17:36:57 -0400 Subject: [PATCH 7/8] Answer the intro's two questions in the GAP paragraph "Check which version was released" read clinically. Say that a receiver can read the content and check who signed off on it and what it was based on, answering the questions the opening paragraph asks. Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e543d91..59bf1bd 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread, an agent session, or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. -**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Records of all three travel with each released version, like a packet of context. A person or an AI agent receiving it can check which version was released, who authorized it, and which sources it names, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. +**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Records of all three travel with each released version, like a packet of context. A person or an AI agent receiving it can read the content and check who signed off on it and what it was based on, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. GAP is for people building and operating applications where a person or an AI agent creates, authorizes, or consumes structured content. Each application chooses its interface, storage, permissions, and review policy. From 03720e687568c67954715a6d9030c17a050ead83 Mon Sep 17 00:00:00 2001 From: Andrew Harvard Date: Fri, 9 Oct 2026 17:38:20 -0400 Subject: [PATCH 8/8] Tie the receiver's check back to where context gets left behind "Without recreating the original workflow" read clinically. Name the review thread and agent session from the opening paragraph instead. Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 59bf1bd..f5c2cd8 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Content moves between tools, people, and AI agents. The answers to "what was this based on?" and "who signed off on it?" usually stay behind, in a review thread, an agent session, or someone's memory. When an AI agent receives content through a file, a copied answer, or another tool, its available context may differ from the context in which that content was created. -**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Records of all three travel with each released version, like a packet of context. A person or an AI agent receiving it can read the content and check who signed off on it and what it was based on, without recreating the original workflow. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. +**Governed Artifact Protocol (GAP)** defines how applications keep content connected to its rules, source references, and release decisions. Records of all three travel with each released version, like a packet of context. A person or an AI agent receiving it can read the content and check who signed off on it and what it was based on, without digging through the review thread or agent session it came from. Checking a source's own content requires retrieving it under the receiver's own access and trust rules. GAP is for people building and operating applications where a person or an AI agent creates, authorizes, or consumes structured content. Each application chooses its interface, storage, permissions, and review policy.