Unclassified

06 — Contextual Twin and Four Buttons

Product rule

Twin appears only where work is happening. It is not a large autonomous chatbot attached to every page.

Twin may detect, predict, explain, prepare, and present. It may not execute autonomously, write canonical truth, approve itself, or change a source system without explicit user approval.

Contextual signal

A Twin signal is a small, dismissible next-action prompt inside the active work surface.

Example:

Twin noticed a possible next action
Prepare the recovery plan for Thursday?

[Ask your Twin] [Assign your Twin] [Dismiss]

Trigger scenarios

FinanceFlow

The user opens FinanceFlow, reads Aisha's email, and inspects two P1 tickets.

Twin may surface:

Prepare the recovery plan for Thursday?

Repeated meeting follow-up

The user repeatedly creates the same task set after meetings.

Twin may surface:

You usually create this follow-up after customer meetings. Prepare the task set?

Account-risk preparation

The user reviews account risk, opens linked documents, and schedules a meeting.

Twin may surface:

Prepare a meeting brief with the account risk and linked evidence?

Missing follow-through

The user changes a record and pauses.

Twin may surface:

Store this observation in Spine?
Draft the customer update?

The Four Buttons

Store in Spine

Meaning: prepare a governed proposal to capture truth.

UI sequence:

  1. Open proposal drawer.
  2. Show proposed content and evidence.
  3. Allow edits.
  4. Mark as awaiting approval.
  5. Allow explicit approval or rejection.
  6. Display simulated completion only; do not claim a real canonical write.

Ask your Twin

Meaning: reason over the active work context.

UI sequence:

  1. Open contextual drawer.
  2. Show included context and evidence.
  3. Accept a question.
  4. Return a deterministic local response.
  5. Offer relevant next actions.

Assign your Twin

Meaning: prepare a draft or bounded workflow.

UI sequence:

  1. Show assignment, context, expected output, and limits.
  2. Create a local prepared run.
  3. Show the draft result.
  4. Require approval before any represented action.

Approve Twin's Action

Meaning: authorize a prepared governed proposal.

UI sequence:

  1. Show target, proposed change, evidence, and risk.
  2. Require explicit confirmation.
  3. Move the local proposal to approved.
  4. Optionally show simulated completion.
  5. Never call a real external system in this frontend increment.

Proposal state machine

Suggested
→ Prepared
→ Awaiting approval
→ Approved or rejected
→ Simulated complete

export type ProposalStatus =
  | "suggested"
  | "prepared"
  | "awaiting_approval"
  | "approved"
  | "rejected"
  | "simulated_complete";

Placement rules

Twin signals may appear:

  • Near a selected account, ticket, task, email, document, or meeting
  • Inside a detail drawer
  • At the end of a meaningful sequence of user actions
  • Beside missing follow-through

Twin signals must not appear as unrelated dashboard decoration.

Approval law

Twin may explain an approval and prepare revisions. Twin may not approve its own action.