Damocles · Credibility Release One · Technical candidate

Recovered behaviour, made reviewable.

CR1 is a technical candidate for a coherent, deterministic and testable modern Windows evaluation build within a deliberately limited recovery scope.

Candidate records report a coherent deterministic route and matching declared outcomes between the modern reference and Windows-native runtimes. CR1 is not yet an accepted public release.

What CR1 is

A credibility milestone, not a finished remake.

This is not a complete remake. It is a technical candidate with a deliberately bounded scope.

CR1 is designed to remove a particular kind of uncertainty: whether enough original behaviour can be recovered from evidence to support a modern implementation that can run, be replayed and be compared against accepted observations.

It does not claim rights ownership, a complete game, an authorised remaster, or a public product release. Its value lies in the specificity of the demonstrated scope and the audit trail around it.

Evidence snapshot

Public records, with their boundaries intact.

Each record names its status and public source. These summaries do not substitute for the evidence or pending review gates.

Candidate result · Technical candidate

Coherent route candidate

The candidate record describes one normal-start route that enters the bounded State Office slice, exercises its declared contexts, collects the recovered file and returns with the collection state retained.

Candidate result · Human review pending

Repeatable runtime comparison

Candidate records report repeatable results and matching declared outcomes between the TypeScript reference and Windows-native runtimes across the recorded executions.

Method · Publication control

Explicit authority boundary

Recovered findings, supported reconstruction, authored presentation and behaviour outside the demonstrated scope are kept distinct.

Read the evidence records and limitations

Windows evaluator

Why an executable matters.

For a non-technical review, a modern executable turns recovered understanding into something that can be assessed repeatedly rather than merely described. For technical review, it provides a defined target for replay, validation and controlled comparison.

That is a meaningful engineering milestone. It does not erase the remaining unknowns or extend the CR1 claim beyond its recorded scope.

The Windows x64 evaluator candidate is for controlled private review only. Independent clean-machine Windows evaluation remains open.

Decision-makers

What questions has CR1 narrowed?

Understand the bounded milestone, its preservation and feasibility relevance, and what has deliberately not been claimed.

Read the overview

Developers

How is the claim checked?

See the public-level model of provenance, deterministic validation and confidence-labelled reconstruction.

Read the technical account

Review

What is available publicly?

Inspect the sanitised evidence records, citations, limitations and questions that remain open.

Review evidence