AXIS BLUE
OPERATIONS CONSOLE
OPERATIONS

A field execution console built to protect the record.

Run-day work captured once, structured correctly, and packaged for leadership. The console keeps reporting clean, identifiers consistent, and evidence tied to every assignment so the output is trusted.

Session Context
Operator identity, work profile, and session state.
Controls guardrails and tool access.
Used in exports and summaries.
Changes labels and export phrasing only.
Included in exports when provided.
Session
—
State
—
Active UID
—
Events
0
Active Assignment
Start an assignment to mint a UID. Reporting, evidence, and capture bind here.
Site: —
UID: —
GPS: —
Type: —
UNI: —
PID: —
Guardrail: structured capture requires an active UID (prevents orphan data).
Advanced Planning & Controls Program, plan, pillars
Run Pillars
Every action ties back to reporting, identification, and structure.
Reporting
Outputs are generated from structured events, not memory. Every summary is defensible.
Identification
UNI, PID, UID, and bucket IDs keep every action traceable across time and teams.
Structure
Capture stays categorized, evidence stays attached, and records stay clean for review.
Continuity
Plans, assignments, and exports persist locally to protect the run-day narrative.
Program / Task
Mint a PID for the run-day objective. UNI binds the day. Assignments inherit both.
Readable label.
Labels only. Structure stays consistent.
UNI: —
PID: —
Program Register
0 entries
No programs yet.
Plan
Build the route list, lock the plan, and keep the run structured.
Loads a starter list (Full Access only).
Sites
0 total
None.
Directive
Guided structure that preserves reporting, identification, and execution flow.
Directive Card
AXIS RUN: Directive
Guided structure that preserves reporting, identification, and execution flow.
Next best action
—
Readiness: —
    Append-only log of directive events.
    Directive event stream
    No entries yet.
    AXIS BLUE is independently developed. Evidence windows and storage limits may be enforced to control cost and prevent misuse.
    Assignment
    Start an assignment to mint a UID. Events, evidence, and exports attach to it.
    UNI: —
    PID: —
    Assignment Register
    0 entries
    No assignments yet.
    Capture
    Use the capture drawer to log identifiers under the active Assignment UID.
    Last capture
    None.
    Evidence
    Evidence attaches to the Assignment UID and can optionally bind to a specific bucket.
    Attachments (Local Manifest)
    0 items
    None.
    Outputs
    Reporting layer. Summaries stay executive-ready while detail remains in exports.
    Executive summary (text)
    Nothing generated yet.
    PDF output
    Generate a PDF for client-ready delivery.
    Output Templates
    Stored locally (demo). Branding templates can be gated by Control access.
    Controls verbosity and included sections.
    Header style selection.
    Branding customization can be gated by Control access.
    Adds a single evidence availability line to summaries.
    Adds an ID register text block to exports.
    Groups captured IDs by category.
    Shows bucket name/details alongside codes.
    Adds filename/size/time list.
    Leave manifest off unless you need it.
    —
    Capture Rules
    Enforces clean data while capturing identifiers and attaching evidence.
    After this limit, bucket details are required.
    If Yes, capture continues into a new group automatically.
    Prevents orphan data outside an assignment.
    If no bucket exists, it binds to assignment UID.
    —