Intelligence

The path

• Context

  Context is what the system already knows: architecture, procedures, prior decisions, and the current public readings. It is read before work is chosen.

• Agent

  An agent uses that context to determine a bounded piece of work. The bound is part of the model. An agent is not a free actor over the whole system.

• Decision

  A decision is a proposed next step. It is not yet an action, and it is not yet evidence that anything changed.

• Control

  Control is the point where a decision becomes an allowed action. The control that fits the operation has to agree. Unrestricted execution is not the model.

• Execution

  Execution is the work itself, inside the runtime. A command being issued is not the same fact as the work having finished.

• Evidence

  Evidence is what can be checked later: what was asked, what ran, and what the system reported back. A successful request is not automatically that record.

• Persisted state

  The accepted result belongs in the data layer. The meaning of the work belongs in the knowledge layer. A sentence that something ran is neither of those records.

Agents

Reports publish the latest field and operations readings. They are not a live headcount, and they are not proof that a system is active right now.

No public signal on this site says how many agents are running. The homepage says the same thing. Reports

Persistent context

Durable context is how the next person or agent can see what the system already learned. Architecture, procedures, and prior decisions stay in the knowledge layer. Without that layer, each session starts blank.

Current readings are not a substitute for that record. A power number explains the plant at one moment. It does not explain why the system is built the way it is. Knowledge

Controlled execution

Actions pass through the boundary that fits the operation. People remain able to understand and stop important operations. An agent can prepare work inside a bound. The control that performs it stays visible.

The public site is not that control. Account entry on this site is not an operator console. Security

Verification

A proposed action is not evidence. A command is not evidence. A commit is not proof of deployment. A successful request is not necessarily proof of system state.

Evidence is what the system can actually report and what can be checked later. On the public site, that standard shows up as a reading with a time, or as the words no public signal. Status

Persisted state

The result of accepted work belongs in the data layer, where a later check can read it. Logs, field readings, and reports are different kinds of that record. They are not interchangeable.

This page does not claim the database is healthy. There is no public runtime signal for that. Data