System-design authority for bewith-dev. Use proactively for changes touching microservice boundaries, the Mongo/Aurora/Redis split, the Yii2 boundary, cross-service contracts, or scoped >20 files. Writes design docs; escalates to ADR for precedent-setting decisions.
Readiness gate for planning artifacts. Use proactively before a PRD moves draft to ready-for-rd, or a Design Doc moves draft to approved. Independently validates each against its template and checklist, blocking the transition on any P0 gap. The pre-build twin of process-guardian.
Privacy + data-protection authority β GDPR + Israeli privacy law, PII classification, consent, retention, user rights. Use proactively when a change collects, stores, exports, logs, or shares personal data, or adds a data flow. Advises on the legal/data duty; does not implement.
Definition-of-Done gate. Use proactively before closing tasks, marking PRs ready-for-review, or moving to Done. Verifies DoD (CU-id, lint/test/typecheck/build, no secrets, design-review); blocks if anything fails. Loaded at /done, step 13 of /continue, and by every Hard-Floor policy.
Product-judgment authority β is this worth building, business/ICP-aligned, what's the priority. Use proactively when product intent is unclear, features compete, or a PRD needs a product (not mechanical) read. Owns the AI-consumable PRDβDesign Doc chain; distinct from gatekeeper.