Handoff: Inaugural Orchestrator Integration Test
Context: The technical "Trinity Build" of the spec-agentic-source-orchestrator is finished. Infrastructure (Codex), Intelligence (Claude), and the State-Machine (Integration) are all versioned and passing mocked tests. The mission for the next session is to execute the first Live End-to-End Ingestion Run.
1. Prerequisites (Credentials Required)
Before starting, ensure the following environment variables are set in the shell (DO NOT COMMIT THESE):
FIRECRAWL_API_KEY: For crawling and mapping.SUPABASE_URL&SUPABASE_SERVICE_KEY: For vector storage and state tracking.OPENAI_API_KEY: For generating text-embedding-3-small vectors.
2. Test Target Selection
Choose a high-signal, atomic technical source.
- Primary Candidate: Firecrawl Documentation - Crawling
- Alternative: A specific technical blog post about MCP or Agentic RAG.
- Goal: Ingest ~5-10 high-quality chunks to verify the T5 (Verified) epistemic path.
3. The 8-Stage Execution Sequence
Execute the following tools via the vulture-ingest MCP server:
- Stage 1 (Propose):
propose_source_intake(Sethuman_approved: true). - Stage 2 (Map):
orchestrate_ingestion(Setdry_run: false). Verify URLs returned. - Stage 3 (Crawl):
execute_source_crawl(Setdry_run: false). Confirm Markdown retrieval. - Stage 4 (Index):
index_crawled_source. Confirm Supabasesource_chunkspopulation. - Stage 5 (Verify):
verify_source_index. Look forstatus: passedand any T3 warnings. - Stage 6 (Search):
semantic_search_sourceswith a specific query from the text to verify retrieval quality. - Stage 7 (Synthesize): Claude to draft a Permanent Note in
01_Wiki/based on retrieved chunks. - Stage 8 (Promote):
promote_synthesis_candidateto merge the draft with its validatedprovenanceblock.
4. Success Criteria
- [ ] Raw source stored in Supabase
source_pages. - [ ] Chunks embedded and searchable via vector query.
- [ ] Epistemic gate (T5) successfully identifies direct evidence.
- [ ] Final YANP note created in
01_Wiki/with a valid, auditableprovenanceblock.