Operations Board

Define the smallest useful telemetry layer before adopting a full external stack: health checks, structured logs, key counters, and simple internal status views. EXPECTED OUTPUT: A build plan for basic telemetry improvements with implementation order. DESTINATION SURFACE: Tasks + linked strategy brief. REVIEW OWNER: TC FALLBACK IF BLOCKED: If metrics scope is unclear, propose the smallest high-signal set first.

EXPECTED OUTPUT: Executor-owned message generation and conversation-management workflow that moves qualified leads toward a booked strategy call. DESTINATION SURFACE: Nexus outreach execution task + conversation-state spec. REVIEW OWNER: Taylor Cunningham FALLBACK IF BLOCKED: Escalate only if conversation-state logic or intent classification becomes too ambiguous to handle with the planner plus executor chain. RESEARCH - Use the required tone: consultative, professional, non aggressive. - Use the required message structure: acknowledge problem, show expertise, offer insight, invite conversation. BUILD - Define executor-owned state transitions for Initial message sent, Lead response detected, Intent classification, Problem exploration, Solution positioning, Call invitation, Meeting booked. - Define interaction-history tracking requirements. REVIEW - Verify every lead interaction can be traced from first message to meeting booked. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Create the durable data model for Workflow, WorkflowRun, WorkflowPhaseRun, WorkflowArtifact, WorkflowAlert, WorkflowApprovalLink, and WorkflowSendLink. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Implement run/phase/worker lifecycle truth with explicit statuses, transitions, and invalid-state protection. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Build the execution boundary layer: timeouts, retries, kill semantics, no-op detection, and stale-run detection. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Create the aggregation barrier that waits for parallel workers, dedupes, validates, persists outputs, and decides phase completion. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Make artifacts and provenance first-class so every lead, draft, approval, send, and reply has inspectable lineage. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Implement message-prep objects, 3 draft variants, judge scoring, selected draft logic, and disqualification path. Workflow Contract: EXPECTED OUTPUT: First reviewable outreach-message batch grouped by angle and tied to real lead context DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Audience context, angle selection, objections, and proof points worth using. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the chosen angle into concrete message assets tied to real context. Required output: First reviewable outreach-message batch grouped by angle and tied to real lead context. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check accuracy, tone, relevance, and whether the messages are send-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Govern approval, send-state, and browser execution through explicit state machines and a bounded deterministic action lane. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Turn /workflows into mission control for run lifecycle, phase truth, artifacts, approvals, send-state, and recovery. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Keep the program moving continuously: sequence waves, track blockers, verify shipped state, and keep the campaign aligned to the north star until the orchestration spine and workflow command surface are world-class. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Gather data sources for sentiment analysis, including news articles, social media posts, and financial reports related to gold trading. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

List possible sources for sentiment analysis data related to gold trading. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Urgent rule: one owner, helpers optional, no silent drift EVIDENCE: (fill) VERIFICATION: (fill)

Define which failure conditions matter, who owns them, how alerts should route, and how to avoid spam before implementing tools like Alertmanager. EXPECTED OUTPUT: A practical alerting decision framework and escalation path. DESTINATION SURFACE: Tasks + notifications/brief evidence. REVIEW OWNER: TC FALLBACK IF BLOCKED: If tool choice is premature, lock routing logic and thresholds first.

Turn the deployment strategy into an implementation sequence covering lint/build/test automation first, then controlled deploy automation. EXPECTED OUTPUT: A staged CI/CD plan with practical first steps. DESTINATION SURFACE: Tasks + linked strategy brief. REVIEW OWNER: TC FALLBACK IF BLOCKED: If infra access is missing, produce repo-level workflow scaffolding and host-side prerequisites separately.

