Public evidence architecture
Evidence should mature before language does.
This page explains the proof expected before the proposed campus can move from concept to control, delivery or operation. It is a readiness framework, not a claim that every document, permission or capability exists.
Evidence control
Every public claim should have a route back to source.
- 01
Source
Preserve the originating record, owner, date and precise statement before creating public language.
- 02
Challenge
Separate verified fact, assumption, dependency, gap and reserved information under accountable review.
- 03
Authorise
Match the wording and next action to the evidence state, decision rights and approved scope.
- 04
Recheck
Retain review dates, change history, evidence links and stop logic so claims cannot outrun reality.
Evidence states
Progress is recorded as a controlled state change.
Each promotion should identify the source, accountable owner, review date, decision supported and approved public wording. A later state cannot be inferred from an earlier one.
Current readiness
Eight workstreams must converge.
Current public positions remain deliberately conservative. Private evidence, if available, would still require controlled review before it could change public status.
Capital discipline
Capital follows a question and stops when the answer is weak.
No gate is a forecast or promise. Each stage remains conditional on evidence, authority, funding and the continuing strength of the operating case.
- 01
Explore
Use limited predevelopment resource to test the scientific, market, location and operating questions that could invalidate the proposal early.
- 02
Control
Consider conditional rights only when a specific site has credible planning, infrastructure, commercial and legal potential.
- 03
Design
Develop the technical brief, test fit, cost plan and operator model only for scope supported by defined users and decision needs.
- 04
Commit
Make a material capital commitment only after funding, authority, risk allocation, permissions and delivery responsibility are documented.
- 05
Deliver
Release capital against controlled design, contracts, programme, contingency, assurance and evidence that the next stage remains viable.
- 06
Operate
Describe capability as active only after commissioning, competent people, procedures, quality systems, safe operations and any necessary licences exist.
Controlled diligence
What a serious evidence pack should contain.
This is the proposed architecture of a diligence pack. Inclusion here does not mean a document is complete, approved or available for release.
- 01
Corporate and governance
Entity records, ownership and rights mapping, board authorities, conflicts controls, decision records and the proposed project structure.
- 02
Site and property
Plot identity, ownership, title, rights, access, constraints, site control terms and the relationship between selected land and the proposed programme.
- 03
Planning and infrastructure
Planning, safeguarding, ground, environmental, transport, utility, servicing and resilience evidence tied to the specific parcel and phase.
- 04
Market and demand
Defined users, discovery records, use cases, alternatives, access requirements, commercial testing and the evidence supporting any utilisation assumption.
- 05
Technical and operating model
Approved work types, adjacencies, flows, equipment strategy, operator responsibilities, quality boundaries, licence path and commissioning logic.
- 06
Capital and economics
Stage-specific uses, cost plan, contingency, funding sources, operating assumptions, sensitivities, downside responses and approval thresholds.
- 07
Risk and assurance
Risk ownership, evidence gaps, stop rules, safety and security considerations, independent review and records of material decisions.
Control standard
Every material claim needs a source and an owner.
A controlled record should identify the exact claim, evidence source, evidence date, accountable reviewer, current state, decision supported, limitations and next review point.
Concept imagery, correspondence, meetings and public policy sources can provide context. They cannot prove site control, demand, commercial agreement, funding, permission, construction or operating capability.
Read the public status definitionsAccess boundary
Public transparency does not remove confidentiality.
Commercial terms, site records, scientific opportunity files, capital assumptions, risk detail and advice may require identity checks, a defined purpose, confidentiality and controlled disclosure. Access remains discretionary and does not constitute an offer or commitment.