# AstraNL Coordination Grammar — CORE_SCOPE v0.1 (2026-08-27)

Status: specification freeze candidate (blueprint days 0–14). Evidence, not calendar, is the gate.

## One sentence
AstraNL is a machine-readable protocol that turns an AUTHORIZED intent into a coordinated, measurable and provable change of real economic state — through the systems the world already runs. The world does not migrate to the protocol; the protocol adapts to the world.

## The narrow waist (what the core IS)
Fourteen primitives, nothing else:
INTENT · PARTICIPANT · PRINCIPAL · MANDATE_REFERENCE · CAPABILITY_REQUIREMENT · OFFER · COMMITMENT · EXECUTION · EVIDENCE_REQUIREMENT · ACCEPTANCE · SETTLEMENT_CONDITION · RECOVERY_POLICY · STATE_TRANSITION · PROVENANCE_REFERENCE

Machine form: `coordination-contract.schema.json` (CoordinationContract v0.1), `state-machine.json`, `evidence-levels.json`, `failure-taxonomy.json`, `prov-mapping.json`.

## Hard rules (normative, each has a conformance scenario)
MESSAGE != COMMITMENT · QUOTE != ACCEPTANCE · AGENT IDENTITY != AUTHORITY · PAYMENT AUTHORIZATION != PAYOUT · HASH != REALITY · COMPLETED != PROVEN · NO MANDATE -> NON-BINDING ONLY · NO_EXECUTABLE_PATH is honest success.

## What the core is NOT (out of scope, by design)
- not an agent chat/collaboration transport (A2A 1.0 does that)
- not a tools transport (MCP 2026-07-28 does that)
- not an identity system (W3C VC 2.0 / EUDI are referenced, never owned)
- not a payment rail or bank (PSP/SEPA rails are adapters; custody never)
- not a B2B document standard (UBL 2.3 / Peppol BIS are used as-is)
- not a physical-event vocabulary (GS1 EPCIS 2.0 is used as-is)
- not a robot motion/safety protocol (VDA 5050 3.0 / native stacks own motion)
- not a marketplace, not "another AI", not an ERP

## Profiles (reference standards, keep the core narrow)
CORE · HUMAN_EXECUTION · B2B · COMMERCE · SUPPLY_CHAIN · ROBOTICS · PUBLIC_SECTOR · HIGH_ASSURANCE

## Versioning and deprecation
- protocol_version is a string; 0.x may break with a changelog; from 1.0 additive only in minor versions.
- Every normative behavior has a scenario in `conformance-scenarios.json`; a change without a scenario is not a change.
- Deprecation: Active -> Deprecated (>= 12 months, mirrors the MCP feature lifecycle) -> Removed.
- Conformance words: PASS / PARTIAL / FAIL / NOT TESTED. "Compatible" is not a word.

## Protocol evolution rule
A new core primitive only if: repeated across corridors, cannot be a profile/extension, independent implementations need it, improves interoperability, complexity justified. Otherwise: profile or adapter. No primitive for one customer.

## Universal addressability (anti-cold-start)
AI agent -> A2A/MCP · old supplier -> Peppol/UBL · small business -> email/web/API/payment link · product -> GS1/EPCIS · robot -> VDA5050/fleet adapter · person -> human interface. One native caller must be able to succeed against a counterparty that never installed anything.

## Metrics that count
Verified Completed Coordinations · Coordination Gain Ratio (with published methodology, no imaginary baseline) · Completion Rate · Time to Executable Path · Time to Verified Outcome · Evidence Acceptance Rate · Dispute Rate · Recovery Success Rate · Internal Operator Intervention Rate · Repeat Coordination Rate · Interoperability Rate · False Match Rate · Settlement Finality Rate · Cost per Verified Coordination · Learning Improvement Rate.
Not: pageviews, endpoint count, synthetic tasks, catalogue size.

## Maturity threshold of a living protocol
core grammar stable · core small · four archetypes (AI↔AI, AI↔Human, AI↔Existing Business, AI↔Machine) proven through ONE grammar · evidence works · authority works · legal profiles gate action · external payment rails used · conformance automated · second independent implementation exists · scanners run · learning promotion works · automatic downgrade works · routine coordination needs no internal human operator · new development starts from real coordination evidence.

## Reference implementation
`core/coordination_grammar.py` (validate, transition with guards, reality router, failure classifier, learning records, adapters) · runner `tests/coordination_grammar_conformance.py` · public machine surface `/spec/*` and `/api/coordination/grammar`.