Reference

Database schema — `cro.*` ERD

The canonical data model. Tables are color-coded by category: regulated tables carry provenance and require a Part 11 signature to promote staging → live. Click any table in the diagram to jump to its details card below, or open `/schema?table=study` to deep link.

Tables

Columns

174

Foreign keys

Regulated tables

Regulated9

Carries created_at / updated_at / created_by / provenance_id. Promotion requires a Part 11 signature.

Staging2

Where agents land their writes. State machine: proposed → reviewing → signed → promoted.

Audit2

Append-only provenance and ops logs. Not part of the regulated write path.

Reference2

External or read-only data we index but do not own.

LegendRegulatedStagingAuditReferencePKprimary keyFKforeign key

Table reference

2 of 15 tables shown (Staging only)

cro

staging_record

The only legal write destination for agents. Proposed state lands here in `proposed`; humans review and sign to advance through `reviewing` → `signed` → `promoted`.

Staging

Column	Type	Key	References	Notes
`id`	uuid	PK	—
`entity_kind`	text	required	—
`entity_id`	uuid	nullable	—
`agent_id`	text	required	—
`model_version_id`	uuid	FK	→ cro.model_registry_version
`provenance_id`	uuid	FK	→ cro.provenance_event
`state`	enum	required	—	staging_state enum
`proposed_state`	jsonb	required	—
`created_at`	timestamptz	required	—
`updated_at`	timestamptz	required	—
`created_by`	uuid	required	—

cro

sponsor_request

Sponsor portal intake. Every inbound request lands as a staging row first; promotion to an actionable item still requires the same A2 gate.

Staging

Column	Type	Key	References
`id`	uuid	PK	—
`sponsor_id`	text	required	—
`study_id`	uuid	nullable	—
`subject`	text	required	—
`body`	text	required	—
`priority`	text	required	—
`status`	text	required	—
`provenance_id`	uuid	FK	→ cro.provenance_event
`created_at`	timestamptz	required	—
`updated_at`	timestamptz	required	—
`created_by`	uuid	required	—