🎭 Three status demonstrations · sample progress only. These examples are independent of live work records.

Reusable handoffTASK 1CREATED 9/14/26UPDATED 9/14/26Next: Illustration: worker is handling the next step
Working
1 of 4 sample checks

Workflow stage

  1. Prepare
  2. Work
  3. Review
  4. Complete

Priority · High

Worker active

Purpose

Package reviewed patterns so future workers can reproduce them without private content.

Future operating direction: a Brain Buddy Design / Brand Builder role may have its own heartbeat to maintain Design Universes.

Reuse the shared Play·Packet and task template, with its own verified notes, update and review routes; do not connect it to Shadow’s runtime by assumption.

Role naming and schedule setup remain proposals, not active operations.

Steps & checks

Follow the actions. Mark a check only when its evidence is verified.

  • Complete: Review each implemented variant with evidence
  • Not complete: Document source lineage, behavior and adoption state
  • Not complete: Prepare public design-system changes as a separate scoped handoff
  • Not complete: Keep unpublished drafts and verified releases distinct

Handoff & success

OwnerBrain Buddy · scope owner

Depends onConnection categories, Themed foam interactions, Message and voice examples, Accuracy and questionnaire patterns

Done whenA preparation-only handoff contains exact sources, context, boundaries, dependencies, output and acceptance route. After implementation, separate evidence identifies verified variants; private content is excluded from reusable release.

Reference mapping in Sources · Prepared brief

Illustrative state · sample checks and outcomes, not live task evidence.
Accuracy and questionnaire patternsTASK 2CREATED 9/14/26UPDATED 9/14/26Next: Your review: accept the result or request changes
Needs you
2 of 6 sample checks

Workflow stage

  1. Prepare
  2. Work
  3. Review
  4. Complete

Priority · Normal

Your review needed

Purpose

Reuse verified deck accuracy bars and organize survey/questionnaire choices by meaning.

Steps & checks

Follow the actions. Mark a check only when its evidence is verified.

  • Complete: Locate actual deck implementation and visual reference
  • Complete: Distinguish ratings, confidence, progress and completion
  • Not complete: Prepare named endpoints and meaningful input behavior
  • Not complete: Create scoped examples only after reference verification
  • Not complete: Verify narrow layout and keyboard controls
  • Not complete: Include one representative example plus a Tap for examples gallery for each selected family

Handoff & success

OwnerBrain Buddy · scope owner

Depends onReview area

Done whenRating/questionnaire families have one source-matched example and Tap for examples gallery. Named endpoints and stored user selection behave correctly; ratings are never presented as completion counts.

Reference mapping in Sources · Prepared brief

Illustrative state · sample checks and outcomes, not live task evidence.
Themed foam interactionsTASK 3CREATED 9/14/26UPDATED 9/14/26Saved: Illustration: accepted result is filed
Verified complete
5 of 5 sample checks

Workflow stage

  1. Prepare
  2. Work
  3. Review
  4. Complete

Priority · Low

Accepted · filed

Purpose

Keep sticker, handwritten label/count, hover cue and opened surface visually coherent.

Steps & checks

Follow the actions. Mark a check only when its evidence is verified.

  • Complete: Use exact foam material and distinct subtle tilts
  • Complete: Chalkduster themed label and gray Chalkduster count
  • Complete: Theme-matched hover cue describing the actual action
  • Complete: Click-toggle full surface, trigger-origin reveal, Escape and keyboard support
  • Complete: Preserve paper variants, colored emphasis, spacing and all information

Handoff & success

OwnerBrain Buddy · scope owner

Depends onReview area

Done whenPointer and keyboard checks show matching themed hint, handwritten colored label, gray count, click-open/click-close and Escape. The full surface preserves content and readable contrast; reduced motion works.

Reference mapping in Sources · Prepared brief

Illustrative state · sample checks and outcomes, not live task evidence.
🗝️ Status key
Up next

The next prepared priority; not a running task.

To prepare

Preparation is still required.

Not connected

A required connection does not exist yet.

To build + test

Implementation and observed verification remain.

Waiting on connection

Another piece must be connected first.

Waiting on prerequisite

A named prerequisite must be resolved.

After the proof

This follows the readiness proof.

Not started

Saved in the queue; no execution evidence yet.

Checks underway

Some checks are verified; it does not establish live activity.

Verified complete

All checks for the stated item are verified.

Working

Reserved for an observed active run with fresh evidence.

Paused

An intentional pause with a recorded resume condition.

Needs you

A normal handoff waiting for your input or review; not a failure.

Ready for review

A result returned; acceptance is still separate.

📡 Activity lights
Working / return received

Read the gray caption: working is active; received or reviewed means the output came back.

Queued / paused

Waiting to start or temporarily paused.

On hold / needs your input

A normal wait for your input, review or support, or a deliberate hold. The caption explains what is needed.

Stopped / problem to fix

Work stopped because of a problem. The caption explains the issue and recovery action; ordinary review is not a red state.

Checks documented

Saved checklist evidence exists; this is not live activity.

Not connected / unavailable

No reliable current activity signal. No activity is inferred.

Accepted and complete

The pale-gold-to-green glow marks verified completion, distinct from steady green working. A returned result still needs acceptance. Reduced motion uses a steady completion light.

🧭 Stages & numbers

Prepare → Work → Review → Complete is the shared overview in this template. Each task has its own detailed steps; stages can be revisited. A different workflow can be defined when the task calls for it, with its own clear key.

The fraction counts documented checks out of all checks. It does not identify a workflow stage or prove a worker is active. Status explains the situation; the light describes the activity caption beside it. A returned result still needs acceptance. Ready for review means a result is waiting; name its reviewer. An agent actively reviewing uses an active caption naming that agent. Needs you means your decision is required. Review is the workflow stage in both cases.

These three examples deliberately show different illustrative states. Their numbers and lights are demonstrations, not the live work queue.

🎯 Priority key

Urgent

Time-critical: needs an explicit reason or deadline.

High

Important to move forward soon.

Normal

Standard planned work.

Low

Useful when higher priorities allow.

Not set

No priority assigned; never infer it from the task number.

Priority is importance, not progress or activity. Dependencies and authorization still determine what can run. Task numbers identify cards; they are not priority rankings.