Build with Gnaww
Use these guides when you are building a real integration rather than looking up an individual API operation.
They follow one controlled print requirement from source intent through canonical demand and capability evaluation, then show the boundary into planned production orchestration.
The journey in two minutes
buyer or system intent
-> Gnaww interpretation
-> clarification when required
-> canonical Gnaww Job Specification
-> durable Specification when a stable workflow reference is needed
-> SpecMatch across authorised producer capability
-> one or more capability-fit routes
-> planned transaction plane for live checks, approval, acceptance and production
Gnaww creates and governs the meaning on the demand and capability sides. SpecMatch™ evaluates the relationship between those controlled meanings. Live commercial and transaction state remains separate.
Choose a guide
| Journey | Current status | What you will do |
|---|---|---|
| Understand a print requirement | Implemented | Turn ordinary or system-originated intent into controlled GJS v0.4 demand. |
| Get and display a Specification | Implemented | Retain completed canonical demand and retrieve it later by specification_id. |
| Find capable production | Foundation | Evaluate canonical demand across the authorised producer capability universe. |
| Validate one capability | Foundation | Run SpecMatch against one explicit producer capability target. |
| Send an approved job towards production | Planned | Understand the contract boundary from capability fit into live production orchestration. |
| Track production | Planned | Understand the planned producer acceptance, production and dispatch lifecycle. |
| Connect producer capability | Foundation | Understand capability intake, normalisation, publication and safe public reads. |
The status words above use the canonical Gnaww feature-register vocabulary. A Foundation operation is working contract or service capability whose wider production workflow or integration remains incomplete. A Planned journey is architecture, not an available developer operation.
One boundary to keep visible
canonical specification != provider-specific order payload
capability match != current price
capability match != current availability
capability match != producer acceptance
capability match != an order
A ranked producer-universe result tells you about capability fit. It does not choose a commercial producer for you and it does not prove that a producer can accept this particular job now.
The API reference remains the schema authority
These guides show how operations fit together. They do not maintain a second copy of request and response schemas.
Use the generated API reference and the pinned gnaww-developer-v0.1 contract for field-level authority. Copy returned canonical objects between operations rather than rebuilding Gnaww meaning inside your application.
Example story used in the guides
The supported examples use the same controlled fictional requirement throughout:
500 A5 double-sided flyers on 170gsm silk, full colour
The caller-owned reconciliation reference is campaign-4821. Producer capability returned by Gnaww is treated according to its explicit source and truth_state rather than being described as live availability.