sample-unit-writing-guide-sep25-1
Unit writing test
AI-generated working guide · not part of the reader sequence
This is a test of one idea, not a replacement master scaffold. Start with the reader's entrance; use this guide while comparing the actual pages.
What each unit does
Time · diary entry
The unit is an encounter with the project at a represented moment: an observation, discussion, attempt, uncertainty, recollection or several thoughts pressing on one another. It moves with time. It need not deliver a new insight or advance an argument.
In 9 February, programme, sensory ambition, material memory and uncertainty about methods coexist. Only the programme/return strand is followed in this sample. The other thoughts are not forced into that explanation.
Writing test: can I stay within this moment without explaining how everything will eventually turn out?
Time · chapter slice
The unit is an orientation across a meaningful interval. It gives the diary a temporal neighbourhood and shows what is in play. It does not stand in for the entries.
The three short slice notes here are sample groupings, not a decision about the year's chapter boundaries. An insight might motivate a boundary, but a diary does not have to earn its place by producing one.
Writing test: does this help me locate the following entries without pre-arguing their outcome?
Knowledge · review within a thread
A thread is the continuity or relationship I follow across occurrences. Its Knowledge note reviews material through an organising idea or theoretical question: distinctions, source analysis, situated interpretation, changing understanding, counterevidence and gaps. Material can include scholarship, testimony, feedback, observation or a made object.
The unit has a conceptual centre, not necessarily a single source or a single claim. It can argue about what its material establishes, but it does not announce a design decision. In this test the organising ideas are participation/omission and continuing relationship/different occasions. The reviewed material is largely diary, consultation, programme and feedback; a developed scholarly review has not been fabricated.
In ritual participation and choice, Aresh's account supports a local distinction about participation and sequence. That review result can be used by Story without being repeated. The dated sections are used because change matters here; they are not a mandatory miniature diary inside every Knowledge note.
Writing test: if I remove the dates, is there still a recognisable topic worth understanding? If a subsection only says what happened that day, link its diary occurrence instead.
Story · investigation
The unit is an argument about resolution, formed where reviewed ideas converge or overlap and a test gives me something to interpret. It may remain partial. A question alone can stay present as a trace until there is enough work to make an investigation worth reading. A test can produce contradiction or failure; it does not have to produce closure.
In the worked investigation, the additional work is the move from choice within a ritual process to relationships between ritual, memorial and grief care. A new sample reasoning test compares three hypothetical arrangements. It supports a conditional direction while leaving the spatial test outstanding. It is not a newly discovered historical experiment.
Writing test: what relation am I arguing here that is not already adequately argued in one existing Knowledge passage?
Maps and contents
These are views of the units. They do not require another body of explanatory prose. A Story contents item can point straight to a Knowledge passage when that passage already does the argumentative work.
An orientation is therefore not an instruction to write every idea three times.
Templates to copy and adapt
Prompts below are choices for composing, not compulsory paragraph headings or a sequence every entry must complete. The blank sample properties are deliberate; fill them when making another rehearsal.
Diary template
---
sample: true
authorship: specify writer
orientation: time
unit_type: diary
represented_date: fill in
written: fill in
source_keys: []
threads_present: []
thread_emphasis: []
reader_encounter: trace or substantial detour
---
### Date or represented period
A title that belongs to this moment
[What am I noticing, trying, reading, hearing, remembering or struggling with?]
[What else presses into this moment? What remains contradictory or uncertain?]
[What specific detail keeps this from becoming a summary of a theme?]
[Write the entry freely. I do not need to answer every prompt.]
---
[A thread may be present as an unlinked trace.]
[When a detour opens: name the topic, readable chunk and return point.]
[Continue in Time: the next dated entry or chapter.]
[Source basis for this rehearsal.]
Keep three chronologies in the working properties: the actual encounter, composition now, and the reader's placement. Writing composed now can belong beside an early moment and speak from within that moment. The reader does not need constant reminders that it was written later. A later state that would change what the early voice knows belongs in a separately identified layer. Do not invent a consultation, reading, quotation or completed experiment to fill a gap.
Knowledge template
---
sample: true
authorship: specify writer
orientation: knowledge
unit_type: thread-review
written: fill in
source_keys: []
---
### Topic
[What is the particular concern I can follow here? What falls outside it?]
[Entry points if this note holds materially different states.]
#### A distinction that matters
[What does the source, experience, drawing or observation actually support?]
[What is my interpretation? What does it not establish?]
[What alternative, tension or counterexample must remain visible?]
#### A changed relation, if there is one
[What changed, persisted or became more specific?]
[Link the time occurrence; do not repeat its whole scene.]
#### Current reading
[What can I argue locally? What other thread changes its meaning?]
[Am I reviewing what the material supports, or announcing a project decision?]
[What research or design work is genuinely unresolved?]
---
[Return to the specific diary entry points.]
[Cross to a related thread, with the relation named.]
[Link to any Story investigation that uses this material.]
Use the structure demanded by the topic. Several dated states, one close source analysis, or a comparison may be appropriate. Every thread need not have the same internal shape.
Story template
---
sample: true
authorship: specify writer
orientation: story
unit_type: investigation
written: fill in
source_keys: []
---
### A question or provisional claim
[What am I trying to establish, and within what scope?]
[Bring the necessary material into relation. Give enough substance here
for the argument to be understood; link the full analysis in Knowledge.]
[Show the relevant test or comparison and its result, including failure
or incompleteness. Distinguish a new sample test from historical work.]
[Explain the inference. Why does that result warrant this relation,
and where might it fail?]
[What becomes consequential for the architectural proposition?]
[What remains a question, and what evidence or test would change my view?]
---
[Linked Knowledge passages.]
[Relevant Time occurrences.]
[Return to working Story contents.]
A link cannot replace the reasoning required to follow this page. A short restatement of essential evidence is useful; copying the full source analysis into both notes usually is not.
Where the same material goes
Aresh's optional antechamber is the overlap test.
- Diary: the encounter with a specific room and the route past it; why that detail catches my attention amid other operational matters.
- Knowledge: the account, its limits and the local argument about providing for different participation.
- Story: a short statement of that result, used alongside return and simultaneous use to argue about relationships between programmes.
The full consultation analysis has one home. The Story contents also links directly to its Knowledge passage as supporting material. That link does not turn the review into a second Story unit. The consultation alone does not resolve my project's arrangement.
Return creates the second test. The memorial thread can investigate different occasions, quiet and gathering without accepting the whole sanctuary argument. Story draws a particular relation between that thread and ritual participation. Keeping these units distinct makes the added inference inspectable.
For this sample, I would retain two Knowledge reviews and one cross-thread Story investigation. Shared evidence has one home, while review and resolution remain distinguishable writing jobs. If the Story page merely restates the review, it has not earned its existence. Here its added work is the comparison of programme arrangements and the conditional project direction. This is a result to test on the page, not a final rule for every topic.
Reader encounters
The primary forward action on a diary page is always “Continue in Time”.
Presence comes before navigation. February shows unlinked thread traces; May opens the first substantial ritual review; July opens the return review while witnessing remains a trace; August opens an expanded reading across their relation. The properties record presence and editorial estimates of emphasis without making every present thread an immediate destination.
When a thread link opens, it says where it lands and what chunk is worth reading. A local return follows that chunk. Later material is labelled. Scrolling onward is an explicit choice to read ahead.
A reader can also choose a current-state or Story route from the opening maps. That reader has chosen synthesis before emergence; the diary is not rewritten to accommodate that choice.
Return links list actual entry points. Plain Markdown has no reliable automatic memory of the reader's origin. Obsidian's back command is useful, but named returns also remain available. A thread reader can continue across Knowledge rather than being compelled back to Time.
There is one physical home for the full thread text at the back. A PDF page order would not need to follow every link. The separate layout file makes that distinction explicit without selecting a publishing platform.
What to notice when reading the test
Read the five diary entries without leaving Time. Notice that the early traces do not demand a detour. Then revisit May and take its newly opened thread link. Finally, enter from the Story map and work backwards.
Notice where the writing helps you distinguish an encounter, a developed question and an argued relation. Notice where those distinctions feel artificial, where the dated Knowledge sections repeat the diary, and whether the Story inference adds enough to earn its own note.
This sample tests programme and encounter. It does not establish that the same split will suit an affective, material or situated thread. Nor does working navigation by itself demonstrate the thesis's rhizomatic method.
