Unclassified

Workbench Interaction Contract

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

Contextual controls

The Workbench provides the four OODA controls—Store in Spine, Ask your
Twin
, Assign your Twin, and Approve Twin's Action—in a contextual
interaction slot at the relevant section, object, selection, or canvas block.
They are not global navigation, sticky footer controls, or a persistent Twin
panel. Twin remains silent unless the context has material value or a person
engages it.

Approval is a governed decision

Approve Twin's Action appears only for a concrete pending governed proposal
or action and only when the current person has matching authority. A click,
confidence score, selected entity, or general Twin recommendation does not
grant authority. Without a pending proposal and matching authority, approval is
not rendered and no external mutation occurs.

The full write path is:

Browser or Twin → governed command → Capability Fabric → owning integration or host
→ reconciliation → Spine

Capabilities, tools, integrations, and actions stay distinct along this path.
Host credentials never leave their host boundary, and the Workbench does not
make direct provider or database reads.

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.