Intent
Validate that one planner can coordinate a single initiative spanning tuber-service and peeler while each repository retains its own native ticket, project policy, candidate, delivery, and acceptance.
Scope
- Create shared initiative context without collapsing the two repositories into one execution unit.
- Promote repository-specific assignments with independent authority ceilings and native tickets.
- Run separate project-serial worker claims and Agent Scripts delegations.
- Preserve causal links between the initiative and both deliveries.
- Audit and accept each repository independently, including partial success or blocking in only one project.
- Demonstrate restart/recovery from the Git mailbox across planner and worker tasks.
Non-goals
Do not add parallel project scheduling, cross-repository atomic commits, centralized source control, automatic merge, or a portfolio database.
Done definition
A real Tuber/Peeler initiative produces two independently reviewable native deliveries with explicit per-project acceptance, while the planner can explain the shared outcome and recover all coordination state without relying on task transcripts.
Source
See Atelier as a Skill, the Implementation Plan, and epic #772.
Proposal key: CROSS-PROJECT. This is post-v0 product validation. Native dependencies are authoritative.
Intent
Validate that one planner can coordinate a single initiative spanning
tuber-serviceandpeelerwhile each repository retains its own native ticket, project policy, candidate, delivery, and acceptance.Scope
Non-goals
Do not add parallel project scheduling, cross-repository atomic commits, centralized source control, automatic merge, or a portfolio database.
Done definition
A real Tuber/Peeler initiative produces two independently reviewable native deliveries with explicit per-project acceptance, while the planner can explain the shared outcome and recover all coordination state without relying on task transcripts.
Source
See Atelier as a Skill, the Implementation Plan, and epic #772.
Proposal key:
CROSS-PROJECT. This is post-v0 product validation. Native dependencies are authoritative.