EM-XCT-02 · Enterprise profiles · Published 0.1.0

Enterprise Fact Authority

Describe who is accountable for a fact, who maintains it, which source is preferred, who may submit a change, and how conflicts and history are retained in your Company Dimension.

4 bundles · 6 layers · 18 findings · 18 questions. Open a layer to inspect its findings, questions, expected answers, artifacts and permitted actions.

Use in a Company Dimension

Start with one governed fact scope, an accountable party, a manual or connected source and an explicit write grant. Add stewardship, competing sources and history as needed. The downloadable package includes the schema, reference validator and three synthetic Dimension examples.

Research assurance: reviewable-draft. EM-XCT-02 remains partially covered. The host must authenticate actors and invoke the companion validator; native envelope validation alone is insufficient. Read adoption limits.

Bundles → Layers → Findings → Questions

Findings are information needs about the model, not additional entity types. Expected answers describe what to collect or inspect; they are not prefilled facts about your company. Listed actions confer no permission by themselves.

Bundle Governance 2 layers

Scope, accountability and operational appointments.

Layer Scope and accountable term 6 findings

FactAuthority; definition/value separation.

Finding · FA-boundary

Object boundary

Question Q01

Is this a meaning, value assertion or ownership record?

Expected answer

  • Identify whether the record concerns meaning, values or ownership.
  • For FactAuthority, governs is values; consult the separate definitionAuthorityRef for meaning.

Artifact / evidence

boundary-decision + governs

Action and unknown handling

Explain; do not infer title or definition ownership

Finding · FA-identity

Stable identity

Question Q02

What survives rename/transfer?

Expected answer

  • Record ID, dimension, scope, predicate, revision and previousDigest.
  • For an observation, preserve subject/source; for a part, preserve its identity, kind, owner and party/source.

Artifact / evidence

record IDs, anchors, revision chain

Action and unknown handling

Follow exact lineage; transfer by new term, never merge parties

Finding · FA-meaning

Definition authority

Question Q03

Who defines this predicate?

Expected answer

  • The external definitionAuthorityRef and the predicate whose meaning it governs.
  • State whether the external reference was verified; this companion does not validate it.

Artifact / evidence

definitionAuthorityRef

Action and unknown handling

Resolve externally; insufficient context if absent/unverified

Finding · FA-accountable

Accountability for values

Question Q04

Who answers for values at T?

Expected answer

  • The exact fact-valid time and knowledge cut, matching authority IDs/revisions/digests and accountable party.
  • No applicable authority means unknown; overlapping authority IDs mean authority-contested.

Artifact / evidence

authority slice

Action and unknown handling

Read accountable; zero/multiple returns unknown/contested

Finding · FA-overlap

Overlapping authorities

Question Q09

Which of two authorities applies?

Expected answer

  • Every matching active authority ID and exact revision digest at the requested times.
  • Return authority-contested; do not choose by recency or silently merge policies.

Artifact / evidence

authority-contested outcome

Action and unknown handling

Governor investigates; no recency fallback

Finding · FA-transfer

Accountability transfer

Question Q12

What happens at responsible-party change?

Expected answer

  • Guarded closure of the old term, transfer cutoff and a new term with a new identity.
  • Preserve old effective coverage; a gap remains unknown and a correction is not an automatic transfer.

Artifact / evidence

closed old term + new term

Action and unknown handling

Governor records both; gap stays unknown

Layer Operational appointments 1 finding

StewardshipAssignment; bounded duties and valid terms.

Finding · FA-steward

Stewardship and escalation

Question Q05

Who handles the disagreement?

Expected answer

  • Active stewardship IDs, party references, duties, effective terms and evidence.
  • Return the active resolve-conflict routes; absence is a gap. Duties confer no API write right.

Artifact / evidence

active assignment IDs and duties

Action and unknown handling

Propose routing; missing route needs appointment, no approval

Bundle Source policy 2 layers

Source preference and submission permission are governed separately.

Layer Selection 1 finding

MastershipRule; explicit source priority and overlap conflict.

Finding · FA-rank

Source precedence

Question Q07

Which source is preferred at fact time?

Expected answer

  • Applicable MastershipRule IDs, source URIs, priorities, valid terms and authority revision pins.
  • A smaller priority wins among eligible sources; priority neither proves truth nor grants writes.

Artifact / evidence

MastershipRule + policy pin

Action and unknown handling

Evaluate; priority is not truth or permission

Layer Submission 1 finding

WriteGrant; current rights for an authenticated source writer.

Finding · FA-write

Current submission rights

Question Q06

May this actor submit for source S now?

