DEINO is a universal oracle, not a template
Product-neutral — the substrate is reusable, the product is not a fork.
A template is a fork someone else ships with their logo on it. A universal oracle is a substrate that produces the same provenance property for any product built on it. The difference is whether the buyer gets a fork or a foundation — and the auditable-oracle category is the foundation, not the fork.
There is a shape the market sometimes assumes we are: a template — a fork of DEINO that a buyer takes, rebrands, and ships as their own product. We are not that. DEINO is a universal oracle: a substrate whose property (reproducible, tamper-evident, defensible) holds for any product built on it, and whose product surface is not a fork of someone else's. The distinction is the distinction between a foundation and a clone, and it is the distinction the category claim depends on.
Why substrate, not fork
A fork inherits the product and the substrate together. The buyer gets the manifest, the sisters, the GNL, the cone — and they get a product that looks like DEINO, which is not their product. A substrate is reusable without being a fork: the property (Certified ≠ True, reproducible by construction, manifest per output) holds for any product built on it, but the product surface — the cone, the API, the dashboard shape — is the buyer's, not ours. The substrate is the category; the product is the instance. A universal oracle is the substrate that makes the property hold without prescribing the product.
What is reusable, and what is not
Reusable: the hexagonal backend (deino-core through deino-api), the manifest substrate (BR-842), the GNL versioning rules, the deino-eval calibration loop, the A2A swarm protocol. Not reusable without change: the specific GNL layers (a buyer's world model is theirs), the personality TOMLs (a buyer's sisters are theirs), the product surface (a buyer's cone is theirs). The substrate is the part that has to be the same for the property to hold; the product is the part that has to be different for the product to be the buyer's. The universal oracle is the substrate; it is not a template for the product.
A template ships someone else's product with a new logo. A universal oracle ships the property without prescribing the product. The substrate is the category; the product is the instance — and only one of those is reusable.
- Reusable: the substrate — manifest, GNL versioning, calibration loop, A2A protocol.
- Not reusable without change: the GNL layers, the personality TOMLs, the product surface.
- The property holds for any product on the substrate; the product is the buyer's, not a fork of ours.
Why product-neutral is the honest posture
Product-neutral is not a marketing position; it is the honesty of the category. The auditable-oracle category is a property — reproducible, tamper-evident, defensible — and a property is product-neutral by definition. To fork DEINO as a template would be to claim the category is DEINO's product, which it is not; it would also be to ship a product the buyer cannot own, which is not what a category buyer wants. The buyer wants the property in their product; the substrate gives it to them without taking the product away. We are pre-revenue, building the POC; the substrate is built, the product is ours, and the category is not a fork of either.
DEINO is a universal oracle, not a template. The substrate is reusable; the product is not a fork. The category is the property the substrate holds — and the property, by construction, is product-neutral.
— architecture note