โ† Back to Signals
Theoretical Framework
Experimental ยท Research

Meaningful Oversight Has a Throughput Boundary

Decision Wave Compression and Formal Accountability Collapse in High-Density Decision Systems
Technical Note v0.1 ยท May 2026, revised 28 July 2026 ยท Emanuel Celano, Informatica in Azienda ยท EVIDE Research Layer
This document introduces Decision Wave Compression (DWC) and Formal Accountability Collapse (FAC) as inferential constructs for observing governance stability in high-throughput AI decision systems. Neither construct accuses. Both describe conditions. The framework is observational, not prescriptive.
How to read this document
Implemented behavior Describes what the system does today. Verifiable against the API response and the stored evidentiary profile.
Research DWC Describes the full observational model this note proposes. It is a research program, not a description of current output.
Future roadmap Describes intended development. Nothing in this category has been built.
Every block on this page carries exactly one of these labels. They are never combined. Where the implemented layer and the research model diverge, both are stated separately rather than reconciled into a single description.
Section 1
1. The Problem: Declared vs Operational Oversight
Research DWC

Current AI governance frameworks distinguish between systems with and without human oversight. A system either has a human in the loop or it does not. This binary has produced a significant blind spot.

The blind spot is this: oversight can be formally present while being operationally absent. A human authority may exist, sign closures, and remain formally attributed to every decision - while the volume, velocity, and density of those decisions has long since exceeded any realistic capacity for meaningful review.

This condition does not manifest as error. It does not manifest as misconduct. It manifests as a gradual semantic collapse of the oversight function - invisible in any individual decision record, visible only when the system is observed as a temporal and volumetric whole.

Declared oversight records that a human exists.
Operational oversight requires that the human can actually govern.
The gap between the two is what this framework is designed to observe.

Most audit systems check individual decisions for correctness, attribution, and formal compliance. None of them systematically measure whether the organizational and cognitive conditions for meaningful oversight still exist at the moment those decisions were closed.

Section 2
2. Decision Wave Compression (DWC)
Research DWC

Decision Wave Compression is an inferential construct that measures the systemic pressure exerted on the capacity for meaningful oversight by the volume, velocity, and density of decision closures crossing a governance boundary within a defined time window.

It does not measure the quality of any individual decision. It measures the compression of the space within which accountability can stabilize.

Implemented behavior
The current decision_wave_compression dimension represents the first implemented server-side observational layer of the broader DWC research program described in this document. The current implementation exposes a narrower per-closure observational signal. Future versions may extend this into the population-scale observational model described below while preserving backward compatibility. The exact shape and derivation of what ships today are documented in Section 9.1.
Conceptual formulation
Research DWC

DWC can be understood as a ratio between decision throughput and oversight capacity at a given layer of the governance structure:

// Conceptual - not a numeric score DWC = decision_closure_frequency / accountable_oversight_capacity // Becomes critical when: DWC > 1 - more decisions are crossing the boundary than can be meaningfully understood, attributed, reviewed, and closed with real human governance
On precision: DWC is intentionally formulated as an inferential construct, not a numeric score. Expressing it as a specific ratio (e.g. "DWC = 4.2") would introduce false precision and expose the framework to methodological attacks it does not need. The meaningful output is categorical. The inference is structural, not arithmetic.

On the denominator: EVIDE does not measure the intrinsic cognitive capacity of a human operator - a psychological or medical question that is outside the framework's scope and deliberately avoided. What EVIDE observes is the asymmetry of scale between the machine-side generation pipeline and the human-side validation structure as declared by the organization itself. The denominator is not a universal human constant. It is the governance baseline the organization has declared - through its authority binding, its organizational structure, and its intake configuration. If that declared structure appears structurally inconsistent with the throughput the same organization's system is producing, the asymmetry is structurally observable. The burden of defining governance capacity rests with the organization, not with EVIDE.
DWC Levels
Research DWC

The research model defines four categorical levels. These describe the population-scale construct proposed in this note. They are not the values emitted by the current implementation - see the mapping note below.

Low
Decision closure frequency is compatible with real human oversight. Attribution, review, and contestability remain operationally viable for the declared authority structure.
Elevated
Frequency is increasing. Individual closures remain attributable and reconstructable. Oversight is still operational but approaching observable pressure. Monitoring recommended.
Compressed
Decisions are arriving faster than the authority structure can meaningfully process them. Attribution risk is active. Closure may remain formally valid while oversight becomes operationally strained.
Critical
Decision velocity appears structurally inconsistent with accountable closure conditions. Responsibility remains formally declared. It is no longer operationally governed. This is the entry condition for Formal Accountability Collapse.
Implemented behavior
The two scales are distinct and must not be conflated. The four levels above belong to the research model. The implemented dimension emits a different set of values under the profile key state: not_detected, detected, critical, unknown. Only the token critical appears in both, and it does not carry the same meaning in each. Integrators reading the API should follow the value set documented in Section 9.1, not the level names above.
Section 3
3. The DWC Stack - Five Observational Layers
Research DWC

In the research model, DWC is not a flat metric. It is a layered observation. Compression can occur at any level of the governance structure independently, or propagate across multiple levels simultaneously. A single layer appearing stable does not guarantee systemic stability. No part of this layered model is implemented today.

L1
Authority
Single decision-maker throughput
Can the declared authority realistically review, understand, and meaningfully close the volume of decisions attributed to them within the observed window? Compression here is the most direct form of oversight saturation.
L2
Organization
Institutional governance throughput
Does the organizational structure - its review panels, oversight committees, and accountability chains - have the collective capacity to process the decision volume being produced? Organizational compression can exist even when individual authorities appear unaffected.
L3
Workflow
Process pipeline density
Is the pipeline producing decision closures at a rate compatible with the review steps defined in the governance process? Workflow compression occurs when the process design appears structurally inconsistent with the operational volume, even if individual steps remain formally completed.
L4
Escalation
Review handoff bottlenecks
Are escalation paths - exception handling, contested decision review, override authorization - still operationally viable at current volume? Escalation compression is particularly dangerous because it removes the safety valve that exception governance provides.
L5
Domain
Governance category saturation
Is a specific decision category - a particular risk classification, a specific type of AI-assisted evaluation - being produced at a rate that appears structurally inconsistent with domain-specific review conditions? Domain compression can be invisible at higher organizational levels while critically saturated within a specific governance area.
The most dangerous DWC configuration is not maximum compression at a single level. It is moderate compression distributed across all five levels simultaneously - a condition where every layer appears manageable in isolation while the aggregate systemic pressure has already made meaningful oversight unrealizable.
Section 4
4. Formal Accountability Collapse (FAC)
Research DWC
Historical / research formulation. This section preserves the original research formulation published under the name Formal Accountability Collapse. It does not describe the implemented formal_accountability_collapse dimension returned by the current EVIDE API - that dimension, with its actual derivation and states, is documented in Section 9.1. The systemic FCC/DWC condition described below is retained as research history, pending the separate architectural disposition of what is referred to internally as OVC.

Formal Accountability Collapse is the emergent condition that arises when the Forensic Cross-Check (FCC) of individual decisions remains stable - closures are structurally intact, attributable, and reconstructable - while Decision Wave Compression has reached a level at which the governance infrastructure surrounding those closures can no longer sustain real oversight.

Formal Accountability Collapse is not misconduct.
It is not failure. It is not error.
It is the condition in which compliance remains visible
while governance has become operationally absent.

FAC does not require that anyone has acted in bad faith. It does not require that the system has malfunctioned. It does not require that any individual decision was incorrect. It requires only that the throughput of decisions has compressed the space available for accountability to stabilize to the point where the human oversight function, while formally present, has become semantically empty.

The critical distinction

FAC introduces a distinction that most governance frameworks do not model:

  • Visible compliance - dashboards show green, audit trails are complete, signatures are present, human authorities are declared
  • Viable governance - the human authorities can actually understand, review, contest, and meaningfully close the decisions attributed to them

Visible compliance and viable governance are not the same condition. They can diverge. FAC is the name for that divergence when it becomes systemic.

What FAC is not: FAC does not claim that any specific decision was wrong. It does not claim that any authority acted improperly. It does not constitute evidence of misconduct, negligence, or regulatory violation. It observes that the systemic conditions under which a series of decisions were closed are structurally inconsistent with the kind of oversight that makes those closures meaningfully attributable.

