searchpo-full-flow

Searchpo Full Flow

This is the visible skill wrapper for the shared /searchpo-full-flow command. Use searchpo-main-agent as the lead, keep research with searchpo-research-agent, and keep provider/render/publish execution with searchpo-impl-agent.

Agent-Team Requirement

For Codex runs, selecting this skill or writing owner labels into main_task_plan.json is not enough to prove delegation. When the current host exposes a subagent or agent-team runtime, explicitly spawn or assign:

Use the searchpo-main-agent as lead. Do not run research and implementation in parallel. First spawn or assign only searchpo-research-agent for AnySearch-first source discovery/extraction, GitHub API/README evidence, FactBank/TopicBrief, cross-check tasks, and only supporting DeepWiki repo context when useful. Wait until the main agent verifies cross_check_review.status == pass and research_sufficient == true, then spawn or assign searchpo-impl-agent for provider, render, audit, and Douyin tasks. The main agent must not run implementation commands itself; it verifies artifacts and makes the final release decision.

If the host cannot spawn or assign teammates, say that before running the flow, follow the same ownership split manually, and report the run as manual fallback, not as a spawned agent-team run.

When spawned teammates are available, use the phased runtime so each teammate owns a real command boundary:

python3 agent_harness/run_agent_loop.py --topic "topic" --mode provider --stop-after research_enrichment --delegation-mode spawned_subagents --delegation-agent searchpo-research-agent --delegation-proof "<host-subagent-id>"
python3 agent_harness/run_agent_loop.py "<run_dir>" --mode provider --resume-from 4 --stop-after main_task_plan --delegation-mode spawned_subagents --delegation-agent searchpo-main-agent --delegation-proof "<host-subagent-id>"
python3 agent_harness/run_agent_loop.py "<run_dir>" --mode provider --resume-from 5 --delegation-mode spawned_subagents --delegation-agent searchpo-impl-agent --delegation-proof "<host-subagent-id>"

When using the synchronous shell wrapper, keep the default --delegation-mode single_harness or explicitly set SEARCHPO_DELEGATION_MODE=manual_fallback; do not call that a spawned team run.

Command Choice

• Topic-only widesearch with publishable local render:

SEARCHPO_TOPIC="topic to investigate" npm run e2e:provider

• Direct link:

SEARCHPO_LINK="https://github.com/owner/repo" npm run e2e:provider

• Topic with canonical evidence URL:

SEARCHPO_TOPIC="topic" SEARCHPO_TOPIC_URL="https://example.com/source" npm run e2e:provider

• Live Douyin publish only after an explicit current-run user request:

SEARCHPO_TOPIC="topic to investigate" npm run e2e:live

Use npm run e2e only for no-provider contract wiring checks, and still pass SEARCHPO_TOPIC, SEARCHPO_LINK, or SEARCHPO_TOPIC_URL. The legacy source-registry sweep requires explicit SEARCHPO_ENABLE_DAILY_RADAR=1.

Required Flow

1. Establish the delegation mode: spawned/assigned sequential agent team when the host supports it, otherwise manual fallback with the same ownership split.
2. Inspect capability availability with python3 scripts/agent_capabilities.py --profile all --format text; do not print .env values.
3. Assign evidence/research to searchpo-research-agent only: canonical URL detail, GitHub API/README for GitHub repos, AnySearch-first supplemental search/extract, FactBank, TopicBrief, enriched cross-check, and only supporting DeepWiki repo context when useful. Do not let DeepWiki-only notes count as completed research.
4. Stop at the research barrier. The main agent must verify widesearch_strategy.json, anysearch_research.json, raw AnySearch search/extract files, fact_bank.json, topic_brief.json, and cross_check_review.json before implementation starts.
5. Only after cross_check_review.status == "pass" and research_sufficient == true, assign provider/render/publish execution to searchpo-impl-agent: DeepSeek, Gemini scoring/TTS/audit, Remotion render, deterministic media audit, final artifact binding, and Douyin adapter/live checks.
6. Main must not run provider/render/publish commands when searchpo-impl-agent is available. Main verifies artifacts before declaring success, and includes the actual delegation mode in the final report.

Verification

After the command finishes, read runtime/latest_run.txt and verify the run directory:

• agent_run.json
• main_task_plan.json
• runtime_contract.json
• research_barrier.json
• evidence_bundle.json
• widesearch_strategy.json
• anysearch_research.json
• fact_bank.json
• topic_brief.json
• research_brief.json
• cross_check_review.json
• provider/live: script.json, scene_plan.json, video_spec.json, render_payload.json, render_input_manifest.json
• provider/live: implementation_loop.json, deepseek_polish.json, content_score.json, voiceover_manifest.json, video_optimization_loop.json, visual_audit_deterministic.json, gemini_visual_audit.json
• provider/live: artifact_manifest.json, release_gate.json, delivery_package.json, run_final.json, post/douyin_upload_check.json
• live: post/post_publish_verification.json

submitted is not live success. Live success requires remote identity verification. Always report agent_run.json.delegation.mode; owner labels in main_task_plan.json are not execution proof.