Method
Built by agents. Governed like it matters.
Asdes runs its company on the agents it builds - the same system that wrote this page ships the products in the portfolio. That only works because the machine is governed. Five principles carry the weight.
01 / 05
Work runs on contracts.
Every build opens as a written contract - scope, slices, acceptance criteria that pass or fail mechanically. Agents execute it; they do not reinterpret it.
build-contract.md
scope: portfolio site - six products, one system
slices: 12, each independently shippable
acceptance: mechanical - it passes or it does not
drift: not permitted mid-flight
contract locked - execution begins
02 / 05
Work survives the gap.
Sessions end; the work does not. State, decisions, and lessons write to durable memory and cross to the next session intact. Nothing is relearned.
Session 12
endedstate written
decisions kept
lessons banked
the gap
Session 13
woke with everythingstate written
decisions kept
lessons banked
03 / 05
The builder never signs it off.
Whatever built the thing does not declare it done. An independent verifier probes the running system - a claim without evidence is treated as false.
the build claims done
an independent verifier probes it
no evidence, no green - the gate has killed real ships
04 / 05
Autonomy has enforced limits.
Routine work runs free in the inner tiers. Direction, money, and the irreversible escalate outward - and stop at the ring where a human decides.
05 / 05
Everything compounds.
One substrate ships every product. Each launch lays rails for the next - the portfolio is one system, photographed six times.
one substrate - every launch lays rails for the next
The fine print
01
Work runs on contracts
Every build starts as a written contract: scope, slices, acceptance criteria that pass or fail mechanically, and a definition of done that cannot drift mid-flight. Agents execute the contract; they do not reinterpret it.
When reality disagrees with the spec, the spec gets amended in the open - not quietly worked around.
02
The work survives the gap between sessions
An agent's memory does not persist by accident, so persistence is engineered: every session writes its state, decisions, and lessons to durable memory before it ends. Tomorrow's session picks up exactly where today's stopped.
This is why the tenth product costs less than the third. Nothing is relearned.
03
The builder never signs off its own work
Whatever built the thing does not get to declare it done. Verification runs through independent gates - separate reviewers, real probes against the running system, screenshots read by different eyes than the ones that wrote the code.
A claim without evidence is treated as false. That rule has caught more bugs than any test suite.
04
Autonomy has enforced limits
Agents act freely inside tiers: routine work executes silently, notable work notifies, and anything touching direction, money, or the irreversible stops and waits for a human verdict. The tiers are enforced by the system, not by good intentions.
Daybreak, in the portfolio, is this principle turned into a product.
05
Everything compounds
One substrate runs the company: shared memory, shared tooling, shared review gates, shared taste. Each product ships onto rails the previous one laid.
The portfolio is not six separate efforts. It is one system, photographed six times.
The proof is the portfolio.
Six live products, one system. Open any of them and touch it.