Enterprise Fact Authority · 0.1.0
Accountable parties, named stewardship appointments, source precedence and separate write grants for a Company Dimension. Published; reviewable-draft. A bounded EM-XCT-02 increment.
Download the complete contract · Adoption instructions · Semantic specification · Research and Claude/Grok reviews
Keep conflicting facts visible
Two equally preferred sources with different values produce a contested result, retain both evidence references and provide an informational steward route. A later spreadsheet never wins merely because it arrived last. Missing or overlapping authority does not create a grant.
Use distinct responsibilities
- Accountability for values is separate from the referenced definition owner.
- Stewardship duties do not grant write access.
- Source priority and current submission rights are separate records.
- Immutable corrections, explicit transfer terms and historical query cuts retain provenance.
Validated scope
53 reference tests and three synthetic new-Dimension scenarios passed. Native V3 checks the envelope; companion validation is mandatory. This is an original companion contract associated with Ownership / Stewardship, not a ControlRecord subtype. No authentication, durable concurrency, real connector, definition governance, federation, legal validity or full parent conformance is claimed.
Boundary and remaining work · Closed schema · Reference implementation · Tests · Native acceptance · Manifest · Checksums
Own machine specification · Detailed adoption limits. The runtime identifier is vr.profile.enterprise-fact-authority; the parent is a semantic reference.