Team & Governance
Who is accountable for this research
A university cannot approve a partnership with an anonymous brand as the accountable party. This page exists to answer, in under two minutes: which legal entity is responsible, who is the scientific lead, who signs an agreement, and how is funding disclosed.
Current state: these facts have not yet been published.
The fields below are deliberately empty. They are facts about real people and a real registered entity, and this project does not publish invented ones. A missing scientific lead is a gap an evaluator can price and ask about. A fabricated scientific lead would invalidate the entire scientific record the moment it was checked — so the empty state is the honest one, and it is enforced: scripts/harness/check-governance-facts.py fails the build if any of these fields is filled with an invented stand-in value, a non-deliverable example address, or a malformed ORCID.
Legal entity
| Legal name | Not published |
|---|---|
| Jurisdiction | Not published |
| Registration number | Not published |
| Registered address | Not published |
| Data controller | Not published |
Accountable roles
Each role is published only once its holder is verified, with affiliation and ORCID where applicable.
| Scientific lead | Not published Accountable for scientific claims, source admission policy and claim boundaries. |
|---|---|
| Technical lead | Not published Accountable for the software, releases and reproduction. |
| Data contact | Not published Point of contact for data-use agreements and real detector data. |
| Security contact | Not published Route for responsible disclosure. See SECURITY.md. |
| Authorized signatory | Not published The person who may sign an NDA, DUA, MoU or contract. |
Funding and conflicts of interest
| Funding sources | Not published |
|---|---|
| Conflicts of interest | Not published |
| Research integrity contact | Not published |
A funding and conflict statement is a precondition for institutional engagement, not an optional extra. Where a project has any financial or token-related activity under common control, an evaluator will expect that relationship to be stated plainly here rather than discovered later.
Research independence
This research surface contains no financial, token, wallet, presale, referral or purchase functionality. That is enforced at build time rather than asserted: scripts/harness/check-research-token-boundary.py fails the package if any such route, link, wallet integration or purchase call-to-action is present.
Whether related financial activity continues elsewhere, and under which separate domain, brand and legal entity, is a decision for the operator and its counsel. It is recorded as an open decision in the build harness rather than silently resolved.
Partnership principles
- No reactor-performance or net-energy claim is made.
- No outcome is predetermined; the partner chooses or approves the independent method.
- Negative results, disagreements and abstentions are published, not withheld.
- Conflicts, funding and roles are disclosed before work begins.
- Data, IP and publication terms are agreed before any data transfer.
- No token purchase, wallet connection or financial participation is required or requested.