Governance registry and discovery map
The registry is the public catalog of human and machine surfaces published by InferensLab. It exists to make discovery, precedence, and file roles explicit.
Use it to understand what each surface is for, not to downgrade the precedence of the higher-priority governance files.
Registry companion files
Catalog + discovery
The registry is only one part of the discovery layer.
/.well-known/governance-registry.json— Catalog of public surfaces./.well-known/reading-paths.json— Ordered routes through the catalog./.well-known/doctrine-taxonomy.json— Theme, lane, and adjacency structure.
Source map + integrity
The library and doctrine index complement the registry instead of duplicating it.
/.well-known/doctrine-library.json— Governed source map./.well-known/doctrine-index.json— Integrity hashes for public files./.well-known/change-control.json— Change and deprecation policy.
How to use the registry
- Find the right surface: human page, machine file, policy, glossary, or disclosure route.
- Check the role: explanatory page, routing surface, integrity support, or boundary file.
- Respect precedence: the registry helps discovery, but the stop-rules and scope files still outrank it.
- Cross-check integrity: use the registry together with
doctrine-index.jsonand Change control.
Explorer
Search and filter the public catalog below.
Loading…