EM-XCT-08 · Enterprise profiles · Published 0.1.0

Enterprise Source Synchronization

Connect qualified source records to existing company subjects, preserve immutable intake evidence and explain synchronization progress without inventing identity or deletion.

5 bundles · 10 layers · 27 findings · 54 questions

Required adoption limits

Start with SourceInstance, qualified acquisition scope and steward-reviewed aboutness to existing subjects. Metadata intake never creates or retires business subjects. Executable use needs trusted host identity, grants, time, evidence custody and current local-store ownership. Read the finite-capacity, shared-page, disclosure and recovery limits before installation.

Publication addendum and exact limits

Use in a Company Dimension

Begin with a declared source, qualified scope and reviewed aboutness mapping to an existing subject. The local reference and three synthetic profiles add atomic metadata receipts, snapshot coverage and a native restricted projection.

Research assurance: reviewable-draft. This is a bounded original companion. No live connectors, IAM, business fact application, distributed exactly-once, writable archive import, automated quarantine resolution or production-scale storage. Current host state and protected evidence custody are required. Adoption limits.

Bundles → Layers → Findings → Questions

Collect the expected evidence for each question. Unknown context remains explicit. Listed actions confer no operational permission.

SS-B1Sources2 layers

Sources questions, evidence and guarded decisions.

SS-B1-L1Source identity3 findings

Source identity of a source synchronization register.

SS-F01

Source instance

Immutable SourceInstance declaration and continuity evidence

Questions

SS-Q01 Which actual tenant and environment emits these records?host-guidance
Expected answer
- Immutable SourceInstance declaration and continuity evidence
- Register a new instance generation only after host verification.
SS-Q02 What evidence distinguishes a restored or recreated instance?host-guidance
Expected answer
- Immutable SourceInstance declaration and continuity evidence
- Register a new instance generation only after host verification.

Artifacts

Immutable SourceInstance declaration and continuity evidenceRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

SS-F02

Qualified keys

Source, resource, scheme/version, exact key and record generation

Questions

SS-Q03 What qualifies this local record key?host-guidance
Expected answer
- Source, resource, scheme/version, exact key and record generation
- Preserve lexical bytes and namespace; never infer identity from a display name.
SS-Q04 Are lexical differences or recycled keys being hidden?host-guidance
Expected answer
- Source, resource, scheme/version, exact key and record generation
- Preserve lexical bytes and namespace; never infer identity from a display name.

Artifacts

Source, resource, scheme/version, exact key and record generationRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Preserve lexical bytes and namespace; never infer identity from a display name. Requires applicable host authority.

SS-F03

Continuity

Generation evidence with source or authorized steward attribution

Questions

SS-Q05 Is the record generation known?host-guidance
Expected answer
- Generation evidence with source or authorized steward attribution
- Keep unknown continuity unpinned; do not invent a generation.
SS-Q06 Who can attest non-reuse or an incarnation?host-guidance
Expected answer
- Generation evidence with source or authorized steward attribution
- Keep unknown continuity unpinned; do not invent a generation.

Artifacts

Generation evidence with source or authorized steward attributionRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Keep unknown continuity unpinned; do not invent a generation. Requires applicable host authority.

SS-B1-L2Acquisition interpretation2 findings

Acquisition interpretation of a source synchronization register.

SS-F04

Scope boundary

Immutable scope and literal evidence-reference fingerprint

Questions

SS-Q07 Which filter, projection and visibility does this acquisition cover?host-guidance
Expected answer
- Immutable scope and literal evidence-reference fingerprint
- Create a new scope for changed interpretation; do not compare incompatible coverage.
SS-Q08 Did interpretation or schema change?host-guidance
Expected answer
- Immutable scope and literal evidence-reference fingerprint
- Create a new scope for changed interpretation; do not compare incompatible coverage.

Artifacts

Immutable scope and literal evidence-reference fingerprintRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Create a new scope for changed interpretation; do not compare incompatible coverage. Requires applicable host authority.

SS-F05

Opaque progress

Protected token reference, local epoch, fence and head

Questions

