Local and Offline Operating Guide

Evidence note[!IMPORTANT] Check this guide before moving OGO™ into a disconnected, restricted, customer, lab, or field environment. Local operation does not remove the operator's responsibility for authorization, evidence handling, and site procedure.

Oprynta™ Guide Ops is designed so its core simulation does not require a live infrastructure connection.

• Master domain launcher
• Problem catalog
• Free-text intake
• Deterministic local classifier
• JSON playbook loader
• Evidence gates
• Command guidance
• Branch selection
• Safety gates
• Owner route
• Resolution architecture map
• Resolution and escalation packet
• Browser-local session history

• Authentication
• Database
• Management-controller connection
• Fleet console connection
• SSH
• Remote execution agent
• Production monitoring integration
• Internet access after installation when AI is disabled

• OpenAI classification and evidence summary require internet access and an API key.
• Firestore persistence requires Google Cloud configuration and network access.

The deterministic simulator remains available if either optional service is unavailable.

Before using the application in a disconnected environment:

1. 01Install npm dependencies while online.
2. 02Run npm run build.
3. 03Preserve the project directory and local playbooks on the approved laptop.
4. 04Set OPENAI_ENABLED=false.
5. 05Set DATA_BACKEND=local.
6. 06Do not paste restricted or customer-confidential information into the simulator unless the local operating policy permits it.

Before disconnecting, confirm:

• The production build completes successfully.
• The required local playbooks are present and validated.
• Optional cloud persistence is disabled or intentionally configured.
• No API key is required by the selected operating mode.
• The approved laptop has enough storage for the project, dependencies, and local records.
• The team knows where generated dossiers and browser-local session records will be retained.
• A named operator remains responsible for every command, change, and evidence decision.

The application displays commands but does not execute them. The operator remains responsible for authorization, site procedure, command review, maintenance controls, and evidence handling.

Evidence note[!WARNING] Local execution is not automatic authorization. Do not run a displayed command merely because it appears in an approved guide. Confirm the current fault boundary, access level, safety classification, site procedure, and accountable owner first.

Teams that need a private local scenario can add one without publishing it. Continue to the Playbook Authoring Guide for the required schema, routing contract, branch rules, safety fields, and validation workflow.