Read Project setup contract, Backend contract, and Purpose and architecture contract completely. For a Python project also read Python QC profile completely; for a TypeScript or JavaScript project also read TypeScript QC profile. Read both for a mixed Python/TypeScript project. Read only the applicable language profiles completely.

Detect Orca through its native environment and status surface; report unsupported or ambiguous environments. Check / separately from the upstream companion skill.

When watchdog readiness is in scope, check mature and dependencies separately from backend controls.

Use Orca's version-matched guide. Report the exact source separately from control discovery; an unrelated personal copy is not evidence.

Inspect knowledge, entry instructions, README, architecture reasons, backlog quality, E2E and acceptance mapping, language/build config, mature complexity and size linting, significant-code purpose, deterministic non-mutating QC, and unsandboxed Codex/Claude Code/OpenCode posture. Do not create a backend fixture document in ordinary projects.

If tracked repair is required, explain it and use a separate branch based on up-to-date ; never mix setup repair into the current feature branch. Personal configuration changes require explicit confirmation.