Fact ownership and responsibility
Make responsibility and change authority explicit for each fact type so that updates, disputes and mastership transfers follow accountable rules.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 3 findings · 8 questions
Authority Who owns the meaning of a fact type and who may change its values.
Fact authority
Semantic owner, steward and master system per fact type.
Fact type owner
The owner of a fact type, kept apart from the owner of the model.
- Who is the semantic owner of this fact type, and who is its steward?
- Which system is the master for this fact type, and since when?
- Who may change a specific fact, and under which rule?
Conflict and transfer How conflicting sources are resolved and responsibility moves.
Conflict resolution
Conflicts between sources resolved by rule, not by import order.
Contested fact
A fact with conflicting values from sources of equal authority.
- Do two sources of equal authority disagree on this fact?
- Which resolution route applies, and who decides?
Rule over time
Mastership rules with validity periods and their transfer.
Mastership rule
A rule that applies for a period and is transferred with provenance.
- Which mastership rule applied at the time the fact was recorded?
- When responsibility moved, was the provenance of earlier values kept?
- Which facts were written by a source that was not master at the time?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise contract
- Entry kind
- contract
- Domain
- EnterpriseXCT
- Industry
- Cross-industry
- Tags
- EM-XCT-02W0contractFactAuthorityStewardshipMastershipRule
What it is Filled
A contract for semantic owner, steward, master system and change rights at the fact-type level.
Why it exists Filled
Make responsibility and change authority explicit for each fact type so that updates, disputes and mastership transfers follow accountable rules.
Distinguishing features Filled
- Authority is assigned per fact type, allowing different facts in one record to have different master systems.
- Maintaining a model does not grant authority over the enterprise facts described by that model.
- Permission to submit evidence does not grant authority to change a master value.
- Explicit authority rules and resolution routes govern conflicts instead of import order.
- Mastership rules have validity periods that preserve historical authority when responsibilities change.
What robots and AI may and may not do Filled
Must not
- Treat the last uploaded file as more truthful than the system of record.
- Overwrite a fact silently when sources of equal authority disagree.
- Assume the model owner may change any instance fact.
- Treat permission to submit evidence as authority to change a master value.
- Apply a current mastership rule retroactively to past values.
- Drop provenance when responsibility for a fact type is transferred.
Only with a human decision
- An authorized enterprise data owner must approve assigning or changing the master system for a fact type.
- A designated human decision maker must decide contested facts between sources of equal authority.
- An authorized enterprise data owner must approve transferring stewardship to another role or unit.
May
- Report the master system and steward for each fact type.
- Mark a fact as contested when equally authoritative sources disagree and open the applicable resolution route.
- Check whether a change to a master value was authorized under the rule valid at that time.
- Record evidence submitted by a permitted source without treating the submission as an authorized change to the master value.
- Show the history of mastership transfers for a fact type.
Moral aspects Filled
- Wrong facts about people, pay or obligations can cause real harm when authority is unclear.
- Clear ownership makes someone accountable for correcting errors.
Who is affected
- People and organisations described by the facts
- Data stewards and system owners
- Consumers of the facts in reports and decisions
Owners Filled
Steward
An enterprise data governance steward maintains fact authority assignments on behalf of authorized domain data owners, separately from model maintenance.
Master systems
- A data governance registry maintains fact ownership and stewardship assignments.
- An authority policy registry maintains mastership periods and change rights.
- A governance workflow system maintains assignment approvals, disputes and transfers.
- Designated domain systems of record maintain the master values assigned to them.
Links to other meta-models Filled
references
- WM-XCT-001 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A mastership rule is identified by fact type, master system and validity period.
- A stewardship assignment is identified by fact type, role and period.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- An authority record names a fact type, an owner, a steward, a master system and a period.
- Often confused with the owner of a whole model, dataset or application.
Capabilities and actions required Filled
- Writes can be checked against the rule valid at the time.
- Contested facts can be routed to the right person for resolution.
Hazards and failure modes required Filled
- Silent overwrites by the most recent import.
- Orphaned fact types without any steward.
- Retroactive rule changes that rewrite history.
Standards and interfaces required Filled
- W3C PROV-O for attribution of facts to sources and agents.
- W3C ODRL for policies that express change rights.
- ISO 8000 from ISO for data quality and master data.
Context of use required Filled
- Used wherever several systems hold overlapping facts about the same subjects.
- Master data management and data governance programs rely on these rules.
Sources Filled
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
- W3C Data on the Web Best Practices - Checked live (HTTP 200) on 2026-10-07.
- Controlled Identifiers v1.0 - Carried over from the published world model wm-xct-001-ownership-stewardship; checked live (HTTP 200) on 2026-10-09.
- Decentralized Identifiers (DIDs) v1.1 - Carried over from the published world model wm-xct-001-ownership-stewardship; checked live (HTTP 200) on 2026-10-09.
- PROV-O: The PROV Ontology - Carried over from the published world model wm-xct-001-ownership-stewardship; checked live (HTTP 200) on 2026-10-09.
Open questions
- Who may change a specific fact?
- How to resolve a conflict between equal sources?
- How to transfer responsibility without losing provenance?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-xct-02/brief.json, ver-cy/world-models/card-supplements/em-xct-02.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.