The worked example
One run of the framework, listed whole.
Everywhere else on this site the documents are described, counted or photographed. Here is the inventory. One command, on 23 October 2026, ran four applications against the Roulette Sample and merged what came back: 113 files, of which 59 are documents and data files — every one of them named below. The board is the one you can watch being tested in the sequencer's videos.
The documents themselves are not here This page is the file list, not the files. The run wrote 113 of them; 54 are a program's working formats — JSON models, StrictDoc sources, Markdown copies, the folder of agent instructions and the zip of all of it — which is why the count below is 59. What each application concluded is summarised on this page and the numbers are real, but a finished report is written for one board and one customer, so it is not something to leave on a public page. If you want to see the real thing, ask.
What one command did
Four applications, three waves, 14 seconds.
The dispatcher asked each installed application what it reads and what it writes, worked out from that which could run first, ran them, and merged the results. Nothing in that order is hard-coded: testability and validation have nothing to wait for, EMC waits for the testability analysis, and the traceability model waits for all three.
| Application | Version | Files | Took |
|---|---|---|---|
| PCB Test Analysis | pcbtest 1.4.2 | 6 | 0.7 s |
| EMC Design Compatibility | emc 0.1.1 | 14 | 1.9 s |
| Validation Testing | vtest 0.1.0 | 10 | 0.5 s |
| Test Spec Ecosystem | tspec 0.1.1 | 21 | 11.3 s |
Verdict: all 4 app(s) ran and passed their gates — which means they ran and their own release gates passed, not that the board did. It did not: the EMC analysis predicts this one fails electrostatic discharge at the USB port by 57.2 dB, and says why, in the report. The same analysis expects radiated emissions to pass with about 18.3 dB in hand. A worked example that only ever passed would be worth nothing.
Start here
The combined report, and the documents under it.
The combined report is the one page written over the top of all four applications: the verdict, what each one concluded, the findings worst first, the merged plan and the equipment. Under it sit the documents each application wrote, and under those the exchange formats, the project tasks and the model itself. That shape is the point — one run, one verdict, and everything underneath it agreeing by construction rather than by review.
Everything the run wrote
All 59 files, grouped.
This list is generated by walking the run itself, and the build fails if a file would not appear on it. So it is not a curated set of highlights: it is the directory, name for name.
The combined report3
What the dispatcher writes over the top of all four applications: the verdict, each one's gates, the merged plan and the equipment - as a page, and as Word and PDF. run.json is the same thing for a machine.
- Roulette Sample-combined-report.docx
- Roulette Sample-combined-report.pdf
- index.html
The merged project plan, and the bench1
Every application writes its tasks against the same milestone ids. This is the merged result as one Microsoft Project file, and the equipment reconciled across all four of them. Each application's own contribution is in its own folder below, unmerged.
- Roulette Sample-mblab-project.xml
Test Spec Ecosystem - the documents8
The readable end of the trace model: the hub, the test plan with its flowcharts, ninety test cases, the DFT report, the FMEA and the traceability matrix - and the single self-contained file that holds every one of those pages at once.
- Roulette_Sample-reports.html
- Roulette_Sample-test-ecosystem.xlsx
- dft-report.html
- index.html
- risk-analysis.html
- test-plan.html
- test-spec.html
- traceability.html
Test Spec Ecosystem - Word and PDF10
The same documents in the formats a reviewer actually opens.
- Roulette_Sample-dft-report.docx
- Roulette_Sample-dft-report.pdf
- Roulette_Sample-risk-analysis.docx
- Roulette_Sample-risk-analysis.pdf
- Roulette_Sample-test-plan.docx
- Roulette_Sample-test-plan.pdf
- Roulette_Sample-test-specification.docx
- Roulette_Sample-test-specification.pdf
- Roulette_Sample-traceability.docx
- Roulette_Sample-traceability.pdf
Test Spec Ecosystem - the exchanges2
The trace model exported into the tools other people use: ReqIF for DOORS and DOORS Next, and a flat CSV of every link.
- Roulette_Sample-trace.csv
- Roulette_Sample.reqif
Test Spec Ecosystem - its own project plan1
What it contributed to the merged plan, before the merge.
- Roulette_Sample-tspec-project.xml
PCB Test Analysis6
Testability: per-component coverage, which nets a probe can reach, the test points it suggests, and the lists the optical inspection and in-circuit stations need.
- roulette_sample-pcbtest-project.xml
- roulette_sample-aoi-list.csv
- roulette_sample-ict-probes.csv
- roulette_sample-test-coverage.xlsx
- roulette_sample-test-report.html
- roulette_sample-testpoints.csv
EMC Design Compatibility14
Pre-compliance against the standards this product's industry and markets impose, the field data behind it, the test plan and the per-setup instructions.
- roulette-sample-emc-analysis-report.docx
- roulette-sample-emc-test-instructions.docx
- roulette-sample-emc-test-plan.docx
- roulette-sample-fdtd-far.csv
- roulette-sample-fdtd-far.png
- roulette-sample-fdtd-near.csv
- roulette-sample-fdtd-near.png
- roulette-sample-nearfield-scan.csv
- roulette-sample-nearfield-scan.png
- index.html
- roulette-sample-emc-project.xml
- roulette-sample-emc.xlsx
- test-instructions.html
- test-plan.html
Validation Testing10
Which environmental and mechanical tests are required, how many samples, how long and what it costs - with the instructions and the requirement traceability that go with them.
- roulette-sample-validation-report-template.docx
- roulette-sample-validation-test-instructions.docx
- roulette-sample-validation-test-plan.docx
- roulette-sample-validation-doors.csv
- roulette-sample-validation-doors.reqif
- index.html
- roulette-sample-vtest-project.xml
- roulette-sample-validation.xlsx
- test-instructions.html
- test-plan.html
The run's own logs4
What each application printed while it ran. Here because a worked example that hides its logs is a brochure.
- emc.log
- pcbtest.log
- tspec.log
- vtest.log
How the dispatcher works out the order → · What each application writes → · The board itself →