MINUTE OS documentation

Create or restore

Open MINUTE OS on a trusted device. Choose a unique passphrase of at least twelve characters and confirm it. This creates a real encrypted local database, not a cloud account. For an existing encrypted export, select the backup on a browser with no saved workspace and enter the backup phrase.

The database remains scoped to this website and browser profile. It is not account-synchronized, and browser data deletion can remove it. Export an encrypted backup regularly.

First service-business workflow

• Create a job in Workspace: title, customer/reference, assignee label, due date, status, priority and notes. Save explicitly.
• Register an equipment item in Device Center. Status is manual, not live telemetry.
• Add a plain-text procedure in Vault; optionally import a text file up to 20 KB. Search titles and contents locally.
• Create a workflow for overdue manual jobs or equipment marked attention. Preview matches, then explicitly approve local review-task creation.
• Inspect the run history and Sentinel audit, then mark jobs active/done by editing them. Repeating a flow/source/day does not duplicate the task.
• Use Intelligence for a calculated briefing or literal document search. Optional All•Tier is a separate tool and receives no automatic workspace data.
• Export an encrypted backup in Settings, then lock and unlock the workspace to rehearse recovery.

Save, lock and recover

Each record save validates, encrypts and writes the whole bounded workspace atomically. A newer revision from another tab causes a conflict rather than lost updates. Your editor stays open if saving fails.

Switching tabs or ten minutes of inactivity hides the screen while retaining open edits/key in memory. Resume is not an identity check. Finish or cancel an editor before fully locking. A full lock clears page references to plaintext and the key; encrypted data remains.

Only one device-owner workspace is supported. Assignee labels are not users or permissions. No cloud authentication, organization role enforcement, remote notifications, scanner or device controller is implemented.

Limits and cost

No fees, seat limits priced for upgrades, payment forms, trial expiry or paid AI provider. Hard storage limits protect the browser and are not a pricing tier.

Limits: 300 jobs, 150 equipment items, 50 documents of up to 20,000 characters, 20 flows, 1,000 runs and 500 audit actions. Do not use this pilot for regulated records or safety-critical decisions. It has not been independently security-certified.

Appendix F. Deployment, scale and failure recovery

Current deployment uses the existing XRP Legacy build and hosting target. No new database, AI binding, broker, object-storage resource or paid font service is provisioned. Keep module code/styles scoped and load the operations workspace only on its route. The logo is a static supplied asset.

Self-hosting is a future option: containerized application, PostgreSQL, explicit local object storage, optional local inference, and a broker only for an authorized telemetry need. A local machine can still incur power, administration and backup costs. Do not label it an enterprise production system without operational validation.

Scale by measurements: bounded payload/record limits now; future pagination, organization indexes, controlled worker concurrency, backpressure, dead-letter queues and telemetry retention. No requests-per-second or latency result is invented. Establish p50/p95 benchmarks on declared hardware and real workloads before publishing targets.

Failure recovery: no paid fallback; failed encryption/write keeps visible edits and prior saved snapshot. Wrong passphrase leaves stored ciphertext untouched. Unsupported versions stop import. A second writer receives a conflict rather than silently replacing another tab. Restore uses a fresh browser context and the backup phrase; a lost phrase cannot be reset.