What rules may apply
- Credit and eligibility conditions set by the lender
- Covenant checks
- Assignment consent requirements
- Collateral-coverage conditions
Represented as workflow conditions—not legal or regulatory determinations.
Use Case / Private Credit
Keep the loan, its collateral and every servicing event in one frame.
Borrower and lender state, loan and collateral records, origination, assignment and servicing.
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.
A private loan combines borrower and lender state, a loan agreement, collateral records, covenants and a long tail of servicing events—across originators, servicers, collateral agents and funding sources.
Novera's architecture could coordinate the state of the loan and its collateral over its life, while lending, servicing and custody remain with the parties responsible for them.
02 · Participants
Who takes part—and who stays authoritative.
- Borrower
Its obligations and disclosures.
- Lender
The credit decision and funding.
- ServicerExternal authority
Payment processing and servicing records.
- Collateral agent / custodianExternal authority
Holding or controlling collateral.
- Lien registryExternal authority
Authoritative security-interest filings.
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.
- IdentityBorrower and lender state
STAGE 01 / 06 · NovaID
Borrower and lender are represented
NovaID could reference each party's externally supplied participant state.
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
One obligation, followed over time.
A loan's state keeps changing long after origination. These are the events a coordination layer would need to follow.
- 01Origination
Terms agreed; loan and collateral records established.
- 02Funding
Disbursement confirmed by the lender—an external event.
- 03Servicing
Payment and reporting events referenced over the loan's life.
- 04Assignment
Loan or participation assigned, subject to consent.
- 05Covenant check
Conditions re-evaluated and the outcome recorded.
- 06Payoff
Obligation closed; lien release referenced.
06 · 07 · 08 · Policy, evidence, settlement
Rules, proof and the final boundary.
What supports each transition
- Loan agreement and amendment references
- Collateral valuation and inspection references
- Lien filing references
- Payment and servicing-event references
Referenced from its source, not certified by Novera.
Where Novera stops
Disbursement and repayment move through lenders', servicers' and payment providers' systems; Novera would reference those events at the interface.
- Handled externally by
- Lenders, servicers, payment providers
09 · What Novera does not replace
Coordinate state. Preserve the authority.
Novera does not originate, fund, underwrite or service loans, or perform any regulated lending activity.
- REMAINS AUTHORITATIVELenders and credit decisions
- REMAINS AUTHORITATIVELoan servicers
- REMAINS AUTHORITATIVECollateral agents and custodians
- REMAINS AUTHORITATIVELien and security-interest registries
- REMAINS AUTHORITATIVEBanks and payment providers
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.