What Makes an Agent System an Operating System

The operating-system analogy belongs to the composed environment, not to Converge alone.

The kernel contract

Converge implements the low-level contract close to the mathematics: kernel, shared context, facts, authority boundaries, promotions, and bounded convergence. It is not the complete runtime or operator environment.

The kernel controls what may enter the governed record. That record is a shared model with provenance, not reality itself. A promoted claim can later be rejected or superseded without erasing what the system believed when a decision was made.

What the surrounding components supply

Formation organizes reasoning through formations, including Competition and Huddle. Axioms supports human-readable Truth specs/Gherkin and checkable artifacts. Helm gives people a surface for describing desired outcomes, inspecting evidence, and exercising authority.

Runtime-Runway supplies runtime capabilities such as messaging and storage. The composition supports the OS analogy: intent, resources, state, lifecycle, and authority are managed together. This analogy does not assert that Converge's kernel owns every service or that every integration is already implemented.

One problem, several attempts

A Business Truth describes what should be true without prescribing a workflow. Its evidence requirements state what must be demonstrated before a result can be relied upon.

Several attempts can address it in parallel, with different formations, resources, or budgets. An attempt may reach a fixed point that is unacceptable, or stop before reaching a fixed point. Zero, one, or several results may meet the requirements.

Selection can follow a declared rule, another review, or a human decision. Selecting a candidate does not itself bind the organization. A commitment requires explicit authority and references a specific version of the Business Truth.

Bounded execution and honest evidence

A fixed point is stability under the loop's rules, not proof of business success. Budget exhaustion, waiting for authority, and invariant violations are distinct stopping conditions. None should be reported as a successful convergence.

Likewise, finding no solution is not proof that none exists. Keep heuristic, feasible, proved-optimal, unknown, and error outcomes distinguishable. An authorized exception may permit action with uncertainty; it cannot turn that uncertainty into knowledge.

Replay is not fresh reasoning

A deterministic promotion rule does not make every run deterministic. Exact reproducibility depends on complete inputs, versions, transformations, execution conditions, and the mathematical assumptions of the component involved.

Replaying recorded external responses differs from making fresh LLM calls. Different admissible plans for the same Business Truth are allowed. Auditability means being able to explain the particular evidence, selection, and authorization behind an undertaking.

Learn without rewriting the record

The adaptive cycle is Coordinate → Commit → Update Priors. Outcomes can improve the shared model for later attempts. They cannot silently alter promises on which others have already relied.

Keep unsuccessful attempts, rejected proposals, and dissent. Current views may filter what is eligible for further work while the history records why a once-promising approach stopped looking promising.

This is the operating-system model we mean: a composition that makes intent, evidence, authority, and execution inspectable, with Converge supplying the kernel contract.