D·TELCO verification console

Proves the parts of this demonstration that a page cannot prove about itself: that the backend answers, that the segment counts are the ones the presenter will say out loud, that the catalogue in the feed is the catalogue in the repository, and that every message the demonstration composes exists and is readable before anybody presses send.

1. Backend

Sixteen assertions across seven functions. Each one names what it expects, so a failure says which promise broke rather than that something is red.

ResultAssertionWhat came back

2. Segments

Live counts from the fourteen segment views, beside the seeded baseline recorded in handoff/SEGMENTS.md. Two are empty on purpose: pressing a signal in the operator simulator takes them from zero to one while the room watches. Seven are relative to today's date, so they move on their own, and the drift column says which and why.

Segment Seeded Pinned Live Delta Moves on its own

3. Contact

The same shape check every server endpoint applies before it acts, run here in the open, then the profile the backend would answer with. A key of the wrong shape is refused rather than looked up, because setContactKey does not fail on an unknown key: it creates that contact.

4. Catalogue feed

The feed Dengage would poll for its product table, counted and sampled. Two columns move by design: stock and discounted price belong to the operator simulator, so a difference there is the demo working rather than the feed drifting.

5. The content pack, and where every piece of it goes

One row per moment, naming the channels it carries copy for, the journey it belongs to and the trigger it fires on. The copy itself is not drawn here: it lives in the Dengage panel, which is where a prospect should be looking at it, and a second rendering on this page would be a second place for it to go stale. What this proves is that the pack is complete and that every file a person has to paste exists.

#MomentFires onLaneChannelsPaste from

6. Dengage wiring

js/config.js read as text and never executed, so this console can report whether the account is wired without becoming a visitor. Until the account id and app guid arrive, the storefront runs in full and logs its writes instead of making them.

Counts are read live at the moment you press a button. Nothing on this page writes to Dengage, to Supabase or to the storefront's storage. The one thing it does write is a pinned baseline, under dps:dtelco:verify:baseline, which no page of the demo reads.