Memorandum

A memorandum is the investor briefing for an organisation, written as a set of named prose sections plus two supporting documents.

Purpose

Each organisation has at most one memorandum. It holds the narrative shown on the investors page — summary, commercial position, product, financials, governance and outlook — with an optional briefing document and financial report attached. Keeping the sections as separate columns lets the front end render them independently rather than parsing one blob of text.

Usage

The memorandum is edited by staff and read by investors.

• app/Http/Controllers/Investors/InvestorsController.php — renders the investors Inertia page from the organisation’s memorandum.
• app/Filament/Resources/OrganizationResource.php — staff edit the memorandum from the organisation record.

Relationships

Relation	Type	Related model
organization	belongsTo	Organization
briefing	belongsTo	Attachment via briefing_attachment_id
financialReport	belongsTo	Attachment via financial_report_attachment_id

The inverse is Organization::memorandum() (hasOne).

Data shape

Table: memorandums (set explicitly via $table, since Laravel would otherwise pluralise to memoranda).

Column	Type	Notes
id	uuid	Primary key
organization_id	uuid	Unique; FK to organizations, cascade delete
summary	text	Nullable
commercial	text	Nullable
product	text	Nullable
financials	text	Nullable
governance	text	Nullable
outlook	text	Nullable
briefing_attachment_id	uuid	Nullable FK to attachments, null on delete
financial_report_attachment_id	uuid	Nullable FK to attachments, null on delete
created_at, updated_at	timestamp

One per organisation

organization_id is unique, so a second memorandum for the same organisation will fail at the database level.