KogniOS is an execution layer for agents, with a human-defined outcome at the top and durable, verifiable state underneath. A Manager may replace workers, recover after restarts, or replan around failure without losing the mission contract or pretending unfinished work is done.
Vision contract · criteria · authority · plan · leases · events · verification history
the mission survives browser, model, worker, and process replacementIsolated checkout · shell · files · browser · context · checkpoint · handoff
workers receive a task and authority—not the whole accountThe Manager reads the project and asks focused questions until the outcome, constraints, criteria, and consequential ambiguity are explicit.
The human reviews one revisioned contract, including authority grants, budget, deadline, assumptions, non-goals, evidence expectations, and stop conditions.
Every task maps back to a mission criterion. Worker leases and capabilities bind an account, mission, task, repository, base revision, audience, and expiry.
Server-owned checks evaluate the exact candidate. Failed or partial evidence causes bounded repair or replanning; worker narration cannot publish a result.
The mission finishes only when required criteria pass. It waits when capacity, human judgment, new authority, budget, deadline, or an external dependency makes progress impossible.
The Manager assigns criterion-linked work, observes leases and events, handles clarification and approvals, cancels exact runs, and replaces failed workers without merging their private contexts.
Each worker gets a bounded checkout and audience-specific capability. Checkpoints, change sets, claims, events, and handoffs are explicit; collaborator text is context, never authority.
InvariantA worker cannot turn its own report into verified state. Publication requires exact repository evidence and server-owned checks against the current mission revision.
KogniOS creates a proof-bound device identity through a TUI QR or manual code. The account service returns a signed, expiring, monotonic manifest containing only authorized projects, policies, cursors, and exact commits.
Objects land in staging, pass digest, commit, path, signature, expiry, and rollback checks, then publish atomically into the account namespace. Interrupted or conflicting sync never becomes ready state.
Offline ruleA device may use only an unexpired signed manifest and a clean exact commit. Revoked credentials do not silently fall back to cached authority.
Workspace reads, writes, commands, network access, publication, deployment, spend, messaging, account changes, and destructive operations are distinct grants with human gates where required.
Bounded Git processes, quarantine, object and tree policy, exact compare-and-set refs, and rollback protect shared verified state from a compromised or stale worker.
Managed provider keys stay in the gateway. Worker bootstraps are single-use; workload and collaboration capabilities bind the exact worker, mission, task, audience, and expiry.
Clarifications resume the same durable run. A human can pause execution, amend the vision, cancel exact work, take over a browser, or revoke a device without erasing mission history.
Durable missions, native repositories, collaboration, signed sync, recovery, and internal safety gates are implemented and locally evidenced. Real elastic-provider operations, managed AI and billing credentials, signed image publication, hardware qualification, production key ceremonies, and independent security review are not presented as complete.
The agent may be temporary. The mission, authority, evidence, and exact result are not.
