{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:09:18.442Z",
  "record_id": "VXI-EXT-PROCUREMENT-SALESFORCE-APEX-API-VERSION-EXECUTION-MODE-01-v1",
  "record_kind": "external_reference",
  "title": "Salesforce Apex versioned execution defaults",
  "system": "Salesforce",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does every Apex version enforce the same default field and object permissions as the Salesforce user interface?",
  "near_questions": [
    "How does API v67 change Apex default execution mode?",
    "Can an explicit system-mode Apex query ignore user field permissions?",
    "Does with sharing establish all object and field checks?",
    "What version evidence is needed to assess Apex authority?"
  ],
  "supported_claims": [
    {
      "claim": "The reviewed Secure Apex Classes guide states that API v67.0 and later default to user mode, while v66.0 and earlier default to system mode. Explicit system-mode operations and sharing declarations change the applicable boundary. Record sharing and field/object permissions are separate concerns; the source version must be retained when interpreting the default.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Guaranteed field-level security in every Apex execution context",
    "No buyer Apex code or runtime access result has been tested.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "The reviewed Secure Apex Classes guide states that API v67.0 and later default to user mode, while v66.0 and earlier default to system mode. Explicit system-mode operations and sharing declarations change the applicable boundary. Record sharing and field/object permissions are separate concerns; the source version must be retained when interpreting the default.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Secure Apex Classes | Work with Salesforce Data | Lightning Web Components Developer Guide | Salesforce Developers",
    "source_url": "https://developer.salesforce.com/docs/platform/lwc/guide/apex-security",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SALESFORCE-APEX-API-VERSION-EXECUTION-MODE-01-v1",
    "candidate_record_sha256": "209f3011d28da4381e9cd140e37fb7610e71e390149d8179b0d883341e58b225",
    "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 Secure Apex Classes guide states that API v67.0 and later default to user mode, while v66.0 and earlier default to system mode. Explicit system-mode operations and sharing declarations change the applicable boundary. Record sharing and field/object permissions are separate concerns; the source version must be retained when interpreting the default.",
    "required_buyer_context": "Apex class API version and entry point; Explicit user/system mode and sharing declarations; Required object, field and record-level authorization 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 every Apex version enforce the same default field and object permissions as the Salesforce user interface?",
    "documented_statement": {
      "status": "documented",
      "statement": "The reviewed Secure Apex Classes guide states that API v67.0 and later default to user mode, while v66.0 and earlier default to system mode. Explicit system-mode operations and sharing declarations change the applicable boundary. Record sharing and field/object permissions are separate concerns; the source version must be retained when interpreting the default.",
      "source_ids": [
        "salesforce-apex"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Inspect the class API version and explicit query, database-operation and sharing modes.",
      "source_ids": [
        "salesforce-apex"
      ]
    },
    "buyer_evidence_required": [
      "Apex class API version and entry point",
      "Explicit user/system mode and sharing declarations",
      "Required object, field and record-level authorization checks"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Reject a uniform-permission claim that omits API version or explicit execution modes."
    },
    "unknowns": "No buyer Apex code or runtime access result has been tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No buyer Apex code or runtime access result has been tested."
    },
    "evidence_sources": [
      {
        "source_id": "salesforce-apex",
        "url": "https://developer.salesforce.com/docs/platform/lwc/guide/apex-security",
        "final_url": "https://developer.salesforce.com/docs/platform/lwc/guide/apex-security",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:47:25.905Z",
        "sha256": "6f305975fe8ed17a70fb58d4a82fb701b9832d238058c3243c22d9d99a48b263",
        "bytes": 224173,
        "title": "Secure Apex Classes | Work with Salesforce Data | Lightning Web Components Developer Guide | Salesforce Developers",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "API 67.0 versus 66.0 defaults",
          "Sharing and user/system modes"
        ],
        "version_context": "Current Secure Apex Classes guide explicitly distinguishes API 67.0+ user-mode default from API 66.0-and-earlier system-mode default; explicit modes and class version must be checked."
      }
    ],
    "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 applying an obsolete execution-default assumption to a privileged integration.",
      "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 applying an obsolete execution-default assumption to a privileged integration.",
    "refusal_conditions": [
      "Reject a uniform-permission claim that omits API version or explicit execution modes."
    ]
  },
  "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 applying an obsolete execution-default assumption to a privileged integration.",
    "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#salesforce-apex-api-version-execution-mode",
  "machine_readable_record": "/varexis-index/records/salesforce-apex-api-version-execution-mode.json"
}
