engine-revival

Public tooling spine for reviving historical game engines, SDKs, rendering libraries, CGI toolkits, and studio technology lineages.

This repo publishes public-safe metadata, schemas, validation tools, target matrices, generated summaries, and evidence packets. It does not publish proprietary SDKs, leaked source, game assets, private donor files, private contact data, credentials, restricted media, or upstream source snapshots.

Current Public Boundary

BRender is the current flagship evidence lane. Engine Revival now preserves the public BRender Archival v0.1.1 boundary:

• BRender Archival release commit: 11b5a8d539e911a9c07991b751402a7d51bf1bde.
• Release tag: v0.1.1.
• PR: HarperZ9/brender-archival#9.
• Candidate contents: bbf3ba2f26ee9ae265759e282dc1454b2234b6be.
• Upstream public source snapshot: foone/BRender-v1.3.2 at d88d0ed41122664b9781015b517db64353e16f19.
• Native verification: 21/21 CTest targets under Visual Studio Win32 Debug.
• Release media source run: brender_core_softrend_render over dat/sph32.dat with final_frame_lit=19284 valid=true.

Two build/evidence boundaries are intentionally separate:

• Engine Revival local 12-target portable materializer: public metadata and scaffold for the portable core ladder.
• External pinned BRender Archival v0.1.1 21-target release: public receipt imported from HarperZ9/brender-archival at commit 11b5a8d539e911a9c07991b751402a7d51bf1bde.

The relationship boundary is explicit:

• Retro Engine equals play.
• Engine Revival equals preservation, research, metadata, and evidence.
• BRender Archival equals the verified specific BRender restoration.
• Generic Retro output is never BRender proof.

Engine Revival imports BRender Archival's public-safe receipt, transcript, media, and provenance. It does not import local experimental branches, private build trees, upstream source, binaries, or assets.

Non-Claims

The BRender evidence packet does not claim completed textured TIA output, x64 readiness, production readiness, adoption, endorsement, or vendored upstream source/assets. The experimental textured TIA path executes in BRender Archival, but public release notes record black output from a measured vertex-layout/state mismatch.

First Workflow

python -m pip install -e ".[test]"
engine-revival seed
engine-revival validate
engine-revival audit-public
engine-revival index
engine-revival report
python -m pytest

BRender Evidence

• BRender archival packet
• Sanitized 21-target transcript
• 21-target attempt record
• Release media provenance
• Period pipeline still
• Period pipeline contact sheet
• Orbit frame sequence
• Social card

BRender Harness Metadata

engine-revival materialize-brender-harness `
  --source-root C:\path\to\BRender-v1.3.2 `
  --output-root C:\path\to\brender-v132-portable-core-harness

This command is retained as public harness metadata and scaffolding. The verified 21-target restoration boundary is not produced by this local materializer in this patch. Use an explicit pinned external checkout recipe for that receipt:

git clone https://github.com/HarperZ9/brender-archival.git <brender-archival-v0.1.1>
git -C <brender-archival-v0.1.1> fetch --tags origin
git -C <brender-archival-v0.1.1> checkout 11b5a8d539e911a9c07991b751402a7d51bf1bde
git -C <brender-archival-v0.1.1> rev-parse HEAD

The final command must resolve to 11b5a8d539e911a9c07991b751402a7d51bf1bde. Engine Revival stores the public receipt and provenance, not the external implementation checkout.

Third-party notices

See THIRD_PARTY_NOTICES.md. Engine Revival code is MIT licensed. The upstream BRender source snapshot is recorded as MIT-licensed source provenance and is not vendored here. Imported or derived BRender Archival release media/transcript/provenance is treated as AGPL-3.0-or-later covered third-party material unless verified asset-specific evidence grants otherwise.

Public Docs

• Revival mission
• Lost engine directory
• BRender archival packet
• Public boundary
• Recovery workflow
• Remaster lane
• Generated public index
• Generated corpus database
• Generated targets
• Generated sources
• Generated artifacts
• Generated accessions
• Generated tasks
• Generated milestones
• Generated reproductions
• Generated snapshots
• Generated production readiness
• Generated build environments
• Generated harnesses
• Generated attempts
• Generated coverage
• Generated rights summary
• Contributing

---

Zentropy Labs · order out of entropy. An independent lab building evidence-first tools that leave a re-checkable artifact behind. Built by Zain Dana Harper in Seattle. The full workbench is at Project Telos.