ETHRAEON Manifest
The naming engine. Manifest defines how everything in the system is named, versioned and referenced, so that every engine, agent, document and surface points to the same object under the same name across the entire estate and over time.
What it does
Large autonomous estates drift. The same system gets called three names, versions collide, references break, and nothing can be audited because nothing can be found. Manifest removes that failure mode. It gives the estate a single naming standard: a fixed set of object types, one official name format, clear versioning rules, and the governance fields every named object must declare.
The result is identity that holds. A decision, a model, a document or a surface keeps one name and one lineage from the day it is created, so any downstream engine, reviewer or auditor resolves it without guessing.
How it works
A fixed allowlist of object types and prefixes. Every named thing declares what it is before it enters the estate.
A single structured format binds object type, system, engine, version and scope into a name that reads the same everywhere.
Semantic versioning plus the governance fields each object must carry, so change is tracked and nothing is renamed in the dark.
Run it live
Enter a candidate name and the engine checks it in real time: the object-type prefix against the official allowlist, the version against semantic versioning, and the overall field structure. Format: OBJECT_TYPE - SYSTEM - ENGINE - VERSION - SCOPE.
Enter a name and select Validate to run the live engine.
Runs against the live ETHRAEON engine and returns a real result.
16 filed U.S. provisional applications / 75 technical specifications / 9 families.