Recovery Command Center
GitHub-native trace → preserve → protect → recover → restore workflow with evidence, competence and human-decision gates.
Open →19 SEPTEMBER 2026 · GITHUB ACTIVE CONTINUITY BACKEND
GitLab ↔ GitHub public gap map
A fail-closed map of public functionality observed on GitLab Pages and its current GitHub status. Functional successor does not mean exact GitLab byte recovery.
High-value gaps already closed functionally
Asset Recovery Situation Room
Adversarial review, competing hypotheses, contrary evidence and decisive-test discipline linked to Case Prism and Second Pair of Eyes.
Open →Connections + deep search
GitHub-native connections explorer plus opt-in same-origin visible-text scan over current GitHub Pages.
Connections → · Search →Portfolio / RICPE freshness
Current GitHub pages now carry the controlled 11 September Portfolio status and the current RICPE source-led continuity layer.
Portfolio → · RICPE →Identity registry 515 vs 380
GitHub discloses the verified rendered-count discrepancy but keeps the canonical 380-ID source unchanged until the exact GitLab registry objects are recovered.
Registry →Por Derecho operating standard
Current methodology is rebuilt from GitHub-controlled Second Pair, Case Prism and continuity controls rather than copied from GitLab markup.
Por Derecho →Specialist September route continuity
The following GitLab-visible specialist route families now have source-led noindex GitHub functional successors. They are rebuilt from current GitHub-controlled dossiers; they are not the missing GitLab source or template bytes.
Orion transparency memorandum
Successor →Portfolio international nexus
Successor →Portfolio board open letter
Successor →Canary Presidency records coordination
Successor →Media / travel / asset recovery
Successor →New Horizons source images
Successor →ACTUA to title documentary journey
Successor →Sun Park history
Successor →Exact-recovery boundary: GitLab Duo configuration, MR discussions/approvals, native pipeline/job artifacts, variables, runners, environments, settings/integrations, Orbit/index state and exact source/template bytes for the specialist routes remain pending authenticated GitLab restoration. Public rendered GitLab HTML is not used as a substitute for those bytes.