- NovaID participant / eligibility state
- Asset record in NovaRegistry
- Offer / workflow state
- Policy conditions
- Evidence
- NovaDeed ownership / document workflow
- Settlement interface
Use Case / Real Estate
Real estate: Novera's first reference workflow.
Buyer and seller state, property records and document workflows—Novera's first reference workflow.
Implemented enough to demonstrate as an end-to-end Novera reference workflow—using synthetic data only, in the pre-production MVP.
- NovaIDMVP MOCK
- NovaRegistryMVP
- NovaDeedMVP MOCK
01 · The coordination problem
Many systems. One asset state.
A property transaction depends on buyer and seller information, a property record, title documents, financing and inspection conditions and a closing process—each held by a different party and system.
Real estate is demanding enough to exercise every Novera stage, which is why it is the first reference workflow. It demonstrates the architecture; it does not define it.
SYNTHETIC DEMONSTRATION DATANo real identity documents, payments, deeds, titles or legal determinations.
02 · Participants
Who takes part—and who stays authoritative.
- Buyer
Their offer, consent and information supplied to external verification.
- Seller
Their listing, consent and supporting documents.
- Builder / asset operator
The asset and transaction context they define.
- Legal & title professionalsExternal authority
Legal review, title search and deed preparation.
- Lender / escrow providerExternal authority
Financing decisions and the movement of funds.
- Land registry / title systemExternal authority
The authoritative record of title.
04 · State to coordinate
Six stages. State accumulates around the asset.
Step through the same Novera lifecycle used by every asset class. Each stage names the primitive involved and where Novera stops.
- IdentityBuyer and seller participant state
Buyer and seller are represented
NovaID attaches participant references and a mock eligibility outcome to each party.
Who is participating?
Boundary Does not independently perform regulated identity verification.
05 · Primitive mapping
A configuration of NovaID, NovaRegistry and NovaDeed.
Not a separate product. The same three primitives—with the same component status—applied to this asset lifecycle.
NovaID
Represents buyer and seller participant state with a mock eligibility outcome. No real KYC or identity documents.
NovaRegistry
Holds the synthetic property record, its source references and its versions.
NovaDeed
Models offer, document-package and transfer workflow states: prepared, in review, recorded.
Signature workflow
Two sides of one transaction.
Buyer and seller follow different paths through the same stages. Both are conceptual reference workflows using synthetic data.
- NovaID participant state
- Asset record in NovaRegistry
- Ownership / document workflow in NovaDeed
- Policy conditions
- Evidence
- Transfer workflow
- Settlement interface
06 · 07 · 08 · Policy, evidence, settlement
Rules, proof and the final boundary.
What rules may apply
- Financing condition met or unmet
- Inspection condition satisfied
- Required documents present and reviewed
- Jurisdiction-specific items flagged for professional review
Represented as workflow conditions—not legal or regulatory determinations.
What supports each transition
- Inspection and appraisal report references
- Document-package versions and review events
- Participant consent and approval events
- Property-record version history
Referenced from its source, not certified by Novera.
Where Novera stops
At closing the workflow reaches the settlement interface. Funds movement, deed registration and title updates happen in external, authoritative systems.
- Handled externally by
- Escrow, lenders, payment providers, land registries
Reference workflow · Illustrative state machine
Eight transitions. Every responsibility remains visible.
The synthetic MVP reference workflow in detail. Select module pages and documentation for the data and trust model behind each transition.
Participant created
Create a synthetic participant reference and workflow role.
Eligibility represented
Attach an illustrative verification outcome; no real KYC/KYB occurs.
Asset registered
Create a synthetic asset record and provenance references.
Intent recorded
Represent a proposed transaction and required participants.
Evidence assembled
Model document-package status, versions, and review events.
Policy state recorded
Attach an illustrative policy result without a legal determination.
Lifecycle event emitted
Add an append-oriented event to the synthetic lifecycle history.
Settlement boundary reached
Stop at the adapter boundary; no funds or legal title move.
Coherent lifecycle state.
- Participant and role references
- Synthetic asset records and versions
- Document-package workflow states
- Policy-decision references
- Append-oriented lifecycle events
Authoritative real-world action.
- Identity verification and regulated screening
- Legal advice, title validation, or deed transfer
- Escrow, custody, payment, or settlement
- Government registry updates
- Production blockchain or oracle integration
09 · What Novera does not replace
Coordinate state. Preserve the authority.
Novera does not create legally effective deeds, register title, move funds or verify identity.
- REMAINS AUTHORITATIVELand registries and title systems
- REMAINS AUTHORITATIVELegal and title professionals
- REMAINS AUTHORITATIVELenders and escrow providers
- REMAINS AUTHORITATIVEIdentity providers
- REMAINS AUTHORITATIVEPayment providers
Demonstrated end to end with synthetic data.
Different assets · One control layer
The asset changes. The architecture remains.
Compare how the same primitives map to other asset lifecycles, or review the architecture behind them.