The Wizard NexusIn developmentThe standalone Sentinel app is not yet available to download or purchase.
Roadmap · Updated August 13, 2026
Built inside Arcane. Becoming Sentinel.
Current status
Active incubation inside Arcane OS
Standalone downloadNot available
Current packageArcane Investigator
Next dependencyArcane SDK boundary
Extraction phases
Advance by evidence, not a speculative date.
Each phase has an exit condition. Sentinel moves only when the next boundary can be tested without duplicating or freezing the Arcane runtime.
- Now
Active incubation
Prove the investigative workflow in Arcane OS.
Refine source review, analysis, reporting, and privacy guardrails while shared runtime contracts mature.
- Next
SDK boundary
Stabilize the services Sentinel actually consumes.
Version storage, identity, document navigation, components, packaging, and failure contracts.
- Then
Standalone extraction
Generalize, migrate, and verify Sentinel.
Remove case assumptions, preserve source provenance, add synthetic fixtures, and prove package equivalence.
- After
Independent releases
Maintain one authoritative Sentinel application.
Ship versioned standalone releases without forking or vendor-freezing the Arcane runtime.
Release dossier · Review criteria
Six requirements for a safe move.
Six requirements to investigate before release. Open each file to see the evidence required; these are not completed milestones.
Reliable shared services
Storage, identity, components, document inspection, and packaging must use versioned SDK interfaces with defined failure behavior.
A fresh workspace for every investigation
Case-specific names, identifiers, paths, storage keys, and workflow logic must become neutral workspace contracts.
Testing that protects private records
Tests must use synthetic examples, without copying private filings, contacts, evidence, or reports.
A traceable history of the code
The source commit, original paths, Git blobs, and SHA-256 records must distinguish unchanged files from adapted derivatives.
A safe move for existing workspaces
Existing local workspaces need a deliberate storage-identity migration and a tested rollback or recovery path.
The standalone app passes its essential checks
Critical review, citation, export, and package-integrity tests must pass against the standalone build.
Commercial launch gates
A price appears before a checkout does.
The planned pricing page describes the intended access model. Payment does not open until the product and operating boundary are ready.
- Extracted v1 capabilities confirmed and documented
- Export, deletion, backup, and access-control paths tested
- Processing, storage, support, and abuse-prevention costs measured
- Hunter, survivor-waiver, and nonprofit capacity funded
- Privacy, acceptable-use, license, and purchase terms published
- Support and implementation scopes defined without unverified compliance claims
Follow the source
This public site is the record of the extraction plan.
Application code arrives only after the Arcane SDK and migration gates are ready. Until then, this site remains the public planning contract.
Explore TWiN on GitHubSee planned pricing