SBL-TOP-001 Terminal Operator Manual

SABRELAKE
SECURITY
CLASSIFIED

Sabrelake Security
Terminal Operations Division
Internal Publication

Document No. SBL-TOP-001
Revision: 4.1
Date: [REDACTED]
Pages: CLASSIFIED

RESTRICTED -- AUTHORISED OPERATORS ONLY

Sabrelake Terminal Operations Manual

Terminal Operator
Procedures and
Reference Guide

SBL-TOP-001 // All Sector Dispatch Terminals

Applicability All Sabrelake Terminal Operators, Clearance Level 2 and above

Supersedes SBL-TOP-000 Rev. 3.8 -- Destroy previous edition upon receipt

Distribution Sabrelake Internal Network -- Not for external circulation

Authority Terminal Operations Division // Approved: [REDACTED]

!

Warning

This document contains procedures for active Sabrelake dispatch terminals. Incorrect terminal operation during an active breach event may result in containment failure, personnel casualty, or uncontrolled Voidway expansion. Read all sections completely before operating any terminal.

1.1 Purpose

This manual establishes standard procedures for all personnel operating Sabrelake dispatch terminals across active sector installations. It covers normal operations, emergency procedures, communications protocols, and post-incident logging requirements. Compliance with procedures contained herein is mandatory for all authorised operators.

1.2 Scope of Application

Procedures in this manual apply to the following terminal types:

Sector Dispatch Terminal (SDT) -- All variants, fixed installation

Mobile Command Interface (MCI) -- Portable field units, Type-2 and above

Omni Projector Control Node (OPCN) -- Dedicated projection dispatch consoles

Anomaly Monitoring Station (AMS) -- Passive and active monitoring configurations

Voidway Relay Interface (VRI) -- Signal interception and transcription terminals

1.3 Definitions

Term	Definition
`OPERATOR`	Any Sabrelake personnel with Level 2 or higher clearance authorised to operate a dispatch terminal.
`BREACH EVENT`	Any confirmed or suspected unauthorised entry, Voidway instability, or cryptid manifestation within a monitored sector.
`OMNI DISPATCH`	The act of deploying Omni Projector units to a designated sector via terminal command. Requires Level 3 clearance or emergency override.
`TERMINATE`	Emergency power cut to a designated sector. Irreversible without manual restoration. Must precede Omni Dispatch in all standard breach protocols.
`ANOMALY`	Any unclassified or partially classified entity or signal originating from or associated with Voidway activity.

Note: All terminal commands are logged automatically and retained by the Sabrelake incident archive system. Operators are reminded that all actions taken at a terminal constitute an official operational record.

2.1 Terminal Session Initiation

Before beginning any operational session, the operator shall complete the following pre-session checklist in sequence. No steps may be omitted. Checkboxes must be completed before terminal is considered operationally ready.

Verify operator credentials and clearance level against current duty roster REF 2.1.A

Confirm terminal hardware status -- all indicators nominal, no fault lights present REF 2.1.B

Initiate session authentication via agent ID and password. Confirm autofill if applicable. REF 2.1.C

Review sector status overview -- note any pre-existing alerts or flagged sectors REF 2.1.D

Confirm communications array online -- incoming call indicator functional REF 2.1.E

Confirm dispatch log is recording -- entry timestamp matches current operational time REF 2.1.F

2.2 Sector Monitoring

During all operational sessions, the operator shall maintain continuous awareness of the sector status display. Sector indicators are colour-coded as follows:

Indicator	Meaning	Required Action
NOMINAL	Sector operating within all normal parameters. No anomaly activity detected.	Continue monitoring. No action required.
ALERT (blinking)	Breach detected or suspected. Sector requires immediate operator attention.	Proceed to Section 3. Do not delay.
CONTAINED	Breach event concluded. Omni Dispatch complete. Sector stable.	File incident report. Notify senior operator.
OFFLINE	Terminal communication with sector lost. Cause unknown.	Escalate immediately. Do not attempt Terminate or Dispatch.

>

Fig. 2-1 – Sector Status Display, Sample Alert State

!

Warning -- Critical Sequence

TERMINATE must always be executed before OMNI DISPATCH. Dispatching Omni Projectors into a powered sector will result in projector loss and possible amplification of the breach event. There are no exceptions to this sequence.

3.1 Breach Response Sequence

Upon detection of an ALERT indicator, the operator shall proceed through the following sequence without deviation. Actions must be completed in order.

Acknowledge the alert. Note sector number and time of initial detection in the dispatch log.

If an incoming call is received simultaneously, answer immediately. The call may contain critical breach intelligence. Record all information conveyed.

