Experience / recorded replay

Atlas Motion
EstateBoot

A deterministic motion study of a bounded public topology snapshot. This page presents the exact released artifact so the composition, source identity, and evidence boundary can be inspected without running Motion in the browser.

Back to LabRead provenance

Preview · v0.1.0

The released EstateBoot composition.

Recorded replay of a historical, simplified topology snapshot. The media is served from this repository and does not call the Motion source repository at runtime.

EstateBoot · 15 seconds · 1920 × 1080 · 30 fps · H.264 video · no audio. If playback is unavailable, the transcript below is the complete sequence.
Motion release
v0.1.0 / tag v0.1.0
Source identity
AtlasReaper311/atlas-motion
Source commit
857f2a575480590c75186694a79860f60fcf899d
Composition
EstateBoot
Render
450 frames / 15 seconds / 30 fps
Data mode
Recorded replay of a historical snapshot

Accessible sequence

What EstateBoot shows.

This detailed sequence is the non-visual equivalent of the released media and remains available with JavaScript disabled.

  1. Public surface. The composition begins with atlas-systems.uk, the public portfolio and Lab surface.
  2. Public spine. It moves through atlas-api-public, the public API spine represented by the snapshot.
  3. Supporting components. The simplified view brings in status, atlas-blackbox, atlas-notify, and specular-telemetry.
  4. Infrastructure anchor. SPECULAR-CORE appears as the single infrastructure anchor derived from the telemetry declaration.
  5. Declared relationships. Six source-declared relationships resolve: atlas-systems → atlas-api-public, status → atlas-api-public, atlas-api-public → specular-telemetry, atlas-blackbox → specular-telemetry, atlas-blackbox → atlas-notify, and specular-telemetry → SPECULAR-CORE.
  6. Evidence close. The frame closes on the release and render identity: six components, one infrastructure anchor, and six relationships from the pinned snapshot.

Snapshot identity: estate-boot-v0-5b970a9bf3b6. It was captured on and is historical/pinned evidence, not a live topology feed.

Release and evidence

Bound to exact source and output.

The release manifest, render sidecar, and vendored media were checked together before this surface was added.

Release binding

Release
v0.1.0 · candidate release
Source commit
857f2a575480590c75186694a79860f60fcf899d
Manifest SHA-256
7c13a6001eda8759a89e9922e6792d2f19cd83f8d2477abb83e810f37dcaed82
Release archive SHA-256
15cfe10ce335b823aa9becd00d5a3f95e45c343699e17a476e249e8f3dece5bf

Topology evidence

Snapshot
estate-boot-v0-5b970a9bf3b6 · simplified
Source commit
5b970a9bf3b66b5469ce883aacec4a4b496e72cc
Source blob
4fb554265a60c320f74500af1cfebc9465921484
Snapshot SHA-256
00acfc41c19b9c5e5477c6150cd917c1e880c541f356faf95ca2a6f294ea41fd

Rendered output

Composition
EstateBoot · 1920 × 1080
Render evidence
30 fps · 450 frames · H.264 · yuv420p · no audio
MP4 SHA-256
c7c437b70d66eed9c1f8c50b4ea08adf6833981dcf242dd5e98325312aab6de4
Render sidecar SHA-256
c25d0e3bda706247b51deb67eaba92e089cc07e5de478d96dec89384bb6b9ce7

Why this is deterministic release evidence

The Motion release binds the EstateBoot composition, the exact source commit, the pinned topology snapshot, and the output hashes. Atlas Systems vendors the resulting MP4 and poster as versioned static assets. It does not execute Motion, fetch the private Motion repository, or require a Motion API or provider at page load.