johba/disinto
1
0
Fork 0
Code Issues 4 Pull requests Projects Releases Packages Wiki Activity Actions
disinto/predictor/AGENTS.md
johba 71fe89cdd0 fix: {project}-ops repo — separate operations from code (#757) (#767) 
Fixes #757

## Changes
Separate operations from code into {project}-ops repo pattern. Added OPS_REPO_ROOT infrastructure (env.sh, load-project.sh, formula-session.sh with ensure_ops_repo helper). Updated all 8 agent scripts and 7 formulas to read/write vault items, journals, evidence, prerequisites, RESOURCES.md, and knowledge from the ops repo. Added setup_ops_repo() to disinto init for automatic ops repo creation and seeding. Removed migrated data from code repo (vault data dirs, planner journal/memory/prerequisites, supervisor journal/best-practices, evidence, RESOURCES.md). Updated all documentation. 55 files changed, ShellCheck clean, all 38 phase tests pass.

Co-authored-by: openhands <openhands@all-hands.dev>
Reviewed-on: https://codeberg.org/johba/disinto/pulls/767
Reviewed-by: Disinto_bot <disinto_bot@noreply.codeberg.org>
2026-03-26 19:55:12 +01:00

3.1 KiB
Raw Blame History

Predictor Agent

Role: Abstract adversary (the "goblin"). Runs a 2-step formula (preflight → find-weakness-and-act) via interactive tmux Claude session (sonnet). Finds the project's biggest weakness, challenges planner claims, and generates evidence through explore/exploit decisions:

  • Explore (low confidence) — file a prediction/unreviewed issue for the planner to triage
  • Exploit (high confidence) — file a prediction AND dispatch a formula via an action issue to generate evidence before the planner even runs

The predictor's own prediction history (open + closed issues) serves as its memory — it reviews what was actioned, dismissed, or deferred to decide where to focus next. No hardcoded signal categories; Claude decides where to look based on available data: prerequisite tree, evidence directories, VISION.md, RESOURCES.md (from ops repo), open issues, agent logs, and external signals (via web search).

Files up to 5 actions per run (predictions + dispatches combined). Each exploit counts as 2 (prediction + action dispatch). The predictor MUST NOT emit feature work — only observations challenging claims, exposing gaps, and surfacing risks.

Trigger: predictor-run.sh runs daily at 06:00 UTC via cron (1h before the planner at 07:00). Sources lib/guard.sh and calls check_active predictor first — skips if $FACTORY_ROOT/state/.predictor-active is absent. Also guarded by PID lock (/tmp/predictor-run.lock) and memory check (skips if available RAM < 2000 MB).

Key files:

  • predictor/predictor-run.sh — Cron wrapper + orchestrator: active-state guard, lock, memory guard, sources disinto project config, builds structural analysis via lib/formula-session.sh:build_graph_section() (full-project scan — results included in prompt as ## Structural analysis; failures non-fatal), builds prompt with formula + forge API reference, creates tmux session (sonnet), monitors phase file, handles crash recovery via run_formula_and_monitor
  • formulas/run-predictor.toml — Execution spec: two steps (preflight, find-weakness-and-act) with needs dependencies. Claude reviews prediction history, explores/exploits weaknesses, and files issues in a single interactive session

Environment variables consumed:

  • FORGE_TOKEN, FORGE_PREDICTOR_TOKEN (falls back to FORGE_TOKEN), FORGE_REPO, FORGE_API, PROJECT_NAME, PROJECT_REPO_ROOT, OPS_REPO_ROOT
  • PRIMARY_BRANCH, CLAUDE_MODEL (set to sonnet by predictor-run.sh)

Lifecycle: predictor-run.sh (daily 06:00 cron) → lock + memory guard → load formula + context (AGENTS.md, VISION.md from code repo; RESOURCES.md, prerequisites.md from ops repo) → create tmux session → Claude fetches prediction history (open + closed) → reviews track record (actioned/dismissed/watching) → finds weaknesses (prerequisite tree gaps, thin evidence, stale watches, external risks) → dedup against existing open predictions → explore (file prediction) or exploit (file prediction + dispatch formula via action issue) → PHASE:done. The planner's Phase 1 later triages these predictions.