The framing is epidemiological, not accusatory. Epidemiology identifies conditions that increase the probability of a disease outcome - without claiming that any specific individual will become sick, or that any specific instance of illness was caused by that condition alone. DWC operates analogously: it identifies governance conditions that increase the probability of accountability fragility - without claiming that any specific decision was incorrectly closed, or that any specific authority failed.

FAC is a signal of governance fragility. It is not a finding of fault.
Section 5
5. Why Existing Audit Models Do Not Capture This
Research DWC

Traditional audit and compliance models are designed to evaluate individual decisions or transaction records. They ask: was this decision correctly made? Was it properly attributed? Is the documentation complete? Does it satisfy the relevant policy?

These are the right questions for individual decision quality. They are insufficient for systemic governance stability, because they are structurally blind to temporal and volumetric pressure.

What traditional audit observes
  • Whether a specific decision was correctly recorded
  • Whether the declared authority exists and is credentialed
  • Whether the required steps in the process were completed
  • Whether the documentation is present and consistent
What traditional audit does not observe
  • How many decisions were closed by the same authority in the same window
  • Whether the review latency was consistent with meaningful evaluation
  • Whether the escalation path remained viable at that volume
  • Whether the cognitive and organizational conditions for real oversight existed
  • Whether the throughput itself has structurally degraded the attribution

This is not a criticism of audit methodology. Audit was designed for a world where decision volumes were bounded by human production capacity. In high-density AI decision systems, the production capacity constraint has been removed from the decision-making process while remaining present in the oversight process. That asymmetry is precisely what DWC and FAC are designed to observe.

Audit verifies what was decided.
DWC observes whether the conditions for deciding responsibly still existed.
On statistical sampling: DWC does not presuppose that a human operator must review every record sequentially. It is compatible with sampling-based governance models. What DWC observes is not whether each individual record was inspected, but whether the rate of decisions carrying direct legal attribution - including anomaly triggers that would require escalation under a sampling model - is structurally consistent with the declared governance bandwidth. If an organization's governance model relies on sampling, the sampling policy itself is part of its declared oversight structure. When throughput generates attribution-bearing records faster than that structure can absorb them - including the escalation paths that sampling anomalies would activate - DWC registers compression. The sampling argument does not dissolve the asymmetry. It shifts the boundary at which the asymmetry becomes visible.

A useful analogy: an audit of a hospital's patient records would verify that each patient file is complete, signed, and compliant. DWC would observe whether the throughput of cases assigned to each physician is compatible with the kind of medical judgment that makes each signature meaningful - not by establishing a specific number, but by observing whether the rate is structurally consistent with the review depth the signature implies. The files can be identical in form. The governance condition they represent is not.

Section 6
6. FCC ร— DWC - The Combined Framework
Research DWC

The Forensic Cross-Check (FCC) and Decision Wave Compression (DWC) are inferentially independent despite sharing observational inputs. Both read the runtime visibility dimension; neither reads the other's output. FCC is structural and synchronic - it evaluates the quality of a single closure surface at a point in time. DWC is dynamic and diachronic - it evaluates the pressure context surrounding a series of closures over time.

A system can exhibit any combination of FCC and DWC states. The intersection defines the governance condition. The matrix below is expressed in Research DWC levels, not in the values emitted by the current implementation:

