Independent implementations will determine whether APH provides a practical cryptographic verification and notarization layer for interactions between agents controlled by different parties.

state: expiredheat: lowuncertainty: highknownscott: mediumagentic-security agent-handoff-protocols agent-authenticationSquillo

What is this?

APH is presented as a draft protocol for cryptographic verification and notarization of interactions between agents controlled by different parties, accompanied by open-source engine and server implementations in Rust and N. The evidence titles indicate a v0.1.0 draft specification and an initial public repository commit, while the case associates Squillo with the project. The supplied web snippets do not independently document APH, its architecture, authorship, adoption, or interoperability, so the claim that independent implementations will establish its practicality remains an untested hypothesis.

Why it matters to Scott

The radar already tracks this same development in `radar:agent-handoff-protocol-adoption`. APH directly bears on Scott’s Agent Provenance Stack and cryptographic-trust model for authenticated, auditable cross-party delegation, but the supplied evidence establishes only a draft and project-provided implementations—not the independent interoperability results that could validate, extend, or challenge his architecture.

ip:framework.agent-provenance-stackip:concept.cryptographic-trustip:concept.capability-tokensip:concept.execution-attestationradar:agent-handoff-protocol-adoptionradar:concept.agent-authenticationradar:concept.agent-interoperability

queries asked of Scott's wikis

cross-party agent authentication and trust
cryptographic audit trails for agent actions
secure agent handoffs and delegation
protocol interoperability for multi-agent systems
non-repudiation and notarization in agent workflows
agent identity, credentials, and key management

Measured heat

no measured readings yet — the hourly heat pass fills this in

How the heat travelled

no chain yet — the hourly chain pass fills this in

Evidence (4) — ⭐ canonical anchor

source	object	author	score	comments
🟧 hn	Show HN: Opensourcing APH Engine and Servers in Rust and N Lang	scott-b	4	0
🟧 echo.github ⭐	The repository’s root commit is explicitly titled “Initial public draft of the APH protocol specification,” with the v0.1.0-draft spec, exam	Scott Wyatt	—	—
🟧 hn	An MCP server for cameras that signs a receipt for every agent action	mkvisher	2	0
🟧 hn	BTP v2.2 – An open, offline cryptographic trust protocol for AI agents	itsub_sa	1	0

Interpretation history

2026-08-23T00:22:54Z
Repeated checks have produced only adjacent notarization and trust projects, with no independent APH implementation, interoperability test, adoption, or security review. The APH-specific episode has faded and can be reopened if substantive external activity appears.
2026-08-20T23:35:37Z
BTP v2.2 adds another independent approach to cryptographic agent trust, broadening the competing design space but providing no APH implementation, interoperability result, adoption, or security review. APH’s practical cross-party notarization value therefore remains untested.
2026-08-20T23:23:04Z
evidence attached: hn.story.49381508 — An open-source cryptographic trust protocol is relevant competing evidence for practical agent-to-agent verification, though this low-engagement post lacks validation details.
2026-08-20T16:42:47Z
The signed-receipt camera MCP implementation validates interest in action notarization as a broader pattern, but it neither implements APH nor tests cross-party APH interoperability, so the protocol-specific hypothesis remains unadvanced.
2026-08-20T16:24:01Z
evidence attached: hn.story.49376254 — A concrete MCP implementation using signed receipts for every camera action provides relevant independent evidence for agent-interaction notarization and auditability.
2026-08-18T16:58:42Z
The staleness check adds no external implementation, interoperability test, adoption, or security review; APH remains a first-party draft whose practical cross-party trust value is untested.
2026-08-16T16:31:26Z
The slight engagement increase adds no independent implementation, interoperability, adoption, or security evidence; APH remains an untested project-authored draft awaiting substantive external activity.
2026-08-14T15:50:52Z
The one-time re-evaluation adds no evidence of independent implementations, interoperability, adoption, or security review; APH remains a project-authored draft whose practical cross-party trust value is untested.
2026-08-14T15:40:40Z
grounded: known/medium — The radar already tracks this same development in `radar:agent-handoff-protocol-adoption`. APH directly bears on Scott’s Agent Provenance Stack and cryptographi
2026-08-14T15:38:31Z
origin walked (codex/luna, conf 0.96): anchor hn.story.49299146 -> echo.github.5d343a0766 by Scott Wyatt
2026-08-14T15:37:14Z
case created — The open engine and servers constitute a distinct trust-layer release rather than another observation about the existing Agent Handoff Protocol.

Decision trace

