{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:09:18.442Z",
  "record_id": "VXI-EXT-PROCUREMENT-SERVICENOW-UI-POLICY-DATA-POLICY-API-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "ServiceNow UI policies and API data validation",
  "system": "ServiceNow",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does hiding or restricting a field with a ServiceNow UI policy establish the same restriction for REST writes?",
  "near_questions": [
    "Do ServiceNow UI policies apply to REST writes?",
    "Which ServiceNow operations use data policies by default?",
    "Can import-set settings affect data-policy enforcement?",
    "What evidence checks a field restriction outside the browser form?"
  ],
  "supported_claims": [
    {
      "claim": "The Brazil data-policy guide limits UI policies to standard-browser form entry. Data policies instead apply mandatory and read-only rules and, by default, cover GlideRecord operations including Scripted REST and the Table API. Certain SOAP, import-set and client-side applications can be opted out. A form policy is not a universal API data control.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A hidden UI field as proof of API denial or authorization",
    "Effective policies and the buyer’s write outcome are unknown.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "The Brazil data-policy guide limits UI policies to standard-browser form entry. Data policies instead apply mandatory and read-only rules and, by default, cover GlideRecord operations including Scripted REST and the Table API. Certain SOAP, import-set and client-side applications can be opted out. A form policy is not a universal API data control.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Data policy — Brazil",
    "source_url": "https://www.servicenow.com/docs/r/platform-administration/c_DataPolicy.html",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SERVICENOW-UI-POLICY-DATA-POLICY-API-BOUNDARY-01-v1",
    "candidate_record_sha256": "14579c8ae43beaa380c9cefcc1c53587355aadfae971a20750ce50ad68c38503",
    "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 Brazil data-policy guide limits UI policies to standard-browser form entry. Data policies instead apply mandatory and read-only rules and, by default, cover GlideRecord operations including Scripted REST and the Table API. Certain SOAP, import-set and client-side applications can be opted out. A form policy is not a universal API data control.",
    "required_buyer_context": "Field and applicable UI and data policies; REST, GlideRecord or import path and opt-out settings; Separate authorization ACLs and observed validation result. 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 hiding or restricting a field with a ServiceNow UI policy establish the same restriction for REST writes?",
    "documented_statement": {
      "status": "documented",
      "statement": "The Brazil data-policy guide limits UI policies to standard-browser form entry. Data policies instead apply mandatory and read-only rules and, by default, cover GlideRecord operations including Scripted REST and the Table API. Certain SOAP, import-set and client-side applications can be opted out. A form policy is not a universal API data control.",
      "source_ids": [
        "servicenow-data-policy-extract"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review data-policy applicability and ACLs for the actual write path rather than infer API behavior from the form.",
      "source_ids": [
        "servicenow-data-policy-extract"
      ]
    },
    "buyer_evidence_required": [
      "Field and applicable UI and data policies",
      "REST, GlideRecord or import path and opt-out settings",
      "Separate authorization ACLs and observed validation result"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Reject an API-write restriction claim based only on the field’s form appearance."
    },
    "unknowns": "Effective policies and the buyer’s write outcome are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Effective policies and the buyer’s write outcome are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "servicenow-data-policy-extract",
        "url": "https://www.servicenow.com/docs/r/platform-administration/c_DataPolicy.html",
        "final_url": "https://www.servicenow.com/docs/r/platform-administration/c_DataPolicy.html",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:09:18.307Z",
        "sha256": "4b421a59db252da476c7044aa5ca50b4942d6989dc39f438487fea329db3ddab",
        "bytes": 1963,
        "title": "Data policy — Brazil",
        "hash_basis": "SHA-256 of exact extracted section text UTF-8 bytes in the private .body file, not a publisher HTML hash.",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "capture_method": "Inspected web-tool extraction of the primary documentation section; raw browser HTML contained an unpopulated application shell.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "UI versus data policies",
          "GlideRecord defaults and opt-outs"
        ],
        "version_context": "Brazil documentation; page updated 10 September 2026, inspected 24 October 2026. Hash identifies the extracted section, not the full HTML."
      }
    ],
    "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 automated data changes within the documented validation path.",
      "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 automated data changes within the documented validation path.",
    "refusal_conditions": [
      "Reject an API-write restriction claim based only on the field’s form appearance."
    ]
  },
  "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 automated data changes within the documented validation path.",
    "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#servicenow-ui-policy-data-policy-api-boundary",
  "machine_readable_record": "/varexis-index/records/servicenow-ui-policy-data-policy-api-boundary.json"
}
