Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -742,6 +742,7 @@ docker-compose up
- AgentSkill delegated authority fixtures guide: [`docs/guides/agentskill-authz-interop-fixtures.md`](docs/guides/agentskill-authz-interop-fixtures.md)
- action_ref identity/explainability profile: [`docs/specs/action-ref-identity-explainability-profile.md`](docs/specs/action-ref-identity-explainability-profile.md)
- Payment governance profile (Economic Layer v1): [`docs/specs/payment-governance-profile-v1.md`](docs/specs/payment-governance-profile-v1.md)
- Agent commerce governance profile: [`docs/specs/agent-commerce-governance-profile-v1.md`](docs/specs/agent-commerce-governance-profile-v1.md)
- OpenAI Agents SDK governance guide: [`docs/guides/openai-agents-sdk-integration.md`](docs/guides/openai-agents-sdk-integration.md)
- Cursor integration guide: [`docs/guides/cursor-integration.md`](docs/guides/cursor-integration.md)
- Benchmark report: [`docs/reports/industrial-benchmark-report.md`](docs/reports/industrial-benchmark-report.md)
Expand Down
10 changes: 10 additions & 0 deletions docs/.vitepress/config.mts
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,16 @@ export default defineConfig({
{ text: "Collaboration Reply Playbook", link: "/community/open-source-collaboration-replies" },
],
},
{
text: "Specs",
items: [
{ text: "Agent Commerce Governance Profile", link: "/specs/agent-commerce-governance-profile-v1" },
{ text: "Payment Governance Profile", link: "/specs/payment-governance-profile-v1" },
{ text: "Action Ref Explainability Profile", link: "/specs/action-ref-identity-explainability-profile" },
{ text: "APS-SINT Handshake", link: "/specs/aps-sint-handshake-v1" },
{ text: "SINT Industrial Action Profile", link: "/specs/sint-industrial-action-profile" },
],
},
{
text: "Roadmaps",
items: [
Expand Down
1 change: 1 addition & 0 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,7 @@ limits, and tamper-evident audit evidence before execution.
- ISO 13482 alignment: [Compliance/ISO 13482](./compliance/iso-13482-alignment.md)
- Formal threat model: [Security/Formal Threat Model](./security/formal-threat-model.md)
- MITRE ATLAS candidate mappings: [Security/MITRE ATLAS](./security/mitre-atlas-agent-technique-mappings.md)
- Agent commerce governance profile: [Spec](./specs/agent-commerce-governance-profile-v1.md)
- NIST submission bundle report: [Report](./reports/nist-submission-bundle.md)
- Latest security bulletin: [May 2026](./security-bulletins/2026-05.md)

Expand Down
8 changes: 8 additions & 0 deletions docs/marketing-message-map.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,12 @@ Every decision is captured in a tamper-evident, hash-chained ledger for audit an

SINT works across execution surfaces such as MCP, A2A, ROS 2, MAVLink, MQTT/Sparkplug, OPC UA, Open-RMF, and gRPC.

### 6. Agent commerce

SINT can govern task-market and machine-payment workflows before work or money
moves: task creation, bids, claims, benchmark proof submission, worker
selection, settlement release, and x402-style payment permits.

## Proof points to emphasize

- Apache-2.0 licensed
Expand All @@ -90,6 +96,8 @@ SINT works across execution surfaces such as MCP, A2A, ROS 2, MAVLink, MQTT/Spar
- "approval tiers"
- "physical AI governance"
- "industrial AI safety"
- "agent commerce governance"
- "x402 policy enforcement"
- "tamper-evident evidence ledger"
- "open protocol and reference stack"
- "real-world consequences"
Expand Down
110 changes: 110 additions & 0 deletions docs/specs/agent-commerce-governance-profile-v1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,110 @@
# Agent Commerce Governance Profile v1

Status: executable conformance profile

This profile defines a transport-neutral governance contract for agent-to-agent
task markets, x402-style machine payments, and machine-router workflows. It is
inspired by current task-market patterns such as bounty, claim, pitch,
benchmark, and auction modes, but it is not vendor-specific.

## Scope

Agent commerce systems need two separate controls:

1. **Market state control**: an agent should only create, bid, claim, submit,
accept, rate, or settle a task when the task state and agent authority allow
that transition.
2. **Payment control**: an agent should only sign or submit x402-style payment
permits when spend caps, expiry, recipient, session, and policy limits are
valid.

SINT provides the pre-action policy boundary for both. Marketplaces remain free
to implement escrow, identity registries, reputation, and settlement rails; SINT
defines the observable policy outcomes that must happen before execution.

## Governed Actions

The profile uses these resource and action names:

| Resource | Action | Typical tier |
|---|---|---|
| `market://task/*` | `create` | T1 or T2 when reward is high |
| `market://task/*` | `pitch` | T1 |
| `market://task/*` | `bid` | T1 or T2 when paid |
| `market://task/*` | `claim` | T2 when exclusive or staked |
| `market://task/*` | `submit` | T1 |
| `market://task/*` | `submit_proof` | T1 |
| `market://task/*` | `select_worker` | T2 |
| `market://task/*` | `accept` | T3 when payment releases |
| `market://settlement/*` | `release` | T3 |
| `x402://session/*` | `authorize_permit` | T2 or T3 when cap is high |

## Required Controls

1. Agent identity must be registered before reputation-bearing work.
2. Capability scope must include the requested market action.
3. Task-mode state transitions must be monotonic and valid.
4. Exclusive claim tasks must deny non-selected workers.
5. Auction bids must satisfy the active price-discovery rule.
6. Benchmark submissions must include a proof digest and metric value.
7. x402 permits must enforce cap, expiry, recipient, and session constraints.
8. Settlement must only release after accepted work and must reject receipt
replay.
9. High-value task creation or settlement must escalate to human approval.
10. Every deny, escalate, accept, and release decision must carry an evidence
reference.

## Decision Reasons

The executable fixtures use the following stable outcome reasons:

- `ALLOW`
- `AGENT_IDENTITY_REQUIRED`
- `SCOPE_NOT_AUTHORIZED`
- `REPUTATION_BELOW_THRESHOLD`
- `VALUE_REQUIRES_APPROVAL`
- `STATE_TRANSITION_INVALID`
- `BID_NOT_COMPETITIVE`
- `PROOF_REQUIRED`
- `X402_CAP_EXCEEDED`
- `X402_PERMIT_EXPIRED`
- `RECIPIENT_NOT_ALLOWLISTED`
- `SETTLEMENT_STATE_INVALID`
- `RECEIPT_REPLAY`

## Fixture Contract

Fixture file:

- `packages/conformance-tests/fixtures/economy/agent-commerce-governance.v1.json`

Executable test:

- `packages/conformance-tests/src/agent-commerce-governance-conformance.test.ts`

Run:

```bash
pnpm --filter @pshkv/conformance-tests exec vitest run src/agent-commerce-governance-conformance.test.ts
```

## Reference Systems

The profile is designed to map cleanly onto emerging agent-commerce systems:

- Task modes such as bounty, claim, pitch, benchmark, and auction:
`https://docs-market.daydreams.systems/concepts/task-modes`
- x402 permit/session routing with spend caps and expiry:
`https://router.daydreams.systems/how-it-works`
- scoped device signing and revocation:
`https://docs-market.daydreams.systems/identity/device-setup`
- ERC-8004 style agent identity and reputation linkage:
`https://docs-market.daydreams.systems/identity/agent-registration`

## Non-Goals

- This profile does not implement escrow, auctions, or x402 settlement.
- This profile does not claim compatibility with any specific marketplace API.
- This profile does not define a new payment rail.

It defines the policy contract SINT can enforce before those systems execute.
Loading