This demo · Under the hood

How this demo is built

Four views of the proof of concept itself (the other architecture pages describe how a production platform would be built). Boxes with a link open the page.

① Site map ② Submission thread ③ Plan-design engine ④ Delivery

① Navigation

Site map: what to click

Four role flows start from the home page. ★ marks the two pages where the substance lives.

Customer · quote → submit

Sign inmockOnboardingintakeProductspick a linePlan designer★ design the policySubmittedreceipt

Underwriter · decide → bind

Dashboardqueue + AI agentRate tablesactuarialPricingprice & bind

Case & Claims · service → claim

Case managementin-forceClaimsFNOL + feedback

Distribution · presale

ChannelsarchitectureProducerdashboardMortgageedashboard

② The product

Role workspaces over one submission thread

There is no backend, yet the personas feel connected: they read and write one submission thread in browser storage (js/store.js, through js/secure-store.js, so nothing is stored as readable text).

Write

Customer submitsplan designer

UWStore threadsubmission + queue

Read / decide

Underwriter queueyour submission on top

Decisionapprove / refer / decline

Pricingbind → policy number

Close the loop

Case managementbound policy

Claimsloss profile

Underwritingrisk feedback

The punchline: a customer's address appears in the underwriter's queue, a bound policy appears in case management, and a claim feeds risk back to underwriting. Reset demo in the header clears the thread.

③ Domain model

The plan-design engine

A clean-room rewrite in 2026: modern vanilla JavaScript (ES modules), no framework, no build step, no eval. Each product is a JSON tree (product → group → provision → option → nested provisions). Rules are data; rating is a pure function.

Data

data/products.json5 products as JSON trees

data/rules.jsonrisk · constraint · compliance

data/rates.jsonrelativity tables

Engine (js/)

engine.jstree → DOM, one delegated listener

rules.jsdeclarative predicates, no eval

rating.jspure premium function

Shell

app.jspremium panel, referrals, KB dialog

plan-flow.jswrites the submission thread

secure-store.jsobfuscated browser storage

Two rule classes stay separate: compliance notes and constraint rules block a submit; risk rules route to a human (referral). The climate scores per state are the seam where a production cat-model API would plug in.

④ Delivery

A static site with a strict content security policy

No login gate, no server, no keys. Scripts and styles load only from this origin; markup carries no inline scripts, inline styles or inline event handlers.

Request

Visitor

Vercel CDNstatic files, cleanUrls

Security headersCSP: script-src self, style-src self

HTML + /js + /css + /datano server code, no API routes