Skip to content

Add family closure scheduling, report workflow, and v0.2.0 docs - #2

Open
Zihao-Liu-Leo wants to merge 4 commits into
frenzymath:mainfrom
Zihao-Liu-Leo:main
Open

Add family closure scheduling, report workflow, and v0.2.0 docs#2
Zihao-Liu-Leo wants to merge 4 commits into
frenzymath:mainfrom
Zihao-Liu-Leo:main

Conversation

@Zihao-Liu-Leo

Copy link
Copy Markdown

Summary

This PR adds two optional, non-invasive capabilities on top of the existing Iteris CLI (monitor, doctor, run, evolve, …):

  • iteris family — joint scheduling and shared verified-fact pool for parallel sibling North-Star closure projects (wrapper .iteris/FAMILY.json, sibling markers, max_concurrent scheduling via subprocess iteris run).
  • iteris report — draft/build versioned LaTeX reports from verified project evidence, plus dashboard Reports UI.

Version bumped to 0.2.0. English/Chinese READMEs, docs/user-guide.md, and GUIDE_INDEX document both features. User-facing docs order: Evolve → Family Closure → Reports, matching the natural workflow (generalize from one verified result, then parallel sibling closure).

Design constraints (non-breaking)

  • cli.py: only +2 lines to register family; report typer unchanged from prior integration pattern.
  • Family scheduling calls iteris run via subprocess — no changes to commands/run.py state machine.
  • Family goal context uses lazy import in goal/prompt.py.
  • memory/family.py extended (closure sibling markers + .iteris/FAMILY.json) without removing evolve behavior.

Test plan

  • pytest tests/test_monitor_command.py tests/test_doctor_command.py tests/test_report_command.py tests/test_goal_command.py tests/test_family_state.py tests/test_family_closure.py tests/test_family_memory.py63 passed
  • Smoke: family init/status/schedule --dry-run/export/pool + legacy doctor, report doctor, status, run --print
  • iteris --help still lists monitor, doctor, report, evolve, family

Commits

  1. Add family closure scheduling and report workflow
  2. Document family/report in README; bump to 0.2.0
  3. Put Evolve before Family Closure in user-facing guides

Made with Cursor

Zihao-Liu-Leo and others added 4 commits July 1, 2026 03:13
Introduce iteris family for parallel sibling North-Star runs with shared verified-fact pool and max_concurrent scheduling, plus iteris report for LaTeX/PDF drafts from verified project evidence. Existing monitor, doctor, run, and evolve commands remain unchanged; family integrates via a thin CLI typer and lazy goal-prompt context.

Co-authored-by: Cursor <cursoragent@cursor.com>
Expose iteris family and iteris report in English and Chinese READMEs, user guide, and GUIDE_INDEX so open-source users can discover the new workflows.

Co-authored-by: Cursor <cursoragent@cursor.com>
Add family closure scheduling and report workflow
Match the natural workflow order: generalize from one verified result first, then parallel sibling North-Star closure.

Co-authored-by: Cursor <cursoragent@cursor.com>
LehengChen added a commit to LehengChen/iteris-dev that referenced this pull request Jul 26, 2026
…workflow

Merges frenzymath#2 (Zihao-Liu-Leo). The report half of that PR is
already present in main via local development (identical tree), so this
merge effectively lands the family-closure feature: iteris family init/
status/schedule/export/pool, shared verified-fact pool, sibling markers,
and .iteris/FAMILY.json wrapper scheduling with max_concurrent.

Supersedes PR frenzymath#1, whose family files appear here in revised form.
LehengChen added a commit to LehengChen/iteris-dev that referenced this pull request Jul 26, 2026
PR frenzymath#2 dropped the mode bit (100755 -> 100644) as an unintended side effect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant