Skip to content

feat: add iteris family closure for parallel sibling North-Star tracks - #1

Closed
Zihao-Liu-Leo wants to merge 1 commit into
frenzymath:mainfrom
LehengChen:feat/family-closure
Closed

feat: add iteris family closure for parallel sibling North-Star tracks#1
Zihao-Liu-Leo wants to merge 1 commit into
frenzymath:mainfrom
LehengChen:feat/family-closure

Conversation

@Zihao-Liu-Leo

Copy link
Copy Markdown

Introduce family workspace scaffolding, shared verified-fact pool, joint tmux scheduling, and goal-prompt context injection so operators can run related problems (e.g. 2.15–2.19) under one FAMILY.json with max_concurrent control. Includes operator guide, QA testing guide, and 14 regression tests.

Introduce family workspace scaffolding, shared verified-fact pool, joint tmux
scheduling, and goal-prompt context injection so operators can run related
problems (e.g. 2.15–2.19) under one FAMILY.json with max_concurrent control.
Includes operator guide, QA testing guide, and 14 regression tests.

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

Add family closure scheduling and report workflow
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

Copy link
Copy Markdown
Collaborator

Closing as superseded by #2.

Both PRs implement the same family-closure feature from the same author, and #2 is a strict superset: the four family modules here (`family.py`, `family_pool.py`, `family_scaffold.py`, `commands/family.py`) all reappear in #2 in revised form, along with the report workflow. Merging both would replay the same feature twice, so the work from this PR lands via #2 rather than being dropped.

Thanks for the contribution — it is preserved in the newer PR.

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.

2 participants