EduardoRemedios

Close implementation work against an approved Factory pack. Use when Codex is asked to verify execution after human Go, compare a code/doc diff to the approved envelope and micro-sprints, prepare execution completion notes, check residual risk, or decide whether a completed implementation is ready for project-specific merge gates.

Consolidate a Factory pack during Stage J. Use when Codex is asked to create or repair PACK_MANIFEST.md, create or repair PACK_CHECKLIST.md, verify required pack artifacts are present and non-empty before Stage I2, instantiate the Purple Gate checklist, or prepare a completed pack for pack-lint.

Perform Factory Purple Gate adjudication against evidence. Use when Codex is asked to review Stage D or Stage I2, decide PASS, CONDITIONAL PASS, or FAIL, evaluate PACK_CHECKLIST.md, resolve Red/Blue disputes, assess whether scope expansion remains unapproved, or produce PACK_AUDIT_REPORT.md from completed Factory artifacts.

Coordinate a Factory run from raw brief through Stage I2. Use when Codex is asked to initialize a Factory run, run Stage A, create or repair run-root evidence, enforce Factory read order, choose PLANNING_ONLY versus EXECUTION_ENABLED posture, coordinate the full stage flow, or prepare a pack for human review without executing implementation.

Run a full Factory execution-enabled pipeline A→I2→POST_GATE with EXECUTION_PROMPT and HUMAN_GO.

Run a full Factory planning-only pipeline A→I2 with stage dispatch prompts and gate enforcement; EXECUTION_MODE=PLANNING_ONLY.

Dispatch the Intent Contractor (Stage A) for a Factory run using the blueprint dispatch prompt and allowed writes.

Run knowledge lint for a Factory run and block Stage A until PASS; persist output to run root.

Use to red-team a Factory V3 discovery output, candidate mission contract, long-running build plan, overnight Codex plan, or mission envelope before execution. Finds weak assumptions, missing authority, over-scoping, verification gaps, fallback triggers, and human-decision risks. Do not use to implement changes.

Use when turning a vague idea, product direction, long-running build request, overnight Codex goal, or "what am I missing" prompt into a non-executing Factory V3 discovery output, option set, execution-readiness assessment, and candidate mission contract. Do not use for already-bounded code changes that can proceed directly under an approved execution envelope.