Canonical status record
One release. One route map. One validation state.
This page is the single source of truth for what HBF currently is, which release is citable, which routes are canonical, and exactly how much has and has not been validated. Every canonical page and export must agree with this record.
Machine-readable form: /status/status.json. If a page on this site disagrees with that file, the file is correct and the page is a defect.
Product identity
| Name | HBF Research Preview |
|---|---|
| What it is | An independent research-software project for transparent, bounded p–¹¹B calculations and external validation. |
| What it is not | Not a reactor. Not an engineering-performance prediction. Not an experimentally validated result. Not an independently reviewed scientific claim. |
Canonical release
| Version | 1.0.0 |
|---|---|
| Released | 21 August 2026 |
| Build tag | v700-RESEARCH-PREVIEW-1.0 |
| Source repository | Not yet published A public repository with issue history, CI and a tagged release has not been created. A repository URL will not be shown here until one exists. |
| Git commit | Not available There is no public commit to cite until the repository is published. Commit hashes are never invented. |
| Version DOI | Not registered |
| Concept DOI | Not registered DOI registration requires a depositor such as Zenodo. No DOI value is displayed until one resolves. |
| Licence | Not yet selected Selection requires a third-party rights review across dependencies and bundled assets. |
Validation status
| Internal scientific gates | 56 passed, 0 failed
Command: |
|---|---|
| Independent external decisions | 0 completed / 3 proposed
No independent external scientific decision has been completed. An in-house or AI-generated cross-implementation check is an internal check, not independent validation. |
| Experimental validation | None |
| Peer review | None |
| Accessibility conformance | Not certified
Automated scanning is not WCAG conformance certification. No qualified accessibility reviewer has assessed this release. |
Accountability
A university partnership cannot be approved with an anonymous brand as the accountable party. The following fields are required and are not yet supplied:
| Legal entity | Not supplied |
|---|---|
| Scientific lead | Not supplied |
| Technical lead | Not supplied |
| Data contact | Not supplied |
| Security contact | Not supplied |
| Authorized signatory | Not supplied |
| Funding and conflicts | Not supplied |
These are verified facts about real people and a real legal entity. They are deliberately left empty rather than filled with plausible-looking placeholders: publishing an invented accountable party is worse than publishing none, because it looks like an answer. See Team & Governance.
Financial and token activity
This research surface contains no financial, token, wallet, presale, referral or purchase functionality. That separation is enforced mechanically at build time by scripts/harness/check-research-token-boundary.py, which fails the package if any such route, link or integration is present.
Whether financial activity continues elsewhere under a separate domain, brand and legal entity is a business and legal decision reserved to the operator. This package guarantees only that the research surface is clean.
Archived routes — do not cite
The following older generations remain reachable for historical reference but are not the canonical product: /platform/, /research-hub/, /workbench/. Each carries an archived notice. Older lab routes redirect to their canonical successors under /labs/.