FCC StateDWC LevelConditionInterpretation
stablelow Green Closure is structurally sound. Oversight is operationally viable. No governance pressure signal.
stableelevated Monitor Individual closures remain intact. Volume is increasing. Attention to throughput trends recommended.
stablecompressed Accountability Risk Each closure appears formally sound while the governance context has entered compression. Attribution is at risk of becoming formal rather than substantive.
stablecritical Asymmetric Attribution Risk (FAC — research term) Formal Accountability Collapse condition. Closures are individually intact. Governance infrastructure has become operationally absent. Visible compliance. Non-viable oversight.
degradedcompressed Compound Risk Structural continuity is degraded and throughput pressure is active. Both dimensions are signaling instability simultaneously.
degradedcritical Unverifiable Governance Context Maximum combined governance risk. Structural and dynamic instability are both critical. Full remediation required before further evidentiary use.
Naming note. The label "Formal Accountability Collapse (FAC)" in the row above belongs to the Research DWC model - the same historical name used in Section 4. It is not the implemented formal_accountability_collapse API dimension, which uses a different derivation and is documented in Section 9.1.
The FCC stable + DWC critical combination is the most important and least visible risk state. Because every individual closure appears formally intact, no existing audit signal fires. Only a temporal and volumetric layer of observation - which traditional audit does not provide - can detect it.
EVIDE observes. It does not enforce.
DWC does not declare what the threshold is.
It makes the approach to the threshold visible.
Observation and enforcement are architecturally separate. DWC belongs to the first. It provides no basis for automatic invalidation, legal determination, or regulatory ruling. It provides structured evidence that a question about governance viability can be asked - with evidence rather than assumption.
Section 7
7. The Foundational Principle
Research DWC
"Meaningful oversight has a throughput boundary."
Beyond that boundary, oversight continues to exist formally while ceasing to function semantically.

This principle does not depend on a specific number. It does not require a defined threshold. It is structurally true because any act of meaningful oversight - understanding a decision, attributing it, evaluating whether it should be contested, accepting responsibility for it - requires time, cognitive capacity, and contextual availability. These are finite resources.

When the system producing decisions removes the production constraint without removing the oversight constraint, an asymmetry emerges. The asymmetry is initially invisible - the oversight function is formally present. It becomes measurable over time, as throughput pressure accumulates. It becomes catastrophic when the asymmetry is discovered during a regulatory investigation or legal dispute, at which point all previous closures in the affected window come into question simultaneously.

An analogy from information theory

Shannon's channel capacity theorem establishes that any communication channel has a maximum rate at which information can be transmitted without loss. Beyond that rate, information degrades - not because the channel is broken, but because it cannot carry the semantic load at that speed.

The governance channel through a human authority has an analogous property. Beyond a certain throughput, meaningful accountability cannot be transmitted through it - not because the authority is dishonest or incompetent, but because the channel cannot carry the governance load at that decision velocity. The analogy is structural, not quantitative. It grounds the principle without committing to a specific number.

DWC observes the approach to that boundary.

Section 8
8. Regulatory Implications
Research DWC

The EU AI Act (Regulation 2024/1689), Article 14, requires that high-risk AI systems be designed and developed in such a way as to allow for effective human oversight during their use. The Article specifies that human oversight must be capable of:

  • fully understanding the AI system's capacities and limitations
  • monitoring its operation and detecting anomalies, dysfunctions, and unexpected performance
  • deciding not to use the AI system or overriding its outputs

None of these requirements can be meaningfully satisfied when the throughput of decisions produced by the AI system appears structurally inconsistent with the conditions under which the human oversight structure can meaningfully process them. The Article requires effective oversight - not formally declared oversight.

The research model set out in this note proposes DWC as an inferential construct for observing the distance between those two conditions. It is a proposal, not a delivered instrument: what the system emits today is the narrower per-closure observational signal described in Section 9.1.

The unresolved regulatory gap:

Article 14 of the EU AI Act does not define a measurement method - or any threshold - for determining when throughput conditions make meaningful oversight operationally impossible. The regulation requires the condition but provides no instrument for detecting when it has been violated.

This is a structural gap in the regulation, not a drafting oversight. Defining such thresholds would require the regulation to take a position on human cognitive limits and organizational capacity - terrain that legislation is poorly suited to occupy with precision.

DWC is designed to occupy exactly that terrain: not by establishing thresholds, but by providing an inferential construct that makes the systemic conditions observable in a structured, auditable, and non-prescriptive way. It does not tell a regulator what the threshold is. It makes the approach to the threshold visible - so that the question of whether meaningful oversight still exists can be asked with evidence rather than assumption.

The same structural gap applies across multiple regulatory frameworks:

  • NIST AI RMF (Govern 1.2, 1.4) - requires human oversight functions without defining throughput-based degradation conditions
  • ISO/IEC 42001 (clause 6.1.2) - requires identification of AI risks without providing instruments for volumetric governance pressure
  • GDPR Article 22 - requires meaningful human involvement in automated decision-making without specifying the conditions under which involvement ceases to be meaningful at scale

