← Back to catalogue
Published

Enterprise Fact Authority

vr.profile.enterprise-fact-authority · enterprise-fact-authority

EM-XCT-02: explicit fact accountability, stewardship, source precedence, write grants and retained conflicts in a Company Dimension. Bounded original companion contract.

Enterprise profiles Cross-cutting context EnterpriseData governance

Bundle → Layer → Finding → Questions Filled

4 bundles · 6 layers · 18 findings · 18 questions

Governance Scope, accountability and operational appointments.

Scope and accountable term

FactAuthority; definition/value separation.

Object boundary

Information needed to answer this governance question for a Company Dimension.

  1. Is this a meaning, value assertion or ownership record? context-question

Stable identity

Information needed to answer this governance question for a Company Dimension.

  1. What survives rename/transfer? context-question

Definition authority

Information needed to answer this governance question for a Company Dimension.

  1. Who defines this predicate? context-question

Accountability for values

Information needed to answer this governance question for a Company Dimension.

  1. Who answers for values at T? context-question

Overlapping authorities

Information needed to answer this governance question for a Company Dimension.

  1. Which of two authorities applies? context-question

Accountability transfer

Information needed to answer this governance question for a Company Dimension.

  1. What happens at responsible-party change? context-question

Operational appointments

StewardshipAssignment; bounded duties and valid terms.

Stewardship and escalation

Information needed to answer this governance question for a Company Dimension.

  1. Who handles the disagreement? context-question
Source policy Source preference and submission permission are governed separately.

Selection

MastershipRule; explicit source priority and overlap conflict.

Source precedence

Information needed to answer this governance question for a Company Dimension.

  1. Which source is preferred at fact time? context-question

Submission

WriteGrant; current rights for an authenticated source writer.

Current submission rights

Information needed to answer this governance question for a Company Dimension.

  1. May this actor submit for source S now? context-question
Observation Source-scoped assertions, correction history and retained evidence.

Assertions and corrections

FactObservation; immutable anchors and attributed revisions.

Correction history

Information needed to answer this governance question for a Company Dimension.

  1. How is a wrong claim corrected? context-question

Evidence and veracity

Information needed to answer this governance question for a Company Dimension.

  1. Does provenance prove the value? context-question
Reliance Historical evaluation, disclosure, adoption and integration.

Historical query and projection

Derived Evaluation and AuthorityRegister; explicit input slices and permissions.

Conflicting observations

Information needed to answer this governance question for a Company Dimension.

  1. What if equal sources disagree? context-question

Historical knowledge

Information needed to answer this governance question for a Company Dimension.

  1. What was known at T about valid time V? context-question

Reader disclosure

Information needed to answer this governance question for a Company Dimension.

  1. What can this reader see? context-question

Minimum startup profile

Information needed to answer this governance question for a Company Dimension.

  1. Does a startup need HRIS? context-question

Missing context

Information needed to answer this governance question for a Company Dimension.

  1. What if source/policy is missing? context-question

Native binding and validation

Information needed to answer this governance question for a Company Dimension.

  1. Does native validation prove semantics? context-question

Legacy migration

Information needed to answer this governance question for a Company Dimension.

  1. Can earlier owner strings be imported? context-question

Classifiers Filled

Family
Enterprise profiles
Category
Cross-cutting context
Entry kind
companion-contract
Navigation path
NAV.XCT
Domain
EnterpriseData governance
Industry
Cross-industry
Tags
EM-XCT-02authoritystewardshipmastershipsource-prioritywrite-grants
Also called
EM-XCT-02, Enterprise data accountability, Fact Authority, Stewardship and source precedence

What it is Filled

A companion profile for a Company Dimension that states, per fact scope, who is accountable, who stewards it, which source takes precedence, who may write, and which conflicts between sources remain open.

Why it exists Filled

EM-XCT-02: explicit fact accountability, stewardship, source precedence, write grants and retained conflicts in a Company Dimension. Bounded original companion contract.

Distinguishing features Filled

  • Says who is accountable for each kind of fact and which source wins when sources disagree.
  • Keeps conflicts between sources as records instead of resolving them silently.
  • Grants write access per fact scope, separate from read access.

What robots and AI may and may not do Filled

Must not

  • Overwrite a fact from a source that does not hold the write grant.
  • Resolve a conflict by picking the newest value without a precedence rule.
  • Infer ownership from who last edited a value.

Only with a human decision

  • Changing source precedence for a fact scope.
  • Granting or revoking write authority.

May

  • Look up the accountable owner and precedence for a fact.
  • Record a conflict between two sources with both values.

Moral aspects Filled

  • Clear accountability lets people correct wrong facts about them.
  • Hidden precedence rules can let one system silently override another team's truth.

Who is affected

  • Employees and contractors whose actions or data appear in company records
  • Customers, suppliers and partners named in company records
  • Auditors, regulators and courts that rely on the record later

Owners Filled

Steward

The data governance council assigns fact accountability; each fact scope names its own accountable owner.

Master systems

  • Data governance catalogue
  • Systems of record per fact scope

Links to other meta-models Filled

references

  • WM-XCT-001 - 0.3.0-research.1
  • WM-XCT-002 - 0.3.0-research.1
  • WM-XCT-012 - 0.3.0-research.1

aligned

  • vr.wm-xct-001

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Fact scope ID.
  • Grant ID per writer and scope.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: it has no physical body to measure.

Recognition optional Filled

  • A fact authority entry names a fact scope, an accountable owner, steward, source precedence and write grants.

Capabilities and actions required Filled

  • Look up accountability, evaluate precedence, record and retain conflicts, issue and revoke write grants.

Hazards and failure modes required Filled

  • Two systems both believing they are master.
  • Orphaned facts with no accountable owner.

Standards and interfaces required Filled

  • DAMA-DMBOK data governance roles.
  • RACI accountability matrices.

Context of use required Filled

  • Any Company Dimension that merges facts from more than one system.

Sources Filled

  1. Research record EM-XCT-02: independent provider studies, audits and reconciled findings - Evidence behind the release; claims in the card trace to it.
  2. Enterprise Fact Authority 0.1.0 specification - Normative release, digest sha256:cf027b56d01f23e39c15ad49a728967e45e7fb8d2b34137b6bb532536f35f582

Open questions

  • Use the pinned companion schema/validator and trusted-host binding. Native outer validation alone does not enforce nested semantics. Consult the released adoption limits.

Machine files

Provenance

enterprise research · reviewable-draft

Built from: models/wm-xct-001-ownership-stewardship/profiles/enterprise-fact-authority/0.1.0/spec.json, models/enterprise-fact-authority/catalogue-entry.json, ver-cy/world-models/card-supplements/enterprise-fact-authority.json