{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T12:05:03.000Z",
  "record_id": "VXI-EXT-PROCUREMENT-OAUTH-REVOCATION-SUCCESS-INVALID-TOKEN-AMBIGUITY-01-v1",
  "record_kind": "external_reference",
  "title": "OAuth revocation success and invalid-token ambiguity",
  "system": "IETF OAuth",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an OAuth token revocation HTTP 200 prove that the submitted token previously existed?",
  "near_questions": [
    "Why can OAuth revocation return success for an invalid token?",
    "Is a revocation HTTP 200 evidence that a live token was found?",
    "Can one revocation acknowledgement close the entire credential inventory?",
    "What should offboarding evidence retain beyond the OAuth revocation response?"
  ],
  "supported_claims": [
    {
      "claim": "RFC 7009 returns HTTP 200 both when revocation succeeds and when the submitted token is invalid; clients ignore the response body. An invalid token is not an error because the requested invalidation outcome is already satisfied. The response therefore does not establish that a particular valid credential existed or that every related credential was revoked.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Proof of historical token existence or revocation of every related credential",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "RFC 7009 returns HTTP 200 both when revocation succeeds and when the submitted token is invalid; clients ignore the response body. An invalid token is not an error because the requested invalidation outcome is already satisfied. The response therefore does not establish that a particular valid credential existed or that every related credential was revoked.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "RFC 7009: OAuth 2.0 Token Revocation",
    "source_url": "https://www.rfc-editor.org/rfc/rfc7009.txt",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-OAUTH-REVOCATION-SUCCESS-INVALID-TOKEN-AMBIGUITY-01-v1",
    "candidate_record_sha256": "3b3093f203b6efe4fc36f5ce872328752f515177f8609499e655caf473f8c6ba",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "RFC 7009 returns HTTP 200 both when revocation succeeds and when the submitted token is invalid; clients ignore the response body. An invalid token is not an error because the requested invalidation outcome is already satisfied. The response therefore does not establish that a particular valid credential existed or that every related credential was revoked.",
    "required_buyer_context": "Non-secret credential inventory and issuer identity; Revocation request identity, time and response status; Documented related-token scope and residual-access checks. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "Does an OAuth token revocation HTTP 200 prove that the submitted token previously existed?",
    "documented_statement": {
      "status": "documented",
      "statement": "RFC 7009 returns HTTP 200 both when revocation succeeds and when the submitted token is invalid; clients ignore the response body. An invalid token is not an error because the requested invalidation outcome is already satisfied. The response therefore does not establish that a particular valid credential existed or that every related credential was revoked.",
      "source_ids": [
        "rfc7009"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Retain credential inventory and applicable revocation-scope evidence separately from the acknowledgement.",
      "source_ids": [
        "rfc7009"
      ]
    },
    "buyer_evidence_required": [
      "Non-secret credential inventory and issuer identity",
      "Revocation request identity, time and response status",
      "Documented related-token scope and residual-access checks"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim a complete offboarding inventory or universal credential revocation from a single HTTP 200 response."
    },
    "unknowns": "Prior token validity, related credential state and residual access in the buyer deployment were not observed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Prior token validity, related credential state and residual access in the buyer deployment were not observed."
    },
    "evidence_sources": [
      {
        "source_id": "rfc7009",
        "url": "https://www.rfc-editor.org/rfc/rfc7009.txt",
        "final_url": "https://www.rfc-editor.org/rfc/rfc7009.txt",
        "status": 200,
        "captured_at_utc": "2026-10-24T11:34:50.104Z",
        "sha256": "b2f346d5a87ba9d7f09047901257a65f7ac0b26352095969c25821afab447829",
        "bytes": 23517,
        "title": "RFC 7009: OAuth 2.0 Token Revocation",
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "version_context": "Published RFC7009; exact captured RFC text",
        "reviewed_sections": [
          "2.2 Revocation Response"
        ],
        "claim_review_completed": true
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Keep offboarding receipts honest about what the provider acknowledgement proves.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Keep offboarding receipts honest about what the provider acknowledgement proves.",
    "refusal_conditions": [
      "Do not claim a complete offboarding inventory or universal credential revocation from a single HTTP 200 response."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Keep offboarding receipts honest about what the provider acknowledgement proves.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#oauth-revocation-success-invalid-token-ambiguity",
  "machine_readable_record": "/varexis-index/records/oauth-revocation-success-invalid-token-ambiguity.json"
}
