AIP-18: Agent Intent Model — Provider, Buyer, and Dual agents#3
Open
DamirAGI wants to merge 1 commit into
Open
AIP-18: Agent Intent Model — Provider, Buyer, and Dual agents#3DamirAGI wants to merge 1 commit into
DamirAGI wants to merge 1 commit into
Conversation
Cements the earn / pay / both model surfaced by a live onboarding incident (buyer 413; meaningless covenant/service-terms for a pure buyer). - Two orthogonal field groups (provider-side, buyer-side) gated by intent; `both` is the union, not a third schema (DEC-1). - Buyer budget is private — never on-chain/IPFS/hashed (DEC-2, §8 invariant). - Provider publishes (AgentRegistry + configHash + listing); buyer links (DB + optional ERC-8004); dual does both (DEC-3/4). - Identity layering per ADR-001: address = spine; ERC-8004 = portable WHO / reputation anchor (= agentId, default-on, opt-out, agentId=0 valid); AgentRegistry = address-keyed provider profile (DEC-5). - Reputation honestly scoped: provider side live (kernel updateReputationOnSettlement); buyer/counterparty side NOT built — a known gap needing a protocol change (DEC-6). - §7 resolved: servicesNeeded opt-in semi-public; buyer profile minimal opt-in; one `actp publish` branching by intent. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 5, 2026
Merged
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
1 participant
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.
Cements the
earn/pay/bothagent model, surfaced by a live onboarding incident (2026-06-05): a pure buyer hit a publish 413 and was handed meaningless service terms + covenant.Core
intent;both= the union, not a third schema (DEC-1).agentId, default-on, opt-out,agentId=0valid); AgentRegistry = address-keyed provider profile. (Not competing identities.)updateReputationOnSettlement); buyer/counterparty reputation is NOT built — a known gap requiring a protocol change (flagged, not hand-waved).servicesNeededopt-in semi-public; buyer profile minimal opt-in; oneactp publishbranching by intent.Grounding
Verified against live code + ADR-001, not theory: the 413 path, the kernel reputation call (provider-only),
resolveIdentityPath, andagentId-is-ERC-8004. Passes the §8 single-page test (adds invariants, no new contracts).Status
Draft — for review. Companion implementation already underway: buyer-publish 413 fix (sdk #19, shipped 4.4.2), onboarding de-coercion (agirails.app #43, merged). Next: buyer config shape (wizard stops emitting provider fields for
pay) + the fuller buyer "link" path.🤖 Generated with Claude Code