Identify the affected sector on the status display. Confirm ALERT status is active (blinking indicator).

Execute TERMINATE command on the affected sector. Confirm the command registers in the dispatch log. Wait for TERMINATED confirmation before proceeding.

Execute OMNI DISPATCH command. Confirm dispatch registers. Wait for DISPATCHED confirmation and sector indicator transition to CONTAINED.

File incident report upon CONTAINED confirmation. Include: time of initial alert, time of TERMINATE, time of DISPATCH, any communications received, operator ID.

Caution

If an incoming call is received during an active breach, the operator must not ignore the call. Calls during breach events are frequently the primary source of sector intelligence. Failure to answer may result in incomplete breach assessment and incorrect response escalation.

3.2 Communications During Breach

Incoming calls during breach events may originate from encrypted or unknown signal sources. The operator shall:

Answer all incoming calls promptly regardless of signal origin classification.

If the call begins with Morse code, allow transcription to complete before responding.

Note all specific sector references, entity descriptions, and action directives conveyed in the call.

After the call concludes, proceed immediately to Section 3.1 Step 3 using intelligence gathered.

Do not attempt to re-establish contact with the call origin. Log signal classification and proceed.

Note: Calls containing Morse code preamble are classified as encrypted priority transmissions. The Morse sequence will self-identify the transmitting party. Operators should be familiar with standard Morse alphabet for rapid decoding.

4.1 Standard Command Set

Command	Function	Clearance	Reversible
`TERMINATE [SECTOR]`	Executes full power cut to designated sector. All systems offline.	Level 2	No -- manual restore required
`DISPATCH OMNI [SECTOR]`	Deploys Omni Projector units to designated sector. Requires TERMINATE confirmation.	Level 2	Yes -- recall available within 60s
`ANSWER`	Accepts incoming communication on active call queue.	Level 1	N/A
`END CALL`	Terminates active communication session. Auto-logs transcript.	Level 1	N/A
`LOG [TEXT]`	Appends manual entry to active dispatch log.	Level 1	No -- all log entries are permanent
`STATUS [SECTOR]`	Returns current status of specified sector to dispatch log.	Level 1	N/A
`ESCALATE [SECTOR]`	Flags sector for senior operator review. Does not trigger automated response.	Level 1	Yes
`OVERRIDE [AUTH]`	Bypasses clearance requirement for single command. Requires supervisor authorisation code.	Level 4	N/A

Caution -- Irreversible Commands

TERMINATE and LOG commands cannot be undone once confirmed. Operators shall verify sector number and command syntax before executing. Misapplication of TERMINATE to an incorrect sector is an immediately reportable incident.

4.2 Tab Navigation Reference

All standard terminals present two primary navigation tabs. Operators shall be familiar with the function of each:

Tab	Contents	Primary Use
`DISPATCH`	Sector status grid, action controls (TERMINATE, DISPATCH), dispatch log.	All breach response operations. Primary operational view.
`INCOMING`	Active call queue, call history, signal classification display.	Communications monitoring. Check when badge indicator is active.

Note: The INCOMING tab will display a pulsing indicator when an unacknowledged call is present. The operator shall switch to INCOMING and answer promptly. Do not allow calls to go unanswered during an active breach event.

5.1 Known System Limitations

Terminal session does not persist across browser sessions. All logged data is retained server-side but the operator interface will reset on reload.

Incoming calls may be delayed by up to 8 seconds following terminal initialisation due to communications array warm-up period.

DISPATCH command will remain locked until TERMINATE confirmation is received. This is by design and cannot be overridden at Level 2.

Sector indicators will continue to show ALERT state during the TERMINATE execution window (approximately 2 seconds). This is normal and does not indicate command failure.

Call transcripts may be delayed by 0.5 to 3.5 seconds per line depending on signal quality. Operators shall not interpret transcript delay as call completion.

5.2 Open Anomaly Reports

Report ID	Description	Status
SBL-INT-07	Unregistered presence detected inside internal archive. Left encoded data. Origin unidentified.	UNRESOLVED
SBL-INT-08	Three-lock data fragment left by anomaly. UNSC-pattern content. Personnel file match: Alpha-Nine.	UNRESOLVED
SBL-INT-09	UNSC-pattern data portal observed in Sub-Level 3, Complex-7. Portal collapsed. Anomaly entry unconfirmed.	UNRESOLVED

!

Warning -- Unresolved Anomalies

Three open anomaly reports remain unresolved as of this revision. The entity responsible for SBL-INT-07 through SBL-INT-09 has not been identified. Operators are advised to report any unusual terminal behaviour, unsolicited data, or unexplained signal activity immediately to the Terminal Operations Division.