sample-page-layouts-guide-sep25-1
Page layouts for the sample
AI-generated composition test · separate from the reader's notes
These are proposed page compositions, not a rendered PDF or fixed pagination. The existing folio identifiers are retained to make the revision easy to compare. The fuller Knowledge writing and newly shortened Story require fresh pagination; the old page allocations are not evidence of fit. This file is an unrendered layout record, not the current text to read. P18–P19 are retired from the reading sequence because they previously held the production ledger.
The sample compresses cover, how-to-read and justification into P01. It does not invent administrative pages. After that, the sample follows the existing proposed order: opening maps; timeline chapters and diary; timeline cut; current Knowledge map; provisional Story; working contents; full Knowledge Topic Threads. The production ledger is outside the reader route.
The writing guide and this layout file sit outside that sequence. YAML and workbench links are production information, not part of the composed page.
The difference this layout tests
Information architecture: five daily entries use diary tone; two provisional Topic Threads contain academic Knowledge writing; the existing Story investigation remains available for comparison. Maps provide different views. The Knowledge/Story boundary and the rules of Threads remain unresolved.
Reading order: a reader can follow P01–P17, then P20–P23. Early thread presence does not automatically open a detour. At P09, a fuller ritual reading becomes available: the reader can leave for P20, return to P09, and carry on at P10. The full thread discussions remain at P20–P23 in this unrendered plan. Their evidence and references are self-contained. Necessary evidence also appears within Story so that links do not carry missing premises.
Note and page are different units: the earlier plan allocated one page to each chapter slice and diary, and two pages to each Knowledge note and to Story. These allocations now require checking against the revised text. The short timeline strip on diary pages is a repeated view of the chapter context, not another Knowledge note.
Page frames
Diary frame
Used on P06, P07, P09, P11 and P12.
┌────────────────────────────────────────────────────┐
│ TIME · represented date chapter │
├──────────────┬─────────────────────────────────────┤
│ year strip │ entry title │
│ current │ │
│ chapter │ first-person diary │
│ exposed │ │
│ │ pauses and paragraph breaks stay │
│ week strip │ visible; no “therefore” box added │
│ entry day │ │
│ marked │ │
├──────────────┴─────────────────────────────────────┤
│ Thread trace OR read [thread + named chunk] │
│ short source citation Continue in Time → │
└────────────────────────────────────────────────────┘
The timeline occupies roughly a quarter of the proposed page width; diary text occupies the remainder. Where present, a retrospective reflection sits at the bottom, separately labelled after the main entry and navigation. This is a compositional proposal, not a commitment to dimensions. A plain thread name can register presence without becoming a link. When a detour opens, its action stays separate from “Continue in Time”.
Knowledge frame
Used on P20–P23.
┌────────────────────────────────────────────────────┐
│ KNOWLEDGE · topic state entry points │
├────────────────────────────────────────────────────┤
│ topic section / source account │
│ interpretation and limit │
│ [Return to the dated encounter] │
│ │
│ related topic section │
│ analysis, qualifications and local references │
│ [Return to its dated encounter] │
├────────────────────────────────────────────────────┤
│ related thread · Story use · current map │
└────────────────────────────────────────────────────┘
The return follows the relevant topic discussion. On a continuation page, repeat the topic title. Dates identify evidence and its context; the academic writing is organised by the subject rather than a sequence of diary states. Sources must remain available with the discussion.
Story frame
Used on P15–P16.
┌────────────────────────────────────────────────────┐
│ STORY · working question │
├────────────────────────────────────────────────────┤
│ proposition and scope │
│ │
│ necessary evidence from connected threads │
│ reasoning that connects it │
│ │
│ tension / objection │
│ consequence and test still required │
├────────────────────────────────────────────────────┤
│ inspect Knowledge · return to Time · Story contents │
└────────────────────────────────────────────────────┘
Story carries its reasoning on the page. Links offer the fuller analysis. Its open design test is part of the argument's limit, not an empty promise of a resolved final chapter.
Opening pages
P01 · sample entrance
Vault note: sample-reading-entry-guide-sep25-1.
Top: project title and the sample idea. Middle: diary-led reading premise and the three orientations. Bottom: visible sample status and “Begin with the Time map”. Explain that the Knowledge/Story boundary remains under review.
Keep the two workbench links available in the vault note but outside the proposed reader page. No institutional front matter is simulated.
P02 · Time map
Vault note: time-orientation-map-sample-sep25-1.
Top: Time and the forward-reading question. Centre: full selected timeline graphic, then the chapter and dated-entry links. Bottom: scope of the gaps; next opening map.
Each chapter name links to its slice page, not to a Story chapter. Each date can also enter the diary directly.
P03 · Knowledge map
Vault note: knowledge-orientation-map-sample-sep25-1.
Top: Knowledge and its relational question. Centre: two thread clusters joined through the unresolved question of encounter. Below: what each thread contains and how it affects the other. Bottom: next opening map.
The linked cluster names enter the full Knowledge topics at P20 and P22. This is a deliberate invitation to read a thread across time, not a concealed jump into the future.
P04 · Story map
Vault note: story-orientation-map-sample-sep25-1.
Top: Story as a current backward reading. Centre: local argument; cross-thread investigation; unresolved architectural test. Bottom: begin the diary.
The supporting item links to the academic discussion of ritual provision and omission. The existing separate Story note remains a provisional comparison. This arrangement does not establish an exclusive division between review and resolution.
Time pages
P05 · February slice
Vault note: february-opening-questions-slice-sep25-1.
Upper half: year strip with February exposed; 8–9 February within it. Lower half: what is simultaneously in play, followed by “Enter 8 February”. Foot: whole timeline and explicitly labelled next-chapter shortcut.
This is a temporal grouping, not a claim that all February work concerns this idea.
P06 · 8 February diary
Vault note: february-many-locations-diary-sep25-1.
Use the diary frame. Week strip: 2–8 February, with the 8th marked.
Main text: unfamiliar places; meaningful journey; ashes; private/shared remembrance. Thread traces: ritual participation and choice; memory and return. Print their names without hyperlinks. Their presence is also recorded in the note properties. Forward action: 9 February, P07.
The first branches register here, but their larger readings are not opened yet. The reader can feel the questions accumulate without having to leave the entry.
P07 · 9 February diary
Vault note: february-competing-possibilities-diary-sep25-1.
Use the diary frame. Week strip: 9–15 February, with the 9th marked.
Main text: hybrid programme alongside feeling, methods, material memory and absent site knowledge. Thread trace: memory and return, still without a detour. Forward action: May slice, P08, with the intervening work explicitly outside this sample. At the bottom, place the separately labelled retrospective reflection copied from Parishka's existing annotation.
The material/method questions remain visible as unexpanded branches. Do not convert them into supporting bullets for the journey argument.
P08 · May slice
Vault note: may-operational-encounters-slice-sep25-1.
Upper half: May exposed in the year strip, with 26 May located. Lower half: operational specificity and uneven knowledge across programmes. Foot: enter 26 May; timeline; adjacent chapter links.
P09 · 26 May diary
Vault note: may-optional-ritual-diary-sep25-1.
Use the diary frame. Week strip: 25–31 May, with the 26th marked.
Main text: antechamber and alternative route; family, body and staff movements; maintenance and support. First substantial detour: ritual provision, omission and collection access in Knowledge, P20, with evidence, analysis and source attribution. Forward action: July–August slice, P10.
The entry contains the antechamber detail itself. The reader need not leave the diary to understand what caught my attention.
P10 · July–August slice
Vault note: july-august-coexistence-slice-sep25-1.
Upper half: July–August exposed, with 1 July and 30 August marked. Lower half: the three programmes and questions about their encounter. Foot: enter July; timeline; previous slice.
P11 · 1 July diary
Vault note: july-returning-visitors-diary-sep25-1.
Use the diary frame. Week strip: 29 June–5 July, with 1 July marked.
Main text: witnessing, protection, return, gathering and quiet. Detour: gathering, individual remembrance and grief care at P22. Witnessing and protection remain a plain thread trace on this page. Forward action: 30 August, P12.
Keep the contradiction between exposure and protection within the diary body. Do not resolve it through a margin summary.
P12 · 30 August diary
Vault note: august-connected-programmes-diary-sep25-1.
Use the diary frame. Week strip: 24–30 August, with the 30th marked.
Main text: Alex's question; connection/dependence; privacy/agency; wayfinding and atmosphere as branching work; uneven research. Expanded detour: simultaneous use and access in memory, return and coexistence, P23. That reading can cross into witnessing, visibility and exposure at P21. The forming Story question is present on the diary page but not yet linked from it. Forward action: the current cut, P13.
The ending is a question to draw through. There is no completed solution diagram.
P13 · timeline cut
Vault note: timeline-current-cut-sample-sep25-1.
Top: the selected timeline reaches its edge. Middle: what has become more specific, what persists and what is still entangled. Bottom: current Knowledge map; optional return to a thread or Time.
The cut does not claim August is the end of Part One or the year. It marks the edge of this selection.
Current reading and Story
P14 · current Knowledge map
Vault note: knowledge-current-state-sample-sep25-1.
Top: the selected temporal coverage. Centre: updated relationships between choice, return, privacy and exposure. Below: uneven evidence and the linking question. Bottom: enter the Story investigation, P15.
Compared with P03, this map states what the encounters allow me to relate. It does not turn the topics into a final hierarchy.
P15 · Story investigation, first page
Vault note: story-connected-programmes-investigation-sep25-1.
Use the Story frame. Include the question, short proposition, two brief Knowledge embeds and proposed arrangement. Keep the question visually available beside the optional deeper readings. The full source discussions remain in Knowledge.
Forward page turn continues the same note at P16.
P16 · Story investigation, continued
Same vault note, from Proposed arrangement.
Top: repeated working question, marked continued. Middle: the concise proposed arrangement and the condition that would challenge it. The previous full comparison has been shortened. AI authorship and the exercise status remain in the entrance and production properties. Lower part: local references and exact reading routes. The current short Story may not require two pages; this allocation is unverified. Foot: Knowledge sources; Time occurrences; working contents, P17.
These two pages form one investigation unit. They are not two chapters or two new insights.
P17 · working Story contents
Vault note: story-working-contents-sample-sep25-1.
Top and centre: contents diagram with its unresolved branch. Below: links to the two Knowledge passages, the cross-thread argument and its test. Bottom: first Knowledge Topic Thread, P20. The production ledger is not in the reading sequence.
The contents remains partial. Its first two substantive destinations are Knowledge passages at the back, not newly duplicated Story essays.
Full thread destinations
The former P18–P19 source-ledger pages have been withdrawn from the reader route. The ledger remains available as production provenance. Source substance, citations and reference details now belong on the relevant reading pages.
P20 · ritual thread, first page
Vault note: ritual-participation-choice-thread-sep25-1.
Use the Knowledge frame. Include topic scope, the literature on participation and recognition, consolidation and journey, ritual provision and omission, and collection access. Place the February return after the journey discussion and the May return after collection access.
This is the first detour destination from P09 and a supporting destination from the Story maps. The journey discussion remains accessible here, with a return to its February diary occurrence.
P21 · ritual thread, continued
Same vault note, from July · witnessing and exposure.
Include witnessing, visibility and exposure; the scope of evidence; local sources; and return links. Cross-link to simultaneous use and access at P23 and the provisional Story investigation at P15. Physical continuation: the memory/return thread begins on P22.
P22 · memory and return, first page
Vault note: memory-return-coexistence-thread-sep25-1.
Use the Knowledge frame. Include scope, the literature on continuing relationships and coping, return beyond the funeral, gathering and individual remembrance, and grief care. Keep the corresponding February and July return links beside the relevant discussions.
P11 opens the discussion of gathering, individual remembrance and grief care. Return beyond the funeral remains available to readers following the whole topic from the Knowledge map, with links to P06/P07.
P23 · memory and return, continued
Same vault note, from August · the pressure of simultaneous use.
Include simultaneous use and access, the limits of the evidence, sources and return links. The topic's fuller account remains available even if the reader never reads Story. End with cross-thread, current-map and Time options, not an instruction to accept a final argument.
Routes to rehearse
Forward only: P01–P04 opening maps; P05–P13 Time. The chronological reading should remain intelligible without taking a detour.
A local deepening: P09 → ritual provision and collection access at P20 → embedded departure cue and exact return to the reading choice at P09 → P10. Further reading reaches witnessing and exposure at P21. How later understanding is signalled to an early reader remains under review.
Across a thread: choose Knowledge at P03 → return beyond the funeral at P22 → gathering and grief care at P22 → simultaneous use at P23 → witnessing and exposure at P21. This alternative map route can enter the whole field early. It does not change the staged availability of detours along Time.
Backward argument: P04 → P15–P16 → simultaneous-use discussion at P23 → its dated encounter at P12. The argument is a route back through the material, not a replacement order for Time.
Overlap test: P04 or P17 → ritual provision and omission at P20. Compare this academic discussion with the proposed argument at P15–P16. Whether both need separate units remains unresolved.
These are alternative traversals of the same notes. The test is whether the different encounters remain distinct and useful, not whether every reader follows every route.