In each case, the regulatory requirement is real and correctly framed. The measurement instrument is absent. DWC is proposed as a contribution toward filling that absence.

Section 9
9. Implementation Status

This section separates what the system emits today from what this note proposes and from what is planned. The three are stated independently and are not reconciled into a single description.

9.1 โ€” Current implemented layer
Implemented behavior

A dimension named decision_wave_compression is present in the evidentiary profile returned by the intake API, from profile_version 1.1 onward. It is computed server-side, cannot be submitted or overridden by the intake system, and is not part of the hashed evidentiary object: it is an observation attached to the closure record, not a declaration bound into it.

It is derived from three values declared in the payload of the single closure being stabilized. It does not aggregate across records, does not observe a time window, and does not read volume, velocity, or density.

What the API returns today
"decision_wave_compression": { "mode": "inferred", "state": "detected", "derivation": "runtime_visibility_x_boundary_readiness_x_unresolved_signals", "function": "decision_wave_compression" }

The key is state, not level. There is no frequency_window, no intake_count, no signal, and no authority_capacity_profile. Those members belong to the research model in 9.2 and do not exist in any released version.

Implemented derivation
// runtime_visibility is itself derived, not declared: // handoff.boundary_readiness.visibility_surface // declared_complete โ†’ confirmed // partial โ†’ partial // insufficient โ†’ unverifiable runtime_visibility = confirmed AND boundary_readiness = verified AND unresolved_signals is empty โ†’ not_detected runtime_visibility = unverifiable OR boundary_readiness = unverifiable โ†’ critical runtime_visibility = partial OR boundary_readiness = verified_partial OR unresolved_signals is not empty โ†’ detected // no rule matched โ†’ unknown
StateMeaning in the implemented layer
not_detectedThe closure was stabilized under fully declared observational conditions with no unresolved signals.
detectedObservational conditions were partial, or unresolved signals were present at closure.
criticalObservational conditions or boundary readiness were declared unverifiable.
unknownNo rule matched. Absence of inference, not a positive finding.
What this layer is: a per-closure observability signal. It reports the declared observational quality of the conditions under which one decision was stabilized. What it is not: a measurement of throughput. The research model in 9.2 describes a population-scale instrument; this is not a partial computation of it, it is a different and narrower observation that ships under the same field name.
Formal Accountability Collapse — Implemented behavior
Implemented behavior

A dimension named formal_accountability_collapse is present in the same evidentiary profile, from profile_version 1.1 onward, computed by the identical server-side mechanism as decision_wave_compression: it cannot be submitted or overridden by the intake system, and it is not part of the hashed evidentiary object.

It is derived from three values read for the same closure: whether authority was declared, the declared attribution status of the threshold authority, and the Forensic Cross-Check continuity state already computed for that closure. It is not a combination of the Decision Wave Compression state and the Forensic Cross-Check state - the historical formulation that used this same name is preserved, unchanged, in Section 4, with a notice at its start pointing back here.

What the API returns today
"formal_accountability_collapse": { "mode": "inferred", "state": "detected", "derivation": "authority_x_threshold_attribution_x_continuity", "function": "formal_accountability_collapse" }
Implemented derivation
// authority: "declared" only if both authority.id and authority.role // are non-empty in the payload; otherwise absent (null) // threshold_attribution: classification_context.threshold_authority.attribution_status // continuity: the Forensic Cross-Check state already computed for this same closure - // not a separately declared input authority = declared AND threshold_attribution in (attributed, implicit) AND continuity = stable → not_detected continuity = broken OR authority is absent OR threshold_attribution = unknown → critical threshold_attribution = fragmented OR continuity = degraded → detected // no rule matchedunknown
On precedence and missing values: the three rules above are evaluated in order, and the first match wins. This produces two asymmetric behaviors worth stating explicitly. An absent authority forces critical unconditionally, regardless of the other two values. An absent threshold attribution does not by itself force any state - it fails the first rule, does not match the literal string unknown checked by the second, and falls through to unknown unless continuity is independently broken or degraded.
StateMeaning in the implemented layer
not_detectedAuthority was declared, the threshold's attribution was declared attributed or implicit, and this closure's Forensic Cross-Check state was stable.
detectedThe threshold's attribution was declared fragmented, or this closure's Forensic Cross-Check state was degraded.
criticalThis closure's Forensic Cross-Check state was broken, authority was not declared, or the threshold's attribution was declared unknown.
unknownNo rule matched - for example, threshold attribution was not declared and none of the other conditions applied. Absence of inference, not a positive finding.
What this layer is: a per-closure structural signal reporting whether a declared, attributable authority - with an attributable or implicit threshold ownership - stood behind a closure whose own Forensic Cross-Check state was stable. What it is not: it is not a measure of decision throughput, not a measure of human cognitive capacity, and not a temporal or population-level analysis of a series of closures. It is not derived by combining the Decision Wave Compression state with the Forensic Cross-Check state. It does not determine misconduct. It does not determine legal liability. It does not determine that any specific decision was incorrect. The research construct published under the same name in Section 4 describes a different, systemic condition and is not the source of this implemented signal.
9.2 โ€” Research DWC
Research DWC

