• Found during Phase 1 real end-to-end verification (2026-08-12): 3
    independent real runs, 3 different goals, all hit the same known,
    unrelated-to-Phase-1 issue -- a self-planned benchmark/test_script node's
    own judgment rejecting narrative summaries, exhausting loop_back's
    max_attempts. One of the three ran against the real production
    backend_server after the FK migration fix (bd1404d), confirming the new
    Phase 1 status machine routes the failure correctly (blocked_pending_human
    with a real diagnostic trail) even when the underlying pre-existing bug
    fires before planner_reviewer is ever reached.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse File »
  • Phase 1 (planner_reviewer review gate + P0 resume-bug fix) shipped as
    ea19c7d, matching org-graph-unification-phase1-review-gate-design.md
    exactly (new task.status value, org role, _REQUIRED_ARTIFACTS narrowing,
    both bugs fixed). Moving that design doc and the P0 bug doc it subsumed
    to docs/done/, updating their status headers, and fixing the doc-path
    references left pointing at their old docs/todo/ location across
    agents/planner_reviewer/{SOUL,AGENTS}.md, src/schema.py migration
    docstrings, and the other Phase 2/deblackbox docs. Full suite green
    (731 tests) both before and after.
    
    Also ran Phase 2 SDD's §9 interface-reconciliation checklist against the
    real Phase 1 implementation now that it exists for real: all three items
    check out (run_id is included in plan_and_review_documents()'s return
    shape, the new task.status value is exactly reviewing_planner_output as
    assumed, and planner_reviewer's role.json doesn't pre-reserve a skill
    slot for Phase 2's new skill, which is fine -- a one-line addition when
    Phase 2c lands, not an incompatibility). Updated §9 to reflect this.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse File »

  • … work, compress bloated incident log
    
    - Delete org-graph-as-work-graph-unified-loop-requirements.md: fully
      superseded by org-graph-unification-and-universal-self-planning-
      requirements.md; folded its one non-duplicated detail (the 2084590a
      benchmark-narration trigger incident) into that doc's background instead.
    - Split scheduler-production-polling-loop-{requirements,design}.md by
      completion status: FR-2 (in-flight task reconciliation, shipped) moves to
      docs/done/scheduler-task-reconciliation-{requirements,design}.md; FR-1
      (new-goal auto-dispatch, still undecided) becomes a small standalone
      docs/todo/scheduler-new-goal-dispatch-requirements.md instead of staying
      bundled with a doc that's mostly done.
    - Compress validator-test-script-narrative-output-issue.md's six
      ad-hoc "第N轮更新" paragraphs crammed into one status line into a scannable
      timeline table; moved the task 2084590a benchmark evidence into §1 where
      the other repro examples live instead of leaving it stranded in the header.
    - implementation-gap-analysis.md: logged two new gaps found today (no
      pre-Coder review of Planner's output; node execution still depends on
      native Dynamic Workflow) plus the architecture.md §10.1 staleness itself,
      per that doc's own "edit in place" maintenance convention.
    - Updated the doc-path references left in src/task_execution.py and
      src/task_reconciliation.py docstrings to point at the new locations.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse File »
  • Merges the fixed-flow change (Planner -> Validator -> Coder -> Validator),
    universal per-org-agent self-planning, node-level validator skill, and
    frontend dynamic/historical graph asks into one requirements doc, folding
    in the P0 resume-artifact bug and the P2 test_script structural-fix
    placeholder that were blocking on the same design. Records the user's
    2026-08-08 decision to merge all four org stages into one work_graph_run
    (scheme A) rather than cross-graph routing (scheme B), plus the concrete
    schema conflicts that decision surfaces (work_graph_run.org_node's single
    value + unique-active-run index) for Phase 2's SDD to resolve.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse File »
  • work-graph-partial-artifact-persistence and work-graph-self-planning-
    and-loop-back (requirements + design) are all shipped and tested;
    move them out of docs/todo/ and fix up the docs/todo/*.md and
    src/*.py path references that pointed at their old location.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse File »
  • Real end-to-end verification of Work Graph self-planning + loop-back
    (task 2084590a) hit the narrative-output problem again -- this time on a
    self-planned benchmark node, not test_script, disproving the earlier
    "BRD/PRD/SDD/Benchmark won't recur" hypothesis in validator-test-script-
    narrative-output-issue.md. The judge caught it once (round 3) but couldn't
    force a fix; the loop_back retry limit correctly exhausted and blocked the
    task cleanly instead of hanging or crashing.
    
    Also drafts org-graph-as-work-graph-unified-loop-requirements.md: extending
    today's Work-Graph-internal judgment/on_fail/loop_back mechanism up to the
    Org Graph itself, so Coder doesn't start from an unreviewed Planner output
    and a Validator FAIL can route to a precise node instead of a whole phase.
    Flags the real hard part (Planner/Coder each plan their own graph_manifest,
    so node ids don't share an address space across the org boundary) as the
    first open question, not yet implemented.
    
    Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
    bboonnee authored
     
    Browse File »
  • …4843-main-checkout-drift
    graphlemon authored
     
    Browse File »