.pm/board.yaml

@@ -0,0 +1,68 @@
+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

.pm/gitea-url

@@ -0,0 +1 @@
+https://git.jajahome.duckdns.org/omp/rsi

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 Gitea issues labelled `Requirement`.
+  through reviewable PRs and pm-board proposals.
 
 ## Status
 

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 Gitea issue labelled `Requirement` — and the user merges.
+against the config repo and/or a pm-board proposal — 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 + Gitea requirement issue)
+              S6 calibration ← S5 human gate (PR + pm-board proposals)
 ```
 
 ### 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.
-- the Gitea issue tracker — accepted/rejected proposals tell you which past
+- pm-board `.pm/` state — 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
-- Gitea issues labelled `Requirement` (frontmatter `op:`/`id:`/
+- pm-board proposals in `.pm/proposals/*.md` (frontmatter `op:`/`id:`/
   `section:`/`title:`) for board-tracked items.
 
 The user's accept/reject is the ground-truth label for S6.