{"slug":"spine/projection-context-assembly","title":"20 · Projection & Context Assembly","section":"spine","sectionLabel":"Spine","status":"unclassified","type":"document","path":"spine/projection-context-assembly.mdx","bytes":3377,"description":"One business reality → different participant projections. Projection Engine, contracts, Active Context Bundle — how context assembly and relevance work.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## One Business Reality → Different Participant Projections\n\n```text\n                 BUSINESS CONTEXT SPINE\n                      │\n          ┌───────────┴───────────┐\n          ▼                       ▼\n    HUMAN PROJECTION          AI PROJECTION\n          │                       │\n    Human Workbench          AI Workbench\n          │                       │\n  Personal Contextual      AI Continuity\n      Memory (serves BC)     Memory (serves BC)\n          │                       │\n          └───────────┬───────────┘\n                      ▼\n                Shared Work\n          (same reality, scoped view)\n```\n\n\nHumans and AI share the same Business Context Spine. They do not share the same projection. Twin never needs to re-explain the business because it hydrates the same Work + Spine slice as the human.\n\n\n## Active Context Bundle\n\nThe Workbench and the AI Workbench hydrate from the same **Active Context Bundle**:\n\n* **Business Context slice** — the relevant entities, relationships, and state for this Work and participant\n* **Work** — objective, state, participants, and history\n* **Evidence** — what has already been proven to have happened\n* **Authority** — what this participant may do in this context\n* **Continuity** — personal or AI working memory relevant to this Work\n\n## How Assembly Works\n\n\n  \n    Human opens Work or Twin receives Work — both request the Active Context Bundle for that Work and identity.\n  \n  \n    The engine selects the governed slice of the Spine for this participant, tenant, and Work context — per projection contracts and authority.\n  \n  \n    Additional contextual context is assembled (related Work, prior decisions, related entities) and ranked by relevance — not dumped as raw payloads.\n  \n  \n    Both workbenches hydrate from the resulting bundle. Handoffs carry Work state and evidence, not transcripts.\n  \n\n\n## Projection Contracts\n\nProjection is governed. Contracts define:\n\n* Which entities and fields are visible to which participant in which Work type\n* Which memory (Personal Contextual vs AI Continuity) contributes to the bundle and how\n* How provenance and evidence are surfaced vs kept internal\n* When projections invalidate and workbenches must rehydrate (after verify → reconcile → Spine)\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    Why two working memories serve one organizational memory — ownership, privacy, durability.\n  \n  \n    What the human actually experiences of this projection.\n  \n  \n    How the AI Workbench uses the same bundle.\n  \n</CardGroup>\n"}