Connect producer capability
Status: Foundation
Gnaww needs controlled producer capability before SpecMatch can compare that capability with controlled demand.
producer, supplier or catalogue source
-> Gnaww source interpretation
-> terminology and capability normalisation
-> validation and review
-> canonical ProducerCapabilityProfile
-> publication
-> safe public capability read
-> SpecMatch
The producer source does not become matching truth merely because it is structured data. Gnaww governs the meaning, evidence and normalisation before SpecMatch uses it.
What Gnaww owns on the capability side
Gnaww capability intelligence includes:
- source interpretation and extraction;
- supplier-specific terminology mapping;
- product-family mapping;
- material, process and constraint normalisation;
- evidence and provenance handling;
- ProducerCapabilityProfile validation;
- controlled publication semantics.
SpecMatch begins after that controlled capability exists. It does not parse raw supplier payloads or rename capability fields to make a buyer request fit.
Safe public capability reads
The reviewed developer contract exposes a safe read for a capability target you already know:
curl "https://api.gnaww.io/v1/producer-capabilities/${PROFILE_ID}" \
--header "X-Gnaww-API-Key: ${GNAWW_API_KEY}" \
--dump-header capability-headers.txt \
--output capability.json
The public projection keeps capability truth explicit while excluding private lifecycle resources, tenancy wrappers, raw imports and internal notes.
Use the returned capability as Gnaww-controlled evidence. Do not copy private producer administration concepts into your integration.
Capability onboarding is not a public lifecycle API yet
Gnaww has internal capability-profile lifecycle foundations, but create, validate, publish, retire and source-administration operations are deliberately outside the general reviewed developer contract today.
If you are building a producer or catalogue connection, design around this product boundary:
your source connector
-> controlled Gnaww capability intake
-> Gnaww normalisation and review
-> published safe capability
-> public read and SpecMatch consumption
Do not call undocumented private lifecycle routes from a general integration.
Live source proofs and continuous synchronisation are different states
Gnaww has Live external read-only catalogue proofs for selected provider sources recorded in the current feature register. Those proofs show that real external catalogue information can be read and mapped into controlled capability.
Automated continuous catalogue synchronisation, change handling and production operationalisation remain Planned. A live catalogue read also does not prove current price, physical-site availability, producer acceptance or an order.
Use capability in the demand journey
Once a safe public capability is available, you can:
The generated API reference remains the field-level authority for the safe public capability read.