[Project Name] Onboarding

This repository is now in active downstream onboarding mode.

Purpose: move from template export into an operating project with PM, AM, CM, SM, and OM discipline, durable evidence, and milestone execution.

Current Status

Establish a filtered vendored template snapshot and perform the first controlled export using docs/downstream-onboarding-playbook.md.
Run and complete docs/operator-onboarding-checklist.md with the Operator.
Finalize project-specific sections in MEMORY.md:
- project purpose
- architecture
- environments
- safety constraints
Open first milestone plan in minions/plans.
Track decisions and handoffs in the active daily thread under minions/chat/.
Keep ROADMAP.md, TODO.md, and CHANGELOG.md updated during execution.
Use docs/downstream-upgrade-playbook.md for later template updates.

Role context policy:

each minion may maintain role-specific context in its own file under minions/roles/ (for example: PM.md, AM.md, CM.md, SM.md, OM.md)
no minion may alter existing base guardrails/rules without explicit Operator approval

Git handoff policy:

no minion may hand off workflow state, implementation state, or decision-ready work to another minion or the Operator until at least one local commit captures the current change set
a local commit is the minimum handoff checkpoint for every minion role
if the next owner is operating on a different computer, handoff requires both a commit and a push so the work is actually available to them
the Operator decides the default handoff sync mode for each role: commit-only or commit-and-push
the default may differ by role, but commit-and-push is mandatory whenever the next owner is on a different computer
if remote-visible handoff is required, follow the repo's PR/push policy

Default flow when the work changes architecture, system boundaries, data flow, major dependencies, or overall design direction:

Implementation-to-runtime flow inside an approved architecture:

Use this structure for actions requiring a decision or handoff:

DECISION:
RATIONALE:
ACTION NEEDED:

Optional sections when needed: RISK, BLOCKER, DEADLINE.

All minions must close work with a clear handoff packet in the active daily thread.

Required structure (in this exact order):

Hard rules:

No minion may mark work complete without naming the NEXT OWNER.
No minion may hand off work without meeting the active commit/push rule set by the Operator for that role and handoff.
No minion may accept handoff with ambiguous ownership.
If blocked, handoff is still required with a blocker packet and explicit owner for unblock.
PM must reject handoffs that do not include evidence and clear next-owner assignment.

This project is considered fully onboarded when all are true: