# Enterprise Source Synchronization

Read model-spec.md, adoption-limits.md and bindings/native-v3.md before proposing installation. This companion records source metadata and aboutness; never treat it as a business subject factory, Identity same-as registry, fact authority, credential provider or production connector.

Use exact source/resource/key scheme/generation. Unknown continuity stays unpinned. Never create one Project per source board. Mapping changes append a new claim or guarded state revision; old occurrence pins stay unchanged. Missing source records never authorize subject retirement. Current intake, mapping, read and coverage-attestation rights are separate. Occurrence corrections require current map and read as well as intake in the same scope/purpose.

Actor, source attestation, catalogue, evidence custody, current time and owned-current database are trusted host inputs. A valid archive proves internal consistency only. Privileged native/archive APIs are not public disclosure APIs. Never resume from an imported token or coherent old backup without external reconciliation. No production credentials or actual company records belong in the public fixtures.

Run test_sync.py and acceptance.py with exact tool-pins.json. Native outer validation alone does not validate nested history. Preserve reviewed release bytes and the trusted predecessor snapshot when checking extensions. Publication status does not complete the broader research contour.