Software architect and proof engine

Dao

Yin-yang mark Zhuangzi character

Dao redesigns software from the ground up, then proves the work. Expert panels propose the clean architecture; bounded AI workers implement it; deterministic gates decide what advances.

See the redesign loop -> Proof model
Expert waves Architecture, types, storage, security, schema, and observability.
Worker missions Claude, Codex, and later workers operate inside bounded paths.
Green gates Verdicts, parity, design audits, and deterministic checks.

Product posture

Dao is not a coding chatbot. It is the architect and judge above workers.

Now

Deterministic validation, typed verdict doctrine, gate flow, expert-panel design corpus, and a Claude-driven orchestrator.

North star

Give Dao a messy codebase and a goal. It studies, redesigns, drives workers, verifies, heals, and pauses at human doors.

Trust rail

Every agent claim needs evidence: typed verdicts, reproducible checks, design/code conformance, and reviewable records.

Redesign loop

Rewrite only when the architecture and the proof loop both hold.

01

Read scars and contracts.

Dao studies current behavior, failure history, tests, interfaces, production constraints, and live checks before proposing shape.

Evidence: baseline, scars, invariants.
02

Run expert design waves.

Architecture, DDD, Rust/types, Python exterior, security, verification, storage, schema, and agent lenses compete.

Evidence: integrated target architecture.
03

Launch bounded workers.

Claude, Codex, or another worker receives a path-isolated mission and returns a typed verdict instead of informal confidence.

Evidence: mission, diff, verdict.
04

Gate, heal, or halt.

Dao runs checks, catches drift, launches repair missions, and pauses before irreversible product, money, contract, or merge decisions.

Evidence: green gate or explicit refusal.

Operating rule

A redesign is not correct because an agent says it is correct.

Dao treats every proposal and generated change as a claim that needs evidence. Zhuangzi gives the character direction: perspective shifts are useful only when balanced by proof.

Expert panels propose. Workers build. Dao proves. Only then does the migration move.

Capabilities

Built for migrations, parity, production hardening, and full re-architecture.

Dao should make "redesign this properly" into a controlled, testable, reviewable production migration instead of a long chat transcript.

Expert design waves

Use architecture, types, security, verification, storage, schema, observability, and agent lenses.

Clean-room redesign

Prefer the correct production architecture over cosmetic refactors around a broken shape.

Provider-neutral workers

Drive Claude, Codex, and later workers through one proof envelope.

Path isolation

Bound each mission to owned paths so a repair cannot mutate the whole system.

Design audits

Compare intended architecture against actual code and classify divergences.

Parity gates

Preserve behavior while old layers are replaced behind shims.

Maturity

Bold vision, honest state: Dao is the proof layer, not magic.

Now

Typed verdicts, deterministic validation, expert design corpus, and Claude-oriented orchestration.

Emerging

Codex worker integration, provider-neutral driver model, and deeper design-wave workflows.

North star

Full production re-architecture from legacy systems to the best target architecture under proof, parity, and review.