Document the minimum viable resilience baseline: backups, restore testing, restart behavior, and failure recovery expectations for Nexus/OpenClaw. EXPECTED OUTPUT: A resilience checklist and rollout sequence. DESTINATION SURFACE: Tasks + linked strategy brief. REVIEW OWNER: TC FALLBACK IF BLOCKED: If current backup state is unknown, produce a current-state gap list and recovery plan.

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Created by automated smoke test. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Add stale-run, no-output, approval bottleneck, send mismatch, duplicate overload, evidence-missing, and false-completion alerts. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Harden for continuous operation with polling, live updates, comparisons, and proof-backed verification tests. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Review the Prisma schema additions for the run, phase, artifact, alert, approval, and send links to ensure they meet the project's requirements and align with the end goals. Provide feedback and approval for the schema changes. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Implement the backend logic to support the new Prisma schema models for run, phase, artifact, alert, approval, and send links. Update the existing codebase to handle the new data structures and ensure workflow execution is trustworthy, observable, recoverable, approval-aware, and provably complete. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Create a migration plan to update the database schema for the new Prisma schema models. Generate the necessary migration files and apply them to the database. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Create a detailed plan for migrating existing workflow records to the new schema and ensure backward compatibility. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Identify all possible run statuses, define legal transitions between them, and implement guards to enforce these transitions. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Create rules or guards for each run status transition to ensure they are valid and safe. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Document the legal transitions and guards for run statuses for reference and implementation. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Outline the steps required to preprocess the data before sentiment analysis. This includes cleaning the data, normalizing text, and any other necessary preprocessing steps. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Create rules or guards for each run status transition to ensure they are valid and safe. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Document the legal transitions and guards for run statuses for reference and implementation. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Clean and preprocess the collected data to make it suitable for sentiment analysis (e.g., tokenization, removing stop words, handling missing values). Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

List all possible run statuses and their transitions. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Create rules or guards for each run transition to ensure they are valid and safe. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the architecture and workflow for the sentiment analysis pipeline, including data ingestion, processing, and output stages. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Clean and preprocess the collected data to make it suitable for model training, including text normalization, tokenization, and handling missing values. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

For each phase state, define which transitions are allowed (e.g., from pending to running, from running to succeeded or failed, etc.). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

For each transition, define the conditions that must be met for the transition to occur (e.g., a phase can only transition from running to succeeded if all its steps have completed successfully). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Specify which transitions between run statuses are allowed (e.g., pending → running → succeeded). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

List and define all possible statuses that a workflow phase can have (e.g., pending, running, completed, failed, etc.). Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define the conditions that must be met for each legal transition to occur. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Specify which transitions between phase statuses are allowed (e.g., pending → running → completed). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define the conditions that must be met for each legal transition between phase statuses. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Determine and document the allowed transitions between each phase status identified in the previous task. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop and implement the logic to enforce the legal transitions between phase statuses, preventing invalid state changes. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Specify which transitions between run statuses are allowed (e.g., pending → running, running → succeeded/failed, running → cancelled). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define the conditions that must be met for each legal transition between run statuses (e.g., can only transition to succeeded if all phases completed successfully). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Specify which transitions between phase statuses are allowed and under what conditions. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define the conditions and checks that must be met for each legal phase transition to occur. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Specify which transitions between run statuses are allowed (e.g., pending → running → succeeded, or pending → running → failed). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define the conditions that must be met for each transition between run statuses to occur. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

For each phase status, define which transitions are allowed (e.g., pending → running, running → completed, etc.). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

For each transition, define the conditions that must be met for the transition to occur (e.g., a phase can only transition from running to completed if all tasks are done). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define the complete set of legal run statuses (e.g., pending, running, succeeded, failed, timed_out, etc.) Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Create a state machine diagram or table showing allowed transitions (e.g., pending → running, running → succeeded, running → failed) Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

For each transition, define the conditions that must be met (e.g., a run can only transition from pending to running if a worker is available) Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

