blog: Phase 1 Ratify spike writeup - #47
Conversation
A non-technical companion to the joint technical note Ratify published, covering what the Phase 1 delegated-authority spike showed, the scope mapping cost, the confinement claim we corrected, and what Phase 1 explicitly does not establish. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded an engineering blog post about delegated authority verification between independent systems. It covers authorization scenarios, permission mapping, repository confinement, OS-level enforcement, and planned resource-binding validation. ChangesDelegated Authority Article
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@web/content/blog/trusting-an-agent-you-didnt-spawn.mdx`:
- Line 78: Update the alpha.16 reference in the blog text to identify it as an
integration candidate, or provide the pinned commit instead of describing it as
a released version. Preserve the explanation of resource binding while ensuring
readers do not interpret alpha.16 as an installable release.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 99a7b8f0-9074-4e45-b6cb-c497938ede30
📒 Files selected for processing (1)
web/content/blog/trusting-an-agent-you-didnt-spawn.mdx
|
|
||
| ## Where it goes | ||
|
|
||
| Ratify's alpha.16 adds resource binding, so authority names the thing it applies to and can only get narrower as it's passed along. We're validating against it now, then re-running the scenarios with the resource-bound and confinement cases included. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
ratifyprotocol.com writing agent-relay-phase1-technical-note alpha.16
💡 Result:
The term "agent-relay-phase1-technical-note" does not correspond to an official document or release version associated with the Ratify Protocol [1][2]. The Ratify Protocol (github.com/identities-ai/ratify-protocol) is an open-source cryptographic primitive for verifying delegated authority in human-to-agent and agent-to-agent interactions, currently in its alpha release phase [1][3]. While there is a separate entity known as Agent Relay (agentrelay.com), which provides a messaging layer for AI agents, it is distinct from the Ratify Protocol [4]. The Ratify Protocol versioning follows a standard semantic versioning pattern (e.g., v1.0.0-alpha.14, v1.0.0-alpha.15), and there is no alpha.16 release or technical note matching the requested title in the protocol's repository or documentation [1][5][6]. It is possible the query conflates different projects or refers to internal, non-public, or inaccurately remembered documentation [4][2].
Citations:
- 1: https://github.com/identities-ai/ratify-protocol
- 2: https://github.com/identities-ai/ratify-protocol/blob/main/README.md
- 3: https://github.com/identities-ai/ratify-protocol/blob/main/SPEC.md
- 4: https://agentrelay.com/docs/introduction
- 5: https://pkg.go.dev/github.com/identities-ai/ratify-protocol
- 6: https://github.com/identities-ai/ratify-protocol/blob/main/CHANGELOG.md
🌐 Web query:
"identities-ai/ratify-protocol" "alpha.16" "v1.0.0-alpha.15"
💡 Result:
The Ratify Protocol, maintained by Identities AI, Inc., is an open cryptographic trust protocol designed for AI agent authorization [1][2]. As of August 5, 2026, the latest release is v1.0.0-alpha.15, published on July 25, 2026 [3][4]. There is no "alpha.16" release currently available [5]. The protocol provides portable, quantum-safe delegated-authority proofs for human-agent and agent-agent interactions [1][6]. Key technical characteristics include: - Cryptography: Uses a hybrid approach combining Ed25519 and ML-DSA-65 (NIST FIPS 204), ensuring signatures are quantum-safe [3][1][6]. - SDKs: Reference SDKs are available for Go, TypeScript, Python, Rust, and C/C++ [3][2]. These are released atomically, ensuring byte-identical bundle verification across different languages [7]. - Status: The protocol is in alpha, meaning fixture bytes may change between releases [1][7]. - Licensing: The reference code is licensed under Apache-2.0, while the specification text is under CC-BY-4.0 [6][2]. The protocol is designed to be stateless and offline-capable, allowing verifiers to confirm agent authority, scope, constraints, and expiration in sub-millisecond timeframes without relying on a central authority [1][8][6].
Citations:
- 1: https://github.com/identities-ai/ratify-protocol
- 2: https://identities.ai/faq
- 3: https://github.com/identities-ai/ratify-protocol/releases/tag/v1.0.0-alpha.15
- 4: https://docs.identities.ai/start/quickstart/
- 5: https://github.com/identities-ai/ratify-protocol/releases
- 6: https://github.com/identities-ai/ratify-protocol/blob/main/SPEC.md
- 7: https://docs.identities.ai/sdk/packages/
- 8: https://ratifyprotocol.com/
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="web/content/blog/trusting-an-agent-you-didnt-spawn.mdx"
printf '--- file excerpt ---\n'
sed -n '68,88p' "$file"
printf '\n--- ratify mentions ---\n'
rg -n "alpha\.16|v1\.0\.0-alpha\.15|Ratify|resource binding|agent-relay-phase1-technical-note" "$file" web/content/blog || true
printf '\n--- tags/releases references in tracked files ---\n'
rg -n "identities-ai/ratify-protocol@|github.com/identities-ai/ratify-protocol|v1\.0\.0-alpha\.1[0-9]|alpha\.16" . --glob '!node_modules/**' --glob '!dist/**' --glob '!build/**' | head -200 || trueRepository: AgentWorkforce/agentrelay.com
Length of output: 258
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="web/content/blog/trusting-an-agent-you-didnt-spawn.mdx"
cat -n "$file" | sed -n '68,88p'
printf '\n--- ratify mentions ---\n'
rg -n "alpha\.16|v1\.0\.0-alpha\.15|Ratify|resource binding|agent-relay-phase1-technical-note" "$file" web/content/blog || true
printf '\n--- tags/releases references in tracked files ---\n'
rg -n "identities-ai/ratify-protocol@|github.com/identities-ai/ratify-protocol|v1\.0\.0-alpha\.1[0-9]|alpha\.16" . --glob '!node_modules/**' --glob '!dist/**' --glob '!build/**' | head -200 || trueRepository: AgentWorkforce/agentrelay.com
Length of output: 7338
Clarify alpha.16’s status before describing it as a release.
Ratify's latest release is v1.0.0-alpha.15, and there is no published alpha.16 Release. Call it “the alpha.16 integration candidate” or name the pinned commit so readers do not treat resource binding as an installable release feature.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@web/content/blog/trusting-an-agent-you-didnt-spawn.mdx` at line 78, Update
the alpha.16 reference in the blog text to identify it as an integration
candidate, or provide the pinned commit instead of describing it as a released
version. Preserve the explanation of resource binding while ensuring readers do
not interpret alpha.16 as an installable release.
Source: MCP tools
|
Preview deployed!
This is a Cloudflare Workers preview version of this PR's build. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Full rewrite by Khaliq. Adds the Agent Relay thesis framing and the bike permission-slip analogy, tightens the confinement correction. Corrects two accuracy points against the spike artifacts: Phase 2 is federation between two independent Relay deployments rather than two workspaces, and Agent Relay is the platform while Ratify is the protocol. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 participant
A plain-language companion to the technical note Ratify published on 2026-08-04. Same substance, written for people who aren't going to read a scope-mapping table.
Draft — needs a human pass before publish. Two things in particular:
What it covers
Checks
/blog/trusting-an-agent-you-didnt-spawn, blog index 200s, zero build errorslib/blog-authors.tskhaliq-voiceskill inproactive-agents/.agentworkforceNot included
A local-only fix for running the dev server in this repo sits uncommitted in
web/next.config.mjs(aRELAY_PRESERVE_SYMLINKS-gatedresolve.symlinks = false). It's unrelated to the post, so it's left out.npm run devis currently broken on machines wherenode_modulessymlinks off to another volume — happy to send that as its own PR.🤖 Generated with Claude Code
Summary by cubic
Adds a new blog post, “Trusting an agent you didn’t spawn,” a plain-language companion to Ratify’s Phase 1 delegated-authority spike, rewritten in author voice with corrected Phase 2 framing. Draft for review; before publish, confirm whether to name the Ratify reviewer and whether to assert the end-to-end novelty claim.
New Features
web/content/blog/trusting-an-agent-you-didnt-spawn.mdx; renders at/blog/trusting-an-agent-you-didnt-spawnand appears on the blog index.Refactors
Written for commit 06ff21e. Summary will update on new commits.