docs(learning-tier): owner decisions 1–5 recorded (closes #34) - #36
Merged
Merged
Conversation
… waits for 0.5.x Decision 1 of the plan §7 queue (#34). The owner accepted the council D13 split and went further: feat/jev-struggle-eval is not cut until milestone 0.5.x is closed, because item 1 (the mentor writes to the learning tier) is the MVP blocker and item 2 is a post-MVP measurement. The reasoning is recorded beside the verdict rather than in chat: the repository history shows 17 archive tags whose tips never reached main and six parallel branches opened 7-8 Sept and archived on the 10th, which is what one shared vehicle risks. Consequence recorded: decision 4 (Jev spend cap) is deferred to the day S2 starts. Decision 5 (merge order) is marked resolved by the housekeeping PR #35 cherry-pick, as issue #34 already states. §2 cut-point sentence updated from the stale 4f8e3e0.
…provals, noticing episode by rule Decision 2: no pre-approval of W_auto on Claude (prompt per call), OpenCode wildcard untouched this branch; consequence taken: no new pre-approval on any harness, kiro keeps its existing log_topic entry as the one recorded asymmetry. Evidence recorded beside the verdict: kiro and opencode already had grants and still logged zero writer calls, so the defect is the instruction, not the prompt. Naming is distinguished from approving: socratic-mentor.md must name each W_auto tool because its tools: line names none today. The §1 paragraph, S1-0 bullets and the parity test-table row are rewritten to match. Decision 3: the noticing episode is scheduled by rule — the first real study session after S1-GREEN reaches main — with the date recorded in the S1-SIM receipt.
5 tasks
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The plan has stale status text and an unresolved mismatch in noticing-episode timing.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
This docs-only PR records owner decisions 1–5 for the learning-tier plan.
Changes:
- Confirms branch sequencing and defers Jev evaluation.
- Defines harness writer naming and approval policies.
- Records noticing, spend-cap, and merge-order decisions.
| File | Summary |
|---|---|
docs/architecture/learning-tier/plan-2026-09-19.md |
Updates owner decisions and implementation constraints; remaining documentation inconsistencies require correction. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+12
to
+15
| 143,973 historical messages. This item adds the missing writer, names the additive writers in every harness | ||
| definition (no new pre-approvals — owner decision 2, §7), gives every harness one machine-readable trigger | ||
| table, and proves the pipe is open with a scripted learner on all six installed harnesses — claiming only what | ||
| was observed. |
4 of 6 tasks
…names, not grants) The stage list still said kiro allowedTools += W_auto and claude settings.json += W_auto, contradicting the §7 verdict recorded two commits earlier. Now: names in every definition, both grant files unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #34.
Records the owner verdicts for the learning-tier plan §7 (
docs/architecture/learning-tier/plan-2026-09-19.md), one commit per sitting. Docs only; mkdocs strict clean (the plan is excluded from the public site by policy).feat/learning-tier-fedis cut when S1-0 starts;feat/jev-struggle-evalis not cut until milestone 0.5.x is closed — item 1 is the MVP blocker, item 2 a post-MVP measurement. Reasoning recorded with the repo history that motivated it (17 archive tags whose tips never reached main; six parallel branches opened 7–8 Sept, archived on the 10th).log_topicentry as the one recorded asymmetry.socratic-mentor.mdmust still name eachW_autotool (itstools:line names none today) — naming is instruction, not approval. Parity is pinned on the instruction (trigger table +W_autoset), never on approval. §1, the S1-0 bullets and the parity test-table row are rewritten to match.main; date recorded in the S1-SIM receipt.feat/jev-judgemain).What this unblocks: item 1 (feed the learning tier) can be filed as its own issue and S1-0 can start on
feat/learning-tier-fedcut frommain.