os-me V5: predict reads the outcome node of the project #1756

New issue

Open

opened 2026-11-13 20:10:49 +00:00 by jared · 1 comment

jared commented

2026-11-13 20:10:49 +00:00

Owner

Problem

/os-me:predict does not read the outcome node of the project before it predicts. Stage V5 of docs/decision-system/build-plan.md asks for this: "/os-me:predict reads the project's outcome node before it predicts. Session start injects one pointer to the node, not the picture." V5 needs V4. The V4 tracer writes the first vault outcome nodes at outcome/<project>.md on 2026-11-13.

Observed

plugins/os-me/skills/predict/SKILL.md does not contain the word "outcome".
~/dev/os-me-store/brief.md does not contain the word "outcome". ~/dev/os-me-store/ENTRY.md contains it only in an example Prediction.
plugins/os-context/prompts/session-start/40-decisions.md rung 1 tells a session to read outcome/<project>.md in the vault. No session-start text gives the path of the node for the current project.
The build-plan Status table has no row for V4, V5, or V6.

Reproduce

n/a: feature ticket.

Approach

Change text first. Write code only if a reader object is necessary.

Required work:

The predict skill tells the predictor to read the outcome node of the project before it predicts, and to name the node in the Prediction — check: present outcome/ in plugins/os-me/skills/predict/SKILL.md

Orchestrator work: Update ~/dev/os-me-store/brief.md and ~/dev/os-me-store/ENTRY.md (a different repository) so that the predictor reads the node and the Prediction names the node it read. Add one pointer to the node in the os-context session-start text. The pointer gives the path, not the content. Run bin/refresh-plugins. Mark V5 in the Status table of docs/decision-system/build-plan.md and add one History row to docs/implementation-status/os-me.md.

Acceptance criteria

Given a project with a vault node at outcome/<project>.md, when a session runs /os-me:predict, then the Prediction names the node it read.
Given a project with no outcome node, when a session runs /os-me:predict, then the Prediction says that no node exists.
Given a new session in a project with an outcome node, when the session starts, then the injected text contains one pointer to the node and does not contain the node content.
Given the changed files, when bin/refresh-plugins runs, then it passes.

Non-goals

V6, the hook-level check that a judgment-tier decision read the outcome node.

Origin

Trigger: the os-me check of 2026-11-13 in session 2bb44e9c. Jared asked how the os-me outcome function works and said "We definitely need to get this back on track. /os-me:predict desired outcome, how to get there, then do it!" The applied Prediction (docs/decisions/rulings.tsv row 161) sends this work to a ticket.
Improvised this session: none
Chain: predict does not read the outcome node ← stage V5 is not built (docs/decision-system/build-plan.md, V5 row) ← V5 needs V4, and V4 starts on 2026-11-13 ← DESIGN (docs/decision-system/build-plan.md)
Root candidate: none found; searched outcome node, outcome/, V5, stage V, decision-system, os-me predict, predict skill, session-start pointer
Where: plugins/os-me/skills/predict/SKILL.md; ~/dev/os-me-store/brief.md; ~/dev/os-me-store/ENTRY.md
Session: 2bb44e9c-522c-4c97-8449-bd46bed898e0
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/2bb44e9c-522c-4c97-8449-bd46bed898e0.jsonl

VERDICT: CREATE (ticket-skeptic, 2026-11-13): stage V5 is a stated requirement in docs/decision-system/build-plan.md and no open ticket covers it.