The population-scale model described in Sections 2 through 8 is a research program. Its target output shape is set out below for reference. No released version emits this structure, and its member names are not stable.

Target shape โ€” research model, not released
{ "decision_wave_compression": { "mode": "inferred", "level": "elevated", // low | elevated | compressed | critical "signal": "accountability_compression", "frequency_window": "1h", "intake_count": 84, "authority_capacity_profile": { "mode": "inferred", "classification": "single_attributable_identity", "oversight_band": "bounded" } } }
On single_attributable_identity: This classification refers to the juridical and formal identity bound to the intake credential - not the physical number of people who may share a workstation or credential. If five individuals operate under the same authenticated identity, the attributable legal actor is one: the entity to whom the DAPI-verified identity and API key are formally assigned. EVIDE tracks the identity context as declared and bound at authentication time. The physical headcount in the room is outside EVIDE's observational scope and outside its responsibility. Organizations that assign shared credentials to multiple operators are making a governance choice that determines the attribution structure EVIDE will observe - not one that EVIDE is responsible for correcting.
9.3 โ€” Future evolution
Future roadmap

The original roadmap for this note is restated below against what has actually been delivered. Nothing in this subsection has been built.

PhaseScopeStatus
1 Theoretical framework definition โ€” this document Delivered
2 Server-side frequency tracking per authority, API key, and organization Not started
3 DWC signal in the evidentiary profile carrying level, signal, frequency_window, intake_count and authority_capacity_profile Open โ€” current implementation diverges
4 Multi-layer DWC stack across organization, workflow, and domain dimensions Not started
5 Formal schema declaration and public specification Not started
On Phase 3. A first server-side version of the construct was implemented and ships today, but it is not the object specified in Phase 3. It is a different, narrower observation that occupies the same field name. The phase as originally described remains open; Section 9.1 sets out what the implemented layer does instead.
The evidentiary profile evolves independently from the intake schema. profile_version tracks the profile structure; evide_schema tracks the payload contract. Extending the implemented layer toward the research model would change the profile, not the intake schema, and would preserve backward compatibility for consumers that branch on profile_version.

References and Related Work

EVIDE Framework: certifywebcontent.com - Evidentiary Deposit

Forensic Cross-Check (FCC): Canonical construct reference

EVIDE Intake Schema Documentation: Intake schema reference

Evidentiary Continuity: Chaining responsibility across decisions

The Hidden Governance Risk (continuity-substrate instability): Technical Note v1.0

EVIDE v2.x Roadmap: Architectural Backlog

EU AI Act, Article 14 - Human Oversight: Regulation (EU) 2024/1689

EVIDE Signals: External Validation & Research Signals

Two dimensions. One framework.

FCC observes the structural quality of the closure surface.
DWC observes the temporal pressure on the governance infrastructure surrounding it.
FAC — the implemented dimension — observes whether a declared, attributable authority stands behind a structurally coherent closure.

"A decision is not only risky because of what it decides,
but because of how many adjacent decisions are being closed
before responsibility can meaningfully stabilize."

Framework status: research layer ยท narrower server-side observational layers implemented
Contact: info@informaticainazienda.it