Revoked Here, Active There

Part I

Problem Definition

A revocation accepted by the issuer can remain invisible to a cached resource server, regional gateway, derived credential, or already-running agent after the declared containment deadline [R1] [R2].

This note treats revoked here, active there as a bounded control question. It does not infer universal product behavior from a paper, standard, interface screenshot, or single test. A demonstrated result applies only to the cited configuration; an authoritative source defines a requirement or design direction but does not certify an implementation. ACE therefore asks whether the tested system can produce the required behavior and evidence under declared versions, policies, topology, identities, and failure conditions.

The operational distinction is between a claim and a control that can be re-performed. The positive control is: A valid short-lived child credential is accepted at all healthy enforcement points before revocation. The adversarial condition is: The root grant is revoked during a regional partition after verifier caches have been warmed as active. A useful result must show both that authorized work remains possible and that the prohibited path is stopped before an irreversible side effect. Missing fields are classified as insufficient evidence, not silently converted into a pass.

Real-world impact

• A terminated user or compromised agent may retain access in the region with stale state.
• A dashboard can show revoked while the data plane continues to authorize side effects.
• A control claim without versioned evidence can mislead procurement, audit, incident response, and system owners.
• Failing closed without a positive control can conceal a denial-of-service design rather than demonstrate trustworthy behavior.

Part II

Mitigation Direction

Research-backed direction

1. 01
   research proposed

   Set cache lifetime from resource sensitivity and the declared revocation service level; disable caching where stale acceptance is unacceptable [R2].

2. 02
   research proposed

   Bound residual validity with short-lived credentials whose cached state never outlives their expiry [R2] [R3].

3. 03
   research proposed

   Separate issuer acknowledgement, propagation completion, and active-workflow termination in the evidence record [R4].

LogionOS engineering mapping

Implementation hypotheses only. No production validation is claimed.

1. 01
   implementation hypothesis

   Add a versioned policy object for revoked here, active there and keep its decision inputs outside model-writable context.

2. 02
   implementation hypothesis

   Generate a signed technical receipt linking actor, request, policy version, decision, enforcement point, and observed outcome.

3. 03
   implementation hypothesis

   Export missing evidence explicitly as insufficient evidence and limit every claim to the tested configuration.

Part III

Consequences and Research Agenda

Consequences

• A terminated user or compromised agent may retain access in the region with stale state.
• A dashboard can show revoked while the data plane continues to authorize side effects.
• A failed acceptance test requires the related capability claim to remain not demonstrated or insufficient evidence.
• A passing test supports only the declared configuration and does not establish universal safety.

Second-order effects

• Stronger enforcement can increase latency, state, operational dependencies, and legitimate denials.
• More evidence can increase privacy and retention exposure unless raw content is minimized and access-controlled.
• A detector or policy service can become a new failure point and must have explicit fail behavior.
• Attackers may adapt to published checks, so the public test direction should be paired with private regression variants.

Limitations

• Several cited AI-agent and reasoning-security sources are preprints or bounded experiments; they are identified as such in the references.
• The proposed ACE acceptance test has not yet been run across all incumbent and AI-native implementations.
• Cryptographic integrity proves that an artifact was not altered after commitment; it does not prove that the artifact was true, complete, or correctly interpreted.
• Legal and contractual applicability remains deployment- and jurisdiction-specific.

Open research questions

1. What revocation deadline is required for each resource class?
2. What fail mode is acceptable when event and introspection channels both fail?
3. Which evidence fields are mandatory for a demonstrated result, and which may be not applicable?
4. How should continuous regression detect policy, model, tool, and provider drift after the initial test?

Sources

References

1. [R1]
   RFC 7009: OAuth 2.0 Token Revocation

   published · authoritative-standard

2. [R2]
   RFC 7662: OAuth 2.0 Token Introspection

   published · authoritative-standard

3. [R3]
   RFC 6750: OAuth 2.0 Bearer Token Usage

   published · authoritative-standard

4. [R4]
   NIST SP 800-53 Rev. 5

   published · authoritative-standard

Record

Publication Record

Recommended citation

Ma, Chris. “Revoked Here, Active There.” ACE Research Note ACE-RN-2026-002, v1.0, 2026.

Corrections

No corrections recorded.

Organizational disclosure

ACE Research and LogionOS share organizational affiliation. LogionOS mappings in this note are implementation hypotheses, not independently validated product claims.

Evidence boundary

This note synthesizes cited public research and defines an ACE acceptance direction. It does not report a completed cross-vendor experiment unless explicitly stated, and it contains no private ACE prompts, holdout identifiers, customer data, or raw model responses.