Understand / owner review Revision 05 · 78 states

The design package is ready to decide

One place to review what changes next.

Start with the interactive package. Then answer the eight decisions that block the Flutter port. The reports below hold the evidence when you need the detail.

Status

The review work is finished.

All five specialist reviews fed the synthesis. The package keeps the 78-state contract and records the decisions that still need your call.

78canonical states
13state groups
159transition rows
0new Flutter changes in this pass

Owner anchors

These rules are already locked into revision 05.

They came directly from your corrections. The synthesis does not reopen them.

01 / Reader transport

One play/pause control

The matter orb owns playback. It shows play when idle or paused and pause while playing or seeking. No second transport control is added.

02 / Voice sheet

Preview stays in Voice

Voice preview uses explicit "Preview voice" and "Stop preview" copy inside the Voice sheet. It never starts Reader playback.

03 / Reading surface

No banner over the text

Paused and seeking live in the dock through the glyph, position row, timecode, and status label. Reading text stays clear.

Start here

Revision 05, in the browser.

Walk the state package at full size. It is the visual source for this review, not a thumbnail summary.

Interactive state package · consolidated-state-package-05.html Open full preview

If the embedded view feels cramped, open the full preview. The earlier package revisions remain untouched.

Review order

Four passes. No scavenger hunt.

This order keeps visual reactions separate from product decisions.

Walk the package

Check Library, Reader, sheets, dialogs, recovery, and platform-owned states.

Check the anchors

Look for the single matter control, Voice-only preview, and clean reading text.

Choose D-1 to D-8

Use the selectors below to record your current decision in this browser.

Approve the port

After the decisions, the next work is tokens, components, Reader geometry, then device proof.

Owner decisions

Eight choices still shape the port.

These selectors are a private review aid. They save locally in this browser and do not send a decision anywhere.

D-1Needs decision

Model gate bypass

When no voice is installed, may the person browse the Library through "Not now" and "Keep browsing", or must the model gate block the flow?

D-2Needs decision

Premium surface state

Settings currently says Premium is unavailable in this build while the package shows live checkout. Which truth should the product show?

D-3Needs decision

Quiet token value

The pinned quiet color is only 2.64–2.80:1 on reading surfaces. Raise it to an accessible value, or make quiet decorative-only and keep wake for must-read text?

D-4Needs decision

Local rewrite setup

The roughly 600 MB on-device rewrite model has setup states that are folded into copy. Add explicit states, or keep the fold and name the inline setup state?

D-5Needs decision

Contents current-row accent

When the current sentence appears in Contents, should the row use live text, the spike accent, or both? The package and Flutter must match.

D-6Needs decision

Voice sheet close behavior

If a voice preview is playing and the person closes the sheet with Back or outside tap, should preview stop? Revision 05 assumes yes.

D-7Needs decision

Idle chrome fade

Confirm the five-second fade for secondary dock rows and reveal on tap or scroll, or change the timing before it becomes the port contract?

D-8Needs decision

Retelling settings action

If Retelling settings ships in this pass, its dirty, apply, cancel, and loading states need Flow proof. Otherwise, keep the affordance as a stub.

Evidence

Five reviews, each with a narrow job.

Open a report only when you want the line-level reasoning behind the package.

Hierarchy and large text

Checks the 78 states against the Ferrofluid composition and the Reader at large text.

Key findings. Matter glyph, dock inset, idle dock, overlay containment, and state-specific renderer gaps.

Transitions and feedback

Reviews how the experience hands attention from voice to chrome, sheets, progress, and recovery.

15 findings. Fixed first-play timer, dock reflow, live-region churn, non-frozen Hold, races, and reduced-motion gaps.
ACCESSIBILITYOpen report

Semantics and targets

Checks screen-reader order, labels, contrast, hit areas, text scaling, and recovery.

5 critical findings. Quiet contrast, Voice close label, Contents current state, small Retelling target, and small speed chips.
FLOW / COPYOpen report

Paths and plain language

Checks whether every state tells the truth about local, cloud, premium, privacy, and recovery.

Approval blockers. Model gate, cloud/local wording, local rewrite setup, replayable actions, and privacy copy.
DESIGN SYSTEMOpen report

Tokens and handoff

Checks whether the visual rules can become reusable components without geometry drift.

Main blockers. Component-token layer, modal normalization, package actions, and Reader geometry proof.

What happens next

The port starts only after these choices.

The next engineering pass is deliberately separate from this review package.

Included in the next approved pass

  • Apply the decisions above to the design contract and state package.
  • Port tokens, reusable components, and Reader geometry.
  • Prove the user story on a real device at narrow, wide, 2× text, screen reader, and reduced motion settings.
  • Keep the five reports as acceptance evidence.

Not included yet

  • No Flutter implementation from this synthesis.
  • No new state IDs without an owner decision.
  • No store, billing, release, or upload action.
  • The quiet color and model-gate choices are still yours to make.

Approval checklist

Leave this page with a clear handoff.

Selections and checks stay in this browser. They are a working review aid, not a substitute for the written decision.

0/8 decisions chosen · 0/8 reviewed

Source files

The contract is one click away.

These are the source documents used to build revision 05.

Fleet synthesis

The complete reconciliation, checks, unresolved decisions, and recommended next step.

Design contract

Ferrofluid roles, type, layout, motion, voice, and edge-case rules.