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.

Current working understanding · 27 September

Confirmed in this conversation:

• Diary tone belongs exclusively to the timeline daily entries.
• Knowledge must provide rigorous academic depth. Relevant evidence and its attribution belong on the reading page; a source-ledger link cannot stand in for the writing.
• The sample must demonstrate fully developed academic writing with literature, alongside corresponding Story writing. A formal register without scholarly substance is insufficient for this test.
• Retrospective corrections can sit at the bottom of a diary entry, leaving the represented moment uninterrupted.
• All threads occur across time. Temporality does not distinguish a Thread from a question or investigation.
• Knowledge offers a topical orientation, like a visual glossary or index. Its readings are selected for project relevance; they are not required to be neutral article summaries.
• Reader navigation must preserve a recognisable departure passage and a precise return point. Dates alone do not carry enough context.

Provisional:

• The sample retains its Topic Thread labels for comparison. Whether one Thread should equal one Knowledge note remains unresolved.
• Threads run through the timeline. A slice may reveal the hierarchy of relevant threads at that moment. This does not establish one hierarchy for every orientation.
• The two existing topic groupings remain sample selections, not approved boundaries or aliases.
• The current trial gives Knowledge the fuller discussion and Story a substantially shorter project argument. Story embeds brief distinctions from their existing Knowledge passages instead of repeating the source discussion. Both remain interpretive; their exact boundary is still being tested.

Unresolved:

• What warrants a separate Thread rather than a related section; how a Thread, question and investigation differ in role. The supplied thesis thread field remains a set of candidates, not an approved set of publication units.
• How much project implication belongs inside Knowledge, and what additional work makes a passage Story.
• Whether Knowledge is organised by topic, reading or a combination, and how interpretation and argument are distributed.
• How a reader entering from an earlier date should encounter later knowledge.

Superseded as instructions:

• Knowledge written as a retrospective diary or as commentary about what a source ledger contains.
• The earlier revision relying only on primary project material, with scholarship deferred. It did not provide enough substance to evaluate the proposed difference in writing.
• The later trial giving Knowledge and Story near-equal density and repeated evidence. The user found the distinction insufficiently visible.
• The earlier guide's categorical restriction of Knowledge to review and Story to tested resolution. These are prior proposals, not governing rules.

What each unit currently tests

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 the main entry sustain the represented moment? A separately labelled retrospective reflection can sit at the bottom. The 9 February sample now demonstrates this with a short passage copied exactly from Parishka's existing reflection.

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. They identify relevant threads and selected emphasis without claiming to have established their full hierarchy. Their tone is orientating rather than diaristic.

Writing test: does this help me locate the following entries without pre-arguing their outcome?

Knowledge · Topic Thread, provisionally

The Knowledge note format remains useful for sustained academic treatment. Its equivalence to a whole Thread has not been established. The user accepts that all threads occur across time; that shared property does not resolve what deserves a separate note.

The revised notes engage six verified scholarly articles across the two topics. Ritual brings evidence about meaningful participation and social recognition into contact with a crematorium precedent and Aresh's account of operation. Memory considers continuing relationships, changing attention and the spatial dimensions of grief. Each note develops its analysis in prose and includes full references. These concepts are placed in relation without treating them as aliases.

The literature is incorporated into the sample's current academic reading. Its addition on 27 September does not establish that Parishka read it at an earlier timeline date. The references are real; the connecting analysis remains AI-composed sample writing. The production ledger records verification details outside the reader route.

This pass retains the existing two titles and their constituent terms for comparison. It does not establish that memory, return and coexistence must constitute one Thread, or that all threads should have the same shape.

Writing test: can the reader understand the topic, the relevant evidence, the reasoning and its limits on this page, without following a production link?

Story · existing investigation retained for comparison

The corresponding Story unit has been shortened to foreground the building question, the proposed arrangement and a condition that would challenge it. Two short block embeds reuse distinctions held in Knowledge; links open the precise supporting sections. One operational precedent is briefly restated because it is necessary to understand the proposed test. The argument remains AI-composed sample writing, not an approved project decision or a completed design experiment.

The prose advances the proposition directly, as a substantive academic passage. Its sample status sits in the entrance, properties and production record rather than repeatedly interrupting the argument. Its status as a separate Story unit remains provisional; the guide does not impose a ban on argument or design interpretation within Knowledge.

Writing test: what does this passage do, and does that work require a separate Story unit? That question remains open for Parishka's review.

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.]
[A concise source citation where needed, with its full reference available here.]

#### Retrospective reflection
[Optional later correction or reflection, after the main entry and navigation.
Keep its later viewpoint explicit; do not insert it into the immersive passage.]

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 correction can be included at the bottom of the same diary entry under a retrospective heading. Do not invent a consultation, reading, quotation or completed experiment to fill a gap.

Knowledge template

This is a provisional writing aid, not a definition of Thread boundaries.

---
sample: true
authorship: specify writer
orientation: knowledge
unit_type: topic-thread
unit_status: provisional
written: fill in
source_keys: []
---

### Topic Thread title
[Introduce the subject and scope in academic prose.]

#### A substantive distinction
[Present relevant source material fully enough to understand it here.
Attribute it, explain its context, compare where useful, and develop the analysis.]

#### A related problem or qualification
[Use the topic's needs to organise the discussion.
Retain differences and contradictions; distinguish evidence from inference.
Dates can identify source context without making this a second diary.]

#### Consequence or unresolved tension
[Develop what follows from the discussion. State material limits where they
change the reasoning; do not replace the academic discussion with a research to-do list.]

#### Sources
[Provide usable bibliographic or primary-source references on the page.]

---
[Return links to relevant timeline occurrences.]
[Related threads, with relationships left provisional where needed.]
[Story links only where useful; their presence does not settle the distinction.]

Academic writing here includes interpretation, qualification and explicit attribution. No claim to a neutral or non-biased view has been established. The place of authorial interpretation within Knowledge remains a question for review.

Story template · provisional

---
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?]

---

[Sources cited on this page, followed by any useful Knowledge links.]
[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 is being tested

The antechamber example currently appears in three settings:

• Diary: the encounter and what captures attention, in the voice of the represented moment.
• Knowledge: a self-contained academic analysis of ritual provision, omission, collection and operational access.
• Story: enough of that evidence is restated to make the proposed programme argument readable on its own.

This distribution is a sample to assess, not a confirmed division of intellectual work. Necessary evidence may recur when a passage needs it to be intelligible. A link can offer further analysis without carrying missing premises.

The ledger remains a production record. It records source locations and AI authorship, while the reading pages contain the evidence, citations and references they need.

Reader encounters

In the present sample, the primary forward action on a diary page is “Continue in Time”.

The sample currently tests presence 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.

A reading link lands at a named heading. Its label identifies the intended reading span. The end of that span contains a short block embed from the departure passage and a link to the exact reading choice in the diary or Story. The source excerpt is maintained once, in its original sample passage. Early diary entries also offer explicit returns for readers arriving from Knowledge. How much later understanding a forward reader should encounter remains a navigation question.

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.

These are static, explicitly labelled return routes. A passage used by both Time and Story offers a separate short cue for each. The sample does not claim to detect the reader's origin automatically. A reader can continue within Knowledge, return to the precise departure point or use its topical orientation. Block embeds avoid duplicating the remembered wording.

There is one physical home for each full Knowledge discussion in the current sample. 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.

For the immediate comparison, read the two Knowledge notes and the corresponding Story passage. Notice whether the discussion of literature offers enough depth, and whether the architectural argument does distinct work. Their separate locations remain part of the experiment.

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.