# EM-LND-18 local synthesis ## Disposition - Propose identifier-unassigned **Enterprise Landscape** as a governed composition declaration with lifecycle independent of its domain members. - Profile **Enterprise View Scope** as a versioned WM-KNW-012 policy/expression release, not a new root. - Keep projection outputs immutable, digest-identified artifacts with no write path and no domain-data copies. - Do not use WM-XCT-039 as the host; it remains managed-IT-specific. - Allocate no catalogue or runtime identifier. ## Identity and mastership Enterprise Landscape owns its declaration identity, revisions, member selection, management questions, mastership map, crosswalk pins, completeness perimeter, authority and review cycle. It can be approved, narrowed, superseded and retired without changing any domain fact. All facts remain mastered in their domains. The declaration owns only pins, derived rows and a gap/conflict register. View-local keys and digests never become business identifiers, and corrections return to source masters. Enterprise View Scope uses WM-KNW-012 work/expression/manifestation identity to publish immutable inclusion rules, precedence/conflict strategy, derogations, comparability, disclosure and retention policy. ## Selection and questions A domain enters only for a cited management question, a decision it informs and a traceable question-to-domain-to-measure path. Registry membership, tags and convenience never require inclusion. Non-selected domains are recorded with reasons and remain distinct from unavailable, withheld, pending, blocked and unknown. The registry never imposes installation of every domain. ## Composition and transitions Every cross-domain transition preserves owning domain/master, steward, asserting party and capacity, evidence/digest, method, confidence, effective interval, observation/record time, rights and uncertainty. Derived rows retain inputs, rule versions and as-of cuts and remain distinct from assertions. Desired, observed, scenario and derived states remain parallel. ## Semantic conflicts Conflicts are adjudicated by axis. Shared labels never prove identity. Identifiers require master-system evidence or a governed mapping. Effective, observation, record, reporting and knowledge clocks remain distinct. Completeness claims retain native granularity. The most restrictive constituent access rule governs derived disclosure. Edge direction, native term and reversal semantics are preserved. Every axis is classified comparable, bridged by a named transformation or non-comparable. Missing verdict means non-comparable; recency never resolves a dispute. ## Completeness and absence Completeness is relative to named questions, selected domains, perimeter, denominator, supported granularity and opaque segments. Negative claims require covering closed-scope evidence. Unavailable, withheld, suppressed, unknown, pending, not-selected and zero never collapse. A domain outside the question does not reduce completeness. ## Rights, time and provenance Composition grants no access. Cross-domain reads require explicit purpose, scope and revocation and a least-disclosure projection. Withheld segments are marked withheld and cached paths cannot bypass revocation. Views pin world time and knowledge time separately. Issued outputs are immutable, digest-identified and non-reimportable. Corrections append successors; scenarios never become authoritative facts. ## Host and runtime boundary WM-XCT-039 is a managed-IT provider/client graph and cannot host finance, legal, workforce, knowledge and other domain composition without becoming the forbidden universal kernel. Its transferable patterns include per-fact mastership, default-deny access, indeterminate outcomes and incomplete-impact semantics. Landscape artifact, completeness perimeter, crosswalk edition and management-question boundaries remain unallocated. WM-XCT-037 traversal contradictions and empty composition contracts block safe cross-domain traversal. ## Acceptance result A three-person service firm selects contract/obligation, finance and client-commercial landscapes for three questions; workforce, group, consolidation and supply are not-selected with reasons. A holding group uses another release selecting ownership, consolidation, finance, commercial concentration and risk. Ownership and consolidation remain parallel, an unknown ultimate parent remains reason-coded unknown, and neither organization installs the other's unused domains. ## Required invariants 1. Composition is explicitly selected and question-justified. 2. Facts remain mastered in domains and the landscape has no write path. 3. Cross-context transitions preserve mastership, rights, provenance, time and uncertainty. 4. Shared labels never establish identity or comparability. 5. Every conflict axis has a comparability verdict. 6. Completeness is perimeter-relative. 7. Negative claims require covering completeness. 8. Membership grants no access. 9. Withheld, unknown, not-selected and zero remain distinct. 10. World and knowledge time are pinned separately. 11. Views are immutable and non-reimportable. 12. Scenarios never become authoritative. 13. No universal kernel or domain-data copy is created. ## Holds Enterprise Landscape and several support boundaries are unallocated. WM-KNW-012 lacks record-classification, retention, tailoring and defect functions. WM-XCT-037 has unresolved traversal, identity-strength and composition contradictions. WM-XCT-039 has validation and adapter gaps. Organization relationship parentage remains unsettled. All bases are non-canonical and mostly single-provider; crosswalks, immutable pins and fixtures are absent. No installability or publication-readiness claim is made. ## Grok reconciliation Grok accepted both candidates with gaps and confirmed the no-ID, domain-mastership, non-reimport and non-universal-host boundary. The reconciled dossier adds explicit perimeter, withheld markers, semantic-axis readings, three distinct clocks and per-release rights evaluation. ## Frozen audit outcome The single Claude Opus high/no-tools audit call received the frozen dossier but timed out after nearly ten hours and returned zero bytes. The call is spent and will not be rerun. This failure is a publication hold, not evidence against the boundary.