Skip to content

I0813 — A closed session becomes a node that points at its episode

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.

BLOCKED wave 7 · p1 · implementation profile · runs alone

Part of M003 — A session is a durable envelope, and knowledge is compiled from what is already canonical.

Blocked. This issue cannot start until I0806, I0812 are done. The status is derived from that, not declared.

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.

Current state

The knowledge graph covers repository artifacts. Sessions exist as records that nothing traverses.

Desired state

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.

Scope

  • lib/knowledge.sh
  • lib/knowledge.awk
  • test/cases/71_session_knowledge.sh

Out of scope

  • Any inference about why a session touched something
  • Copying a session summary into a node

Dependencies

What waits on this

Acceptance criteria

  • 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

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0813.yaml. Read it back with majordomus plan show I0813.