Shows one page of the app being specified as a mockument: the twenty-two blocks of the specification beside a mock frame the reader can walk. A person opens it to see what a page will do and to find out what is not yet decided about it. They leave knowing which questions are open and who owes each answer.
No mock yet. The frame is rendered from the blocks around it.
Structure only, example data, nothing here is proof.
| ID | Element | Shows | Comes from | Status | Traces to |
|---|---|---|---|---|---|
| EL-01 | Page header | Name, route, build status, version, date, owner, the three readiness gates, and the share of elements that are actually required | the page record | required | §15 block 1 |
| EL-02 | Represents | The process and step this page belongs to, and the device types it covers, as links into the app map | the page record | required | §15 block 2 |
| EL-03 | Available to | Every role that may reach the page, what differs between them, and what each must not see | the page record | required | §15 block 3 |
| EL-04 | Purpose | Three or four sentences: what work this supports, why somebody opens it, what they leave with | the page record | required | §15 block 4 |
| EL-05 | The mock frame | The navigable representation, with four controls above it and an inspector that opens when any element is clicked | rendered from the blocks around it | required | §15 block 5, §16 |
| EL-06 | Fidelity note | One standing line: structure only, example data, nothing here is proof | fixed text | required | §15 block 6 |
| EL-07 | Elements | ID, element, what it shows or accepts, where it comes from, status, and what it traces to | the page record | required | §15 block 7 |
| EL-08 | Controls and actions | ID, control, business effect, whether it needs information only the server holds, where it leads, what confirmation or undo exists, status | the page record | required | §15 block 8 |
| EL-09 | Data and fields | Field, meaning, one value or a list, unit, what it is as of, when a user can see it, where it comes from, how it is calculated and from what, and the sample value used in the mock | the page record | required | §15 block 9, Part 5 |
| EL-10 | Lists | Per list: order, filtering and grouping, whether items can be selected and what then happens, nesting depth, and per device what appears when the list holds nothing, one item, or more than fits | the step this page represents | required | §15 block 10 |
| EL-11 | States | Default, empty, one item, more than fits, loading, error, restricted: when each happens, what the person sees, and what they can do next | the page record | required | §15 block 11 |
| EL-12 | What can go wrong | Described as the person notices it, never as a cause; what should happen; who is told | the page record | required | §15 block 12 |
| EL-13 | Remembered between visits | What the app remembers about this person, for how long, and whether they can clear it | the page record | required | §15 block 13 |
| EL-14 | Changes while being looked at | What may update under the person's eyes, how they are told, and what happens if they are mid-action | the page record | required | §15 block 14 |
| EL-15 | Connections | Where a person arrives from, where they can go, and which shared components this page uses, rendered as links | not answered | unanswered | §15 block 15 |
| EL-16 | Workflows | The named pieces of work this page takes part in, and where in each it sits | not answered | unanswered | §15 block 16 |
| EL-17 | Copy register | Every user-visible string, each marked required wording or placeholder | the page record | required | §15 block 17 |
| EL-18 | Decisions | What was decided, by whom, on what date | the page record | required | §15 block 18 |
| EL-19 | Observations | What walking through revealed, explicitly not decisions and not requirements | the page record | required | §15 block 19 |
| EL-20 | Open questions | Question, why it matters, what it blocks, who must answer, needed by | the page record | required | §15 block 20 |
| EL-21 | Out of scope | What this page deliberately does not answer, plus the standing list from §13 | the page record | required | §15 block 21 |
| EL-22 | Build contract and machine-readable record | What to build, what not to invent, what to ask about first, what done means, and the structured record the checker validates | the page record | required | §15 block 22 |
| ID | Control | Effect | Server only | Leads to | Confirm or undo | Status |
|---|---|---|---|---|---|---|
| CTL-01 | Device type | alters the screen | False | the same page rendered for the chosen device | switch back | required |
| CTL-02 | Role | alters the screen | False | the same page with elements hidden or revealed per the permissions block | switch back | required |
| CTL-03 | State | alters the screen | False | the chosen state's sketch, or a quote of what the specification says should happen | switch back | required |
| CTL-04 | Honesty overlay | alters the screen | False | every element tinted by its status | switch off | required |
| CTL-05 | Inspector | alters the screen | False | the clicked element's full record, or a plain statement that it has none | close | required |
Held on the step, not on the page: how a list is ordered, filtered and grouped is business meaning that does not change between devices. Look at the step named in block 2.
not answered · owed by Vincent
not answered · owed by Vincent
§15 requires where a person arrives from, where they can go, and which shared components this page uses. §30's schema cannot hold it: page_spec has no property for connections, so no record can carry it and no gate can compute it.
§15 requires the named pieces of work this page takes part in, and where in each it sits. §30's schema cannot hold it: page_spec has no property for workflows, so no record can carry it and no gate can compute it.
| Key | String | Status |
|---|---|---|
| fidelity | Structure only, example data, nothing here is proof. | required |
Observations are not decisions and not requirements.
not answered| ID | Question | Why it matters | Blocks | Who must answer | Needed by | |
|---|---|---|---|---|---|---|
| Q-01 | Who may reach this page, and what differs between them? | Gate 2 will not pass without it, and the role control has nothing to switch between | CTL-02 and gate 2 | Vincent | not answered | blocks the build |
| Q-02 | What does this page show when the app has no pages yet, when a page record fails to load, and when the reader may not see it? | Gate 2 requires the empty, error and restricted states, and the state control has nothing to switch between | CTL-03 and gate 2 | Vincent | not answered | blocks the build |
| Q-03 | What can go wrong here as a reader would notice it, and what should happen? | Gate 2 requires it, and it is the block users forget because it does not feel like work | gate 2 | Vincent | not answered | blocks the build |
| Q-04 | Which step of the method does this page represent, and what is its id? | Gate 1 turns on the page naming the step it represents | gate 1 | Vincent | not answered | blocks the build |
| Q-05 | Which device types must this page work on? | Section 14 warns that a step becoming twenty-six voice prompts means either the step is too big or voice is the wrong device for it | CTL-01 | Vincent | not answered | not answered |
| Q-06 | What does the app remember about a reader between visits, and what may change while they are looking? | Gate 3 requires both settled, and section 15 says these are asked directly because they are never volunteered | gate 3 | Vincent | not answered | not answered |
| Q-07 | Where should connections and workflows live, given section 30's schema has no property for either? | Two of the twenty-two blocks cannot be recorded, and gate 1's clause that the menu and the workflows navigate cannot be computed without them | EL-15, EL-16 and gate 1 | Vincent | not answered | blocks the build |
| What this page does not answer | Why |
|---|---|
| How page records are stored, fetched or cached | Section 22: architecture, storage and integration are untouched by the gates |
| Final visual design, typography, colour and density | Section 12 puts these out of scope unless the wording is itself a requirement |