Learning with the demo estate

The built-in demo estate is one of the fastest ways to understand the product's behaviour.

Why the demo matters

The demos are not marketing toys. They exercise the system's workflows against seeded defects and realistic outputs.

Recommended sequence

Treat the following as a tour of separate exercises, not one prescribed engagement history. In particular, a later /layered exercise does not retrospectively govern earlier /sabsa authoring. Choose the arrangement using Methodical workflows; follow the worked cases for coherent end-to-end engagements. Use Claude slash commands below or the corresponding Codex $workflow-<name> skills in the provider conversation.

1. /demo setup
2. /analyse invoice-service
3. /criteria invoice-service
4. /review invoice-service
5. /diagnose ...
6. /sabsa prepare ...
7. /publish ...
8. /layered ...

What good results look like

Good results are typically characterised by:

• explicit scope and assumptions;
• visible review criteria;
• separation between findings and fixes;
• concrete next actions;
• professional deliverable structure;
• clear statement of uncertainty when evidence is weak.