People do just three things: raise the issue, stamp the checks, accept the delivery. Specifications, test reports and progress reports are written by the machine and approved by people. Against the deliverables catalogue, nothing is missing.
With or without existing assets, once you are in, the same seven phases apply. We do not skip phases; the machine performs them — so the deliverables keep the shape you already know.
There is no system yet, or it is being rebuilt. Feed in the material describing what you need, and it is assembled in order, starting from the requirements specification.
The system runs, but there is no specification and nobody who wrote it is left. We read the source and produce the design documents that never existed.
The phases are never folded. For each one, what the machine produces and what a person stamps are fixed. The next phase does not start until the stamp is on.
Only testing splits into four stages — unit, integration, system and acceptance. Each defect report links back to the design phase that caused it, so which design error surfaced in which test can be traced afterwards.
What gets delivered is defined by a template. The catalogue can be swapped for your own standard — chapter structure and page layout are properties of the template, so documents come out in your in-house format.
Chapter structure and page layout — margins, typeface, stamp boxes — are properties of the template. Give us your in-house Word or Excel and the documents come out in that shape.
If a document the template requires is not there, it shows in red on the acceptance screen. There is no way to declare it complete when it is not.
Progress reports and monthly reports are generated from the check-stamp history. There is no field anywhere for a person to type a number into.
After you sign in there are six screens. On every one, what is waiting on a person — rulings and approvals — comes first.
A list with what is waiting on you (rulings and approvals) at the top. Raise issues here, start work from the detail, and answer rulings and approvals.
One run for one issue. It moves through the V-model phases from intake to approval and close-out, leaving each phase’s deliverables, review records and PRs.
See, start and stop the operators that run on-device tests on VDI lines, and evolution, which proposes improvements from experience.
Set up repositories, documents and VDI lines for each project.
Settings that apply to every project: the LLM gateway, run limits and project types.
Display language, appearance, motion and your sessions. Switch to Chinese and you can still approve Japanese deliverables.
We map your standard into a template and take one module of your existing assets. The PoC is one module over four weeks: we run all seven phases on one module of your own assets, and you judge the full set of deliverables and the quality metrics on the real thing. You keep the deliverables as they come out.