Entity Context and Entity 360 Contract

Status: Normative human explanation backed by
total-end-state-contract.json.

Live Entity is not Entity 360

A Live Entity may exist on day one after one canonical identity is resolved. It
must disclose its lifecycle state, external identities, source provenance,
freshness or sync status, evidence, known relationships, and unresolved links.
It is not an Entity 360 merely because it is live.

Entity 360 is a derived, maturity-gated multi-entity projection. It requires at
least two distinct resolved related canonical entities and sufficient evidence.
It discloses coverage, freshness, provenance, confidence, uncertainty, missing
relationship classes, and unresolved links; it never manufactures completeness
from sample data.

Formation states

The only formation states are not_formed, forming, partial, formed, and
degraded. The first three return honest Entity Context without presenting an
Entity 360. formed may present a formed projection. degraded may present the
last formed projection only with explicit degraded and freshness metadata and
policy permission.

Twin reads a bounded Active Context Bundle. A formed Entity 360 is an optional
derived member of that bundle, not its sole permissible input.

Information boundaries

Evidence, signals, events, state, proposals, knowledge, memory, and
relationships retain their own kinds. They are not silently promoted into a
canonical entity type or operational truth. Canonical entity formation and
governed promotion preserve provenance and authority.

Supersedes

This contract supersedes:

• fixed per-role Entity 360 navigation;
• Twin ONLY reads Entity360;
• global/sticky four-button controls;
• role workbook Role domain entity classification;
• direct browser database/provider reads;
• independent donor app deployment; and
• generic fallback to another projection when hostname resolution fails.