SS-Q09 What exact source position was retained?host-guidance
Expected answer
- Protected token reference, local epoch, fence and head
- Treat tokens as opaque; a new epoch does not itself change business identity.
SS-Q10 Is a token reset being confused with record rebirth?host-guidance
Expected answer
- Protected token reference, local epoch, fence and head
- Treat tokens as opaque; a new epoch does not itself change business identity.

Artifacts

Protected token reference, local epoch, fence and headRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Treat tokens as opaque; a new epoch does not itself change business identity. Requires applicable host authority.

SS-B2Mappings2 layers

Mappings questions, evidence and guarded decisions.

SS-B2-L1Aboutness governance3 findings

Aboutness governance of a source synchronization register.

SS-F06

Subject meaning

Governed target catalogue and source-kind/target-kind/purpose pair

Questions

SS-Q11 Which existing subject is this record about?host-guidance
Expected answer
- Governed target catalogue and source-kind/target-kind/purpose pair
- Propose aboutness only; do not create or merge business subjects.
SS-Q12 Is a source board being mistaken for a business Project?host-guidance
Expected answer
- Governed target catalogue and source-kind/target-kind/purpose pair
- Propose aboutness only; do not create or merge business subjects.

Artifacts

Governed target catalogue and source-kind/target-kind/purpose pairRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Propose aboutness only; do not create or merge business subjects. Requires applicable host authority.

SS-F07

Lifecycle

Proposed, active, disputed or retracted revisions with activation guard

Questions

SS-Q13 Which mapping revision is active?host-guidance
Expected answer
- Proposed, active, disputed or retracted revisions with activation guard
- Check complete-lineage/purpose uniqueness on every activation.
SS-Q14 Can a disputed claim reactivate beside another active claim?host-guidance
Expected answer
- Proposed, active, disputed or retracted revisions with activation guard
- Check complete-lineage/purpose uniqueness on every activation.

Artifacts

Proposed, active, disputed or retracted revisions with activation guardRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Check complete-lineage/purpose uniqueness on every activation. Requires applicable host authority.

SS-F08

Replacement

New mapping identity, correction predecessor and retained history

Questions

SS-Q15 Which earlier mapping is being corrected?host-guidance
Expected answer
- New mapping identity, correction predecessor and retained history
- Retract the old claim before activation; a temporary zero-active interval is allowed.
SS-Q16 Has the earlier claim been retracted first?host-guidance
Expected answer
- New mapping identity, correction predecessor and retained history
- Retract the old claim before activation; a temporary zero-active interval is allowed.

Artifacts

New mapping identity, correction predecessor and retained historyRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Retract the old claim before activation; a temporary zero-active interval is allowed. Requires applicable host authority.

SS-B2-L2Pinned interpretation2 findings

Pinned interpretation of a source synchronization register.

SS-F09

Historical outcome

Occurrence mapping/state, catalogue and policy revision pins

Questions

SS-Q17 Which mapping applied at first admission?host-guidance
Expected answer
- Occurrence mapping/state, catalogue and policy revision pins
- Keep the original outcome immutable; inspect later revisions separately.
SS-Q18 Will a later correction silently repin old data?host-guidance
Expected answer
- Occurrence mapping/state, catalogue and policy revision pins
- Keep the original outcome immutable; inspect later revisions separately.

Artifacts

Occurrence mapping/state, catalogue and policy revision pinsRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Keep the original outcome immutable; inspect later revisions separately. Requires applicable host authority.

SS-F10

Suspension

Current catalogue/validity check within the receiving scope and active-pin-suspended outcome

Questions

SS-Q19 Does the current target kind still satisfy the mapping?host-guidance
Expected answer
- Current catalogue/validity check within the receiving scope and active-pin-suspended outcome
- Withhold new pins and preserve the active uniqueness reservation until steward action.
SS-Q20 Does a suspended claim still reserve its lineage?host-guidance
Expected answer
- Current catalogue/validity check within the receiving scope and active-pin-suspended outcome
- Withhold new pins and preserve the active uniqueness reservation until steward action.

Artifacts

Current catalogue/validity check within the receiving scope and active-pin-suspended outcomeRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Withhold new pins and preserve the active uniqueness reservation until steward action. Requires applicable host authority.

SS-B3Intake2 layers

Intake questions, evidence and guarded decisions.

SS-B3-L1Atomic delivery3 findings

