INTERACTIVE EXHIBIT · SELF-HOSTED INFRASTRUCTURE

Ark Fleet architecture

A look at the infrastructure decisions behind the work, not an equipment catalog.

Explain topology, commissioning, recovery and what has actually been observed without exposing operational access details.

Local review record. Not a release or a claim of completed integration.

A peek at the wiring plan

Historical topology: router to QNAP access and SODOLA core; control computer and fleet branches, with unresolved storage path.
Historical architecture excerpt from the existing Fleet Field Manual. Ordered, owned, unresolved and offline labels describe that source, not current measurements. The animated trace is paused; it is not live traffic. Internal node identifier omitted.

The intended path

  1. 01

    Identify the component and role

  2. 02

    Separate owned, installed, tested and planned

  3. 03

    Trace the intended connection

  4. 04

    Attach a dated observation before claiming operation

What the record supports

OBSERVED

A read-only inventory evidence adapter exists. Its contract labels records as historical inventory projections, not live telemetry.

ARCHITECTURE

A public-safe wiring-diagram preview should show relationships and boundaries while excluding addresses, credentials, serials and operational procedures.

UNVERIFIED

Current device health, current wiring and live benchmark streams; the diagram is a historical source excerpt, not a verified operating network.

NEXT CHECK

Validate the displayed historical relationships against current evidence before making current-network claims; retain the public-safe scope.

Diagram copied from the existing source geometry. No addresses, credentials, serial numbers or operational instructions are included. Publication remains subject to the Architect’s review.

Source basis: Ark data-center evidence adapter README inspected 13 November 2026; Portabela infrastructure direction.