The Method

Stage by stage: what each step takes in and what it leaves behind.

1

Signal Extraction

Everything known about the system is gathered — documentation, API specs, database schemas, architecture notes, or nothing if nothing exists. From this, A-00 produces the mission brief: a structured document that tells every downstream agent what the system is, what workflows it handles, what it connects to, and what its team already knows. This is the heads-up before the forage begins.

2

Forage & Extraction

A-01 and A-02 run in sequence. A-01 traces every workflow from its server-side entry point through the call stack to its terminus — producing ASCII flow traces, one per process. A-02 traces the same workflows through the user interface — producing ASCII wireframes, screen by screen. Together these two layers capture what the system does and how its users experience it. Both in plain language. Both permanent.

3

Synthesis & Architecture

A-03 reads both layers together and produces the semantic intent specs — one per workflow, answering what it was actually trying to accomplish. A-04 reads those specs alongside the mission brief and recommends the modern stack that best fits what the system needs to do and what the organisation already runs. Custom work is flagged explicitly before build begins.

4

Build & Validate

A-05 builds in six passes — UI shell first, then API layer, data layer, external integrations, background processes, and finally the test suite. The method calls for a human sign-off between passes. When the build is complete, A-06 runs four validation stages: unit tests, integration tests, Playwright UI tests, and system load tests. Binary outcome per workflow — certified or returned with a precise gap report. The design is that nothing ships without certification.

5

Outputs

Each stage leaves its output behind as a .sil file: the mission brief, the workflow traces and wireframes, the intent specs, the stack recommendation and blueprint, the build passes, and the certification document. Together they form a written record of what the old system did and why the new one was built the way it was.