Atomic delivery of a source synchronization register.

SS-F11

Batch identity

Scope/epoch-wide key and exact ordered content digest

Questions

SS-Q21 What identity survives a retry and a writer replacement?host-guidance
Expected answer
- Scope/epoch-wide key and exact ordered content digest
- Reuse exact content/key after a lost response; never silently accept changed content.
SS-Q22 Has content changed under the same key?host-guidance
Expected answer
- Scope/epoch-wide key and exact ordered content digest
- Reuse exact content/key after a lost response; never silently accept changed content.

Artifacts

Scope/epoch-wide key and exact ordered content digestRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Reuse exact content/key after a lost response; never silently accept changed content. Requires applicable host authority.

SS-F12

Commit boundary

One local SQLite transaction and retained acknowledgement

Questions

SS-Q23 Were metadata, receipt and progress committed together?host-guidance
Expected answer
- One local SQLite transaction and retained acknowledgement
- Use the owned local store; external payload durability remains a host responsibility.
SS-Q24 Could a crash expose a head without its records?host-guidance
Expected answer
- One local SQLite transaction and retained acknowledgement
- Use the owned local store; external payload durability remains a host responsibility.

Artifacts

One local SQLite transaction and retained acknowledgementRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Use the owned local store; external payload durability remains a host responsibility. Requires applicable host authority.

SS-F13

Concurrency

Serialized transaction and restricted conflict diagnostic

Questions

SS-Q25 Which expected head and fence admitted this new batch?host-guidance
Expected answer
- Serialized transaction and restricted conflict diagnostic
- Refuse stale new admissions; an authorized exact own retry returns its old acknowledgement.
SS-Q26 Does a stale writer advance progress?host-guidance
Expected answer
- Serialized transaction and restricted conflict diagnostic
- Refuse stale new admissions; an authorized exact own retry returns its old acknowledgement.

Artifacts

Serialized transaction and restricted conflict diagnosticRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Refuse stale new admissions; an authorized exact own retry returns its old acknowledgement. Requires applicable host authority.

SS-B3-L2Partial failure2 findings

Partial failure of a source synchronization register.

SS-F14

Quarantine

Durable restricted quarantine evidence and open retry obligation

Questions

SS-Q27 Which input descriptors were rejected?host-guidance
Expected answer
- Durable restricted quarantine evidence and open retry obligation
- Retain each rejected descriptor; resolve externally and reingest with a new batch.
SS-Q28 Do received counts equal retained accepted plus quarantined counts?host-guidance
Expected answer
- Durable restricted quarantine evidence and open retry obligation
- Retain each rejected descriptor; resolve externally and reingest with a new batch.

Artifacts

Durable restricted quarantine evidence and open retry obligationRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Retain each rejected descriptor; resolve externally and reingest with a new batch. Requires applicable host authority.

SS-F15

Empty versus missing

Explicit empty flag, contiguous page indices and terminal marker

Questions

SS-Q29 Was an empty page explicitly delivered?host-guidance
Expected answer
- Explicit empty flag, contiguous page indices and terminal marker
- Keep missing coverage insufficient; do not infer business deletion.
SS-Q30 Are missing pages or transport failures being treated as an empty source?host-guidance
Expected answer
- Explicit empty flag, contiguous page indices and terminal marker
- Keep missing coverage insufficient; do not infer business deletion.

Artifacts

Explicit empty flag, contiguous page indices and terminal markerRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Keep missing coverage insufficient; do not infer business deletion. Requires applicable host authority.

SS-B4Evidence2 layers

Evidence questions, evidence and guarded decisions.

SS-B4-L1Time and availability3 findings

Time and availability of a source synchronization register.

SS-F16

Three clocks

Nullable sourceEventTime, declared observedAt, trusted recordedAt and sequence

Questions

SS-Q31 When did the source event, acquisition and host receipt occur?host-guidance
Expected answer
- Nullable sourceEventTime, declared observedAt, trusted recordedAt and sequence
- Preserve unknown source time and compare only the appropriate clock.
SS-Q32 Was an unknown source time invented?host-guidance
Expected answer
- Nullable sourceEventTime, declared observedAt, trusted recordedAt and sequence
- Preserve unknown source time and compare only the appropriate clock.

