Canonical Platform Glossary

Canonical Glossary: Entities, Providers & Architecture

Authoritative definitions of core entities, canonical truth providers, and composable dimensions within the CLADORA operating architecture.

Notice on Architectural Definitions
Glossary terms articulate domain boundaries, ownership scopes, and data modeling principles. Assigning canonical responsibility to a provider (such as BK01 for reservations or FIN01 for financial truth) reflects architectural boundaries, not universal production availability across all deployed instances.
Total canonical terms defined: 30
Property / Asset
The enduring, physical subject in the built world (land parcel, building, commercial complex, residential community, or infrastructure facility) that maintains persistent identity across changes in ownership, tenancy, or management agencies.
Workspace
The logical, administrative, and security boundary of an organization (developer, homeowner association, property management firm, or service vendor). Governs operational isolation, permission scoping, and data separation.
Place / Resource
A spatial subdivision or functional element within a property (apartment, office suite, parking stall, storage locker, conference room, elevator, or utility meter) uniquely referenced in the asset hierarchy.
Person
The persistent digital identity of a human actor. A single person may hold concurrent roles across distinct workspaces based on verified legal relationships, switching contexts without data cross-bleeding.
Organization
The legal entity or collective body (HOA, developer, asset management company, technical contractor) that owns, controls, or participates in one or more workspaces.
Role
A defined set of operational privileges applicable within a specific workspace boundary (e.g., Property Manager, Board President, Auditor, Resident, Service Contractor).
Relationship
The formal, verifiable legal link connecting a Person (or Organization) to a Property or Resource (e.g., Title Owner, Co-owner, Tenant, Authorized Representative). Governs the basis for permission assignment.
Authority
The legitimate operational entitlement conferred upon a Person to execute impactful actions within a workspace (authorizing invoices, approving maintenance orders, validating meter readings). Authority is always scoped, contextual, and auditable.
Mandate
The time-bound, legally sanctioned operational term during which an authorized party exercises governance duties (e.g., an elected HOA board term pursuant to statutory regulations).
Capability
A discrete, composable functional block of the platform (e.g., utility meter tracking, bank transaction reconciliation, cost allocation rules) enabled dynamically according to property requirements.
Canonical Provider
The designated architectural domain that holds sole write authority and custodial responsibility for a specific class of operational truth (e.g., FIN01 for financial ledgers, DOCUMENTS for evidence provenance).
Canonical Truth
The single, authoritative state of critical data maintained by its designated provider, designed to reduce reconciliation ambiguity and error risk while preserving clear ownership of operational truth.
CORE
The canonical truth provider for physical asset identities, organizational workspaces, natural/legal persons, verified relationships, and operational authority boundaries.
DOCUMENTS
The canonical provider architecture for official document versions, evidentiary records, and file provenance across authorized workspace contexts.
FIN01
The canonical provider for financial truth: transaction ledgers, posting rules, expense allocation calculations, trial balances, and banking reconciliation records.
BK01
The canonical provider for booking truth, capacity constraints, availability schedules, and shared resource reservations.
SERVICE
The domain governing service intent, maintenance inquiries, quote requests, and vendor coordination semantics.
OPERATIONS
The domain governing field work-order execution, preventative maintenance routines, contractor dispatch, and equipment inspection logs.
COMMUNICATIONS
The canonical provider for official message delivery, formal notices, digital community boards, and communication delivery auditability.
AIRPROP
The domain governing commercial lifecycle semantics: pipeline tracking, sales/leasing availability, deal structuring, and pre-handover record continuity.
Community & Experience (C&E)
The domain orchestrating user interactions, place guides, community events, and contextual occupant journeys across properties.
CLADORA Intelligence
The assistive, context-aware artificial intelligence layer that operates subordinately within CORE authority boundaries and policy gates, without autonomous canonical ownership.
Country Pack
The localized operational overlay encompassing jurisdictional terminology, document and allocation contexts (e.g., Romanian Law 196/2018 reference framework), and local operating expectations without branching core platform architecture.
Building DNA
The architectural typology and physical profile of a property (e.g., high-rise tower, villa community, commercial office, logistics warehouse) determining its modular configuration.
Property Profile
The specific operational blueprint of an asset resulting from the intersection of its Building DNA, ownership structure, and service complexity.
Operating Model
The organizational governance framework applied to an asset: self-managed HOA, outsourced third-party manager, or corporate portfolio administration.
Service Profile
The defined scope of physical operations contracted for an asset (e.g., elevator maintenance, security surveillance, landscaping, HVAC systems).
Migration Provenance
The immutable metadata trail attached to every imported legacy record (source system, source key, mapping decision, batch identifier, validation state, and sign-off).
Availability Governance
The public truth framework that rigorously differentiates architectural domain relevance, runtime release maturity, deployment scope, and user entitlement.
Action Receipt
An immutable, auditable record emitted following a consequential operation (invoice approval, meter submission, ticket closure) logging actor attribution, timestamp, and supporting evidence.