Data model

The core entities are owned by Payload (Postgres). In v1 the rich tool fixtures remain in the app; the core — tenants, launches, documents, the evidence base, the audit trail, and the agency rules — is backed by Payload collections.

Tenants

A customer organisation (e.g. Cygnus Therapeutics). Fields: name, slug, logo, region (data residency, fixed at provisioning), tier, status, contact, and a trainingOptIn flag.

Launches

A discrete submission — one product by country by agency (the unit of work, billing, and isolation). Fields: brand, molecule, indication, market, hta (PBAC / NICE / IQWiG / HAS / CDA-AMC), status, launchType (national / lifecycle / jca), tenant, team, lodgement date, denormalised counters, milestones, and enabled tools.

Documents

A source document in a launch's corpus. Fields: name, launch, category (Registry, PBS, ABS, Literature, Workforce, HTA decision, Regulatory, Statistics, Internal), pages, file, uploader, uploaded-at, parse status, and indexed-chunk count.

Parameters (the evidence base)

The heart of the product. Each row is a single parameter with full provenance and a reviewer decision:

• identity: launch, key, category, label, value, unit;
• status: proposed · active · superseded · rejected, plus a supersedes self-relation;
• provenance: proposed-by (model), proposed-at, confidence (0–1), confidence label, and a source group (document, title, page, snippet, organisation);
• reviewer: user, reviewed-at, notes.

Models and exports read only status = active rows. A revision supersedes, never overwrites.

Audit events

The append-only event stream. Fields: launch, at, who, action (promote · modify · reject · pipeline · upload · export · login), target, note, resource. Update and delete are denied at the application layer and revoked at the database role level — see Architecture.

Agency profiles

The rules engine. Per HTA agency: country, currency, willingness-to-pay threshold (null for efficiency-frontier agencies), discount rate, time-horizon default, preferred outcome, dossier format, cycles per year, required BIM scenarios, required CEA sections, equity dimensions, and an efficiency-frontier flag. This is what makes every tool agency-aware.