02Project / Infrastructure Engineering Program
NetFRAME
identity.
A program to make infrastructure identity explicit. Its core object is a tuple: (realm, kind, name). Its target is every quiet corruption that happens when tooling assumes a plain name identifies exactly one thing.
Names collide.
Scopes don't.
Distributed infrastructure breaks the assumption of globally unique plain names constantly. Hostnames recur across sites and environments. A node, its management controller, and its backup client share a natural name while being three different endpoints. Hardware is replaced under an old name and inherits a history that is not its own.
Each collision quietly corrupts something downstream: metrics continuity, alert routing, inventory, incident timelines. Nothing crashes. The records just stop being trustworthy, which is worse.
Core modelScoped identity
(realm, kind, name)
- RealmWhich naming authority the claim lives in: a site, an environment, a cluster, a tenant. Scopes what unique has to mean.
- KindWhat category of thing is named: host, service, device, virtual machine. Separates endpoints that share a natural name.
- NameThe claim itself, now only required to be unique within its scope, which real systems can actually promise.
01
Provenance
Multiple collectors observe the same estate from different angles, and without scoping, their observations collide or fragment. Under the tuple model, every observation states which authority it was made under and what category of thing it describes, giving each fact operational provenance: who saw this, in what scope, about what.
Collisions become structural rather than accidental, and resolvable by evidence rather than by overwrite.
02
Migration & compatibility
The hard engineering is the installed base: years of records keyed by plain name, and consumers that cannot change overnight. The program treats a plain name as a degenerate tuple in a default realm, keeping historical data addressable while new data is written fully qualified. Compatibility views remain for consumers that need old keys, with their lossiness made explicit.
Renames, rebuilds, and hardware replacement become recorded identity events instead of silent label churn, which is what makes long-lived infrastructure records auditable at all.
03
Governance
Scoped identity underpins infrastructure governance: inventory that reconciles, telemetry that stays continuous across rebuilds, and evidence that can be attributed years later. It is foundational work for the Jarvis program, whose operational knowledge is only as trustworthy as the identities its facts hang from.
Related