[signet-ded9d4] docs(apas): define the 0.4 agent activity protocol - #175
Open
jamestexas wants to merge 8 commits into
Open
[signet-ded9d4] docs(apas): define the 0.4 agent activity protocol#175jamestexas wants to merge 8 commits into
jamestexas wants to merge 8 commits into
Conversation
…e vendor's implementation APAS 0.3.1-draft. Every level stated a portable Requirement, then listed bullets — previous_chain_hash, dispatch manifests, bridge certificates, a shared CMS/Ed25519 primitive, ACP request_permission — in the position readers take as conformance criteria. An implementer could not tell which lines they had to satisfy and which merely narrated how we built it. That made APAS unimplementable by anyone who had not built our stack, which is the actual obstacle to it being a standard rather than a design doc. Each level now carries mechanism-neutral core properties (L2.1-L2.5, L3.1-L3.4, L4.1-L4.5), each with a stated falsification, and the original bullets are retained verbatim as a named reference profile. §2.0 gives the reading rule and forbids core properties from naming an algorithm, envelope, protocol, namespace, predicateType, product, or path. Prompted by measuring a second, independently built implementation against L2-L4 (new §7.7). It satisfies L2 while failing most of L2's bullets, and by the property that matters — an externally certified signing identity rather than a key held by the same component that writes the attestations — it is STRONGER than the profile that defined the level. A scheme that scores that non-conformant is measuring the wrong thing. Two properties are new, and both were learned rather than designed: L3.3 generalizes ACP request_permission to "the capability set is bounded, declared, and default-deny". A runtime permission boundary and a declarative capability set are two encodings of one property. The declarative form is preferred: it is default-deny by construction, so there is no prompt to fatigue a human into accepting and no approval path to social-engineer. A runtime boundary that defaults to allow on timeout or missing policy does not satisfy it — the property is default-deny, not "a decision happens". Advisory annotations are explicitly not a boundary. L4.5 requires outcome be distinguishable from completion. Taken from the second implementation, which documents at the type that committing a result is no evidence work succeeded, because executors steer a stuck model into submitting a degraded one. An attestation recording only completion is correctly signed and materially misleading — the worst combination, since it survives verification. Also refreshes the version-disambiguation note, which pinned its example to 0.3.0 and to a superseded rc; APAS 0.3.1 alongside signet v0.3.0 is now the worked example of the two clocks diverging. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NbcVvbUMkJHvSXbz1MMw5n
jamestexas
force-pushed
the
docs/apas-core-profile-split
branch
from
August 11, 2026 19:24
084f88d to
64801c3
Compare
jamestexas
changed the title
jamestexas
marked this pull request as ready for review
August 12, 2026 17:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft for review.
What changed
Verification
Follow-up
Signet schema and code conformance for activity/v1 will be tracked separately after the protocol text is accepted.