{"slug":"architecture/ENTITY_CONTEXT_AND_360_CONTRACT","title":"Entity Context and Entity 360 Contract","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/ENTITY_CONTEXT_AND_360_CONTRACT.mdx","bytes":1980,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Normative human explanation backed by\n[`total-end-state-contract.json`](./total-end-state-contract.json).\n\n## Live Entity is not Entity 360\n\nA Live Entity may exist on day one after one canonical identity is resolved. It\nmust disclose its lifecycle state, external identities, source provenance,\nfreshness or sync status, evidence, known relationships, and unresolved links.\nIt is not an Entity 360 merely because it is live.\n\nEntity 360 is a derived, maturity-gated multi-entity projection. It requires at\nleast two distinct resolved related canonical entities and sufficient evidence.\nIt discloses coverage, freshness, provenance, confidence, uncertainty, missing\nrelationship classes, and unresolved links; it never manufactures completeness\nfrom sample data.\n\n## Formation states\n\nThe only formation states are `not_formed`, `forming`, `partial`, `formed`, and\n`degraded`. The first three return honest Entity Context without presenting an\nEntity 360. `formed` may present a formed projection. `degraded` may present the\nlast formed projection only with explicit degraded and freshness metadata and\npolicy permission.\n\nTwin reads a bounded Active Context Bundle. A formed Entity 360 is an optional\nderived member of that bundle, not its sole permissible input.\n\n## Information boundaries\n\nEvidence, signals, events, state, proposals, knowledge, memory, and\nrelationships retain their own kinds. They are not silently promoted into a\ncanonical entity type or operational truth. Canonical entity formation and\ngoverned promotion preserve provenance and authority.\n\n## Supersedes\n\nThis contract supersedes:\n\n- fixed per-role Entity 360 navigation;\n- `Twin ONLY reads Entity360`;\n- global/sticky four-button controls;\n- role workbook `Role domain entity` classification;\n- direct browser database/provider reads;\n- independent donor app deployment; and\n- generic fallback to another projection when hostname resolution fails.\n"}