Deterministic motion for systems, evidence, and change impact. Three released compositions make the work legible as spectacle first, understanding second, and proof always.
Recorded replay of a historical, simplified topology snapshot. The release media is served locally and does not call the Motion source repository at runtime.
ATLAS MOTION / ESTATEBOOTRELEASED OUTPUT
EstateBoot · 15 seconds · 1920 × 1080 · 30 fps · H.264 video · no audio. If playback is unavailable, the transcript below is the complete sequence.
Composition
EstateBoot
Release
v0.1.0
Source
atlas-motion
Frames
450
FPS
30
Mode
Historical replay
Accessible sequence
What EstateBoot shows.
This detailed sequence is the non-visual equivalent of the released media and remains available with JavaScript disabled.
Grid / opening. The composition opens on a dark architecture-visualisation field before any topology is assembled. The frame is recorded evidence, not live health.
Terminal prompt. A terminal prompt appears as the recorded sequence starts, still before the public surface is named.
Public surface. The composition then names atlas-systems.uk, the public portfolio and Lab surface.
Public spine. It moves through atlas-api-public, the public API spine represented by the snapshot.
Supporting components. The simplified view brings in status, atlas-blackbox, atlas-notify, and specular-telemetry.
Infrastructure anchor.SPECULAR-CORE appears as the single infrastructure anchor derived from the telemetry declaration.
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.
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.
The release binds the EstateBoot composition, exact source commit, pinned topology snapshot, and output hashes. Exact v0.1.0 media and provenance remain under static/media/atlas-motion/v0.1.0/.
Composition 02 / released v0.2.0
EvidenceChain
Reviewed replay of accepted evidence-lifecycle vocabulary. The sequence shows ordering and separation, never a current rollout or live-state result.
ATLAS MOTION / EVIDENCECHAINRELEASED OUTPUT
EvidenceChain · 20 seconds · 1920 × 1080 · 30 fps · H.264 video · no audio. The released keyframes are retained as information-bearing posters in the local asset directory.
Composition
EvidenceChain
Release
v0.2.0
Source
atlas-motion
Frames
600
FPS
30
Mode
Reviewed replay
Accessible sequence
What EvidenceChain shows.
This textual sequence remains available without JavaScript and keeps every lifecycle boundary explicit.
Opening statement. Reviewed evidence vocabulary is ordered, not inferred: every stage needs its own proof.
SOURCE. A named change identity exists as repository source.
CHECKED. Repository-native validation or required checks ran against that exact head.
MERGED. The exact head is integrated on the target default branch.
DEPLOYMENT OBSERVED. A named deployment event was seen for a stated identity.
DEPLOYED. The expected identity is the deployed identity.
RUNTIME VERIFIED. The deployed subject answered a stated runtime check for the expected identity.
LIVE VERIFIED. An independent live check of the public or operator-facing behaviour succeeded.
Order is not proof. A rendered stage never proves the next stage. CHECKED does not imply MERGED; MERGED does not imply DEPLOYED; DEPLOYED does not imply RUNTIME VERIFIED; RUNTIME VERIFIED does not imply LIVE VERIFIED.
Terminal semantics.CLOSED / NOT SHIPPED, FAILED, UNKNOWN / NOT OBSERVED, and NOT APPLICABLE remain separate outcomes.
Input identity: evidence-chain-v0. It is historical reviewed vocabulary from accepted Atlas Infra ADR-0013/ADR-0014 input, rendered offline with no provider, runtime, network, or current rollout claim.
Open exact EvidenceChain provenance and release caveat
Exact release manifest, render sidecar, FFprobe report, frame-MD5 stream, reviewed input, MP4, and released keyframes are vendored under static/media/atlas-motion/v0.2.0/.
Composition 03 / released v0.3.0
TwinImpact
Twin-supplied mapping of a proposed change, mapped without inference. A validated real Atlas Twin export for a proposed change in AtlasReaper311/atlas-api-public is shown against Twin-supplied systems and relationships that COULD BE AFFECTED, followed by supplied evidence, limitations, and provenance.
ATLAS MOTION / TWINIMPACTRELEASED OUTPUT
TwinImpact · 18 seconds · 1920 × 1080 · 30 fps · H.264 video · no audio. The poster is the released 1200 × 630 final hold frame. If playback is unavailable, the transcript below is the complete sequence.
Composition
TwinImpact
Release
v0.3.0
Source
atlas-motion
Frames
540
FPS
30
Mode
Twin-supplied mapping
Accessible sequence
What TwinImpact shows.
This textual sequence remains available without JavaScript and keeps the supplied evidence boundaries explicit.
Identity / proposed change. The released composition begins with a validated real Atlas Twin export for a proposed change in AtlasReaper311/atlas-api-public. The supplied subject is a git_range from base 8ff638f92cfc3a3ec5e2243ecb6464c964bd8e65 to head 02a0e6a7bfac66ea85cff536d0c89e6406abee5f.
COULD BE AFFECTED / system view. Twin supplies 51 nodes and 60 relationships. The presentation shows systems and relationships that COULD BE AFFECTED. NOT OBSERVED IMPACT.
Declared relationships / evidence context. The sequence presents Twin-declared relationships and supplied evidence context. The relationship subset is a deterministic presentation selection. It is not an importance ranking or a causal claim.
Boundaries / non-claims.COULD BE AFFECTED is the bounded label. NOT OBSERVED IMPACT. The evidence does not prove deployment, runtime impact, provider state, current live state, current service health, or current estate health.
Provenance close. The chain is validated Atlas Twin export → Atlas Motion TwinImpact → v0.3.0 released evidence → repository-local public presentation. The release and render are offline evidence only. Twin export passport fingerprint: 48b61a17e77f04b738dc4947e08f9f8eb70099ddd0b0420beb68262d623d65da.
Input contract: atlas-twin-motion-export/v1. Twin version 1.1.0. The source export is vendored locally and is not a current runtime feed.
Open exact TwinImpact provenance and release boundary
FFprobe, frame-MD5, input export, and manifest are vendored locally.
Exact release manifest, Twin export, render sidecars, FFprobe report, frame-MD5 stream, MP4, and poster are vendored under static/media/atlas-motion/v0.3.0/. No current deployment, runtime, provider, live-state, service-health, or estate-health claim is made.