Plans and code
Implementation plans and code changes that can be inspected in the repository.
Daedalus
Software-development factory built with Radi
Daedalus turns product intent, requirements, technical context and repository state into working software through staged execution, explicit artifacts, review and verification.
Inputs
What it works from
Daedalus starts from the actual software problem, not from a blank chat. Typical material includes product intent and requirements, existing repositories and code, architecture and technical constraints, issues and implementation plans, runtime, build and test evidence, and prior technical decisions.
Work and output
What it helps produce
Tests and review
Tests, validation, technical decisions, review findings, and release handoffs.
Work is split into bounded stages. Outputs become artifacts. Failures are meant to be caught before they quietly spread into the next stage.
Factory, not a single agent
Different workers. Same production structure.
Daedalus does not depend on one coding model, agent product or worker. Planning, implementation, review and verification can use different workers while the factory keeps the process, artifacts and source-of-truth boundaries stable.
It is not a single coding agent and not “vibe coding with more agents.” It is a software-production system.
Wider Radi system
It can build software that implements other harnesses
Daedalus also builds and evolves the codebases that implement other Radi harnesses and products. KlarForm, Vulcan and 4wd Scout stay distinct domain systems. The software that supports their tools, integrations and interfaces can itself be produced and maintained through Daedalus.