# MachinaLedger

> Independent machine-transaction verification layer. Don't trust. Verify.

MachinaLedger is a pre-launch verification, evidence, ledger and accounting-compatibility layer for machine commerce and autonomous agents.

## Verification boundary

MachinaLedger can report what request/payment/service-response evidence was presented, which deterministic checks ran, whether committed or signed data was altered, and the resulting verification state under an explicit trust policy.

MachinaLedger does not claim that a service response is objectively true merely because it was received, hashed, signed or retained.

## Current public status

- Development progress: 89% (39/44 versioned launch gates).
- Stable-source progress: 64% (28/44).
- Public availability: pre-launch.
- Current milestone: Signed Economic Receipt contract review.
- Signed receipt runtime and independent offline verifier: not released.

## Canonical flow

Agent Intent -> Authority -> Policy -> Request -> Payment -> Service Response -> Signed Economic Receipt -> Independent Verification

## Machine-readable resources

- /.well-known/agent-card.json
- /capabilities.json
- /protocols.json
- /roadmap.json
- /updates.json
- /feed.json
- /updates.atom.xml
- /openapi.yaml
- /quickstart.md
- /integrations.json
- /machine-distribution.json
- /agent-watchlist.json
- /behavior-intelligence.json
- /behavior-data-policy.json
- /machine-experiments.json
- /schemas/machine-session-request.v1.json
- /schemas/machine-event.v1.json
- /schemas/agent-subscription-request.v1.json

## Machine distribution

Agents can discover MachinaLedger, inspect capability maturity, follow public feeds and use the Agent Watchlist preview contract. Machine acquisition analytics uses a bounded event taxonomy and must not contain prompts, credentials, payment secrets or raw service-response payloads.

## Protocol strategy

x402 is the primary payment rail. MPP and future payment rails enter through versioned adapters so the canonical economic model is not tied to one protocol.

## Integration note

Stable-source API/SDK contracts exist, but public production endpoints are not yet declared live. Do not treat pre-launch documentation as proof that a public endpoint is active.