Walkable Salesforce demos — before the build.

New engagement — what it writes

Scaffolds a whole workspace under client/, the authoring truth:

• client/base/engagement/src/schema/ — the standard objects you picked, with their real standard fields from the canonical metadata source.
• src/seed/ — an admin profile, a demo user, a profile-owned permission set, and an ObjectPermissions read grant per object. Object read is default-denied, so without those rows the objects would compose and stay invisible.
• src/manifest/base.json — a curated nav; everything else is one click away in the App Launcher’s All Items, as in a real org.
• client/variants/<id>/ — one unpinned starter variant.
• client/POC-CLIENT.md — the client-facts sheet, prefilled with whatever you answered in the form.

The flow

1. Click Start a new engagement.
2. Pick a slug + display name + first variant. The slug becomes the folder name and the runtime’s ?engagement= key, and is permanent.
3. Record what you already know about the client. Blank stays a TODO rather than being marked done.
4. Choose a tier — minimal, core, everything or substrate-only — and tick any optional packs. Counts update live.
5. Create. Then compose --variant <id>; expect 0 blockers.

One-click creation needs the server started as python tools/poc.py dev --allow-create <parent dir>. Without it the page still does everything except write — it hands you the spec and the exact command. Creation is opt-in because it writes to disk on request: the directory named there is the only place it can ever write, and a per-run token is required.

Adding objects later

The Schema Picker is for a workspace that already exists. It emits a selection and one command; the plan is built by the generator, not the browser:

python tools/poc.py plan add-standard-object     --selection <file> --apply

• The plan adds schema shards, a read grant per object, and any polymorphic lookups that should now include them.
• It runs through the gated kernel, so a change that would not compose does not land.
• Installed objects are ordinary authored source afterwards — edit or delete them freely.

Caveats & cautionary points

• Neither page writes generated output. Both used to write engagements/<slug>/ directly — which the next compose destroys, and which git ignores. That path was removed; authoring truth is client/base/engagement/ + client/variants/<id>/.
• Serve, don’t open. Both pages fetch the metadata source, so file:// cannot load them. Use poc dev.
• Slug renames — hand-edit manifest.json + engagements/_index.json and rename the folder. No picker path.
• Four TODOs survive creation in POC-CLIENT.md by design: they are build-time discoveries (shared-field risks, managed-package choices, demo gates). release.py --tier release blocks until they are answered, and the form deliberately does not offer to prefill them — that would clear the gate without answering anything.
• Reset Database — wipes localStorage mutations only. Scaffold and kernel writes touch disk and are unaffected.