Draft — still being shaped, not yet part of the source of truth.
The demos
Each demo is a fictional company running on Astent — proof of what can be built, of which architectures work, and something to show customers.
Demos are not experiments or benchmarks. Experiments measure an agent against a task set, and the harness in astent-lab owns that. A demo tests what can be built: it takes one company's core process, prototypes it on the Astent stack with all the mechanics production software will have, and ends as something a customer can watch working. Everything in a demo is synthetic — the companies are fictional and no customer data appears anywhere.
Every demo is described in the same shape:
- The company — who the fictional business is and what it sells.
- The core process — the one being tested and prototyped.
- What the demo shows — what it proved could be built, and what a customer sees.
On the architecture side, each demo is one case: its own Frappe site, its own case package, its own baseline identifier.
Fenestra fenestra_v1
The company. A made-to-order window manufacturer. Full introduction pending.
The core process. Configure-price-quote for made-to-order products: whether a requested configuration is orderable at all, what it costs — surcharges, channel factors, a colour percentage — and the BOM and routing the order implies.
What the demo shows. Pricing driven by policy records rather than code: a surcharge edited as a single record moved a real quotation from €412.40 to €452.40 with no code change and no deploy. Full write-up pending.
Kler kler_v0
The company. Introduction pending.
The core process. Composition validity, zone covering and delivery sets.
What the demo shows. Write-up pending.