Skip to content
FractalOps

Research Astro/Starlight Workspaces

Research Astro/Starlight Workspaces

Section titled “Research Astro/Starlight Workspaces”

Research work is separate from project delivery as a product domain, but it is not a separate agent runtime. A user request creates one research mono repo, one Daytona workspace, and one Astro/Starlight documentation surface for that request, then runs through the same AgentSquad Daytona + LangGraph + mailbox + GitHub App PR loop as project delivery.

Contract

Section titled “Contract”
  • Template: research-team
  • Runtime kind: project_delivery
  • Issue sink: research_repo
  • Repository type: research_monorepo
  • Team contract: Studio Team Contract owns research role order, handoff graph, MCP/skill loadout, write policy, and PR submitter policy.
  • Workspace contract: .fractalops/research/contract.json
  • Base image: ghcr.io/yamonco/fractalops-research-starlight:latest
  • Package manager: pnpm

Research runs emit project_delivery so Daytona workspace allocation, LangGraph session state, retry/resume, task cards, mailbox handoff, and GitHub App PR submission stay on the existing AgentSquad rails.

Flow

Section titled “Flow”
  1. The user submits a question or target site from /research.
  2. inquirer creates three to five clarifying questions.
  3. The user’s answers become research tickets in the request mono repo.
  4. curator assigns work to scout, auditor, actor, and scribe.
  5. scribe updates Astro/Starlight through a pull request.
  6. tester verifies the Astro/Starlight preview and evidence links.
  7. committer merges accepted PRs.
  8. closer publishes DataHub/wiki lineage and closes the ticket.

Boundaries

Section titled “Boundaries”
  • Research repos are not project assembly repos.
  • Research teams must not create local-only runners, local-only repos, alternate workspace managers, or a second orchestration engine.
  • One research request maps to one Daytona workspace; role-specific work happens as AgentSquad slots/worktrees inside that workspace.
  • Research agents may use searxnggrid, agent-memory-archive, datahub, playwrightgrid, and suit.
  • Secrets from SUIT or target sites must never be written to Astro/Starlight or wiki facts.
  • Stale wiki findings must be refreshed through a linked research ticket and PR.