Quick Reference

Group Models
Investigations Investigation · InvestigationParty · Regulator
Requests & Requirements RegulatoryRequest · Requirement · RequirementAssignment · ExtensionRequest
Evidence & Review EvidenceItem · EvidenceReview
Response & Submissions ResponseDraft · ReviewDecision · Submission · SubmissionRequirement · ProductionItem
Comms & Exceptions Communication · IssueException

16 models in total.

The models

Model Purpose
Regulator The authority issuing requests
Investigation The matter — status, risk, confidentiality, legal hold, due date
InvestigationParty A participant in the matter (respondent, counsel, …)
RegulatoryRequest A notice/request with statutory basis, due date, extensions
Requirement A discrete thing to produce or answer, with owner/reviewer/approver
RequirementAssignment Who is working a requirement, in what role
EvidenceItem Material collected — custody, hash, privilege & confidentiality
EvidenceReview Legal/relevance review — responsive? privileged? redact?
ResponseDraft A versioned response draft with review/approval status
ReviewDecision A recorded review or approval decision
ExtensionRequest A request to the regulator for more time
Submission A package issued to the regulator, with receipt
SubmissionRequirement Which requirements a submission covers
ProductionItem Which evidence is produced/redacted/withheld in a submission
Communication Correspondence (incoming/outgoing/internal)
IssueException A privilege / deadline / completeness issue on the matter

Status vocabularies (enums)

  • Investigation: draft · active · stayed · closed · archived
  • Request: received · triaged · assigned · collecting · drafting · legal_review · awaiting_approval · submitted · acknowledged · overdue · closed
  • Requirement: open · in_progress · evidence_complete · response_drafted · reviewed · approved · submitted · waived · overdue · closed
  • Evidence: identified · requested · received · validated · excluded · produced · withheld
  • Privilege: unknown · not_privileged · potentially_privileged · privileged · waived
  • Confidentiality: public · internal · confidential · highly_confidential · regulator_only
  • Submission: draft · review · approved · issued · accepted · rejected · superseded
  • Response type: narrative · document_production · data_production · declaration · affidavit · schedule · other
  • Communication type: incoming · outgoing · internal_note · phone_call · meeting · email · letter · portal_upload
  • Assignment role: owner · contributor · legal_reviewer · approver · records_manager · subject_matter_expert
  • Risk / severity: low · medium · high · critical

The demo data set — one coherent story

INV-2026-014 "ASIC governance records notice — Project Harbour" (active, high risk, legal hold; external counsel Harbour & Vale).

  • ASIC notice R1 ("Produce governance and approval records", s.33) → two requirements: R1.1 board/committee records (document production, privilege expected) and R1.2 narrative explanation.
  • Evidence: EV-001 board minutes (reviewed privileged → redact) and EV-002 approval emails (not privileged, validated, fully responsive).
  • Response drafts for both; R1.2 approved, R1.1 sent back for changes; an extension request (+5 business days).
  • SUB-001 issued to ASIC (receipted): the R1.2 narrative in full plus two production items — EV-002 produced in full, EV-001 a redacted sample.
  • Two communications (the incoming notice, the outgoing extension request) and a privilege-risk exception on the board minutes.

28 seeded rows across all 16 models.

Key demo codes

INV-2026-014 (investigation) · R1 (request) · R1.1/R1.2 (requirements) · EV-001/002 (evidence) · SUB-001 (submission).

Notes

  • Fields named name on Requirement and EvidenceItem exist so referencing lists show a short label rather than the description paragraph (a framework display-field convention). People are plain string fields, not a model.
  • The deadline/response engine (effective_due_at, days_remaining, overdue detection, event emission) is Phase 2; the demo models those outcomes statically.