{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "ice-09-tranche-68-v1",
  "route_id": "agentic_reviewed_entra_agent_dynamic_consent_static_inventory_gap",
  "record_id": "VXI-EXT-ICE09-ENTRA-AGENT-DYNAMIC-CONSENT-STATIC-INVENTORY-GAP-01-v1",
  "question": "Can a blueprint's initial permission list describe all later inherited access?",
  "answer": "Not necessarily. Explicit dynamic consent can add inherited permissions for an inheritable resource even when absent from required resource access. Under all-allowed inheritance, later granted scopes or roles on the blueprint principal also flow to child identities; scope and role inheritance are configured independently. Reconcile later grants and the applicable inheritance settings before treating the installation declaration as current authority.",
  "records": [
    {
      "record_id": "VXI-EXT-ICE09-ENTRA-AGENT-DYNAMIC-CONSENT-STATIC-INVENTORY-GAP-01-v1",
      "url": "/varexis-index/records/entra-agent-dynamic-consent-static-inventory-gap.json",
      "content_sha256": "c23dcf93ede285c72aa825c1bfcb61fb26d356918a2f0fb8c5c19c8d1b5b4dc5",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-30T15:17:58.235744+00:00",
        "record_id": "VXI-EXT-ICE09-ENTRA-AGENT-DYNAMIC-CONSENT-STATIC-INVENTORY-GAP-01-v1",
        "record_kind": "external_reference",
        "title": "Can a blueprint's initial permission list describe all later inherited access",
        "system": "Microsoft",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Can a blueprint's initial permission list describe all later inherited access?",
        "near_questions": [
          "Can later consent exceed the agent's installation declaration?",
          "Which inherited scopes were added after onboarding?",
          "Is requiredResourceAccess a complete historical permission inventory?",
          "What changed when dynamic consent was granted?"
        ],
        "supported_claims": [
          {
            "claim": "Not necessarily. Explicit dynamic consent can add inherited permissions for an inheritable resource even when absent from required resource access. Under all-allowed inheritance, later granted scopes or roles on the blueprint principal also flow to child identities; scope and role inheritance are configured independently. Reconcile later grants and the applicable inheritance settings before treating the installation declaration as current authority.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Reconcile subsequent consent before treating installation declarations as current access.",
          "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.",
          "No expanded capabilities or licences for existing INDEX executables."
        ],
        "public_summary": "Not necessarily. Explicit dynamic consent can add inherited permissions for an inheritable resource even when absent from required resource access. Under all-allowed inheritance, later granted scopes or roles on the blueprint principal also flow to child identities; scope and role inheritance are configured independently. Reconcile later grants and the applicable inheritance settings before treating the installation declaration as current authority.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "Microsoft primary documentation: entra inheritance",
          "source_url": "https://learn.microsoft.com/en-us/entra/agent-id/concept-inheritable-permissions",
          "checked_on": "2026-10-30",
          "candidate_record_id": "VXI-EXT-ICE09-ENTRA-AGENT-DYNAMIC-CONSENT-STATIC-INVENTORY-GAP-01-v1",
          "candidate_record_sha256": "31378bf93cca80ab7e65b2bf1fd6d3de596b7625b63a74c38227e6106ec41d04",
          "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": "Not necessarily. Explicit dynamic consent can add inherited permissions for an inheritable resource even when absent from required resource access. Under all-allowed inheritance, later granted scopes or roles on the blueprint principal also flow to child identities; scope and role inheritance are configured independently. Reconcile later grants and the applicable inheritance settings before treating the installation declaration as current authority.",
          "required_buyer_context": "initial declarations; later grants; inheritance settings; review time; separate scope/role inheritance settings. 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",
          "applicability_status": "Existing documented requirement; captured 2026-10-30; deployed behaviour unverified.",
          "checked_on": "2026-10-30",
          "claim_to_check": "Can a blueprint's initial permission list describe all later inherited access?",
          "documented_statement": {
            "status": "documented",
            "statement": "Not necessarily. Explicit dynamic consent can add inherited permissions for an inheritable resource even when absent from required resource access. Under all-allowed inheritance, later granted scopes or roles on the blueprint principal also flow to child identities; scope and role inheritance are configured independently. Reconcile later grants and the applicable inheritance settings before treating the installation declaration as current authority.",
            "source_ids": [
              "entra-inheritance"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Can a blueprint's initial permission list describe all later inherited access? Reconcile subsequent consent before treating installation declarations as current access. Entra dynamic consent extends inherited access beyond static declarations, unlike GitHub installation approval. This is an operational review inference, not an observed deployment outcome.",
            "source_ids": [
              "entra-inheritance"
            ]
          },
          "buyer_evidence_required": [
            "initial declarations",
            "later grants",
            "inheritance settings",
            "review time",
            "separate scope/role inheritance settings"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Reconcile subsequent consent before treating installation declarations as current access."
          },
          "unknowns": "The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.",
          "unknown_finding": {
            "status": "unknown",
            "statement": "No buyer deployment or transaction was observed."
          },
          "evidence_sources": [
            {
              "source_id": "entra-inheritance",
              "url": "https://learn.microsoft.com/en-us/entra/agent-id/concept-inheritable-permissions",
              "final_url": "https://learn.microsoft.com/en-us/entra/agent-id/concept-inheritable-permissions",
              "captured_at_utc": "2026-10-30T14:23:57.839577+00:00",
              "status": 200,
              "content_type": "text/html",
              "bytes": 60403,
              "sha256": "8e3c12d3cb933ca96a3ce66c507dde2c5a28973aae78f94fa1846c748618fd48",
              "title": "Microsoft primary documentation: entra inheritance",
              "publisher": "Microsoft",
              "checked_on": "2026-10-30",
              "capture_status": 200,
              "claim_review_completed": true,
              "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
              "version_context": "Existing documented requirement; captured 2026-10-30; deployed behaviour unverified.",
              "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
              "reviewed_sections": [
                "Two conditions for inheritance",
                "Required resource access",
                "Inheritance patterns",
                "Dynamic consent (blueprint principal, permission explicitly requested)",
                "only observable in the token"
              ]
            }
          ],
          "observed_deployment": false,
          "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.",
          "paid_value": {
            "decision_context": "Can a blueprint's initial permission list describe all later inherited access? Reconcile subsequent consent before treating installation declarations as current access.",
            "free": "Complete source review, questions, provenance and limitations; free to read and save locally.",
            "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.",
            "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.",
            "excluded": [
              "Fresh source research",
              "Native provider integration or schema support",
              "Live inspection or runtime enforcement",
              "Payment settlement or verified deletion",
              "Certification or expanded licences"
            ],
            "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature."
          },
          "revalidation": {
            "trigger": "Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included.",
            "specific_watch": "Required resource access; Two conditions for inheritance; Inheritance patterns; Dynamic consent (blueprint principal, permission explicitly requested)"
          },
          "buyer_relevance": "Can a blueprint's initial permission list describe all later inherited access? Reconcile subsequent consent before treating installation declarations as current access.",
          "refusal_conditions": [
            "Reconcile subsequent consent before treating installation declarations as current access.",
            "Do not infer deployment conformance, authority or successful outcomes from source documentation."
          ],
          "decision_context": {
            "operator": "Identity administrator or delegated-access reviewer",
            "scenario": "Can a blueprint's initial permission list describe all later inherited access?",
            "consequence": "Reconcile subsequent consent before treating installation declarations as current access.",
            "confidence": "High for the explicitly bounded captured clause; conflicts and version limits retained; deployment untested."
          },
          "novelty_review": {
            "candidate_id": "ICE09-201",
            "disposition": "EXTENSION",
            "nearest_record_id": "VXI-EXT-PROCUREMENT-GITHUB-APP-PERMISSION-APPROVAL-01-v1",
            "nearest_record_url": "/varexis-index/records/github-app-permission-update-installation-approval.json",
            "nearest_record_sha256": "ebe98ade79c2235f8b12f29f0935eff7ea402bef3fdce391785714b13a7e7eb9",
            "material_distinction": "Entra dynamic consent extends inherited access beyond static declarations, unlike GitHub installation approval.",
            "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
          },
          "optional_selection": {
            "guide_id": "delegated-agent-identity-continuity",
            "guide_url": "/index-guides/delegated-agent-identity-continuity",
            "guide_manifest": "/varexis-index/decision-guides.json",
            "checker": {
              "product_id": "agent-tool-admission",
              "price_gbp_excluding_vat": 49,
              "purchase_url": "/index-access?route=agentic_pack_tool_admission_v1",
              "licence_scope": "Existing separate internal-use licence; subscriptions do not include the executable.",
              "benefit": "Optional local analysis of supported supplied declarations only; no native provider integration or verification is added."
            },
            "boundary": "Optional existing checker analyses its supported supplied declarations locally. It does not connect to the documented provider, import native provider exports, verify tokens, establish live outcomes or extend its schema or licence."
          },
          "exact_access": {
            "endpoint": "/mcp/catalogue",
            "tool": "get_publication_record",
            "arguments": {
              "record_id": "VXI-EXT-ICE09-ENTRA-AGENT-DYNAMIC-CONSENT-STATIC-INVENTORY-GAP-01-v1"
            },
            "record_url": "/varexis-index/records/entra-agent-dynamic-consent-static-inventory-gap.json",
            "original_mcp_search": false,
            "paid_saved_retrieval": false
          }
        },
        "niche": {
          "niche_id": "ice09-identity",
          "label": "Agent Identity, Credentials & Delegation",
          "classification_id": "identity",
          "classification_label": "Agent Identity, Credentials & Delegation",
          "topic_id": "identity",
          "buyer_intent": "Can a blueprint's initial permission list describe all later inherited access? Reconcile subsequent consent before treating installation declarations as current access.",
          "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#entra-agent-dynamic-consent-static-inventory-gap",
        "machine_readable_record": "/varexis-index/records/entra-agent-dynamic-consent-static-inventory-gap.json"
      }
    }
  ],
  "access": {
    "mode": "exact_http_only",
    "payment_required": false,
    "purchase_url": null,
    "mcp_preview_available": false,
    "paid_saved_retrieval_available": false,
    "natural_language_search_qualified": false
  },
  "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.",
  "content_sha256": "4f88cad320d9e5c3cc66f4367e2322df1709ab8104d95682c5e7d4899993ee7f"
}