Artifacts

Nullable sourceEventTime, declared observedAt, trusted recordedAt and sequenceRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Preserve unknown source time and compare only the appropriate clock. Requires applicable host authority.

SS-F17

Occurrence correction

Earlier occurrence reference, known lineage and steward admission

Questions

SS-Q33 Which retained occurrence is corrected?host-guidance
Expected answer
- Earlier occurrence reference, known lineage and steward admission
- Append correction evidence; keep the old occurrence unchanged.
SS-Q34 Is correction lineage and attribution valid?host-guidance
Expected answer
- Earlier occurrence reference, known lineage and steward admission
- Append correction evidence; keep the old occurrence unchanged.

Artifacts

Earlier occurrence reference, known lineage and steward admissionRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Append correction evidence; keep the old occurrence unchanged. Requires applicable host authority.

SS-F18

Source availability

Explicit source-availability operation

Questions

SS-Q35 Was a source record deleted, removed from scope or inaccessible?host-guidance
Expected answer
- Explicit source-availability operation
- Retain availability evidence without changing the subject lifecycle.
SS-Q36 Does that authorize retirement of a business subject?host-guidance
Expected answer
- Explicit source-availability operation
- Retain availability evidence without changing the subject lifecycle.

Artifacts

Explicit source-availability operationRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Retain availability evidence without changing the subject lifecycle. Requires applicable host authority.

SS-B4-L2Coverage assessment3 findings

Coverage assessment of a source synchronization register.

SS-F19

Round completion

Sealed terminal round and separate consistency/visibility declarations

Questions

SS-Q37 Were all pages accounted for without quarantine or unknown keys?host-guidance
Expected answer
- Sealed terminal round and separate consistency/visibility declarations
- Distinguish strong local key accounting from a verified source guarantee.
SS-Q38 Does this prove that the external source is actually complete?host-guidance
Expected answer
- Sealed terminal round and separate consistency/visibility declarations
- Distinguish strong local key accounting from a verified source guarantee.

Artifacts

Sealed terminal round and separate consistency/visibility declarationsRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Distinguish strong local key accounting from a verified source guarantee. Requires applicable host authority.

SS-F20

Comparable absence

Explicit not-earlier witness and complete source-snapshot rounds

Questions

SS-Q39 Are two rounds of the same scope genuinely ordered and comparable?host-guidance
Expected answer
- Explicit not-earlier witness and complete source-snapshot rounds
- Emit only a steward-review proposal and no effects.
SS-Q40 Could visibility or a new interpretation explain the missing key?host-guidance
Expected answer
- Explicit not-earlier witness and complete source-snapshot rounds
- Emit only a steward-review proposal and no effects.

Artifacts

Explicit not-earlier witness and complete source-snapshot roundsRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Emit only a steward-review proposal and no effects. Requires applicable host authority.

SS-F21

Competing evidence

Both retained evidence references and separately governed selection policy

Questions

SS-Q41 Do different sources disagree about a subject?host-guidance
Expected answer
- Both retained evidence references and separately governed selection policy
- Do not let arrival order or connector ownership choose business truth.
SS-Q42 Which separate authority contract can adjudicate those facts?host-guidance
Expected answer
- Both retained evidence references and separately governed selection policy
- Do not let arrival order or connector ownership choose business truth.

Artifacts

Both retained evidence references and separately governed selection policyRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Do not let arrival order or connector ownership choose business truth. Requires applicable host authority.

SS-B5Operation2 layers

Operation questions, evidence and guarded decisions.

SS-B5-L1Rights and custody3 findings

Rights and custody of a source synchronization register.

SS-F22

Current permission

Current exact host grant and authenticated actor

Questions

SS-Q43 Can this actor intake, map, read or attest coverage for this purpose now?host-guidance
Expected answer
- Current exact host grant and authenticated actor
- Check each right independently; never derive permission from semantic source priority.
SS-Q44 Does bootstrap administration imply ordinary writer permission?host-guidance
Expected answer
- Current exact host grant and authenticated actor
- Check each right independently; never derive permission from semantic source priority.

Artifacts

Current exact host grant and authenticated actorRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Check each right independently; never derive permission from semantic source priority. Requires applicable host authority.

