The interactive sandbox is under construction.

An in-browser trial environment is easy to do badly: you prepare a fake domain, show three screens, and whoever looks learns little — because the interesting part of Pwas isn't the interface, it's what happens when you change the domain description and everything else adapts.

A useful sandbox therefore has to let you genuinely edit the declaration and see the effect: add a field and find it on the screen, change a permission and watch a request be refused, ask the agent for a disallowed action and watch the plan fail to compile. That requires real, isolated execution per session, not a simulation.

It's feasible and it's in the works. But we'd rather publish it when it works that way than ship a version that shows screens and teaches nothing.

Even once the sandbox exists, the guided demo will remain more useful for one reason: someone who knows the product can connect it to your work. We show you a business application that already works and focus on the areas that concern you.

The distance between an example and your case can't be closed in thirty minutes, and we don't promise to: that is the job of the assessment phases that follow the demo, where your process is analysed with method and turned into specifications and a concrete proposal.

The other thing a sandbox doesn't do is answer the awkward questions the moment they occur to you: what if this field depended on the role? what if the data came from an ERP that exposes nothing? what if this rule changed every year?