From b451e4932b6bf143355f54cd3fbc1d1c87ec4c75 Mon Sep 17 00:00:00 2001 From: Jason Dekarske Date: Mon, 5 Oct 2026 07:39:37 -0700 Subject: [PATCH] Remove the .pm board; requirements now live in Gitea issues The pm-board web UI and its task runner are retired in goodcode/pm-board#38. Every requirement on this board was migrated to a Gitea issue labelled `Requirement` and every implementation choice to an issue labelled `Choice`, so the local board file has no remaining source. --- .pm/board.yaml | 68 ------------------------------------ .pm/gitea-url | 1 - README.md | 2 +- docs/03-dreaming-with-jev.md | 8 ++--- 4 files changed, 5 insertions(+), 74 deletions(-) delete mode 100644 .pm/board.yaml delete mode 100644 .pm/gitea-url diff --git a/.pm/board.yaml b/.pm/board.yaml deleted file mode 100644 index c1f2fe2..0000000 --- a/.pm/board.yaml +++ /dev/null @@ -1,68 +0,0 @@ -requirements: - - id: R1 - title: Jev research summary - body: | - Summarize what Jev (TypeSafe AI, launched 2026-09-15) does and how it - works at an undergraduate level, with examples. Claims must be tagged - confirmed / self-reported / speculative, with sources. - last_changed: "2026-09-18 06:10" - changed_by: agent - - id: R2 - title: Jev use cases inside the pi harness - body: | - Identify concrete use cases for Jev within the pi (Oh My Pi) harness, - each grounded in a real extension surface (hooks, custom tools, skills, - context files, memory pipeline, model routing) with honest limits and - explicitly non-fitting cases. - last_changed: "2026-09-18 06:10" - changed_by: agent - - id: R3 - title: Dreaming method proposal - body: | - Propose a method using Jev to "dream": a batch job that replays past - interactions, mines improvement opportunities, and adds useful skills, - AGENTS.md/RULES.md guidance, system-prompt updates, and custom tools to - the pi configuration via human-approved PRs and pm-board proposals. - last_changed: "2026-09-18 06:10" - changed_by: agent - - id: R4 - title: Hosted and reviewable - body: | - Repo on Gitea (goodcode/rsi), work lands via pull request (never direct - to main), and the project is enrolled in the deployed pm-board. - last_changed: "2026-09-18 06:10" - changed_by: agent -choices: - - id: C1 - title: Board-only project, docs in-repo - body: | - No static site is served; the deliverables are research documents in the - repo. A site would add serving surface without adding information. - last_changed: "2026-09-18 06:10" - changed_by: agent - - id: C2 - title: Jev judges, the LLM writes - body: | - Jev is used only for bounded-output decisions (Noul/Score/Choice - triage, routing, gating). All synthesis — drafting skills, diffs, - tool code — stays with the harness LLM, because Jev structurally - cannot generate strings. - last_changed: "2026-09-18 06:10" - changed_by: agent - - id: C3 - title: Dream outputs are proposals, never direct edits - body: | - The dreaming pipeline writes PRs and pm-board proposals with evidence - links; the user merges. Accept/reject outcomes are the ground-truth - labels for a calibration loop that tunes Jev thresholds over time. - last_changed: "2026-09-18 06:10" - changed_by: agent - - id: C4 - title: Swappable Jev backend behind one interface - body: | - JevClient with three backends: real Jev (needs TYPESAFE_API_KEY early - access), an LLM constrained to the same typed schema (system-one - adapter pattern) for building/auditing now, and a deterministic mock - for tests. Pin jev-1.13.0 when live; log the responding model id. - last_changed: "2026-09-18 06:10" - changed_by: agent \ No newline at end of file diff --git a/.pm/gitea-url b/.pm/gitea-url deleted file mode 100644 index 0050252..0000000 --- a/.pm/gitea-url +++ /dev/null @@ -1 +0,0 @@ -https://git.jajahome.duckdns.org/omp/rsi \ No newline at end of file diff --git a/README.md b/README.md index e0186cc..91e7024 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ starting from **Jev** — TypeSafe AI's System One decision model a scheduled "dream" job that replays past sessions, uses Jev to screen every segment for improvement opportunities, and turns the best into skills, AGENTS.md/RULES.md edits, system-prompt updates, and custom tools — all - through reviewable PRs and pm-board proposals. + through reviewable PRs and Gitea issues labelled `Requirement`. ## Status diff --git a/docs/03-dreaming-with-jev.md b/docs/03-dreaming-with-jev.md index aa7f5a7..23a588c 100644 --- a/docs/03-dreaming-with-jev.md +++ b/docs/03-dreaming-with-jev.md @@ -14,7 +14,7 @@ configuration changes: - new **custom tools** (`~/.omp/agent/tools/*.ts`) Nothing lands directly. Every output is a reviewable artifact — a Gitea PR -against the config repo and/or a pm-board proposal — and the user merges. +against the config repo and/or a Gitea issue labelled `Requirement` — and the user merges. ## Why Jev, and why now @@ -44,7 +44,7 @@ look. ``` S0 harvest → S1 segment → S2 jev triage → S3 cluster → S4 LLM synthesis ↓ - S6 calibration ← S5 human gate (PR + pm-board proposals) + S6 calibration ← S5 human gate (PR + Gitea requirement issue) ``` ### S0 — Harvest @@ -59,7 +59,7 @@ Sources: entries after `reset_boundary`. - `~/.omp/agent/history.db` (`history` table) — bare user prompts are a cheap signal of repeated requests. -- pm-board `.pm/` state — accepted/rejected proposals tell you which past +- the Gitea issue tracker — accepted/rejected proposals tell you which past suggestions the user actually wanted. - Generated skills and `learned.md` under the memory root — what has already been learned, so the dreamer proposes deltas, not duplicates. @@ -149,7 +149,7 @@ Artifacts are written to a dream workspace branch: - one Gitea PR per dream run against the config repo (per the standing branch workflow: never commit to main; the user merges), and -- pm-board proposals in `.pm/proposals/*.md` (frontmatter `op:`/`id:`/ +- Gitea issues labelled `Requirement` (frontmatter `op:`/`id:`/ `section:`/`title:`) for board-tracked items. The user's accept/reject is the ground-truth label for S6. -- 2.47.2