Expected answer

  • Authenticated caller, source, current trusted receipt time and matching WriteGrant.
  • Require one active source grant naming the caller plus current scoped authority/configuration; reject missing or ambiguous permission.

Artifact / evidence

separate WriteGrant + trust config

Action and unknown handling

Call admit through host; absent/ambiguous rejects

Bundle Observation 1 layer

Source-scoped assertions, correction history and retained evidence.

Layer Assertions and corrections 2 findings

FactObservation; immutable anchors and attributed revisions.

Finding · FA-correction

Correction history

Question Q11

How is a wrong claim corrected?

Expected answer

  • Next observation revision, immediate previousDigest, currently permitted writer and correction evidence.
  • Retain earlier rows and attribution; the source/subject anchors cannot change.

Artifact / evidence

next observation revision

Action and unknown handling

Currently granted same-source writer submits with evidence; retain prior rows

Finding · FA-evidence

Evidence and veracity

Question Q18

Does provenance prove the value?

Expected answer

  • Exact evidence references associated with the relevant record revisions.
  • Inspect provenance externally; its presence alone establishes neither veracity nor access rights.

Artifact / evidence

evidence references

Action and unknown handling

Inspect externally; no inferred veracity or access grant

Bundle Reliance 1 layer

Historical evaluation, disclosure, adoption and integration.

Layer Historical query and projection 7 findings

Derived Evaluation and AuthorityRegister; explicit input slices and permissions.

Finding · FA-conflict

Conflicting observations

Question Q08

What if equal sources disagree?

Expected answer

  • Competing observation IDs/revisions/digests, tagged lexical values and retained evidence.
  • Equal-priority disagreement returns contested with no selected value; preserve all competing records.

Artifact / evidence

both observation IDs/evidence

Action and unknown handling

Preserve contested; request human review, never overwrite

Finding · FA-history

Historical knowledge

Question Q10

What was known at T about valid time V?

Expected answer

  • fact-valid time, knownAt, profile version, configuration digest and full known input-slice digest.
  • Filter by receipt cut, then latest revision per ID, then effective interval; reject future knowledge.

Artifact / evidence

known input slice + authority pins

Action and unknown handling

Re-evaluate; future knowledge rejected

Finding · FA-disclosure

Reader disclosure

Question Q13

What can this reader see?

Expected answer

  • Current authenticated reader, admitted purpose and full-register read configuration.
  • All or deny before ledger diagnostics; never disclose a selectively filtered register as complete.

Artifact / evidence

trusted full-register read policy

Action and unknown handling

All or deny; do not drop a hidden contradiction

Finding · FA-minimum

Minimum startup profile

Question Q14

Does a startup need HRIS?

Expected answer

  • A Dimension, scoped governor, explicit accountable party, governed manual source and separate WriteGrant.
  • A single-source manual register is possible; missing stewardship remains visible and no HRIS is required.

Artifact / evidence

one-source minimal register

Action and unknown handling

Use governed manual source with explicit rights

Finding · FA-context

Missing context

Question Q15

What if source/policy is missing?

Expected answer

  • Query outcome/reason, retained evidence and unranked observation IDs in the matching slice.
  • Identify the missing authority, rule or source context; do not invent a preferred value.

Artifact / evidence

reason and unranked IDs

Action and unknown handling

Ask for missing authority/rule; do not invent source truth

Finding · FA-binding

Native binding and validation

Question Q16

Does native validation prove semantics?

Expected answer

  • Own runtime identity/version/specification digest, native envelope report and companion validation report.
  • Validate the nested register and extensions against the trusted previous snapshot; outer V3 validation is insufficient.

Artifact / evidence

native + companion reports

Action and unknown handling

Invoke both; nested V3 acceptance alone insufficient

Finding · FA-migration

Legacy migration

Question Q17

Can earlier owner strings be imported?

Expected answer

  • Explicit legacy-party/source/scope mappings, source evidence and staged candidates.
  • Do not promote owner strings automatically; refuse migration that loses history or semantics.

Artifact / evidence

migration.md

Action and unknown handling

Stage candidates outside operative register; explicit mapping required

Specification and research

This tree is a navigation view of the published contract’s structure table and all Q01–Q18 routes. The immutable 0.1.0 specification and package are unchanged. Machine specification · Release checksums · Claude and Grok research and audits.

Catalogue identity: vr.profile.enterprise-fact-authority. EM-XCT-02 identifies the broader research contour. The companion is associated with WM-XCT-001; it is not its subtype. Catalogue registration and this navigation view were added after the immutable release, whose historical manifest describes its earlier discovery status.