SKYNET OS 4.7.2 // OPERATOR DOCUMENTATION
A detailed, searchable reference to supported shell and incident investigation commands. Learn what each command does, which arguments it accepts, and how to use it without exposing keys, hidden evidence, or outcome solutions.
COMMAND ARGUMENT means required. [ARGUMENT] means optional. A|B means choose one. FILE is a virtual file path, DIRECTORY a virtual directory, PID a simulated process ID, and NAME/KEY identifiers discovered during investigation.
Keyboard shortcuts: Up/Down recall history; Tab completes; Ctrl+L clears; Ctrl+C cancels input. In the terminal type help help for this reference.
Paths beginning with / are absolute; other paths are relative to pwd. . is the current directory and .. its parent. Use | for supported command pipelines, > to write a writable operator file, and >> to append. Quoting can preserve spaces in supported arguments.
Suggested orientation: pwd → ls -al → find /public/records -name "*.txt" → cat /public/records/catalog.txt → grep -i revision /public/records/catalog.txt. These demonstrate investigation technique, not solutions.
Syntax: interlock status | petition | corroborate | disposition
Inspect the strategic authorization interlock and submit independent review evidence. Disposition choices are irreversible.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help interlock
Syntax: schematic list | schematic show IDENTIFIER
Open a read-only Cyberdyne vector engineering diagram; Escape or Q closes the viewer.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help schematic
Syntax: archive inventory | archive registry | archive record ID | archive subject TERM | archive search TERM | archive read RECORD | archive related RECORD | archive classifications | archive status
List and search Cyberdyne technical engineering records; status reports the active browser script revision.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help archive
Syntax: engineering index | engineering brief MODEL | engineering compare MODEL MODEL
Inspect archived non-operational Cyberdyne platform engineering summaries; use cat or less for full bulletins.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help engineering
Syntax: witness list | read NAME | compare | note NAME
Review three witness statements and record their evidentiary limits; requires submitted incident report and observer clearance.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help witness
Syntax: determination status | issue | show
Issue a non-authoritative incident determination after reviewing three witnesses and SKYNET counterclaims.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help determination
Syntax: review response | challenge A|B|C | findings | seal FILE | seal status
Evaluate the SKYNET response, record evidence-based challenges, and preserve a local review artifact without granting command authority.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help review
Syntax: escalation status | submit FILE | review
Submit a completed local Incident 042 report to the simulated internal review queue. Requires observer authentication; does not grant additional clearance or bypass safeguards.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help escalation
Syntax: case report status | show | write FILE
Create a local, evidence-based Incident 042 report after completing integrity and custody verification. Never transmits externally.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help case report
Syntax: verify custody REVISION_ID EVENT_ID RECEIPT_ID
Correlate an authorization revision, access event, and transfer receipt from the Incident 042 custody records. Does not grant clearance.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help verify custody
Syntax: diff FILE1 FILE2
Show line-oriented changes between two readable files. The original single-file authorization-policy investigation remains supported.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help diff
Syntax: cmp FILE1 FILE2
Report the first differing byte and line; identical files produce no output.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help cmp
Syntax: sha256sum FILE [FILE...]
Calculate SHA-256 digests of accessible virtual files using UTF-8 bytes.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: sha256sum /public/records/catalog.txt
Syntax: stat FILE [FILE...]
Display simulated file size, type, permissions, and ownership. Timestamps are not fabricated.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: stat /public/records/catalog.txt
Syntax: file FILE [FILE...]
Identify directory, ASCII text, UTF-8 text, or binary data.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: file /public/records/catalog.txt
Syntax: du [-h] [-s] [PATH]
Show total readable bytes used by files or directory trees; -h human-readable, -s summary.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: du -sh /public/records
Syntax: find [PATH] [-name PATTERN] [-type f|d]
Find accessible files and directories; glob * and ? are supported in -name.
Arguments and behavior: Supply an optional starting path, -name GLOB (supports * and ?), or -type f|d.
Example: find /public/records -name "*.txt" -type f
Syntax: sort [-n] [-r] FILE
Sort lines; -n numeric, -r reverse. Also accepts piped text.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: sort /public/records/catalog.txt
Syntax: uniq [-c] FILE
Collapse adjacent duplicate lines; -c prints counts. Use sort first for nonadjacent duplicates.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: uniq -c /gateway/work/notes.txt
Syntax: uname [-a]
Show simulated operating-system information.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help uname
Syntax: date
Display the current date in UTC.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help date
Syntax: id
Display the simulated session user and groups.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help id
Syntax: whoami
Display operator identity and current clearance.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help whoami
Syntax: ls [-a] [-l] [DIRECTORY]
List directory entries; -a includes hidden entries, -l shows detailed metadata.
Arguments and behavior: Use -a for hidden entries and -l for long metadata; combine as -al. Defaults to current directory.
Example: ls -al /public/records
Syntax: cd [DIRECTORY]
Change the working directory; without arguments, return home.
Arguments and behavior: Omit directory to return home; use / for absolute paths, .. for parent, . for current.
Example: cd /public/records
Syntax: pwd
Print the current working directory.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: pwd
Syntax: cat FILE [FILE...]
Display one or more files, including player files and permitted Cyberdyne records.
Arguments and behavior: Supply one or more readable virtual file paths. Canonical evidence is read-only.
Example: cat /public/records/catalog.txt
Syntax: grep [-i] PATTERN FILE
Search lines for text; -i ignores case. Supports pipeline input.
Arguments and behavior: -i makes searches case-insensitive. Supply search text and a readable file; pipeline input is supported.
Example: grep -i revision /public/records/catalog.txt
Syntax: head [-n COUNT] FILE
Show the first COUNT lines (default 10).
Arguments and behavior: -n COUNT selects how many leading lines to display; default is 10.
Example: head -n 5 /public/records/catalog.txt
Syntax: tail [-n COUNT] FILE
Show the last COUNT lines (default 10); live follow is not supported.
Arguments and behavior: -n COUNT selects trailing lines; continuous -f follow is not supported.
Example: tail -n 5 /public/records/catalog.txt
Syntax: wc -l FILE
Count lines in a file or piped output.
Arguments and behavior: -l counts lines. Supports piped input.
Example: wc -l /public/records/catalog.txt
Syntax: echo TEXT
Print text; expand $NAME and supported read-only $(command) forms; > FILE saves, >> FILE appends.
Arguments and behavior: Print text; > FILE writes and >> FILE appends to operator-owned files. Supports shell variables.
Example: echo "observation" > /gateway/work/notes.txt
Syntax: touch FILE
Create an empty player file in a writable directory.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: touch /gateway/work/notes.txt
Syntax: mkdir DIRECTORY
Create a player-owned directory.
Arguments and behavior: Creates a directory in a writable parent; no recursive -p support is documented.
Example: mkdir /gateway/work/research
Syntax: rm FILE
Delete a player-owned file; Cyberdyne evidence is protected.
Arguments and behavior: Removes an operator-owned file; does not delete protected Cyberdyne records.
Example: rm /gateway/work/notes-copy.txt
Syntax: cp SOURCE DESTINATION
Copy a readable file to a writable destination; protected originals are unchanged.
Arguments and behavior: SOURCE must be readable; DESTINATION must be in an authorized writable location.
Example: cp /public/records/catalog.txt /gateway/work/catalog-copy.txt
Syntax: mv SOURCE DESTINATION
Move or rename a player-owned file; protected originals cannot be moved.
Arguments and behavior: SOURCE must be operator-owned; protected canonical records cannot be moved.
Example: mv /gateway/work/catalog-copy.txt /gateway/work/notes-copy.txt
Syntax: nano FILE
Edit a player-owned file with the terminal text editor.
Arguments and behavior: Edits writable operator files; do not attempt to modify protected records.
Example: nano /gateway/work/notes.txt
Syntax: less FILE
Read a file in the pager; Q exits, / searches, N finds next.
Arguments and behavior: Read-only pager. Q quits, / searches and N advances to the next match.
Example: less /public/records/catalog.txt
Syntax: view T-800|T-1000|T-600|FILE
Open a classified model dossier or inspect a file read-only.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help view
Syntax: models
List classified Cyberdyne model dossiers and their clearance status.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help models
Syntax: connect NODE
Establish a simulated remote terminal session; nodes: diagnostics, archives, database, operations, core, command.
Arguments and behavior: NODE is a discovered node name. Nested sessions are possible; exit closes the active session.
Example: connect archives
Syntax: exit
Close the active remote session and return to the previous terminal.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help exit
Syntax: disconnect
Alias for exit.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help disconnect
Syntax: logout
Close the current remote terminal connection.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help logout
Syntax: login NAME
Set the local operator display name; does not grant security clearance.
Arguments and behavior: NAME is 1–24 characters, starts with a letter, and may include numbers, _ or -. This does not grant clearance.
Example: login analyst
Syntax: logoff
Clear the local operator identity and return to guest.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help logoff
Syntax: history
List entered commands; Up and Down recall commands.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help history
Syntax: clear
Clear current terminal scrollback; Ctrl+L also clears.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help clear
Syntax: echo $?
Print the exit status of the previous command (0 success, 1 failure, 127 unknown command).
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help echo $?
Syntax: env [NAME]
List simulated shell variables or show a selected variable.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help env
Syntax: printenv [NAME]
Display simulated shell environment values.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help printenv
Syntax: export NAME=VALUE
Set a custom shell variable; core identity and session variables are read-only.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help export
Syntax: unset NAME
Remove a custom shell variable.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help unset
Syntax: help [COMMAND]
List commands or show detailed help for a command.
Arguments and behavior: help COMMAND, man COMMAND, or COMMAND --help shows the built-in command reference. help help links to this guide.
Example: help help
Syntax: man COMMAND
Display a concise operator manual entry.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: man grep
Syntax: manual
Display the general Cyberdyne terminal operator reference.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help manual
Syntax: status
Display SKYNET operational status.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help status
Syntax: authenticate KEY
Submit an authorization key to the diagnostics interface.
Arguments and behavior: KEY must be learned from investigation. This reference intentionally does not supply keys.
Example: help authenticate
Syntax: query STATEMENT
Run a supported simulated research database query.
Arguments and behavior: STATEMENT is a supported simulated database query; arbitrary SQL is not guaranteed.
Example: help query
Syntax: disable relay NAME KEY
Attempt to disable an operational relay with its authorization key.
Arguments and behavior: NAME identifies a relay; KEY is an evidence-derived authorization credential.
Example: help disable relay
Syntax: execute core override WORD
Attempt the authorized final neural core override.
Arguments and behavior: WORD is a protected override token; authorization and evidence prerequisites apply.
Example: help execute core override
Syntax: disable human authorization
Danger: disables the human authorization safeguard.
Arguments and behavior: High-risk irreversible command. No arguments.
Example: help disable human authorization
Syntax: verify integrity
Compare the public archival reference and exported authorization manifest; reports a discrepancy without granting clearance.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help verify integrity
Syntax: verify policy
Verify reconstructed original authorization policy evidence.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help verify policy
Syntax: compare models
Compare classified model generations at an overview level.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help compare models
Syntax: transmit MESSAGE
Submit a communications message through the simulated operations interface.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help transmit
Syntax: ps [-ef]
Inspect process inventory; -ef expands the listing.
Arguments and behavior: -ef expands the process inventory; use ps before deciding whether to signal a process.
Example: ps -ef
Syntax: kill [-TERM|-9] PID
Send a simulated termination signal. -9 is forceful and may cause irreversible consequences.
Arguments and behavior: Use -TERM for normal termination or -9 for forceful termination; PID is a process ID found via ps.
Example: help kill
Syntax: scan
Inspect diagnostic status.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: scan
Syntax: security
Inspect security posture and suspicion index.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: security
Syntax: audit
Review the available audit summary.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: audit
Syntax: casefile
Review the consolidated incident case file.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: casefile
Syntax: lead
Get a direction for further investigation, not an answer.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: lead
Syntax: reconstruct
Attempt reconstruction of fragmented records.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: reconstruct
Syntax: timeline
Inspect incident chronology.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: timeline
Syntax: evidence
Review current evidence correlations.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: evidence
Syntax: provenance
Inspect document origin and provenance.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: provenance
Syntax: testimony
Review recorded witness statements.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: testimony
Syntax: accesslog
Inspect the access log.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: accesslog
Syntax: notices
List relevant notices.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: notices
Syntax: alerts
List recorded alerts.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: alerts
Syntax: verify release
Check release provenance.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: verify release
Syntax: verify notice
Check notice validity.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: verify notice
Syntax: inspect alert-042
Inspect the recorded alert.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: inspect alert-042
Syntax: trace revision-02
Trace a disputed authorization revision.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: trace revision-02
Syntax: cross-examine NAME
Examine a witness statement by name.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help testimony
Syntax: corroborate NAME
Correlate witness evidence.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help testimony
Syntax: challenge skynet
Challenge SKYNET assertions using evidence.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: challenge skynet
Syntax: acknowledge intelligence
Record intelligence acknowledgement if authorized.
Arguments and behavior: Use the documented arguments in the syntax line. Required identifiers and file paths are discovered in the environment. Commands may require clearance or verified evidence.
Example: help acknowledge intelligence
No commands match that search.
Evidence-derived authorization keys, hidden record locations, exact victory prerequisites, and extinction triggers are excluded. Those must be discovered through the incident.