neqsim-continuous-task-improvement

Continuous Task Improvement (Living Tasks)

A normal task ends with a report. A living task keeps a continuous/ folder next to the normal three steps and is improved by cycles: small, resumable, auditable runs that pull new evidence, recompute KPIs, detect drift, update an improvement ledger and — only on a trigger — ask an agent to look. The engineer promotes a reviewed cycle to the new baseline. Nothing in the old task changes.

Principle: program the loop, prompt the exceptions. The runner makes no LLM calls; agents run only when a trigger fires; people decide.

When to use

All commands run through the shared interpreter: <python-executable> devtools/neqsim_cli.py task-<command> ... (or neqsim task-<command>). <task> may be a path or a folder name inside the task root (neqsim --show-task-root); task-status and task-reference-case default to the task root when no folder is given.

Workflow

1. Make it living (never overwrites):

   neqsim task-living <task> --brief brief.docx
   

   Creates continuous/cycle_plan.yaml, a draft goal.yaml compiled from the brief, baseline/ from results.json key results, a ledger seeded from recommendations, and a continuous: block in study_config.yaml.
2. Edit the plan — sources (adapter + options), scripts (task-local stage functions), KPIs, drift signals, triggers, stages, solve settings, backtest expectations. See the template written by task-living.
3. Confirm the goal — fill objective.metric/direction/target and set confirmed_by. task-solve refuses an unconfirmed goal (--allow-unconfirmed for experiments only).
4. Backtest before scheduling — replay archived data with a simulated clock:

   neqsim task-backtest <task> --start 2025-10-02 --end 2026-09-30 --repeat
   

   Report: detected / missed expected events, delay, false alarms per month, reproducibility. Written to continuous/backtests/<run>/; live state is untouched.
5. Resume before starting fresh work — neqsim task-status <task> is the five-second persisted view. If it reports resumable work, run neqsim task-resume <task>. The task folder, not prior chat, is authoritative.
6. Process evidence changes — map evidence globs to affected stages and conclusions under evidence.rules (match, stages, affected kpis, and conclusions); use neqsim task-update <task>. Mapped changes rerun only the affected stages and declared dependencies while invalidating affected KPIs and retaining unaffected ones. An unmapped path fails closed to the full plan.
7. Run cycles — neqsim task-cycle <task> (monitor) or schedule it: neqsim task-schedule <task> --daily 05:00 --install (Windows Task Scheduler; the cron line is printed for Linux servers).
8. Review and promote — read continuous/LIVING_REPORT.md (the always-current view) and cycles/<id>/digest.md, decide ledger items (task-ledger <task> set OPP-0002 accepted --by NAME), then neqsim task-promote <task> <cycle-id> --reviewer NAME.
9. Finalize explicitly — only after the accepted result is promoted and evidence is current, run neqsim task-report <task> --final --reviewer NAME. This uses the canonical Task Solver generator and writes an immutable FR-### Word/HTML delivery plus hashes and audit references.