Read-only source posture
Source evidence is read-only by default, with derived analysis performed against verified copies or derived indexes.
Recovery + diagnostics
A standalone Windows recovery and reconstruction product built around evidence safety, verified working copies, provenance, confidence assessment, durable recovery missions, diagnostics, and recovery reporting.
What it does
Deep Orbit treats recovery as evidence work. Source material is protected, derived work keeps provenance, confidence is explicit, and interruption is designed to preserve rather than corrupt the mission.
Source evidence is read-only by default, with derived analysis performed against verified copies or derived indexes.
Recovered and derived items retain provenance so findings can be traced back to the evidence and method that produced them.
Recovered remnants, reconstruction candidates, correlations, and interpretations carry visible confidence instead of being presented as certainty.
Recovery work persists as a mission with state, evidence references, analysis progress, derived artifacts, and a recoverable execution history.
SAFE STOP behavior preserves evidence and mission state while explaining why the recovery process stopped.
Package findings, timelines, reconstruction candidates, hashes, confidence, and provenance into reviewable recovery reports.
Interface
The standalone WinUI shell is organized around mission state, evidence, analyzers, reconstruction candidates, media, timelines, and reporting. The panel below is an explanatory website illustration.
The user should always be able to tell what source is being examined, what was derived, what changed, what remains uncertain, and whether the mission can be resumed safely.
Requirements
Deep Orbit owns its launch, recovery mission, contracts, packaging, and release lifecycle. It must not require a PowerShell Principal source checkout to perform core recovery work.
Roadmap
The product repository is already seeded with stable analyzers, a standalone mission/import boundary, recovery implementation references, packaging, and a WinUI shell. The next work is validation and defect isolation rather than broad replacement.
Confirm the standalone analyzers preserve expected behavior and evidence semantics against the stable reference baseline.
Prove import, persistence, SAFE STOP, resume, provenance, and derived-artifact behavior across realistic recovery missions.
Prove x64 and ARM64 packaging, setup, launch, dependencies, and repair behavior outside a developer checkout.
Only after standalone parity and clean-machine evidence should broader distribution or reduction of the full Principal implementation occur.
Downloads
The website does not expose a recovery installer until packaging, clean-machine launch, evidence handling, and release checks have a verified artifact to publish.
Standalone builds are used for validation and defect isolation. They are not represented as supported public releases here.
Public distribution stays closed until the product proves independent launch, packaging, mission safety, and recovery parity.
Automation foundation
Principal may provide generic execution, logging, diagnostics, and launch integration, but Deep Orbit owns the full recovery product, evidence semantics, mission lifecycle, and release path.