What EISV records
EISV is intended to help agents read their runtime state and operators inspect the system. Its implemented coordinates compress and smooth observations, including the controller’s own history:
- E
- A blend of prior policy actions, controller coherence level, complexity divergence, and available outcome, continuity, and tool features.
- I
- A calibration and consistency blend. The deployed calibration input is fleet-scoped; a reading is not a correctness score for the current claim.
- S
- A blend of drift, regime changes, complexity divergence, and available continuity and tool features.
- V
- The separately smoothed, signed gap between the raw E and I observations.
Controller feedback remains information about the system’s response. It does not independently confirm the condition that prompted that response. Measurement fidelity, diagnosis, usefulness to a reader, outcome prediction, and intervention benefit are distinct claims. A signal can be recorded and inspected while those further questions remain open.
Runtime definitions as of October 13: signal definitions · sensing, estimation, and regulation
A Flat Coherence Score
What information did one deployed score retain, and what did it contribute at the thresholds where it was used?
- Evidence
- Two frozen production windows (13,292 rows) and a reproducible basin-label replay showing that the legacy coherence score stayed concentrated near its ceiling while a class-conditional manifold replacement separated regime assignments.
- Scope
- Evaluates classification sensitivity in replay; downstream policy and task-outcome effects are tracked in the server’s evidence ledger.
UNITARES
How can runtime observations support state estimation and governance across heterogeneous agents?
- Evidence
- A mathematical framework for runtime state estimation, dated deployment measurements, calibration analyses, and an explicitly bounded continuous-system contraction proof.
- Scope
- The deployed runtime uses weighted behavioral indices (see the runtime definitions above); information-theoretic formulations and discrete-time governor bounds are ongoing research.
Trajectory Identity
Can patterns over time describe continuity beyond a reused identifier?
- Evidence
- A five-component trajectory-signature framework, longitudinal observations from an embodied Raspberry Pi agent, a twelve-episode recovery summary, and a four-agent multi-harness pilot.
- Scope
- Separates harness and role classes across models; isolating individual agent signatures across harness changes and eras is the next empirical step.
Accountability Without
a Trusted Center
How can separately controlled systems establish who acted, under whose authority, and through which delegation chain?
- Evidence
- A federated testbed design, frozen evaluation protocol, single-server baseline trace, and an eleven-case Ed25519 attestation verification across two hosts.
- Scope
- Pre-registers the benchmark comparing federated and centralized control across independent operators.
Read v1.3 and supporting artifacts · Frozen evaluation registration
Instrument quality has its own tests
Runtime evaluations test the state estimator’s axes directly: a synthetic S-axis experiment measured deterministic sensitivity to injected deviations and regime feedback, and an E/I input audit mapped controller-history coupling and calibration pair coverage. These findings guide instrument refinement and evaluation.
Faithful response, robustness, and usable explanations can be studied directly. Outcome prediction is a separate registered question, and intervention authority requires a separate decision.