TA-14 ACA v1.1 · PUBLIC EXPLANATORY SURFACE

T0 → T1
CONTINUING STANDING

An initial ALLOW is not permanent computational authority. TA-14 ACA treats continuity as a live requirement: the conditions that supported standing must remain sufficient when the next material computational commitment is reached.

A valid determination at T0 does not automatically establish standing for a material commitment at T1.

T0 · DETERMINE

Current evidence, authority, purpose, scope, continuity and resource conditions support a bounded ACA determination.

→

CHANGE · TEST

Observe a candidate change, attribute it, and determine whether it is material to the basis on which standing was established.

→

T1 · REVALIDATE

If a supporting condition materially changed, prior standing is not presumed controlling. Revalidate before the next material COMMIT.

What can invalidate affected standing?

Materiality follows dependency. ACA does not require every insignificant change to restart the chain.

EVIDENCEStale, contradicted, superseded, provenance-broken, or newly insufficient evidence can require revalidation.

AUTHORITYExpired, revoked, narrowed, or changed authority does not silently survive into the next material commitment.

SCOPEA branch, retry, tool, endpoint, target, or data scope outside the original binding requires a new determination.

PURPOSEA completed, cancelled, narrowed, or changed objective can remove the necessity that supported standing.

RESOURCEA changed compute class, budget, capacity condition, or resource consequence can require proportionality review.

DEPENDENCY / POLICYChanges to models, data sources, credentials, rules, endpoints, identity, or governing baseline can invalidate affected standing.

Detection is not authority

A monitor, detector, telemetry stream, or external system may produce evidence of change. It does not become the governance decision-maker merely because it detected the event.

DETECTObserve, timestamp, bind, and attribute a candidate material change.

ADJUDICATEACA evaluates whether the affected standing remains sufficient for the next computational commitment.

ALLOW

HOLD

DENY

ESCALATE

This was not added by a LinkedIn challenge

The public ACA v1.1 baseline already contains continuity and changed-context revalidation, material-change invalidation, current standing at COMMIT, outcome reset, and non-inheritance of authority. Later research can deepen implementation and adversarial testing without rewriting the frozen chronology.

Chronology matters. A later explanation or research note may make an existing rule easier to see or test. That does not mean the underlying rule was absent from the dated parent architecture.

What ACA already governs

CURRENT STANDING AT COMMITNo consequential branch crosses COMMIT without a current admissibility determination and binding.

MATERIAL-CHANGE INVALIDATIONA material change to a condition supporting standing invalidates the affected portion until revalidation.

FINAL CONTINUITYThe path must survive a final continuity check before COMMIT.

NO INHERITED AUTHORITYOutcome creates a new state and evidence record; it does not silently authorize the next consequence.

NO SILENT REPAIRHOLD, DENY, and ESCALATE remain real states rather than being converted into ALLOW to preserve throughput.

BOUND CONSEQUENCEPermission remains attached to the purpose, scope, evidence, authority, resource envelope, and consequence that justified it.

Examination boundary

Architecture-level interoperability or adversarial examination requires an identifiable, versioned, frozen governance object. Commentary can raise a proposition; it does not itself create a stable architecture for formal comparison.

Return to ACA Showcase Open ACA Pilot Lab Canonical ACA v1.1 Record