daily-note-demonstration-method-oct11-1
Purpose and stop condition
Demonstrate two days and two formats inside the publication vault. Preserve the existing daily-note relationships while testing a more integrated reading experience. Stop after the sample, its placement records, metadata and adoption instructions are checked.
The sequence can be provisionally useful before the full audit finishes. A later correction changes the affected contribution, date or dependency. It need not trigger a rewrite of every diary entry.
Operations stack and the decisions carried forward
Preserved and processed inputs
Read the legible diarised account first and inspect original human work where dates, attribution or wording matter. Exact human extracts remain exact. AI extracts, interpretations and navigation records retain their status. A file creation date, event date, recollection date, proposed narrative date and current production date are separate fields.
Placement material
01 placement material is a bridge to earlier writing, recovered questions and source relationships. Its flattened reading copy helps identify a passage, but the actual Review 1 deck and oral draft establish this sample's wording and setting. Question and precedent recovery records supply leads. Older missing-writing and AI-draft lists do not automatically create current obligations or prove an encounter.
Transcript interpretation and the mid-sequence plan
Reuse the existing S source blocks, U work units and M planning moments. M04 supplies the early theory neighbourhood. The 5 March preparation is an evidenced expression of that enquiry, not a redating of M04. Review 1 is a checkpoint. M26's proposed 9–11 March scope response and M05's 12–13 March criteria work remain downstream. Their proposed dates do not prove decisions, readings or completed research.
Investigation research and argument drafting
The connected investigation drafts have done substantive research. Their literature notes, figures, response log, question log and handovers must be reused. Drafting status, access and historical encounter are different questions. The sample uses their existing paragraphs through the consolidated text. It does not recommission the research or answer current drafting questions as though they were March diary thoughts.
Argument consolidation
The flattened argument supplies coherent academic passages. The three retained paragraphs are copied unchanged into dated cycle contributions. Their original investigation origin stays recorded even when another investigation needs a reference to them. The current consolidation log accounts for draft blocks, not every human transcript point. Fresh snapshot locators and hashes accompany this run because stored line numbers have shifted.
The pending source audit
Use one source-led record: human point → relevant investigation units and drafts → consolidated contribution → cycle home → daily exposure. Search across all investigations for a point's consequences. Record partial representation and missing implications, rather than treating one matching paragraph as complete coverage.
A missing point first becomes a bounded pending item with its source, function and proposed destination. A personal memory goes to a memory prompt. Research needs go to the relevant cycle category. A task remains an intention. A consequential design choice returns to the user. No missing point is automatically written into the thesis or squeezed into the nearest date.
Timeline interviews and daily production
Reuse the existing first-person daily adaptations unchanged apart from local links and shorter source pointers. They remain #AIdraft. Exact human wording is preserved separately. The diagnostic version exposes the functional divisions. The integrated version rearranges the same blocks around the foreground passage, its image and the surrounding thought.
Events orient the entry. The day shows processing before or after an event. The 6 March live discussion and the 8 March written feedback remain different moments. Historical programme indecision continues beyond this sample.
Tasks, questions and loose ideas
Use the confirmed task master and other registers as navigation. Verify against the human source before using an item as a dated intention or decision. GIS access and books arise in the actual review material. The later loose list overlaps with site criteria, grief care and the relationship between the programmes. Its undated and later additions remain later material, not March facts.
The integrated sample disperses questions and fleeting intentions beside the thought that gives them a reason. None is marked complete. A cross-reference in the operations record accounts for useful later material without making the day carry every register item.
Investigation cycles
Each contribution has one primary home under the existing cycle and one dated H6 heading. A related investigation points to that heading. The daily note transcludes the primary contribution. The image accompanies that contribution, with its origin and proposed match visible.
The nine headers keep distinct jobs:
- opening questions or claims, position: the early Dreamscape proposition and the programmes' independent journeys.
- other ways of knowing: personal experience and drawing can inform an enquiry. Memory prose remains with the user.
- literature review: verified source material and academic development belong here after an encounter is handled. The dated 2014 extract and the unplaced 2011 passage remain distinct.
- precedents: a recommendation is a lead. Walkscapes and the unidentified crematorium do not become completed precedent analyses.
- qualities: familiar/strange, beauty, attention and comfort can be developed here. This sample does not duplicate its opening passage to fill this header.
- context: the dated site-criteria passage connects programme, regional reach and water.
- design test or experiments: the actual earth/sky sketch is an existing exploratory artefact. Its question remains open.
- interpretation: later reflection on Review 1 has a later placement. Receiving feedback on 6 March does not supply a resolved interpretation that day.
- design consequences: a developed proposal or supported change belongs here. Alternatives and technical intentions remain open, and no finished building is inferred.
Unfilled headers remain visible in the supporting cycles. They do not create writing quotas. Cycle function, originating investigation, primary home and daily foreground are recorded independently.
Memories
Retain a focused exact first-person extract, its recollection date, uncertainty and one writing prompt. Link back to the sample day that activates it. No event date is invented and no finished memoir is generated. Public use remains for the user to decide.
Literature encounters
An extract already shown by the review can appear on that day as a known resource, without claiming that this was the first reading. A book recommendation can appear as a recommendation. A later academic citation cannot be backdated from a catalogue date or a thematically similar earlier paper.
The companion demonstrates the known 2014 quotation and the unplaced 2011 passage. It preserves the latter's developed architectural reasoning for later placement. It does not silently substitute the earlier article for the dissertation or invent a diary reading encounter.
Decisions and containers
Only source-supported decisions produce change-log lines. The 5 March presentation stance and provisional site criteria, and the 6 March public subtitle, are eligible. Hybrid programme retention is a continuation, not a completed resolution. Live recommendations to narrow scope or intensify community use are feedback, not accepted changes.
Each sample container has current position and change log. These are state summaries rather than a second diary. The integration plan compares existing lines before adding anything.
Thread properties and future visualisation
Presence, expression and importance are independent. The YAML uses compact lists for the two binary axes, with separate unknown lists for unassessed values, and thirteen numerical importance fields. The JSON expands these into nullable booleans and numbers for a future visual.
Unknown is a limit of assessment, not another conceptual thread state. Implicit requires a stated positive basis. Importance concerns the project's weight at that point. The day's foreground does not automatically score highest. The structured version is excluded from the visual dataset so a day is counted once.
Images and publication
Use bounded copies of actual existing assets. Record the archive, deck page or current publication asset and match status. Historical drawings can accompany later explanatory prose without proving that the later explanation was their original intent. No generated drawing is introduced.
All reader links resolve within the sample inside the publication vault. The sample is not published. The existing PDF text folder, live notes, workbook, registries, publication settings and another workflow's methods are unchanged.
Daily template headers and their integrated equivalents
- thoughts: retained first-person blocks form the narrative around the academic foreground.
- in the background: retained blocks appear at the point where their relationship matters, including water memories and unresolved material interests.
- thread tags: existing short tags remain at the body opening. Detailed assessments sit in YAML and the metadata companion.
- events: the presentation opening and feedback passage orient the day. They do not become an information dump or a duplicate event registry.
- encounters: the actual extract is transcluded beside the reflection it informs. Unknown reading remains in its companion.
- investigation relations: foreground prose and image are transcluded from their dated cycle home. Background relations are links or short references.
- decisions: plain sentences link to the container state they change.
- tasks: existing short intentions become fleeting lines beside the relevant question. The source records retain their origin and status.
Comparison and revision control
Both daily formats use identical first-person blocks, academic contributions, images, source pointers and task wording. Only order, functional headings and task presentation differ. The sample contains one academic copy per primary contribution. Stable contribution IDs let a later audit revise the passage or its placement independently of the chosen daily format.