Synthetic fixture · no customer data
Synthetic underwriting evidence pack
Trace infrastructure evidence into model-ready capacity.
A runnable, deterministic demonstration of how Doku links a submitted GPU plan, protected power, technical qualification, contract acceptance, and an illustrative cash-flow bridge without turning missing evidence into a pass.
Of 256 installed GPUs, the submitted synthetic record supports 192 as configuration-qualified contracted capacity. The current-versus-restored modeled monthly revenue delta is $126,720.00.
All transaction facts and financial inputs are invented. This is not a customer case, credit decision, technical opinion, covenant calculation, or proof of real-world performance.
Decision path
Start with the question. Preserve the source trail.
The pack keeps evidence state, technical support, model consequence, and decision authority separate.
- 01
Which physical assets are in the submitted scope?
- 02
What capacity is admitted by the declared protected-power boundary?
- 03
Which admitted nodes have current, scoped qualification evidence?
- 04
Which complete service pools satisfy contract acceptance and billing gates?
- 05
How do those evidence states change the declared cash-flow proxy?
- 06
What evidence would close each unsupported assumption?
Live synthetic scenario lab
Change an assumption. Get a fresh, hashed result.
The page calls a real same-origin endpoint backed by exact rational arithmetic. Presets show why power, qualification, acceptance, timing, and price cannot be collapsed into one haircut.
200 OK · SYNTHETIC
asmt_synthetic_2fb831577d4ca92bEligible poolsA, B, C
Billable GPU-hours138240
Technical conclusionNot issued
Open evidence and model conditions
- PC-001Establish sufficient protected placement for Pool D
Commissioning evidence and an approved asset-to-rack/feed plan for the full-system envelope.
- AC-001Resolve the n27 hardware qualification exception
Identity-linked recovery record and repeat supported test results.
- AC-002Complete n28 hardware qualification evidence
Raw required results covering n28 and all eight device IDs.
- AC-003Evidence whole-pool customer acceptance
Complete topology/workload test package, customer acceptance evidence, and contractual billing start.
- FM-001Reconcile the lender cash-flow definition
Lender-approved debt schedule, expense rows, collection assumptions, and covenant definition.
Synthetic verification snapshot
A large test surface, with a narrow claim.
The supplied corpus passed direct and actual-loopback HTTP comparison against an independent oracle. These checks measure agreement with an explicit synthetic requirements contract; they do not verify evidence authenticity, hardware feasibility, customer outcomes, or underwriting superiority.
Inspect verification summary- Synthetic cases
- 200,000
- Requirement families
- 25
- Rules per case
- 3 of 75
- Named regressions
- 251
- Selected mutants killed
- 38 / 38
- Oracle comparisons
- 14.4M
One assessment, multiple representations
Readable pack and machine records stay aligned.
The PDF, JSON, CSV, OpenAPI, and browser result are generated from the same canonical fixture and engine output.
Model assumptions
Unsupported assumptions stay visible.
The demo is useful because it refuses to turn missing evidence into zero, a failed check into a waiver, or a calculated state into a technical conclusion.
- 01
The contract covers the analysis period with no service credits, collection lag, bad debt, or revenue sharing.
- 02
Fixed operating expense includes other site charges and does not duplicate the modeled electricity row.
- 03
Remediation and acceptance costs are excluded from the initial proxy.
- 04
The working-capital row is incremental to all other modeled cash receipts and payments.
- 05
Power, cooling, placement, health, acceptance, price, and expense inputs are authored synthetic assumptions, not verified facts.
Move from synthetic to scoped
Use the demonstration to define the first real evidence question.
Real or redacted transaction work begins only after conflict review, permitted-use confirmation, and controlled intake. Doku does not accept live customer evidence through this public sandbox.