Frequently Asked Questions & Architectural Clarifications
Frequently Asked Questions: Architecture, Workspaces & Operations
Authoritative answers covering platform architecture, contextual authority, data migration, security principles, and capability availability.
Notice on FAQ Answers & Capability Availability
The answers provided reflect CLADORA’s approved architectural model. The concrete availability of specific capabilities in any given deployment depends on release maturity, contracted edition tiers, and agreed implementation scope.
Platform & Architecture
What is CLADORA and how does it differ from traditional property management software (PMS)?
CLADORA is a unified property operating platform engineered to sustain data continuity throughout an asset’s lifecycle. Unlike fragmented PMS tools that operate as disconnected silos, CLADORA decouples enduring physical asset identity from organizational workspaces and relies on designated canonical truth providers for financial, evidentiary, and operational integrity.
What does the “single source of canonical truth” principle mean?
It establishes that exactly one designated domain holds sole write authority and custodial custody over critical operational records: FIN01 for financial ledgers, DOCUMENTS for evidentiary files, BK01 for reservations, and CORE for identity and authority boundaries. This is designed to reduce reconciliation ambiguity and error risk while preserving clear ownership of operational truth.
Workspaces & Authority
What is the precise distinction between a Property, a Workspace, and a Person?
The Property is the enduring physical subject (land, building structures, common elements). The Workspace is the administrative and security boundary of an operating organization (HOA, developer, property management company). The Person is a persistent digital identity who holds time-bound, scoped operational authority within specific workspaces pursuant to verified legal relationships.
Can a single user operate multiple roles across different buildings without data cross-bleed?
Yes. CLADORA natively decouples human identity from workspace-specific credentials. A user can act as an owner in one building, an audit board member in a second, and a tenant in a third, transitioning contexts cleanly without leaking confidential records across boundary walls.
Capabilities & Maturity
Are all architectural capabilities universally live across all deployments?
No. CLADORA enforces strict availability governance: architectural domain relevance defines where a capability logically belongs, but runtime availability is determined by formal release maturity and contractual implementation scope.
How does the platform handle submetering and utility allocations?
The architecture associates physical meters with spatial units, records verified meter readings, and routes consumption data to FIN01 to execute allocation formulas configured for the specific property archetype and local operating context.
Solutions by Participant Context
Do the six canonical Solutions represent six disparate software products?
No. The six Solutions (Developers, Property Owners, Associations, Property Managers, Residents, Service Providers) represent tailored operational lenses over the SAME unified platform architecture, shaped by the legal standing and scoped authority of each participant.
What financial visibility does an occupant or tenant receive?
Visibility is strictly scoped: occupants receive authorized access only to their own operational utility allocations, assigned invoices, and maintenance tickets. Private landlord ledgers, reserve fund investments, and neighbor billing records remain strictly restricted.
Industries & Property Typologies
Is CLADORA exclusively designed for multi-family residential buildings?
No. While residential associations represent an important operational baseline, CLADORA’s composable architecture covers 8 built-world property sectors: residential, workplace/office, retail, hospitality, industrial, logistics, automotive, and mixed-use environments.
What is Building DNA?
Building DNA is the architectural typology framework describing an asset’s physical and engineering characteristics (e.g., high-rise tower, horizontal villa community, logistics hub). It informs modular configuration without requiring separate software codebases.
Data Migration & System Transition
Is legacy system migration completely automated without human involvement?
No. CLADORA promotes a disciplined, assisted migration methodology where intake, unit mapping, balance carryover, and shadow validation runs require explicit verification and sign-off by authorized administrators. We do not promise unsupervised automated reconciliation.
What is the “Zero-Write” migration principle?
The migration architecture is designed to deny mutations when required authority, validation, mapping, or migration state cannot be established, preserving integrity throughout data intake.
Security, Trust & GDPR
Does CLADORA possess formal GDPR or ISO compliance certifications?
CLADORA is architecturally aligned with European GDPR principles such as data minimization, purpose limitation, and EU-oriented governance. We transparently document our technical controls rather than marketing unverified external badges.
Are databases or digital sign-offs described as mathematically immutable or tamper-proof?
No. We deliberately avoid absolute terminology such as “tamper-proof” or unqualified cryptographic guarantees. The platform uses append-oriented audit logs, standard encryption, and evidentiary tracking in DOCUMENTS.
Country Packs & Romania (Law 196/2018)
Does CLADORA provide automated legal compliance with Romanian Law 196/2018?
CLADORA provides a Romanian Country Pack designed to support residential association workflows (monthly maintenance sheets, reserve funds, working capital). The platform provides operational support but does not replace legal counsel or statutory executive board responsibility.
What legal weight do general assembly records stored in the platform have?
Platform records in DOCUMENTS provide operational organization and transparent communication for assemblies. They do not constitute qualified electronic voting or judicial evidentiary filings without integration with accredited statutory trust services.
CLADORA Intelligence & Governed AI
Can CLADORA Intelligence disburse funds or mutate balances autonomously?
No. Pursuant to the WP-09A AI governance standard, CLADORA Intelligence operates strictly as a subordinate assistive layer and is not designated as an independent canonical writer. Consequential financial mutations and administrative actions are designed to pass through the responsible canonical provider, verified authority, and applicable policy or human approval controls.
Partnership & Onboarding
What occurs after submitting a partnership inquiry?
Submitting an inquiry initiates a structured consultation. Our solutions team reviews your portfolio requirements, configures your initial property profile, and coordinates a transition roadmap.
Have a specialized technical question about your assets?
Our architecture team is available to discuss specific implementation requirements and operational models.