The Public-Good Stack and Enterprise Stack define how Nexus separates readiness from execution, legitimacy from implementation, evidence from approval, finance-readiness from investment advice, insurance relevance from underwriting, and lawful continuation from public-good authority. The Public-Good Stack creates the record-based, non-executing infrastructure through which systemic risk is observed, structured, tested, translated, corrected, and prepared. The Enterprise Stack provides the separated lawful continuation environment through which companies, providers, sponsors, operators, investors, insurers, National Consortium Companies, Project SPVs, and implementation partners may act only where separate authority, contracts, safeguards, finance, insurance, procurement, professional review, data rules, and public authority processes permit.
Opening Definition
The Public-Good Stack is the non-executing institutional layer of Nexus.
It organizes evidence, records, maturity, observability, readiness, public-safe intelligence, public authority learning, stakeholder participation, technical credibility, finance-readiness, insurance relevance, safeguards, correction, and lawful routing.
The Enterprise Stack is the separated execution-side environment.
It includes National Consortium Companies, Project SPVs, providers, sponsors, operators, contractors, hosts, investors, insurers, technology companies, service providers, implementation partners, and other competent actors that may act only under their own lawful authority.
The two stacks are connected by Nexus Rails, tested through Nexus Universe, technically supported by Nexus Core, extended through Nexus Network, and governed by role separation, non-execution, validity by record, correctionability, claims discipline, data governance, public-safe language, sponsor neutrality, procurement neutrality, finance boundaries, insurance boundaries, community safeguards, workforce safeguards, and lawful continuation controls.
The institutional base for this article is grounded in the Organization documentation, the Nexus Charter, the governance foundations, the Operations overview, the Operations frameworks, the public Public-Good Technical Stack, the Non-Execution Doctrine, and the doctrine of Authority by Boundary.
The central rule is simple: the Public-Good Stack makes readiness usable; the Enterprise Stack may act only where separate lawful authority exists.
Why Two Stacks Are Necessary
Nexus exists because systemic risk must be converted into governed innovation demand, but that conversion cannot happen safely if public-good functions and execution functions are collapsed into one structure.
Public-good readiness requires trust.
Execution requires authority.
Trust and authority are related, but they are not the same.
A public-good record may make a risk more visible. It does not approve a project.
A technical-readiness note may make a technology more understandable. It does not certify the technology.
A public authority learning record may make a government-facing issue clearer. It does not create official approval.
A finance-readiness note may make a portfolio more legible to capital. It does not provide investment advice.
An insurance-relevance record may make exposure and risk-reduction questions clearer. It does not underwrite, price, bind, or approve insurance.
A community safeguards record may make local concerns more visible. It does not create consent, FPIC, social license, or lawful consultation completion.
A workforce exposure record may make transition and occupational risk clearer. It does not create worker approval, union representation, collective bargaining completion, or employer compliance.
An enterprise handoff may make lawful continuation possible. It does not transfer Nexus endorsement, public authority approval, procurement preference, financing approval, insurance approval, or implementation authority.
Two stacks are necessary because public-good architecture must prepare without executing, and enterprise-side actors must be able to continue without inheriting public-good authority.
Without the Public-Good Stack, Nexus would become another implementation marketplace, event platform, or project pipeline.
Without the Enterprise Stack, Nexus would produce records that cannot continue.
The two-stack design solves both problems.
Master Thesis
The Public-Good Stack and Enterprise Stack allow Nexus to convert systemic risk into governed innovation demand without turning public-good readiness into execution or enterprise continuation into institutional endorsement.
The Public-Good Stack is responsible for evidence, records, readiness, public-safe intelligence, stakeholder legitimacy, technical credibility, finance-readiness translation, insurance-relevance translation, safeguards, correction, recognition, maturity, annual proving, durable capacity, and lawful routing.
The Enterprise Stack is responsible only for separated lawful activity where competent actors possess independent authority through law, contract, procurement, financing, insurance, professional review, data governance, safeguards, public authority process, or implementation mandate.
The Public-Good Stack may prepare.
It may record.
It may observe.
It may test.
It may translate.
It may convene.
It may safeguard.
It may report.
It may correct.
It may route.
It may not execute.
The Enterprise Stack may execute only where separately authorized.
It may not claim that public-good records are approvals.
It may not claim that participation is endorsement.
It may not claim that recognition is certification.
It may not claim that finance-readiness is investment advice.
It may not claim that insurance relevance is underwriting.
It may not claim that public authority learning is official approval.
It may not claim that community participation is consent.
It may not claim that workforce participation is representation.
It may not claim that Nexus handoff is implementation authorization.
This is the institutional logic that makes Nexus both usable and safe.
The Public-Good Stack
The Public-Good Stack is the readiness infrastructure of Nexus.
It is where systemic risk becomes visible, structured, documented, tested, translated, corrected, and prepared for possible continuation.
It includes the institutional functions that help turn all-hazards, whole-of-society complexity into usable public-good records.
These functions include evidence intake, risk signal recording, technical-readiness notes, observability, model and simulation records, public authority learning, community safeguards, workforce exposure, university and research participation, council records, maturity records, recognition records, claims review, public-safe reporting, data classification, finance-readiness notes, insurance-relevance records, protection-gap notes, national portfolio records, Universe room records, Core technical records, Network node maturity records, Rails status records, correction records, supersession notices, withdrawal notices, archive records, and lawful continuation records.
The Public-Good Stack is not weak because it does not execute. Its strength is precisely that it prepares the conditions under which competent actors can make better decisions without pretending to make those decisions for them.
A public-good stack that executes too soon becomes unsafe.
A public-good stack that never prepares for continuation becomes irrelevant.
Nexus solves this by separating readiness from execution while connecting both through record-based handoff.
What the Public-Good Stack May Do
The Public-Good Stack may support all-hazards readiness.
It may structure risk signals.
It may create evidence records.
It may support observability.
It may support data classification.
It may support technical-readiness notes.
It may support model and simulation governance.
It may support public authority learning.
It may support community safeguards.
It may support workforce exposure records.
It may support university and research contributions.
It may support councils, working groups, and competence cells.
It may support public-safe reporting.
It may support recognition and maturity records.
It may support finance-readiness translation.
It may support insurance-relevance translation.
It may support protection-gap learning.
It may support national de-risking portfolios.
It may support Nexus Universe annual proving.
It may support Nexus Core technical intensity.
It may support Nexus Network durable capacity.
It may support Nexus Rails record custody and continuation routing.
It may support correction, supersession, withdrawal, and archive.
It may support lawful continuation pathways.
These functions are powerful because they create institutional readability. They help public authorities, MDBs, DFIs, insurers, investors, universities, communities, workers, technology providers, sponsors, and enterprise actors understand what is known, what remains uncertain, what is ready for further review, what must be corrected, and what cannot yet be claimed.
What the Public-Good Stack Must Not Do
The Public-Good Stack must not regulate.
It must not certify.
It must not approve procurement.
It must not approve technologies.
It must not approve vendors.
It must not provide investment advice.
It must not solicit capital.
It must not approve finance.
It must not underwrite insurance.
It must not price insurance.
It must not bind coverage.
It must not issue ratings.
It must not guarantee outcomes.
It must not issue official warnings.
It must not represent governments.
It must not replace public authorities.
It must not grant social license.
It must not replace community consent.
It must not represent workers or unions.
It must not replace professional engineering, legal, cybersecurity, financial, insurance, audit, assurance, or safeguards review.
It must not execute projects.
It must not allow records to circulate as approvals.
The Public-Good Stack exists to improve readiness, not to occupy authority.
The Enterprise Stack
The Enterprise Stack is the lawful continuation environment of Nexus.
It is not the opposite of the Public-Good Stack. It is the separated continuation layer that allows mature public-good outputs to be used by actors who have their own lawful authority.
The Enterprise Stack may include companies, providers, operators, sponsors, contractors, hosts, investors, insurers, National Consortium Companies, Project SPVs, technology firms, professional service providers, infrastructure actors, local partners, implementation partners, and other competent institutions.
It may support technical deployment, service delivery, project preparation, contracting, financing review, insurance review, professional design, procurement participation, implementation, operations, sponsorship, hosting, or commercial activity where separately authorized.
But the Enterprise Stack does not inherit authority from Nexus.
It may use a Nexus record only within the permitted-use label attached to that record.
It may continue only where separate legal, contractual, procurement, finance, insurance, safeguards, professional, data, and public authority requirements are satisfied.
The Enterprise Stack is therefore a continuation environment, not an endorsement environment.
What the Enterprise Stack May Do
The Enterprise Stack may implement where separately authorized.
It may provide technology where separately contracted or approved.
It may operate services where legally and contractually permitted.
It may support project preparation where authorized.
It may participate in procurement where permitted by the relevant procurement authority.
It may seek financing through competent financial processes.
It may seek insurance through competent insurance processes.
It may support infrastructure development where authorized.
It may support data services under applicable data rules.
It may support professional review under competent professional standards.
It may support local delivery through lawful partnerships.
It may support sponsorship under sponsor neutrality rules.
It may support Project SPVs where lawful continuation requires a separate vehicle.
It may support National Consortium Companies where national enterprise-side structures are appropriate.
It may use Nexus records only within their permitted-use labels.
The Enterprise Stack is how Nexus avoids producing public-good records that have no pathway to real-world use.
What the Enterprise Stack Must Not Do
The Enterprise Stack must not claim Nexus approval.
It must not claim public-good endorsement.
It must not claim public authority approval.
It must not claim procurement preference.
It must not claim vendor certification.
It must not claim financing approval.
It must not claim investment readiness.
It must not claim bankability certification.
It must not claim financeability certification.
It must not claim insurance approval.
It must not claim insurability certification.
It must not claim underwriting support.
It must not claim community consent.
It must not claim worker approval.
It must not claim social license.
It must not claim official status.
It must not claim that participation in Universe, Core, Network, Rails, councils, working groups, competence cells, sponsorship, or national assistance creates implementation authority.
It must not use Nexus language, records, logos, recognition, maturity status, or public-good outputs beyond permitted-use rules.
The Enterprise Stack may act only through its own lawful authority.
The One Rail, Two Stacks Model
The One Rail, Two Stacks model is the operating logic that connects the Public-Good Stack and Enterprise Stack without merging them.
One rail means that records, labels, correction, maturity states, decision-use boundaries, permitted-use rules, and lawful continuation routes move through a common public-good operating rail.
Two stacks means that readiness and execution remain institutionally separate.
The Public-Good Stack prepares and records.
The Enterprise Stack may act only where separately authorized.
The public article on Nexus Rails for Development Finance explains how rails can connect evidence, risk, records, and development-finance relevance without turning public-good readiness into financing approval.
The model is necessary because systemic risk work must be able to continue. A technical-readiness note may need professional review. A national de-risking portfolio may need project preparation. A finance-readiness record may need DFI or investor diligence. An insurance-relevance record may need underwriting review by competent insurers. A community safeguards note may need formal consultation. A workforce exposure record may need social dialogue. A technical prototype may need procurement consideration.
Nexus enables records to move toward these next steps without becoming those next steps.
Role of GCRI in the Two-Stack Model
GCRI provides technical credibility inside the Public-Good Stack and supports technical readiness where records may later inform Enterprise Stack review.
GCRI may help define evidence requirements, model descriptions, data provenance, observability, technical-readiness notes, simulation governance, AI output labels, technical challenge records, and Core technical environments.
The public reference for this role is GCRI as the technical backbone of the Nexus ecosystem. Related technical functions include Nexus Observatory, Nexus Standards, Nexus Registry, Nexus Reports, Nexus Labs, Nexus Foundry, Nexus Academy, and Nexus Agency.
GCRI’s technical work may support enterprise review, but it does not certify enterprise actors.
A GCRI-supported technical record may help clarify what evidence exists. It does not approve deployment.
A GCRI-supported simulation may support learning. It does not create official reliance.
A GCRI-supported dashboard may support public-safe reporting. It does not issue official warning.
GCRI protects the boundary between technical credibility and technical authority.
Role of GRF in the Two-Stack Model
GRF provides public-good legitimacy inside the Public-Good Stack and protects public-facing records from overclaim.
The public reference for this role is GRF’s article on how GRF fits with GCRI and GRA. GRF’s participation architecture includes Nexus Governance Councils, the Leadership Council, the State and Government Council, the Community and Indigenous Council, the Media and Civil Society Council, the Industry and Standards Council, and the Academia and Universities Council.
GRF may steward participation, councils, recognition, maturity records, public-safe reporting, claims discipline, community safeguards, public authority learning, and stakeholder formation.
GRF may support the Public-Good Stack by making participation meaningful.
It may support lawful continuation by ensuring that records carry the right limits.
It may not endorse Enterprise Stack actors.
It may not certify companies.
It may not approve projects.
It may not grant social license.
It may not represent governments, communities, or workers.
GRF protects the boundary between legitimacy and authority.
Role of GRA in the Two-Stack Model
GRA provides finance-readiness and insurance-relevance translation inside the Public-Good Stack and supports the readability of records that may later be reviewed by competent financial or insurance actors.
The public reference for this role is GRA’s whole-of-society model for financial services risk management. Domain references include Insurance Nexus, Banking Nexus, Asset Management Nexus, Capital Markets, Development Finance, Sovereign and Public Finance, Financial Regulations Nexus, Critical Systems Finance, and Knowledge Products.
GRA may help make records more legible for capital, public finance, development finance, insurance, reinsurance, risk-transfer, banking, asset management, and financial regulation learning.
GRA may support finance-readiness rooms and insurance-relevance rooms during Universe.
GRA may support National De-Risking Portfolio readability.
GRA may support protection-gap records and public finance context.
GRA does not provide investment advice, fiduciary advice, securities promotion, financing approval, underwriting, brokerage, ratings, guarantees, bankability certification, investability certification, financeability certification, or insurability certification.
GRA protects the boundary between financial readability and financial authority.
Universe as the Public-Good Stress Test
Universe is the annual proving environment where the Public-Good Stack is tested and Enterprise Stack boundaries are enforced under visibility.
The public explanation of Nexus Universe as GRF’s annual mobilization cycle for global risk readiness provides the public reference for this annual system.
Universe may bring public authorities, MDBs, DFIs, insurers, investors, universities, communities, workers, technology providers, sponsors, civil society, media, and enterprise actors into structured rooms.
But each room must preserve the two-stack distinction.
A technology challenge is not vendor approval.
A finance-readiness room is not investment advice.
An insurance-relevance room is not underwriting.
A public authority learning room is not official approval.
A community safeguards room is not consent.
A workforce room is not representation.
A sponsor room is not influence.
An enterprise handoff room is not Nexus endorsement.
Universe tests whether the architecture can remain disciplined when actors, records, technology, visibility, and institutional incentives converge.
Core as Technical Capacity for the Public-Good Stack
Core is the temporary technical intensity layer that supports serious public-good readiness.
It may include high-performance compute, cloud, edge, controlled workspaces, clean rooms, AI workflows, simulation environments, digital twins, telemetry, geospatial intelligence, cybersecurity monitoring, identity and access systems, model registries, data provenance, public-safe dashboards, and verifiable intelligence workflows.
Core belongs to the public-good architecture because its purpose is to support evidence, records, simulation, observability, and technical-readiness.
But Core must not become command infrastructure.
It must not approve models.
It must not certify technologies.
It must not authorize deployment.
It must not issue official warnings.
It must not create procurement preference.
It must not override data sovereignty.
It must not allow technical outputs to circulate beyond their labels.
Core is technical capability under non-execution discipline.
Network as Durable Public-Good Capacity
Network converts annual learning into durable capacity.
The federated network architecture and federation model provide institutional references for distributed capacity.
Network may include national nodes, regional nodes, university nodes, technical nodes, finance-readiness nodes, insurance-relevance nodes, community-facing nodes, workforce-facing nodes, sector nodes, and competence-based nodes.
But nodes are capacity surfaces, not authority surfaces.
A national node is not government.
A regional node is not treaty authority.
A university node is not policy authority.
A technical node is not certification.
A finance-readiness node is not investment advice.
An insurance-relevance node is not underwriting.
A community node is not consent.
A workforce node is not union representation.
Network extends the Public-Good Stack. It does not create distributed authority without mandate.
Rails as Record Custody and Handoff Control
Rails is the infrastructure that connects the Public-Good Stack and Enterprise Stack without merging them.
Rails carries evidence status, steward identity, decision-use labels, permitted-use labels, public-safe language, correction history, maturity status, recognition status, data classification, finance boundaries, insurance boundaries, public authority boundaries, safeguards, and continuation conditions.
Without Rails, a readiness record could become an approval claim.
Without Rails, a technical note could become certification language.
Without Rails, a finance-readiness note could become investment language.
Without Rails, an insurance-relevance record could become underwriting language.
Without Rails, a community safeguards note could become consent language.
Without Rails, a workforce exposure record could become worker approval language.
Without Rails, an enterprise handoff could become Nexus endorsement.
Rails protects meaning.
It allows records to move without becoming more than they are.
This is the operational connection between the two stacks.
National Consortium Companies
A National Consortium Company is an Enterprise Stack vehicle.
It may support lawful commercial, technical, service, sponsorship, hosting, local operations, project-preparation, or implementation-related activity where separately authorized.
It is not the same as a National Nexus Consortium.
A National Nexus Consortium is a public-good readiness structure.
A National Consortium Company is an enterprise-side vehicle.
The company does not inherit public-good authority, public authority status, procurement preference, financing approval, insurance approval, certification, community consent, worker approval, or guaranteed access to Nexus records.
It may use Nexus records only where permitted-use labels allow.
It may operate only under applicable law, governance, contracts, safeguards, finance, insurance, procurement, professional review, data rules, and public authority processes.
The distinction protects both national readiness and national enterprise activity.
Project SPVs
A Project SPV is a project-specific Enterprise Stack vehicle.
It may be created where lawful continuation requires a distinct structure for governance, sponsors, investors, contractors, data rights, safeguards, liability, intellectual property, local partners, public authority interfaces, and implementation.
A Project SPV may receive or use Nexus outputs only within permitted-use labels.
It cannot claim Nexus approval, public authority approval, MDB approval, DFI approval, procurement preference, financing approval, insurance approval, technology certification, bankability, insurability, social license, community consent, worker approval, or implementation guarantee.
A Project SPV is a separate enterprise-side vehicle. It does not carry public-good authority.
Project SPV separation is how Nexus allows continuation without becoming the executor.
Public Authority Boundary
Public authorities may learn from the Public-Good Stack and may engage with Nexus records, Universe rooms, national assistance, portfolios, technical notes, public-safe reports, finance-readiness discussions, insurance-relevance discussions, and safeguards records.
But public authority participation does not create endorsement.
Observation does not create approval.
Input does not create adoption.
Learning does not create official decision.
A dashboard does not create official warning.
A portfolio does not create policy approval.
A technical note does not create public authority validation.
A finance-readiness note does not create public funding approval.
An insurance-relevance note does not create public risk-transfer approval.
GRF’s State and Government Council provides a public-facing reference for public authority learning.
The Public-Good Stack supports public authority learning. It does not become public authority.
Finance and Insurance Boundary
Finance-readiness and insurance relevance are essential parts of the Public-Good Stack.
They make systemic risk more legible to capital, development finance, public finance, insurers, reinsurers, and risk-transfer actors.
But finance-readiness is not investment advice.
Insurance relevance is not underwriting.
A capital-readable record is not a recommendation.
A development-finance note is not finance approval.
A public finance context note is not fiscal advice.
A protection-gap record is not coverage.
An insurance-relevance note is not pricing, binding, brokering, or risk-transfer approval.
GRA’s Development Finance, Sovereign and Public Finance, Insurance Nexus, Banking Nexus, Capital Markets, and Asset Management Nexus provide public references for the financial-services translation role.
The Enterprise Stack may pursue finance or insurance only through competent actors and lawful processes.
Community and Workforce Boundary
Community and workforce records are part of the Public-Good Stack because all-hazards readiness must include lived exposure, local knowledge, livelihoods, labor, safety, transition, access, burden distribution, and safeguards.
The Community and Indigenous Council and the Sustainable Competency Framework provide institutional references for community participation and capability formation.
Community participation is not consent.
A safeguards note is not FPIC.
A community record is not social license.
A workforce forum is not union representation.
A worker exposure note is not worker approval.
A social dialogue record is not collective bargaining.
The Enterprise Stack must not use public-good community or workforce records to imply approval, consent, or representation.
Data, Sovereignty, Security, and AI Boundary
The Public-Good Stack may use data, compute, AI, simulation, digital twins, dashboards, and verifiable intelligence, but only within data governance rules.
Institutional references such as Nexus Sovereignty, Nexus Ecosystem, Verifiable Execution, Verifiable Credentials, Simulation and Foresight, Interoperability and Integration, and Security, Privacy, and Resilience support this layer.
A dataset may be valid but not publishable.
A dashboard may be useful but not public-safe.
A model output may be technically valuable but not decision-ready.
A digital twin may support learning but not official reliance.
An AI output may support analysis but not certification.
Enterprise actors may not use Public-Good Stack technical outputs beyond permitted-use labels.
Standards and Interoperability Boundary
The Public-Good Stack may support standards alignment, record schemas, maturity labels, technical-readiness notes, finance-readiness notes, insurance-relevance records, public-safe language, and interoperability logic.
The Standardization architecture, Nexus Sovereignty, and Nexus Ecosystem provide institutional references for standards and interoperability.
But standards alignment is not certification.
Interoperability is not compliance approval.
Maturity is not accreditation.
Readiness is not assurance.
The Public-Good Stack can make outputs more coherent. It does not replace standards bodies, regulators, auditors, certification systems, or professional assurance.
Public-Safe Reporting
Public-safe reporting is a Public-Good Stack function.
Nexus Reports and GRA’s Knowledge Products provide public references for record-based reporting and finance-facing knowledge products.
A public-safe report may summarize risk signals, evidence, readiness, technical findings, maturity states, public authority learning, safeguards, finance-readiness, insurance relevance, protection gaps, correction history, and continuation boundaries.
It must not imply official approval, government adoption, procurement readiness, financing approval, underwriting, certification, community consent, worker approval, social license, or implementation authorization.
Reports are useful because they make records accessible.
They become unsafe if they make records sound like decisions.
Correction and Claims Discipline
Correction is the safeguard that keeps the two-stack model trustworthy.
The public Built to Correct doctrine and Nexus Claims Discipline provide the public doctrine for correction and claims control.
Correction may be required when:
A Public-Good Stack record is described as approval.
A technical note is described as certification.
A finance-readiness note is described as investment advice.
An insurance-relevance record is described as underwriting.
A public authority meeting is described as endorsement.
A community safeguards record is described as consent.
A workforce record is described as worker approval.
A sponsor contribution is described as control.
A National Consortium Company claims public-good authority.
A Project SPV claims Nexus approval.
A node overclaims status.
An enterprise actor misuses a record.
Correction may include clarification, narrowing, supersession, withdrawal, archive, name-use restriction, public notice, maturity adjustment, sponsor statement correction, or continuation restriction.
Correction is what prevents public-good readiness from becoming false authority over time.
Failure Modes
A mature two-stack architecture must name the risks it is designed to prevent.
Execution Drift
Execution drift occurs when the Public-Good Stack begins to act like an implementation authority.
The remedy is non-execution discipline, role separation, and continuation routing.
Endorsement Drift
Endorsement drift occurs when Enterprise Stack actors use public-good participation to imply approval.
The remedy is permitted-use labels and claims correction.
Certification Drift
Certification drift occurs when technical-readiness, maturity, recognition, or standards-alignment records are presented as certification.
The remedy is status labeling and public-safe language.
Finance Drift
Finance drift occurs when finance-readiness is presented as investment advice, financing approval, bankability, investability, financeability, or capital solicitation.
The remedy is GRA boundary review and correction.
Insurance Drift
Insurance drift occurs when insurance relevance is presented as underwriting, pricing, coverage, brokerage, insurability, or insurance approval.
The remedy is insurance boundary review and protection-gap language.
Procurement Drift
Procurement drift occurs when technology participation, Core exercises, Labs activity, or enterprise handoff is used to imply vendor preference or procurement readiness.
The remedy is procurement firewalling.
Sponsor Capture
Sponsor capture occurs when support is used to imply influence over agenda, records, findings, recognition, finance-readiness, insurance relevance, or continuation.
The remedy is sponsor neutrality and contribution records.
Community and Workforce Overclaim
Community and workforce overclaim occurs when participation records are used to imply consent, social license, worker approval, union representation, or collective bargaining.
The remedy is safeguards review and non-consent, non-representation language.
Rails Misuse
Rails misuse occurs when record custody is treated as approval.
The remedy is decision-use labels and correction.
The Two-Stack Test
Every Nexus record, activity, room, pathway, node, office, company, SPV, report, sponsor statement, or continuation process should be able to answer the following questions.
Is this Public-Good Stack or Enterprise Stack?
What role is being performed?
Who is the steward?
What record is created?
What authority is not held?
What evidence supports the record?
What decision-use label applies?
What permitted-use label applies?
What public-safe language applies?
What claims are prohibited?
What data classification applies?
What public authority boundary applies?
What finance boundary applies?
What insurance boundary applies?
What procurement boundary applies?
What sponsor boundary applies?
What community safeguards apply?
What workforce safeguards apply?
What professional reliance boundary applies?
What correction pathway applies?
What may continue lawfully?
Who is competent to act after continuation?
If these questions cannot be answered, the relationship between readiness and execution is not mature enough for publication, handoff, or continuation.
Strategic Value
The Public-Good Stack and Enterprise Stack give Nexus the architecture required to be useful without becoming unsafe.
For public authorities, the model creates learning and readiness without implied approval.
For MDBs and DFIs, it creates better upstream records without bypassing country ownership, safeguards, procurement rules, project appraisal, or board processes.
For insurers and reinsurers, it creates better risk-reduction and protection-gap records without underwriting.
For investors and financial institutions, it creates finance-readiness without investment advice.
For communities, it protects local knowledge from being converted into consent.
For workers, it records exposure and transition needs without replacing representation.
For universities, it connects research to readiness without converting research into policy approval.
For technology providers, it enables technical participation without procurement endorsement.
For sponsors, it enables contribution without control.
For enterprise actors, it creates lawful continuation pathways without public-good authority transfer.
For the public, it preserves the difference between readiness and approval.
This is why the two-stack model is one of the central institutional innovations of Nexus.
Final Architecture Statement
The Public-Good Stack and Enterprise Stack define the operating separation that allows Nexus to convert systemic risk into governed innovation demand without becoming an executor, certifier, regulator, financial adviser, underwriter, procurement authority, public authority, consent mechanism, or implementation command structure.
The Public-Good Stack prepares readiness.
The Enterprise Stack may act only where separately authorized.
Rails carries records between them without changing their meaning.
Universe tests the boundary annually.
Core supplies technical intensity under non-execution discipline.
Network converts learning into durable capacity without creating distributed authority.
GCRI safeguards technical credibility.
GRF safeguards public-good legitimacy.
GRA safeguards finance-readiness and insurance relevance.
National Consortium Companies and Project SPVs may support lawful continuation but may not inherit public-good authority.
No readiness record becomes approval by circulation.
No technical note becomes certification by usefulness.
No finance-readiness note becomes investment advice by readability.
No insurance-relevance record becomes underwriting by relevance.
No public authority learning becomes official decision by participation.
No community record becomes consent by documentation.
No workforce record becomes representation by inclusion.
No enterprise handoff becomes Nexus endorsement by proximity.
The two-stack model allows Nexus to be ambitious without being unsafe. It allows public-good readiness to become usable and enterprise continuation to become possible while preserving the institutional boundaries that make the architecture trustworthy.
That is the Public-Good Stack and Enterprise Stack.