Concept
The Capability Schema is published — ahead of the product, on purpose.
Version 0.1 of the Capability Schema is now public — and it is a schema you can write in, not a vocabulary we describe: a validatable JSON Schema with seven capability classes, five required fields per declaration (its class, the kind of resource, reach, lead time and the consent chain), a six-state status vocabulary mirroring the onboarding gates — every published example honestly stops at the first — namespaced domain extensions, and one deliberate exclusion: cost, which belongs to a booking, not a capability. It lives at tilfang.com/schema, as a full reference and as JSON, with this site’s entire resource catalogue embedded as conformant examples.
Publishing the vocabulary before the platform is the cheapest honest test this concept can run: if an operator can describe a real asset in it, the abstraction holds; if they argue with it, the argument is the finding. Both outcomes beat a private draft. If you run sensors, drones, labs or analysts — read it and tell us where it breaks.