{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T12:05:03.000Z",
  "record_id": "VXI-EXT-PROCUREMENT-OAUTH-INTROSPECTION-ACTIVE-NOT-ACTION-AUTHORITY-01-v1",
  "record_kind": "external_reference",
  "title": "OAuth active introspection and action authority",
  "system": "IETF OAuth",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a resource server treat an OAuth introspection active response as approval for the requested action?",
  "near_questions": [
    "Does OAuth active true prove the required scope is granted?",
    "What must a resource server decide after token introspection?",
    "Can a live token still lack authority for the target resource?",
    "Which context is missing from an OAuth active-only check?"
  ],
  "supported_claims": [
    {
      "claim": "RFC 7662 defines active as an implementation-dependent token state, generally indicating an issued, unexpired and unrevoked token. Other introspection fields convey authorization context, including scope when supplied. The protected resource uses that information to make its authorization decision. active true alone does not establish permission for a particular operation and resource.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Action authorisation from token liveness alone or instantaneous revocation propagation",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "RFC 7662 defines active as an implementation-dependent token state, generally indicating an issued, unexpired and unrevoked token. Other introspection fields convey authorization context, including scope when supplied. The protected resource uses that information to make its authorization decision. active true alone does not establish permission for a particular operation and resource.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "RFC 7662: OAuth 2.0 Token Introspection",
    "source_url": "https://www.rfc-editor.org/rfc/rfc7662.txt",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-OAUTH-INTROSPECTION-ACTIVE-NOT-ACTION-AUTHORITY-01-v1",
    "candidate_record_sha256": "4a80dc13b5752d106c806d2b8fb46eb11739a168922a2398e8e025d152631834",
    "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 7662 defines active as an implementation-dependent token state, generally indicating an issued, unexpired and unrevoked token. Other introspection fields convey authorization context, including scope when supplied. The protected resource uses that information to make its authorization decision. active true alone does not establish permission for a particular operation and resource.",
    "required_buyer_context": "Introspection response, issuer and observation time; Required operation, resource and applicable scope; Resource-server authorization rules and caching behaviour. 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": "Can a resource server treat an OAuth introspection active response as approval for the requested action?",
    "documented_statement": {
      "status": "documented",
      "statement": "RFC 7662 defines active as an implementation-dependent token state, generally indicating an issued, unexpired and unrevoked token. Other introspection fields convey authorization context, including scope when supplied. The protected resource uses that information to make its authorization decision. active true alone does not establish permission for a particular operation and resource.",
      "source_ids": [
        "rfc7662"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Evaluate applicable scope, audience and resource policy with sufficiently fresh token-state evidence before admitting an action.",
      "source_ids": [
        "rfc7662"
      ]
    },
    "buyer_evidence_required": [
      "Introspection response, issuer and observation time",
      "Required operation, resource and applicable scope",
      "Resource-server authorization rules and caching behaviour"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not allow an action solely because active is true when its required authority has not been established."
    },
    "unknowns": "The issuer's active semantics, response freshness and actual resource-server decision are buyer-specific.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The issuer's active semantics, response freshness and actual resource-server decision are buyer-specific."
    },
    "evidence_sources": [
      {
        "source_id": "rfc7662",
        "url": "https://www.rfc-editor.org/rfc/rfc7662.txt",
        "final_url": "https://www.rfc-editor.org/rfc/rfc7662.txt",
        "status": 200,
        "captured_at_utc": "2026-10-24T11:34:50.489Z",
        "sha256": "2b7d688cb849f093e860557ac97e6cddac2556d69a4386561b22cdf97bf13657",
        "bytes": 36591,
        "title": "RFC 7662: OAuth 2.0 Token Introspection",
        "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 RFC7662; exact captured RFC text",
        "reviewed_sections": [
          "2.2 Introspection Response",
          "4 Security Considerations"
        ],
        "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": "Avoid admitting an agent action merely because its credential remains live.",
      "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": "Avoid admitting an agent action merely because its credential remains live.",
    "refusal_conditions": [
      "Do not allow an action solely because active is true when its required authority has not been established."
    ]
  },
  "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": "Avoid admitting an agent action merely because its credential remains live.",
    "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-introspection-active-not-action-authority",
  "machine_readable_record": "/varexis-index/records/oauth-introspection-active-not-action-authority.json"
}
