Skip to content

docs: align sibling-repo references with Agent Native Format - #177

Merged
shreyanshjain7174 merged 1 commit into
mainfrom
docs/reframe-anf-references
Jul 13, 2026
Merged

docs: align sibling-repo references with Agent Native Format#177
shreyanshjain7174 merged 1 commit into
mainfrom
docs/reframe-anf-references

Conversation

@shreyanshjain7174

Copy link
Copy Markdown
Collaborator

The sibling repo agent-contract-protocol is renamed to agent-native-format and reframed to lead with ANF, the token-minimal view format. See Clawdlinux/agent-native-format#22.

Changed (docs only, no code)

  • docs/DESIGN.md: 'ACP in one paragraph' section, repo-map line, and the 'working today' list now describe the sibling repo as ANF with the execution runtime as a component.
  • docs/MARKET-EVIDENCE.md: agent-contract-protocol -> agent-native-format path.
  • README.md: capability table Context row reframed to ANF.
  • docs/PITCH-SCRIPT.md: 'ACP numbers' -> 'execution runtime numbers'.

Deliberately left as-is

  • ROADMAP.md May 2026 entry: dated history, kept accurate to what happened.
  • clawd.acp.* OTel span attributes + acp-cache Grafana dashboard: stable telemetry contract for the execution-contract manifest, which still exists as the runtime. Renaming breaks dashboards and downstream span consumers. The observability chart docs that name 'ACP manifest IDs' are kept for consistency with the attribute name.

Flagged for a separate decision (not touched)

  • landing/ sub-app has stale content (dead clawdlinux-acp slug, old PRODUCT 01/02 framing). It has its own vercel.json and a CI quality gate, so it is live. Needs its own update pass.
  • naming-decision.md + RALPH_BACKLOG.md carry a stale, never-ratified 'Concord' recommendation that now conflicts with the ANF decision.

No code changed. Telemetry and CRDs untouched.

The sibling repo agent-contract-protocol is renamed to agent-native-format
and reframed to lead with ANF, the token-minimal view format. Update DESIGN,
MARKET-EVIDENCE, the README capability row, and the pitch script to match.

Deliberately left as-is:
- ROADMAP May 2026 entry (dated history).
- clawd.acp.* OTel span attributes and the acp-cache Grafana dashboard
  (stable telemetry contract for the execution-contract manifest).
- landing/ sub-app (own vercel.json + CI quality gate; has stale content
  to update separately).
- naming-decision.md Concord recommendation (stale, never ratified).

Signed-off-by: Shreyansh Sancheti <43677304+shreyanshjain7174@users.noreply.github.com>
Copilot AI review requested due to automatic review settings July 13, 2026 16:14

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates documentation across the repo to reflect the sibling repository rename/reframe from “agent-contract-protocol (ACP)” to “agent-native-format (ANF)”, positioning ANF as the token-minimal context format with an execution runtime component.

Changes:

  • Reframes the core “context” capability language in README around Agent Native Format (ANF).
  • Updates DESIGN and pitch narrative to describe ANF as the sibling repo and adjust terminology around benchmarks.
  • Updates MARKET-EVIDENCE to point readers to the renamed sibling repo documentation path.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
README.md Rewords the “Context” capability row to describe ANF + governed execution runtime.
docs/PITCH-SCRIPT.md Renames “ACP numbers” phrasing to “execution runtime numbers” in the slide script.
docs/MARKET-EVIDENCE.md Updates the sibling repo path reference from agent-contract-protocol to agent-native-format.
docs/DESIGN.md Renames the “ACP in one paragraph” section and updates repo-map + “working today” references to ANF.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/DESIGN.md
## Agent Native Format in one paragraph

Agent Contract Protocol is the same philosophy applied to tool calls. MCP answers what tools exist; ACP answers what execution is allowed for this agent right now. The server consumes MCP `tools/list` and returns a signed execution contract: scoped capabilities, identity binding, credential injection at the proxy (secrets never enter model context), declared ordering, egress and approval policy. Measured side effect: 64.7% to 97.4% fewer setup tokens and one round trip instead of up to 21, across five benchmark scenarios (see agent-contract-protocol/results). Separate repo, separate spec (v0.2 draft), feeds the same audit chain.
Agent Native Format (ANF) is the sibling repo. Its headline is a token-minimal view format. It translates system state into far fewer tokens for agents (see FORMAT.md). It also ships an execution runtime that applies the same governance philosophy to tool calls. MCP answers what tools exist. The runtime answers what execution is allowed for this agent right now. The server consumes MCP `tools/list` and returns a signed execution contract: scoped capabilities, identity binding, credential injection at the proxy (secrets never enter model context), declared ordering, egress and approval policy. Measured side effect: 64.7% to 97.4% fewer setup tokens and one round trip instead of up to 21, across five benchmark scenarios (see agent-native-format/results). Separate repo, separate spec, feeds the same audit chain.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

Comment thread docs/DESIGN.md
## Agent Native Format in one paragraph

Agent Contract Protocol is the same philosophy applied to tool calls. MCP answers what tools exist; ACP answers what execution is allowed for this agent right now. The server consumes MCP `tools/list` and returns a signed execution contract: scoped capabilities, identity binding, credential injection at the proxy (secrets never enter model context), declared ordering, egress and approval policy. Measured side effect: 64.7% to 97.4% fewer setup tokens and one round trip instead of up to 21, across five benchmark scenarios (see agent-contract-protocol/results). Separate repo, separate spec (v0.2 draft), feeds the same audit chain.
Agent Native Format (ANF) is the sibling repo. Its headline is a token-minimal view format. It translates system state into far fewer tokens for agents (see FORMAT.md). It also ships an execution runtime that applies the same governance philosophy to tool calls. MCP answers what tools exist. The runtime answers what execution is allowed for this agent right now. The server consumes MCP `tools/list` and returns a signed execution contract: scoped capabilities, identity binding, credential injection at the proxy (secrets never enter model context), declared ordering, egress and approval policy. Measured side effect: 64.7% to 97.4% fewer setup tokens and one round trip instead of up to 21, across five benchmark scenarios (see agent-native-format/results). Separate repo, separate spec, feeds the same audit chain.
@shreyanshjain7174
shreyanshjain7174 merged commit 93a3b5c into main Jul 13, 2026
8 checks passed
@shreyanshjain7174
shreyanshjain7174 deleted the docs/reframe-anf-references branch July 13, 2026 16:26
shreyanshjain7174 added a commit that referenced this pull request Jul 22, 2026
The sibling repo agent-contract-protocol is renamed to agent-native-format
and reframed to lead with ANF, the token-minimal view format. Update DESIGN,
MARKET-EVIDENCE, the README capability row, and the pitch script to match.

Deliberately left as-is:
- ROADMAP May 2026 entry (dated history).
- clawd.acp.* OTel span attributes and the acp-cache Grafana dashboard
  (stable telemetry contract for the execution-contract manifest).
- landing/ sub-app (own vercel.json + CI quality gate; has stale content
  to update separately).
- naming-decision.md Concord recommendation (stale, never ratified).

Signed-off-by: Shreyansh Sancheti <43677304+shreyanshjain7174@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants