Enterprise Assertion Provenance
Preserve the origins, evidence, changes and method-qualified confidence of enterprise assertions without inferring truth or permission.
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 20 findings · 20 questions
Sources and execution Sources and execution for the bounded assertion-provenance contract.
Captured representations
Collect explicit context and preserve unknowns. See the semantic contract for exact rules.
What was directly acquired, and by whom?
What was directly acquired, and by whom? Separate capture from claim truth
- What was directly acquired, and by whom? Separate capture from claim truth governed-context
What survives rename or relocation?
What survives rename or relocation? Distinguish source location and identity
- What survives rename or relocation? Distinguish source location and identity governed-context
Which representation and which execution event are being described?
Which representation and which execution event are being described? Keep their identities separate
- Which representation and which execution event are being described? Keep their identities separate governed-context
Execution activities
Collect explicit context and preserve unknowns. See the semantic contract for exact rules.
Is this source-asserted, inferred or proposed?
Is this source-asserted, inferred or proposed? Separate account and activity kind
- Is this source-asserted, inferred or proposed? Separate account and activity kind governed-context
Correction or a new acquisition/assessment?
Correction or a new acquisition/assessment? Preserve activity identity
- Correction or a new acquisition/assessment? Preserve activity identity governed-context
Assertion accounts Assertion accounts for the bounded assertion-provenance contract.
Claim and account boundary
Collect explicit context and preserve unknowns. See the semantic contract for exact rules.
Is this the claim, its account or its evidence?
Is this the claim, its account or its evidence? Preserve grain
- Is this the claim, its account or its evidence? Preserve grain governed-context
Which system masters which data?
Which system masters which data? Avoid a new master for the external claim
- Which system masters which data? Avoid a new master for the external claim governed-context
Historical reliance
Collect explicit context and preserve unknowns. See the semantic contract for exact rules.
How is an unreliable account withdrawn?
How is an unreliable account withdrawn? Preserve immutable history
- How is an unreliable account withdrawn? Preserve immutable history governed-context
What was known at a particular time?
What was known at a particular time? Keep occurrence/capture/receipt separate
- What was known at a particular time? Keep occurrence/capture/receipt separate governed-context
Which state transitions are allowed?
Which state transitions are allowed? Distinguish account lifecycle from kind
- Which state transitions are allowed? Distinguish account lifecycle from kind governed-context
Evidence and assessment Evidence and assessment for the bounded assertion-provenance contract.
Evidence relationships
Collect explicit context and preserve unknowns. See the semantic contract for exact rules.
What is missing or disputed?
What is missing or disputed? No selected truth from absent evidence
- What is missing or disputed? No selected truth from absent evidence governed-context
Which links and cardinalities are required?
Which links and cardinalities are required? No dangling executable references
- Which links and cardinalities are required? No dangling executable references governed-context
Are multiple citations independent?
Are multiple citations independent? Repetition is not corroboration
- Are multiple citations independent? Repetition is not corroboration governed-context
Qualified confidence
Collect explicit context and preserve unknowns. See the semantic contract for exact rules.
Can two confidence values be compared?
Can two confidence values be compared? Method and scale matter
- Can two confidence values be compared? Method and scale matter governed-context
Governance and adoption Governance and adoption for the bounded assertion-provenance contract.
Rights and disclosure
Collect explicit context and preserve unknowns. See the semantic contract for exact rules.
Who may change this record?
Who may change this record? Authorship is not authentication
- Who may change this record? Authorship is not authentication governed-context
What can this reader see for this purpose?
What can this reader see for this purpose? Avoid evidence leakage
- What can this reader see for this purpose? Avoid evidence leakage governed-context
What can an agent conclude or propose?
What can an agent conclude or propose? Keep evidence distinct from permission
- What can an agent conclude or propose? Keep evidence distinct from permission governed-context
Minimal composition and migration
Collect explicit context and preserve unknowns. See the semantic contract for exact rules.
What is the smallest useful setup?
What is the smallest useful setup? Optional confidence, no mandatory ERP
- What is the smallest useful setup? Optional confidence, no mandatory ERP governed-context
Does the native envelope validate the inner history?
Does the native envelope validate the inner history? Check both layers
- Does the native envelope validate the inner history? Check both layers governed-context
Can this old payload be imported without losing semantics?
Can this old payload be imported without losing semantics? Preserve unknowns
- Can this old payload be imported without losing semantics? Preserve unknowns governed-context
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Cross-cutting context
- Entry kind
- companion-contract
- Navigation path
- NAV.XCT
- Domain
- EnterpriseProvenanceEvidence
- Industry
- Cross-industry
- Tags
- EM-XCT-03provenanceevidenceassertionconfidence
- Also called
- Assertion provenance, EM-XCT-03, Evidence and confidence
What it is Filled
A companion contract for a Company Dimension that records where each enterprise assertion came from: the source, how and when it was acquired, the evidence kept and the method-qualified confidence, without judging whether the assertion is true.
Why it exists Filled
Preserve the origins, evidence, changes and method-qualified confidence of enterprise assertions without inferring truth or permission.
Distinguishing features Filled
- Records where an enterprise assertion came from and on what evidence, without deciding whether it is true.
- Gives every change of source, acquisition, version or content digest a new capture ID instead of overwriting.
- Keeps confidence qualified by the method that produced it, so numbers from different schemes are never added up.
What robots and AI may and may not do Filled
Must not
- Infer that a source is true because it is recorded here.
- Count assertions with shared inputs as independent confirmation.
- Do arithmetic across confidence schemes.
- Rewrite a historical account when reading it.
Only with a human decision
- Withdrawing an assertion that others rely on.
- Adopting an assertion as authoritative for a business decision.
May
- Show the acquisition account and evidence behind an assertion.
- Append an authorized correction or withdrawal and propose re-review.
- Return insufficient-context with the known gaps when evidence is missing.
Moral aspects Filled
- Provenance records can expose who said what about whom; access must follow the rules of the underlying data.
- A confident-looking assertion without visible evidence can mislead decisions about people.
- Withdrawn assertions stay visible as history so that blame and correction remain traceable.
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 function of the company stewards provenance records; each assertion stays owned by its source system.
Master systems
- Source systems that issue the assertions
- Evidence store holding captured content
Links to other meta-models Filled
references
- WM-XCT-012 - 0.3.0-research.1
- WM-XCT-026 - 0.3.0-research.1
- WM-XCT-028 - 0.3.0-research.1
aligned
- vr.wm-xct-012
- vr.wm-xct-026
- vr.wm-xct-028
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Capture ID per acquisition, changed whenever source identity, version or content digest changes.
- External source identity kept separately from the capture.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: it has no physical body to measure.
Recognition optional Filled
- A provenance record points to one assertion and lists its source, acquisition time, method and evidence.
- It is confused with the assertion itself and with an audit log of system access.
Capabilities and actions required Filled
- Show acquisition account; never infer source truth
- Preserve external source identity separately; a changed sourceRef, acquisition, version or content digest requires a new Capture ID
- Record one representation and a separately identified event; reject incompatible declaration
- Explain declared kind and its limits
- Correct metadata or mint a genuinely new event
- Resolve exact record kind
- Link to the owning system
- Append an authorized withdrawal; propose re-review
- Read historical account without rewriting it
- Admit authorized creation/correction/withdrawal
- Return insufficient-context and known gaps
- Reject malformed or unresolved internal pins
- Flag shared inputs; never count distinct roots as proof
- Refuse automatic cross-scheme arithmetic
- Validate current scope; emit generic rejection
- Return full permitted view or generic denial
- Explain and propose a check; do not contact, publish or change rights
- Compose the bounded companion
- Validate nested register and extension against trusted prior root
- Accept same-version lossless snapshot only; stage other mappings for review
Hazards and failure modes required Filled
- Circular confirmation when two records share one upstream source.
- False authority when provenance is displayed as proof.
Standards and interfaces required Filled
- W3C PROV-O.
- Content digests (SHA-256) for captured evidence.
Context of use required Filled
- Applies to facts held in a Company Dimension that come from internal or external sources.
Sources Filled
- Research record EM-XCT-03: independent provider studies, audits and reconciled findings - Evidence behind the release; claims in the card trace to it.
- Enterprise Assertion Provenance 0.1.0 specification - Normative release, digest sha256:a8f41fb65aa5892c884731c9c4d06402637bf26bc55ab53a6ad9c7fbc34a44f0
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/enterprise-assertion-provenance/versions/0.1.0/spec.json, models/enterprise-assertion-provenance/catalogue-entry.json, ver-cy/world-models/card-supplements/enterprise-assertion-provenance.json