Documentation
The model, before the menus.
Most of what is confusing about an ownership platform is conceptual rather than procedural. These are the six ideas everything else is built from.
Objects
Entities, brands, assets, agreements, people, repositories and packages. Every object has a stable identity the rest of the graph points at, so renaming a brand does not orphan its history.
Typed relationships
Owns, operates, licenses, depends on, was created by, belongs to. Direction and type carry meaning: the difference between owns and operates is what lets the graph answer a transfer question.
Assertions and verification
A claim with a source, a status and a reviewer. The resolved current state is what verified assertions produce, and superseded assertions stay queryable with their evidence.
Effective dating
Relationships record when they became true, not when they were entered. Point-in-time questions are answered from the same records as present-day ones.
Permissions and labels
Object-level permissions and confidentiality labels apply to traversal, search, export and AI retrieval — not only to pages. A node you cannot see does not leak through a path or a count.
Audit events
Material changes are appended with actor, capacity and before/after state, including changes made by an integration rather than a person.
By module
Each module, and what it is responsible for.
The platform pages carry the detail. This is the one-line version of who owns which part of the model.
- Asset GraphA live relationship graph across entities, brands, assets, agreements, people, repositories and rights.
- Brand & Asset RegistryOne structured register for entities, brands, intangible assets, domains, digital accounts and economic asset packages.
- Software ProvenanceConnect repositories, contributors, agreements, components, releases and SBOM data to legal ownership.
- Agreements, Rights & LicencesNormalize the rights, restrictions and obligations created by contracts so the graph can reason over them.
- Evidence & Chain of TitleEvidence-backed ownership assertions, document versioning and end-to-end chain-of-title paths.
- Readiness & ControlsContinuously surface missing ownership evidence, contributor gaps, custody mismatches, expirations and unresolved restrictions.
- Transfer IntelligenceModel sales, spin-outs and reorganizations before changing the live ownership graph.
- Intelligence & IntegrationsUse AI to interpret verified data, and integrations to keep the ownership graph connected to source systems.
Step-by-step setup and administration documentation ships with the product console. This page covers the concepts a reader needs before any of those procedures make sense.
Build the ownership record before somebody asks for it.
Register what exists, connect the relationships, attach the evidence. The answer you need under deadline is the one you maintained beforehand.
Evidence-backed relationships Multi-entity by design Built for transfer and diligence