INTELLISYS / OPERATIONS GUIDE

Data & continuity

Where employee files live, what survives a restart and what a complete backup needs.

DATA / 01

Follow the work state
and the request content.

The environment lives on the team server. Files saved to the Mac and content sent to model services have different destinations.

Where the environment lives. Where requests go.. The team server stores primary work state. The Mac can keep saved files. Model request content reaches the selected service; CroHub’s data flows are still to be defined. — The team server stores primary work state. The Mac can keep saved files. Model request content reaches the selected service; CroHub’s data flows are still to be defined.

DATA / 02

Separate persistent files
from the runtime layer.

Each employee environment mounts seven private directories. Replacing a container is different from permanently deleting an environment.

Replace the runtime. Keep the work files.. Routine container maintenance preserves the private directories under its procedure. Permanent environment deletion removes them. — Routine container maintenance preserves the private directories under its procedure. Permanent environment deletion removes them.

DATA / 03

Identity, host access and
model authorization are separate.

CroGate checks sessions, roles, request origins and environment ownership. Those controls coexist with host administration and upstream credentials.

Platform access

Administrator and employee roles, session revocation, CSRF and Origin checks control requests. Device reports are informational.

Host responsibility

Server operators manage host, container platform and backup access. Private directories and shared credentials require appropriate controls.

Upstream authorization

Delivered keys are readable in their assigned environments. Vendor login state stays in private directories, and account disablement does not revoke those credentials automatically.

DATA / 04

Back up all the state
needed to recover the system.

Gateway state, employee files, skill libraries, image versions and auxiliary services all belong in the recovery plan.

Three kinds of state. One coordinated recovery plan.. Include separate network identity volumes, external inference data and matching images. Maintenance snapshots support rollback; independent backups support recovery. — Include separate network identity volumes, external inference data and matching images. Maintenance snapshots support rollback; independent backups support recovery.

Include separate stores

Cover the Tailscale identity volume and inference data located outside the gateway state directory.

Coordinate writers

Account for active tasks, containers and services when taking a consistent backup.

Verify recovery

Upgrade snapshots support rollback. Independent backups and a recovery procedure address broader failures.

KEEP EXPLORING

Data & continuity

Follow the work stateand the request content.

Where the environment lives. Where requests go.

Separate persistent filesfrom the runtime layer.

Replace the runtime. Keep the work files.

Identity, host access andmodel authorization are separate.