Property & Development Hierarchy

BlockManOS models Irish multi-unit developments using a three-level hierarchy:

Development (MUD)
└── Building / Block
    └── Unit

Owner profiles are maintained separately and linked to units via a time-stamped ownership table, preserving full ownership history.

Developments

A Development is the top-level entity, corresponding to a Multi-Unit Development (MUD) as defined under the MUD Act 2011.

Key Fields

Field	Description
`name`	Development name (e.g. "Elm Park Apartments")
`type`	`development_type` enum — e.g. apartment complex, mixed-use
`status`	`development_status` enum — e.g. active, under construction
`eircode`	Irish postal code for the development address
`county`	One of all 32 Irish counties (selected via dropdown)
`omc_name`	Owners' Management Company legal name
`omc_company_number`	CRO registration number
`psra_licence_number`	Property Services Regulatory Authority licence
`lpt_number`	Local Property Tax reference
Insurance fields	Insurer, policy number, expiry date

Navigating to Developments

Click Developments in the left-hand dashboard sidebar.
The developments list shows a card for each development with its status badge, unit count, and building count.
Use the filter controls to narrow by development type or status.

Creating a Development

From the developments list, click New Development.
Complete the form — required fields are marked with a red asterisk.
Enter OMC/CRO, PSRA licence, and LPT details in the compliance section.
Click Create Development.

Role requirement: Only users with the admin role can create, update, or delete developments.

Buildings

A Building (also called a Block) is a physical structure within a development — for example, Block A, Block B, or a named block.

Key Fields

Field	Description
`name`	Building name (e.g. "Block A") — required
`floors`	Number of floors (optional)
`totalUnits`	Expected total unit count for the building
`notes`	Free-text notes

Adding a Building

Open the development detail page (/dashboard/developments/[id]).
Select the Buildings tab.
Click Add Building / Block to open the dialog.
Enter the building name and optional floor/unit count.
Click Add Building.

Units

A Unit is an individual residential or commercial space within a development. Units can optionally be assigned to a specific building.

Key Fields

Field	Description
`unitNumber`	Identifier, e.g. `Apt 12` or `Unit 3A` — required
`buildingId`	Optional link to a building within the development
`floor`	Floor number
`type`	`unit_type` enum: `apartment`, `house`, `duplex`, `penthouse`, `studio`, `commercial`, `other`
`status`	`unit_status` enum: `vacant`, `occupied`, `owner_occupied`, `let`, `for_sale`, `under_renovation`
`bedrooms` / `bathrooms`	Room counts
`floorAreaSqm`	Floor area in square metres
`eircode`	Unit-level Eircode
`serviceChargePercent`	Service charge apportionment as a percentage
`serviceChargeFixed`	Service charge as a fixed euro amount
`lpt_valuation`	Local Property Tax valuation

Viewing a Unit

The unit detail page (/dashboard/developments/[id]/units/[unitId]) shows:

Unit metadata (type, status, floor area, Eircode)
Service charge apportionment
Full ownership history with start and end dates

Adding a Unit

Open the development detail page and select the Units tab.
Click Add Unit.
Enter the unit number, optionally select a building, choose type and status.
Fill in physical details (bedrooms, bathrooms, floor area, Eircode).
Set service charge apportionment — either as a percentage or a fixed euro amount.
Click Add Unit.

Owners & Ownership History

Owner profiles are stored independently of units and linked via the unit_ownerships table. Each ownership record carries a start date and an optional end date, enabling full historical tracking.

Owner Roles

An owner can hold one or more roles:

owner_occupier
landlord
investor
developer

AML Compliance

Each owner profile tracks whether an Anti-Money Laundering check has been completed (aml_checked) and when it was performed (aml_checked_at).

Assigning an Owner to a Unit

Use the assignOwner procedure — provide the unitId, ownerId, ownership type, and start date. To end an ownership, call removeOwner with an end date; the record is retained for audit purposes.

Access Control

All property data is scoped to the authenticated user's organisation. No cross-organisation data access is possible.

Operation	Required Role
List / read any entity	Any authenticated user
Create / update / delete	`admin`

Every mutation writes an entry to the audit log.

Irish Regulatory Compliance

The property data model is designed to meet requirements under the Multi-Unit Developments Act 2011 (MUD Act) and related Irish property regulations:

OMC details — Every development can store the Owners' Management Company name and CRO company number as required by the MUD Act.
PSRA licence — The managing agent's Property Services Regulatory Authority licence number is stored at the development level.
LPT — Local Property Tax reference numbers and valuations are stored at both development and unit level.
Eircode — Irish postal codes are captured for developments and individual units.
AML checks — Owner profiles record whether an Anti-Money Laundering verification has been completed, supporting obligations under the Criminal Justice (Money Laundering and Terrorist Financing) Act 2010.