Skip to content

fix: separate Core Development into its own page - #22

Merged
RFT-SIRM merged 2 commits into
mainfrom
fix/separate-core-development-page-2026-11-13
Nov 13, 2026
Merged

RFT-SIRM merged 2 commits into
mainfrom
fix/separate-core-development-page-2026-11-13

Conversation

@RFT-SIRM

Copy link
Copy Markdown
Owner

What this fixes

The Core Development portfolio was injected immediately before </body> in the interactive Research Explorer. Since the Explorer already had a complete footer, the portfolio appeared as a second page appended underneath it.

Changes

  • Create a dedicated MkDocs page at /core-development/.
  • Add it to the Core Development navigation, documentation home, and README.
  • Remove the HTML injector and its source fragment.
  • Keep /interactive/ as the standalone Research Explorer and add CI checks that reject portfolio injection there.
  • Preserve explicit evidence boundaries: QPU Stage 11B is a three-mode closed-system model (not measured hardware fidelity), local-retune raw artifacts are not yet archived; financial dispute adjudication remains open; higher-moment finite bridges and Phi-Genesis open questions remain scoped accurately.

Verification

  • Checked the published gh-pages HTML: the Research Explorer footer was followed by the injected portfolio section, confirming the cause.
  • Checked that all linked project repositories exist and inspected their current status documents.
  • Checked the prepared README, MkDocs navigation, page content, and workflow diffs.
  • No build or deployment result is claimed yet; CI must validate the new separate-page build before merge.

@RFT-SIRM
RFT-SIRM merged commit e60ee92 into main Nov 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant