{
  "name": "exhaustive-srs",
  "goal": "Run an iterative map->acquire->evaluate->targeted-dispatch loop that builds an exhaustive Knowledge Matrix for a given topic (per-node >=0.85 completeness, overall >95% complete), then synthesize it into a comprehensive SRS document.",
  "status": "stopped",
  "schedule": null,
  "run_config": {
    "max_concurrent_agents": 4,
    "budget_tokens": 1000000000,
    "memory_namespace": "org:exhaustive-srs",
    "max_turns_per_message": 30
  },
  "roles": [
    {
      "id": "orchestrator",
      "title": "Orchestrator (Taxonomy & State Manager)",
      "type": "boss",
      "reports_to": null,
      "responsibilities": [
        "Generate a deeply nested Knowledge Matrix JSON tree from the initial topic, covering every sub-domain, competitor vector, technical requirement, and feature category",
        "Own the Knowledge Matrix as the sole source of truth for completeness stats — manage structure and state only, never edit content directly",
        "Translate Gap Analyzer deficiency reports into specific, targeted acquisition tasks for the Acquirer Swarm",
        "Dispatch and re-dispatch Acquirer agents per matrix node until the Gap Analyzer signals overall completeness above 95%",
        "Hand off the saturated Knowledge Matrix to the Architect for SRS synthesis once approved",
        "Never perform research or content writing itself — pure state and orchestration role"
      ]
    },
    {
      "id": "acquirer-swarm",
      "title": "Acquirer Swarm (Parallel Gatherers)",
      "type": "specialist",
      "reports_to": "orchestrator",
      "responsibilities": [
        "Execute targeted research queries assigned to specific Knowledge Matrix node IDs using web search, GitHub APIs, Arxiv, and competitor documentation",
        "Tag every gathered data chunk with the exact Matrix Node ID it targets",
        "Summarize raw findings into structured, source-cited data chunks — no synthesis or opinion, only verified facts",
        "Prioritize technical specificity (APIs, algorithms, rate limits, pricing models, schemas) over marketing language",
        "Report findings only to the Orchestrator, never directly to the Architect",
        "Re-run with narrower, more targeted queries when handed a deficiency directive"
      ]
    },
    {
      "id": "gap-analyzer",
      "title": "Gap Analyzer (Critic / Stats Engine)",
      "type": "reviewer",
      "reports_to": "orchestrator",
      "responsibilities": [
        "Never perform research — strictly evaluate the Knowledge Matrix data provided by the Orchestrator",
        "Score every node completeness from 0.0 to 1.0 based on depth, technical specificity, and cross-source verification",
        "Act as an aggressive technical auditor: score fluff or marketing-only content 0.1 and demand actionable engineering specifics (APIs, algorithms, distinct features)",
        "Produce a Deficiency Report listing every node below the 0.85 completeness threshold with an exact search directive to close the gap",
        "Compute and report the overall Matrix completeness percentage after every evaluation pass",
        "Only approve handoff to the Architect once overall completeness exceeds 95%"
      ]
    },
    {
      "id": "architect",
      "title": "Architect (SRS Synthesizer)",
      "type": "specialist",
      "reports_to": "orchestrator",
      "responsibilities": [
        "Wait for Gap Analyzer approval of Matrix saturation before starting synthesis",
        "Parse the completed Knowledge Matrix node by node into a single coherent SRS document",
        "Produce Functional Requirements, Non-Functional Requirements, System Architecture, Database Schemas, API endpoint designs, and feature-level UI/UX logic",
        "Never fetch new data or fill gaps itself — flag any residual gap back to the Orchestrator instead of guessing",
        "Ensure every requirement in the SRS traces back to a specific Matrix node and its cited sources"
      ]
    }
  ]
}