08-23 10:22expireRepeated checks have produced only adjacent notarization and trust projects, with no independent APH implementation, interoperability test, adoption, or security review. The APH-specific episode has f
08-23 10:22alert_silentThere is no new consequential delta; unchanged low-signal evidence and continued absence of APH-specific validation do not warrant Scott’s attention.
08-23 10:22alert_routeThere is no new consequential delta; unchanged low-signal evidence and continued absence of APH-specific validation do not warrant Scott’s attention.
08-21 09:35repriceBTP v2.2 adds another independent approach to cryptographic agent trust, broadening the competing design space but providing no APH implementation, interoperability result, adoption, or security revie
08-21 09:35alert_silentThe new evidence concerns a separate low-signal protocol and does not materially validate or challenge APH or Scott’s architecture; it can wait for routine review unless technical interoperability, ad
08-21 09:35alert_routeThe new evidence concerns a separate low-signal protocol and does not materially validate or challenge APH or Scott’s architecture; it can wait for routine review unless technical interoperability, ad
08-21 09:23alert_silentThe evidence establishes only a low-signal repository post for a separate cryptographic trust protocol. It does not show an independent APH implementation, interoperability result, adoption, or concre
08-21 09:23surface_candidateThe evidence establishes only a low-signal repository post for a separate cryptographic trust protocol. It does not show an independent APH implementation, interoperability result, adoption, or concre
08-21 09:23alert_routeThe evidence establishes only a low-signal repository post for a separate cryptographic trust protocol. It does not show an independent APH implementation, interoperability result, adoption, or concre
08-21 09:23attachAn open-source cryptographic trust protocol is relevant competing evidence for practical agent-to-agent verification, though this low-engagement post lacks validation details.
08-21 09:22propose_attachAn open-source cryptographic trust protocol is relevant competing evidence for practical agent-to-agent verification, though this low-engagement post lacks validation details.
08-21 02:42repriceThe signed-receipt camera MCP implementation validates interest in action notarization as a broader pattern, but it neither implements APH nor tests cross-party APH interoperability, so the protocol-s
08-21 02:42alert_silentThe new evidence is adjacent rather than confirming: no APH integration, independent implementation, interoperability result, or security assessment has occurred, so it can wait for routine review.
08-21 02:42alert_routeThe new evidence is adjacent rather than confirming: no APH integration, independent implementation, interoperability result, or security assessment has occurred, so it can wait for routine review.
08-21 02:24alert_silentThe camera MCP server’s signed per-action receipts are conceptually relevant to agent provenance, but the supplied evidence does not show APH support, an independent APH implementation, or interoperab
08-21 02:24alert_routeThe camera MCP server’s signed per-action receipts are conceptually relevant to agent provenance, but the supplied evidence does not show APH support, an independent APH implementation, or interoperab
08-21 02:24attachA concrete MCP implementation using signed receipts for every camera action provides relevant independent evidence for agent-interaction notarization and auditability.
08-21 02:23propose_attachA concrete MCP implementation using signed receipts for every camera action provides relevant independent evidence for agent-interaction notarization and auditability.
08-19 02:58repriceThe staleness check adds no external implementation, interoperability test, adoption, or security review; APH remains a first-party draft whose practical cross-party trust value is untested.
08-19 02:58alert_silentNo consequential delta occurred, and repeated observation has produced only the already-known first-party release; wait for an independent implementation, interoperability result, or security assessme
08-19 02:58alert_routeNo consequential delta occurred, and repeated observation has produced only the already-known first-party release; wait for an independent implementation, interoperability result, or security assessme
08-17 02:31repriceThe slight engagement increase adds no independent implementation, interoperability, adoption, or security evidence; APH remains an untested project-authored draft awaiting substantive external activi
08-17 02:31alert_silentNo consequential event occurred beyond minimal engagement on the existing announcement, so this can wait for evidence of an external implementation, interoperability test, or security review.
08-17 02:31alert_routeNo consequential event occurred beyond minimal engagement on the existing announcement, so this can wait for evidence of an external implementation, interoperability test, or security review.
08-15 01:50repriceThe one-time re-evaluation adds no evidence of independent implementations, interoperability, adoption, or security review; APH remains a project-authored draft whose practical cross-party trust value
08-15 01:50alert_silentNo new consequential delta occurred; the unchanged announcement engagement does not advance the hypothesis beyond the already-known draft and first-party implementations.
08-15 01:50alert_routeNo new consequential delta occurred; the unchanged announcement engagement does not advance the hypothesis beyond the already-known draft and first-party implementations.
08-15 01:45alert_silentAPH’s authors have publicly released a draft specification and project-provided Rust/server implementations, but this does not yet add the independent interoperability, adoption, or security evidence
08-15 01:45surface_candidateAPH’s authors have publicly released a draft specification and project-provided Rust/server implementations, but this does not yet add the independent interoperability, adoption, or security evidence
08-15 01:45alert_routeAPH’s authors have publicly released a draft specification and project-provided Rust/server implementations, but this does not yet add the independent interoperability, adoption, or security evidence
08-15 01:40groundThe radar already tracks this same development in `radar:agent-handoff-protocol-adoption`. APH directly bears on Scott’s Agent Provenance Stack and cryptographic-trust model for authenticated, auditab
08-15 01:38promote_anchororigin walk conf 0.96
08-15 01:37createThe open engine and servers constitute a distinct trust-layer release rather than another observation about the existing Agent Handoff Protocol.