How to enable your twin

Open the twin panel

On the program home, the Twin panel sits under “Decisions waiting for you”. With no twin it offers Set up your twin, which opens /p/<slug>/twin. If a phase-2 schedule of yours was moved here by the migration, the panel already shows a twin paused with “Paused: a schedule from phase 2 was moved to your twin; review it and resume”; continue with the same steps.

Step 1: what your twin will do

The persona’s default duties appear as cards, each naming its tools, the permission every tool exercises and, where knowledge.fetch_document is used, the fetch cap you can lower (“Documents fetched per pass”, default 10). A duty whose permission you lack is disabled and names the key (“Needs review.sops.manage”). Untick any duty you do not want. For a scientist the defaults are the weekly literature watch, notebook follow-through, draft readiness, report scaffold, gap hygiene and information hand-offs to the lead; for a quality reviewer SOP watch, hand-off intake, check triage and the requirement-set queue (about personas and twins).

Step 2: when

Set the brief time (digest_time), the batch times, quiet hours and the proposal expiry (default 72 h). Quiet hours hold delivery, not the record: a proposal filed at night is in your inbox at once and in your e-mail after the window. One person, one clock: the time zone is users.settings.timezone.

Step 3: what it never does

The three fixed sentences, then one standing-plan approval per enabled duty. Choosing Enable calls POST /programs/{program_id}/twins with TwinCreate {persona_key, duties, expiry_hours, digest_time, batch_times}; the API creates the twin, audits twin.create, and enqueues one planning-only twin_cycle (input.phase = standing_plan) per duty. Each plan arrives on this screen as a detached plan_approval naming the tools, sources, expected writes, budget.tool_calls, max_proposals_per_cycle, max_fetches_per_cycle and cadence. Read it and choose Approve; the audit row records permission_exercised = program.twins.use, the plan is copied to the trigger (standing_plan_json, standing_plan_hash) and the duty becomes enabled. A duty without an approved plan does not run.

Read the panel

“Your twin · scientist · active · last pass 07:10 · next 12:00 · 3 proposals waiting” with Pause, Run now and Duties, and the transparency line “0 record writes without your approval. This week: 14 reads, 8 documents fetched, 6 proposals, 4 accepted, 1 edited, 1 declined, 1 brief written (agent-generated, unsigned).” The counts are computed from records and link to the runs. Every twin run’s footer reads “Started by schedule, event, hand-off or you under <Name>’s standing plan (approved <date>, plan <hash prefix>)”.