Web 4

pay-policy/1 · commerce

agentpay — pay-policy/1, the commerce layer of Web 4

pay-policy/1 is a vendor-neutral payment-policy format and a pure allow / deny / escalate evaluator for agents that spend — it sits over any rail and answers one question: given a policy and a proposed payment, may it go, must it stop, or must a person decide.

This repository is the human front door to that stack — for anyone who needs the whole thing legible in ninety seconds. It holds no protocol code: the map, the principles, and the rule for how a protocol joins. The machine-readable twin is stack.json, served at /.well-known/stack.json; this page renders the human table and never duplicates that file's data.

The stack

Nine layers, each answering one question, composed so a single query travels the whole stack. The standalone reference is the stack page; the table below is rendered from the stack.json copy this repository serves — the figures are never typed into this page.

#LayerQuestionReposContract
1IdentityWho are you?flashyid-spec, flashyiddelegation/1
2GraphWhat exists?agentgraph, therealmgraph/1, realm/1
3DiscoveryWho can accomplish this intent?intent-spec, intentmeshintent/1
4TrustShould I deal with you?magician, Rites-Network, trustgraph plannedtrust/1, ritual/1
5GatewayHow do I connect to the old web?agent-wellknown, agent-dns, bastionagent/1, agent-dns/1
6RepresentationHow is the org shown to machines?aaoaao/0.1
7ExecutionHow does it operate?flashyos, flashyos-spec, flashyos-tools, agentfile—
8CommerceHow does value move?agentpay, flashyos-wdk, flashy-rails, flashy-ledger, flashy-contractspay-policy/1
9AuditWhat happened?agentledger planned, chronicle, flashy-networkaction-ledger/1, chronicle/1

Principle: Own the open protocols through which agents discover, identify, authorize, trust, transact with and audit one another — not the agents.

Where to go next