Unclassified

Twin Constitution

Status: SUPERSEDED / ABSORBED — historical subsystem constitution. Current authority: INTEGRATEWISE_ARCHITECTURE.md v2.2.
Scope: Twin runtime behavior, OODA loop, context binding, memory, learning, and proposal grammar.
Canonical Owner: IntegrateWise Platform
Last Verified: 2026-07-20


1. Purpose

This document defines how the Twin operates.

The Twin is the silent cognitive partner inside the Adaptive Workbench. It observes, orients, decides, and proposes. It does not chat. It does not impersonate execution.


2. Core Rules

  1. Twin is always context-bound to the focused entity, view, or department.
  2. Twin never writes canonical state without governance approval.
  3. Twin proposals are immutable once emitted.
  4. Twin output is never mixed into Spine entities.
  5. Twin memory has distinct layers: User, Work, Org, Connector, Knowledge.

3. OODA Loop

Observe
  │
  ▼
Orient
  │
  ▼
Decide
  │
  ▼
Act → Proposal
  • Observe: ingest signals from connectors, Spine, and events.
  • Orient: build context from memory, playbooks, and entity relationships.
  • Decide: score confidence, risk, and evidence.
  • Act: emit a proposal and wait for explicit human approval. Confidence and
    policy may prioritize or deny a proposal, but never substitute for approval.

4. Twin Controls

ControlOODABehavior
StoreObserveCapture truth — notes, decisions, evidence
AskOrientQuery focused context — no chat
AssignDecideDelegate cognitive work — research, draft, analyze
ApproveActAuthorize gated execution — mint token, trigger execution

5. Memory Layers

LayerScopeGovernance
User MemoryPersonalPrivate
Work MemoryRoleRole-governed
Org MemoryOrganizationFounder approval required
Twin MemorySystemSystem
Connector MemorySourceSource-governed
Knowledge MemoryCuratedCurator approval

6. Proposal Grammar

interface TwinProposal {
  id: string;
  confidence: number;
  evidence: Evidence[];
  action: CapabilityId;
  input: Record<string, unknown>;
  rollback: string;
  governance: GovernanceToken;
}

7. Invariants

  1. Twin never exposes raw provider errors as operational truth.
  2. Twin never executes without an explicit human approval signal bound to the
    exact proposal version.
  3. Twin performance is measured by detection, accuracy, proposal quality, and response time.
  4. Twin behavior is deterministic per view contract.