CAUM Documentation

Welcome to the technical observation infrastructure of CAUM.

This repository acts as a Passive Oracle for structural diagnostics. Its mission is to issue **Proof-of-Progress (PoP)** attestations based strictly on the physics of agentic trajectories. CAUM operates as a neutral scientific instrument for the governance of autonomous systems.

The Core Axiom: "CAUM no decide; CAUM registra." (CAUM does not decide; CAUM registers).

Proof-of-Progress (PoP) Standard

CAUM is explicitly designed to be deterministic. Given the exact same input trajectory, the output attestation is identical bit-by-bit.

  • Deterministic Engine: Zero stochastic components. Zero internal learning heuristics altering observation during a session.
  • Lexicographical Serialization: All evidence objects and manifests are strictly ordered for cryptographic hashing.
  • Session Fingerprinting: Every audit generates an immutable SHA256 physical constraint signature to guarantee diagnostic integrity.

Unitary Structural Density (UDS)

CAUM evaluates structural characteristics within a trajectory. It does NOT analyze semantic meaning, goals, or LLM prompts.

Diffusion Coefficient (α)

Analyzed via Mean Squared Displacement. Evaluates whether the agent is diffusing outwards (Expansion) or trapped locally (Confinement).

Topological Persistence

Measures the loss of Degrees of Freedom. Triggers when persistent structural loops dominate the execution window.

Neutral Taxonomy (Regimes)

Based on the calculated UDS and Diffusion bounds, the Advisory Layer translates the physical data into one of the following Informational Signals:

Regime Structural Meaning
EXPANSION Genuine structural growth and structural progress. Vector states are novel.
STABLE Productive and consistent movement within defined mathematical bounds.
CONFINEMENT Circularity or entrapment. Critical loss of Degrees of Freedom detected.
STUPOR Minimal kinetic energy; trajectory is indistinguishable from system noise.
INSUFFICIENT Signal quality or trace window size is below the diagnostic threshold.

Payload Constraints

For offline observation reports, our portal accepts trace logs. The minimum requirement is a stable discretized representation of state per step.

  • .jsonl (Recommended): One step object per line.
  • .json: A strict JSON array of state objects.
  • .zip: Batch of multiple trajectory files.
  • .csv: Columns representing time and concatenated state elements.

Self-serve File Size Limitations: Standard payloads are capped at 50MB and 10,000,000 steps. Larger footprint datasets require Enterprise Staging.

Advisory vs. Action

Any client integrating CAUM must respect the separation of concerns to ensure diagnostic validity:

  1. The Observation Layer: Passive Observation (Thermometer). Emits raw physics.
  2. The Advisory Layer: Translates physics into Regime Health Signals (e.g. CONFINEMENT).
  3. The External Client Layer: This is YOUR system. You read the CAUM PoP and execute policies (halting the agent, raising alerts, modifying prompts).