Anti-patterns

Things that look helpful but create a second orchestration system in the target repo. Avoid them in Fulreach and other Mainark target repos.

Do not add to target repos

Anti-pattern	Why it's wrong
`.mainark/plans/FUL-*.md`	Duplicates Linear `## Mainark plan`; drifts
`.mainark/batches/*.json`	Duplicates Linear blockers + wave manifest
`*-plan.md` runbooks for waves	Mainark CLI + Linear are the runbook
`scripts/mainark-sequences-*.sh`	Wraps `mainark implement`; use CLI directly
`sync--linear.mjs`	Plans/blockers belong in Linear MCP or future `mainark linear sync-plan`
Markdown TODO lists for agent deps	Use Linear `blockedBy` or Beads (`bd`) in agent scope

Allowed in `.mainark/`

File	Role
`epics.json`	Which epics are active for queue commands
`parallel.json`	Runtime worktree registry (generated)
`issue.json`, `implement-*.md`, `logs/`	Per-run agent state (generated)

Agent rules

Linear for tickets, blockers, epic plans
mainark implement for parallel execution — not custom bash orchestrators
mainark parallel clean before a fresh wave — not hand-deleted registries
mainark fix only in the correct worktree from mainark parallel paths

When Mainark is missing a feature

Extend Mainark or ask the operator — do not bolt workarounds onto the target repo.

Examples: plan sync to Linear, multi-epic coordinator, cloud runner — these belong in the Mainark repo.

Legacy exception