## Problem `/os-me:predict` does not read the outcome node of the project before it predicts. Stage V5 of `docs/decision-system/build-plan.md` asks for this: "`/os-me:predict` reads the project's outcome node before it predicts. Session start injects one pointer to the node, not the picture." V5 needs V4. The V4 tracer writes the first vault outcome nodes at `outcome/<project>.md` on 2026-11-13. ## Observed `plugins/os-me/skills/predict/SKILL.md` does not contain the word "outcome". `~/dev/os-me-store/brief.md` does not contain the word "outcome". `~/dev/os-me-store/ENTRY.md` contains it only in an example Prediction. `plugins/os-context/prompts/session-start/40-decisions.md` rung 1 tells a session to read `outcome/<project>.md` in the vault. No session-start text gives the path of the node for the current project. The build-plan Status table has no row for V4, V5, or V6. ## Reproduce n/a: feature ticket. ## Approach Change text first. Write code only if a reader object is necessary. Required work: 1. The predict skill tells the predictor to read the outcome node of the project before it predicts, and to name the node in the Prediction — check: present `outcome/` in `plugins/os-me/skills/predict/SKILL.md` Orchestrator work: Update `~/dev/os-me-store/brief.md` and `~/dev/os-me-store/ENTRY.md` (a different repository) so that the predictor reads the node and the Prediction names the node it read. Add one pointer to the node in the os-context session-start text. The pointer gives the path, not the content. Run `bin/refresh-plugins`. Mark V5 in the Status table of `docs/decision-system/build-plan.md` and add one History row to `docs/implementation-status/os-me.md`. ## Acceptance criteria 1. Given a project with a vault node at `outcome/<project>.md`, when a session runs `/os-me:predict`, then the Prediction names the node it read. 2. Given a project with no outcome node, when a session runs `/os-me:predict`, then the Prediction says that no node exists. 3. Given a new session in a project with an outcome node, when the session starts, then the injected text contains one pointer to the node and does not contain the node content. 4. Given the changed files, when `bin/refresh-plugins` runs, then it passes. ## Non-goals V6, the hook-level check that a judgment-tier decision read the outcome node. ## Origin - Trigger: the os-me check of 2026-11-13 in session 2bb44e9c. Jared asked how the os-me outcome function works and said "We definitely need to get this back on track. /os-me:predict desired outcome, how to get there, then do it!" The applied Prediction (docs/decisions/rulings.tsv row 161) sends this work to a ticket. - Improvised this session: none - Chain: predict does not read the outcome node ← stage V5 is not built (docs/decision-system/build-plan.md, V5 row) ← V5 needs V4, and V4 starts on 2026-11-13 ← DESIGN (docs/decision-system/build-plan.md) - Root candidate: none found; searched outcome node, outcome/<project>, V5, stage V, decision-system, os-me predict, predict skill, session-start pointer - Where: plugins/os-me/skills/predict/SKILL.md; ~/dev/os-me-store/brief.md; ~/dev/os-me-store/ENTRY.md - Session: 2bb44e9c-522c-4c97-8449-bd46bed898e0 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/2bb44e9c-522c-4c97-8449-bd46bed898e0.jsonl VERDICT: CREATE (ticket-skeptic, 2026-11-13): stage V5 is a stated requirement in docs/decision-system/build-plan.md and no open ticket covers it.

jared added the

project/cc-os

filed-by/agent

category/prose-artifact

labels

2026-11-13 20:10:49 +00:00

jared commented

2026-11-13 20:24:49 +00:00

Author

Owner

State on 2026-11-13, after this ticket was filed. The vault has ~/Documents/SecondBrain/outcome/ with five nodes (cc-os, hyperthrive, hyperthrive-websites, os-me, os-sdlc) and an outcome note type. Rung 1 of plugins/os-context/prompts/session-start/40-decisions.md now defines <project> (commit c55c5af9e). The Observed line about ENTRY.md is no longer true: Store commit 41975ba made ~/dev/os-me-store/ENTRY.md read outcome/<project>.md and gave brief.md a Project: line. Still open: plugins/os-me/skills/predict/SKILL.md has no outcome/ text, no session-start text injects a pointer to the node, and the build-plan Status table has no V4, V5, or V6 row.

State on 2026-11-13, after this ticket was filed. The vault has `~/Documents/SecondBrain/outcome/` with five nodes (cc-os, hyperthrive, hyperthrive-websites, os-me, os-sdlc) and an `outcome` note type. Rung 1 of `plugins/os-context/prompts/session-start/40-decisions.md` now defines `<project>` (commit c55c5af9e). The Observed line about `ENTRY.md` is no longer true: Store commit 41975ba made `~/dev/os-me-store/ENTRY.md` read `outcome/<project>.md` and gave `brief.md` a `Project:` line. Still open: `plugins/os-me/skills/predict/SKILL.md` has no `outcome/` text, no session-start text injects a pointer to the node, and the build-plan Status table has no V4, V5, or V6 row.

jared referenced this issue from a commit

2026-11-13 20:49:46 +00:00

feat(os-me): Read outcome node before predicting