- Investor eligibility state
- Interest class in NovaRegistry
- Subscription documents in NovaDeed
- Eligibility and allocation conditions
- Acceptance evidence
- Capital-movement interface
Use Case / Private Markets
Coordinate issuers, investors and every ownership interest.
Investor eligibility, issuer and interest records, subscription and transfer workflows.
USE-CASE MATURITYARCHITECTURE USE CASE
Novera architecture has been mapped conceptually to the use case, but this is not a production product or deployment.
Configures the same primitives
How maturity is defined - NovaIDMVP MOCK
- NovaRegistryMVP
- NovaDeedMVP MOCK
01 · The coordination problem
Many systems. One asset state.
Private-market ownership interests move through subscription documents, eligibility checks, approvals and transfer restrictions spread across issuers, investors, counsel and transfer agents.
Novera's architecture could give those parties a shared view of interest state and its supporting evidence—while regulated functions stay with regulated parties.
02 · Participants
Who takes part—and who stays authoritative.
- Issuer
Its offering terms and corporate records.
- Investor
Their subscription, consent and supplied information.
- Transfer agent / registrarExternal authority
The authoritative securityholder register.
- CounselExternal authority
Offering documents and legal review.
- Broker-dealer or placement agentExternal authority
Regulated distribution, where required.
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.
- IdentityInvestor eligibility and issuer state
STAGE 01 / 06 · NovaID
Investor eligibility is attached
NovaID could reference an eligibility outcome from a qualified external provider. Novera performs no verification.
Who is participating?
Boundary Does not independently perform regulated identity verification.
Conceptual model · Visitor-controlled · No live data
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.
Signature workflow
Subscription and transfer.
Two workflows over the same interest record. Both are conceptual mappings, not an offering or trading service.
- Transferor and transferee state
- Existing interest record
- Transfer-request workflow
- Restriction and consent conditions
- Approval evidence
- Register-update interface
06 · 07 · 08 · Policy, evidence, settlement
Rules, proof and the final boundary.
What rules may apply
- Investor eligibility requirements
- Transfer restrictions and holding periods
- Issuer or manager consent
- Jurisdiction-dependent requirements
Represented as workflow conditions—not legal or regulatory determinations.
What supports each transition
- Subscription agreement references
- Eligibility attestations from external providers
- Approval and consent events
- Interest-record version history
Referenced from its source, not certified by Novera.
Where Novera stops
Capital movement and any official register update would happen through external banking, payment and transfer-agent systems at the settlement interface.
- Handled externally by
- Banks, payment providers, transfer agents
09 · What Novera does not replace
Coordinate state. Preserve the authority.
Novera does not issue securities and is not a broker-dealer, exchange, transfer agent, custodian or securities registrar.
- REMAINS AUTHORITATIVETransfer agents and securities registrars
- REMAINS AUTHORITATIVEBroker-dealers and exchanges
- REMAINS AUTHORITATIVECustodians
- REMAINS AUTHORITATIVESecurities regulators
- REMAINS AUTHORITATIVELegal counsel
10 · MATURITYARCHITECTURE USE CASE
Mapped conceptually · not a product or deployment.
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.