OASIS DIGITAL PARLIAMENT
Authority Console OS
CI • Archive

Upload

Domain-driven filing intake. SHA-256 enforced. Storage upload → register_minute_book_upload().

Launchpad
Enterprise contract • SHA-256 enforced•State: Ready•Lane: RoT•OS module surface
Filing Context
Entity + Domain + Type + Date
context
Entity
holdings
Must match entity_key_enum.
Filing Mode
Standalone remains the default. Linked mode attaches this filing to an existing governance_ledger record.
Domain
Source: governance_domains
Entry Type
Source: entry_type_section_defaults
Date
Domain: —standalone
Filing Payload
Title • Notes • PDF • Hash
writer
Title
Notes
PDF
Bucket: minute_book#SHA-256 enforced
This page writes: Storage upload → register_minute_book_upload().
The registry reads evidence from minute_book_entries + supporting_documents.
Standalone mode will file a pristine Minute Book upload with no governance link.
Registry Projection
Path + Evidence + Local Preview
projection
Storage Path
Fill fields + choose a PDF to compute path…
Mode
Standalone Archive
No source_record_id will be attached
Domain
— (—)
Evidence
No file selected
SHA-256: —
Local Preview
PDF-first
Select a PDF to preview.
If the Minute Book registry ever says “no storage_path on primary document”, it means supporting_documents didn’t get created for that entry_id.
This upload page now supports both pristine standalone filings and optional ledger-linked filings.
Upload is the write entry point.Go to Registry →
OS behavior
CI-Archive Upload inherits the OS shell. No module-owned window frames. This surface remains the sole write entry point for Minute Book records. Standalone preserves existing upload behavior; linked mode only adds an optional governance_ledger bridge via source_record_id.
CI-Archive · Oasis Digital ParliamentODP.AI · Governance Firmware
CI-ArchiveMinute BookVerified