SS-F23

Restricted disclosure

Current read decision, protected projections and documented key-unavailability bit

Questions

SS-Q45 Can this result or diagnostic be disclosed now?host-guidance
Expected answer
- Current read decision, protected projections and documented key-unavailability bit
- Keep full archives privileged; acknowledge the residual availability side channel.
SS-Q46 What can a competing authorized writer infer from refusal?host-guidance
Expected answer
- Current read decision, protected projections and documented key-unavailability bit
- Keep full archives privileged; acknowledge the residual availability side channel.

Artifacts

Current read decision, protected projections and documented key-unavailability bitRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Keep full archives privileged; acknowledge the residual availability side channel. Requires applicable host authority.

SS-F24

Evidence custody

Host-managed protected evidence references

Questions

SS-Q47 Where are payloads, tokens and verification evidence stored?host-guidance
Expected answer
- Host-managed protected evidence references
- Verify custody externally; the reference neither fetches nor authenticates payload bytes.
SS-Q48 Does a submitted digest prove they exist or are safe?host-guidance
Expected answer
- Host-managed protected evidence references
- Verify custody externally; the reference neither fetches nor authenticates payload bytes.

Artifacts

Host-managed protected evidence referencesRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Verify custody externally; the reference neither fetches nor authenticates payload bytes. Requires applicable host authority.

SS-B5-L2Adoption and recovery3 findings

Adoption and recovery of a source synchronization register.

SS-F25

Native binding

One register object, snapshot facts and explicit extension validation

Questions

SS-Q49 Does the stored snapshot preserve the full semantic journal?host-guidance
Expected answer
- One register object, snapshot facts and explicit extension validation
- Validate both envelopes and nested history; the snapshot is a restricted projection.
SS-Q50 Did installed companion validation run after outer checks?host-guidance
Expected answer
- One register object, snapshot facts and explicit extension validation
- Validate both envelopes and nested history; the snapshot is a restricted projection.

Artifacts

One register object, snapshot facts and explicit extension validationRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Validate both envelopes and nested history; the snapshot is a restricted projection. Requires applicable host authority.

SS-F26

Restore continuity

External ownership/current-root evidence and historical-only import report

Questions

SS-Q51 Is this the current owned database or a coherent old copy?host-guidance
Expected answer
- External ownership/current-root evidence and historical-only import report
- Refuse writable archive import; establish a fresh baseline on another host.
SS-Q52 Can an archive legitimately resume an external token?host-guidance
Expected answer
- External ownership/current-root evidence and historical-only import report
- Refuse writable archive import; establish a fresh baseline on another host.

Artifacts

External ownership/current-root evidence and historical-only import reportRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Refuse writable archive import; establish a fresh baseline on another host. Requires applicable host authority.

SS-F27

Minimum profile

Synthetic startup, international and AI cases with explicit limits

Questions

SS-Q53 Which small source/mapping boundary is useful today?host-guidance
Expected answer
- Synthetic startup, international and AI cases with explicit limits
- Start with the smallest reviewed scope; scale storage and connectors under a separate contract.
SS-Q54 Which enterprise capabilities are still deferred?host-guidance
Expected answer
- Synthetic startup, international and AI cases with explicit limits
- Start with the smallest reviewed scope; scale storage and connectors under a separate contract.

Artifacts

Synthetic startup, international and AI cases with explicit limitsRetained or host-verified evidence; unknown context is explicit.

Actions and unknown handling

Start with the smallest reviewed scope; scale storage and connectors under a separate contract. Requires applicable host authority.

Research and validation

Actual independent Claude Opus 5 High and Grok Heavy studies and S1/S2 research clarification were followed by separate implementation audits. Divergent R2/R3 verdicts and reproduced defects are retained. Both R4 delta audits accept with limits; both final R4a documentation/test addendum reviews accept. Author-executed 101 tests, three native compositions and one near-capacity observation are separate evidence, not reviewer execution. Executed tests and native checks are recorded separately. Research dossier · Review and limits · Tests · Native acceptance · Checksums.

Catalogue identity: vr.profile.enterprise-source-synchronization. EM-XCT-08 remains a broader, partially covered research contour. Parent models are semantic references; no subtype or whole-parent conformance is asserted.