# E06. Administration frontend analysis

## Acquisition record

The 23 July record describes recovery of seventy frontend modules by following imports exposed by a Vite development deployment. Embedded source maps supplied original TypeScript comments. The recorded acquisition did not use a login or invoke the authenticated data API. This report reviews the saved analysis, without contacting the deployment. [S1]

## Interface observations

The client includes mail-status metrics, inbox and outbox views, templates, auto-reply controls, task boards and a database browser. A delivery-repository view uses clone URLs and availability labels with refresh controls. These components demonstrate an interface for managing messaging and monitoring repository availability; they do not supply verified sending volumes or suspension-response timings. [S1]

Wallet views expose import, balance preview, refresh, claim and bulk-claim operations. Mnemonic and ColdKey fields, together with Bittensor-related interface language, connect the intended workflow to collection targets found in the payloads. The source also refers to EVM and Aptos. No transaction receipt or backend execution log accompanies these interface observations.

## Authorization and backend limits

A frontend helper accepts either a super-administrator flag or an email comparison. Its use in navigation and route guards establishes client behavior only. It does not prove backend enforcement or that a single account exclusively controls wallet operations. The personal mailbox value is omitted. Source comments suggest a Python/Django backend, but that backend was not recovered with the client. [S1]

The presence of a signup route does not demonstrate open registration. The record later identifies a disabled-signup message, qualifying its initial multi-operator interpretation. Neither a role model nor a task board establishes team size.

## Assessment

The recovered interfaces connect delivery-repository monitoring and wallet-management functions in one application. This is evidence of software design and intended workflow, not proof of an end-to-end operational service or financial theft. The absence of wallet destinations in the reviewed frontend cannot establish that those destinations are unrecoverable elsewhere. Provider records, backend source, configuration or transactions would be required for stronger claims.