Operator Surface

Make PIN operations visible, controlled, and recoverable.

This is now a real operator surface, not a placeholder brochure. Devices, vault evidence, sessions, release state, and console exports all resolve through the isolated pin.onenos.ai API path.

Current devices

Heartbeat, bridge status, release state, and storage posture.

Full fleet

Latest sessions

Recovery runs, diagnostics, and console exports.

Full ledger

Devices

List and inspect registered Pins, see bridge health, and trigger relaunch, recovery, or reboot requests.

Go to devices

Vault

Keep photos, videos, audio, logs, and investigation exports inside the isolated PIN evidence store.

Go to vault

Sessions

Track device sessions, diagnostics, recovery runs, and saved console investigations in one operator ledger.

Go to sessions

Install

Use the stable release card, mirrored asset placeholders, and manual install fallback without faking device control.

Go to install

Relaunch

Restart the runtime bridge quickly after reboot or battery drain without jumping straight into full recovery.

Go to relaunch

Recovery

Keep stable and rollback targets visible while recovery sessions and operator notes stay traceable.

Go to recovery

Releases

Manifest placeholders, notes, and checksum paths all resolve under the isolated PIN mirror structure.

Go to releases

Console

Capture investigation notes, paste command output, export JSON locally, and save sessions into the server ledger.

Go to console
Isolation Rule

All code, storage, manifests, and UI work for this phase stay inside /var/www/pin.onenos.ai only.

Takeover Model

ONEN takes over by replacing the backend implementation behind /api/pin/* first. OpenPin remains the bridge until command execution is ready.