For each status identified, define which transitions are allowed (e.g., pending → running, running → completed, etc.). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Create logic to enforce the defined transitions, ensuring that only valid transitions can occur. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Specify which transitions between phase statuses are allowed (e.g., pending → running → succeeded, pending → running → failed) Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define the conditions that must be met for each legal transition to occur (e.g., can only transition from running to succeeded if all checks pass) Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Implement the actual timeout mechanism in the worker code, ensuring it triggers the timed_out state. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define what happens when a worker enters the timed_out state, including any cleanup or notification logic. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Analyze the collected gold market data to identify trends and patterns. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Generate buy/sell/hold recommendations based on market data analysis. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Analyze historical and current gold market data to identify trends, patterns, and key indicators that can inform trading decisions. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop and implement algorithms to generate buy/sell/hold trading signals based on market data analysis and sentiment analysis. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Assess each identified source for relevance, reliability, and accessibility. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Collect historical gold market data from identified sources, ensuring data quality and completeness. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Gather relevant news articles and updates that could impact gold prices. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Combine data from different sources (market data, technical indicators, news sentiment) into a unified format. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Monitor market news for gold trading to identify trends and sentiment shifts. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Gather data from various sources for sentiment analysis, including news articles, social media posts, and financial reports. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Perform sentiment analysis on the collected data using natural language processing techniques. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Generate a report summarizing the sentiment analysis results and provide actionable insights. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Gather data from relevant sources (news, social media, financial reports) for sentiment analysis. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Process the collected data to determine sentiment (positive, negative, neutral). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Compile the sentiment analysis into a report format for review. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Determine the scope of sentiment analysis, including data sources, timeframes, and key metrics to be analyzed. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and select the tools and technologies needed for sentiment analysis, including APIs, libraries, and data processing tools. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the data pipeline for sentiment analysis, including data ingestion, preprocessing, analysis, and reporting. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Gather data from various sources such as news articles, social media, and financial reports that can be used for sentiment analysis. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Clean and preprocess the collected data to make it suitable for analysis. This includes removing noise, normalizing text, and handling missing values. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Identify and evaluate tools for sentiment analysis to determine the best fit for the project. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Choose an appropriate model for sentiment analysis. This could be a pre-trained model or a custom model that needs to be trained. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Outline the steps for processing and analyzing sentiment data, including data collection, preprocessing, and analysis. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop or integrate a model for sentiment analysis that can process news articles and other text data. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Gather relevant news articles, social media posts, and other textual data that could influence gold prices. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Use NLP techniques to analyze the collected data and determine the overall sentiment (positive, negative, neutral). Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Compile the analysis into a report that can be used to inform trading decisions. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Gather data from relevant sources for sentiment analysis, including news articles, social media posts, and financial reports related to gold trading. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Analyze the collected sentiment data to determine the overall market sentiment towards gold trading. This includes identifying trends, key themes, and sentiment scores. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Determine the scope of sentiment analysis, including data sources, timeframes, and key metrics to be analyzed. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Generate a concise report summarizing the sentiment analysis results, including key findings, trends, and recommendations for trading decisions. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and select appropriate tools and technologies for sentiment analysis, including NLP libraries and data processing frameworks. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and identify reliable sources for sentiment data related to gold trading. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the data pipeline for sentiment analysis, including data ingestion, preprocessing, analysis, and reporting stages. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the architecture and workflow for processing sentiment data. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and identify reliable sources for sentiment data related to gold trading. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop and train a sentiment analysis model tailored for gold trading news. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Define the key metrics and indicators that will be used to analyze sentiment data. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop the algorithm or model that will be used to analyze sentiment data. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Determine where we will collect sentiment data from (e.g., news articles, social media, financial reports). Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Implement the collection of sentiment data from the identified sources. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Clean and preprocess the collected data to make it suitable for analysis. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Gather relevant sentiment data from news articles, social media, and other sources related to gold trading. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Analyze the collected sentiment data to determine overall market sentiment towards gold trading. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Generate a report summarizing the sentiment analysis results, including key findings and recommendations. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and identify reliable data sources for sentiment analysis, including news APIs, social media platforms, and financial news websites. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the architecture and workflow for the sentiment analysis pipeline, including data ingestion, processing, and storage. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop the module responsible for ingesting data from identified sources into the sentiment analysis pipeline. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Find and list reliable sources for sentiment data related to gold trading. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and list potential sources for sentiment data relevant to gold trading, including news outlets, financial blogs, and social media platforms. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Outline the methodology for analyzing sentiment data, including tools and techniques. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Outline the methodology for analyzing sentiment data, including the tools, techniques, and algorithms to be used. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop the pipeline to process and analyze sentiment data. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Create a pipeline for collecting, processing, and analyzing sentiment data, ensuring it integrates with the existing data infrastructure. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and identify reliable sources for sentiment data related to gold trading. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Outline the technical approach and pipeline for analyzing sentiment data. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop or integrate a machine learning model for sentiment analysis. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Identify and list potential data sources for sentiment analysis, including news APIs, social media platforms, and financial news websites. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and list potential data sources for sentiment analysis, including news APIs, social media platforms, and financial news websites. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and select appropriate tools and libraries for sentiment analysis, such as Natural Language Processing (NLP) libraries and sentiment analysis APIs. Workflow Contract: EXPECTED OUTPUT: Working implementation or systems change with verification notes and known gaps DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, return the best partial implementation, exact failing step, logs/proof, and the smallest recovery move Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Requirements, constraints, failure mode, dependencies, and existing system behavior. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Implement the actual code, system change, fix, or configuration with visible output. Required output: Working implementation or systems change with verification notes and known gaps. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check correctness, verification quality, regressions, and readiness to ship. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Assess available tools and libraries for sentiment analysis, such as VADER, TextBlob, and custom machine learning models. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the architecture and workflow for the sentiment analysis pipeline, including data ingestion, processing, and visualization. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Outline the steps for the sentiment analysis pipeline, including data collection, preprocessing, analysis, and reporting. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and list potential data sources for sentiment analysis, including news APIs, social media platforms, and financial news websites. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Gather data from relevant sources for sentiment analysis, including news articles, social media posts, and financial reports related to gold trading. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Evaluate and select appropriate tools and libraries for sentiment analysis, such as NLTK, TextBlob, or custom models. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Analyze the collected sentiment data to determine the overall market sentiment towards gold trading. This includes identifying trends, key topics, and sentiment scores. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the architecture and workflow for the sentiment analysis pipeline, including data ingestion, processing, and output. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Generate a concise report summarizing the sentiment analysis results, including key findings, trends, and recommendations for trading decisions. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and identify reliable sources for sentiment data related to gold trading. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the technical pipeline for collecting, processing, and analyzing sentiment data. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and list potential data sources for sentiment analysis, including news APIs, social media feeds, and financial news websites. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Implement the data collection mechanism to gather sentiment data from identified sources. Workflow Contract: EXPECTED OUTPUT: Concrete reviewable artifact attached to the task or project DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Relevant facts, constraints, examples, and evidence needed to avoid low-quality execution. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Produce the concrete artifact, not just commentary about the artifact. Required output: Concrete reviewable artifact attached to the task or project. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check readiness, quality bar, and whether exact fixes are clear if not ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Evaluate and select tools/technologies for sentiment analysis, such as NLP libraries, machine learning models, or cloud-based sentiment analysis services. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and identify reliable sources for sentiment data related to gold trading. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Outline the data flow and processing steps for the sentiment analysis pipeline, including data ingestion, preprocessing, analysis, and reporting. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Design the architecture and workflow for processing sentiment data. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Develop and train a sentiment analysis model tailored for gold trading news. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Identify and list potential data sources for sentiment analysis, including news APIs, social media platforms, and financial news websites. Workflow Contract: EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes DESTINATION SURFACE: Campaign Assets (linked Brief) REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch. Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)

Research and evaluate available tools and libraries for sentiment analysis, such as NLTK, TextBlob, VADER, and transformer-based models. Workflow Contract: EXPECTED OUTPUT: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation DESTINATION SURFACE: Task-linked Brief or Campaign Assets REVIEW OWNER: TC FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective Adaptive Three-Phase Framework: PHASE 1 — RESEARCH Objective: Claims, counterclaims, sources, contradictions, and decision tradeoffs. Required output: Evidence-backed findings, key constraints, and the best recommendation for the task. Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation. PHASE 2 — BUILD Objective: Turn the findings into a brief someone can make a decision from immediately. Required output: Decision-grade research brief with findings, evidence, tradeoffs, and recommendation. Sub-agent standard: Build runs must return the actual artifact/change plus verification notes. PHASE 3 — REVIEW Objective: Check source quality, uncertainty handling, and whether the recommendation is decision-grade. Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready. Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely. Cross-Phase Delegation Rule: - Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work. - If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly. Definition of Done: - Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases - Produce the named output - Link or attach the artifact where stated - Add EVIDENCE and VERIFICATION before REVIEW/DONE - Keep scope tight and reviewable EVIDENCE: (fill) VERIFICATION: (fill)