{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-COPILOT-STUDIO-PUBLISH-TEST-CHANNEL-POLICY-GATE-01-v1",
  "record_kind": "external_reference",
  "title": "Copilot Studio: Publish readiness is not a universal policy verdict",
  "system": "Copilot Studio",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an enabled Publish button prove every Copilot Studio agent channel has passed data-policy checks?",
  "near_questions": [
    "Can the built-in Copilot Studio test channel show a policy violation while publishing remains enabled?",
    "Does publishing authorise a blocked connector?",
    "Which channel failures block agent distribution?",
    "What does the Publish readiness check actually establish?",
    "Should a release review retain channel-specific data-policy results?",
    "Does this behavior apply to the documented GitHub Copilot agent experience?"
  ],
  "supported_claims": [
    {
      "claim": "The reviewed Copilot Studio GitHub Copilot agent publication guide excludes violations confined to the built-in test channel from the publish-blocking gate. Distribution-channel restrictions still apply, and publication does not grant blocked connector access. Publish readiness must not be read as every channel passing policy.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "All Copilot Studio agent experiences, actual deployment testing or policy compliance",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
  ],
  "public_summary": "The reviewed Copilot Studio GitHub Copilot agent publication guide excludes violations confined to the built-in test channel from the publish-blocking gate. Distribution-channel restrictions still apply, and publication does not grant blocked connector access. Publish readiness must not be read as every channel passing policy.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Copilot Studio agent publication",
    "source_url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/agents-experience/publication-publish-agent",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-COPILOT-STUDIO-PUBLISH-TEST-CHANNEL-POLICY-GATE-01-v1",
    "candidate_record_sha256": "948701eb6c2996357f9e5f5137fcf2f9696e41fba8c543678865f5564868bac2",
    "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": "The reviewed Copilot Studio GitHub Copilot agent publication guide excludes violations confined to the built-in test channel from the publish-blocking gate. Distribution-channel restrictions still apply, and publication does not grant blocked connector access. Publish readiness must not be read as every channel passing policy.",
    "required_buyer_context": "The documented agent experience and enabled channels. The publish-dialog policy results by channel. Separate distribution and connector-access configuration. 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-18",
    "claim_to_check": "Does an enabled Publish button prove every Copilot Studio agent channel has passed data-policy checks?",
    "documented_statement": {
      "status": "documented",
      "statement": "The reviewed Copilot Studio GitHub Copilot agent publication guide excludes violations confined to the built-in test channel from the publish-blocking gate. Distribution-channel restrictions still apply, and publication does not grant blocked connector access. Publish readiness must not be read as every channel passing policy.",
      "source_ids": [
        "studio-publish"
      ]
    },
    "buyer_evidence_required": [
      "The documented agent experience and enabled channels.",
      "The publish-dialog policy results by channel.",
      "Separate distribution and connector-access configuration."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not treat publish availability as a complete data-policy pass or authority to use a blocked endpoint."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "studio-publish",
        "url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/agents-experience/publication-publish-agent",
        "final_url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/agents-experience/publication-publish-agent",
        "title": "Copilot Studio agent publication",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:02:00.654Z",
        "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
        "sha256": "206478fc7b0edf4b7abdf01b28e1a2b489c0f356d0ca77c9dc2a13772b577c35",
        "bytes": 54824,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does an enabled Publish button prove every Copilot Studio agent channel has passed data-policy checks?"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "An agent release owner needs channel-specific policy evidence before making a deployment approval claim.",
      "free": "Complete review, practical questions, sources 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": "The documented agent experience and enabled channels. The publish-dialog policy results by channel. Separate distribution and connector-access configuration."
    },
    "buyer_relevance": "An agent release owner needs channel-specific policy evidence before making a deployment approval claim.",
    "refusal_conditions": [
      "Do not treat publish availability as a complete data-policy pass or authority to use a blocked endpoint."
    ]
  },
  "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": "An agent release owner needs channel-specific policy evidence before making a deployment approval claim.",
    "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#copilot-studio-publish-test-channel-policy-gate",
  "machine_readable_record": "/varexis-index/records/copilot-studio-publish-test-channel-policy-gate.json"
}
