Flywheel first · Retro Systems Lab · verify

BRender Archival.

Flywheel is the single primary platform. BRender Archival sits below it as the verify route for a specific restoration lane, next to Retro Engine for play and Engine Revival for preserve.

BRender Archival v0.1.1 is public at release v0.1.1, with main pinned to 11b5a8d539e911a9c07991b751402a7d51bf1bde. The repository is AGPL-3.0-or-later; upstream BRender MIT source is referenced, not vendored.

Flywheel platform Preserve layer Play layer BRender source Evidence manifest

Play, preserve, verify.

Directed diagram: Retro Engine play leads to Engine Revival preserve, then BRender Archival verify, all under Flywheel.
Shared directed crossover visualization. It shows route relationship and evidence flow, not runtime dependency or product parity.
  1. Play: Retro Engine
  2. Preserve: Engine Revival
  3. Verify: BRender Archival
Play

Retro Engine

Interactive browser studio for owned media experiments. It can produce companion visuals, not BRender evidence.

Preserve

Engine Revival

Public MIT preservation spine that records imported AGPL-covered BRender media and receipts.

Verify

BRender Archival

Specific BRender restoration evidence route. It does not inherit proof from generic retro visuals.

Abstract verification grid separating BRender-specific evidence from generic Retro Engine output.
Deterministic generator-owned identity capture for the BRender verify lane. It does not prove restoration completeness, rendering correctness, or performance.

Evidence boundary.

Verified public release

BRender Archival public main and release v0.1.1 both resolve to 11b5a8d539e911a9c07991b751402a7d51bf1bde. The release records 21/21 native CTest targets and a measured release media source run. The repository is AGPL-3.0-or-later, and upstream BRender MIT source is referenced from a public checkout rather than vendored.

Does not prove: completed textured TIA output, x64 readiness, production readiness, adoption, endorsement, performance, legal completeness, or vendored upstream source or assets.

Companion renderer boundary

Retro Engine is a companion renderer, not BRender proof. generic Retro Engine output is not BRender evidence. Engine Revival can preserve release state, but the verify claim remains owned by BRender-specific receipts.

Companion graph.

The route stays reciprocal with the platform, creative tools, and evidence tools while keeping proof ownership distinct.

Flywheel Retro Engine Engine Revival Studio Engine BuildLang Build Color Gather Index System catalog

Responsive contract: this page is static without JavaScript, keeps readable flow at 320px and 390px widths, and must remain usable at 400% zoom with print, forced-colors, text-spacing, focus, and reduced-motion modes.