Quick Reference

Group Models
Projects & Requirements ConnectionProject · ConnectionRequirement · Dependency
Submissions & Review Submission · TechnicalReview · EvidenceItem
Risk & Exceptions ConnectionRisk · ConnectionException

8 models in total.

Key status vocabularies (enums)

  • ConnectionRequirement.status: identified · preparing · submitted · under_review · accepted · rework_required · blocked · waived · closed
  • TechnicalReview.outcome: accepted · accepted_with_conditions · rework_required · rejected
  • Submission.status: draft · submitted · withdrawn · superseded · accepted · rejected
  • materiality/severity: low · medium · high · critical

The demo data set

The Northgate Solar Farm connection NBSF-CONN (transmission, solar, 180 MW, in assessment). The GPS requirement REQ-GPS is accepted (acceptance letter evidence); it blocks the model-validation requirement REQ-MODEL, which is under review: submission SUB-MODEL-01 was superseded by SUB-MODEL-02, whose technical review TR-MODEL-02 came back accepted-with-conditions (re-fit ride-through). That opens risk RSK-MODEL (likelihood 3 × consequence 4 = 12) and exception EXC-MODEL (rework required).

10 rows across all 8 models.

Translation & modelling notes

  • Source is the pack's application { entity E { field: type; } } dialect, machine-translated to native DSL by a dedicated converter: each entity gets a surrogate Int pk, its business key kept as a required unique String, ref(T) → Int [ref], enum(...) inlined, list → Text.
  • ConnectionRequirement.description was renamed summary so its <fk>_name shows the title. Submission.supersedes_id is a self-reference (versioning). EvidenceItem/Dependency use polymorphic subject_id/predecessor_id string pointers, not FKs. ConnectionRisk.rating is a plain Int here (the pack's derived(likelihood*consequence) is Phase 2).
  • Denormalisation is intentional (child rows carry parent codes alongside the FK). Post-seed scan: zero Text leaks.
  • The workflow/governance/events are Phase 2 (page 03).