A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I0813
A closed session becomes a node that points at its episode
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Extract closed sessions as knowledge nodes whose edges point at the tasks, issues, checkpoints, handovers, decisions and questions they name, so that the graph answers which sessions touched an issue, which decisions affected it, and which handover continued a task — without any session body being copied anywhere.
- Why
- This is what makes the two halves of the milestone one thing. Temporal and causal navigation is what a worker actually wants from a prior session, and it is exactly the part that does not require reading the prose.
- Now
- The knowledge graph covers repository artifacts. Sessions exist as records that nothing traverses.
- Wanted
- A session node carries its id, its window and its outcome; its edges carry the relationship and the session record they were observed in. Checkpoints, which are numerous and individually low-value, are represented as references from the session rather than as one node each, so that a high-volume record kind does not dominate the graph.
- Done when
- unknown: the record declares no `completion`
- Risk
- Every operational record kind added to the graph increases the chance one of them leaks into a shared projection. The scope field has to be the only thing that decides, and it has to be tested at the projection boundary rather than at each producer.
Acceptance
- A query for an issue names the sessions that touched it, and each answer carries the session record it came from
- A session node holds no body text from any record it references
- A high-volume record kind does not produce one node per file where a reference list is sufficient, and the reason is stated
- Sessions are operational scope and never shared, proved by a case
- Validation
bash test/run.sh 71_session_knowledge- Evidence required
session_nodes_reference- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
lib/knowledge.shlib/knowledge.awktest/cases- Not
Any inference about why a session touched somethingCopying a session summary into a node- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-04
- Updated
- 2026-09-04
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.