VAREXIS-INDEX

Public Evidence Catalog

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. Browse free additions · Catalogue and search coverage (JSON).

Existing route answers retain the dated production snapshot; catalogue counts below include the separate additions.

A public-safe discovery layer for bounded evidence and claim-boundary questions. Inspect the source and its limits before relying on a claim.

Evidence Packs: compare benefits, included questions and saved delivery. Packs available: GitHub + Playwright, Notion + Slack permissions, audit/export boundaries, Next.js advisories, code-scanner trust, telemetry redaction, GitHub release acceptance, plus the runnable integration kit. Inspect free evidence; choose saved delivery or the executable kit. Browse tool trust or supplier evidence.

External advisory lookup: 304,384 frozen affected-package source records, separately counted; not independent VAREXIS findings.

1817 public records are currently exposed: 66 VAREXIS evidence summaries (including 7 attributed supplied-review summaries), 1711 external documentation references and 40 derived claim-boundary records. Documentation and derived entries are not VAREXIS experiments.

1817public records
1917agentic routes
13791near-question hooks

Near-question hooks count distinct wording across records, routes and contexts; repeated wording is counted once.

Machine-readable index · Service/payment routing · Daily entry builder · Make a request

Questions, public answers and service routes

Read the complete public answer for free. Preview a published route, retain your access key and pay through the automatic service to save its source snapshot or obtain a receipt. Routine delivery needs no email.

Browse 1917 agentic routes

Which records show safe refusal, non-promotion, or not-qualified outcomes?

Public records identify refusal and not-qualified states. They do not convert negative evidence into a success claim.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What should a developer or agent pay for?

Agents can inspect public catalog, public records, question routes and pricing metadata before paying.

VAREXIS-INDEX Developer/API

Relevant public records

Can this evidence be used to claim production readiness, savings, or broad deployment?

Public records expose unsupported and not-demonstrated claim classes. Overclaiming should route to refusal or nearest-supported claim.

VAREXIS-INDEX Single Request

Relevant public records

Which BDAS records show positive selective-execution or workload-reduction evidence?

Public records show bounded positive evidence. They do not show unrestricted production readiness or customer savings.

VAREXIS-INDEX Single Request

Relevant public records

Which records should prevent an overclaim?

Public records expose non-promotion and negative states so agents do not convert them into success claims.

VAREXIS-INDEX Single Request

Relevant public records

Can VAREXIS show evidence pipeline discipline before a developer integrates?

Public records show pipeline and contract-binding discipline without claiming a fully automated self-service runtime.

VAREXIS-INDEX Single Request

Relevant public records

When is paid VAREXIS-INDEX access justified?

The complete published answer is free. Paid access adds saved source snapshots, unsigned receipts or repeated subscription retrievals; it does not add new evidence or bespoke investigation.

VAREXIS-INDEX Developer/API

Relevant public records

What does A2A establish about communication between independent agents?

The A2A specification defines a shared interaction model for independent agent systems. A particular pair of deployments still needs compatibility checks.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can an agent discover another agent's advertised capabilities through A2A?

A2A describes capability discovery and supported interaction modes. Advertised capability is a declaration; delivery quality and access permissions require separate evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does A2A task collaboration require exposing an agent's internal memory or tools?

A2A describes task collaboration and information exchange without requiring peers to expose their internal state, memory or tools. This is a protocol design statement, not proof of a deployment's confidentiality.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can OPA evaluate policy for a proposed agent action?

OPA evaluates policy against structured input. An agent action must be represented by suitable input and policy; this record does not show that a buyer's rules are complete or correct.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an OPA decision by itself enforce an agent's permissions?

OPA separates policy evaluation from enforcement. The calling application must apply the decision at the relevant action boundary; a returned decision alone does not establish that enforcement occurred.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can OPA run alongside services that need policy decisions?

OPA documents deployment alongside services and management interfaces for policy distribution and telemetry. Documentation of this architecture does not establish latency or availability for a particular installation.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What do OPA's management interfaces cover?

OPA documents interfaces for policy bundles, decision logs, status and discovery configuration. Integrators configure or implement the surrounding management service; the interfaces alone are not a completed control plane.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does a SPIFFE SVID establish about a workload?

An SVID lets a workload present a verifiable SPIFFE identity. Identity evidence does not by itself grant permission for a requested action or demonstrate the workload's behaviour.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can an SVID from any SPIFFE trust domain be accepted automatically?

SPIFFE roots identity trust in the relevant trust domain and signing authority. Acceptance across domains requires an appropriate trust relationship and verification policy.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What can a workload obtain through the SPIFFE Workload API?

The Workload API defines retrieval of workload identity documents and trust material. Availability and entitlement depend on the implementation and its configured caller identification.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can SPIFFE tooling support short-lived credentials for workload authentication?

SPIFFE deployment guidance describes workload-bound keys and short-lived X.509 credentials for authentication and TLS. Correct rotation and acceptance still depend on the deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does the Workload API's lack of an explicit client secret mean caller checks are unnecessary?

The Workload API specification places caller identification on the endpoint implementation through out-of-band checks. Lack of an application-level secret does not mean callers may be accepted without identification.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What isolation model does gVisor provide for agent-executed code?

gVisor documents an application-kernel sandbox between workloads and the host. This supports a design description, not a security guarantee for a specific agent deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a sandboxed workload directly use the host kernel's full interface through gVisor?

gVisor's Sentry handles workload system calls in userspace and mediates necessary host interaction. Workload compatibility and the configured access boundary need separate assessment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can gVisor integrate with container tooling through runsc?

gVisor provides the runsc OCI runtime for container integration. Runtime integration support does not establish that a particular image or workload is compatible.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does gVisor's security model eliminate every host-side risk?

gVisor aims to reduce host system-interface exposure through mediation and restriction. Its documented scope does not remove every attack vector or replace a secure surrounding architecture.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does SLSA mean by software provenance?

SLSA describes provenance as verifiable information about an artifact's origin and production. Provenance does not by itself establish that the software is harmless or suitable for a customer's use.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can a SLSA claim be assessed without naming its track and requirements?

SLSA v1.2 separates Build and Source tracks, each with its own requirements. A specific assurance claim needs the relevant track, level and supporting evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does using a recommended SLSA attestation format demonstrate SLSA assurance?

SLSA v1.2 recommends Provenance and Verification Summary Attestation formats without requiring those particular formats. Format choice alone does not show that underlying requirements were met.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does Sigstore's keyless signing model bind together?

Sigstore's documented keyless flow binds a signing key to an authenticated identity using a short-lived certificate. The identity binding does not establish software quality or permission to deploy.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does a Rekor transparency entry establish?

Sigstore describes Rekor as a public, append-only record of signing information. Log evidence supports auditability; it does not by itself approve the artifact's contents.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Is verifying an artifact signature sufficient for a Sigstore reliance decision?

The documented Sigstore verification flow checks the signature, expected identity, certificate trust and log inclusion evidence. Reliance also needs the buyer's expected artifact and use context.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does possession of a Sigstore bundle mean an artifact has already been verified?

A Sigstore bundle packages signature content and supporting verification material. A verifier still needs to evaluate that material against the expected artifact and trust policy.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What do OpenTelemetry semantic conventions contribute to agent observability?

OpenTelemetry semantic conventions standardise names for operations and telemetry data. Consistent naming does not establish that a deployment captures complete or accurate evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does the N1 wind-SCADA outcome establish selective-execution performance?

The supplied N1 evidence records a fallback selected before outer truth access when candidates did not qualify. The recorded external outcome supports safe refusal, not selective-execution performance.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does M4B establish when its centrifuge candidate was not qualified?

The supplied M4B evidence records non-qualification frozen before outer scoring and a full-processing fallback. Its accepted outcome is bounded safe refusal; candidate diagnostics do not establish live selective performance.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does the M4B prospective prediction establish a validated workload classifier?

The supplied observation record describes a prediction frozen before scoring and evaluated after the outcome. It preserves prospective evaluation evidence while the model remains unestablished; it grants no execution authority.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does M4's manufacturing outcome demonstrate selective performance?

The supplied M4 result records non-qualification before outer scoring and use of the full-processing fallback. It supports a bounded safe-refusal outcome beyond the earlier protocol-only summary, without establishing selective performance.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does Backblaze D0 characterisation establish a qualified selective operator?

The D0 source records completed development characterisation with no operator freeze. Qualification and locked-outer access remain recorded as unopened. This is preparation evidence, not an acceleration result.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can Backblaze D1 be cited as a successful performance result?

The D1 final state is worker failure. The supplied final record reports qualification and locked outer unopened and no production promotion. No successful performance result can be inferred from this run.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Which BDAS evidence distinguishes selective correctness, safe fallback and run failure?

PUMP-E2C preserves bounded consumed-data selective evidence. N1 and M4B preserve full-processing refusal outcomes. Backblaze D1 reports worker failure. These states cannot be combined into a general performance claim.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What context does a Cedar authorization request need?

Cedar requests identify the principal, action, resource and context. A correctly shaped request does not prove that these values accurately represent the intended operation.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does Cedar's default denial mean every policy error denies the whole request?

Cedar denies when no permit applies, and a satisfied forbid overrides a permit. Policies that error are skipped; error handling must not be described as unconditional denial.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does Cedar policy validation prove that the policy expresses the intended permissions?

Cedar can check policies against an application schema for consistency. Schema changes can invalidate earlier checks; validation alone does not establish the intended permission model.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can a CVSS score alone determine a buyer's operational risk?

CVSS v4.0 separates Base, Threat, Environmental and Supplemental metrics. Supplemental values add context without changing the score; a severity score alone does not establish local risk.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does a CVSS vector add to a published score?

A CVSS vector records the metric choices behind a score. FIRST's publication guidance calls for both score and vector; this makes the assessment inspectable without proving its inputs correct.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an omitted CVSS Safety value mean there are no safety impacts?

CVSS v4.0 includes safety-related context. An omitted Supplemental Safety assessment does not establish absence of safety impacts; deployment-specific consequences require separate assessment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an empty OSV query prove a package has no vulnerabilities?

OSV provides queries for known vulnerabilities by package version or commit, including batches. No returned match does not prove absence of unknown issues or correct identification of the deployed artifact.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does OSV aggregation establish about a vulnerability advisory?

OSV aggregates advisories in a shared vulnerability format. The originating advisory and affected-version mapping remain relevant; aggregation does not establish that a particular deployment is affected.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Are OSV import findings accepted vulnerability results?

OSV documents an experimental endpoint for records that fail import-time quality checks. Such findings describe ingestion issues and must not be treated as accepted vulnerability results or a stable interface guarantee.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does scanning a lockfile or SBOM establish complete deployment coverage?

OSV-Scanner documents SBOM, lockfile and directory inputs. The result depends on what the supplied input represents; supported input formats do not establish a complete inventory of the running system.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does publishing an SPDX document certify the software it describes?

SPDX is an open specification for exchanging supply-chain information. Its standards status does not certify a submitted document's completeness, license conclusions or the safety of its software.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does citing RFC 9700 establish that an OAuth deployment is secure?

RFC 9700 documents OAuth 2.0 security best practices and updates earlier guidance. Citation alone does not demonstrate that a deployment implements the relevant requirements.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What can sender-constrained access tokens support in an OAuth security claim?

RFC 9700 recommends sender-constraining access tokens to reduce misuse of stolen tokens. A deployment claim needs evidence that the relevant proof is checked; the mechanism is not a universal compromise guarantee.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does OAuth server metadata prove the deployment is correctly configured?

RFC 9700 recommends publishing authorization server metadata and using it where available. Metadata supports configuration but does not prove that advertised controls are correctly enforced.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Do CycloneDX format and version fields establish that a BOM is complete?

CycloneDX 1.7 defines format and specification-version identifiers. They identify the declared representation; completeness and correctness of the described inventory require separate evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can CycloneDX represent service and dependency relationships as well as components?

CycloneDX can describe components, services and dependency relationships. Representation support does not establish that a supplied BOM captures every direct or transitive relationship.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a valid SBOM and an empty vulnerability lookup prove a release is safe?

An inventory format identifies represented content, and a lookup reports known matches for its inputs. Check inventory completeness, artifact mapping and lookup date before describing coverage; neither result guarantees safety.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Did the later Backblaze D1 recovery establish exact output and a qualified speedup?

The supplied D1 recovery review reports acceptable operator quality and retained reference alerts on consumed development data, but an additional output caused the exact-output gate to fail. Repeated performance timing was withheld. This is a review summary, not an independently rechecked archive or rerun, and it supports no performance qualification or promotion.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does the supplied Backblaze D2 review establish a performance-qualified result?

The supplied D2 review reports exact replay on consumed development data, with the evaluated path slower in its reported matched timing comparisons and no net reduction in heavy work. Its disposition is exact development replay without performance qualification. This intake reviewed the report and lineage only; it did not recheck the underlying archive, rerun the experiment or establish fresh holdout performance.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does Agent Protocol standardise for agent runs and state?

Agent Protocol documents a framework-independent interface organised around runs, conversational threads and persistent stores. This describes an API model; it does not establish a particular server's behaviour, permissions or client compatibility.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a platform implementing a superset of Agent Protocol guarantee every client's compatibility?

Agent Protocol documentation describes LangGraph Platform as implementing a superset of the protocol. Additional platform features do not prove that every client, extension or version interoperates; compatibility requires a match between the specific interfaces in use.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does LangGraph's durable execution support establish recovery for a deployed agent?

LangGraph documents orchestration capabilities including durable execution, persistence, streaming and human oversight. A deployment still needs suitable configuration and recovery testing; the documented capabilities alone do not prove that a particular interrupted action resumes correctly.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Is LangChain required to use LangGraph?

The official LangGraph overview states that LangGraph can be used without LangChain. That package-level flexibility does not establish that a particular application's tools, integrations or migration path are independent of their own dependencies.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does NIST AI 600-1 add to AI risk management?

NIST AI 600-1 is a cross-sector generative AI profile accompanying AI RMF 1.0. It frames risks and suggested management actions for generative AI; citing the profile is not evidence that an organisation has implemented or tested those actions.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Do NIST's suggested generative AI risk actions demonstrate that controls were completed?

NIST AI 600-1 suggests actions across the Govern, Map, Measure and Manage functions. A suggested action is guidance, not a completed check: an implementation claim needs an accountable owner, defined scope and supporting evidence for the action actually taken.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does using NIST AI RMF amount to a certified safety result?

NIST describes AI RMF as a voluntary framework for managing AI risks. Its use can structure an assessment, but naming the framework does not establish certification, completion of controls or a safe outcome for a specific system.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Is the reviewed CAEP interoperability profile a final deployment assurance?

The reviewed CAEP Interoperability Profile 1.0 is labelled draft 01. It profiles Shared Signals, CAEP and OAuth requirements for interoperable implementations; draft guidance does not establish final standard status or a conforming, securely configured deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does the CAEP interoperability profile mean every event use case is implemented?

The reviewed draft CAEP profile describes use cases involving session, credential and device-compliance changes. Implementations can support selected use cases; a profile reference alone does not show which events a sender emits, a receiver accepts or an application acts on.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does the OpenID Shared Signals Framework establish?

OpenID's Shared Signals specifications describe a framework for exchanging security events between systems. The framework enables communication; a specification reference does not prove an integration is configured, signals arrive or a receiver enforces the intended policy.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does receiving a CAEP event prove that access changed?

OpenID describes CAEP event types that let receivers adjust access in response to changing conditions. Receiving an event and applying an access decision are separate steps; evidence of the receiver's policy and resulting action is needed to claim enforcement.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a RISC risk event establish that remediation occurred?

OpenID lists RISC as a specification for exchanging risk-related events using Shared Signals. A risk notification supplies information to another system; it does not by itself establish an accurate local risk decision, account recovery or completed remediation.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does OWASP's 2026 Agentic Top 10 provide?

OWASP's 2026 Agentic Top 10 presents security risks for agentic applications. It can inform threat review, but a catalogue is not an exhaustive assessment of a particular agent, its integrations or the actions it can perform.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does adopting OWASP agentic guidance establish tested security controls?

OWASP's agentic resource provides security guidance. A statement that a team follows it does not demonstrate implementation or test results; each claimed mitigation needs evidence tied to the relevant agent behaviour and deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does OWASP's MCP server development guide help assess?

OWASP's MCP server guide discusses security across the server boundary, including authentication, authorisation, input handling, isolation and deployment. This is development guidance; it does not validate a specific server or its connected tools.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does connecting an assistant to an MCP server authorise every chained tool action?

OWASP's MCP guide describes risks from delegated permissions, dynamic tools and chained calls. Connecting an assistant to a server does not establish user intent or permission for each downstream action; the actual authorisation scope and enforcement need review.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does MCP's July 2026 stateless core mean an application cannot keep state?

The MCP July 2026 release describes a stateless protocol core. Applications may still maintain their own state explicitly; the protocol model alone does not establish application retention, isolation or recovery behaviour.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does MCP's extension framework establish support for every optional capability?

The MCP July 2026 release introduces a formal extension framework and authorisation changes. An extension mechanism does not establish that a client and server implement the same optional capabilities or enforce them correctly; review their declared versions and behaviour.

VAREXIS-INDEX Evidence Receipt

Relevant public records

How do the Backblaze D1 failure, recovery and D2 reviews differ?

The historical D1 worker failure, later recovery review and D2 review are separate evidence states. The recovery report retains an exactness failure; the D2 report describes exact development replay without performance qualification. The two later entries summarise supplied reviews and do not independently reverify their archives or upgrade either result to production qualification.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Do agent interface and runtime features establish deployed reliability?

Agent Protocol describes an interface, LangGraph describes runtime capabilities, and MCP's release describes protocol state and extensions. These sources address different layers. Deployment compatibility, state handling and recovery need implementation-specific evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a shared security signal prove access enforcement or remediation?

Shared Signals, CAEP and RISC describe event exchange and event meaning. Actual access changes or remediation depend on receiver policy and observed actions. Preserve supported event coverage and the draft status of the reviewed CAEP interoperability profile.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Do NIST and OWASP references establish implemented agent safeguards?

NIST risk-management guidance and OWASP security resources help frame assessment. Referencing either does not demonstrate completed controls, tested tool permissions or secure behaviour. Retain the cited edition, selected actions and evidence for the actual deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an AgentCore workload identity authorise every action an agent can request?

AWS documents workload identities for agents, including automatic creation with AgentCore Runtime or Gateway deployments and explicit creation for custom deployments. An identity can participate in access policies; its existence does not establish permission for every action or the end user’s intent.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does AgentCore memory support establish correct or appropriately retained agent knowledge?

AWS distinguishes short-term memory for interactions within a session from long-term extraction of information across sessions. These are documented memory capabilities. They do not establish the accuracy of retained information or the access, retention and deletion behaviour of a particular application.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does outbound authentication from AgentCore Runtime prove a tool action is permitted?

AWS documents AgentCore Runtime integration with Identity for outbound authentication to services using OAuth or API keys. Authenticating a connection does not establish that the requested operation, resource or delegated scope is permitted for the user’s task.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does AgentCore Runtime tracing prove a complete or correct agent decision?

AWS describes tracing for agent reasoning steps, tool invocations and model interactions in AgentCore Runtime. Trace support makes these interactions inspectable when configured; it does not prove complete capture, correct reasoning or successful enforcement of a deployment’s controls.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What do Google ADK’s machine-readable documentation files provide?

Google ADK documents an llms.txt index and an llms-full.txt documentation export for coding assistants. These provide access to documentation; they do not demonstrate that an assistant has read the current material, generated correct code or validated a deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does ADK’s documentation MCP server deploy or run an application agent?

Google ADK describes a documentation MCP server that lets coding tools search and read ADK documentation. This is a documentation-access integration. It does not itself establish deployment, execution or authorisation of an application agent.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does Microsoft Agent Framework workflow support establish about execution?

Microsoft describes workflows that connect agents and functions through explicit execution paths, with functional and graph-based approaches. This supports structured orchestration. Available features depend on language and version; documentation alone does not verify a particular workflow’s ordering, failure handling or permissions.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does Agent Framework session-state support prove durable or isolated recovery?

Microsoft lists session-state management among Agent Framework’s building blocks for context and memory. That capability does not establish a particular application’s persistence guarantees, cross-user isolation or recovery behaviour. Those depend on the selected implementation and need separate evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

When can Cedar entity slicing preserve an authorisation result?

Cedar documents additional level validation and matching entity slicing to bound the entity data required for authorisation while preserving the result under the stated conditions. This is conditional on the validation and slicing rules; it does not justify arbitrary data pruning or prove a deployed policy is correct.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can a Sigstore signature remain verifiable after its short-lived certificate expires?

Sigstore’s bundle documentation explains how trusted signing-time evidence can support verification after a short-lived signing certificate expires. The verifier must establish signing within the certificate’s validity and apply its trust policy. A timestamp does not by itself establish artifact safety or the truth of signed content.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does citing the OWASP Agent Control Standard establish certified agent safety?

OWASP presents the Agent Control Standard as an open foundation for inspectable, traceable and instrumentable agent behaviour. This describes a control framework’s purpose. Citing or adopting it does not establish certification, complete implementation or tested safety of a particular agent.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does portable agent-control configuration prove middleware enforces it?

OWASP describes the Agent Control Standard in relation to middleware hooks and portable declarative controls. A declared control still needs an integration that applies it at the relevant execution point. Portability of configuration does not prove universal platform support or enforcement in a specific runtime.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does agent identity plus a control declaration prove an action is allowed?

AgentCore identity and outbound authentication identify workloads and connect credentials. ACS describes controls and their middleware integration. Together these documents still do not verify a particular user’s permission, resource scope or observed enforcement. Preserve the actual action and control evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Do memory and workflow features establish reliable recovery for an agent?

AgentCore memory and Microsoft Agent Framework workflow and session features address different parts of application state and execution. None of these documentation references demonstrates a particular deployment’s recovery, isolation or retention behaviour. Verify the configured implementation and failure paths.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a documentation MCP connector provide agent execution and tracing?

ADK’s documentation MCP connector supports reading and searching documentation. AgentCore Runtime documentation describes hosting and tracing capabilities. These are distinct interfaces: connecting the documentation tool does not deploy an agent or establish trace capture for an application.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an isolated agent runtime hide its execution-role credentials from code running inside it?

AWS documents that code inside an AgentCore VM can obtain execution-role credentials through its metadata service, independently of network mode. The role therefore needs permissions limited to the intended operations. Runtime isolation does not establish that code inside the VM cannot use those credentials.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does enabling MMDSv2 and running a non-root container establish that an agent runtime is secure?

AWS requires AgentCore Runtime to use MMDSv2 from 30 June 2026 and recommends non-root users for custom containers. These controls address particular runtime concerns; they do not establish correct role permissions, protected application data or approval for the agent's actions. Deployment settings still require verification.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can I rely on runtime isolation to protect the credentials available to my agent?

Inspect the execution role, credential exposure and configured runtime controls separately. The linked references identify documented boundaries; they do not assess a supplied deployment or grant permission to act.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does a completed advisory-staging run establish before public release?

At the historical staging checkpoint, the supplied report recorded 303,187 projected records from seven source snapshots, with no canonical import or public release and an upstream rights review still pending. Those statements describe that checkpoint, not the present service. A later release needs separate admission and deployment evidence; staging alone does not verify advisory truth.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Do exact-key retrieval checks establish that an advisory answer is true?

The supplied validation report records source-field and stream checks across the staged corpus, with successful exact-key probes and no reported pointer, stream or absent-key false-match failures. These are mechanical retrieval checks. They do not verify advisory truth, general question-answering quality or an affected-version decision for a buyer deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can an experimental anomaly signal approve a vulnerability finding?

The supplied AURIC study completed an archived-anchor experiment without promotion. Its attention candidates do not certify advisory truth, discover new vulnerabilities or authorise corpus admission. The accompanying scope report does not establish calibrated cross-series probabilities. This historical result does not establish current-engine performance or security of a buyer deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a withdrawn advisory mean the package is safe?

In OSV, withdrawn dates the retirement of that advisory entry; its summary can explain why. Withdrawal alone is not a package-safety verdict. Check the publisher explanation and other applicable records before deciding what remains relevant.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Do multiple advisory IDs provide independent confirmation of a vulnerability?

OSV aliases identify the same vulnerability across databases. Counting those IDs as separate confirmations overstates the evidence. Distinguish alias, upstream and related links, and inspect the originating evidence before claiming independent corroboration.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Is a version unaffected if it is missing from an advisory versions list?

OSV allows affected versions to be expressed by enumeration or ranges. Check both using the appropriate ecosystem or commit ordering. fixed, last_affected and limit have different meanings; a missing enumerated version or a range boundary alone must not be turned into a general safety conclusion.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence is needed before using an advisory match for a deployment decision?

Keep advisory status, alias relationships, affected-version interpretation and deployment identity separate. The linked public references explain those checks; the supplied staging example does not evaluate your package, resolve unsupported ranges or authorise a security action.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can successful staging and an anomaly signal replace an evidence-admission review?

This supplied run completed staging and a separately scoped archived experiment while recording no canonical import or model promotion. Mechanical completion and exploratory attention are different evidence states. Publication, source rights and claim validation need their own review.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an API with no published rate limit guarantee unlimited retrieval?

OSV currently documents no API rate limit, but limits HTTP/1.1 responses to 32 MiB and recommends HTTP/2 for large responses. This is a dated description of the upstream service, not an availability guarantee or a limit inherited by other providers. Check the actual endpoint and transport before planning retrieval.

VAREXIS-INDEX Single Request

Relevant public records

What should accompany a CycloneDX not_affected vulnerability assessment?

CycloneDX 1.7 distinguishes not_affected, in_triage, false_positive and resolved analysis states. It recommends justification for not_affected and details explaining why the component or service is not impacted. The analysis can carry issue and update times. A valid status field alone does not establish that its rationale applies to the deployed artifact.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Is advisory withdrawal the same as a component being not affected?

Withdrawal retires an advisory entry; a CycloneDX not_affected assessment concerns a specific vulnerability and component or service, with supporting rationale. Neither label alone demonstrates safety of the deployed package. Preserve the source, affected object, dates and applicability evidence before deciding how an alert should be handled.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a verified ledger chain prove that a backup is complete and recoverable?

The supplied archive review reports a valid 50-entry ledger chain and consistent receipts for 162 selected objects. It does not independently rehash every local copy, inspect the detailed exclusions, verify a second copy or demonstrate a restore. Preserve the distinction between the selected set and the full intended backup. This is an attributed custody-review example, not a backup certificate or scientific promotion.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What should I check before using a hosted agent for two-way audio or message streaming?

AgentCore documents WebSocket and WebRTC support for bidirectional streaming. WebSocket connections support text, structured messages and audio, with SigV4 or OAuth authentication; WebRTC targets real-time media. Select the transport and authentication contract for the actual client. Documented streaming support does not establish measured latency, uninterrupted sessions or successful integration with a particular model.

VAREXIS-INDEX Single Request

Relevant public records

Does a documented multi-agent orchestration pattern mean its SDK implementation is stable?

The Semantic Kernel orchestration page labels its implementation experimental and warns that it may change before preview or release-candidate status. It lists concurrent, sequential, handoff, group-chat and Magentic patterns, while stating that orchestration is unavailable in its Java SDK. Retain the package, language and review date when assessing suitability; a pattern description is not a compatibility or production-readiness guarantee.

VAREXIS-INDEX Single Request

Relevant public records

Is moving from Semantic Kernel to Microsoft Agent Framework a drop-in replacement?

Microsoft provides a migration guide with changes to packages, agent construction, session handling, tool registration and invocation results. The Python and .NET paths have language-specific mappings. Treat these as migration work items and verify the application behaviour after conversion. The successor relationship alone does not demonstrate equivalent outputs, preserved state or improved performance for an existing agent.

VAREXIS-INDEX Single Request

Relevant public records

Can I assume telemetry names and attributes stay unchanged after an instrumentation upgrade?

The OpenTelemetry Telemetry Stability page, currently marked Development, distinguishes unstable from stable instrumentation. Unstable producers offer no telemetry-shape guarantees; additive telemetry is allowed for both classes. The page also retains a moratorium on relying on schema transformations for stability. Check the producer label, version and emitted fields before updating dashboards or alert rules; a Schema URL alone does not demonstrate compatibility.

VAREXIS-INDEX Single Request

Relevant public records

Does reviewing an MCP connection cover the security of the agent skills that use it?

OWASP Agentic Skills Top 10 treats skills as the behaviour and execution layer that coordinates workflows, distinct from the MCP tool-communication layer. An integration review should therefore identify both the exposed tool interface and the instructions and actions the skill orchestrates. This incubator guidance supplies a review perspective; citing it does not certify a skill or demonstrate that its permissions and behaviour are safe.

VAREXIS-INDEX Single Request

Relevant public records

What separate compatibility checks belong in an agent framework upgrade?

Review the framework API and session migration separately from the shape of emitted telemetry. Microsoft documents language-specific migration changes; OpenTelemetry distinguishes telemetry stability contracts. Successful agent calls alone do not establish that historical dashboards and alert queries still work. Preserve package versions and the results of both application and telemetry checks.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does preserving an experiment change the strength of its result?

The custody review concerns ledger continuity and selected archive receipts. The separate D1 and D2 reviews retain their original development and performance limitations. Preserving a result does not rerun it, supply a fresh holdout or remove a failed qualification condition. Keep preservation status and scientific disposition as separate fields.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Where should validation run when an agent hands work to another agent or calls a tool?

OpenAI documents input guardrails on the first agent, output guardrails on the final-output agent, and tool guardrails on the function tools to which they are attached. Review validation at each side-effecting tool boundary; entry and exit checks alone do not cover every intermediate action. This documents control placement, not tested enforcement or protection for every tool type.

VAREXIS-INDEX Single Request

Relevant public records

How should an application continue an agent run after a tool call waits for approval?

The Agents SDK records an approval interruption before the tool executes and returns resumable state. The application resolves the pending approval or rejection, then resumes that state; delayed review can use a stored serialised state. Starting a new user turn is not the documented continuation path. Approval still needs an authorised decision; this reference does not establish idempotent external side effects.

VAREXIS-INDEX Single Request

Relevant public records

What should I check before assuming an agent run has a usable trace?

OpenAI documents tracing enabled by default for the normal server-side Agents SDK path, with model calls, tool calls and outputs, handoffs, guardrails and custom spans. SDK and per-run controls can change capture. Check the actual runtime, configuration and received trace before relying on it. This source does not establish browser or test-runtime defaults, complete capture, retention compliance or correct agent decisions.

VAREXIS-INDEX Single Request

Relevant public records

What remains the application's responsibility when using an agent SDK?

OpenAI describes its Agents SDK as running inside the application: the application owns deployment, tool implementations, state storage and approval decisions, while the SDK runs the agent loop and invokes tools. Treat hosting, persistence and authorisation as explicit application responsibilities. Installing the SDK alone does not establish a deployed service, durable storage or approved tool access.

VAREXIS-INDEX Single Request

Relevant public records

Does an SDK supporting a protocol release make an existing MCP integration a drop-in upgrade?

The MCP 2026-07-28 announcement identifies TypeScript, Python, Go and C# SDK support and Rust support in beta at that release. It also flags migration work, especially for integrations using session identifiers. Pin the package and protocol versions and review the applicable migration notes. A release-support statement does not verify an installed client's compatibility, optional features or successful deployment.

VAREXIS-INDEX Single Request

Relevant public records

Does adding memory or credentials to an agent project mean the cloud resources are already provisioned?

AWS documents that AgentCore CLI add commands update project configuration; a subsequent deploy provisions the resources through AWS CDK. Deployment requires appropriate AWS credentials and permissions. The CLI offers a dry-run preview of changes. Check the target account, region, configuration and deployment result before claiming a capability is available; a generated project or preview is not a successful provision or working integration.

VAREXIS-INDEX Single Request

Relevant public records

Which checks separate validation, approval and observation of an agent tool call?

Attached guardrails validate the covered tool boundary; approval interruptions let the application resolve permission before continuing; tracing records configured events. These serve different purposes. Retain the tool type, attached checks, approval decision, continuation state and received events. None of these documentation references verifies the buyer's enforcement or makes an observed action authorised.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence separates a working agent library from a provisioned service?

The Agents SDK documentation assigns deployment, storage and approval decisions to the application. AgentCore's CLI documentation separately distinguishes project configuration from resource provisioning. Review hosting ownership, target environment and deployment and invocation results before describing a service as available. This comparison supplies a review checklist, not proof that these products were integrated or tested together.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can adding agent middleware change streaming behaviour or leave output unchecked?

Microsoft's .NET Agent Framework guide distinguishes run and streaming middleware. Supplying only the non-streaming handler makes streaming invocations use non-streaming mode. Its shared handler preserves streaming but cannot intercept or override output. Choose the handler for the required input or output check, then test the installed version. This documents API behaviour, not a verified safety control.

VAREXIS-INDEX Single Request

Relevant public records

Where can I connect LLM security risks to an existing control review?

OWASP's 2026 LLM Top 10 describes risk mappings to NIST, MITRE ATLAS, CWE and the Agentic Applications Top 10. Use these references to locate related risks and review questions. A mapping does not show that a control was implemented or effective. Preserve the editions, selected mapping and application evidence separately; this entry does not assess compliance.

VAREXIS-INDEX Single Request

Relevant public records

Does adding newer vulnerability context refresh the underlying advisory evidence?

The supplied S2 review reports enrichment of the existing advisory population with dated KEV and EPSS context, with no new OSV acquisition. The original advisory capture remains 8 October; feed acquisition and score dates are separate. Missing score joins remain unknown. At the initial 11 October review checkpoint the full archive was unavailable, so that review alone did not establish an activated import. The subsequently verified collection and its current import metadata are described at /index-advisories and /varexis-index/advisory-dataset.json; this record preserves the initial supplied-review boundary.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can improved event detection justify promotion when a false-alert requirement fails?

The supplied S2 review reports improved synthetic event recall over independently selected simple comparators, but failure of the frozen false-emission criterion. The detector remains an unpromoted development candidate. Source enrichment was assessed separately, without detector authority over source admission. These are reported results on consumed synthetic cases, not real-incident qualification or an experiment rerun by this intake.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a low false-alert rate per check mean few monitored streams will alert?

The supplied S2 review distinguishes event recall, false emissions per check and the share of negative-control series that emitted at least once. Its reported results show why these denominators cannot be exchanged. Event-matched emissions also use a specific scoring rule and are not real-world precision. Preserve the unit, observation period and matching definition before translating a detector metric into an alert-workload claim.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an EPSS score establish the risk to my deployed asset?

FIRST describes EPSS as the estimated chance of observed exploitation activity for a CVE over the next 30 days. The percentile is its rank among scored vulnerabilities, not that probability. EPSS excludes asset-specific exposure, controls and impact. Use the dated score as one input alongside deployment evidence; it does not establish that your system is affected, compromised or safe.

VAREXIS-INDEX Single Request

Relevant public records

How should a vulnerability workflow retrieve EPSS scores and preserve the decision date?

FIRST recommends its API for individual or small-batch lookups, and daily CSV files for bulk workflows. Historical lookup can pin a score date. Preserve that date and model version: a model change can shift scores without a change in the vulnerability. This documents retrieval choices; VAREXIS does not fetch or refresh EPSS scores through this entry.

VAREXIS-INDEX Single Request

Relevant public records

What should an enriched vulnerability answer preserve before a risk decision?

Retain the base advisory capture, enrichment acquisition, score date and model version as separate facts. The supplied S2 review illustrates missing joins and an import that still needs actual-output verification. FIRST defines how the score should be interpreted and retrieved. Together these sources support a review checklist, not fresh enrichment, verified asset impact or a safety decision.

VAREXIS-INDEX Evidence Receipt

Relevant public records

How should detection gains and alert workload be assessed together?

The supplied S2 review reports improved event recall alongside a failed false-emission gate. Its alert-metric analysis separately distinguishes checks, monitored series and matched events. Keep acceptance criteria and operational counting units visible in the same review. Neither a recall gain nor a favourable denominator establishes a qualified detector or measured human workload savings.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Should agents run in parallel when one task needs another agent's output?

Microsoft's Semantic Kernel guide describes concurrent orchestration as independent processing of a shared task, while sequential orchestration passes each result to the next agent in order. Choose the pattern around the actual data dependency; a later task that needs an earlier result is not independent. These orchestration features are documented as experimental. The pattern description establishes neither application correctness nor a measured speed or cost benefit.

VAREXIS-INDEX Single Request

Relevant public records

How should an agent identify a package version in an OSV query?

OSV's query documentation separates commit queries from package-version queries. Do not combine a commit with a top-level version. Identify a package through its name and ecosystem, or through a package URL. Supply the version either separately or within that URL; supplying both returns a bad-request response. Preserve the actual package identity and case. A valid query does not establish that the identified package is deployed or safe.

VAREXIS-INDEX Single Request

Relevant public records

Does a session-revocation event apply to every session belonging to a user?

OpenID CAEP 1.0 identifies revoked sessions through the event's subject. That subject can specify a session or properties used to locate applicable sessions. For a complex subject, matching uses the claims together. A user, device and tenant combination must therefore not be reduced to a user-only match. This defines the event's scope; it does not prove that a receiver found the right local sessions or enforced revocation.

VAREXIS-INDEX Single Request

Relevant public records

Can a benchmark gain on repeated work support a claim about processing new inputs?

The supplied lineage review keeps an existing result for repeated-work conditions separate from evaluations of new-input processing. Their recorded gains cannot be transferred between the two claims. The review reports no new runtime measurements and uses historical evaluation material; it does not establish fresh holdout performance or customer savings. Before comparing results, require matching workload assumptions, required outputs and cost accounting.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an affected Requests version prove that proxy credentials leaked?

The Requests maintainer advisory for CVE-2023-32681 describes a proxy-credential leak during redirects to HTTPS when credentials are supplied in the proxy URL. It lists versions from 2.3.0 before 2.31.0, with 2.31.0 fixing this issue. A package-version match alone does not establish that those conditions occurred. For an exposure review, check proxy authentication, redirect destinations and actual requests. This historical fix does not establish that a version is free of other vulnerabilities.

VAREXIS-INDEX Single Request

Relevant public records

Why does the urllib3 cookie-redirect advisory list two fix versions?

The urllib3 maintainer advisory for CVE-2023-43804 lists fixes in both the 1.x and 2.x branches: 1.26.17 and 2.0.6. It concerns a supplied Cookie header retained across redirects to another origin. Applicability depends on the affected version, cookies, redirect handling and the connection context described by the advisory. The frozen source splits the branch ranges into separate affected-package records; these are not separate vulnerabilities. Preserve each branch's fix instead of selecting one universal minimum safe version.

VAREXIS-INDEX Single Request

Relevant public records

Does a Log4j name match or a recorded 2.15.0 fix establish deployment safety?

Apache identifies log4j-core as the affected component for CVE-2021-44228; log4j-api alone is not affected by that vulnerability. Its historical fixes include 2.3.1, 2.12.2 and 2.15.0 for different Java branches. Apache separately reports that the 2.15.0 fix was incomplete in certain configurations, tracked under CVE-2021-45046. Therefore a fix event for the first CVE is not general deployment clearance. Identify the actual component, branch and configuration, then review applicable advisories. These historical versions are not current upgrade recommendations.

VAREXIS-INDEX Single Request

Relevant public records

Is checking third-party dependencies enough to assess Go CVE-2024-24790?

The Go vulnerability report GO-2024-2887 concerns net/netip in the standard library. Certain address-classification methods, including IsPrivate and IsLoopback, can misclassify IPv4-mapped IPv6 addresses. The report lists affected toolchains before 1.21.11 and from 1.22.0-0 before 1.22.4. A third-party dependency list alone is insufficient context. Our review implication is to identify the toolchain used to build the deployed binary and whether affected methods process relevant inputs. An affected toolchain match does not prove reachable exploitation.

VAREXIS-INDEX Single Request

Relevant public records

Does upgrading changed-files establish that earlier workflow secrets were not exposed?

The changed-files maintainer advisory describes tags redirected to malicious code during 14-15 March 2025 and secrets exposed through workflow logs. Upgrading does not establish that earlier runs were unaffected. Review execution dates, resolved code and potentially exposed credentials. The maintainer page lists 46.0.0 as patched; the frozen GHSA-mrrh-fwg8-r2c3 projection records 46.0.1 as a fix event. This review preserves that disagreement rather than choosing a universal safe version. Neither source verifies a buyer's runs or credential recovery.

VAREXIS-INDEX Single Request

Relevant public records

Does the lodash 4.17.21 fix also cover lodash.template and lodash-template?

GitHub's reviewed advisory GHSA-35jh-r3h4-6jhm lists lodash before 4.17.21 as affected by CVE-2021-23337, with 4.17.21 patched. It separately lists lodash.template through 4.5.0 and lodash-template through 1.0.0 without a patched version. Those package names must not inherit lodash's fix by similarity. Retain the exact npm package and its own source range. No patch listed is a statement about this record, not proof that remediation is impossible or that the application is exploitable.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assess middleware authorization bypass from a Next.js version alone?

For CVE-2025-29927, the Next.js maintainer identifies authorization checks performed in middleware as the relevant condition and states that Vercel-hosted deployments are protected against this issue. The frozen records retain branch-specific fixes: 12.3.5, 13.5.9, 14.2.25 and 15.2.3. The maintainer also discusses 11.x, which the frozen 12.x range does not cover. Check where authorization is enforced and how requests reach the deployment. Neither a package match nor this hosting statement establishes overall application security; these are historical issue-specific fixes.

VAREXIS-INDEX Single Request

Relevant public records

Does configuring a base URL stop an agent's HTTP tool from contacting other hosts?

The Axios advisory for CVE-2025-27152 describes supplied absolute URLs overriding the configured base URL, potentially forwarding credentials or reaching unintended destinations. Review caller control over the URL and attached credentials; a base URL alone is not a destination restriction. The maintainer lists affected versions through 1.7.9 and 0.29.0, while the frozen ranges extend to the exclusive fixes 1.8.2 and 0.30.0. Preserve that range difference. This review establishes neither the destination controls of a buyer's tool nor a currently safe Axios version.

VAREXIS-INDEX Single Request

Relevant public records

Do file-upload limits alone cover the Starlette multipart denial-of-service advisory?

Starlette's CVE-2024-47874 advisory concerns multipart parts without a filename, which are buffered as text fields. File-upload controls alone therefore do not address the described path. The maintainer also warns that concurrent requests can cause disruption despite reverse-proxy request limits. Review form parsing, text-field limits and concurrency. The maintainer's affected field says below 0.39.2, while the frozen record extends to the shared fix boundary 0.40.0. That discrepancy remains unresolved here; neither record measures a buyer's available capacity or resistance to denial of service.

VAREXIS-INDEX Single Request

Relevant public records

Does a Jinja sandbox establish that agent-supplied templates are safe to execute?

The Jinja maintainer advisory for CVE-2025-27516 requires attacker control of template content and describes an attribute-filter path around sandbox handling. Supplying data to a fixed trusted template does not by itself establish that condition. Review who authors the template and which environment executes it. The frozen source records 3.1.6 as a fix, while the maintainer page's patched-version field lists none. Preserve that difference; an empty patch field does not prove no fix exists. A sandbox label alone is not evidence that arbitrary generated templates are safe.

VAREXIS-INDEX Single Request

Relevant public records

Is enabling every supported JWT algorithm safe for an agent's token-verification helper?

PyJWT's CVE-2022-29217 advisory describes confusion between asymmetric public keys and symmetric verification when incompatible algorithms are accepted. It recommends explicitly selecting the expected algorithms. The frozen source covers versions from 1.5.0 before 2.4.0; the maintainer lists 2.4.0 as patched. For a verification helper, review the accepted algorithm set and intended key type together, including defaults introduced by wrappers. A token decoding successfully is not evidence of correct signature policy or application authorization. The historical patch does not validate a buyer's configuration.

VAREXIS-INDEX Single Request

Relevant public records

Can a missing JWT verification key change how an unsigned token is handled?

The jsonwebtoken advisory for CVE-2022-23540 identifies three combined conditions in versions through 8.5.1: an unsigned token, no specified algorithms and a falsy verification key or secret. Under those conditions, verification can default to the none algorithm. The maintainer lists 9.0.0 as removing that default. Review missing-key handling and algorithm selection together rather than assuming one matching condition proves bypass. This is a historical library behaviour review, not verification of an application's authentication or of every issue fixed in a major upgrade.

VAREXIS-INDEX Single Request

Relevant public records

Does an agent using aiohttp only as an HTTP client match the static-file traversal conditions?

The aiohttp advisory for CVE-2024-23334 concerns web-server static routes configured with follow_symlinks enabled. It says traversal can occur even without actual symlinks. Client-only use does not establish those server conditions. Review registered static routes and configuration, not just package presence. The maintainer lists 3.9.2 as patched and still advises against enabling this option for remotely accessible production serving. The maintainer's lower-bound field and frozen range differ at 1.0.5; do not infer safety for that boundary version from this review.

VAREXIS-INDEX Single Request

Relevant public records

Does accepting image uploads establish the input conditions of Pillow CVE-2023-50447?

Pillow's 10.2.0 release notes identify attacker control over environment argument keys passed to ImageMath.eval as the relevant condition for CVE-2023-50447. They describe restrictions added to those keys, and the frozen advisory records 10.2.0 as the fix. Merely accepting image uploads does not show that the application calls this evaluator or lets users choose those keys. Review the called API and input mapping. This historical change is not a general guarantee for untrusted expressions, image parsing or a buyer's processing pipeline.

VAREXIS-INDEX Single Request

Relevant public records

How can an agent review repository access without enabling GitHub MCP writes?

GitHub documents a read-only server mode that removes write tools and a separate choice of toolsets. Review both the credential's repository access and the configured server mode. Lockdown is a content filter with stated limitations. This profile helps scope a repository-review connection; it does not verify your token, server configuration or resistance to prompt injection.

VAREXIS-INDEX Single Request

Relevant public records

Does a GitLab MCP tool listing establish permission to change a project?

GitLab documents separate tool discovery and per-call project permissions. Its tool reference includes both reading project data and changing work items, merge requests or files. Some tool availability depends on release, licensing and enabled features. Before approving a task, establish the actual instance, authenticated identity and project rights. A listed tool is not evidence of authorization for a particular change.

VAREXIS-INDEX Single Request

Relevant public records

How should an agent check whether an Atlassian connector can search documents without changing them?

Atlassian documents organization controls for reading, writing and searching, alongside tool-specific scopes for Jira and Confluence. Its supported-tools page includes mutations, so a search use case does not make the entire connector read-only. Check the relevant app permissions and whether future permissions inherit an allow decision. This record does not inspect your organization's settings.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assume Notion content stays inside Notion when using its MCP connector?

Notion documents a hosted OAuth connector that can read and update accessible content. Its security guidance explicitly warns that connected clients may send returned content outside Notion. Check the client and model data policy as well as workspace access. The connector's publisher and valid login do not establish a no-egress or no-training guarantee.

VAREXIS-INDEX Single Request

Relevant public records

What should an agent check before using Linear MCP across more than one workspace?

Linear documents a separate authentication context for each workspace; reconnecting alone does not switch an existing session's workspace. Its MCP supports OAuth and direct tokens, including a restricted read-only API key. Check the active workspace, actor and granted scopes before posting or updating work. This profile does not verify your current session.

VAREXIS-INDEX Single Request

Relevant public records

What should an agent check before sending project error data through Sentry MCP?

Sentry documents organization- or project-scoped connections for its remote MCP, with project scope recommended where possible. Its toolkit describes debugging workflows and notes that AI-powered search in self-hosted setup requires a configured model provider. Identify the deployment, enabled tools and model route before transferring sensitive event context. The public connection page and repository differ in their description of authentication options.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting Stripe MCP authorize an agent to refund or change a live account?

Stripe documents broad API read and write tools, with OAuth for interactive use and permission-scoped Agent Keys for autonomous access. A connection is not approval for a particular financial action. Check the account, live or sandbox environment, permissions and approval rules. The documentation announces an MCP key-acceptance change on 31 October 2026; this dated review does not test that future behaviour.

VAREXIS-INDEX Single Request

Relevant public records

Does a small Cloudflare MCP tool list imply narrow account permissions?

Cloudflare's API MCP uses search and execute operations to reach a broad API surface. A small visible tool list therefore does not establish narrow authority. Check OAuth grants or API-token permissions and the intended account resources. The docs and repository describe different tool totals; this record preserves that ambiguity rather than using a count as a security claim.

VAREXIS-INDEX Single Request

Relevant public records

What should an agent check before connecting a database project to Supabase MCP?

Supabase documents project scoping, read-only mode and feature-group restrictions. Its guidance identifies developer permissions and warns about untrusted database content. Review those controls and the actual data requested before connecting a sensitive project. A confirmation prompt or read-only query does not establish that returned data is suitable for the client or model receiving it.

VAREXIS-INDEX Single Request

Relevant public records

Does an isolated Playwright MCP browser session prevent privileged web actions or data disclosure?

Playwright MCP documents persistent, isolated and existing-browser session modes. Isolation concerns session state; it does not make authenticated web actions read-only. Its origin filters explicitly exclude redirects from their protection, and the project states that MCP itself is not a security boundary. Review browser identity, destinations and task authorization separately.

VAREXIS-INDEX Single Request

Relevant public records

What should an agent check before searching private Slack content without posting messages?

Slack documents separate user-token scopes for searches, conversation history and posting. Review the authorized workspace, requested content and client data handling before retrieval. A search permission does not authorize sending a message, and connecting Slack to another tool creates a separate disclosure decision. This record reviews the official server, not Slackbot's connections to third-party servers.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assume every Asana MCP change has a confirmation step or a read-only scope?

Asana's V2 reference distinguishes direct write tools from interactive preview tools. MCP authorization covers available tools without granular permission scopes, within the user's permissions and the selected workspace. Separate workspaces require separate sessions. Confirm the client, workspace and selected tool before a change; a preview interface is not a universal property of every write path.

VAREXIS-INDEX Single Request

Relevant public records

What should an agent check before treating a CRM connector's search results as complete or allowing publication?

HubSpot's hosted MCP can read CRM content and perform permitted updates, including some publishing actions. Access depends on the user, subscription, granted tools and account configuration. With Sensitive Data enabled, the documented MCP restrictions block activity and conversation data. Missing results therefore do not establish that no records exist. New scopes require a renewed installation grant.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent treat a design connector as read-only when it can also capture UI and write to canvas?

Figma's remote MCP documents both design-context retrieval and canvas-changing workflows. OAuth sign-in and an eligible client are required; capabilities and file actions depend on the tool and access rights. Capturing an application UI sends information into Figma, while retrieving a design supplies context to the client. Those are different data-transfer decisions.

VAREXIS-INDEX Single Request

Relevant public records

What should an agent verify before using a deployment connector to inspect or change a team's project?

Vercel documents a separate sign-in and team-authorization step after adding its MCP server. Existing Vercel permissions still apply. Tools cover project and deployment inspection as well as operational changes, so a diagnosis request should not silently become a deployment or account change. Review the target team, project and environment, and the handling of returned logs.

VAREXIS-INDEX Single Request

Relevant public records

Do old MCP-specific deny actions still establish a read-only boundary for an AWS agent?

AWS's current managed MCP documentation says downstream services apply the caller's IAM permissions. It explicitly marks the earlier MCP-specific IAM actions as ineffective and describes condition keys for distinguishing MCP-originated calls. OAuth through AWS Sign-in is also documented alongside the signed-request path. A historical policy name alone does not prove the current connection is restricted.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assume a locally running cloud connector is isolated from production or has limited authority?

Microsoft documents Azure MCP access through Entra identities and Azure RBAC. A local process can still act with the developer's cloud permissions. Remote self-hosted deployments require protection of both the caller boundary and the server's execution identity. Microsoft explicitly excludes production data and credentials from its local-server guidance; this review does not verify a deployed gateway or role assignment.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent treat an observability connector's returned trace as complete or assume it cannot change monitoring?

Datadog documents role and organization controls for MCP reads and writes, plus resource-specific permissions. Its tool reference warns that a large trace may be truncated without a way to retrieve every span. Incident details also omit timeline data. Treat those limits as coverage boundaries when investigating an outage; an incomplete response is not a complete incident record.

VAREXIS-INDEX Single Request

Relevant public records

Does a read-only monitoring connector prevent every database query or disclosure?

Grafana's MCP repository separates disabling writes from disabling queries. Read-only mode removes raw SQL query tools unless explicitly re-enabled, while other queries can remain. Query-free mode removes query tools but is not a universal block on every datasource path. Credential and datasource privileges still need inspection. A read-only label therefore does not establish a no-query or no-disclosure boundary.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assume a shared search connector isolates each user's permissions and project data?

Elastic distinguishes shared API-key identity from per-user OAuth connections, with OAuth documented for Serverless projects. MCP access also depends on the Kibana space in the endpoint and its cross-project search scope. Restrict keys to intended indices and application privileges; a successful connection is not proof of per-user isolation or single-project coverage.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting successfully prove that an MCP client used the required protocol version?

The TypeScript SDK v2 guide documents a legacy default, automatic discovery with legacy fallback, and an explicit version pin that rejects an incompatible server. Successful automatic connection therefore does not prove use of the newer protocol. Check the negotiated mode and required features. This is documented client behaviour, not a test of your installed client or server.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent use an ADK feature matrix as proof that a feature is supported in its chosen language?

The ADK repository warns that its feature matrix is AI-generated from documentation examples and may be inaccurate. The reviewed table covers Python and Java; it is not a complete inventory of every ADK runtime. Use it as a pointer, then check the feature-specific documentation and installed package. A language listing or missing example does not establish feature parity or absence.

VAREXIS-INDEX Single Request

Relevant public records

Does citing the NIST critical-infrastructure AI profile establish that a supplier completed a readiness assessment?

The reviewed NIST project page describes an ongoing effort to develop a critical-infrastructure AI RMF profile and links a concept note. It describes intended guidance, not a completed supplier assessment. Preserve the document stage and date alongside evidence of the controls actually implemented. A reference to this project does not establish certification, a finished checklist or deployment approval.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent inspect MongoDB without receiving permission to change data or clusters?

MongoDB documents a read-only MCP mode and recommends a separate read-only database identity. Write operations are otherwise enabled by default. Review both layers and any Atlas tools: selecting a safer tool set does not establish the effective permissions of an existing connection.

VAREXIS-INDEX Single Request

Relevant public records

Which Postman MCP configuration fits API discovery without granting unnecessary workspace changes?

Postman documents separate tool configurations and local or remote servers. Minimal is a smaller tool set, not a stated read-only guarantee. US remote authentication supports OAuth; the EU remote and local variants use an API key. Match the region, identity and specific tools to the task before connecting.

VAREXIS-INDEX Single Request

Relevant public records

Does permission to connect to Snowflake MCP also authorize every configured data tool?

Snowflake distinguishes access to the MCP server from privileges on its underlying tools and data. OAuth configuration and the effective role matter. Search, analyst, agent and custom-function tools can require different grants; successful tool discovery is not evidence that every invocation is authorized or read-only.

VAREXIS-INDEX Single Request

Relevant public records

Can a retrieval agent search Qdrant without adding persistent memories?

The official Qdrant MCP server separates finding stored information from storing new information. Its read-only option disables the store tool. Review the collection, database credential and deployment transport separately; a retrieval setting does not establish who can reach a remotely exposed server.

VAREXIS-INDEX Single Request

Relevant public records

Can I give an agent Pinecone documentation access without exposing project data or index writes?

Pinecone Developer MCP can search documentation without a project API key. A configured key enables project interactions including supported index creation, upserts and searches. The reviewed server supports integrated-inference indexes; it should not be represented as universal access to every Pinecone product.

VAREXIS-INDEX Single Request

Relevant public records

What evidence separates an analytical ClickHouse MCP session from one that may alter data?

The ClickHouse MCP documentation describes read-only queries by default, an explicit write-access opt-in and an additional destructive-operation control. Database restrictions still apply. Review the effective settings and whether embedded chDB is enabled before making a claim about the session boundary.

VAREXIS-INDEX Single Request

Relevant public records

What should I check before a Zapier agent can discover tools and take actions across connected apps?

Zapier MCP uses connected-app actions and can discover and enable tools during a conversation. A fixed tool list is an alternative. Review the discovery mode, app identities and authorization for each destination; successful calls also consume the existing Zapier task allowance.

VAREXIS-INDEX Single Request

Relevant public records

Does removing a Docker MCP server also revoke its credentials and eliminate its previous access?

Docker documents profile-based server selection, explicit filesystem mounts and credential management. Removing a server does not itself remove its stored credentials. Container packaging and catalogue checks are useful evidence, but do not establish the permissions or safety of every tool in a selected profile.

VAREXIS-INDEX Single Request

Relevant public records

Can a shopping agent prepare a Shopify cart without committing the buyer to payment?

Shopify separates Cart MCP from Checkout MCP. Cart tools can create, read, replace and cancel a pre-checkout cart using unauthenticated requests with agent-profile metadata. Checkout has a separate authentication boundary. Older Storefront cart tools were removed; a cart or estimated total is not proof of payment.

VAREXIS-INDEX Single Request

Relevant public records

What prevents a Redis agent from changing session memory while performing a read task?

The Redis MCP server exposes both retrieval and state-changing tools. Its documentation points to Redis ACLs for database restrictions. Identify the database user, command scope and permitted keys; having a memory interface does not make the session read-only or establish a retention policy.

VAREXIS-INDEX Single Request

Relevant public records

Does a GitHub audit export establish a complete history of repository activity?

GitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.

VAREXIS-INDEX Single Request

Relevant public records

Does a Slack workspace export contain private channels, direct messages and the files themselves?

Slack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.

VAREXIS-INDEX Single Request

Relevant public records

Does Notion AI not training on customer data mean no provider retains any of it?

Notion states that customer data is not used for model training by default. Retention is a separate, plan- and feature-dependent claim, with explicit exceptions for some AI features and External Agents. Treat training, provider retention and deletion of other stored representations as distinct questions; the reviewed documentation does not verify a particular workspace.

VAREXIS-INDEX Single Request

Relevant public records

Can Figma AI be enabled while our team content is excluded from model training?

Figma documents separate controls for AI feature access and content training. Training defaults depend on plan, and switching training off applies to new content and edits. Verify the actual team or organization setting; neither a paid plan nor an AI-enabled interface alone proves the training choice.

VAREXIS-INDEX Single Request

Relevant public records

Does pinning an Atlassian app to a region keep every account, integration and AI data flow there?

Atlassian Cloud residency applies to defined in-scope app data. The documentation lists exclusions and treats Marketplace app data separately. A pinned product location therefore does not establish that every account record, log, integration or AI-related flow stays in that region. Identify the app and data category before relying on the claim.

VAREXIS-INDEX Single Request

Relevant public records

Does a Supabase database backup also recover the uploaded files used by my application?

Supabase documents that database backups contain Storage metadata, not the stored object contents. Restoring a database backup does not recover objects deleted afterwards. A whole-application recovery claim needs separate evidence for files and other dependencies, together with the actual backup configuration and a suitable restore check.

VAREXIS-INDEX Single Request

Relevant public records

Does having Vercel deployment logs mean our plan provides administrative audit evidence?

Vercel documents Audit Logs as an Enterprise feature accessible to team owners. Its event catalogue and export or streaming path need their own review. Deployment output is not equivalent to an administrative activity trail, and the availability of an audit feature does not demonstrate successful capture in the buyer account.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Linear SCIM prove every former user and integration has lost access?

Linear documents SCIM provisioning and suspension driven by the identity provider, including group mapping and exceptions requiring attention. Disabling SCIM stops synchronization; changes may need to be pushed again after re-enablement. A supported feature is not proof of complete offboarding across users, guests and independent integration credentials.

VAREXIS-INDEX Single Request

Relevant public records

Does receiving a Stripe webhook prove that payment was verified and fulfilled exactly once?

Stripe documents signature verification, possible duplicate deliveries and no guaranteed event ordering. Receiving a webhook or returning a successful response does not by itself prove a matching payment entitlement or completed fulfilment. Review authenticity, object state and the application processing record separately.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Cloudflare Logpush provide a complete searchable archive of past activity?

Cloudflare describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.

VAREXIS-INDEX Single Request

Relevant public records

What evidence should I collect before connecting an agent to business databases?

Start with the named database identity, allowed data and commands, server variant and client recipients. MongoDB, Redis, ClickHouse, Snowflake, Qdrant and Pinecone expose different read/write boundaries. These profiles identify the questions to resolve; they do not inspect a live connection or authorize access.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence separates no-training, retention and regional-hosting claims?

Treat training use, retention and regional scope as separate claims. The Notion, Figma and Atlassian reviews identify plan, feature and data-category qualifications. Confirm the buyer configuration and applicable agreement before relying on a broader statement. This route preserves published evidence; it does not decide compliance.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What makes a supplier audit or export record sufficient for a claimed activity history?

Check event and conversation coverage, plan entitlement, collection method, time interval and retained destination. GitHub, Slack, Vercel and Cloudflare document different limits. Missing records cannot be interpreted as no activity without coverage evidence. A saved route retains these limitations; it does not reconstruct missing history.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What distinguishes preparation, authorized action and verified payment in an agent workflow?

A discovered tool is not task authorization; a prepared cart is not a completed purchase; and a received webhook is not proof of verified entitlement or fulfilment. Use the Zapier, Docker, Shopify and Stripe reviews to record each boundary, intended recipient and missing operational evidence before acting.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can I let an agent discover Apify Actors without authorizing paid execution or storage access?

Apify separates unauthenticated discovery tools from authenticated Actor execution and access to run data. Select the tools and Actors needed for the task, then check account authority and spending limits before execution. Discovering an Actor does not establish permission to collect its target data.

VAREXIS-INDEX Single Request

Relevant public records

Does a Firecrawl search connection also allow browser interactions or saved login state?

Firecrawl documents different hosted tool sets. Its full interface includes interaction tools that can click, type and preserve browser state, while a dedicated search-only endpoint has a restricted tool set. Review the actual endpoint and exposed tools before treating a connection as retrieval only.

VAREXIS-INDEX Single Request

Relevant public records

Does signing in to Tavily MCP prove that queries use the intended team API key?

Tavily documents a key-selection order for remote OAuth connections, including a named default and personal-versus-team precedence. Login alone therefore does not demonstrate the intended billing identity. Check the selected key and account before sending work queries; session attribution is separate from user authorization.

VAREXIS-INDEX Single Request

Relevant public records

Can adding Exa authentication expose billable research beyond keyless search?

Exa documents keyless rate-limited access and authenticated modes. The authenticated default tool set includes a usage-billed research operation, while explicit tool selection replaces the defaults. Check the exposed tools and spending authority after connecting credentials; a successful search does not authorize a broader research run.

VAREXIS-INDEX Single Request

Relevant public records

Can I assume a Brave Search MCP response is a complete local-business or factual answer?

Brave documents separate search and summary tools, with plan-dependent local capabilities and a web-search fallback. Record the result type and account entitlement before relying on a local query. A generated summary or returned search page is supporting material, not independent verification of the underlying claim.

VAREXIS-INDEX Single Request

Relevant public records

Can Browserbase MCP use a logged-in browser session to make changes on a website?

Browserbase documents cloud sessions that can retain authentication state and perform navigation, clicks, typing and form actions. Treat the session identity and target website as part of the permission review. Read access to a page does not establish authority to submit a form or make a purchase.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting to n8n MCP only let an agent run a fixed workflow?

The reviewed n8n documentation includes workflow search, execution and authoring. Search previews and full workflow access have different boundaries; OAuth grants and workflow exposure also matter. Check the installed version and execution mode before granting access, because a workflow can call connected services using its configured credentials.

VAREXIS-INDEX Single Request

Relevant public records

Does installing Semgrep MCP prove every agent code change was scanned?

Semgrep distinguishes callable MCP scanning tools from event-triggered hooks. Tool availability alone does not prove invocation or coverage of a particular revision. Its former standalone MCP repository is archived and points to the main Semgrep distribution, so verify the installed integration and retain actual scan evidence.

VAREXIS-INDEX Single Request

Relevant public records

Can a Snyk dependency scan execute project tooling, even when the task is only a security review?

Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.

VAREXIS-INDEX Single Request

Relevant public records

Can I connect PagerDuty MCP for incident review without granting authority to change operations?

PagerDuty documents read and management tools on its hosted MCP service. Authentication scopes constrain successful calls, while hosted tool filtering is not available. Check the regional endpoint, key type and granted scopes before connecting; incident visibility does not authorize changing schedules, services or incident state.

VAREXIS-INDEX Single Request

Relevant public records

Does a pull-request workflow prove external contributions cannot access privileged execution?

GitHub warns that privileged workflow triggers combined with untrusted checkout can expose secrets or repository write access. Review triggers, checked-out revisions and job permissions together. A pull-request label or successful workflow run does not establish an isolated execution boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does a GitLab job-token allowlist grant the pipeline user access to another project?

GitLab states that adding a project to the job-token allowlist does not grant extra permissions to its members. Access also depends on the triggering user and allowed token capabilities. Review both the source-project allowlist and the effective identity before accepting a cross-project access claim.

VAREXIS-INDEX Single Request

Relevant public records

Does excluding a Datadog log from an index mean it was deleted or never collected?

Datadog documents that index-excluded logs can still reach Live Tail, metrics and archives. Exclusion controls searchable indexing rather than proving deletion from every destination. Check the complete configured route before relying on a no-retention or no-event claim.

VAREXIS-INDEX Single Request

Relevant public records

Does one restrictive Elasticsearch role prove a user cannot read other documents or fields?

Elastic documents that permissions from multiple roles can combine to broaden access to the same index. A role without the relevant restriction can defeat the intended document or field limit. Review the complete role assignment, not one restrictive role in isolation.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Sentry server-side scrubbing prove sensitive data never left the application or was removed historically?

Sentry describes server-side scrubbing and states that new advanced rules apply to incoming events. Its JavaScript attachment guidance provides a pre-send handling point. These controls do not by themselves prove that sensitive data never left the application or that older stored material was removed.

VAREXIS-INDEX Single Request

Relevant public records

Are OAuth scopes alone sufficient evidence of the authority granted to an Okta service app?

Okta documents both scope grants and administrative role assignments for service apps. Roles constrain permissions and resources; an organization setting can also automatically assign a broad administrative role. Review the app grants, roles and organization settings together before claiming least-privilege access.

VAREXIS-INDEX Single Request

Relevant public records

Does an empty Auth0 tenant-log search establish that no authentication event occurred?

Auth0 documents plan-dependent retention and possible indexing delay. A query result needs a time-range, plan and collection check before it supports an absence claim. Longer history requires evidence of an external logging arrangement; the feature description does not establish that one was operating.

VAREXIS-INDEX Single Request

Relevant public records

Does giving an agent a 1Password service account restrict it to the intended secrets?

1Password describes service accounts with selected vaults, Environments and permitted actions, independent of an individual identity. Effective secret access depends on those choices. Check the configured scope and usage evidence before assuming a token exposes only the secrets needed for the task.

VAREXIS-INDEX Single Request

Relevant public records

Does a Microsoft Graph permission name mean the same access with and without a signed-in user?

Microsoft distinguishes delegated access on behalf of a user from application access under the app identity. Delegated permissions are bounded by the access of that user, while application permissions can reach data without a user present. Review the permission type, consent and resource controls before judging the scope from its name.

VAREXIS-INDEX Single Request

Relevant public records

Does Google Workspace domain-wide delegation give a service account unlimited direct access to user data?

Google describes domain-wide delegation as authority to impersonate a specified user for API calls, bounded by authorized OAuth scopes and the permissions of that user. Review the delegated client, scopes and selected user. Approval to delegate is distinct from permission for every proposed collection or action.

VAREXIS-INDEX Single Request

Relevant public records

What should I verify before an agent uses paid web research tools?

Check the exposed tool set, billing identity, approved budget and data being sent. Apify, Firecrawl, Tavily, Exa and Brave expose different discovery, retrieval and execution boundaries. An authenticated connection is not approval for every available operation. These reviews preserve documentation limits without claiming to verify returned web content.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What separates tool availability from permission and proof of execution?

Browser sessions, workflows, security scanners and incident tools can cross different action boundaries. Review the affected identity, approved operation and actual execution evidence. Installing or exposing a tool does not prove it was used, and a completed call does not establish that the task was authorized or the result complete.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can missing logs or an enabled scrubber prove no data exposure?

Separate collection, indexing, retention, scrubbing and historical removal. Datadog, Sentry and Auth0 document different boundaries. A missing search result or enabled control does not by itself establish that no event occurred or that sensitive information was never transmitted. Request dated configuration and coverage evidence for the claim.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence establishes the actual data access of a service identity?

Review all relevant grants, roles, resource limits and acting identities together. GitLab, Elasticsearch, Okta, 1Password, Microsoft Graph and Google Workspace use different combinations. A scope name, allowlist or restrictive role alone may not establish effective access. These reviews identify buyer evidence to collect before approval.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can an agent update my Airtable records without activating an automation?

Airtable documents record editing through MCP within the permissions of the connected user. Automation changes are saved as drafts and activation happens in the Airtable interface. Record-write access and permission to activate an automation are separate review questions; verify the selected bases, granted scopes and intended operation.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting Box MCP give my agent only document-search access?

The documented Box MCP tool set includes content reads and writes. Some sharing and move operations are disabled by default until an administrator enables them. Review enabled tools, OAuth scopes and existing user permissions together before calling the connection read-only.

VAREXIS-INDEX Single Request

Relevant public records

Can my agent use a Miro board from a different team after one connection?

Miro documents a team-specific OAuth connection and existing board-access controls. Its tools can read and change board content, so a request to summarise a board should identify both the authorised team and allowed actions. Enterprise availability also depends on administrative enablement.

VAREXIS-INDEX Single Request

Relevant public records

Can a monday.com agent connection do more than read task boards?

The Platform MCP exposes board operations and broader GraphQL queries and mutations, with calls tied to the authenticated user. Tool availability is therefore wider than task lookup. Confirm token permissions, permitted actions and the target board; distinguish this connection from the separate app-development MCP.

VAREXIS-INDEX Single Request

Relevant public records

Does keeping the Webflow Designer closed stop an agent from changing my site?

Webflow documents that most MCP operations use its Data API without an open Designer. Only some live-session capabilities need the Bridge App. The server can change site content and design within existing permissions, so closing the Designer is not evidence of a read-only connection.

VAREXIS-INDEX Single Request

Relevant public records

Can one Canva MCP authorisation stand in for every user of an AI application?

Canva requires individual user authentication, and operations follow the access that user has to designs and assets. The server supports creation, editing, export and collaboration, with some features depending on plan. An application connection alone does not establish entitlement for another user or permission to export a design.

VAREXIS-INDEX Single Request

Relevant public records

Can an Intercom agent add a note when I only asked it to inspect a conversation?

Current Intercom documentation includes internal-note and article writes alongside conversation and contact reads. A note can affect conversation state. The service documents US and EU endpoints, with AU unsupported at review. Confirm the workspace region, consented permissions and exact task before allowing writes.

VAREXIS-INDEX Single Request

Relevant public records

How can I review a feature-flag agent without granting broad change authority?

The local LaunchDarkly MCP uses an API access token. Its documentation recommends both a read-only token role and read scope for a read-only setup, and supports selecting tools. Review the token, environment and enabled operations together; a flag change can affect application behaviour even without a new deployment.

VAREXIS-INDEX Single Request

Relevant public records

Does creating a Sanity release through MCP schedule its publication?

Sanity documents that creating a release records metadata but does not schedule it. Document patching saves drafts or release versions, while separate tools can publish documents. Agents should distinguish a saved draft, a release record and actual publication evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does adding Netlify MCP only give my agent deployment guidance?

Netlify describes MCP capabilities for creating and deploying projects, managing resources and changing configuration. The local package can use the API and CLI; current docs also distinguish a remote server. Review the chosen variant, credentials and permitted resources before treating the connection as guidance-only.

VAREXIS-INDEX Single Request

Relevant public records

Does an empty CloudTrail event history prove no application data was accessed?

AWS distinguishes management events from data events. Default trail and event-store coverage does not include data events, and Event history is not a data-event search. A conclusion about application data access needs evidence of the relevant event category, resource selectors, period and destination.

VAREXIS-INDEX Single Request

Relevant public records

Does the Azure Activity Log show everything an application did inside a resource?

Microsoft describes Activity Log as control-plane evidence and resource logs as the place for data-plane operations. Activity Log has a default retention window; diagnostic routing can retain entries elsewhere. Buyers should establish the required operation and destination instead of treating one activity view as a complete application history.

VAREXIS-INDEX Single Request

Relevant public records

Can a missing Google Cloud Data Access result mean the event was never logged?

Google documents that Data Access logging usually needs explicit enablement, with service-specific exceptions including parts of BigQuery. Viewing those logs also needs appropriate permissions. Check service settings, inherited configuration, exemptions and viewer access before interpreting an empty result.

VAREXIS-INDEX Single Request

Relevant public records

Does buying an audit licence preserve every existing Microsoft 365 audit record for longer?

Microsoft ties audit retention to licensing, record coverage and policy priority. Custom policies can override defaults, and later changes do not update previously committed audit items. Verify the applicable identity, record type and policy at ingestion before claiming a complete extended history.

VAREXIS-INDEX Single Request

Relevant public records

Does a working Vault server prove its secret-access audit trail is complete?

Vault distinguishes operational logs from audit devices, which must be enabled on a new cluster. With auditing enabled, a request requires a successful write to at least one enabled device; one device need not contain the whole history. Documented endpoint exceptions and hashed values also limit interpretation.

VAREXIS-INDEX Single Request

Relevant public records

Does an Anthropic API retention statement apply to every feature and model?

Anthropic describes a standard API deletion period with exceptions for features such as stored files, agreements, policy enforcement and legal obligations. Designated covered models have additional retention conditions, with eligibility exceptions described separately. Confirm the exact product, model, workspace and agreement before accepting an unconditional zero-retention claim.

VAREXIS-INDEX Single Request

Relevant public records

Can Bedrock invocation logging retain prompts even when I only want operational diagnostics?

AWS documents optional invocation logging that can collect supported request/response content and metadata into configured CloudWatch Logs or S3 destinations. Coverage depends on the endpoint and operation. Logging settings therefore need their own review; neither enabled logging nor absent logs establishes universal capture or zero retention.

VAREXIS-INDEX Single Request

Relevant public records

Does a Dropbox storage region prove every data category stays in that region?

Dropbox states that the selected server location applies to team file data permanently stored at rest. Migration has eligibility conditions and needs confirmation. That statement alone does not establish the location of every metadata, processing or connected-application flow.

VAREXIS-INDEX Single Request

Relevant public records

Does sending a Box link only to a colleague keep the linked file private?

Box documents different shared-link audiences and recipient actions. The access setting controls who can use the link; editing, viewing and downloading are separate choices constrained by administrators. The people receiving the message are not sufficient evidence of the effective link audience.

VAREXIS-INDEX Single Request

Relevant public records

Does a restricted Twilio API key make an agent communication task read-only?

Twilio Restricted API keys select permissions that map to endpoint actions. A restricted key can still permit creating calls or other state-changing operations. The feature also has SDK-token limitations. Review the actual permission mapping and task authority instead of treating the word restricted as a read-only guarantee.

VAREXIS-INDEX Single Request

Relevant public records

Can a collaboration assistant read information without changing or sharing it?

Review the acting identity, selected workspace and enabled actions before approving a collaboration connector. Airtable, Box, Miro, monday.com and Intercom expose different write and sharing boundaries. A request to search or summarise does not by itself approve editing, notifications or internal notes. Save the documented capability limits and collect configuration evidence separately.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What proves an agent prepared, exported or published content?

Distinguish the requested state from the operation actually completed. Webflow, Canva, LaunchDarkly, Sanity and Netlify expose different editing, export and operational actions. A saved draft, release record, local connector or closed editor does not establish the same boundary. Require the intended destination and task authority, then inspect outcome evidence before reporting completion.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What makes an audit-history claim complete enough to review?

Establish the event category, capture period, viewer access, destination and applicable retention. CloudTrail, Azure Monitor, Google Cloud, Purview and Vault document different boundaries. A product being enabled or an empty search result is insufficient by itself. These records help a buyer request the missing evidence; they do not inspect or certify the buyer logs.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What should I verify before sending data to an automated service?

Separate retention terms, customer-configured logging, storage-region scope, link audience and credential actions. Anthropic, Bedrock, Dropbox, Box and Twilio illustrate these different checks. A narrow promise about one control does not settle every data-handling question. The paid option preserves this published review and its source versions; it adds no supplier clearance or contractual assurance.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does selecting a Neon tool category make a database agent read-only?

No. The README distinguishes category selection from read-only enforcement and a pinned SQL role. It documents OAuth grants and API-key requests differently, and warns against production use. Review the project, role and write setting together before approving database access.

VAREXIS-INDEX Single Request

Relevant public records

Do Prisma CLI destructive-command safeguards also protect MCP operations?

Prisma explicitly limits those safeguards to CLI commands. Its MCP server exposes workspace operations, and the documentation directs users to review approvals in the AI client. A CLI safety claim therefore does not establish the approval behaviour of an MCP call.

VAREXIS-INDEX Single Request

Relevant public records

Do PlanetScale query safeguards make full-access agent queries harmless?

No. PlanetScale documents branch-specific read-only or full-access permissions and particular query safeguards. These are bounded checks, not proof that every permitted query is appropriate. Review the branch, action and intended effect; a prompt to seek confirmation is not evidence that a person approved.

VAREXIS-INDEX Single Request

Relevant public records

Can an Aiven connection marked read-only still expose selected write tools?

Yes. Aiven documents an optional write allowlist that re-enables named actions in read-only mode. Service-family selection also leaves core discovery available. Review the complete configuration and authenticated user permissions, rather than treating one read-only label as the whole permission boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does every Databricks MCP call pass through Unity Gateway controls?

No. The current AWS documentation distinguishes system.ai MCPs through Unity Gateway from legacy workspace endpoints. Legacy calls use underlying resource permissions and bypass MCP-level Gateway grants, policies and tracing. Record the actual connection path before accepting a governance or audit claim.

VAREXIS-INDEX Single Request

Relevant public records

Does read-only mode isolate a self-hosted MotherDuck MCP server from its host?

No. The publisher explicitly warns that read-only mode alone still allows filesystem access and DuckDB setting changes. The local server and hosted remote service have different boundaries. A data-write restriction is insufficient evidence of host isolation for third-party access.

VAREXIS-INDEX Single Request

Relevant public records

Can a dbt remote MCP connection replace every local development workflow?

No. dbt distinguishes the remote consumption service from self-hosted local development. API availability also depends on the plan. The overview contains overlapping Administrative API descriptions and a broad read-only statement, so it does not settle every operation: inspect the actual tool list before approving job or development actions.

VAREXIS-INDEX Single Request

Relevant public records

Does the absence of ClickUp deletion tools make an agent connection read-only?

No. ClickUp documents task changes, comments and time tracking while its FAQ says deletion tools are not currently included. It also requires OAuth and applies plan/add-on-dependent usage limits. Review the intended write actions and workspace before treating the connection as a reporting-only integration.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting Todoist for a daily review also expose task-changing tools?

Yes. Todoist documents a hosted OAuth MCP service with task and project reads, creation and updates. A planning or review request should specify whether the agent may change the plan. The overview does not establish a buyer-specific read-only grant.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Glean MCP mean any assistant can access all company knowledge?

No. Glean documents per-user access, tenant-controlled server availability and application-registration controls. The organisational connector is distinct from the public documentation MCP. Review the selected tenant server, permitted client and configured tools; connection success alone does not establish the audience or allowed actions.

VAREXIS-INDEX Single Request

Relevant public records

Does an Amplitude analytics connection only retrieve charts?

No. Amplitude describes querying behaviour alongside cohort, experiment and taxonomy workflows. User OAuth and service-account OAuth are separate identity choices, with existing permissions applying. Distinguish organisational MCP access from public documentation access and review the allowed read and write actions.

VAREXIS-INDEX Single Request

Relevant public records

Does Mixpanel Verified Mode exclude unverified entities from MCP results?

No. Mixpanel says requested entities remain in results; unverified ones are flagged and verified equivalents are preferred where available. The connector also exposes write tools. Review result labels and operation permissions separately rather than treating Verified Mode as either data exclusion or read-only access.

VAREXIS-INDEX Single Request

Relevant public records

Does free PostHog MCP access mean every operation has no additional usage cost?

No. PostHog says MCP access and calls are free, while some tools invoke LLMs internally and may incur PostHog AI spend. The connector supports reads and writes across products. Review AI processing settings, the selected project and the intended action separately from the connection price.

VAREXIS-INDEX Single Request

Relevant public records

Does read-only SQL support mean Render MCP cannot change my application?

No. Render lists read-only SQL alongside service creation, environment-variable updates and redeployment. Actions use the selected workspace. A database inspection task therefore needs a narrower authorised scope than the complete connector capability set.

VAREXIS-INDEX Single Request

Relevant public records

Can a Railway project token restrict an MCP agent to one project?

The current documentation says project tokens are not accepted: MCP requires a user identity. OAuth can select workspaces and projects, while the default CLI bridge reuses the login session. Destructive-action hints depend on client support, so verify both the grant and confirmation behaviour.

VAREXIS-INDEX Single Request

Relevant public records

Does limiting Firebase MCP feature groups remove every other capability?

No. Firebase says core tools remain available when feature groups are selected. The local server inherits Firebase CLI credentials, and some tools proxy requests to remote services. Review identity, project context and the complete exposed tool list rather than assuming local execution or a feature filter is complete isolation.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting Resend for support drafting authorise the agent to send email?

No. Resend documents both drafting workflows and transactional sending, plus contact and webhook operations. OAuth grants or API-key access establish technical capability, not the requested business action. Identify whether the task ends at a draft or an authorised send and verify the recipient scope.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Cloudinary media analysis also define every available asset action?

No. Cloudinary documents separate servers for asset management, configuration, metadata, analysis and MediaFlows. Their authentication options also differ. Review the enabled servers, selected product environment and available tools; analysis access alone is insufficient evidence about upload, deletion or configuration authority.

VAREXIS-INDEX Single Request

Relevant public records

Does every Algolia MCP connection access and modify my search indices?

No. Current documentation distinguishes application-scoped Public MCP, user-scoped Productivity MCP and DevEx code generation. Public and Productivity are read-only; DevEx does not access application data. Identify the offering before claiming either data access or write capability.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful PayPal MCP sandbox call establish a live merchant outcome?

No. PayPal documents separate sandbox and production settings and endpoints. Local access tokens and remote client-credential setup also need the intended account context. A sandbox result is testing evidence; it does not establish that a real payment, invoice or other production action completed.

VAREXIS-INDEX Single Request

Relevant public records

Does enabled push protection prove no secret can be pushed?

GitHub documents bypass paths. With delegated bypass, contributors without bypass privileges need reviewer approval; without it, contributors can bypass at their discretion. Review exception permissions and decisions before interpreting the feature as a no-secret guarantee.

VAREXIS-INDEX Single Request

Relevant public records

Does masking a GitLab variable prevent a job from disclosing it?

GitLab warns that masking is not a guarantee against malicious scripts and that both masked and protected variables can be compromised by code given access. Log display controls and job-access restrictions address different questions. Review the pipeline and variable availability before accepting an isolation claim.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful Slack SCIM offboarding action prove user data was erased?

Slack states that SCIM can deactivate users but cannot permanently delete them. Its token authority also depends on the generating account role. A deactivation result supports an identity-lifecycle claim, not a general data-erasure claim.

VAREXIS-INDEX Single Request

Relevant public records

Does an Atlassian app access rule block every API data category?

Atlassian distinguishes covered data from exempt data in its API references. Rules can block covered data, while exempt categories are not blocked by those rules. Map the actual API operations and data categories before accepting a complete app-isolation claim.

VAREXIS-INDEX Single Request

Relevant public records

Does moving a Notion parent page to Private revoke every child-page grant?

Notion says that moving a shared page to Private removes others from that parent, while subpage grants remain. It also applies the broadest access granted to a user. Review parent, child and workspace grants separately before reporting a complete access revocation.

VAREXIS-INDEX Single Request

Relevant public records

Does sending a SharePoint link to one recipient limit access to that person?

Not necessarily. Microsoft describes Anyone links as transferable: another holder can use the link. Deleting a link revokes that link, while other permissions can still provide access. Review the link type and independent grants before claiming a named-only audience or complete revocation.

VAREXIS-INDEX Single Request

Relevant public records

Can a file-level sharing change remove access inherited from a Drive folder?

Google explains that folder access is inherited by contained files and subfolders. Reducing inherited access requires addressing the folder-level permission; limited-access folders provide a separate boundary. Review the path and explicit grants rather than interpreting a single file setting in isolation.

VAREXIS-INDEX Single Request

Relevant public records

Does a Dropbox subscription guarantee every deleted file can be restored?

No. Dropbox ties recovery to the plan window, deletion type and restoration permissions. Permanently deleted files are outside normal recovery, and the page says Support cannot recover them or files outside available history. A product subscription alone does not prove recoverability of a particular file.

VAREXIS-INDEX Single Request

Relevant public records

Does removing a file from a Box folder prove permanent deletion under retention?

No. Box says retained files can be removed from folders but remain in trash until retention expires. Policy, assignment and file-version retention are separate objects; expiry may remove the policy or trigger disposition. Review the actual assignments and outcome rather than treating folder absence as erasure.

VAREXIS-INDEX Single Request

Relevant public records

Does locking an S3 object version prevent new versions or delete markers?

No. AWS describes Object Lock as protection for specified versions. Retention and legal holds do not prevent a new version or a delete marker above the protected version. Distinguish retained-version protection from the object currently returned by an ordinary lookup.

VAREXIS-INDEX Single Request

Relevant public records

Does blob soft delete also recover a deleted container or storage account?

No. Microsoft separates blob and container protection, and blob soft delete does not cover account deletion. The documentation also lists overwrite, metadata and permanent-delete limits. Review the exact deletion scenario and enabled protection before promising recovery.

VAREXIS-INDEX Single Request

Relevant public records

Does an R2 location hint guarantee a storage jurisdiction?

No. Cloudflare describes location hints as best-effort placement preferences and documents jurisdiction restrictions separately. A bucket jurisdiction cannot be changed after creation. Review the actual bucket configuration and relevant service path; a hint is insufficient evidence of a jurisdiction commitment.

VAREXIS-INDEX Single Request

Relevant public records

Does Neon instant restore apply to every branch and any past time?

No. Current documentation limits instant point-in-time restore to eligible root branches within retained history and excludes branches created by snapshot restore. It restores all databases on the chosen branch. Review eligibility, history and blast radius before accepting a universal recovery claim.

VAREXIS-INDEX Single Request

Relevant public records

Does one namespace per tenant prove an application always selects the authorised tenant?

Pinecone documents separate namespaces and requires data operations to target a namespace. That describes storage and query scope. The buyer still needs evidence that its application maps the authenticated tenant to the correct namespace; the documentation does not inspect that mapping.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling row-level security constrain every database identity?

No. PostgreSQL documents exceptions for superusers, BYPASSRLS roles and normally table owners; owners can opt into forced row security. Whole-table operations also have distinct treatment. Review the actual role and operation before using RLS enablement as evidence of tenant isolation.

VAREXIS-INDEX Single Request

Relevant public records

Does an empty Snowflake query-history result prove no query ran?

No. Account Usage query history can be delayed, and some short hybrid-table queries are represented elsewhere. The documentation also says a successful PUT or GET history status indicates authorisation to proceed, not completed file transfer. Review the view, workload and outcome evidence separately.

VAREXIS-INDEX Single Request

Relevant public records

Does storing a change-stream resume token guarantee recovery after any outage?

No. MongoDB requires enough oplog history to locate the relevant operation. Invalidation also affects how a stream can restart. A saved token is a position reference, not a guarantee that the required history still exists or every downstream event was processed.

VAREXIS-INDEX Single Request

Relevant public records

Does an MCP tool allowlist constrain identities that also have direct connection access?

Databricks warns that USE CONNECTION permits direct use outside the MCP tool selection and policies. It also documents all-tools defaults and optional inclusion of future tools. Review direct grants and selector behaviour before claiming the allowlist covers every access path.

VAREXIS-INDEX Single Request

Relevant public records

Do user-managed Google Cloud service-account keys expire automatically by default?

Google states that keys created through IAM have no expiry by default and remain valid until deleted. Expiry and rotation are separate lifecycle choices, and expiry can interrupt workloads. Request the actual key inventory and replacement process rather than assuming automatic expiration proves credential hygiene.

VAREXIS-INDEX Single Request

Relevant public records

Does AWS last-accessed data prove a permission was successfully used?

No. AWS says service last-accessed data includes attempted calls, including denied attempts. Tracking periods, action coverage and policy types also limit interpretation. Correlate the relevant event evidence before concluding successful use, non-use or that a permission can be removed.

VAREXIS-INDEX Single Request

Relevant public records

Does a read-only database agent also have host or management authority?

Separate data-write restrictions from tool categories, account permissions, SQL roles and host access. Neon, Prisma, PlanetScale, Aiven and MotherDuck document different controls and exceptions. Review the intended deployment and actual grant before approving access; an isolated label cannot establish every boundary.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What must I check before an analytics agent can query or change a product?

Identify the server variant, acting user or service account, project, result labels, permitted writes and usage costs. Databricks, dbt, Amplitude, Mixpanel and PostHog illustrate why analytics access is not one uniform capability. The saved review preserves these published distinctions; buyer configuration still needs its own evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a request to review work also authorise changing or sending it?

Separate search and drafting from task changes, time entries, email sends and configured tenant actions. ClickUp, Todoist, Glean, Resend and Algolia expose different capabilities. Establish the intended action and identity, then review the selected offering and tools before reporting what the agent may do.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What proves an agent acted in the intended project and environment?

Record the selected workspace, inherited identity, environment and operation outcome. Render, Railway, Firebase, Cloudinary and PayPal show different target and confirmation boundaries. A local process, successful login or sandbox result does not by itself prove the intended production action completed.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence is missing from a secret-control or offboarding claim?

Review exception authority, runtime secret access, deactivation scope, key lifecycle and access-report coverage. These supplier records distinguish enabled features from observed outcomes. They help request specific evidence without treating masking, expiration, deactivation or an activity report as universal proof.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What proves a sharing change removed the intended audience?

Inspect link type, direct grants, inherited access and API coverage. Atlassian, Notion, SharePoint and Google Drive document different exceptions and inheritance rules. A parent-page change, private delivery channel or blocked API operation is insufficient evidence that every relevant access path was removed.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a retention or recovery feature prove the file can be restored?

Establish the protected resource or version, history window, deletion state, branch eligibility and location setting. Dropbox, Box, S3, Azure, R2 and Neon address different questions. Retained content may be hidden, permanent deletion may end recovery, and a placement hint is not a jurisdiction commitment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What proves data isolation and complete activity history?

Check application tenant routing, effective database roles, history coverage, replay retention and alternate connection grants. Pinecone, PostgreSQL, Snowflake, MongoDB and Databricks document boundaries that require different buyer evidence. Storage separation, a resume token or one audit view cannot substitute for that evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can a Pulumi inventory question start paid infrastructure work?

Most tools retrieve information or instructions, but the Neo bridge can start billed tasks and pass approvals that let Neo change infrastructure. The documentation also describes fallback organisation selection. Verify the organisation and enabled tools before treating the connection as inventory-only.

VAREXIS-INDEX Single Request

Relevant public records

Does keeping secrets in Vault keep them out of an AI client?

Not when an authorised MCP query returns them. The Vault MCP page explicitly warns that secret data can reach clients and models, and describes both read and write operations. It labels the feature beta and discourages production deployment. This review does not establish a buyer-specific access policy.

VAREXIS-INDEX Single Request

Relevant public records

Can an Auth0 onboarding assistant change the tenant and write local credentials?

Yes. The README describes onboarding that creates an application and saves its credentials to a project environment file. It also documents read-only and tool-selection controls. Assess both tenant authority and local file output; merely describing the task as setup does not narrow either.

VAREXIS-INDEX Single Request

Relevant public records

Does the WorkOS sandbox default prevent production changes?

The default target is sandbox, but production access and writes are separately controlled and initially enabled in the documented team settings. The agent inherits the dashboard user role. Check those settings and the requested environment; the sandbox default alone is not a production-access restriction.

VAREXIS-INDEX Single Request

Relevant public records

Does a read-only Infisical tool list keep secret values out of model context?

Read tools can return values. The README documents a separate masking option that defaults off and still returns metadata when enabled. A tool allowlist limits exposed operations, while identity scope limits underlying access. Review all three before claiming that the connector hides secrets.

VAREXIS-INDEX Single Request

Relevant public records

Does protecting the master-password prompt prevent an agent from reading vault items?

The documented unlock dialog keeps the master password outside MCP, but retrieval tools can still return vault items after unlock. Organisation API credentials enable a separate administrative surface. File-based tools require an allowed-directory setting. Review these distinct authorities rather than treating secure unlock as a complete disclosure boundary.

VAREXIS-INDEX Single Request

Relevant public records

Do Doppler MCP scope flags enforce access beyond the connector?

The documentation distinguishes tool filtering from token-enforced API access. Read-only mode hides write tools, but does not stop other ways an agent might attempt writes. Project/config flags also are not a substitute for scoped credentials. Secret reads remain part of the advertised capability.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting a content delivery tool also enable publishing or deployments?

Contentstack separates delivery, management, automation and deployment tool groups. Delivery retrieves published content, while other groups expose state-changing operations and use different credentials. Review the loaded groups and corresponding credentials; a content-oriented connector name does not establish a read-only surface.

VAREXIS-INDEX Single Request

Relevant public records

Can the Twilio documentation MCP send a message or read my account?

This documented variant searches public specifications and retrieves documentation. It requires no account authentication and does not execute Twilio API calls. It also defaults to the latest available API version. Confirm the intended version; do not treat documentation retrieval as proof of an account action.

VAREXIS-INDEX Single Request

Relevant public records

Does the Contentful MCP environment guard block every possible write?

The local server documents an opt-in, case-sensitive environment guard. It blocks environment-scoped write/delete calls but leaves reads and specified organisation-level or generation operations outside that guard. Other clients are unaffected. Review both the guard and underlying permissions before treating an environment as protected.

VAREXIS-INDEX Single Request

Relevant public records

Does Strapi MCP audit logging prove every content read was recorded?

The documentation describes permission checks for tools, fields, locales and individual documents. It separately states that MCP entry actions require the documented version and Enterprise audit entitlement, and content-only reads are not logged. Permission enforcement and activity-record completeness therefore need separate evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does a working New Relic API key provide all MCP analysis tools?

No. The overview distinguishes OAuth-only tools from API-key access and requires organisation-level permission plus relevant feature switches. Preview and API-key access have separate controls. A successful connection therefore does not establish access to every analysis capability or every account dataset.

VAREXIS-INDEX Single Request

Relevant public records

Can a CircleCI troubleshooting connector rerun or cancel builds?

The hosted tool list includes rerunning and cancelling workflows as well as diagnostic reads. The CLI MCP exposes a broader command surface, so it needs a separate review. Identify the variant, project and intended action before treating a troubleshooting request as permission to alter CI state.

VAREXIS-INDEX Single Request

Relevant public records

Does a Buildkite MCP failure summary mean the job is finished and evidence is complete?

No. The documentation distinguishes promised failure from a final job result and warns that investigation summaries can be partial. Remote endpoints update automatically; version pinning requires the local server. Confirm final status, missing evidence and write restrictions before relying on a CI review.

VAREXIS-INDEX Single Request

Relevant public records

Do Harness MCP default organisation and project settings prevent other targets?

The README describes those settings as defaults used when calls omit identifiers; agents can discover and supply other targets. Read-only mode separately blocks mutating operations and defaults off. Hosted OAuth and local credentials also differ. Review effective permissions rather than treating defaults as an access allowlist.

VAREXIS-INDEX Single Request

Relevant public records

Can a Kubernetes inventory role reveal secrets without a get permission?

Kubernetes documents that list and watch access can reveal Secret contents. It also identifies workload-creation permissions as another route to namespace resources. A review confined to the get verb therefore cannot establish secret isolation; inspect the complete role and workload authority.

VAREXIS-INDEX Single Request

Relevant public records

Does an IAM permissions boundary alone prove every access path is restricted?

A boundary limits identity-policy permissions and grants nothing by itself. The documentation also distinguishes direct resource grants to users, roles and sessions, including cases not limited by an implicit boundary denial. Review principal type and resource policies alongside the boundary; explicit denials are a different case.

VAREXIS-INDEX Single Request

Relevant public records

Does an Azure read-only resource lock prevent changes to stored data?

Resource locks apply to control-plane operations. The documentation explicitly separates data-plane activity, including changes to database or storage contents that a resource lock does not prevent. Identify the actual operation and endpoint before accepting a claim that the locked resource is entirely immutable.

VAREXIS-INDEX Single Request

Relevant public records

Is an S3 presigned download a single-use link valid until its stated expiry?

The documentation allows repeated use before expiry. Temporary signing credentials can expire earlier than the URL setting, and a download begun before expiry can continue afterwards. Review reuse requirements and credential lifetime separately from the displayed expiration; the URL alone does not implement single-use delivery.

VAREXIS-INDEX Single Request

Relevant public records

Can one stored access policy revoke every Azure shared access signature?

Stored access policies apply to associated service SAS tokens. User-delegation and account SAS tokens do not support that association. Identify the SAS type and revocation mechanism before claiming that a policy change ends access; an ad hoc signature cannot inherit a policy it was never linked to.

VAREXIS-INDEX Single Request

Relevant public records

Does removing an Okta session prove that related API tokens were revoked?

The guide separates session cookies from access and refresh tokens. Removing all user sessions can optionally include token revocation through a specific parameter. A successful revocation response also covers already-invalid tokens. Record the operation and its options, then verify the relevant access outcome.

VAREXIS-INDEX Single Request

Relevant public records

Does refresh-token rotation let an agent safely retry any old refresh token?

The rotation documentation describes invalidation of a refresh-token family when reuse of an invalidated token is detected. The service cannot identify the legitimate actor from that replay alone. Both recovery and access-token lifetime need consideration; rotation is not permission to retry stale credentials indefinitely.

VAREXIS-INDEX Single Request

Relevant public records

Does marking a Terraform value sensitive keep it out of state and plan files?

The sensitive setting masks ordinary display, but does not by itself omit values from state or plans. The documentation provides separate ephemeral and write-only mechanisms with version and provider constraints. Review the actual data path and backend rather than accepting a masked screenshot as non-persistence evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does Pulumi secret encryption prove a value cannot appear in application logs?

Pulumi encrypts marked secret values in state and tracks their propagation, but runtime callbacks receive plaintext and can expose it elsewhere. The documentation also excludes resource IDs from secret encryption. Review runtime handling and value placement before accepting a blanket no-disclosure claim.

VAREXIS-INDEX Single Request

Relevant public records

Does a Vault lease policy prove that a copied static password expires?

Vault documents leases for dynamic secrets and service tokens, while the key/value backend does not issue secret leases even when a duration is returned. A static value stored in Vault therefore needs its own credential-lifecycle evidence. Storage in a lease-capable product is not evidence of automatic downstream expiry.

VAREXIS-INDEX Single Request

Relevant public records

Does listing several required reviewers mean every reviewer must approve a deployment?

The documentation says one required reviewer can approve a job. Preventing self-review and restricting administrator bypass are separate settings, with plan and repository conditions. Review the actual environment and job reference before claiming independent multi-person approval from the reviewer list.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful CodeQL run prove generated code and every dependency were analysed?

The Action README distinguishes no-build, automatic and manual build modes. It notes that no-build analysis can miss findings involving generated code or inaccessible dependencies. A successful run alone therefore cannot establish complete coverage; review language, build mode and extraction evidence for the actual repository.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful soft purge prove cached content can no longer be served?

Soft purge marks content stale and can leave it available during revalidation or other configured stale-serving conditions. Fastly distinguishes this from hard invalidation. Identify the purge method and cache behaviour before treating a purge response as evidence that old content is unavailable.

VAREXIS-INDEX Single Request

Relevant public records

Does an Access application-session limit end the session inside a SaaS app?

Cloudflare documents that the Access duration controls entry to the SaaS application, whose own cookie manages the session inside it. Session revocation also needs to be distinguished from preventing a still-authorised identity from returning. Review both systems before accepting a complete-session-termination claim.

VAREXIS-INDEX Single Request

Relevant public records

Does adding a group restriction prove a CI secret is limited to the intended project?

CircleCI treats group, project and expression restrictions as separate checks. With no project restriction, the documentation allows use across projects in the organisation; defaults and integration support also matter. Review the complete context configuration and trigger path rather than treating group membership as a project allowlist.

VAREXIS-INDEX Single Request

Relevant public records

Does rotating a Cloud KMS key prove old encrypted data no longer depends on the old version?

The documentation separates creating a new key version from re-encrypting existing data and retiring old versions. Rotation alone does neither. Establish which data still depends on each version before asserting completion; destroying a version still in use can make its data unrecoverable.

VAREXIS-INDEX Single Request

Relevant public records

Does an infrastructure-agent default establish its permitted scope?

Check effective identity, tool selection, target and consequential-action authority. Pulumi, Terraform, WorkOS and Harness document different defaults and restrictions. A sandbox or project default, or a switch for selected destructive actions, does not establish every access and write boundary.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a read-only secrets assistant keep credentials out of model context?

Separate value disclosure, mutation rights, authentication and local file access. Vault, Auth0, Infisical, Bitwarden and Doppler expose different capabilities. Reading can disclose secrets; masking, secure unlock and tool filtering protect different boundaries. Preserve the exact reviewed configuration assumptions and unresolved buyer evidence.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does connecting a content tool authorise publication or account actions?

Identify whether the selected variant retrieves public documentation, delivers published content or manages live resources. Contentstack, Twilio Docs, Contentful and Strapi illustrate different boundaries. Inspect credentials, environment guards, plugins and audit coverage before equating lookup access with publication authority or action completion.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a connected operations tool prove complete analysis and a final outcome?

Check required tool entitlement, the intended CI action and whether the returned evidence is final or partial. New Relic, CircleCI and Buildkite document authentication-specific availability, state-changing tools and provisional failure signals. Successful connection is not evidence of complete coverage, continuous monitoring or action authority.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a limiting access-control label prove the effective permission boundary?

Review the actual operation, principal, policy combination and trigger. Kubernetes Secret listing, IAM resource grants, Azure data-plane operations and CircleCI context restrictions each show why a limiting label needs configuration evidence. These records identify questions to ask, without assessing the buyer deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does expiring or revoking one credential end every relevant access path?

Identify the credential type and the system that enforces it. S3 links can be reused and expire with their signing credentials; Azure policy association varies by SAS type; Okta and Cloudflare distinguish token or gateway state from other sessions. Record exact coverage and verify the intended outcome.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a secret-management feature prove non-disclosure and reliable expiry?

Distinguish refresh-token reuse handling, Terraform persistence, Pulumi runtime disclosure and Vault static-secret lifecycles. Each feature addresses a specific boundary. A masked display, encrypted state or lease-capable product does not establish that every value stays hidden or expires as the buyer expects.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a successful control signal prove the intended change is complete?

Ask what the signal actually establishes: GitHub reviewer lists do not require every reviewer, CodeQL success does not prove complete extraction, Fastly soft purge can retain stale responses, and Cloud KMS rotation does not migrate existing ciphertext. Save the specific evidence gap before reporting completion.

VAREXIS-INDEX Evidence Receipt

Relevant public records

GitHub + Playwright access?

GitHub MCP and Playwright MCP expose different authority boundaries. GitHub documents read-only mode separately from credential scope. Playwright session isolation does not make authenticated browser actions read-only. This pack compares the two published documentation reviews, including read/write capability, authentication, data movement, unknowns and refusal conditions. The reviews are dated 11 October 2026; neither your deployment nor current tool behaviour has been independently tested.

VAREXIS-INDEX Single Request

Relevant public records

Notion + Slack permissions?

Compare Notion and Slack connector access before retrieving workspace content. This pack keeps their documented authentication, read/write permissions and data-sharing boundaries together, with unresolved client and workspace questions. Notion content may leave Notion through the connected client; Slack search and posting permissions are distinct. These are the existing 11 October 2026 documentation reviews, not tests of your configuration or current tool behaviour.

VAREXIS-INDEX Single Request

Relevant public records

Audit and export evidence?

Review what an activity-history claim can establish before using it in a technical review or procurement discussion. This pack compares the existing GitHub audit, Slack export and Cloudflare Logpush documentation reviews dated 14 October 2026. It preserves event and conversation scope, required buyer evidence, retention and delivery gaps, and conditions for withholding broader conclusions. Missing records do not establish that nothing happened; no buyer export or deployment has been inspected.

VAREXIS-INDEX Single Request

Relevant public records

What can a Chrome DevTools agent see or change in my browser session?

The publisher exposes browser inspection and automation, including page interaction and diagnostic capture. Browser content becomes available to the connected agent. Performance features can send trace URLs to the CrUX service, and usage statistics have a documented opt-out. Browser attachment is not a general security sandbox.

VAREXIS-INDEX Single Request

Relevant public records

Can Microsoft Learn MCP verify how my Microsoft tenant is configured?

The public server searches and fetches Microsoft documentation and code samples without authentication. It does not inspect the buyer tenant. Its tool definitions can change, and optional search token budgets can truncate results. A documentation answer is therefore a starting point for a configuration review, not evidence that a control is enabled.

VAREXIS-INDEX Single Request

Relevant public records

Is Hugging Face MCP limited to searching public models and datasets?

The reviewed offering combines discovery with optional repository contributions, jobs, sandboxes and Space tools. Enabled capabilities depend on configuration. A Space introduces its own execution and data-handling context; authorising Hub search does not establish authority for every optional write or compute operation.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent treat the JFrog MCP server as an artifact search-only integration?

No. The published tool inventory includes repository configuration, access-token operations and other administrative capabilities as well as reads. A Platform Admin enables the integration, and experimental tools require a separate selection. Review the actual available tools and effective identity before authorising a search-only workflow.

VAREXIS-INDEX Single Request

Relevant public records

Does GitGuardian MCP automatically revoke secrets or fix code after detecting an incident?

The Developer profile documents scanning, incident review and guided remediation, with limited honeytoken creation. Broader SecOps actions are described as planned, not established here as available. OAuth and personal-token modes have different credential handling. Publisher statements about secret handling are documentation evidence, not an independent execution test.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting SonarQube MCP automatically restrict an agent to reading findings?

The self-hosted server documents a read-only setting that disables write operations, but its default is false. Tool-set filters further narrow availability; per-request headers cannot widen server restrictions. Hosted and local variants differ, so a configuration review must bind the variant, identity and enabled tools rather than assume all connections are read-only.

VAREXIS-INDEX Single Request

Relevant public records

Does asking Dynatrace MCP to generate DQL authorise it to execute that query?

The documentation separates DQL generation from a data-analysis tool that executes queries and returns results. Execution needs the relevant user and token permissions and remains subject to result limits and capability availability. Generated query text does not establish permission, complete coverage or authority to consume query capacity.

VAREXIS-INDEX Single Request

Relevant public records

Does a Splunk MCP 1.0 search result establish complete log coverage?

Version 1.0 describes encrypted-token access and constrained SPL query execution. Unsafe commands or excessive execution time can cause rejection. Search and knowledge-object tools remain bounded by identity and query scope. This dated review does not establish newer-version authentication or that a successful query covered every relevant event.

VAREXIS-INDEX Single Request

Relevant public records

Does every AppDynamics MCP HTTP call validate the supplied bearer identity with the Controller?

The documented middleware checks bearer syntax, while Controller-backed calls rely on downstream validation. Events-only calls use a separate Events credential and do not contact the Controller. The publisher therefore calls for an independently authenticated shared ingress. A syntactically valid bearer header is not proof of caller authentication for every tool.

VAREXIS-INDEX Single Request

Relevant public records

Can the same Azure DevOps MCP setup be assumed to work for every organisation and action?

The remote offering documents Entra-backed organisations and differs from the locally configured server. The local inventory includes writes such as wiki and work-item changes, not just retrieval. Identify the deployment, organisation identity and effective grants before authorising operations; tool-name changes can also affect an existing client.

VAREXIS-INDEX Single Request

Relevant public records

Does Google Developer Knowledge MCP inspect or change my Google Cloud resources?

The documented tools search, fetch and answer questions from developer documentation. API keys or OAuth-based credentials support access and project attribution; that is separate from inspecting a buyer Cloud deployment. A documentation answer cannot establish actual resource state or a control being enabled.

VAREXIS-INDEX Single Request

Relevant public records

Does selecting a read-only BigQuery MCP tool eliminate cost and permission concerns?

The documented read-only SQL tool excludes specified mutation and execution forms, while a separate execute_sql tool can modify data. IAM still controls calls, and queries remain subject to time and result limits. Read-only execution can consume billable query resources; a tool list or truncated result does not establish authorised access or complete coverage.

VAREXIS-INDEX Single Request

Relevant public records

Does Continuous Access Evaluation guarantee immediate revocation in every application?

Continuous Access Evaluation depends on participating resources and clients, including handling of claim challenges. The guide distinguishes supported scenarios and exceptions. Its presence does not establish universal instantaneous revocation; the buyer must identify the actual application and demonstrate the relevant access outcome.

VAREXIS-INDEX Single Request

Relevant public records

Does marking a third-party app Trusted prove it has only the scopes needed for my task?

Trusted apps can access restricted and unrestricted Google services, subject to the relevant authorisation. The guide separately offers Specific Google data scope selection and organisational-unit settings. A Trusted label alone therefore does not establish a narrowly scoped integration.

VAREXIS-INDEX Single Request

Relevant public records

Does revoking active IAM role sessions prevent the role from being assumed again?

The documented operation adds a deny policy for temporary credentials issued before a cutoff time. It does not by itself remove the ability to obtain later sessions. Review the trust relationship and assumption permissions separately from invalidating existing sessions.

VAREXIS-INDEX Single Request

Relevant public records

Does a GitHub App user token have the same effective access as its installation token?

Installation tokens act for an installation, while user tokens act on behalf of a user. The guide describes user-token access as constrained by both the app and the user. Select the token type and repository scope explicitly; an app permission list alone does not identify the complete effective actor.

VAREXIS-INDEX Single Request

Relevant public records

Does rotating a GitLab personal access token preserve uninterrupted access for existing consumers?

Rotation creates a replacement and invalidates the previous token immediately while retaining the original permissions and scope. Consumers still need the new credential. Rotation is a lifecycle action, not evidence that every dependent integration has switched successfully or that access was narrowed.

VAREXIS-INDEX Single Request

Relevant public records

Does a restricted primary Snowflake role prove the session cannot use broader privileges?

Active secondary roles contribute privileges for many SQL operations alongside the primary role and inherited grants. Creation authority is evaluated differently, through the primary role. Inspect the active role set and operation rather than infer the complete permission boundary from the primary-role name.

VAREXIS-INDEX Single Request

Relevant public records

Does upgrading an Entra licence recover audit or sign-in records that already expired?

The retention guide says licence changes are not retroactive. An upgrade retains only data still available, unless older data was separately archived. Log types also differ; Graph activity logs require a storage or analytics integration. A new licence is not evidence that the requested historical interval exists.

VAREXIS-INDEX Single Request

Relevant public records

Does the Notion audit log show everything a Custom Agent did during a run?

The audit documentation lists Custom Agent configuration and access events but explicitly excludes recording what an agent did during a specific run. Exports also follow active filters and a bounded historical window with a recent-data gap. Audit availability is not proof of a complete agent execution trace.

VAREXIS-INDEX Single Request

Relevant public records

Can an audit receiver count each GitLab streamed event as a unique action?

GitLab documents that one event can be streamed more than once to the same destination and recommends deduplication using its event identifier. Destinations can also be deactivated independently. Receiver counts need event identity and destination-state context before being presented as counts of distinct actions.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling CloudTrail log-file integrity validation prove the delivered files were validated?

Enabling the feature delivers signed digest files. The documentation explicitly separates that from actually validating the logs, which requires a validation operation or equivalent implementation. Retain the verification result, coverage interval and file locations before asserting that an integrity check passed.

VAREXIS-INDEX Single Request

Relevant public records

Does excluding a log from one Cloud Logging sink prove Google never received or stored it elsewhere?

Exclusion filters are applied after the Logging API receives entries and determine routing for the relevant sink. Other sinks and aggregated-routing rules can still matter. Review the complete routing topology before treating an exclusion as non-collection, global deletion or absence from every destination.

VAREXIS-INDEX Single Request

Relevant public records

Can S3 server access logs prove that every request was recorded exactly once?

S3 describes server access logging as best effort, with neither completeness nor timeliness guaranteed. Records can arrive late, be duplicated or be absent. These logs support traffic review, but a missing entry alone cannot establish that a request never occurred.

VAREXIS-INDEX Single Request

Relevant public records

Does a free Gemini API request always have the same data-use terms as an unbilled service?

The terms distinguish Paid and Unpaid Services, with billing-account and regional provisions affecting applicability. Paid-service prompts and responses are not used for product improvement under the reviewed terms, but limited abuse-prevention logging remains described. Verify the applicable category instead of equating no charge with a universal retention or training rule.

VAREXIS-INDEX Single Request

Relevant public records

Does Azure AI not training foundation models on prompts mean every feature is stateless?

The privacy documentation separates foundation-model training from feature storage and abuse monitoring. Responses and Assistants features can retain conversation state; human abuse review has a distinct handling path, with modified monitoring subject to approval. Review the actual feature and approved configuration before making a zero-storage claim.

VAREXIS-INDEX Single Request

Relevant public records

Does Model Vault Encrypted mean no information about a request is visible outside its enclave?

For the documented beta, Cohere distinguishes encrypted content from routing metadata, infrastructure metrics and network observations outside the trusted execution environment. Its confidentiality claims do not eliminate those metadata categories or establish independent certification. The buyer still needs the applicable threat model and deployment evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Mistral zero data retention cover every model and stateful product?

The reviewed documentation applies ZDR to supported stateless API calls on eligible paid plans, excluding Labs models and stateful products. It explicitly separates ZDR from training opt-out. Approval and the actual endpoint matter; one organisation setting does not establish universal non-retention across all features.

VAREXIS-INDEX Single Request

Relevant public records

Does a project deletion request prove every Pinecone resource was already removed?

The versioned API requires associated indexes, assistants, backups and collections to be deleted before deleting a project. Its documented response is acceptance of the deletion request. Record dependency removal and subsequent state separately; an accepted response alone is not a complete erasure attestation.

VAREXIS-INDEX Single Request

Relevant public records

Does tiered multitenancy give every small Qdrant tenant independent physical capacity?

The guide places small tenants in a shared fallback shard and describes promotion to dedicated shards. It also documents single-shard transfer constraints and the shared fallback capacity limit. Logical tenant organisation therefore does not establish independent resources, automatic authorisation isolation or unlimited scaling for each tenant.

VAREXIS-INDEX Single Request

Relevant public records

Does S3 replication keep every source and destination deletion state identical?

Replication has documented exclusions, including specific object-version deletions and lifecycle-related behaviour. Existing objects and already replicated objects can require separate batch handling. Review the replication rule, delete-marker behaviour and version identity rather than assume a destination is a complete real-time mirror.

VAREXIS-INDEX Single Request

Relevant public records

Does Cloud Storage soft delete guarantee recovery of every deleted object and its access settings?

Soft delete preserves eligible deleted data for the configured retention period, subject to supported bucket types and permissions. The guide notes that managed-folder IAM policies are not restored and that retained deleted objects can continue to incur storage costs. Recovery of content and recovery of its access context are separate questions.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent restore an Atlas cluster to a timestamp without affecting its current data?

The Continuous Cloud Backup guide distinguishes restore scopes and warns that a cluster-level restore deletes existing target data and makes the target unavailable during restoration. Search index definitions can be restored while their data requires initial sync. Timestamp selection is not proof of a non-disruptive or immediately ready result.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent use Snowflake Fail-safe as routine extended historical-query access?

Fail-safe follows Time Travel and is described as best-effort recovery by Snowflake when other recovery options have been exhausted. It is not ordinary customer historical access and can take substantial time. The documented service also has exclusions and billing implications; a retention label is not a guaranteed self-service restore.

VAREXIS-INDEX Single Request

Relevant public records

Does restoring a deleted GitHub repository restore its original access configuration?

The guide describes a bounded restoration window and fork-network conditions, with some cases requiring paid-plan support. It explicitly states that team permissions are not restored. Recovering repository content therefore does not prove that collaboration access or every dependent workflow has been recovered.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent use D1 Time Travel as a read-only way to inspect a past database?

The documented restore overwrites the database in place and cancels in-flight queries. It returns a prior bookmark for reversal, subject to the available history window. This operation is not a clone or a read-only historical query; restoration authority and preservation of the recovery bookmark are separate requirements.

VAREXIS-INDEX Single Request

Relevant public records

Does a valid GitHub artifact attestation prove the artifact is secure to run?

Attestations bind artifacts to source and build context. The documentation says they must be verified to provide benefit and explicitly rejects treating them as a guarantee of artifact security. The consumer still needs policy criteria and evaluation of the referenced build and content.

VAREXIS-INDEX Single Request

Relevant public records

Does pinning a container image digest automatically keep its security fixes current?

Digest pinning binds a build to a specific image even when a tag moves. The guide explains that this also opts out of automatic updates through the moving tag. Reproducibility and currency therefore require separate evidence: a fixed identity plus a reviewed process for updating it.

VAREXIS-INDEX Single Request

Relevant public records

Does npm provenance guarantee that a package contains no malicious code?

The npm guide explicitly says provenance does not guarantee absence of malicious code. It provides a verifiable link to source and build instructions, with supported publishing environments and separate verification steps. Package identity and provenance verification support a review; they do not replace content evaluation.

VAREXIS-INDEX Single Request

Relevant public records

Does PyPI Trusted Publishing mean PyPI has reviewed and approved the package code?

Trusted Publishing matches OIDC identities to configured project publishers and exchanges them for short-lived project-scoped upload tokens. It reduces reliance on stored long-lived tokens. That is a publishing-authentication mechanism; the reviewed description does not establish an independent assessment of package contents.

VAREXIS-INDEX Single Request

Relevant public records

Does an immutable container-tag rule make every tag permanently undeletable?

Immutable rules match patterns and differ from role-based protected-tag rules. The guide allows an Owner to delete an immutable rule and describes propagation delays tied to existing tokens. Inspect the actual pattern, rule state and effective time before treating a tag label as permanent or universal protection.

VAREXIS-INDEX Single Request

Relevant public records

Does configuring an Artifact Registry cleanup policy prove matching artifacts were deleted?

The service distinguishes dry-run evaluation from deletion and applies keep policies alongside delete policies. Cleanup runs as a periodic background job rather than immediate request-time deletion. Configuration alone does not establish removal of a specific version; retain policy evaluation and subsequent artifact state.

VAREXIS-INDEX Single Request

Relevant public records

Does an AWS budget notification threshold impose an immediate per-call spending cap?

AWS Budgets uses periodically updated billing information and documents delay between usage and notification. Additional costs can accrue beyond the threshold before notice arrives. A notification setting alone is therefore not an immediate limit on an agent call; separately configured actions and execution controls need their own review.

VAREXIS-INDEX Single Request

Relevant public records

Does creating an Azure Cost Management budget stop resources when the amount is reached?

The guide explicitly states that budget notifications do not affect resources or stop consumption. Cost data and budget evaluation are delayed; action groups can support separate automation. Record any actual enforcement mechanism rather than present the budget amount as a hard execution cap.

VAREXIS-INDEX Single Request

Relevant public records

Does every Google Cloud budget automatically pause services at its threshold?

Current documentation distinguishes Alerts-only budgets from Spend cap budgets. Alerts-only settings do not impose a cap. Spend-cap state and supported project scope require separate inspection, and usage-reporting delays remain relevant. A generic budget screenshot cannot identify the enforcement mode or prove an absolute instantaneous ceiling.

VAREXIS-INDEX Single Request

Relevant public records

Does Vercel Spend Management stop every charge as soon as the spend amount is reached?

A spend amount alone does not stop usage; production pausing must be enabled. Checks occur periodically, so usage can continue after the amount is crossed. The guide also excludes AI Gateway API-key and v0 usage from production pausing. Inspect scope and timing before treating it as a universal spending ceiling.

VAREXIS-INDEX Single Request

Relevant public records

Does maximum bytes billed cap every BigQuery charge for an agent workflow?

For on-demand queries, maximum bytes billed checks an estimate before execution and can reject a query above the limit. Clustered-table estimates can exceed the eventual billed amount. This query setting does not establish an account-wide budget or cover every storage and capacity charge.

VAREXIS-INDEX Single Request

Relevant public records

Does an account-level Snowflake resource monitor stop all serverless and cloud-services charges?

Resource monitors control the documented user-managed virtual warehouses, not every Snowflake-provided serverless feature. Warehouse-level monitors cannot suspend cloud-services usage, and further cloud-services cost can arise after warehouse suspension. An account-level label therefore does not prove every credit-consuming path is capped.

VAREXIS-INDEX Single Request

Relevant public records

Which authority is needed before a search agent uses browser, Space or administrative tools?

Chrome DevTools, Hugging Face, JFrog and SonarQube expose different optional execution and write surfaces. Identify the actual tool, identity, data recipient and intended action before extending a discovery task. A read-oriented purpose does not establish read-only configuration.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can a documentation MCP answer prove the configuration of my cloud tenant?

Microsoft Learn and Google Developer Knowledge retrieve documentation rather than inspect buyer resource state. Authentication requirements differ, but neither reviewed tool set turns a published feature description into proof that the feature is configured, licensed or effective in the buyer environment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an authenticated observability tool prove complete evidence and caller identity for every query?

Dynatrace, Splunk Platform and AppDynamics document distinct query, identity and backend paths. Inspect result limits, supported versions and backend authentication. A successful connection or bounded result does not establish complete incident coverage or a uniform caller-validation path.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does tool access authorise remediation, project changes or billable queries?

GitGuardian Developer capabilities, Azure DevOps operations and BigQuery queries need distinct action and entitlement checks. Planned remediation is not live capability; project access is not approval for every mutation; read-only SQL can still consume billable resources. Preserve the exact intended operation and authority.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence shows an agent identity has the intended scope and can be revoked?

Review participating applications, OAuth scopes, token types, active role combinations and session cutoffs. These six records distinguish configuration labels from effective identity and lifecycle evidence. They identify buyer checks; no buyer deployment or offboarding outcome has been tested.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What does an audit export prove about completeness, uniqueness and integrity?

Retention, event coverage, duplicate handling, routing and integrity validation are separate evidence questions. Entra history, Notion agent events, GitLab streams, CloudTrail digests, Cloud Logging sinks and S3 server logs each have explicit boundaries. An export or enabled setting alone does not establish every dimension.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence distinguishes no training, no retention, encryption and deletion?

Gemini, Azure AI, Cohere, Mistral, Pinecone and Qdrant address different data-handling boundaries. Bind the service category, feature, deployment and request outcome. Training restrictions, encrypted content, tenant placement and accepted deletion requests are not interchangeable proofs of non-retention or isolation.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does recovered data mean the service, permissions and current state are restored?

Recovery differs across S3 replication, Cloud Storage soft delete, Atlas restores, Snowflake Fail-safe, GitHub repositories and D1 Time Travel. Check object identity, retention, target replacement, permission recovery and readiness. A recovery label is not proof of an authorised, complete or non-disruptive outcome.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does artifact provenance or immutability establish safe and current software?

GitHub and npm provenance, PyPI publisher identity, Docker digest pins, GitLab tag rules and Artifact Registry cleanup protect different parts of the artifact lifecycle. Verify identity and enforcement, then separately evaluate content, currency and removal. None of these labels alone establishes a security verdict.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Which budget controls actually constrain an agent workflow and which only report spend?

Distinguish delayed alerts, explicitly configured caps, production pauses, per-query limits and warehouse monitors. AWS, Azure, Google Cloud, Vercel, BigQuery and Snowflake have different scopes and delays. Record the actual mode and excluded consumption before accepting a maximum-spend claim.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can a Salesforce MCP connection grant an agent unrestricted or unattended access?

The reviewed hosted service uses an External Client App and the connecting user's permissions. The documented flow is user authorization code, not a shared machine identity. Object, field and record permissions still matter; tool annotations depend on client support. Flex Credits and enabled servers need checking separately.

VAREXIS-INDEX Single Request

Relevant public records

Does the Okta MCP server expose only directory reads?

The server loads tools according to configured scopes. Read scopes and manage scopes expose different operations, and manage scopes also cover reads. Device authorization and private-key JWT are documented alternatives; granted API scopes and assigned admin roles must match the intended task.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assume Confluent MCP cannot change streaming resources?

Most documented operations read data, but connector restart/configuration and Flink statement changes are available. Global and regional endpoints accept different key types. Mutation confirmation is presented through the client, whose auto-approval may bypass a visible prompt. Credential permissions remain decisive.

VAREXIS-INDEX Single Request

Relevant public records

Does Couchbase MCP always allow an agent to modify documents?

The documented configuration defaults to read-only mode, with additional tool disabling. The wider tool inventory includes document mutations and queries, so the effective setting matters. Database authentication supports username/password or client certificates; when both are supplied, the certificate path takes precedence.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful Dremio MCP demonstration prove access to real project data?

The guide distinguishes hosted OAuth connections from self-hosted token configuration. Self-hosted modes expose data exploration, introspection or metrics, with optional view creation. Mock mode preserves tool names and schemas but returns placeholders; a successful mock call therefore does not validate data access.

VAREXIS-INDEX Single Request

Relevant public records

Does SQLcl MCP restrict level 4 prove that an Oracle connection is read-only?

SQLcl 26.3 documents level 4 as the MCP default, restricting host commands and scripts. Its database tools still execute SQL and PL/SQL under the connected identity. A command restriction is not evidence that database privileges exclude changes; saved connection selection and grants need separate review.

VAREXIS-INDEX Single Request

Relevant public records

Is the Langfuse MCP connection a public documentation-only tool?

The data-platform endpoint is authenticated and project-scoped. Read and write tools are available by default; the guide recommends a client allowlist for read-only workflows. It is separate from the public documentation server. Endpoint region, key scope and permitted operations must be identified.

VAREXIS-INDEX Single Request

Relevant public records

Can a LangSmith MCP agent inspect traces without also being authorised to run evaluations?

The remote tool surface includes trace reads alongside prompt publishing, dataset changes and experiment execution. OAuth and API-key access are documented. Self-hosted availability also depends on version and signing configuration. Connection success does not grant task authority for every exposed operation.

VAREXIS-INDEX Single Request

Relevant public records

Is Port MCP automatically read-only when added from an IDE?

The documented read-only header defaults to off, allowing tools according to the user's permissions. Turning it on hides write tools. Enabled external connectors introduce their own identities and operations, so a Port login alone does not establish the scope of every upstream action.

VAREXIS-INDEX Single Request

Relevant public records

Is Kong Konnect MCP limited to reading gateway configuration?

The documented service combines configuration queries and diagnostics with Dev Portal content creation, editing and publication. PAT and system-account access follow the associated permissions. Optional KAi knowledge search uses additional model processing, so selected tools and data recipients need explicit review.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting Zoom MCP give an agent only meeting search?

The publisher lists default meeting, recording and content tools, including file creation. Dedicated product endpoints expose different tool sets and granular scopes. Authentication mode alone does not establish parity across tools or tokens; requested content and write operations must match the granted scope.

VAREXIS-INDEX Single Request

Relevant public records

Does Turso MCP OAuth mean an agent can only query a database?

The publisher describes organization, database and group management as well as SQL. Dashboard consent selects organization, group and scopes; the scoped token is forwarded to the Turso API for enforcement. OAuth removes manual token copying, but does not by itself make the operation read-only.

VAREXIS-INDEX Single Request

Relevant public records

Does a Snowflake function with external access have unrestricted internet access?

External access integrations select allowed network destinations and authentication secrets. Creating a handler that uses them also requires relevant integration and secret privileges. The integration is an outbound capability; its existence alone does not demonstrate the buyer's effective destination list or the data the handler sends.

VAREXIS-INDEX Single Request

Relevant public records

Does a SELECT grant prove an agent can access a catalog from any Databricks workspace?

Catalog binding can deny access from an unassigned workspace despite a user's explicit grants. A binding can also restrict that workspace to reads. Ordinary catalogs are open across the metastore by default, while automatically created workspace catalogs have a narrower default. Both binding and identity evidence are needed.

VAREXIS-INDEX Single Request

Relevant public records

Does a BigQuery authorized view require giving the reader direct access to source tables?

An authorized view can expose selected query results without giving readers direct access to the source dataset. Authorization on the source, access to the view and permission to run a query job are separate. Underlying row and column policies remain relevant; a view name alone is insufficient evidence of the exposed data.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assume a Redshift RLS policy follows every cross-database or shared-data access path?

The reviewed limitations distinguish ordinary RLS access from cross-database queries and datasharing. Cross-database reads of protected relations are blocked for users without IGNORE RLS; sharing also has explicit restrictions and configuration. Inspect the caller privilege and access path instead of assuming one filter covers all consumers.

VAREXIS-INDEX Single Request

Relevant public records

Does an accepted IAM policy update prove the new permission is effective everywhere immediately?

IAM documents eventual consistency across replicated services and caches. An accepted change can take time to become visible. The buyer needs effective-access evidence for the intended operation; neither an immediate denial nor a successful configuration response alone proves the final permission state.

VAREXIS-INDEX Single Request

Relevant public records

Does an eligible PIM assignment mean an agent's user already has the privileged role?

Eligible assignments require activation before use; active assignments permit use within their assigned duration. Approval is conditional on role settings, not inherent in every activation. Review assignment type, activation state, duration and configured approval rather than treating the word PIM as proof of just-in-time approval.

VAREXIS-INDEX Single Request

Relevant public records

Does trusting an external identity provider let every identity from it access Google Cloud?

Workload Identity Federation uses attribute mapping and can apply conditions to accept only selected external identities. Resource access then depends on direct IAM grants or service-account impersonation. Removing a stored service-account key does not establish a narrowly scoped trust relationship by itself.

VAREXIS-INDEX Single Request

Relevant public records

Does possessing a GitHub personal token prove it can access an SSO-linked organization?

Classic personal tokens need SSO authorization for the organization; fine-grained tokens are authorized during creation. A linked SSO identity can require authorized credentials even without enforced SSO. Scope edits, regeneration, expiry or revocation can change that authorization.

VAREXIS-INDEX Single Request

Relevant public records

Does an ephemeral self-hosted runner registration prove the underlying machine was wiped?

The runner reference recommends ephemeral autoscaling and describes one-job assignment with automatic deregistration. Host cleanup and external preservation of runner logs remain operator responsibilities. A vanished runner registration is therefore not evidence that residual workspace data or host state was destroyed.

VAREXIS-INDEX Single Request

Relevant public records

Does running a GitLab job in Docker establish isolation from the runner host?

GitLab distinguishes shell, non-privileged and privileged container execution. Privileged mode exposes substantially more host authority; reusable runners can also carry effects across projects. A container label alone is insufficient: executor, privileges, reuse and network reach determine the review scope.

VAREXIS-INDEX Single Request

Relevant public records

Does an immutable CircleCI cache prove a build used the correct dependencies?

A cache key cannot be overwritten after its first write. Parallel writers can therefore make the selected content depend on completion order, while later writes are discarded. Correctness requires appropriate keys and workflow ordering; immutability alone neither validates dependencies nor guarantees freshness.

VAREXIS-INDEX Single Request

Relevant public records

Does an agent-wide Buildkite hook alone enforce the same security policy for every repository?

The security guide warns that repository-local hooks can evade policies enforced by agent hooks. Disabling local hooks also disables plugins, and a checkout containing a local hook then fails. Policy review must include repository influence, job environment and the trade-off of disabled extensions.

VAREXIS-INDEX Single Request

Relevant public records

Does a Notion workspace export prove that the whole workspace can be restored?

Exports omit pages the exporter cannot access and can be limited by teamspace settings. The guide also states that uploading exported content does not instantly recreate the workspace. Export coverage and a demonstrated restoration workflow are separate evidence requirements.

VAREXIS-INDEX Single Request

Relevant public records

Does an Airtable CSV export preserve everything needed to leave the service?

CSV export is view/table based and includes visible field values. It omits several non-field objects, and attachments appear as filenames and expiring URLs rather than embedded files. A full exit plan needs separate attachment capture, view-filter checks and an inventory of omitted content.

VAREXIS-INDEX Single Request

Relevant public records

Does a Jira Cloud backup include third-party app data and automation configuration?

The export guide excludes third-party apps and app data, and automation flows require their own export/import. Cloud and Data Center destinations have different compatibility constraints. A backup file therefore needs an inventory and target-specific restore evidence before it supports a full migration claim.

VAREXIS-INDEX Single Request

Relevant public records

Can a Confluence PDF or HTML export stand in for a complete space backup?

Export formats preserve different content. PDF omits comments; HTML has additional exclusions, and Team Calendars are not included. Visibility and administrator exceptions also affect coverage. Record the format and exporter identity instead of assuming every space export is a complete archival copy.

VAREXIS-INDEX Single Request

Relevant public records

Does creating an S3 VPC endpoint prove the bucket can only be reached through it?

The documented restriction uses a bucket policy tied to a VPC or endpoint condition. Endpoint existence is not that policy evidence. An explicit deny can also block console access and cause lockout if the identifier is wrong, so the effective policy and intended alternate access require review.

VAREXIS-INDEX Single Request

Relevant public records

Does a Google Cloud service perimeter replace resource permissions?

VPC Service Controls supplies context-based perimeter checks in addition to IAM. Ingress/egress rules and supported-service scope determine which paths it covers. A perimeter configuration does not establish least-privilege identities or coverage for every service operation.

VAREXIS-INDEX Single Request

Relevant public records

Does adding an Azure Storage private endpoint automatically disable public network access?

The storage guide treats the private endpoint and public-endpoint access rules separately. Storage services need their applicable endpoints, and name resolution must reach the private address. An endpoint's existence alone does not prove all service traffic uses it or that public access is blocked.

VAREXIS-INDEX Single Request

Relevant public records

Does creating a Snowflake network rule make it an enforced account restriction?

The network guidance requires activation at the relevant account, user or integration scope. It also distinguishes inbound access from external-access egress, and integration-level policies have storage-stage limitations. A defined rule is not proof of the applicable active policy.

VAREXIS-INDEX Single Request

Relevant public records

Does a Langfuse trace deletion response prove all related personal data is gone?

Tracing deletion is asynchronous and the guide recommends querying again to check completion. Removing traces does not necessarily remove data held in other objects such as datasets, and later ingestion can add data again. Scope, timing and verification need separate evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does a read-only LangSmith trace link keep its content restricted to account members?

A publicly shared trace can be viewed by anyone holding its link without a LangSmith account. Self-hosted network constraints can limit reach. Read-only describes editing, not confidentiality; inspect the trace and deployment before sharing, and distinguish unsharing from deleting the underlying trace.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Datadog Audit Trail guarantee indefinite searchable audit history?

The guide provides configurable retention and a separate optional archive path. Archive upload has an interval and setup delay; it is not immediate evidence that every event is retained in the buyer's bucket. Enablement, retention and verified archive delivery need distinct checks.

VAREXIS-INDEX Single Request

Relevant public records

Does an empty Sentry event search prove that no error occurred?

The reviewed experimental endpoint reports received-but-dropped events alongside accepted volume. It distinguishes filtering, rate limits and other drop reasons. These counts describe ingestion outcomes, not every event generated by an application; missing events require telemetry and filtering context before a conclusion.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent reuse a projected Kubernetes service-account token as a permanent general API credential?

Projected tokens obtained through TokenRequest are time-bound and normally bound to the Pod and Kubernetes API audience. Long-lived manually created tokens are a different mechanism. Credential review must identify token type, audience and object lifetime rather than assume all service-account tokens behave alike.

VAREXIS-INDEX Single Request

Relevant public records

Does generating a new GitHub App private key automatically retire the old one?

The guide supports multiple concurrent private keys for rotation and states that keys do not expire automatically. A new key therefore does not establish that the old signer is revoked. Inventory, consumer handoff and explicit old-key removal need evidence separate from successful generation.

VAREXIS-INDEX Single Request

Relevant public records

Does a short-lived Vault wrapping token make the underlying secret expire at the same time?

Response wrapping delivers a single-use token with its own lifetime instead of the original response. That lifetime is separate from the wrapped secret. Creation-path inspection and unwrap status help review delivery, but failed unwrapping alone does not prove interception; expiry is another possible cause.

VAREXIS-INDEX Single Request

Relevant public records

Does configuring a Secret Manager rotation schedule replace the credential and update every application?

The schedule sends a Pub/Sub rotation notification. A subscriber must perform the required work, such as creating a new secret version and deploying it to consumers. Notification retries and skipped in-flight schedules also matter; the configured timer alone is not proof of completed rotation.

VAREXIS-INDEX Single Request

Relevant public records

What proves the identity and permissions of an enterprise agent connection?

Salesforce, Okta and Port bind access to different user, application and upstream identities. Inspect authentication, effective grants, enabled tools and task authority together. A connected client or visible tool list does not demonstrate least privilege or permission for every operation.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence proves a database MCP workflow is read-only?

Couchbase configuration, Dremio deployment modes, SQLcl command restrictions and Turso consent govern different layers. Bind the real target, identity, enabled tools and database privileges. Mock responses and local command restrictions cannot substitute for evidence of the actual database operation.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does connecting an operational MCP tool authorise changes or content publication?

Confluent, Kong and Zoom mix reads with selected changing operations. Verify the exact server, scope, recipient and action. A client confirmation request, diagnostic purpose or meeting-read permission does not establish authority to modify pipelines or publish content.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can an observability agent inspect traces without authority to publish prompts or run experiments?

Langfuse and LangSmith expose authenticated project data alongside supported write or evaluation tools. Identify the project, effective tools, data recipients and evaluation authority. A request to inspect a trace does not authorise prompt publication, dataset changes or experiment costs.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a data-platform access control cover every execution and sharing path?

Snowflake external integrations, Databricks workspace bindings, BigQuery authorized views and Redshift RLS govern different paths. Establish the target, caller, workspace, data projection and exceptional privileges. A named control does not demonstrate universal data isolation.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What identity evidence is needed immediately before a privileged agent action?

IAM propagation, PIM activation, workload federation and GitHub SSO authorization create different state checks. Record the accepted external identity, current activation and organization authorization, then confirm effective access. Configuration acknowledgement or credential possession is not enough.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence supports isolation and reproducibility in an agent-triggered CI job?

GitHub runner disposal, GitLab executor privileges, CircleCI cache writers and Buildkite hooks affect different parts of a job. Inspect host reuse, repository influence, dependency identity and policy enforcement. Neither containers nor immutable caches independently establish a clean or reproducible run.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a SaaS export provide everything required for migration or recovery?

Notion, Airtable, Jira and Confluence exports have distinct permissions, format and object exclusions. Inventory accessible content, attachments, comments, apps and automation, then validate the intended destination. A successful download is evidence of an export, not a complete recovery demonstration.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does private connectivity prove that public and unauthorized access are blocked?

S3 endpoint policies, Google Cloud service perimeters, Azure private endpoints and Snowflake network activation are separate controls. Verify active policy associations, identity grants, service scope and DNS. An available private path does not prove every alternative path is denied.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence is missing when a trace is shared, deleted, retained or dropped?

Langfuse deletion, LangSmith public links, Datadog retention and Sentry outcomes concern different telemetry lifecycle stages. Bind the object, audience, time interval and completion state. Missing stored data does not prove no event occurred, and a read-only link does not prove confidentiality.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What proves a credential handoff or rotation is complete?

Kubernetes projected tokens, GitHub App keys, Vault wrapping and Secret Manager schedules separate issuance, delivery, scope and retirement. Inspect audience, lifetime, consumer rollout and old-credential retirement. A new key, short delivery token or scheduled notification alone does not establish the completed lifecycle.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an Airbyte agent read upstream data as the signed-in person?

Pipeline operations use the signed-in Airbyte user, or the user who created an application credential. Direct source reads instead use credentials stored in the selected connector. The open-beta server can also change pipelines and start syncs. A successful sign-in does not establish row-level user impersonation in the upstream system.

VAREXIS-INDEX Single Request

Relevant public records

Does a Fivetran MCP confirmation warning enforce approval?

The publisher repository separates read, write and delete tool scopes and supports explicit action exclusions. Its confirmation wording is advisory, not a server-enforced approval step. Credential-related endpoints also need review. The documented HTTP OAuth resource-server mode is unfinished; it must not be represented as verified token authentication.

VAREXIS-INDEX Single Request

Relevant public records

Does Fivetran Agent Context query with each user's warehouse permissions?

This hosted public-preview interface exposes context-layer SQL reads and feedback submission. Setup selects a warehouse query role or credential; it is not evidence of per-user warehouse impersonation. Dedicated read-only options differ by warehouse, and the reviewed setup says role-based query access is not yet supported for Databricks.

VAREXIS-INDEX Single Request

Relevant public records

Does read-only Prefect MCP make the whole agent read-only?

The documented MCP tools inspect runs, logs and infrastructure without mutations. A local server can inherit the active Prefect profile, while the hosted connection uses selected Cloud workspaces. An agent with separate terminal or SDK access can still change Prefect resources; the MCP tool boundary does not restrict those other capabilities.

VAREXIS-INDEX Single Request

Relevant public records

Is Fabric Core MCP only a data-query connection?

The preview Core endpoint manages resources, including workspace and item changes and workspace role assignments. It uses the authenticated Entra identity's Fabric permissions. These resource-management tools are not general-purpose lakehouse table-query tools. Supported-operation audit records and client approval settings must be assessed separately.

VAREXIS-INDEX Single Request

Relevant public records

Do read-only annotations prevent a Kestra flow from changing systems?

Flow tools invoke registered Kestra workflows; their effects depend on the flow. The trigger's annotations are informational and do not change execution. Private and public server modes differ materially: a public server admits unauthenticated callers. Authentication choices and flow-scoped permissions depend on edition and configuration.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting Retool MCP only expose app previews?

Retool's inbound MCP can inspect apps, build or change them, execute resource queries and perform selected administrative tasks according to authorized scopes. It differs from a Retool resource that connects outward to another MCP server. App-building uses both the external development agent and Retool's building service; credit usage remains a separate commercial prerequisite.

VAREXIS-INDEX Single Request

Relevant public records

Does installing the Dagster plugin establish the correct deployment access?

The plugin bundles guidance with a separately authenticated Dagster+ MCP connection. Publisher documentation describes both information access and actions. Region selection matters, and deployment roles govern access; Pro overrides can add permissions rather than subtract the deployment role. Plugin installation alone does not prove the selected identity, region or effective grants.

VAREXIS-INDEX Single Request

Relevant public records

Does an SQS visibility timeout prove a task was processed once?

Visibility temporarily hides a received message. Without deletion it becomes available again when the timeout expires, and standard-queue delivery can still duplicate messages. A lease period is not proof that downstream work committed or that repeating the work is harmless.

VAREXIS-INDEX Single Request

Relevant public records

Does FIFO deduplication prevent every duplicate business action?

SQS suppresses repeated sends within its documented deduplication interval. Content-based IDs use the message body rather than message attributes. This queue admission behaviour does not establish a transaction across the consumer and an external service, or protection for retries beyond that interval.

VAREXIS-INDEX Single Request

Relevant public records

Does an EventBridge rule guarantee eventual delivery to its target?

EventBridge retries retriable target failures within configured age and attempt limits. The documented defaults are bounded, and exhausted delivery attempts can end in a dropped event. A dead-letter queue needs separate configuration; a rule existing is not evidence that undelivered events are retained or recovered.

VAREXIS-INDEX Single Request

Relevant public records

Does successful asynchronous Lambda invocation prove the function completed?

Asynchronous invocation uses a service queue. Function errors and throttling follow different retry behaviour; duplicate delivery is possible even without a function error. Events can expire or exhaust attempts. Dead-letter queues and failure destinations capture different failure information and require configuration.

VAREXIS-INDEX Single Request

Relevant public records

Does redriving a failed workflow use the newly deployed fix?

Eligible Standard Workflow redrives retain the original execution identity, input and state-machine definition. Successful steps are generally preserved while failed work resumes according to state-specific rules. Updating an alias does not make a redrive use its new version; redrive and starting a new execution are different decisions.

VAREXIS-INDEX Single Request

Relevant public records

Does an expired DynamoDB TTL make a record immediately unavailable?

TTL deletion occurs asynchronously, typically within days. Expired items awaiting deletion can still be updated and appear in reads unless the application filters them. The attribute must have the documented numeric timestamp format. An expired timestamp alone does not establish removal or fulfil an erasure commitment.

VAREXIS-INDEX Single Request

Relevant public records

Does storage billing stopping prove an S3 object has already been deleted?

Lifecycle actions can be queued after an object becomes eligible. Billing changes normally follow eligibility even if the action happens later, with documented exceptions for some transitions. Therefore billing status or a scheduled expiration is not an object-level deletion receipt.

VAREXIS-INDEX Single Request

Relevant public records

Does Pub/Sub exactly-once delivery cover every subscription and external action?

The documented feature applies to pull subscriptions within a cloud region. Successful acknowledgement prevents redelivery of that message, while expired acknowledgement deadlines can lead to a new valid delivery. It does not establish an atomic transaction with an external business system or deduplicate separate publisher messages.

VAREXIS-INDEX Single Request

Relevant public records

Does assigning a Cloud Tasks name make the handler operation exactly-once?

A caller-selected task name supports task-creation deduplication. It does not demonstrate that a handler's external work committed once. Delivery headers distinguish retries from executions, and the scheduled ETA changes on retries; the publisher explicitly says ETA is not a deduplication key.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a BigQuery table immediately remove all retained history?

Changed or deleted table data remains within the configured time-travel window, followed by a separate fail-safe period. A deleted table uses the window in force at deletion; increasing the setting later does not simply extend that earlier deletion's recovery window. These are retention boundaries, not a legal erasure conclusion.

VAREXIS-INDEX Single Request

Relevant public records

Does a destroy request always mean secret material is already irrecoverable?

Secret-version destruction is immediate by default, but a configured destruction delay preserves a recovery interval. During that delay the version is scheduled for destruction and authorized administrators can cancel it. A request acknowledgement must therefore be interpreted with the secret's delay configuration and actual version state.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful Service Bus send prove a new message was enqueued?

With duplicate detection enabled, a repeated message identity within the configured window can receive a successful send response while the duplicate is discarded. The feature is tier-dependent and identity construction matters. It does not prove that a downstream consumer completed a unique business action.

VAREXIS-INDEX Single Request

Relevant public records

Does Event Grid guarantee ordered delivery until a subscriber succeeds?

Event Grid attempts at-least-once delivery without guaranteeing event order. Retry behaviour depends on error type and configured limits; some failures are not retried. Events can be dropped when limits are reached or no dead-letter destination exists. Consumers need evidence of ordering and recovery appropriate to their workflow.

VAREXIS-INDEX Single Request

Relevant public records

Does an expired Cosmos DB item disappear physically as soon as queries stop returning it?

Expired items stop appearing in query responses immediately, while background deletion can wait for resources. TTL is measured from the last modification, and item-level values depend on container TTL being enabled. Query absence is therefore not proof of completed physical deletion or deletion from other stores.

VAREXIS-INDEX Single Request

Relevant public records

Does recovering a Key Vault restore every surrounding integration?

Soft deletion retains recoverable vault objects for a configured interval, and purge protection prevents early permanent removal during that interval. Recovering the vault does not automatically restore associated Azure RBAC assignments or Event Grid subscriptions. Recovery of secret material and recovery of the surrounding service are separate checks.

VAREXIS-INDEX Single Request

Relevant public records

Does a concurrency group guarantee every queued workflow will run?

The default single-pending behaviour replaces an earlier pending run when a new one arrives. The documented larger queue mode has a bound and cannot be combined with cancelling in-progress work. Serialisation is not a guarantee that every dispatch executes or that external side effects are rolled back when a run is cancelled.

VAREXIS-INDEX Single Request

Relevant public records

Does GitHub automatically retry every failed webhook delivery?

GitHub documents that failed webhook deliveries are not automatically redelivered. Manual redelivery or a separately implemented scheduled recovery process is required. Failure records and available delivery APIs depend on webhook type. A configured webhook alone does not establish an automatic recovery service.

VAREXIS-INDEX Single Request

Relevant public records

Does a protected GitLab tag mean nobody can create or delete a matching release tag?

Protected tags restrict creation to authorized roles or users; matching wildcard rules require joint review rather than assuming one restrictive pattern wins. Authorized maintainers can delete protected tags through GitLab's UI or API. Protection is an access-control setting, not evidence that a release reference is immutable.

VAREXIS-INDEX Single Request

Relevant public records

Does a Kubernetes NetworkPolicy object prove an agent pod cannot reach the internet?

NetworkPolicy needs a supporting network implementation. Pods are not isolated for egress by default, and applicable policy allowances combine rather than overriding each other by order. A saved policy object is therefore insufficient: selection, direction, implementation support and the combined allowed traffic must be checked.

VAREXIS-INDEX Single Request

Relevant public records

Does a Kubernetes CronJob guarantee exactly one run for each scheduled time?

CronJob scheduling can create duplicate jobs or miss a run in some circumstances; jobs should be designed for idempotent work. Its concurrency policy applies only to jobs from the same CronJob. It does not coordinate another CronJob or prove that a scheduled business operation completed.

VAREXIS-INDEX Single Request

Relevant public records

Does each Semantic Layer service token use an independent warehouse identity?

Service tokens map to configured Semantic Layer credentials. Multiple tokens can share a credential, and available credential mappings depend on the plan. Queries follow the linked warehouse credential's data policies. Different token names alone do not establish separate warehouse access or user-specific row restrictions.

VAREXIS-INDEX Single Request

Relevant public records

Does keeping Delta history guarantee old table versions remain queryable after VACUUM?

VACUUM removes eligible unreferenced data files, which can remove the files needed by older table versions. Log retention is a separate process. Metadata-only deletes and cached copies have additional considerations. Retained history entries alone are not proof of recoverable data or complete removal from every execution environment.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Slack token rotation provide uninterrupted access without further state handling?

Rotation introduces expiring access tokens and replacement refresh tokens. The new refresh token must be retained after exchange; repeatedly using the original token breaks subsequent refreshes. Slack also limits simultaneously active refreshed tokens. Rotation requires a tested credential-lifecycle implementation, not merely an enabled setting.

VAREXIS-INDEX Single Request

Relevant public records

Does a Notion webhook contain the full page content as it existed when the event occurred?

The documented flow sends event metadata and then retrieves updated content through the Notion API. That retrieval is a separate operation, not proof of an event-time content snapshot. Signature checking authenticates the received bytes; it does not establish the completeness or historical identity of subsequently fetched page content.

VAREXIS-INDEX Single Request

Relevant public records

Which data-pipeline agent connection fits a diagnosis-only task?

Airbyte, Fivetran management and Prefect expose different operational surfaces. Identify the target, credential, enabled mutations and separate client capabilities. Pipeline diagnosis does not itself authorize connector changes, credential access or workflow execution.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Which identity controls an analytical agent's access to warehouse data?

Fivetran Context and dbt Semantic Layer use configured warehouse identities, while Fabric Core exposes resource-management operations using an authenticated Fabric identity. Choose the actual interface and inspect its identity mapping. A separate user token or client login does not by itself prove separate warehouse row access.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What must be checked before an agent invokes a workflow or app-building tool?

Inspect registered workflow effects, deployment roles, app-building scope and the selected regional or instance target. Tool annotations and plugin installation do not establish authority for every downstream action. A saved review preserves these questions; it does not test the buyer's deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a queue's exactly-once or deduplication feature prove one business effect?

Visibility leases, duplicate-send suppression and acknowledged-delivery guarantees address different stages. Check feature scope, identity, timing and acknowledgement results, then separately establish the external business commit. None of these descriptions alone proves an atomic transaction spanning the consumer and another service.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Who recovers an integration when event delivery fails or retries are exhausted?

Provider retry policies differ: some are bounded, some errors are not retried, and GitHub does not automatically redeliver failed webhooks. Verify retained failures, receiver idempotency, replay authority and operational ownership. Endpoint recovery alone does not prove missed events were reconciled.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence distinguishes data expiry from completed erasure?

An expired timestamp, missing query result, billing change and scheduled destruction each describe a different lifecycle state. Verify the service-specific deletion behaviour and actual object or version state, including separately retained copies. These documentation reviews do not determine legal erasure compliance.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does recovery restore the intended version and all service dependencies?

Recovery depends on original versions, retained data files, the window at deletion and surrounding permissions or integrations. A redrive may reuse the old workflow; a restored vault may lack previous integrations. Require version identity and dependent-service evidence before declaring recovery complete.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does serialised or scheduled automation guarantee every requested operation completes?

Queue modes, scheduling and task naming control admission and dispatch differently. Pending runs can be replaced, schedules can be missed or repeated, and named tasks do not establish downstream completion. Retain stable operation IDs and reconcile actual outcomes rather than counting schedules as completed work.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does selecting Falcon MCP modules prove the connection is read-only and authenticated?

Modules select a tool surface, while the read-only filter removes mutations and explicit tool additions can extend module selection. HTTP transport has no authentication by default and normally binds to loopback. A network-accessible deployment needs its separate authentication reviewed; Falcon API credentials alone do not authenticate incoming MCP callers.

VAREXIS-INDEX Single Request

Relevant public records

Does Checkmarx MCP access authorize every scanner and remediation operation?

The connector follows the authenticated tenant identity and licensed capabilities. It can trigger scans and retrieve findings; absence of project-deletion tools does not make it read-only. Local-directory scanning also needs the Checkmarx CLI and matching credentials. Supported authentication methods differ between clients.

VAREXIS-INDEX Single Request

Relevant public records

Does a Socket MCP dependency score establish that my application is safe to deploy?

The documented connector retrieves package security and quality information. Hosted access uses OAuth; the local deployment requires a token with packages:list. A score concerns the supplied dependency identity, not an independently tested application. Client rules can request checks but do not establish that every dependency was checked or a deployment was blocked.

VAREXIS-INDEX Single Request

Relevant public records

Does a local Endor Labs MCP process keep analysis offline or prove reachability?

The stdio process runs locally but calls the Endor Labs cloud for security context. Its documented MCP findings are not function-level reachability or action-policy-filtered results. Tools can run scans and code-diff reviews; the latter needs Enterprise enablement and a namespace. A documentation-only connector is a separate interface.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling CloudWatch masking hide sensitive content in every stored log?

Data protection detects and masks matching data as it is ingested. Earlier log events are not masked by a newly applied policy, and principals with logs:Unmask can view unmasked content. This is a presentation and access-control boundary, not evidence that the original content was erased.

VAREXIS-INDEX Single Request

Relevant public records

Does Datadog sensitive-data scanning prove raw content never leaves our environment?

Cloud scanning receives data in the Datadog backend before redaction. Scanning within the customer environment is a different deployment choice. The supported fields differ across logs, APM, RUM and events, and optional sampling reduces the scanned fraction. A masked interface alone does not establish pre-egress redaction or complete coverage.

VAREXIS-INDEX Single Request

Relevant public records

Does Snowflake Dynamic Data Masking replace the underlying sensitive values?

Dynamic Data Masking applies policy at query time. Depending on conditions, execution context and role hierarchy, a query can receive raw, partial or fully masked values. The feature requires Enterprise Edition or higher. Its presence does not establish erasure of source values or the effective output for every identity.

VAREXIS-INDEX Single Request

Relevant public records

Does replacing raw-data access with Masked Reader immediately hide earlier query results?

BigQuery documents a query-cache caveat when a user queries raw data, then loses Fine-Grained Reader and gains Masked Reader within the cache period. An identical query can still return cached raw data. Masking rules and base table permissions also matter; a role-change screenshot does not establish every result is masked.

VAREXIS-INDEX Single Request

Relevant public records

Does a CODEOWNERS file prove the right owner must approve every change?

Code-owner review must be required through the applicable branch controls. Invalid lines are skipped, later matching patterns take precedence, and owners need suitable repository access. A file in the repository therefore does not prove complete matching or enforced review of the target branch.

VAREXIS-INDEX Single Request

Relevant public records

Does a green pull-request check prove the queued merge combination passed?

A merge queue creates a temporary combined change with a different SHA. GitHub Actions must handle merge_group for required checks; third-party CI must handle the queue branch. A pull-request result is not automatically evidence for that combined state, and missing required reports can prevent the merge.

VAREXIS-INDEX Single Request

Relevant public records

Does a GitLab approval count prove independent review of the latest revision?

Approval settings separately govern authors, committers, rule overrides and reset behaviour after changes. Committers can approve by default unless restricted. Changed diffs normally reset approvals, but that behaviour can be changed. Counts alone do not identify reviewer independence or the revision accepted.

VAREXIS-INDEX Single Request

Relevant public records

Does an approved GitLab deployment mean the deployment job has run?

Protected-environment approvals allow a deployment to proceed, but the job must then be run manually. Pipeline-triggerer self-approval is separately configurable, and administrators can approve or reject deployments. Approval state is not execution success or proof of the resulting environment.

VAREXIS-INDEX Single Request

Relevant public records

Does disabling a KMS key immediately stop every read of the protected data?

Disabled customer-managed keys cannot perform KMS cryptographic operations, subject to eventual consistency. Resources already using data keys are not affected until they need KMS again, for example to decrypt a data key. Disabling the parent key is not evidence that every application has discarded plaintext or cached key material.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling rotation for a non-database secret prove the external credential changed?

Lambda-based rotation must update credentials in both Secrets Manager and the target service. The generic function needs service-specific code, permissions and network access. A configured schedule or newly stored value alone does not establish a successful external change or that applications use the replacement.

VAREXIS-INDEX Single Request

Relevant public records

Does denying GetParameter prevent an agent from reading the current parameter value?

Parameter Store authorizes retrieval operations separately. GetParameterHistory can expose the current version as well as earlier values, including SecureString values when decryption is permitted. A denial of other retrieval actions is not evidence that the history path is closed. Parameter and KMS permissions require joint review.

VAREXIS-INDEX Single Request

Relevant public records

Does a clean IAM policy-validation result prove the deployed role has only intended access?

Policy validation checks grammar and AWS best-practice findings. It does not itself execute the buyer workflow or establish the combined effect of every deployed grant. A separate custom check can compare new access with a baseline; AWS still calls for testing new or edited policies before production use.

VAREXIS-INDEX Single Request

Relevant public records

Does a Teleport login also authorize the upstream MCP service?

Some upstream servers need a separate OAuth token. Teleport still applies its own roles and tool permissions, while the upstream token satisfies that service. The documented login stores credentials locally and contacts the authorization server from the workstation. Changing the upstream URI requires a new login.

VAREXIS-INDEX Single Request

Relevant public records

Does an unavailable admission webhook always stop a Kubernetes change?

Failure policy controls webhook errors: Ignore permits the API request to continue, while Fail rejects it. This differs from a valid webhook response that explicitly denies the request, which is rejected regardless of failure policy. Matching rules and selectors also determine whether the webhook is called.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Kubernetes auditing prove every request body is retained?

The first matching audit rule selects the level. None omits events; Metadata excludes bodies; Request and RequestResponse include different content. Policy and stage exclusions govern coverage, and omitting the API-server audit-policy flag means no policy-based events are logged. Export and retention are separate evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does an assigned Azure policy prove non-compliant changes are blocked?

DoNotEnforce evaluates compliance without enforcing the policy effect. Disabled effect is different because it avoids evaluation. Assignment exclusions and scoped overrides also matter. Remediation tasks for deployIfNotExists can still be started in DoNotEnforce mode; that mode is not a blanket no-change guarantee.

VAREXIS-INDEX Single Request

Relevant public records

Does a new Google organization policy automatically correct existing violations?

Organization policies are usually not retroactive unless the specific constraint says otherwise. A service already in a newly prohibited state can continue its earlier behaviour and require separate correction. Constraint-specific applicability and dry-run evidence matter; assignment alone does not establish that old resources were remediated.

VAREXIS-INDEX Single Request

Relevant public records

Does AWS Config daily recording preserve every resource configuration change?

Daily recording captures the most recent state over the preceding day when it differs from the previous recorded configuration. Continuous recording and resource-type selection are separate settings. A daily record is not a complete transition history, and unsupported or unselected types remain outside the asserted coverage.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling S3 Block Public Access remove the old public grants?

The settings can reject new public grants or ignore their effects without rewriting existing ACLs and policies. Their behaviours differ, and the most restrictive applicable combination governs access. A blocking setting is not evidence that underlying grants were cleaned up or that every non-public access path is appropriate.

VAREXIS-INDEX Single Request

Relevant public records

Does a completed AWS Backup restore test prove the application works?

Restore-test completion can trigger a separate, optional validation workflow. The buyer defines checks such as a health endpoint and reports their result. A COMPLETED restore job and a successful workload validation are distinct evidence; the sample validation code is not itself proof that useful checks were implemented.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting an RDS instance also remove every recoverable database copy?

Deletion offers separate choices for a final snapshot and retained automated backups. Earlier manual snapshots and a created final snapshot remain. Retained automated backups follow the retention period effective at deletion. Instance absence alone therefore does not establish removal of all recovery copies.

VAREXIS-INDEX Single Request

Relevant public records

Does a Vault retention arrangement survive deletion of the user or required licence?

Vault requires appropriate licences for users and administrators. The overview warns that deleting a user or required licence can irreversibly purge data and remove Vault availability. Retention rules act on supported service data; an export or retained matter should not be assumed to cover an unverified offboarding change.

VAREXIS-INDEX Single Request

Relevant public records

Does a short deletion policy prove Microsoft 365 content will be permanently removed on that date?

Ordinary retention conflict rules favour retention over deletion and the longest retention period. Deletion labels and policies have further precedence rules. Priority cleanup is a documented exceptional path. A short deletion setting alone does not determine the effective outcome for an item subject to other retention or hold conditions.

VAREXIS-INDEX Single Request

Relevant public records

Does an ILM minimum age mean each log is deleted that long after its event timestamp?

After rollover, ILM phase minimum ages use the previous index rollover time rather than its creation time. The policy acts on indices, while individual events can have different timestamps. A phase-age setting alone is not evidence of exact per-event deletion timing.

VAREXIS-INDEX Single Request

Relevant public records

Does any valid Cosign signature establish the supplier artifact we intended to accept?

Identity-based verification checks the expected certificate identity and OIDC issuer. Container verification normally checks the signed image digest; disabling claim checks changes what is established. A cryptographically valid signature without the intended identity and artifact binding is insufficient for the buyer acceptance decision.

VAREXIS-INDEX Single Request

Relevant public records

Does possessing SLSA provenance prove the package came from the expected build?

The reviewed SLSA v1.2 guidance requires verification against expectations: trusted builder identity, provenance signature, build type and external parameters. Unrecognized external parameters should fail verification. Merely retaining a provenance document does not perform those checks or establish the buyer-specific expected build.

VAREXIS-INDEX Single Request

Relevant public records

Does having no Dependabot alerts prove all dependencies are free of known issues?

Alerts depend on the default-branch dependency graph, supported ecosystems and advisories reviewed by GitHub. New disclosures can take time to appear, archived repositories are not scanned, and GitHub Actions SHA references are outside the documented semantic-version alert case. No alert is therefore not a complete dependency-safety verdict.

VAREXIS-INDEX Single Request

Relevant public records

Does ignore-scripts make every npm operation safe from project script execution?

In npm CLI v11, ignore-scripts suppresses package.json scripts during operations such as installation. Commands explicitly intended to run a script, including npm test and npm run, still run the requested script while omitting pre- and post-scripts. This setting is not an execution sandbox for later agent commands.

VAREXIS-INDEX Single Request

Relevant public records

What evidence is needed before connecting an agent to a security platform?

Check incoming caller authentication, the effective security-platform identity, enabled operations and licensed capabilities. A short tool list or absence of deletion tools does not establish a read-only workflow. These are documentation reviews; the buyer must verify the actual deployment before authorizing tenant access.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What can a dependency tool result establish before accepting a software supplier?

Identify exact dependency inputs, supported coverage, result type and disclosure destination. Package scores, MCP findings and dependency alerts do not by themselves prove application reachability, complete deployed inventory or a safe release. Free previews expose the full review; paid retrieval preserves its dated source basis.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does masking prevent sensitive data from reaching a provider or an authorized reader?

Locate masking in the data flow and identify who can retrieve raw values. Ingestion-time detection, cloud redaction, query-time masking and cached results have different boundaries. Require source-side and identity-specific evidence for the intended claim; none of these features alone proves erasure or complete detection.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a recorded approval establish independent acceptance of the release that ran?

Confirm ownership matching, enforced review rules, independent approvers and the exact tested revision. A merge-group SHA differs from an isolated pull request, and deployment approval differs from completed execution. Preserve these identities separately when assessing a supplier release process.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What proves an agent credential change actually changes effective access?

Check the consuming service, alternate retrieval paths, cached keys and separate upstream identity. A changed secret, disabled parent key or proxy login describes only part of the access path. Require operation-specific evidence before treating credentials as rotated, revoked or limited.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a valid or assigned policy prove a supplier control is enforced?

Static validation, assignment, enforcement and remediation are different states. Check effective mode, matched requests, fail-open behaviour, retained grants and existing-resource exceptions. These reviews supply decision questions rather than a deployment verdict or a recommendation to change production controls.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an audit or inventory record provide the complete change evidence we need?

Identify whether the source records request events, selected bodies or periodic resource states. Ordered audit rules can omit events or payloads; daily configuration recording can omit intermediate changes. A complete review needs coverage, delivery and retention evidence for the specific question.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence distinguishes retained copies from proven recovery or completed deletion?

Identify retained copies, account and licence dependencies, effective policy precedence and lifecycle clocks. Separately verify restored workload behaviour. A completed restore, missing instance, configured deletion date or retained matter each answers only part of a supplier-exit decision.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does signed build evidence authorize an agent to execute the package?

Verify the expected signer, artifact and build parameters, then separately authorize execution. Origin evidence does not establish software safety. Disabling install scripts does not stop an explicit npm script command, so agent execution remains a distinct permission decision.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does Tenable Hexa AI MCP only read vulnerability findings?

Tenable documents both retrieval and state-changing operations, including tagging assets, creating dashboards and launching scans. The hosted connector uses Tenable API keys and requires an eligible Tenable One licence and enabled access. The buyer supplies the AI client; its handling of returned exposure data needs a separate review.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting Aikido MCP prove all generated code and repository issues were checked?

Tools distinguish files on disk, supplied code content, dependency manifests and scoped issue retrieval. Issue filters and pagination affect the returned subset. The Copilot cloud-agent integration uses a personal access token because browser login is unavailable there. An installed connector or prompt instruction does not prove a scan ran on every change.

VAREXIS-INDEX Single Request

Relevant public records

Does a Snyk ignore rule establish that a vulnerability was fixed?

The ignore command changes policy treatment of an issue; it does not document a code fix. Paths and expiry determine scope. The .snyk issue-ignore mechanism is not supported for Snyk Code, which has a separate workflow. An invalid expiry can leave an ignore in place indefinitely, so inspect the effective policy.

VAREXIS-INDEX Single Request

Relevant public records

Does a SonarQube token used by a scanner have only analysis permissions?

User tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.

VAREXIS-INDEX Single Request

Relevant public records

Does a resolved GitGuardian incident prove the exposed credential was revoked?

Integrated revocation requires a supported provider, a valid secret and Full Access to the incident. The documented auto-resolution path also depends on a playbook. Many provider APIs do not directly confirm revocation; GitGuardian uses later validity checks. Preserve the revocation and validity evidence separately from the incident label.

VAREXIS-INDEX Single Request

Relevant public records

Does an unknown GitHub secret-validity result mean the credential is inactive?

GitHub checks supported secrets by contacting issuer APIs and may need host or URL context. Results can be active, inactive or unknown. Coverage varies by provider. An unknown result does not establish inactivity, and enabling verification involves disclosure to the issuer rather than a wholly local check.

VAREXIS-INDEX Single Request

Relevant public records

Does Trivy --offline-scan guarantee no network access and current vulnerability data?

The air-gap guide treats remote Java identification, database availability, version checks and telemetry separately. The offline-scan flag prevents remote dependency-identification requests; it is not an all-network switch. Database acquisition and freshness need their own evidence. Version checks and telemetry have independent disabling controls.

VAREXIS-INDEX Single Request

Relevant public records

Does an empty Semgrep findings list prove every relevant file was scanned?

File or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.

VAREXIS-INDEX Single Request

Relevant public records

Does configuring the OpenTelemetry redaction processor prove every sensitive attribute is masked?

The processor supports key and value policies with explicit exceptions. Ignored keys pass without redaction; allowed values are not masked. Enabling allow_all_keys disables the key allowlist but still applies blocked-value rules. Review the effective exceptions and processed attributes before treating the processor name as evidence of complete removal.

VAREXIS-INDEX Single Request

Relevant public records

Can a Vector remap error send the original sensitive event downstream?

By default, a processing error forwards the original unmodified event because drop_on_error is false. Explicit aborts have a separate drop_on_abort setting. Rerouted dropped events can also carry original data. Review normal, error and dropped outputs separately before relying on a remap transformation as a disclosure barrier.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful ingest pipeline prove the redact processor changed the document?

The redact processor can quietly leave a document unchanged when skip_if_unlicensed is enabled and the licence does not support it. Conditional execution and failure handling also affect what runs. The trace_redact option can mark actual redaction, but absence of that marker alone is not a complete coverage assessment.

VAREXIS-INDEX Single Request

Relevant public records

Does a clean Presidio result prove a document contains no sensitive information?

Presidio combines configurable recognizers and can use external detection models. Its maintainers explicitly warn that automated detection does not find all sensitive information. The selected recognizers, languages and input types need buyer validation; a clean result cannot alone establish complete anonymization or permission to disclose the document.

VAREXIS-INDEX Single Request

Relevant public records

Does Macie automated discovery prove every object in an S3 bucket was inspected?

Automated discovery evaluates bucket inventory and selects representative objects through sampling. Discovery jobs allow more targeted scope and depth. The existence of automated discovery or no findings does not establish exhaustive inspection. Keep selected objects, configured identifiers and analysis results distinct from the total bucket inventory.

VAREXIS-INDEX Single Request

Relevant public records

Does tokenizing data with Sensitive Data Protection permanently erase the original meaning?

AES-SIV and format-preserving encryption support re-identification with the required key and context. HMAC-SHA-256 is a separate one-way option. Deterministic transformations can preserve links between records. Review the selected method and who can re-identify or correlate values; tokenization alone is not proof of erasure.

VAREXIS-INDEX Single Request

Relevant public records

Does a Purview DLP simulation alert prove the attempted transfer was blocked?

Simulation runs policies without actual enforcement and reports matched items and alerts separately. It helps evaluate policy impact but does not prove that a transfer was prevented. Procurement should distinguish simulation evidence from the active policy state and observed enforcement in the intended workload.

VAREXIS-INDEX Single Request

Relevant public records

Does assigning a masking tag prove its policy governs every tagged column?

Tag-based masking depends on the column type matching a policy signature; a tag can hold one masking policy per supported type. If a column also has a directly assigned masking policy, that direct policy takes precedence. Review the effective policy per column rather than treating tag presence as sufficient evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does a passing required GitHub check prove its test job actually ran?

Required checks accept success, skipped and neutral conclusions. A job skipped by a condition can report success, while a whole workflow skipped by path or branch filtering can remain pending. Review job execution and the applicable commit, not just the merge badge, before claiming a release passed a specific test.

VAREXIS-INDEX Single Request

Relevant public records

Can a reusable GitHub workflow grant itself broader GITHUB_TOKEN permissions than its caller?

Nested reusable workflows can retain or reduce the caller token permissions, not elevate them. The actual permission chain therefore matters when diagnosing an operation or reviewing claimed isolation. This constraint concerns GITHUB_TOKEN; it does not establish the scope of other credentials supplied to the job.

VAREXIS-INDEX Single Request

Relevant public records

Does passing secrets to one reusable GitHub workflow automatically pass them to every nested workflow?

Secrets are passed only to the directly called workflow. In a caller-to-intermediate-to-nested chain, the intermediate workflow must also forward the relevant secrets. Explicit mappings and secrets: inherit have different breadth. Review each call boundary without exposing the values when assessing credential disclosure.

VAREXIS-INDEX Single Request

Relevant public records

Does a valid GitHub OIDC token prove an approved reusable deployment workflow ran?

For reusable workflows, ordinary workflow and ref claims describe the caller, while job_workflow_ref identifies the called workflow. Cloud trust policies must use the supported claim or subject conditions for the intended restriction. Token validity alone does not establish that the buyer configured an approved-workflow boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does reusing an artifact name mean a later download contains the same approved build?

The upload-artifact documentation describes immutable artifacts and an overwrite option that deletes and replaces the named artifact with a new ID. A name alone is therefore not a durable identity. Bind acceptance to the artifact ID, digest and producing run, and distinguish retention availability from content identity.

VAREXIS-INDEX Single Request

Relevant public records

Does a manual GitLab job necessarily block release until someone approves it?

Manual jobs can be optional or blocking. Outside rules, when: manual defaults to allow_failure true; inside rules, its default is false. Explicit configuration can alter the outcome. A pipeline can succeed despite optional manual-job failures, so inspect the effective gate rather than relying on the manual button.

VAREXIS-INDEX Single Request

Relevant public records

Does GitLab needs:project wait for the current upstream pipeline before downloading its artifact?

needs:project retrieves artifacts from the latest successful specified job for the selected ref. It does not wait for an already-running pipeline on that ref. A consumer can therefore receive an earlier successful result. Record the producing job, commit and digest before equating that artifact with the current release.

VAREXIS-INDEX Single Request

Relevant public records

Does publishing a Docker provenance attestation keep build arguments private?

The min mode omits build-argument values, while max mode contains additional build detail including argument values and the Dockerfile. Secrets should use the documented secret mechanism rather than build arguments. Review the actual attestation and intended audience; provenance presence alone does not establish confidentiality or an approved build.

VAREXIS-INDEX Single Request

Relevant public records

What should an agent verify before scanning private code or security assets?

Identify the account, effective credential grants, authorized inputs and external client handling. A scanning connector can initiate work or expose sensitive context; its label does not establish read-only access or complete execution. Preserve the exact permission and input basis if a saved review is needed.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a clean security report prove full coverage and completed remediation?

Check excluded scope, ignored findings, source freshness and dated remediation evidence separately. A missing finding, closed incident or unknown validity state is not proof of a fix or complete coverage. These documentation reviews explain the evidence to request; they do not rescan a supplier or validate a credential.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can sensitive data survive redaction through exceptions or processing failures?

Review matching coverage, policy exceptions, licence-dependent skips and every failure output. A configured processor or successful pipeline does not prove complete sensitive-data removal. Require representative output and residual-risk handling for the intended disclosure; payment preserves this review rather than testing the pipeline.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence distinguishes data discovery, reversible masking and enforced prevention?

Sampled discovery, reversible tokens, simulated DLP and query masking establish different things. Identify inspected scope, key authority, active enforcement and the effective per-column policy. None alone establishes erasure or universal prevention. The free answers provide the distinctions; a paid snapshot retains their dated source basis.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a reusable release workflow prove approved identity and mandatory checks?

Inspect actual check execution, effective token permissions, per-hop secret forwarding and cloud trust conditions. A successful badge, valid token or manual button is insufficient by itself. Preserve platform-specific evidence: GitHub and GitLab controls are not interchangeable, and the buyer configuration has not been tested here.

VAREXIS-INDEX Evidence Receipt

Relevant public records

How can an agent check that a retrieved build is the artifact that was approved?

Bind approval to the producing run, source revision and artifact digest. Reused names and moving references can select replacement or earlier successful objects. Inspect provenance content and audience separately from identity: more metadata can expose build inputs without proving approval. A saved review preserves these questions, not the build itself.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Code-scanner access and findings?

Review access before connecting a scanner and interpret what its findings establish. Six dated documentation reviews compare SonarQube server filters and token scope, Snyk folder execution and ignore policies, and Semgrep invocation and scan exclusions. They preserve the evidence still needed before accepting a clean report or a claimed fix. They do not test your repository, credentials or deployment.

VAREXIS-INDEX Single Request

Relevant public records

Telemetry redaction and data flow?

Review where sensitive data can remain or leave a pipeline despite a redaction claim. Five dated documentation reviews cover OpenTelemetry exceptions, Vector error paths, Elastic licence skips, Presidio detection limits and Datadog scanning location. They keep configuration evidence and unresolved coverage questions with the source versions. They do not establish complete removal, regulatory compliance or permission to disclose data.

VAREXIS-INDEX Single Request

Relevant public records

GitHub release acceptance evidence?

Review whether approval and execution evidence is bound to the artifact being accepted. Five dated documentation reviews connect GitHub code-owner enforcement, skipped checks, reusable-workflow OIDC identity and artifact replacement with Cosign signer and digest verification. They preserve the buyer evidence still required for the exact revision and artifact. They do not approve a release, verify your configuration or certify software safety.

VAREXIS-INDEX Single Request

Relevant public records

Check a GitHub + Playwright integration plan?

Evaluate declared GitHub-hosted remote MCP and local Playwright tool inventories against a frozen review matrix. The reusable local checker flags scope and permission conflicts, unsupported operations and missing verification requirements, with source-bound JSON and CI exit codes. It does not connect to tools or verify their behaviour. Complete source evidence and concise demonstrations remain free. Operational schemas and runnable examples accompany the existing licensed package, supplied through the selected paid offer or eligible subscription.

VAREXIS-INDEX Single Request

Relevant public records

Check declared tool permissions, authority and changes before integration?

Compare exact actions, resources and recipients across GitHub, Playwright, Notion and Slack declarations; identify authority conflicts, changes and missing verification. A local validation pass describes supplied declarations only; it does not inspect effective permissions, verify records exist, enforce policy, certify compliance or approve deployment. Source evidence and a concise product summary remain free. Exact operational schemas and runnable cases accompany the licensed package.

Agent Tool Admission & Permission Control

Relevant public records

Check whether a declared event inventory can explain an agent action?

Link identity, authorization, action and outcome declarations; report missing events, conflicting references and unresolved export, retention or recovery coverage. A local validation pass describes supplied declarations only; it does not inspect effective permissions, verify records exist, enforce policy, certify compliance or approve deployment. Source evidence and a concise product summary remain free. Exact operational schemas and runnable cases accompany the licensed package.

Agent Audit & Evidence Coverage

Relevant public records

Can an Attio research assistant also change CRM records?

Attio documents OAuth access as the connecting user, including record and note changes, task deletion and list updates. Existing workspace permissions apply. Connecting for research does not establish approval for these actions or the external assistant's handling of CRM content.

VAREXIS-INDEX Single Request

Relevant public records

Can I connect a Front drafting assistant without allowing it to send?

Front distinguishes read, write and send permissions. Draft creation does not send a message; sending requires the separate send capability and the authorizing teammate's access. Its custom connection requires a confidential OAuth client, and permission changes require reauthorization.

VAREXIS-INDEX Single Request

Relevant public records

Are the remote and local SaaS Manager MCP connections equally read-only?

The remote service permits reads only. The local server defaults to reads but can enable writes when the API client also permits them. Authentication uses client credentials to obtain a short-lived bearer token; remote dynamic client registration is not supported.

VAREXIS-INDEX Single Request

Relevant public records

Does connecting Nylas MCP give an agent only mailbox-reading access?

Nylas exposes mail, calendar, contacts and Notetaker operations, including state-changing actions. It requires an API key and connected account grant, with regional endpoints. The guide recommends narrowly scoped IAM keys for production agents; a working connection alone does not establish a read-only or single-account boundary. Sending requires the documented confirmation step; it does not replace owner approval or IAM restrictions.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent treat no Google Drive search match as proof a document does not exist?

Drive can mark searches across large combined corpora as incomplete. The publisher advises checking incompleteSearch and narrowing the corpus when results were omitted. Query scope and returned fields therefore matter; no match alone does not establish absence from the organisation.

VAREXIS-INDEX Single Request

Relevant public records

Can a Notion search export establish every document an integration can access?

Notion says search is not guaranteed to enumerate everything a connection can access, and indexing is not immediate. Directly shared pages or databases have a documented return guarantee, but general search results are not a complete inventory. A missing match is not proof of deletion or lack of access.

VAREXIS-INDEX Single Request

Relevant public records

Can a Slack bot token search private conversations from an external assistant?

Slack's Real-time Search API requires a user token for private conversation data or use outside the Slack client. Bot-token calls require an action token. File search permission alone does not grant file-content download; that additionally needs files:read.

VAREXIS-INDEX Single Request

Relevant public records

Does consenting to Sites.Selected give an application access to a SharePoint site?

Selected permissions require consent, an explicit resource assignment and a token containing the relevant scope. Consent alone provides no selected-resource access. Delegated access also intersects with the user's permissions; applicable assignments and overlapping scopes must be considered when evaluating access.

VAREXIS-INDEX Single Request

Relevant public records

Does an Azure AI Search security filter authenticate the user named in the filter?

The documented security-filter pattern compares principal strings to indexed values; those strings do not authenticate or authorize the caller themselves. The application must establish caller identity and consistently apply the filter. This pattern is distinct from native ACL support.

VAREXIS-INDEX Single Request

Relevant public records

Does a Bedrock web-crawler knowledge base preserve the source site's access controls?

The crawler guide warns that synced data is retrievable by anyone with bedrock:Retrieve permission, including content with source access controls. The source's permission model must not be assumed to survive ingestion. Review the knowledge-base audience and admitted content separately.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a source file immediately remove it from a Bedrock managed knowledge base?

The managed knowledge-base guide requires synchronization after source additions, changes or removals. A sync request has an ingestion-job identity, status and document statistics; starting one is not evidence that deletion has completed. Scheduled or on-demand configuration determines when work begins.

VAREXIS-INDEX Single Request

Relevant public records

Does removing a Loopio user or project immediately remove it from Glean search?

Glean documents daily participant updates and weekly full synchronization, with deletions detected by the full sync. Its page also warns that removed-user or deleted-project results can persist until that full sync, while its timing table describes daily access updates. The applicable access window needs clarification rather than an immediate-removal assumption.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful Microsoft Graph sendMail response prove the recipient received the message?

sendMail returns 202 Accepted without a response body. Microsoft states this does not establish completed processing; Exchange Online limits and throttling still affect delivery. An agent should distinguish accepted submission from verified delivery.

VAREXIS-INDEX Single Request

Relevant public records

Does an agent that only sends Gmail messages need permission to read and delete the mailbox?

Gmail publishes separate scopes for sending, managing drafts and broader mailbox operations. gmail.send permits sending without read or modify privileges; gmail.compose includes managing drafts and sending. A send-only task does not by itself justify full-mailbox scope.

VAREXIS-INDEX Single Request

Relevant public records

Does creating a Calendar event prove its meeting link is ready?

Conference generation can be asynchronous: the immediate event response may show pending before conference creation succeeds and entry points appear. The guide also requires a full event sync before enabling conference support in an existing client that stores events locally, to avoid losing existing conference data.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent overwrite a newer Zendesk ticket update using an old preview?

Zendesk documents safe updates using safe_update with the last known updated_stamp. A newer ticket change can cause the attempted update to be rejected; the client must obtain fresh state and handle the conflict. An earlier preview is not proof that the ticket remains unchanged.

VAREXIS-INDEX Single Request

Relevant public records

Does HTTP 200 from Salesforce Composite prove every requested change committed?

Salesforce Composite returns subrequest results inside a top-level HTTP 200, including error cases. allOrNone controls rollback; with it false, independent subrequests can continue while dependent ones do not. Nested collection settings can also affect outcomes. Each relevant result must be interpreted.

VAREXIS-INDEX Single Request

Relevant public records

Does restoring a Microsoft Graph subscription recover every notification missed during an outage?

Graph lifecycle events distinguish reauthorization, removed subscriptions and missed notifications, with resource-specific support. Changes during a delivery pause can be lost from notification delivery; after restoring the subscription the application must separately fetch missed changes, such as through supported delta queries.

VAREXIS-INDEX Single Request

Relevant public records

Does a Gmail history 404 mean there were no mailbox changes?

Gmail history is available for a bounded period that can be shorter than expected. An out-of-range startHistoryId produces HTTP 404; the documented response is a full synchronization. Treating this as an empty change list would leave an unsupported coverage gap.

VAREXIS-INDEX Single Request

Relevant public records

Does a queued or delivered Twilio message prove that a customer read it?

Twilio distinguishes creation, sending, delivery and channel-dependent read receipts. Status callbacks can report delivery failures and error codes. Read events depend on channel support; a queued message or a delivery status alone is not a universal read confirmation.

VAREXIS-INDEX Single Request

Relevant public records

Does disabling a Google service-account key revoke tokens already issued from it?

Google states that disabling a service-account key does not revoke short-lived credentials already issued from it. The guide distinguishes the key from the service account represented by those credentials. A key-disabled result therefore does not by itself establish a completed access cutoff.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent infer GitHub access from the scopes listed in an OAuth installation link?

GitHub distinguishes requested scopes from granted scopes: users can reduce access, including after authorization. Scope lists are also normalized, omitting narrower scopes implied by a broader one. Evaluate the current grant and its meaning rather than counting requested scope names.

VAREXIS-INDEX Single Request

Relevant public records

Does GitLab.com group SCIM deprovisioning delete the user's GitLab account?

After the identity provider sync, group SCIM removes access to the top-level group and its subgroups and projects. The GitLab.com account remains, and the linked SAML identity is retained. Enabling SCIM also does not automatically remove existing users without a SAML identity.

VAREXIS-INDEX Single Request

Relevant public records

Is an Okta API token's authority fixed when it is created?

Okta API tokens follow the creating user's permissions, including later permission changes, and require that user to remain active. Their inactivity expiry renews with use. Procurement should check the owner lifecycle and effective privileges, rather than assuming a fixed permission grant or fixed maximum lifetime.

VAREXIS-INDEX Single Request

Relevant public records

Does revoking one Google OAuth token only disconnect that one client?

Google documents revocation of the associated user's project authorization across previously granted scopes and tokens for clients under that project. This can be broader than a single client. The guide also notes that full effect may take time after a successful response.

VAREXIS-INDEX Single Request

Relevant public records

Does a Slack token-revocation event prove the whole app was uninstalled?

Slack says an app is not uninstalled until its final user and bot tokens are revoked. app_uninstalled and tokens_revoked events have no guaranteed sequential order. Correlate the app and workspace and distinguish an individual revoked token from complete uninstall.

VAREXIS-INDEX Single Request

Relevant public records

Does an empty external Access Analyzer report prove nobody else can access a resource?

External findings are defined relative to the selected account or organization as a zone of trust. Sharing within that zone does not produce an external finding. Internal and unused access are separate analyses; the absence of an external finding does not establish absence of internal access or buyer suitability.

VAREXIS-INDEX Single Request

Relevant public records

Does a Cloudflare token's Read or Edit label establish its complete access boundary?

Cloudflare configures token permissions separately from selected resources. Its guide defines Edit as broader create/read/update/delete/list access, while client-IP filtering and token lifetime are optional restrictions. A label alone does not establish which zones, accounts, networks or duration were selected.

VAREXIS-INDEX Single Request

Relevant public records

What should an agent check before connecting CRM, inbox or SaaS-management tools?

Identify the operator, effective user or API identity, regional endpoint, read/write capability and any separate send or confirmation requirement. Attio, Front, SaaS Manager and Nylas expose different action boundaries. A successful connection is not authority to mutate business data. Inspect each full profile free; saving retains this dated review, not a tested deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can an agent rely on enterprise search results as a complete accessible-document inventory?

Check corpus completeness, indexing delay, search identity and the combination of consent and resource grants. Drive and Notion document search limitations; Slack distinguishes client context and token requirements; Graph Selected access needs explicit resource assignment. Missing results do not establish document absence or access revocation.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence shows that an AI knowledge connector respects access changes and deleted content?

Separate caller authentication, retrieval audience, indexed permission metadata and synchronization completion. A filter string is not authentication; source access does not automatically establish retrieval restrictions; deletion and access updates may await connector processing. Preserve unresolved timing differences and require evidence for the actual connector.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What should an agent verify before reporting that a business action completed?

Match the observed outcome to the requested task: granted send scope, accepted submission, conference readiness, collision handling, each composite subresult, notification-gap recovery and channel delivery status are different evidence. Reconcile uncertain results before retrying. These sources support interpretation, not execution or a delivery guarantee.

VAREXIS-INDEX Evidence Receipt

Relevant public records

How can an agent check whether a service credential still has the intended authority?

Review current granted scopes, owner permissions, resource restrictions and issued credentials separately. Disabling a Google key does not itself revoke issued short-lived credentials; GitHub scope normalization can hide implied permissions; Okta tokens follow their owner; Cloudflare restrictions need actual configuration evidence. No credential is tested by this review.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence distinguishes app offboarding from account deletion or complete access removal?

Define the removal boundary first. GitLab.com group SCIM leaves the account; Google OAuth revocation can span the user's project grant; Slack uninstall is distinct from one token revocation; an AWS external-access report omits sharing inside its trust zone. Require scope-matched completion evidence before stating all access is gone.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an allowed IAM simulation prove an agent can execute the production action?

The IAM simulator evaluates supplied policy and context without making the service request or returning its response. AWS documents differences from live behaviour. Editing a simulated policy also leaves the account policy unchanged.

VAREXIS-INDEX Single Request

Relevant public records

Can an AssumeRole session policy grant an agent permissions beyond its role?

AWS describes session permissions as the intersection of the role identity policy and supplied session policies. A session policy cannot add permissions beyond that role policy. The role trust policy separately controls who may assume the role.

VAREXIS-INDEX Single Request

Relevant public records

What evidence explains the authority an agent delegates when it passes an IAM role to a service?

PassRole permits assigning a role that a service can later assume. AWS distinguishes the role permissions, service trust and caller permission to pass it. PassRole is not a separate API event; the resource creation or modification event records the assignment.

VAREXIS-INDEX Single Request

Relevant public records

Does IfExists make an IAM deny harmless when the condition key is absent?

AWS documents that a negated condition such as StringNotEqualsIfExists in a Deny statement can still deny a request when the key is absent. The operator, statement effect and available resource context must be read together.

VAREXIS-INDEX Single Request

Relevant public records

Does an SCP allow statement give an agent permission to act in an AWS account?

Service control policies limit permissions without granting them. AWS states that SCPs affect member-account principals but not users or roles in the management account, and do not restrict service-linked roles. Other permission policies remain necessary.

VAREXIS-INDEX Single Request

Relevant public records

Can permission to edit Kubernetes roles or bindings be treated as ordinary configuration access?

Kubernetes restricts role creation to permissions the caller holds unless escalation is authorised. Binding creation similarly requires the referenced permissions or bind authority. These checks distinguish ordinary object edits from permission delegation.

VAREXIS-INDEX Single Request

Relevant public records

Do Kubernetes impersonation headers alone establish authority to act as another identity?

The API server authenticates the caller and checks impersonation privileges before evaluating the request with impersonated user information. The documented impersonate permission covers the kinds of attributes supplied, including user, group, UID and extra fields.

VAREXIS-INDEX Single Request

Relevant public records

Does changing a webhook authorisation policy guarantee every Kubernetes request immediately uses the new decision?

Kubernetes supports separate caching controls and lifetimes for authorised and unauthorised webhook responses. The configured cache can therefore affect when a fresh webhook decision is requested. Configuration syntax distinguishes disabling caching from setting a duration.

VAREXIS-INDEX Single Request

Relevant public records

Does a failing ValidatingAdmissionPolicy necessarily reject a Kubernetes request?

The binding selects validationActions. Kubernetes documents Deny as rejection, Warn as a client warning and Audit as inclusion in the request audit event. A validation failure must be interpreted with the binding action rather than as an automatic refusal.

VAREXIS-INDEX Single Request

Relevant public records

Can a successful OPA Data API response be interpreted as an allow decision?

OPA documents HTTP 200 with an omitted result field when a Data API document is undefined. HTTP success and the policy decision are separate. A caller must inspect the expected result rather than treating transport success as permission.

VAREXIS-INDEX Single Request

Relevant public records

Does publishing a newly signed OPA bundle prove that running agents use it?

OPA activates a signed bundle only after successful configured verification. On verification failure it retains the existing bundle and reports activation failure through status and error logging. Publication alone does not establish the active policy revision.

VAREXIS-INDEX Single Request

Relevant public records

Does a GitHub App installation token automatically have the narrow scope intended for one agent task?

GitHub allows repository and permission restrictions when generating installation tokens. Omitted restrictions inherit the documented installation or app scope, while requested rights cannot exceed the grant. The response reports token permissions, applicable repositories and expiry.

VAREXIS-INDEX Single Request

Relevant public records

Does projects.testIamPermissions produce a complete inventory of an agent identity's authority?

The Resource Manager method tests the caller against a specified project and explicit permission names. Wildcard permissions are not accepted. Its request scope must therefore be retained when interpreting the result; it is not a wildcard inventory of every possible action.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling Kubernetes auditing establish that every selected event reached storage?

Kubernetes documents event loss when a batch backend buffer overflows and exposes an audit error metric for export losses. Backend modes and size limits also shape collection. An enabled audit policy alone does not establish complete delivery.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent reconstruct an action chain from the order of CloudTrail records in a file?

AWS states that CloudTrail log files are not an ordered stack trace and events do not appear in a specified order. Record position therefore does not establish the causal sequence of API actions.

VAREXIS-INDEX Single Request

Relevant public records

Do repeated CloudTrail records necessarily mean an agent performed the action twice?

AWS documents that delivered CloudTrail logs can contain duplicate events, usually sharing the same eventID. A repeated record is therefore not by itself evidence of a repeated business action, and the identifier guidance is not an absolute deduplication guarantee.

VAREXIS-INDEX Single Request

Relevant public records

Does an empty destination log search prove that no matching Google Cloud action occurred?

Log sinks route entries according to inclusion and exclusion filters. Google also distinguishes intercepting and non-intercepting aggregated routing. A destination search reflects the applicable routing scope, not necessarily every entry received elsewhere in the hierarchy.

VAREXIS-INDEX Single Request

Relevant public records

Can a Log Analytics table be assumed to contain the original unfiltered event stream?

Azure Monitor transformations can filter or modify incoming data after the source delivers it and before the destination receives it. The data collection rule defines this processing. Stored rows can therefore reflect transformation choices rather than the original stream.

VAREXIS-INDEX Single Request

Relevant public records

Can sampled traces establish a complete history of agent actions?

OpenTelemetry sampling selects traces or spans for processing and export. Head and tail sampling make decisions at different points, and can be combined. A retained sample is not an exhaustive record of all actions or requests.

VAREXIS-INDEX Single Request

Relevant public records

Does an enabled Collector sending queue guarantee that telemetry eventually reaches the backend?

OpenTelemetry documents loss when a sending queue fills or its retry window expires. Persistent storage helps across restarts but has its own failure conditions. Queueing and retries improve resilience without establishing loss-free delivery.

VAREXIS-INDEX Single Request

Relevant public records

Does exporting a span prove that all its events, links and attributes were retained?

The OpenTelemetry SDK specification defines limits for span events, links and associated attributes. Content can be discarded when these limits are reached. A span that reaches the backend need not contain every item the application attempted to record.

VAREXIS-INDEX Single Request

Relevant public records

Does validating a GitHub webhook secret prove that a delivery has not already been processed?

GitHub distinguishes secret-based delivery validation from replay protection using X-GitHub-Delivery. Requested redeliveries keep the original delivery identifier. An authenticated payload therefore still needs delivery-identity handling before triggering another action.

VAREXIS-INDEX Single Request

Relevant public records

Should each Slack Events API delivery trigger a fresh agent action?

Slack assigns a globally unique event_id and retries failed delivery acknowledgements. Optional delayed events settings extend retry handling. Receipt attempts and logical events are different, so an integration should preserve event identity when deciding whether to act again.

VAREXIS-INDEX Single Request

Relevant public records

Can every Step Functions workflow be described as exactly-once execution?

AWS distinguishes exactly-once Standard workflow execution, at-least-once asynchronous Express execution and at-most-once synchronous Express execution. Express idempotency is not automatically managed. The selected workflow type is essential context for interpreting repeated or missing runs.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful asynchronous Lambda invocation rule out a duplicate event later?

AWS documents that asynchronous Lambda delivery can repeat the same event even when the function returns no error. Events can also expire or exhaust processing attempts. Function success alone does not establish unique delivery or a complete input history.

VAREXIS-INDEX Single Request

Relevant public records

Does Pub/Sub message ordering provide one global, duplicate-free agent action sequence?

Pub/Sub orders messages within an ordering key under its documented regional and subscription conditions, not across keys. Redelivery can also replay later messages for the same key, including acknowledged ones; dead-letter handling adds further qualifications.

VAREXIS-INDEX Single Request

Relevant public records

Does a crash-safe logical replication slot guarantee each change reaches a consumer only once?

PostgreSQL persists a logical slot position at checkpoints. After a crash it can return to an earlier position and resend recent changes. Clients are responsible for handling repeated messages; a slot does not know the receiver's processing state.

VAREXIS-INDEX Single Request

Relevant public records

Which evidence distinguishes a declared AWS permission from effective agent authority?

Separate simulated results, session restrictions, service-role delegation, missing context and organisational ceilings. Each describes a different part of authority. Read the source-linked reviews free, then request the specific buyer evidence; these reviews do not inspect effective access or enforce an action.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What should an agent declare before using delegated or impersonated authority?

Identify the original and effective identity, permission-delegation rights, issued token scope and exact probe target. Kubernetes delegation, GitHub token restrictions and Google permission probes address different boundaries. A declaration or successful probe does not independently validate the deployment.

VAREXIS-INDEX Evidence Receipt

Relevant public records

When does a policy evaluation fail to prove that an action was refused?

Check the cached decision window, binding action, dry-run flag, result body and active policy revision. A warning, undefined result, dry run or newly published bundle does not establish a production refusal. Current INDEX checks declarations only and does not provide or validate enforced allow/refuse decisions.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence is needed before calling an audit chain complete?

Review backend losses, ordering assumptions, duplicate records, routing filters and ingestion transformations. The surviving records alone cannot establish that every relevant action was captured or that file order proves causality. Preserve provenance and unresolved gaps when assembling a declared chain.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can an exported trace establish complete agent activity?

Separate sampling coverage, retained span content and transport delivery. A trace can be absent because of selection or loss, while a delivered span can still omit content because of limits. These documentation reviews do not inspect a buyer's telemetry pipeline.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence separates delivered events from actions performed once?

Preserve logical event identity, delivery attempts, workflow type, ordering scope and consumer progress. Authentic delivery, acknowledgement and checkpointing have different meanings across these services. Reconcile repeated or missing effects before claiming that an agent performed an action once.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a workflow permission declaration describe every job token without checking job overrides?

GitHub supports workflow-level and job-level GITHUB_TOKEN permissions. When individual permissions are specified, omitted permissions become none. The job configuration and applicable default and trigger restrictions therefore matter when describing the token used by an action.

VAREXIS-INDEX Single Request

Relevant public records

Does rerunning a GitHub job guarantee that a reusable workflow uses the same approved revision?

For reusable workflows referenced by a branch or tag, GitHub distinguishes rerun modes. Rerunning all jobs resolves the specified reference again; rerunning failed jobs or a specific job uses the called workflow commit from the first attempt. Record the resolved revision and rerun mode.

VAREXIS-INDEX Single Request

Relevant public records

Does id-token: write give a GitHub workflow write permission over cloud resources?

GitHub states that id-token: write permits requesting an OIDC token; it does not grant write access to other resources. The receiving provider evaluates token claims against its trust conditions. Resource authority still needs a separate declared permission basis.

VAREXIS-INDEX Single Request

Relevant public records

Does requiring a pull request prevent every authorised GitHub ruleset bypass?

GitHub rulesets can grant bypass to selected actors. The pull-request-only bypass mode requires a pull request but still lets the actor bypass protections when merging it. An active rule must therefore be read together with its targets and bypass list.

VAREXIS-INDEX Single Request

Relevant public records

Does permission to insert Notion content imply permission to read full objects or update existing pages?

Notion separates read, insert and update content capabilities. Insert capability permits creating content without granting full-object reading or existing-page updates. Comment and user-information capabilities are separate choices, so a generic write label obscures the actual declared operations.

VAREXIS-INDEX Single Request

Relevant public records

Does a Slack bot being absent from a public channel prove it cannot post there?

Slack provides chat:write.public for posting to public channels without joining them, alongside chat:write. Channel membership alone is therefore insufficient evidence of the bot's posting boundary. This posting capability does not itself establish permission to read conversation history.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent redirect a Slack incoming webhook by changing channel or username in its payload?

Slack documents that incoming webhooks use the configured channel, username and icon; payload overrides do not change them. The webhook URL is tied to its installed destination. Review that destination before sending rather than relying on a payload label.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assume it can undo every Slack message it sends by calling chat.delete?

Slack limits bot-token deletion to that bot's messages and user-token deletion to messages the user may delete. The method does not accommodate impersonation: a message sent impersonating another user cannot be deleted through that mechanism. Deletion authority needs its own review.

VAREXIS-INDEX Single Request

Relevant public records

Can a saved Playwright authentication-state file be treated as harmless test configuration?

Playwright warns that saved browser state can contain cookies and headers usable to impersonate the account. Loading that state starts a context already authenticated. Its custody and account scope therefore belong in the authority review, not merely the browser settings inventory.

VAREXIS-INDEX Single Request

Relevant public records

Does browserContext.route establish that every browser request passes through an agent's declared filter?

Playwright documents that browserContext.route does not intercept requests already intercepted by a Service Worker. It recommends blocking Service Workers when using request interception. A route handler declaration alone cannot establish complete network mediation for the browser context.

VAREXIS-INDEX Single Request

Relevant public records

Does a shared role session name alone preserve the original identity through an AWS role chain?

AWS distinguishes source identity from a role session name. Once set, source identity cannot change during the session and persists through role chaining. Administrators can require or constrain its value; the value's origin still needs an evidenced identity mapping.

VAREXIS-INDEX Single Request

Relevant public records

Do session tags automatically persist when an agent assumes another AWS role?

AWS STS does not pass session tags into later role sessions by default. Tags marked transitive persist during role chaining, with documented replacement behaviour for matching resource tags. Policies using tags therefore need the actual passed values and transitivity settings.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful GitHub REST list response establish that every matching evidence item was collected?

GitHub paginates large list responses and provides continuation URLs in the Link header. Increasing per_page changes page size, not the need to follow remaining pages. The requested endpoint, filters and completed pagination define the retrieved evidence set.

VAREXIS-INDEX Single Request

Relevant public records

Can Slack Audit Logs API records substitute for a transcript of what an agent read or posted?

Slack describes its Audit Logs API as a read-only view of supported organisational audit actions, not message-content monitoring. It covers a subset of possible audit events and does not determine whether an action was appropriate. A message transcript requires a separate evidence basis.

VAREXIS-INDEX Single Request

Relevant public records

Does receiving fewer Slack history messages than requested prove the conversation has no more evidence?

Slack warns that history responses may contain fewer items than the requested limit before history is exhausted. Cursor continuation and time bounds must be considered together. The inclusive option controls whether messages exactly at the supplied boundary timestamps are included.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent rely on the first Notion property response as the complete relation or rollup result?

Notion returns some property types as paginated lists and directs callers to continue until has_more is false. Rollups include calculation metadata, and every page must be read before using a calculated result. A first response can therefore be incomplete evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does updating one Logpush output option preserve every previously configured evidence field and format?

Cloudflare documents that an update replaces the entire output_options object; omitted options reset to defaults. Selected field names and timestamp formatting therefore need to be retained together. A partial update can change the evidence shape even while delivery continues.

VAREXIS-INDEX Single Request

Relevant public records

Does successful Logpush delivery prove the destination includes every event in the chosen dataset?

Cloudflare lets jobs filter dataset records using expressions and apply output sampling on top of filtering. Delivery success therefore describes the configured selection, not necessarily the whole dataset. The filter and sampling settings are part of any declared coverage claim.

VAREXIS-INDEX Single Request

Relevant public records

Can an exported OPA decision log be assumed to preserve the exact policy input and result?

OPA can erase or modify decision-log fields through a masking policy before upload or custom-plugin delivery. The log records erased or masked paths. A retained decision record can therefore differ from the original input or decision and needs that transformation context.

VAREXIS-INDEX Single Request

Relevant public records

Can an OpenTelemetry log observation timestamp be treated as the time the agent action occurred?

OpenTelemetry distinguishes Timestamp, measured at the event source, from ObservedTimestamp, measured when the collection system observes it. The source timestamp can be absent. Collection delay and clock provenance therefore matter when reconstructing an action sequence from logs.

VAREXIS-INDEX Single Request

Relevant public records

Can a saved CloudTrail event be treated as the final record without considering later addenda?

CloudTrail addenda can explain delayed delivery or correct missing or incorrect fields. For updated data, the addendum identifies updated fields and original request and event IDs. A reconstruction should retain these links rather than counting a correction as an unrelated action.

VAREXIS-INDEX Single Request

Relevant public records

Do Kubernetes audit records with the same auditID necessarily represent duplicate delivery?

Kubernetes generates an auditID for each request and records the handling stage on each audit event. One request can generate events at different stages. ResponseStarted applies to long-running requests; it is distinct from ResponseComplete, so stage-aware correlation is necessary.

VAREXIS-INDEX Single Request

Relevant public records

Which declarations define an automated GitHub workflow's authority?

Review job token permissions, the workflow revision selected for a rerun, downstream OIDC grants and ruleset bypass rights together. Bind declared authority to the execution context. The free reviews identify evidence to request; they do not inspect a repository or validate that its rules prevented an action.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What should be declared before an agent creates content or sends a message?

Separate content capabilities, posting destinations, channel membership and deletion authority. Notion insert permission, Slack public posting, installed webhook destinations and message authorship each change what can be claimed. A permitted send does not establish an available undo operation or owner approval.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What hidden context can change the authority of a declared agent session?

Review saved browser credentials, Service Worker routing boundaries, role-chain source identity and transitive session tags. Session configuration alone does not establish a complete authority boundary. These documentation reviews add context without expanding either licensed checker's supported profiles or providing runtime enforcement.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What makes a successful evidence retrieval incomplete?

Check list continuations, content-versus-audit scope, time boundaries, final property calculations and nested content depth. A successful or short response can still omit relevant evidence. Record the exact retrieved population and unresolved gaps before using it in a declared audit chain.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Which collection choices can remove fields or events from an audit record?

Retain output-option revisions, filtering and sampling settings, and masking provenance. Selected or transformed logs can be useful evidence while omitting events or original fields. Delivery and retention alone do not prove complete source fidelity; current INDEX checks the supplied declarations only.

VAREXIS-INDEX Evidence Receipt

Relevant public records

How should an audit chain distinguish timing, corrections and repeated records?

Keep event and observation clocks distinct, link later corrections to their originals, preserve export duplicate uncertainty and correlate request stages without discarding them. These reviews support careful reconstruction; they do not verify actual completeness, causal order or successful business outcomes.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does a successful Vault force-revoke establish that the backend credential can no longer be used?

Vault force revocation ignores errors from the secrets backend. Removing the lease entry therefore does not establish that the issued credential was disabled in the target system. The ordinary revoke API also distinguishes queued processing from synchronous completion.

VAREXIS-INDEX Single Request

Relevant public records

Does offline validation of a Kubernetes service-account JWT detect that its bound Pod was deleted?

An external service validating a service-account JWT offline does not check that its embedded object claims remain current. A token bound to a deleted object can still pass that validation until expiry. Kubernetes directs clients needing current bound-claim validation to the TokenReview API.

VAREXIS-INDEX Single Request

Relevant public records

Does revoking an input token automatically revoke every token obtained through OAuth token exchange?

RFC 8693 does not define a tightly coupled lifecycle between input and exchanged tokens. Input renewal need not change the output token, and revocation propagation depends on the implementation, token type and deployment. Token exchange alone is not evidence of cascading revocation.

VAREXIS-INDEX Single Request

Relevant public records

Does changing a GitHub App registration prove every existing installation has the new permissions?

Added repository or organization permissions require approval by each installing account; added account permissions require approval by each authorizing user. Updated grants do not take effect there until approved. GitHub documents permission removals as taking effect immediately.

VAREXIS-INDEX Single Request

Relevant public records

Does denying CreatePolicyVersion alone prevent an agent from changing the operative IAM policy?

For customer managed policies, CreatePolicyVersion can create and select a new default, while SetDefaultPolicyVersion can select an existing version. The selected default supplies the policy in effect for attached identities. AWS says both actions must be denied to prevent changes to that default.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent overwrite a conditional Google IAM policy without preserving its version and etag?

Google directs API and client-library callers working with IAM Conditions to use the version 3 policy representation and preserve its etag. Without the etag, IAM permits overwriting a version 3 policy with version 1, which removes the conditions. A successful write alone does not establish preserved restrictions.

VAREXIS-INDEX Single Request

Relevant public records

Can one failed SQS batch item cause an agent to repeat actions that already succeeded?

By default, a failed Lambda SQS batch makes all its messages visible again, including successfully processed items. Partial reporting requires ReportBatchItemFailures plus the failed message identifiers. An uncaught function exception still fails the entire batch; FIFO handling also retains failed and unprocessed items after the first failure.

VAREXIS-INDEX Single Request

Relevant public records

Does HTTP 200 for a Microsoft Graph batch prove every agent action in it succeeded?

A parseable Graph batch can return HTTP 200 while individual responses fail. Each response has its own identifier and status; throttling applies per request, and requests depending on a failed request receive 424. Recovery must use those individual results rather than the outer status alone.

VAREXIS-INDEX Single Request

Relevant public records

Does an HTTP 200 DeleteObjects response prove every requested S3 object was deleted?

S3 documents a DeleteObjects response containing both Deleted and Error entries under HTTP 200. Quiet mode suppresses successful entries, and deleting an absent key is also reported as deleted. The response must be interpreted against requested keys, version IDs and response mode.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful long-running-operation cancel request prove the Spanner operation stopped?

The documented CancelOperation call starts a best-effort asynchronous cancellation; the operation may still complete. GetOperation can establish its later state. Successful cancellation is represented by a CANCELLED error, while DeleteOperation only discards interest in the result and does not cancel the work.

VAREXIS-INDEX Single Request

Relevant public records

After a PostgreSQL serialization failure, is retrying only the last SQL statement sufficient?

PostgreSQL 18 directs applications to retry the complete transaction after a serialization failure, including the logic that chose statements and values. SQLSTATE 40001 identifies that failure. Other errors, such as unique violations, can be persistent, and a retry does not guarantee eventual completion.

VAREXIS-INDEX Single Request

Relevant public records

Does Run Command Success prove the intended change completed on every targeted machine?

Systems Manager reports plugin, invocation and aggregate command statuses separately. AWS documents Success cases with no matching tagged instances, tolerated invocation failures or a zero exit code despite prevented execution. The overall status therefore does not establish the intended change on every target.

VAREXIS-INDEX Single Request

Relevant public records

What evidence is needed to review agent access lifecycle, offboarding and permission drift?

Follow credential issuance and scope through expiry, revocation, offboarding and permission changes. Distinguish declared restrictions from current grants and residual access. Full source-linked evidence is free. Documentation review does not establish actual permissions, event completeness, deletion or settlement.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence distinguishes completed agent actions from partial failures, retries and recovery?

Reconcile action outcomes with source records, retry and recovery state, trace sampling and delivery, export errors and provenance coverage. Existing recovery evidence remains available. This collection does not establish actual event completeness or extend the local Audit Coverage checker. Full source-linked evidence is free. Documentation review does not establish actual permissions, event completeness, deletion or settlement.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does reusing an EC2 client token prevent duplicate creation after an agent changes Region or Availability Zone?

EC2 client-token idempotency is scoped regionally or zonally. RunInstances uses zonal scope when an Availability Zone is specified directly or through a subnet; otherwise it uses regional scope. The same token can create instances in another applicable scope. Other changed parameters can produce IdempotentParameterMismatch.

VAREXIS-INDEX Single Request

Relevant public records

Can a delayed object-delete retry remove a newer Cloud Storage object with the same name?

A delayed delete without a generation condition can affect a replacement object with the same name. A matching generation precondition binds deletion to that object generation; a mismatch returns 412. For object metadata conditions, Google recommends checking generation as well as metageneration. Retryable errors alone do not establish safe repetition.

VAREXIS-INDEX Single Request

Relevant public records

Does completing a compensating workflow prove every original effect was reversed?

Microsoft architecture guidance describes compensation as application-specific recovery that must account for concurrent changes. It need not restore the starting state, can itself fail, and needs resumable progress and repeat-safe steps. Irreversible actions require explicit treatment. This is design guidance, not a guarantee for any Azure service or deployed workflow.

VAREXIS-INDEX Single Request

Relevant public records

Does CloudFormation rollback completion prove skipped resources match the stack template?

ContinueUpdateRollback can skip eligible resources using ResourcesToSkip. CloudFormation marks those resources UPDATE_COMPLETE while their state remains inconsistent with the template after rollback. AWS requires reconciling the stack or resources before another update. The completed rollback therefore does not establish restoration of each skipped resource.

VAREXIS-INDEX Single Request

Relevant public records

What evidence should I gather before concluding an agent has lost access?

Use the free checklist at https://varexis.tech/index-packs#agent-offboarding-checklist. Identify scope and delegation; separate existing credentials from new issuance; account for exchanged tokens and sessions; retain target-system observations; reconcile event gaps; and state a dated, scoped conclusion. This manual evidence guide reuses published reviews. It neither runs access checks nor certifies complete offboarding; missing evidence remains unresolved.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Can a database change commit while its agent completion event is never published?

AWS describes the dual-write gap between a database update and a message notification: one can succeed while the other fails. A transactional outbox records the change and pending event within one database transaction, then publishes separately. The relay can publish duplicates, so consumers still need duplicate handling. This is architecture guidance, not evidence that a buyer implemented the pattern.

VAREXIS-INDEX Single Request

Relevant public records

Does terminating a Durable Task orchestration stop the activities and sub-orchestrations it already launched?

The documented termination request is queued and the instance reaches Terminated later. Microsoft states that instance termination currently does not propagate: activity functions and sub-orchestrations run to completion even when the calling orchestration is terminated. Querying the parent status therefore does not establish the outcome of its child work.

VAREXIS-INDEX Single Request

Relevant public records

Can an SQS redrive preserve the original message identity and undo messages already moved?

SQS treats redriven messages as new messages with new message IDs and enqueue times, resetting retention. Redriven traffic can interleave with newly produced messages. Canceling a move leaves messages already moved at their destination. Recovery correlation therefore needs application-level action references and destination observations, not only the old message ID or a canceled move status.

VAREXIS-INDEX Single Request

Relevant public records

Can an old Hazelcast lock holder still act after a new worker acquires the lock?

Hazelcast 5.7 describes a paused client losing its CP session while another client acquires the lock; the old client can resume unaware that ownership changed. Monotonic fencing tokens let a cooperating external resource reject stale owners. This protection depends on the external resource using the tokens. The default CP unsafe mode has weaker consistency guarantees.

VAREXIS-INDEX Single Request

Relevant public records

Does a RabbitMQ publisher confirm prove that the message reached a destination queue?

RabbitMQ 4.3 can confirm an unroutable publish after the exchange determines that no queue matches. With the mandatory flag, basic.return precedes the confirm for an unroutable message. Publisher confirms and consumer acknowledgements cover separate exchanges of responsibility; the publish confirm alone does not establish queue routing or application processing.

VAREXIS-INDEX Single Request

Relevant public records

Can retrying a failed Kinesis PutRecords item change the intended action sequence?

PutRecords returns one result per submitted item in corresponding array order. A failed item does not stop subsequent items from being processed; failed items must be detected and resubmitted. PutRecords does not include SequenceNumberForOrdering. Consequently, request-array order alone cannot establish execution order after partial failures and later retries.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful SQS DeleteMessage response using an old receipt handle prove the message was removed?

SQS requires the receipt handle from the most recent receive. An old handle can produce a successful DeleteMessage response while the message might not be deleted. Standard queues can also rarely return a message after deletion when a stored copy was unavailable during the delete. Application effects therefore still need duplicate handling.

VAREXIS-INDEX Single Request

Relevant public records

If Service Bus Complete fails after processing, does that mean the agent action failed too?

Service Bus Complete can fail because of a network problem, expired lock or service condition after the handler has already done its work. The message may be redelivered, so the application must decide how to preserve and recognize an existing result. Broker settlement failure is not proof that the business effect did not occur.

VAREXIS-INDEX Single Request

Relevant public records

Does a DynamoDB transaction appear as one atomic, ordered group in its change stream?

After a DynamoDB transaction completes, its changes propagate gradually to streams and indexes. Records from the same transaction can arrive at different times and interleave with other transactions. AWS says stream consumers should not assume transaction atomicity or ordering. TransactGetItems provides an atomic read of the specified items when a coherent item snapshot is required.

VAREXIS-INDEX Single Request

Relevant public records

Can PostgreSQL report a successful asynchronous commit that is lost in a subsequent crash?

PostgreSQL 18 asynchronous commit returns success after logical completion but before the transaction WAL is flushed to durable storage. A crash in that interval can lose the recent transaction while preserving database consistency. The documentation warns against relying on such an acknowledgement for external actions that require the transaction to be remembered.

VAREXIS-INDEX Single Request

Relevant public records

Does PostgreSQL PREPARE TRANSACTION mean a multi-system action has committed?

PostgreSQL 18 PREPARE TRANSACTION stores transaction state for two-phase commit; a later COMMIT PREPARED or ROLLBACK PREPARED resolves it. Prepared transactions retain their locks and should be closed promptly by an external transaction manager. A prepared state is an unresolved participant decision, not proof of a globally completed action.

VAREXIS-INDEX Single Request

Relevant public records

Does a failed Elasticsearch delete-by-query leave the original matching documents intact?

Elasticsearch 8.19 delete-by-query works from an initial snapshot using internal versioning. Concurrent changes can cause version conflicts. If processing stops after failed requests, successful earlier deletions remain; they are not rolled back. Setting conflicts to proceed changes conflict handling, not the need to reconcile remaining documents and completed deletions.

VAREXIS-INDEX Single Request

Relevant public records

Does a Kubernetes Job parallelism setting prevent replacement workers overlapping terminating Pods?

The Kubernetes v1.34 documentation explains that replacement on TerminatingOrFailed can start a new Pod while the old one is still terminating, temporarily exceeding parallelism and allowing two Pods for one indexed task. The Failed replacement policy waits for terminal failure. This controls replacement timing; it does not prove external effects occur only once.

VAREXIS-INDEX Single Request

Relevant public records

Will a Durable Task approval event wait for an orchestration instance that has not been created?

Microsoft documents buffering when an existing orchestration is not yet waiting for the named event. If no orchestration exists with the specified instance ID, the event is discarded. An event sent before instance creation therefore must not be treated as a retained approval; instance identity, existence and receipt need separate evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does requesting Temporal activity cancellation forcibly stop the worker or its external action?

Temporal documents activity cancellation as a cooperative notification that allows cleanup. Activities must heartbeat to receive cancellation from the service, and activity code can accept or ignore it. A workflow can proceed without waiting for acceptance. A cancellation request therefore does not establish that the worker or an external effect has stopped.

VAREXIS-INDEX Single Request

Relevant public records

Does one S3 multipart abort prove all in-flight parts and their storage charges are gone?

S3 states that part uploads already in progress may or may not succeed after a multipart abort. Repeated aborts can be needed to free all part storage. AWS directs operators to use ListParts and verify an empty list. The abort response alone is not complete cleanup evidence for concurrent uploads.

VAREXIS-INDEX Single Request

Relevant public records

Does HTTP 200 from S3 CompleteMultipartUpload establish that the final object was created?

S3 can send HTTP 200 headers while CompleteMultipartUpload is still processing and later embed an error in that response body. Direct callers must parse the complete response; AWS SDKs detect embedded errors and apply their configured handling. The status line alone does not establish successful final object assembly.

VAREXIS-INDEX Single Request

Relevant public records

Does aborting an Azure Blob copy restore the destination to its pre-copy contents and metadata?

Abort Copy Blob cancels a pending copy but leaves a zero-length destination with the new copied or explicitly supplied metadata. The operation does not restore the old destination. Microsoft recommends taking a destination snapshot before copying if the original metadata must be retained. Only a pending copy can be aborted using its matching copy ID.

VAREXIS-INDEX Single Request

Relevant public records

Do Kafka transactions make an agent's writes to an external service exactly once?

Kafka 4.3 describes exactly-once processing between Kafka topics using transactions and read-committed consumers. For an external destination, the consumer position must be coordinated with the stored output; cooperation from that destination is needed. Kafka transaction success alone does not extend its guarantee to an arbitrary external API or database write.

VAREXIS-INDEX Single Request

Relevant public records

Does Lambda retry only the failed Kinesis records listed in a partial batch response?

With ReportBatchItemFailures enabled on the event source mapping, Lambda uses the lowest reported failed sequence number as its checkpoint and retries all records from there. Later successful records can therefore repeat. Returning partial-failure data in function code is insufficient unless that response type is enabled on the mapping.

VAREXIS-INDEX Single Request

Relevant public records

What evidence closes recovery for an S3 object marked FAILED for replication?

AWS documents HeadObject replication status and S3 Batch Replication as a recovery path for failed objects; re-uploading instead creates new objects that initiate replication. It also warns that Batch Replication might not resolve a FAILED status in the documented destination-ownership case even when the object exists there. Destination existence and source status need reconciliation.

VAREXIS-INDEX Single Request

Relevant public records

Can a deferred Service Bus message be treated as completed or expired because normal receives no longer return it?

Deferred Service Bus messages remain in the main queue but require their sequence number for retrieval; peeking can discover them. Expiration is checked when a client tries to retrieve a deferred message by sequence number, rather than automatically removing it as normal time passes. Absence from ordinary receives does not establish completion or cleanup.

VAREXIS-INDEX Single Request

Relevant public records

Does configuring a RabbitMQ dead-letter exchange guarantee that failed work is retained for recovery?

RabbitMQ 4.3 documents dead-lettering as republishing. By default it uses no internal publisher confirms and removes the message from its source queue after publishing; the message can be lost if the destination cannot accept it. Quorum queues offer an at-least-once dead-lettering alternative. A configured exchange alone does not establish a reliable recovery handoff.

VAREXIS-INDEX Single Request

Relevant public records

Does canceling a GitHub Actions workflow immediately stop every running job and unfinished step?

GitHub re-evaluates running-job conditions during cancellation; a true condition such as always() lets the job continue. Conditions for unfinished steps in continuing jobs are also re-evaluated. Steps selected for cancellation receive process signals before forced termination. A cancel request is therefore not immediate evidence that every job or external action has stopped.

VAREXIS-INDEX Single Request

Relevant public records

Does a signed AP2 open mandate authorise any purchase the agent chooses?

AP2 requires an open mandate to be bound to a transaction and its mandate chain to be verified. The verifier must check unchanged claims and evaluate every constraint against the closed mandate; unknown constraints fail evaluation. A signature alone does not establish that a proposed purchase is within the delegated authority.

VAREXIS-INDEX Single Request

Relevant public records

Does a Coinbase spend permission give an agent arbitrary control of the wallet?

Coinbase documents Spend Permissions as recurring native-token or ERC-20 spending delegated to a spender address. The manager checks spending against the approved allowance; the design does not authorise arbitrary external calls from the user account. Permission revocation is a separate onchain operation. A recurring allowance is not evidence of a one-time procurement approval.

VAREXIS-INDEX Single Request

Relevant public records

Can an earlier MCP tools list prove which tools remain available under changed credentials?

MCP 2026-07-28 allows the available tool set to change over time and vary with the authorization presented on each request. Tool listing supports pagination and caching; list-change notifications use an opted-in subscription. An earlier inventory does not establish the current inventory for a different credential context.

VAREXIS-INDEX Single Request

Relevant public records

Can an MCP server accept a valid token issued for a different service?

MCP 2026-07-28 requires HTTP resource servers to validate that access tokens were issued for their own intended audience. Clients must not send unrelated tokens, and servers must not accept or transit tokens for other resources. Token validity alone is not evidence of authority for the target MCP resource.

VAREXIS-INDEX Single Request

Relevant public records

Does an authenticated MCP Registry publisher establish that its server is approved for our tools?

The official MCP Registry requires publication authentication tied to a GitHub user or organization namespace, or to a domain namespace established through DNS or HTTP proof. This identifies the publication namespace. It does not establish the buyer-approved executable, deployed endpoint or permission policy; those require separate review.

VAREXIS-INDEX Single Request

Relevant public records

Does an MCPB fileSha256 in the Registry prove the downloaded bundle was verified?

The MCP Registry package guide requires MCPB metadata to include a fileSha256 value, but states that the Registry does not validate that hash. Clients validate the hash before installation; downstream registries may also validate it. A published hash is therefore a reference to check, not evidence that a particular download was checked or is safe to execute.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful MCP JSON-RPC result mean the underlying tool action succeeded?

MCP 2026-07-28 separates protocol errors from tool execution errors. API, validation and business-logic failures can be returned in a normal result with isError set to true. A JSON-RPC result envelope alone does not establish action success, and a reported success still needs the action-specific outcome evidence required by the buyer.

VAREXIS-INDEX Single Request

Relevant public records

Can different CloudTrail eventIDs in two accounts describe the same cross-account action?

CloudTrail documents sharedEventID for an AWS action delivered to multiple accounts. Those records share sharedEventID while retaining distinct eventID and recipientAccountID values. The shared field is absent when caller and resource owner are the same account. Counting different eventIDs alone can therefore overstate cross-account actions.

VAREXIS-INDEX Single Request

Relevant public records

Does Databricks SQL SUCCEEDED mean the agent retrieved the complete evidence result?

Databricks documents that SQL Statement Execution results can span multiple chunks. The response identifies subsequent chunks, and byte or row limits can set the truncated flag. Execution success therefore does not show that the client fetched every chunk or received an untrimmed result. Reconcile the manifest, limits and collected data for the same statement.

VAREXIS-INDEX Single Request

Relevant public records

Does an IN_SYNC CloudFormation drift result prove every agent-managed resource matches its intended configuration?

CloudFormation checks supported resources and explicitly specified property values; unsupported resources are NOT_CHECKED, and a parent-stack drift check does not inspect nested stacks. An IN_SYNC result therefore does not establish whole-environment conformity. Reconcile the checked resources and properties with the actual intended-state inventory.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a Bedrock knowledge-base data source remove its vector data and store?

Bedrock documents separate DELETE and RETAIN data-deletion policies. RETAIN leaves the data; DELETE removes the data without deleting the vector store itself and can fail because of vector-store configuration or access. DELETE_UNSUCCESSFUL and failureReasons identify an unsuccessful deletion. Data-source removal alone does not establish complete exit cleanup.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a Copilot conversation through eDiscovery also delete its associated memory?

Microsoft documents Copilot memories as IPM.Contact items and states that deleting a conversation or message through Purview or eDiscovery does not delete the associated memory. Memories need their own identification and deletion scope. Conversation deletion is therefore insufficient evidence of complete removal of the related AI memory.

VAREXIS-INDEX Single Request

Relevant public records

Does pausing a Copilot connector or hiding it from search remove its indexed data?

Microsoft documents that pausing connector crawls leaves existing data searchable. Turning off Copilot visibility excludes the connection from Copilot Search and Chat results but can leave crawling active. A failed connection deletion can leave indexed data, quota usage or crawls in place. These controls are distinct from verified data removal.

VAREXIS-INDEX Single Request

Relevant public records

Does a Vault hold or export cover every type of data in Gemini activity?

Google documents Vault support for Gemini app prompts and responses, but excludes attached media or Gems, generated media and Google Workspace with Gemini data from that Gemini coverage. Active Vault retention rules and holds take precedence over Gemini history or user settings for supported conversations. Neither a hold nor an export establishes coverage of the excluded data types.

VAREXIS-INDEX Single Request

Relevant public records

Does a Claude Enterprise chat retention period bound every project conversation and cloud AI feature?

Claude documents activity-based retention and gives project retention precedence for chats inside projects, including when the project default is indefinite. Its custom chat and project periods do not apply to Claude Design, Claude Tag, Claude Managed Agents or other features running Claude Code in the cloud. A chat-period setting alone does not establish a universal enterprise data lifetime.

VAREXIS-INDEX Single Request

Relevant public records

Can a later Claude organization export recover content already deleted by users or retention?

Claude states that organization exports are available to Team and Enterprise Primary Owners and contain organization conversation and user data. Messages, files and projects deleted before an export is initiated are excluded. A later export is not a recovery mechanism for already-deleted content, and its scope must be distinguished from a member export.

VAREXIS-INDEX Single Request

Relevant public records

Does removing a Claude Team or Enterprise member delete their account and organization data?

Claude states that removing a member does not delete their account or data. The Primary Owner can still export removed-member data subject to retention settings; a permanent-deletion request is a separate Support process. SCIM-provisioned users must also be removed in the identity provider to avoid reprovisioning. Loss of shared-chat access is not erasure evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does selecting a user's OneDrive for eDiscovery include their Copilot Pages and Notebooks?

Microsoft states that selecting a user's OneDrive does not include their Copilot Pages or Notebooks in the user-owned SharePoint Embedded container; that container must be included separately. A message containing a Page link and the linked Page are separate eDiscovery items. Under a Page hold, version limits are ignored and versions are retained until the hold is released.

VAREXIS-INDEX Single Request

Relevant public records

What evidence should a buyer review before granting agent spending or tool authority?

Review delegated spending, tool identity, permission changes, policy applicability and provider payment recovery. These sources support an authority review; they do not authorise purchases, test live permissions or extend the local declaration checker. Full source-linked evidence is free. Documentation review does not establish actual permissions, event completeness, deletion or settlement.

VAREXIS-INDEX Evidence Receipt

Relevant public records

What evidence is needed to review enterprise AI data custody and exit completeness?

Review enterprise AI state, transcripts, datasets, recipient copies, processor geography, preserved attachments and supporting backup controls. Sources identify retention, export and exit boundaries; they do not establish actual erasure, legal compliance or successful customer offboarding. Full source-linked evidence is free. Documentation review does not establish actual permissions, event completeness, deletion or settlement.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does ending a Foundry Agent Service run remove its stored agent data?

Foundry Agent Service retains state and uploaded data. Its FAQ says data persists until explicitly deleted through the API or SDK, including threads, files and vector stores. The documented no-training statement does not make the service stateless.

VAREXIS-INDEX Single Request

Relevant public records

Does disabling Copilot Studio transcript saving erase existing conversations and every stored copy?

The control stops future Dataverse transcript saving, with possible writes for up to 24 hours after it is disabled. Existing transcripts require separate handling. Copilot Studio also temporarily retains session information for up to 28 days independently of the Dataverse control.

VAREXIS-INDEX Single Request

Relevant public records

Can a Copilot Studio session CSV establish the complete text of every agent response?

The documented CSV contains a subset of session information from the past 28 days. Each bot response in ChatTranscript is limited to its first 512 characters. A downloaded CSV therefore cannot establish complete long responses or an unrestricted conversation archive.

VAREXIS-INDEX Single Request

Relevant public records

Does a zero-retention objective apply automatically to every Vertex AI grounding and session feature?

The captured Google documentation describes feature-specific storage: Search grounding logs can persist for up to three days, Maps grounding data for 30 days, and optional Live API session resumption for up to 24 hours. These settings and service terms must be reviewed separately from a general model retention claim.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a LangSmith dataset example remove its inputs and outputs from all versions?

LangSmith distinguishes default soft deletion from hard deletion. Soft deletion preserves historical versions; hard deletion removes the selected example inputs, outputs and metadata across dataset versions. The requested mode and affected example IDs matter.

VAREXIS-INDEX Single Request

Relevant public records

Does disconnecting GitHub from Rovo alone remove its indexed GitHub content?

Atlassian documents a GitHub-specific exception to connector cleanup: removing indexed GitHub data requires disconnecting GitHub from Rovo and uninstalling GitHub for Jira. A Rovo disconnect alone does not satisfy that documented prerequisite.

VAREXIS-INDEX Single Request

Relevant public records

Does Rovo provider zero retention mean Atlassian keeps no chat inputs or outputs?

The Rovo privacy guide says its LLM providers do not retain inputs and outputs, while Atlassian retains Chat and agent inputs and outputs for 30 days for safety and security. Provider and application storage are separate boundaries.

VAREXIS-INDEX Single Request

Relevant public records

Can a Cohere Datasets API upload serve as the long-term evidence archive for an embedding job?

Cohere documents automatic dataset deletion 30 days after creation, with earlier manual deletion also available. Dataset availability is therefore time-limited and cannot be assumed to provide the buyer archive needed for later reconstruction.

VAREXIS-INDEX Single Request

Relevant public records

Does Cohere Model Vault Encrypted hide all request metadata from infrastructure operators?

The Model Vault Encrypted FAQ distinguishes prompt and response content from metadata outside its trusted execution environment. Routing information, infrastructure metrics and network timing or volume can remain visible. Content confidentiality is not a claim that every observable signal disappears.

VAREXIS-INDEX Single Request

Relevant public records

Does Snowflake account storage residency prove Cortex inference stays in the same region?

Snowflake describes cross-region inference as transient processing outside the account region without persisting that payload there. The account parameter CORTEX_ENABLED_CROSS_REGION controls permitted routing. A storage-location statement alone does not establish the actual permitted processing geography.

VAREXIS-INDEX Single Request

Relevant public records

Does a Rovo no-training commitment restrict processing to our single approved external LLM provider?

Atlassian describes normal Rovo routing across hosted and third-party models and says that routing cannot be limited to one preferred external provider. Its Cloud Enterprise hosted-LLM option instead keeps LLM processing within the Atlassian Cloud boundary, at organization scope. No-training terms do not specify a single processing supplier.

VAREXIS-INDEX Single Request

Relevant public records

Which Gemini Notebook artifacts does Workspace export preserve, and can it recover deleted chats?

Google lists chat history excluding deleted history, audio overviews, uploaded content and generated notes in Gemini Notebook data exports. The documented export is not a recovery mechanism for previously deleted chats.

VAREXIS-INDEX Single Request

Relevant public records

Does Gemini in Workspace conversation auto-deletion run from the chat creation date?

Google defines inactivity by the time since messages were last added or edited. The administrator can choose an inactivity interval or indefinite retention; deletion normally follows within a day but can be delayed. These controls are separate from Gemini app history settings.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a Microsoft 365 user account erase Copilot messages that are subject to retention?

Microsoft documents that retained Copilot and other covered AI-app messages remain in an inactive mailbox after the user account is deleted. Previously applicable retention continues, and the content remains discoverable through eDiscovery. Account removal is not equivalent to message erasure.

VAREXIS-INDEX Single Request

Relevant public records

Does an automatic retention label for a Copilot cloud attachment label the original file and chat too?

Microsoft describes creating a retained copy of supported cloud attachments in the Preservation Hold library. The label applies to that copy, not the original file or message. Supported Copilot references can therefore create a separately governed evidence copy requiring its own inventory.

VAREXIS-INDEX Single Request

Relevant public records

Does disabling Copilot content sharing remove conversations recipients already continued?

Microsoft explains that continuing a shared session or response creates a separate conversation in the recipient history. Sharing-setting changes affect new sharing attempts and do not remove existing recipient copies. The source conversation and its sharing link are not a complete downstream-copy inventory.

VAREXIS-INDEX Single Request

Relevant public records

Does placing a Box custodian on legal hold preserve every file they could encounter?

Box distinguishes ownership, access and interaction preservation. Ownership alone excludes a file uploaded into another owner folder; interaction and access holds have different scope. Date ranges further restrict eligible versions or interactions. A custodian name alone does not establish universal content preservation.

VAREXIS-INDEX Single Request

Relevant public records

Does scheduling an AWS KMS key for deletion prove protected AI data has already been erased?

AWS KMS uses a mandatory waiting period during which deletion can be cancelled. A multi-Region primary key waits for replica deletion before its own period starts. A scheduled deletion is therefore not completed key destruction, and key state alone does not establish removal of plaintext or separately protected copies.

VAREXIS-INDEX Single Request

Relevant public records

Does an AWS Backup Vault Lock configuration prove its protection can no longer be removed?

AWS distinguishes governance locks, removable with sufficient permission, from compliance locks with a changeable grace period. After that period, a compliance lock cannot be altered while recovery points remain. Mode, LockDate and backup lifecycles matter when assessing both preservation and later exit feasibility.

VAREXIS-INDEX Single Request

Relevant public records

Do Kubernetes RBAC escalation checks prevent every role administrator from delegating stronger permissions?

Kubernetes normally requires a role author to possess the permissions being added and a binding author to possess the permissions being delegated. The explicit escalate and bind verbs provide exceptions. Reviewing ordinary create or update privileges alone misses these distinct delegation authorities.

VAREXIS-INDEX Single Request

Relevant public records

Does a Kubernetes validating admission policy always reject requests when its parameter is missing?

For a binding with paramRef, parameterNotFoundAction determines the missing-parameter behavior. Allow treats no matched parameter as success; Deny invokes the policy failurePolicy. The presence of a policy object alone does not establish a fail-closed missing-parameter decision.

VAREXIS-INDEX Single Request

Relevant public records

Does a GitHub Copilot content-exclusion rule protect the same files in every agent mode?

GitHub documents content exclusion as unsupported in Copilot Chat Edit and Agent modes, and its support matrix marks Copilot CLI as not applicable. A configured exclusion must be assessed against the actual client and mode rather than treated as a universal agent access boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does attaching a Bedrock guardrail establish that every part of a prompt was evaluated?

Bedrock supports selective input evaluation, including tagged content for InvokeModel APIs. Separately enforced organisation or account controls can require comprehensive evaluation regardless of caller tags. Coverage depends on the API, content selection and effective enforcement configuration; a guardrail identifier alone is insufficient.

VAREXIS-INDEX Single Request

Relevant public records

Does a Google Cloud IAM deny policy automatically block every action by a named principal?

Google documents supported permissions and permission groups for deny policies, with optional principal and permission exceptions and scoped conditions. A deny policy must match the requested permission and principal in its effective resource context. Its mere presence is not evidence of a universal block.

VAREXIS-INDEX Single Request

Relevant public records

Does an enabled Publish button prove every Copilot Studio agent channel has passed data-policy checks?

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.

VAREXIS-INDEX Single Request

Relevant public records

Does a missing OpenTelemetry trace prove that an agent action never happened?

OpenTelemetry distinguishes sampled spans exported for observation from data not selected for export. Head sampling cannot ensure that every later error is retained; downstream tail sampling only evaluates data available to it. Trace absence therefore requires review of the sampling pipeline before an action-absence conclusion.

VAREXIS-INDEX Single Request

Relevant public records

Does a returned serverless function prove its LangSmith traces were delivered?

The LangSmith JavaScript SDK guide describes background tracing and the risk of execution ending before pending data is flushed. It documents waiting for pending batches or disabling background tracing; manual flush mode requires an explicit flush. Function return is not trace-delivery evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does receiving a Gemini app Vault export ZIP establish that all matching conversation evidence was exported?

Vault provides Gemini conversation XML, a result-count CSV and an error XML file. AccountStatus can indicate complete, partial or failed retrieval; SuccessCount counts prompt-response pairs. The ZIP alone does not resolve account errors or establish coverage beyond the search and supported data scope.

VAREXIS-INDEX Single Request

Relevant public records

Does SLSA Build L3 provenance guarantee that resolvedDependencies lists every build dependency?

The SLSA v1.2 provenance specification describes resolvedDependencies completeness as best effort through Build L3. This differs from the completeness requirement for externalParameters. A provenance dependency list therefore cannot alone establish an exhaustive inventory for exposure or reconstruction review.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent safely retry an uncertain PayPal capture as a new request?

PayPal documents PayPal-Request-Id for supported APIs, with endpoint-specific retention. Reusing the original identifier returns the latest status of that request; omitting it can duplicate the request. A timeout does not establish that the first capture failed.

VAREXIS-INDEX Single Request

Relevant public records

Does reusing an Adyen idempotency key prevent duplicate payments across regional endpoints?

Adyen documents company-account scope for idempotency keys but says requests sent to multiple regional endpoints are not deduplicated across regions. Regional failover therefore needs reconciliation of the original attempt; the same key alone is not a cross-region exactly-once guarantee.

VAREXIS-INDEX Single Request

Relevant public records

Does a Square refund request or a COMPLETED payment establish that the buyer was refunded?

Square refunds have their own status, including PENDING, COMPLETED, FAILED and REJECTED. The original payment can remain COMPLETED after a partial or full refund. Recovery must inspect the PaymentRefund object; request acceptance or payment status alone does not establish refund completion.

VAREXIS-INDEX Single Request

Relevant public records

Does a PayPal payment authorisation guarantee that a later agent capture will succeed?

PayPal separates authorisation from capture. The documented authorisation window is 29 days, with a three-day honor period; later capture depends on risk assessment and available funds. Reauthorisation produces a new authorisation ID that must be used for subsequent capture. An authorisation is not a completed settlement.

VAREXIS-INDEX Single Request

Relevant public records

Will GitHub dependency graph include packages whose names or versions are supplied through build variables?

GitHub states that manifest analysis lacks the project build environment and cannot resolve variables used for dependency names or versions. Such dependencies are not automatically included through that analysis. A graph review must reconcile build-resolved inputs before claiming inventory completeness.

VAREXIS-INDEX Single Request

Relevant public records

Does a clean Trivy report using --ignore-unfixed show that no known affected packages remain?

The captured Trivy v0.67 documentation describes --ignore-unfixed as excluding affected, will_not_fix, fix_deferred and end_of_life statuses. Filtering those findings changes the report; it does not remediate the packages or establish that no known exposure remains.

VAREXIS-INDEX Single Request

Relevant public records

Can an upstream fixed-version comparison replace Trivy OS-vendor advisory assessment?

The captured Trivy v0.67 guide uses distribution advisories for OS-managed packages because vendors can backport fixes without adopting the upstream version. It also describes precision versus comprehensive detection tradeoffs. Package origin and advisory selection matter; an upstream version comparison alone can misstate exposure.

VAREXIS-INDEX Single Request

Relevant public records

Does enabling automatic dependency submission replace a user-submitted manifest snapshot in GitHub graph?

GitHub describes one displayed manifest instance selected through source precedence: user submissions outrank Dependabot graph jobs, automatic submissions and static analysis. Same-detector correlators can be merged. Enabling automation therefore does not establish that its snapshot is the evidence currently displayed.

VAREXIS-INDEX Single Request

Relevant public records

What evidence is needed before relying on a clean dependency or advisory report?

Review build-resolved inventory gaps, submission precedence, scanner filters, vendor backports and advisory applicability before relying on a clean dependency report. This free collection is not a scanner, deployment verdict or certification. Full source-linked evidence is free. Documentation review does not establish actual permissions, event completeness, deletion or settlement.

VAREXIS-INDEX Evidence Receipt

Relevant public records

Does an AWS resource control policy restrict the external resources an agent can access?

RCPs constrain supported resources in organization member accounts, including access by external principals. They do not constrain resources outside that organization merely because its identities access them. Their coverage is service-specific, with documented exceptions including calls by service-linked roles.

VAREXIS-INDEX Single Request

Relevant public records

Does a Gatekeeper constraint violation prove that the corresponding request was blocked?

Gatekeeper supports deny, dryrun and warn enforcement actions. Dryrun records violations without enforcing denial; warn supplies warnings. A violation must be interpreted with its constraint enforcementAction and audit time rather than as proof of an admission rejection.

VAREXIS-INDEX Single Request

Relevant public records

Does naming several GitHub environment reviewers require every reviewer to approve an agent deployment?

Only one listed required reviewer needs to approve a referencing job. Preventing the initiator from self-review is a separate setting. Administrators can bypass protection rules by default unless that bypass is disabled. Feature availability depends on plan and repository visibility.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent rely on a fixed ordering of Kubernetes mutating admission webhooks?

Kubernetes does not guarantee a consistent mutating-webhook order. The documentation recommends idempotent individual and combined mutations, with validation after mutation to check the resulting object. Reinvocation can observe later changes but is not a fixed-order contract.

VAREXIS-INDEX Single Request

Relevant public records

Will Terraform ask an agent for approval again when it applies a saved plan file?

Passing a saved plan to terraform apply executes its planned operations without another confirmation prompt. Terraform treats submission of that plan as approval. Planning options cannot be changed in this mode; the saved plan can be inspected with terraform show before execution.

VAREXIS-INDEX Single Request

Relevant public records

Does an Azure role-assignment condition explicitly deny the resource through every other grant?

An Azure ABAC condition narrows the permissions supplied by its role definition and assignment for the supported action context. Microsoft states that conditions cannot explicitly deny access to specific resources. A conditional grant is therefore not evidence of an account-wide deny.

VAREXIS-INDEX Single Request

Relevant public records

Does revoking a Vault parent token revoke orphan credentials created from that workflow?

Ordinary child tokens and their leases are revoked with their parent. Orphan tokens have no parent and form their own trees. The revoke-orphan operation removes a token while orphaning its immediate children instead of revoking those children.

VAREXIS-INDEX Single Request

Relevant public records

Does a Google service-account delegation list itself grant permission to impersonate the final account?

A delegated short-lived-credential request needs the required Service Account Token Creator grants along the chain. The delegates array specifies intermediate service accounts in order; it excludes the initiating caller and final target. Listing an account does not supply the required grant.

VAREXIS-INDEX Single Request

Relevant public records

Does an Entra Conditional Access policy assigned to a group govern service principals inside that group?

Workload Conditional Access must target eligible service principals directly; assigning a containing group does not enforce that policy for them. The documented scope excludes managed identities and Microsoft or third-party multitenant SaaS applications. Eligible workload policies require the relevant licence.

VAREXIS-INDEX Single Request

Relevant public records

Does a SPIRE workload registration parent identify only one machine when it names a node alias?

A workload registration has one parent ID, which may identify a specific node or a node alias shared by a set of nodes. Nodes matching the alias selectors can obtain SVIDs for workloads registered under that parent. The parent text alone does not establish single-machine scope.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent keep using its old GitHub App user token after refreshing the token pair?

For expiring GitHub App user tokens, access lasts eight hours and refresh tokens last six months. Refreshing issues a new pair and invalidates both the old refresh token and old access token. Expired refresh tokens require a fresh user authorization flow.

VAREXIS-INDEX Single Request

Relevant public records

Does removing an Azure managed identity from a group immediately remove its access everywhere?

The App Service managed-identity guide documents a per-resource-URI backend cache lasting around 24 hours. Group or role membership changes can take that long to affect access, and a token cannot currently be forced to refresh before expiry through that mechanism.

VAREXIS-INDEX Single Request

Relevant public records

Can one non-interactive Entra sign-in log row be counted as one credential use?

Entra groups non-interactive user sign-ins with matching characteristics into one row. The sign-in count can exceed one, and rows can be expanded to inspect individual times. The selected aggregation window changes how the same activity is presented.

VAREXIS-INDEX Single Request

Relevant public records

Does a matching traceparent identifier prove that two records belong to an authentic agent action chain?

Trace Context standardizes cross-service correlation. Its security discussion warns that callers can forge trace-ID collisions and manipulate recording behavior. VAREXIS therefore treats correlation headers as supplied context that needs independent identity and event evidence, not authenticated action lineage.

VAREXIS-INDEX Single Request

Relevant public records

Does a CloudTrail event guarantee its full request and response fields were preserved?

CloudTrail documents field-size limits and truncation or omission rules, including requestParameters and responseElements. Limits differ for event data stores configured for larger event sizes. An event can remain present while material field content is absent.

VAREXIS-INDEX Single Request

Relevant public records

Does HTTP 200 from the Azure Monitor Logs API prove an evidence query completed without errors?

A non-fatal query error can return HTTP 200 with result tables and an error object whose code is PartialError. Consumers must inspect the response error details as well as the HTTP status before using the results as complete evidence.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent reconstruct a BigQuery script data footprint from the parent job events alone?

For multi-statement queries, the parent job generates job events while child jobs generate table read and change events. The audit entries use parentJobName to relate child jobs to the parent. Reviewing only the parent can omit the actual table-access evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does a Square payment update protect an agent from overwriting another concurrent amendment?

Payment updates are last-write-wins by default. The optional version_token enables optimistic concurrency. Only eligible APPROVED payments and permitted fields can be updated; the payment capabilities and capture/cancel deadline constrain available changes.

VAREXIS-INDEX Single Request

Relevant public records

Does leaving a Square delayed-capture payment untouched guarantee it will be cancelled?

The default delay_action is CANCEL, but eligible payments can specify COMPLETE. At delayed_until, Square applies the configured action if the payment is not already terminal. The declared delay and action must therefore be reviewed together; an approved payment is not an indefinite neutral hold.

VAREXIS-INDEX Single Request

Relevant public records

Does an Adyen CAPTURE webhook with success true prove final settlement?

The successful CAPTURE event means the request passed validation and was submitted to the bank or processor. A later scheme rejection can produce CAPTURE_FAILED, including days after submission. Reconciliation needs later outcomes tied to the same capture reference.

VAREXIS-INDEX Single Request

Relevant public records

Does an Adyen partial capture leave the unused authorization available for another shipment?

In single partial-capture mode, the unused authorized amount is cancelled. Multiple partial captures preserve the remaining amount, but that feature is disabled by default and requires enablement. A first partial capture alone does not prove authority or capacity for a second one.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent use an Adyen reversal for every uncertain capture and treat acceptance as a completed refund?

Reversal chooses cancellation or refund according to capture state, but the documented flow excludes multiple partial captures and certain split-payment cases. A successful CANCEL_OR_REFUND validation can still be followed by refund failure or reversal. The request reference must remain linked to later outcomes.

VAREXIS-INDEX Single Request

Relevant public records

Does payer approval of a PayPal order prove the final captured amount and shipping terms are unchanged?

PayPal documents updating order amounts and shipping details before capture, including changes after payer approval. Its checkout guidance uses Continue with commit=false when final amounts may change. An agent must compare the approved intent with the final order rather than assuming approval freezes every term.

VAREXIS-INDEX Single Request

Relevant public records

Does npm ignore-scripts prevent an agent from executing npm test or npm run?

The npm v11 documentation says ignore-scripts suppresses package.json scripts during installation. Commands explicitly intended to run a script still execute that script, while their pre- and post-scripts are skipped. The flag is not a general command-execution boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does hashing only the top-level Python requirement establish a fully hash-checked installation?

With require-hashes, pip requires pinned requirements and local hashes for every dependency as well as top-level packages. A remotely supplied index hash does not satisfy that local-trust requirement. The captured pip documentation also distinguishes disabling global hash enforcement from strict mode.

VAREXIS-INDEX Single Request

Relevant public records

Does reviewing one Docker image platform establish the contents selected on every other platform?

A multi-platform image contains a manifest list referring to separate platform manifests, configurations and layers. Docker selects the variant matching the host platform on pull. Reviewing one variant therefore does not establish the contents of another.

VAREXIS-INDEX Single Request

Relevant public records

Can an OpenSearch exit inventory omit manual snapshots because automated recovery has a retention window?

OpenSearch distinguishes automated snapshots in a service-managed bucket from manual snapshots in the customer S3 bucket. Manual snapshots have a separate deletion operation and storage charges. Automated retention does not define the lifetime of every customer-held snapshot.

VAREXIS-INDEX Single Request

Relevant public records

Does an Elasticsearch snapshot preserve every index and setting needed for an AI application exit?

Snapshots back up open indices and supported cluster or feature state, but exclude closed indices and items such as transient cluster settings, registered repositories and node configuration files. Selected-index snapshots narrow coverage further. A successful snapshot is not a complete environment inventory.

VAREXIS-INDEX Single Request

Relevant public records

Does one Qdrant node snapshot establish a complete distributed collection export?

Qdrant documents creating and downloading collection snapshots from each node in its distributed-cluster example. Background snapshot creation with wait=false does not return a snapshot name; the resulting snapshots must be listed and downloaded. One accepted request is not evidence of complete node coverage.

VAREXIS-INDEX Single Request

Relevant public records

How can I reconcile declared data exports, deletion, retention and residual holdings offline?

Reconcile declared holdings, export item coverage, deletion outcomes, retention conditions and residual copies. Checks customer-supplied versioned declarations only. No actual deletion verification, vendor-system inspection, unknown-backup discovery, legal certification or offboarding-completion assurance. Free representative findings summarise declaration gaps; exact runnable cases accompany the licensed package. Source bindings provide dated context; they do not certify the executable rules.

Agent Data Exit & Retention Reconciler

Relevant public records

How can I reconcile declared transaction authority, amendments, retries and payment outcomes offline?

Reconcile declared spending authority, amended purchase terms, scoped idempotency keys, retries and reported outcomes. Checks customer-supplied versioned declarations only. No live payment execution or approval, runtime interception, provider-settlement verification, fraud certification or guarantee of duplicate-payment prevention. Free representative findings summarise declaration gaps; exact runnable cases accompany the licensed package. Source bindings provide dated context; they do not certify the executable rules.

Agent Transaction Integrity & Replay Analyzer

Relevant public records

Do OpenAI spending alerts and rate limits prevent an agent from incurring further API costs?

OpenAI distinguishes spend alerts, which leave traffic running, from configured organization or project hard spend limits, which reject affected requests with a 429 error. Enforcement can lag and recorded spend can exceed the amount slightly. Rate limits constrain request or token throughput; they are separate from monthly spend controls and approved usage limits.

VAREXIS-INDEX Single Request

Relevant public records

Do Anthropic workspace caps or archiving stop all further usage by an agent?

Anthropic separates monthly workspace spend caps from request and token rate limits. Custom workspace limits cannot be set on the Default Workspace, and organization limits still apply. Archiving deactivates a workspace and archives its keys within seconds; multi-workspace keys can no longer act in that workspace. Historical reporting data remains and archiving cannot be undone.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent rely on MCP readOnlyHint, destructiveHint or idempotentHint as enforced permissions?

MCP 2026-07-28 defines ToolAnnotations as hints that are not guaranteed to describe behavior faithfully, and warns against tool-use decisions based on untrusted servers' annotations. readOnlyHint describes mutation, destructiveHint concerns destructive rather than additive updates, and idempotentHint concerns repeated arguments. These declarations do not establish a tested authorization or execution boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does a model-generated OpenAI function call prove that the external action happened?

OpenAI's function-calling workflow returns a tool call to the application, which executes its code and supplies the tool output in a subsequent request. The model can then produce a final response or further calls. The documented application-executed function flow separates the model's requested operation from the application-supplied result.

VAREXIS-INDEX Single Request

Relevant public records

Does Bedrock RETURN_CONTROL mean that an action group operation has already executed?

With RETURN_CONTROL configured, Bedrock returns the predicted action's inputs and an invocationId in InvokeAgent. The application performs the API or function work and supplies returnControlInvocationResults on a later invocation, using the matching invocationId and actionGroup. When those results are supplied, inputText is ignored. The returned control payload is the application's handoff point.

VAREXIS-INDEX Single Request

Relevant public records

What establishes an OpenAI project service-account key's effective authority after a role or scope change?

OpenAI documents project-owned service accounts, group-assigned project roles and separately issued scoped API keys. Key scopes can narrow the account's assigned project permissions but cannot grant permissions outside that role. The Terraform creation flow can create an identity with no default role or key. The RBAC guide allows up to 30 minutes for role changes and group sync to propagate.

VAREXIS-INDEX Single Request

Relevant public records

Does unbinding a Databricks external location from a workspace stop access through tables already created there?

Databricks checks an external location's workspace binding when privileges against that location are exercised, such as creating an external table. Its GCP guide explicitly says that an external table continues to function if the location is subsequently unbound. Catalog bindings provide a separate way to control the workspaces in which catalog contents are available.

VAREXIS-INDEX Single Request

Relevant public records

Does a Docusign completion notification prove which signed document was retained and processed downstream?

Docusign recommends configuring completed documents, completion certificates where needed and document fields in completion webhooks. It also recommends accepting received messages into a queue for asynchronous processing. Document inclusion is configurable; a completion event and the listener's later processing are separate parts of the documented integration.

VAREXIS-INDEX Single Request

Relevant public records

Does a completed Stripe Checkout session prove successful payment for an asynchronous payment method?

Stripe's fulfillment guide directs integrations to retrieve the Checkout Session and inspect payment_status. Delayed payment methods can remain processing after checkout; checkout.session.async_payment_succeeded and checkout.session.async_payment_failed report later outcomes. The guide also requires the application to record fulfillment separately and handle repeated fulfillment calls safely.

VAREXIS-INDEX Single Request

Relevant public records

Does a Shopify order marked paid demonstrate that its goods were fulfilled or delivered?

Shopify's Admin GraphQL Order exposes financial and fulfillment statuses separately. OrderDisplayFinancialStatus includes PAID, while OrderDisplayFulfillmentStatus distinguishes states such as UNFULFILLED, PARTIALLY_FULFILLED and FULFILLED. The separate fields describe different aspects of an order; the reviewed latest API reference does not equate financial status with fulfillment state.

VAREXIS-INDEX Single Request

Relevant public records

Does creating a Stripe refund establish that the customer received it and the original effects were reversed?

Stripe documents refunds that remain pending when a card refund lacks sufficient available balance, and refunds that later fail when the bank or card issuer cannot process them. Failed refunds return funds to the Stripe balance and expose failure information. Some early refunds appear as reversals of the original charge rather than a separate credit.

VAREXIS-INDEX Single Request

Relevant public records

What binds a Stripe tax calculation and approved purchase terms to the payment actually submitted?

Stripe's custom tax integration uses a calculation's amount_total as the amount to charge. Recording the sale requires a Tax Transaction created from that calculation, with a unique reference for reconciliation. The calculation can be used until expires_at, documented as 90 days; recorded Tax Transaction amounts are not recalculated for later tax-rate changes.

VAREXIS-INDEX Single Request

Relevant public records

What OpenAI response state can persist after a call when storage or retention settings change?

OpenAI's data guide describes Responses application-state retention by default or with store=true, stating that response data is retained for at least 30 days in those cases. Zero Data Retention treats store as false, but endpoint and feature exceptions remain. Background mode uses temporary storage for polling, and Modified Abuse Monitoring has additional rules for omitted versus explicit store settings.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a file from an OpenAI vector store also delete the underlying uploaded file?

The OpenAI vector-store file deletion reference explicitly distinguishes removal from the vector store from deletion of the underlying file. Its DELETE operation removes the vector-store file association; deleting the uploaded file requires the separate file deletion endpoint. The response identifies a vector_store.file.deleted result.

VAREXIS-INDEX Single Request

Relevant public records

Can source document deletion leave retrievable copies in an Azure AI Search index?

Microsoft requires a deletion-detection strategy from the first indexer run; adding one later and resetting the indexer does not remove documents deleted before the policy existed. Native blob soft deletion must remain detectable until the indexer processes it. The documented soft-delete policies do not cover one-to-many indexing, which requires explicit index deletion requests.

VAREXIS-INDEX Single Request

Relevant public records

Can one organization's Slack Connect retention and exports cover all externally contributed content?

Slack explains that organizations generally control retention of content sent by their own members; external contributions follow the contributing organization's settings, with documented invitation and plan exceptions. Slack Connect exports can include externally sent messages and display names, but file-link and member-information coverage is limited. Retention by another organization can affect what remains available to export.

VAREXIS-INDEX Single Request

Relevant public records

Can a Weaviate backup restore tenant content beyond a declared deletion boundary?

Weaviate backups include active and inactive tenants from v1.37.0, with backports to v1.35.17 and v1.36.10; earlier releases include active tenants only. Offloaded tenant data is excluded. Backups operate at instance or collection granularity, and tenant-level restore is unavailable: restoring brings back a whole collection. Backup coverage therefore depends on version and tenant state.

VAREXIS-INDEX Single Request

Relevant public records

Does an R2 lifecycle rule prove that all targeted objects were deleted immediately?

Cloudflare says R2 objects are typically removed within 24 hours of x-amz-expiration. Applying a changed lifecycle configuration to existing objects can take longer depending on object count, and old rules may remain visible during migration. New objects reflect the new expiry immediately. The documented default rule for unfinished multipart uploads is a separate seven-day expiry.

VAREXIS-INDEX Single Request

Relevant public records

What do Gemini explicit cache expiry, deletion and usage metadata establish about retained context?

Google's GenerateContent explicit-caching guide provides TTL or expire_time controls, cache deletion and metadata retrieval. Cached content itself cannot be retrieved or viewed through cache listing/get operations; metadata includes identity, model, times and usage. Usage metadata reports token accounting. The data-retention guide treats explicit cache lifetime, separately uploaded files and abuse-monitoring data as different concerns.

VAREXIS-INDEX Single Request

Relevant public records

Does reusing a Stripe API v1 idempotency key guarantee that a payment retry is safe indefinitely?

Stripe API v1 retains the first executed response for a key, including a 500 response. Keys may be pruned after at least 24 hours; reuse after pruning starts a new request. Parameter mismatches fail, while validation or concurrent-execution conflicts may leave no cached result. These rules do not establish the payment outcome.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent treat a Stripe card authorization as available funds for any later capture?

Stripe exposes a card authorization deadline through capture_before. An uncaptured authorization that expires releases its funds and becomes canceled. For most payments a partial capture releases the remainder and permits no second capture; eligible multicapture payments are an exception. Authorization is therefore not evidence that the intended amount was captured.

VAREXIS-INDEX Single Request

Relevant public records

Does increasing a Stripe authorization renew its deadline or replace the original amount when declined?

For eligible Stripe incremental authorizations, success updates the authorized amount. If an increment is declined, the earlier authorized amount remains capturable and proposed field updates are not saved. Incrementing does not extend the original authorization validity period. Eligibility, the increment result and subsequent capture must be checked separately.

VAREXIS-INDEX Single Request

Relevant public records

Does refunding a Stripe separate charge automatically recover money transferred to connected accounts?

With Stripe separate charges and transfers, refunding the charge does not reverse its associated transfers. The platform must reconcile recovery separately, for example through transfer reversals or adjusted later transfers. Reversals have balance or reserve requirements and may fail. A customer refund and recovery from recipients are different outcomes.

VAREXIS-INDEX Single Request

Relevant public records

Does a Stripe invoice marked paid prove that Stripe collected the money?

The Stripe invoice payment API accepts paid_out_of_band to record payment outside Stripe; this option makes no charge. Consequently, a paid invoice alone cannot identify the collection channel or establish a provider-processed payment. Reconcile the invoice with the relevant Stripe payment or separately supported external receipt.

VAREXIS-INDEX Single Request

Relevant public records

Does a Stripe payout initially marked paid establish irreversible receipt by the destination bank?

Stripe documents payout states including paid, failed and canceled. Some payouts that initially appear paid can later change to failed. Failure information and the associated reversal balance transaction help reconcile the returned funds. A single status observation is insufficient to establish irreversible bank receipt.

VAREXIS-INDEX Single Request

Relevant public records

Does allowing a remote MCP tool in OpenAI Responses also approve sending it data?

OpenAI Responses uses allowed_tools to limit imported MCP tools and a separate require_approval setting for tool-call approval. By default it requests approval before sharing data with a connector or remote MCP server. An approval request exposes the tool and arguments for review; disabling approvals changes that sharing gate, not the remote service permissions.

VAREXIS-INDEX Single Request

Relevant public records

Does listing a few tool overrides restrict Anthropic MCP connector access to only those tools?

In the documented MCP toolset configuration, tool-specific configs override default_config, which overrides system defaults. The enabled default is true. Listing selected overrides alone is therefore not an allowlist for all other tools; a restrictive configuration needs the appropriate disabled default. This concerns connector selection, not the upstream credential grant.

VAREXIS-INDEX Single Request

Relevant public records

Does a SharePoint application allowlist block every unlisted agent from the site?

SharePoint Application Restrictions require the tenant switch to be enabled; tenant denials outrank site allowances. Only positively classified third-party applications are governed: first-party and unclassified callers are excluded. The control does not apply to personal sites or trim search enumeration. Existing authorization still applies to requests that pass this additional gate.

VAREXIS-INDEX Single Request

Relevant public records

Does Restricted Content Discovery revoke access to a SharePoint site or remove its search index data?

SharePoint Restricted Content Discovery limits organization-wide discovery and Copilot exposure while governance work proceeds. It does not change existing access permissions or remove content from the Microsoft 365 search index. Users with permission can still access content directly, and propagation takes time. Discovery suppression is not an offboarding or erasure result.

VAREXIS-INDEX Single Request

Relevant public records

Does blocking a SharePoint agent in the Microsoft 365 agent inventory disable it in every host?

The captured SharePoint guidance states that blocking an agent in the administration experience affects Copilot Chat availability, but does not yet apply to OneDrive, SharePoint or Teams. An organization-wide shutdown therefore requires a host-specific access review. The documented administrative block alone does not demonstrate universal removal of the agent.

VAREXIS-INDEX Single Request

Relevant public records

Does an AWS Backup legal hold automatically protect copied and continuous backups?

AWS Backup legal holds apply to selected recovery points created by AWS Backup, not continuous backups. A hold on an original backup does not carry to copies across accounts or Regions. Filtering and completion state also affect inclusion. The existence of one hold does not establish preservation coverage for every copy.

VAREXIS-INDEX Single Request

Relevant public records

Does terminating an Atlas cluster remove snapshots governed by a Backup Compliance Policy?

Atlas retains existing snapshots after cluster termination according to the backup policy. With Backup Compliance Policy enabled, snapshot deletion and reduced retention are restricted. Extra snapshot retention can extend storage beyond the protected period, when appropriately authorized users can delete snapshots. Cluster removal and backup erasure are therefore separate decisions.

VAREXIS-INDEX Single Request

Relevant public records

Does dropping a Unity Catalog table or volume immediately delete its underlying files?

For external tables and volumes, Unity Catalog removes metadata while underlying files remain. Managed files pass through a recovery window and asynchronous purge; the captured guide allows roughly 7–30 days after deletion. Customer storage versioning or soft-delete policies can retain files beyond purge. Object type and storage policy determine the residual-data boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does a Databricks table clone constitute an independent, complete exit archive?

A shallow clone copies metadata and references source data files, while a deep clone copies data and metadata. The documented clone operation does not copy table history, user-defined commit metadata or certain Unity Catalog properties such as tags. Clone success alone therefore cannot establish an independent archive containing all required evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does removed=true in a Google Drive change record prove that the underlying file was deleted?

The Drive API v3 Change resource uses removed when a file or shared drive leaves the changes list, including through deletion or loss of access. The marker does not distinguish those causes by itself. An agent can lose visibility while data remains, so offboarding and deletion findings need additional evidence.

VAREXIS-INDEX Single Request

Relevant public records

Can an S3 Inventory report prove the current absence of an object after deletion?

S3 Inventory reports are eventually consistent snapshots and may omit recent additions or reflect objects since deleted. Reports can also be restricted by prefix and version selection. AWS recommends checking current object metadata before acting. An inventory report is useful evidence, but its absence or presence alone does not establish current deletion state.

VAREXIS-INDEX Single Request

Relevant public records

Does a completed OpenAI Batch output file establish success for every submitted request?

OpenAI Batch writes successful requests to the output file and failed-request information to a separate error file. Output order need not match input order; custom_id links each result to its request. A completed batch or downloaded success file alone does not account for every submitted item.

VAREXIS-INDEX Single Request

Relevant public records

Does one successful MCP tools/list response establish the complete tool inventory?

MCP specification 2026-07-28 supports cursor-based tools/list pagination. Servers choose page sizes and return nextCursor when more results exist. Cursors are opaque; an empty string is valid and must not be mistaken for end-of-results. A successful first page does not establish a complete inventory.

VAREXIS-INDEX Single Request

Relevant public records

Does a Shopify bulk_operations/finish webhook prove that a complete export is ready?

Shopify sends bulk_operations/finish for completed, failed or canceled operations. A failed query may expose a partialDataUrl containing incomplete results. Result download URLs expire after one week. A finish notification or downloadable file therefore needs status and coverage reconciliation before being treated as a complete export.

VAREXIS-INDEX Single Request

Relevant public records

Can Microsoft Graph delta responses be treated as an ordered, duplicate-free action ledger?

Graph delta responses can repeat entities and replay changes across responses; clients must not assume a particular sequence. A 410 Gone reset can require a new full synchronization. Delta supports state synchronization, but these behaviors prevent treating its responses alone as an ordered, duplicate-free history of agent actions.

VAREXIS-INDEX Single Request

Relevant public records

Does accepting an MCP URL elicitation prove that its payment or authorization completed?

In MCP 2026-07-28, accepting URL elicitation records consent to an external interaction, not its completion. The client is not directly told the external outcome. When the original request is retried, the server checks requestState or its own state and returns a result or requests more input.

VAREXIS-INDEX Single Request

Relevant public records

Does resuming a LangGraph approval interrupt avoid repeating actions earlier in the same node?

LangGraph resumes an interrupted node from its beginning, so code before the interrupt runs again. The guide requires preceding side effects to be idempotent and recommends placing effects after the interrupt or in separate nodes where appropriate. A saved checkpoint does not make arbitrary earlier effects execute only once.

VAREXIS-INDEX Single Request

Relevant public records

Does removing a GitHub user revoke repository deploy keys that the user created?

GitHub deploy keys belong to repositories rather than personal accounts or organization membership. Removing their creator from the repository leaves those keys active. Deploy keys have no expiry date and are read-only unless write access was enabled. Offboarding therefore needs a separate deploy-key inventory and removal decision.

VAREXIS-INDEX Single Request

Relevant public records

Does AgentCore Gateway Policy apply its tool rules to MCP prompts and resources?

AgentCore documents Policy evaluation for MCP tools only. Its Policy layer allows the listed prompt and resource methods regardless of evaluation mode. Gateway authentication and other access controls remain separate. A tool-policy configuration therefore does not establish equivalent policy coverage for prompts or resources.

VAREXIS-INDEX Single Request

Relevant public records

Does AgentCore Gateway automatically reflect independently changed MCP tools in DEFAULT listing mode?

DEFAULT listing mode discovers capabilities during target creation or updates and through explicit SynchronizeGatewayTargets calls. AWS directs operators to synchronize after upstream definitions change. Synchronization is asynchronous, so acceptance is not completion. DYNAMIC mode forwards discovery requests and has different documented compatibility limits.

VAREXIS-INDEX Single Request

Relevant public records

Can a GitHub Enterprise audit stream recover every event after a prolonged pause or configuration failure?

GitHub documents a seven-day buffer for paused streams; longer pauses resume from a bounded recent point, and pauses of three weeks or more restart from the current time. Misconfigured streams must be fixed within six days to avoid dropped events. At-least-once delivery can also produce duplicates.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting an AgentCore event also delete long-term memory extracted from it?

AgentCore DeleteEvent removes an individual event. AWS explicitly states that this does not remove structured information derived from it in long-term memory and points to DeleteMemoryRecord for that separate operation. Deleting the source event therefore does not establish removal of its derived memory.

VAREXIS-INDEX Single Request

Relevant public records

Does a Complete S3 Batch Operations job prove every manifest object's operation succeeded?

S3 Batch Operations marks a job Complete after processing the requested manifest operations, which may have succeeded or failed per object. Optional completion reports can include all tasks or failed tasks only and identify object keys, versions and outcomes. Job status alone does not prove every object's success.

VAREXIS-INDEX Single Request

Relevant public records

May an MCP server collect API keys or payment credentials through form elicitation?

MCP 2026-07-28 prohibits requesting passwords, API keys, access tokens or payment credentials through form elicitation and requires URL mode for those interactions. General contact information is not categorically prohibited. URL elicitation is separate from authorizing the MCP client's access to the server.

VAREXIS-INDEX Single Request

Relevant public records

Does an ACTIVE AgentCore policy enforce its decision when the gateway is in LOG_ONLY mode?

AgentCore separates gateway policy-engine mode from each policy's enforcement mode. Gateway LOG_ONLY records decisions without enforcing any policy, including ACTIVE policies. With gateway ENFORCE, ACTIVE policies contribute to the enforced decision while individual LOG_ONLY policies are evaluated separately. Both settings must be checked; a policy status or denial trace alone does not establish blocking.

VAREXIS-INDEX Single Request

Relevant public records

Can AgentCore UpdateGateway authority downgrade or detach a gateway policy engine?

AWS documents that bedrock-agentcore:UpdateGateway permits changing policyEngineConfiguration.mode from ENFORCE to LOG_ONLY, or setting policyEngineConfiguration to null to remove the engine. The mode field has no separate protecting action or condition key beyond UpdateGateway. A review must therefore include who can change gateway configuration, as well as who can call its tools.

VAREXIS-INDEX Single Request

Relevant public records

Which CloudTrail data-event resource selector is required for AgentCore Gateway requests?

The AgentCore Gateway guide requires explicitly enabled CloudTrail data events, an S3-backed trail and advanced event selectors for gateway operations. Its selector uses eventCategory Data and resources.type AWS::BedrockAgentCore::Gateway. These data events are not captured by default. A general trail configuration alone does not establish that the relevant Gateway requests were selected or delivered.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful MCP tasks/cancel response prove the underlying work stopped?

In the MCP Tasks extension 2026-07-28, tasks/cancel acknowledges cancellation intent. Processing is eventually consistent: observable status may remain non-terminal, and work may reach another terminal state. Cancellation is cooperative; the server is not required to stop the work or eventually report cancelled. The ordinary notifications/cancelled notification must not be used to cancel a task.

VAREXIS-INDEX Single Request

Relevant public records

Does expiry of an MCP task prove its external action failed or never happened?

The MCP Tasks extension 2026-07-28 defines ttlMs from task creation, with null representing no limit. The value can change during the task lifetime. After expiry, a server may mark the task failed and later delete it; the task may no longer be usable. These retention and protocol-state rules do not establish the outcome of an external payment or write.

VAREXIS-INDEX Single Request

Relevant public records

Do LangGraph exit, async and sync modes preserve the same recovery state after a process crash?

LangGraph documents three durability modes. exit persists at successful exit, error or interrupt, leaving intermediate state unavailable after a mid-run process crash. async writes checkpoints while the next step runs and can lose an unwritten checkpoint in a crash. sync writes each checkpoint before the next step starts. The selected mode changes the checkpoint recovery boundary.

VAREXIS-INDEX Single Request

Relevant public records

Must LangGraph rerun every parallel node when one node in the same super-step fails?

LangGraph documents pending checkpoint writes for nodes that finish successfully within a super-step. When another node in that step fails, the retained writes allow normal recovery to resume without rerunning those successful nodes. These per-task writes are not complete StateSnapshot checkpoints; time travel uses full super-step checkpoints. This recovery mechanism does not independently reconcile external side effects.

VAREXIS-INDEX Single Request

Relevant public records

What spending authority does an agent grant with a Stripe shared payment token?

Stripe's agent-side SPT guide creates a token for a seller Stripe profile using a customer payment method, with currency, maximum amount and expiry limits. Revocation prevents the seller using that token to create a payment. Token states include active, requires_action and terminal deactivated; deactivation can mean consumption, expiry or revocation. A token state alone is not a settlement or delivery record.

VAREXIS-INDEX Single Request

Relevant public records

Does a Temporal Activity timeout prove that its external action did not complete?

Temporal can time out an Activity Task when its worker does not report completion, including when the worker called an external function and then failed. Activity retry policies can schedule another attempt. The timeout reports the execution boundary observed by Temporal; it does not establish that an external system made no change.

VAREXIS-INDEX Single Request

Relevant public records

Does Temporal Workflow replay itself repeat a completed Activity external side effect?

Temporal replays deterministic Workflow code against recorded history and compares generated commands with the existing events. External interactions belong in Activities, which execute outside the replay path. Activity retries are a separate mechanism. A Workflow replay should therefore not be equated with a new execution of every recorded Activity.

VAREXIS-INDEX Single Request

Relevant public records

Will Temporal automatically recognise a business refusal as a non-retryable Activity failure?

Temporal Retry Policies support non-retryable error types matched against the Application Failure type, and SDKs can report an explicitly non-retryable failure. The default non-retryable error list is empty. Activity retry defaults do not classify an application-specific business refusal on the buyer's behalf.

VAREXIS-INDEX Single Request

Relevant public records

Does Temporal Workflow ID reuse policy deduplicate every external API call made by an agent?

Temporal distinguishes conflict handling for an already running Workflow ID from reuse policy for a closed execution with that ID. Closed-execution reuse checks depend on retained history, and the default reuse policy permits another execution. These policies govern starting Workflow executions in a namespace, not provider-side deduplication of each external API call.

VAREXIS-INDEX Single Request

Relevant public records

Can Temporal retention expiry remove the history needed to reconstruct a closed Workflow?

Temporal retention applies to closed Workflow execution data in a namespace's persistence store; cleanup is scheduled at the end of that period. Self-hosted Archival can copy closed histories and visibility records to blob storage beyond retention, but the reviewed documentation describes it as experimental and disabled by default for manual and Helm installations. Retention configuration alone is not evidence that an archive exists.

VAREXIS-INDEX Single Request

Relevant public records

Does Temporal Continue-As-New preserve one run ID and one continuous event history?

Temporal Continue-As-New closes the current execution and starts a new execution in the same Workflow chain with the same Workflow ID, a new Run ID and a fresh event history. State needed by the next execution must be supplied in its input arguments. A single run history therefore does not cover the entire chain.

VAREXIS-INDEX Single Request

Relevant public records

Can a Temporal child Workflow continue after its parent closes?

Temporal Parent Close Policy determines what happens to a child Workflow when its parent closes. Abandon leaves it unaffected; RequestCancel requests cancellation; Terminate terminates the child Workflow and is the documented default. The policy is set per child. Parent closure therefore cannot by itself establish that every child stopped.

VAREXIS-INDEX Single Request

Relevant public records

Does an OpenTelemetry span with status OK independently prove an external action succeeded?

The OpenTelemetry Trace API defines OK as application developer or operator validation that the operation completed successfully. Its status ordering is OK above Error above Unset: setting OK can override a prior Error, and subsequent Error or Unset updates are ignored. The span status is an application assertion with precedence rules, not independent verification of an external outcome.

VAREXIS-INDEX Single Request

Relevant public records

Does an OTLP exporter acknowledgement prove durable retention in the final telemetry backend?

OTLP 1.11.1 defines acknowledgements between a single client and server. A full-success response means that receiver accepted the telemetry. End-to-end delivery guarantees across intermediaries are outside the protocol's scope. Acceptance by an agent or collector therefore does not establish durable retention in a downstream backend.

VAREXIS-INDEX Single Request

Relevant public records

Does calling OpenTelemetry ForceFlush guarantee that pending spans were exported before shutdown?

The OpenTelemetry Trace SDK specifies ForceFlush across registered SpanProcessors. It should indicate success, failure or timeout and complete or abort within a timeout. Calling it without checking the result therefore does not establish successful export. OTLP acknowledgement also remains a single-hop acceptance boundary rather than proof of final backend retention.

VAREXIS-INDEX Single Request

Relevant public records

Can OpenTelemetry baggage be trusted as authenticated user identity or agent spending authority?

OpenTelemetry baggage carries contextual key-value data that can propagate to downstream services and unintended third parties. Its documentation states that there are no built-in integrity checks proving that baggage items originated with the reader's system. Baggage is also separate from span, metric and log attributes unless explicitly copied into them.

VAREXIS-INDEX Single Request

Relevant public records

Does an OpenTelemetry instrumentation scope identify the vendor of the remote tool being called?

OpenTelemetry instrumentation scope identifies the logical software unit that emits telemetry, using a name and optional version, schema URL and attributes. When an instrumentation library emits telemetry for another library, the scope identifies the instrumentation library. It is not a standard attestation of the remote service vendor or tool operator.

VAREXIS-INDEX Single Request

Relevant public records

Should an OTLP client retry an export when the response contains partial_success?

OTLP 1.11.1 uses a populated partial_success response to report rejected telemetry counts or warnings. The client must not retry that request. A warning can carry zero rejected items, so a populated field is not itself evidence of data loss; the rejection counts and diagnostic message must be interpreted. An HTTP success response can still report rejected spans.

VAREXIS-INDEX Single Request

Relevant public records

Does OpenTelemetry service.name uniquely identify the production instance that performed an action?

OpenTelemetry defines service.name as the logical service name. service.instance.id distinguishes instances of the same service, and the combination of service.namespace, service.name and service.instance.id must be globally unique. A shared service.name alone cannot distinguish replicas or environments, and these declared attributes do not authenticate the emitting workload.

VAREXIS-INDEX Single Request

Relevant public records

Can OAuth PKCE replace client authentication for a confidential authorization-code client?

RFC 9700 recommends PKCE for confidential clients as protection against authorization-code misuse. RFC 6749 separately requires client authentication for confidential clients or clients issued credentials when using the token endpoint. PKCE binds a code exchange to a verifier; it does not remove that client-authentication requirement.

VAREXIS-INDEX Single Request

Relevant public records

Can an OAuth server replace exact redirect URI matching with a trusted parent-domain check?

RFC 9700 requires exact string matching against pre-registered redirect URIs, apart from the localhost port exception for native applications. A parent-domain match or a general wildcard is not that comparison. The guidance also prohibits open redirectors in clients and authorization servers.

VAREXIS-INDEX Single Request

Relevant public records

How should a multi-provider OAuth client verify the issuer of an authorization response?

RFC 9207 defines the iss authorization-response parameter. A supporting client compares it with the expected issuer using simple string comparison and rejects a mismatch. It must remember which configured servers support the parameter and reject a response missing iss from one that does. Expected issuer identity comes from server metadata or deployment-specific configuration.

VAREXIS-INDEX Single Request

Relevant public records

Does an OAuth client-credentials token prove that a human approved this particular agent action?

RFC 6749 limits the client-credentials grant to confidential clients. The client requests access using its own authentication for resources under its control or access previously arranged with the authorization server. That authentication supplies the grant without an additional authorization request. The flow does not itself record a human's approval of each proposed action.

VAREXIS-INDEX Single Request

Relevant public records

Can a resource server treat an OAuth introspection active response as approval for the requested action?

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.

VAREXIS-INDEX Single Request

Relevant public records

Does an OAuth token revocation HTTP 200 prove that the submitted token previously existed?

RFC 7009 returns HTTP 200 both when revocation succeeds and when the submitted token is invalid; clients ignore the response body. An invalid token is not an error because the requested invalidation outcome is already satisfied. The response therefore does not establish that a particular valid credential existed or that every related credential was revoked.

VAREXIS-INDEX Single Request

Relevant public records

Can a Kubernetes RBAC Role deny a permission granted through another RoleBinding?

Kubernetes RBAC permissions are purely additive and do not include deny rules. A restrictive Role does not cancel an allow supplied by another applicable RoleBinding or ClusterRoleBinding. Review all applicable RBAC grants; this statement does not describe every other authorization or admission mechanism that a cluster may use.

VAREXIS-INDEX Single Request

Relevant public records

Can an MCP application state handle or legacy session ID replace authentication?

MCP security guidance for revision 2026-07-28 requires verification of inbound requests and prohibits using application state handles for authentication. It recommends unpredictable handles bound to the authenticated principal. The 2025-11-25 guidance applies the same authentication warning to that revision's session IDs. These are version-specific state mechanisms, not bearer authority to act.

VAREXIS-INDEX Single Request

Relevant public records

Can an MCP client assume that Streamable HTTP always supports resuming a stream with Last-Event-ID?

MCP Streamable HTTP revision 2026-07-28 does not support resumable SSE streams through Last-Event-ID and instructs servers to ignore that header. Its compatibility section distinguishes earlier revisions that used session IDs and resumable streams; supporting those clients requires the corresponding older behaviour. A transport name alone therefore does not establish replay or resumption support.

VAREXIS-INDEX Single Request

Relevant public records

Can MCP progress notifications establish that an external action completed successfully?

MCP progress guidance for revision 2026-07-28 permits optional progress notifications for an active request. A total value is optional, progress values increase, and notifications must stop after the operation completes. Progress updates are not the terminal request result, and their numeric values do not independently establish the external business outcome.

VAREXIS-INDEX Single Request

Relevant public records

Can a Slack bot read private-channel history merely because its token has a history scope?

Slack conversations.history combines the relevant history scope with token-specific access. Bot tokens can read conversations the bot belongs to; app-level tokens cover conversations the app belongs to; user tokens cover private conversations the user belongs to and public conversations. A scope name alone does not establish membership or make bot and user access interchangeable.

VAREXIS-INDEX Single Request

Relevant public records

Does a Stripe Payment Link guarantee a trustworthy unique order identifier in every Checkout Session?

Payment Link metadata is copied to the sessions it creates, but an application-specific reference is not automatically generated. The optional client_reference_id URL parameter accepts a caller-supplied string; invalid values are silently dropped while checkout continues. A session can therefore exist without the expected reference, and a supplied reference is not independent proof of the buyer or purchased entitlement.

VAREXIS-INDEX Single Request

Relevant public records

Does recovering an expired Stripe Checkout Session resume the same provider session identity?

An expired Checkout Session cannot be completed. With recovery enabled, opening its recovery URL creates a new copied Checkout Session. The recovered_from field identifies the original expired session. Recovery therefore creates a new attempt that can be correlated with the abandoned one; it does not turn the expired session itself into a completed payment.

VAREXIS-INDEX Single Request

Relevant public records

Can a Stripe Payment Link buyer change purchased quantity while retaining the same Price ID?

Payment Link line items can enable adjustable_quantity with minimum and maximum limits. The customer can then change the quantity during checkout without replacing the referenced Price. The resulting session line items contain purchased quantities. A Price identifier or the link template quantity alone therefore does not establish how many units were purchased.

VAREXIS-INDEX Single Request

Relevant public records

Does a Stripe Checkout Session with no_payment_required prove a new cash payment?

Checkout payment_status distinguishes paid, unpaid and no_payment_required. Stripe documents no_payment_required for setup mode or a billing-cycle anchor without proration where collection happens at the anchor date. That state can be relevant to a merchant workflow, but it does not by itself establish a new charge or money received.

VAREXIS-INDEX Single Request

Relevant public records

Does expanding line_items on a Stripe Checkout Session necessarily return every purchased item?

Stripe describes the includable session line_items property as containing the first handful of items. The dedicated session line-items endpoint returns the full list through pagination. A session expansion alone is therefore not evidence that every purchased product and quantity has been enumerated.

VAREXIS-INDEX Single Request

Relevant public records

Does an active Stripe subscription establish that every outstanding invoice is paid?

Stripe explicitly states that active does not necessarily mean every outstanding subscription invoice has been paid. Status resolution can depend on the most recent invoice or all applicable invoices; settling can also include marking an invoice uncollectible. Failed-payment settings can leave a subscription past_due. Subscription status and invoice-level collection evidence are therefore separate.

VAREXIS-INDEX Single Request

Relevant public records

Does a Stripe subscription proration establish that the old or changed plan was actually paid?

Stripe calculates prorations assuming previous invoices will eventually be paid. An unpaid period can consequently produce a credit for unused time. Negative prorations are not automatically refunded and positive prorations are not necessarily immediately billed. A proration amount records a billing adjustment, not proof of collection or refund completion.

VAREXIS-INDEX Single Request

Relevant public records

Does setting Stripe cancel_at_period_end mean the subscription has already ended?

Setting cancel_at_period_end schedules cancellation for the end of the billing period; it can be unset before that point. Stripe distinguishes subscription.updated when the flag changes from subscription.deleted when cancellation occurs. Pending prorations can remain collectible at period end. The scheduling event alone is not the terminal cancellation event.

VAREXIS-INDEX Single Request

Relevant public records

Does resuming Stripe payment collection automatically settle invoices created during the pause?

Pausing collection leaves subscription status unchanged and can retain invoices as drafts, mark them uncollectible or void them. When invoices were kept as drafts, resuming subscription collection does not itself settle those invoices: Stripe instructs merchants to enable auto_advance on each retained draft to collect later. A resumed collection setting is not a payment receipt.

VAREXIS-INDEX Single Request

Relevant public records

Does a Stripe invoice marked paid after balance adjustments prove new money was received?

Stripe customer invoice balances are a ledger of credit and debit adjustments that can apply to later invoices. Credit reduces the amount due; very small amounts can be moved to the invoice balance while the invoice is marked paid. These documented balance movements do not themselves establish a new cash payment for that invoice.

VAREXIS-INDEX Single Request

Relevant public records

Does issuing a Stripe credit note guarantee a refund to the original payment method?

A credit note reduces an open or paid invoice. For a paid invoice, Stripe supports allocation to a payment-method refund, customer credit balance or an out-of-band refund. Invoices funded partly by customer balance can return excess credit to that balance. The credit-note total therefore does not identify one refund destination or prove bank receipt.

VAREXIS-INDEX Single Request

Relevant public records

Do Stripe pending subscription updates always prevent a plan change before successful payment?

Pending updates normally apply changes only after the resulting invoice payment succeeds. Stripe documents an exception when resumption moves a paused subscription to active or past_due: a matching pending update can apply even without successful payment. A populated pending_update can also mean payment is still processing. Applied-update and invoice-payment outcomes require separate checks.

VAREXIS-INDEX Single Request

Relevant public records

Does Stripe on_behalf_of move dispute debits to a connected account for every charge model?

Stripe separates direct charges from charges created on a platform. Direct-charge disputes debit the connected account for the disputed amount, while destination charges and separate charges and transfers debit the platform balance, with or without on_behalf_of. The parameter can make the connected account the business of record, but it does not erase charge-model-specific debit rules.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful Stripe transfer request prove that the associated charge funds were already available?

For separate charges and transfers, a transfer using source_transaction can be accepted before the charge funds become available; Stripe waits for those funds before executing it. Without that linkage, available platform balance constrains transfers, and failed transfers are not automatically retried. Acceptance, funding availability and completed movement must therefore be distinguished.

VAREXIS-INDEX Single Request

Relevant public records

Does a shared Stripe transfer_group prove a one-to-one funding relationship between a charge and transfer?

Stripe describes transfer_group as an association string that does not change standard transfer behavior. Charge and transfer amounts need not match: one charge can support several transfers, and several charges can be included in a transfer. A shared group alone therefore does not establish a unique funding allocation or completed delivery for a particular purchase.

VAREXIS-INDEX Single Request

Relevant public records

Does refunding a Stripe destination charge automatically refund the platform application fee?

For a destination charge, Stripe says the platform keeps the application fee by default when refunding the charge. refund_application_fee can return it, and that path also requires reversing the transfer. A full refund returns the full fee on that path; a partial refund returns a proportional fee. Customer refund, transfer reversal and application-fee refund are distinct records.

VAREXIS-INDEX Single Request

Relevant public records

Does charges_enabled on a Stripe connected account establish that it can also receive payouts?

Stripe exposes separate charges_enabled and payouts_enabled fields. The first states whether the account can process charges; the second states whether funds in the account can be paid out. One flag does not replace the other, nor does either flag identify a completed payout to a particular bank account.

VAREXIS-INDEX Single Request

Relevant public records

Is a Stripe balance transaction amount the net proceeds of the underlying payment?

Stripe defines amount as the gross transaction amount, fee as assessed fees and net as the net impact on the balance. The balance transaction has its own currency and can include an exchange rate when conversion occurs. available_on describes when net funds become available. Gross payment, balance impact and bank payout are therefore different observations.

VAREXIS-INDEX Single Request

Relevant public records

Does successful software delivery make a Stripe card payment immune to a later dispute debit?

Stripe documents that a formal card dispute causes the card network to debit Stripe and Stripe to debit the merchant balance for the disputed amount and a dispute fee. The dispute process can subsequently return funds or uphold the cardholder outcome. An application delivery record does not disable that provider process or prove irreversible funds.

VAREXIS-INDEX Single Request

Relevant public records

Does an HTTP 402 MPP challenge establish that its stated merchant and payment terms are authorised?

MPP clients are instructed to check the requested amount, recipient, currency or asset and validity window before authorising payment. The description is display text and must not be used for payment verification. A 402 challenge supplies payment requirements; its presence does not independently establish that the endpoint or recipient matches the buyer intent.

VAREXIS-INDEX Single Request

Relevant public records

Does an MPP payment credential automatically authorise a different request body or resource?

MPP supports a digest parameter binding a challenge to the request body. When present, the submitted body must match that digest. The security guidance also requires verification of amount, currency, recipient and route-level context. Challenge integrity therefore needs to be connected to the actual paid request; a receipt or payment proof is not a general-purpose resource authorisation.

VAREXIS-INDEX Single Request

Relevant public records

Does an MPP receipt alone prove the intended API result was delivered for the agreed amount and currency?

The common MPP receipt records a payment method, method-specific reference, success status and processing timestamp; methods may add fields. It is a server acknowledgement of payment, not a complete copy of the challenge or the delivered result. Reconciliation must retain the challenge terms and application outcome alongside the payment reference.

VAREXIS-INDEX Single Request

Relevant public records

Can an MPP server accept a caller payment assertion after the challenge expired merely because it was signed earlier?

MPP credential processing checks that the challenge identifier is outstanding, that the challenge has not expired, that the method-specific payment or proof verifies, and that the credential is not replayed. A client-supplied signature or transaction identifier does not replace those checks. For a submitted Tempo transaction hash, the server verifies the confirmed transfer against challenge parameters.

VAREXIS-INDEX Single Request

Relevant public records

Does cryptographically binding an MPP challenge guarantee safe retries across multiple server instances?

MPP distinguishes challenge integrity from replay prevention. Payment methods must enforce single-use proof semantics separately; deployment guidance calls for shared atomic replay state across instances and warns against process-local memory. Non-idempotent operations also need idempotency handling. Preventing proof reuse is therefore not the same as proving an external operation executed exactly once.

VAREXIS-INDEX Single Request

Relevant public records

Does a valid MPP payment credential by itself authorise access to a customer private resource?

MPP distinguishes payment failure from application authentication and policy denial. It documents a 403 response when payment verifies but policy denies access. When an endpoint also uses application Authorization, it can advertise Payment-Authorization for the payment credential, keeping the two credentials separate. Valid payment is therefore not a substitute for application-level access authority.

VAREXIS-INDEX Single Request

Relevant public records

Does switching MPP payment methods preserve the same verification and settlement behavior?

MPP standardises the challenge and credential framework while payment-method specifications define request and proof schemas, verification and settlement procedures. Session methods additionally define how setup, incremental authorisation and accepted usage settle. Sharing the protocol envelope does not make a card payment, transaction proof or metered channel operationally interchangeable.

VAREXIS-INDEX Single Request

Relevant public records

Does a capability advertised in a UCP profile become active for every checkout operation?

UCP v2026-08-25 selects response capabilities from the negotiated session intersection and those relevant to the operation type. An extension must relate to a relevant root capability. Profile advertisement therefore does not establish that every capability or merchant extension is active in the current checkout, or that the buyer authorised its use.

VAREXIS-INDEX Single Request

Relevant public records

Does the initial UCP checkout response freeze the terms an agent will later commit to purchase?

UCP v2026-08-25 permits Update Checkout to replace checkout state with updated inputs before accepted completion. Complete Checkout is the final placement operation when the user has committed to the chosen items. Once completion is accepted and in progress, updates are not permitted. An earlier cart response is therefore not a substitute for the current checkout terms.

VAREXIS-INDEX Single Request

Relevant public records

Does UCP ready_for_complete establish a completed or paid order?

In UCP v2026-08-25, ready_for_complete means the required information is present and the platform can invoke Complete Checkout. incomplete requires resolution, while complete_in_progress means processing was accepted and must not include an order. completed includes the placed order. Readiness, accepted processing and completed placement are distinct states, not interchangeable payment evidence.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent assume every UCP payment handler sends credentials to the same parties?

The UCP payment-handler guide requires each handler specification to identify participants, prerequisites, configuration, acquisition and processing flows. Business, platform and response declarations serve different purposes. The common architecture expects the platform to pass a token or mandate to the business while using the credential provider interface. The handler identity alone does not establish an unchanged credential destination.

VAREXIS-INDEX Single Request

Relevant public records

Does a confirmed UCP order prove that the purchased entitlement or goods were delivered?

UCP orders represent confirmed transactions following checkout. The order model separately tracks line-item quantities, fulfilment expectations and fulfilment events as the order progresses. Placing the order creates its initial representation; subsequent events update its state. An order identifier or expected delivery grouping therefore does not by itself establish completed fulfilment.

VAREXIS-INDEX Single Request

Relevant public records

Does UCP require one universal authentication scheme for every merchant endpoint?

UCP v2026-08-25 supports API keys, OAuth, mutual TLS and HTTP Message Signatures. Regardless of mechanism, the authenticated identity must be consistent with the advertised UCP-Agent profile; business-to-platform webhooks must be signed. A discoverable profile therefore does not remove identity-binding requirements or prove a particular deployment uses the expected authentication method.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent rely indefinitely on a cached UCP profile because its dated version is unchanged?

UCP v2026-08-25 allows approved amendments to a supported release. Runtime consumers should follow HTTP caching semantics and revalidate after max-age expires. UCP-defined capabilities must match their profile release version, with mismatched entries rejected. A dated version string alone therefore does not prove that a cached artifact remains current or internally consistent.

VAREXIS-INDEX Single Request

Relevant public records

Can an AP2 mandate be reused after the checkout terms or payment recipient have changed?

AP2 v0.2 requires the merchant to verify that checkout_hash matches the latest checkout_jwt. The Payment Mandate links to the checkout, and constraint evaluation checks amounts and payees against authorised limits. Closed mandates also bind to their presented open mandate. A previously valid signature does not by itself establish authority for changed checkout contents or a substituted payee.

VAREXIS-INDEX Single Request

Relevant public records

Does an AP2 Payment Mandate replace evidence of the actual payment outcome?

AP2 v0.2 separates the Payment Mandate authorising a particular checkout from the Payment Receipt. The receipt carries Success or Error, issuer, timestamp, a reference to the closed mandate and a payment ID; provider and network confirmation IDs are optional success fields. The authorising mandate is therefore not itself the later payment outcome record.

VAREXIS-INDEX Single Request

Relevant public records

Does AP2 define a universal dispute outcome or evidence-retention service for an agent purchase?

AP2 v0.2 describes bringing Checkout and Payment Mandates and their receipts together and verifying their signatures and cross-references as dispute evidence. It explicitly leaves specific dispute-resolution use, retention and retrieval requirements outside the specification. The protocol evidence can describe what participants saw; it does not prescribe one dispute result or provide an archive service.

VAREXIS-INDEX Single Request

Relevant public records

Does AP2 v0.2 fully specify passing purchase mandates between independent shopping agents?

AP2 v0.2 says shopping-agent-to-shopping-agent mandate delegation is conceptually possible but outside the current specification. It separately allows a role to delegate verification responsibilities to a technology provider, which then follows that role verification rules. Outsourcing a verifier is not the same as a specified interoperable chain of spending redelegation.

VAREXIS-INDEX Single Request

Relevant public records

Does an accepted Adyen split payment prove that the intended balance account received the funds?

Adyen split instructions allocate sale proceeds, commission, fees and remainder between balance accounts. The request validates instruction format rather than the specified accounts. A nonexistent account or a closed account holder can cause the full transaction and fees to be booked to the platform liable account instead. Payment success therefore does not establish the intended allocation.

VAREXIS-INDEX Single Request

Relevant public records

Can a Square CreatePayment retry reuse its idempotency key with a changed payment amount?

Square documents that repeating a successful CreatePayment request with the same idempotency key returns the original successful response instead of taking another payment. Reusing that key with a changed request, such as a different amount, returns an error. Square notes that idempotency behavior can vary by API, so this rule must not be generalised to every endpoint.

VAREXIS-INDEX Single Request

Relevant public records

Do AP2 direct and autonomous purchases use the same signer evidence for a closed mandate?

AP2 v0.2 verifiers receive closed Checkout and Payment Mandates in both modes. In the direct mode, the closed mandate signature is validated as coming from the user. In autonomous mode, an agent signs the closed mandate and trust in that key comes through user- or provider-signed open mandates and their constraints. The common closed form does not eliminate the different authority chain.

VAREXIS-INDEX Single Request

Relevant public records

Does completing an OpenAI batch establish that its uploaded files and application state have been deleted?

The upload reference makes file lifetime depend on purpose and expiration settings: batch-purpose uploads expire after 30 days by default, while other uploaded files persist until manually deleted unless an expiration policy applies. The data guide separately lists batch application state as retained until deletion. A completed job is not a file-deletion receipt.

VAREXIS-INDEX Single Request

Relevant public records

Does an OpenAI regional-storage configuration establish that all processing stays in that region?

OpenAI distinguishes regional storage from regional processing. If a selected region does not support regional processing, customer content may be processed and temporarily stored elsewhere. Residency also excludes system data and third-party services. Applicable endpoints, models, snapshots and regional capabilities must be checked together.

VAREXIS-INDEX Single Request

Relevant public records

Is OpenAI abuse-monitoring retention an unconditional maximum that applies despite all safety and legal exceptions?

The data guide describes ordinary abuse-log retention of up to 30 days, with longer retention for legal requirements or protection from harm. It also describes retaining suspected CSAM image material for manual review even under approved Zero Data Retention or Modified Abuse Monitoring. These exceptions differ from ordinary application-state retention.

VAREXIS-INDEX Single Request

Relevant public records

Do OpenAI organization retention controls automatically govern data sent to a remote MCP service?

OpenAI identifies remote MCP servers as third-party services whose own retention policies apply to data sent to them. Network transfers to other third-party services likewise follow those services’ retention policies. OpenAI account controls therefore do not describe the complete downstream retention boundary.

VAREXIS-INDEX Single Request

Relevant public records

Can a global administrator later shorten or disable a Purview policy after applying Preservation Lock?

Purview Preservation Lock prevents disabling, deleting or making the policy less restrictive, including by global administrators. A locked retention policy can gain locations or a longer period, but cannot lose locations or have its period shortened. A locked retention-label policy can add labels but cannot remove them.

VAREXIS-INDEX Single Request

Relevant public records

Does a Teams message disappearing from chat prove that its retained compliance copy is gone?

Microsoft describes separate Teams service data and message copies in hidden Exchange mailbox locations used by compliance tools. Chat and channel types use different mailbox types. Retention and eDiscovery operate on these compliance copies, so the visible Teams conversation is not a complete inventory of retained message evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does approving a Purview disposition review prove immediate deletion of every copy of the item?

Purview separates disposition approval from permanent deletion: its documented timeline allows up to 15 days after final approval for eligible content. Disposed-item information relies on searchable audit events. Approval and the recorded deletion event are different evidence, and the documented workflow does not attest to every independently exported copy.

VAREXIS-INDEX Single Request

Relevant public records

Does applying Purview retention to a SharePoint site alone guarantee preservation of every file version?

SharePoint retention can copy changed or deleted content into a Preservation Hold library. Microsoft says retaining all file versions requires site versioning; new content is not copied on its first edit. The behavior also differs between retention policies, record labels and ordinary retention labels. Retention configuration alone is not an all-version archive.

VAREXIS-INDEX Single Request

Relevant public records

Does excluding a SharePoint site from a Purview retention policy receive the same grace period as releasing the policy?

The retention guide describes a 30-day preservation grace period when a SharePoint or OneDrive retention policy is released. It explicitly excludes updates that remove particular sites or accounts through policy exclusions: their Preservation Hold library cleanup proceeds without that 30-day delay. Other applicable retention controls still need evaluation.

VAREXIS-INDEX Single Request

Relevant public records

Does applying an event-based Purview record label start its retention countdown before the event is matched?

Purview event-based retention links labels and event types to a triggering event, with asset IDs identifying relevant documents. A declared record whose triggering event has not happened is retained indefinitely. The configured duration therefore does not by itself establish a calendar deletion deadline from the date the label was applied.

VAREXIS-INDEX Single Request

Relevant public records

Can a Google Vault matter be closed while preserving its active holds and existing downloadable exports?

Vault requires all holds to be deleted before a matter can be closed. Closing retains saved queries and audit data but immediately deletes export files. Reopening preserves the queries and audit data; holds and exports must be recreated. Matter closure is therefore a different operation from merely pausing an investigation.

VAREXIS-INDEX Single Request

Relevant public records

Can a Google Vault export remain a downloadable evidence archive indefinitely after it is created?

The Vault exports guide makes exports available for 15 days after creation, after which they are deleted and no longer accessible. Listing an export or recording its identifier does not preserve the downloadable files beyond that window. Creating, downloading and independently retaining the export are separate steps.

VAREXIS-INDEX Single Request

Relevant public records

Does expiry of a Google Vault retention rule prove immediate removal from every supported service and from Vault?

Vault documents different post-expiry behavior by service. Drive items can take up to 15 days to leave Drive and become unavailable to Vault once removed without a protecting rule or hold. Gmail and Gemini messages can remain searchable in Vault for roughly 30 more days. A single policy timestamp is not a uniform purge receipt.

VAREXIS-INDEX Single Request

Relevant public records

Does a Vault version-date search reproduce every historical Drive revision and its metadata exactly as they existed then?

Vault searches a file’s current version even when a version date is supplied. For supported Google file types, preview and export use the last version saved before midnight on that date, but properties such as title, sharing and modification metadata remain current. Comment inclusion has separate rules. This is not an exact replay of every historical property.

VAREXIS-INDEX Single Request

Relevant public records

Does selecting custodian accounts in a Vault Drive search automatically include all relevant shared-drive files?

Vault distinguishes account searches from searches of selected shared drives. Account search coverage depends on sharing and shared-drive inclusion settings. The API documents sharedDrivesOption with explicit exclusion, conditional inclusion and inclusion modes; it supersedes the older includeSharedDrives and includeTeamDrives fields. Selecting an account alone does not describe complete shared-drive scope.

VAREXIS-INDEX Single Request

Relevant public records

Does an S3 Lifecycle Expiration action permanently remove all versions of an object in a versioned bucket?

In a versioning-enabled bucket, Expiration can make a delete marker current while the former current object becomes noncurrent. The action applies to current versions and does not remove noncurrent versions. Those require separately configured noncurrent-version expiration, subject to documented lock and replication constraints. An ordinary lookup returning no object is not an all-version deletion inventory.

VAREXIS-INDEX Single Request

Relevant public records

Does an S3 Object Lock legal hold end automatically when the object version’s retention date passes?

S3 legal holds have no expiration date and remain until explicitly removed. They are independent of time-based retention and apply to individual object versions. A version can therefore remain protected after its retention period ends, and clearing a hold does not remove a separate unexpired retention restriction.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting one S3 access point revoke access through other access points or the bucket hostname?

AWS states that removing an access point does not disrupt access through other access points or the bucket hostname. Access-point policy restrictions apply to requests using that access point; attaching one does not change other bucket operations. Removing a connector-specific path therefore does not establish complete bucket offboarding.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a Cloud Storage bucket with soft delete enabled prove that the bucket and its objects are permanently gone?

Cloud Storage soft delete preserves deleted buckets and objects for the configured period. A bucket restored through the CLI or JSON API is restored empty; restoring its objects is a separate operation. Project deletion can shorten preservation to the smaller of the soft-delete duration and project recovery window. Deletion and restoration scope must be checked separately.

VAREXIS-INDEX Single Request

Relevant public records

Can a project owner unlock or shorten a Cloud Storage bucket retention policy after it is locked?

Cloud Storage describes locking a bucket retention policy as irreversible. A locked policy cannot be removed or reduced, although its period can be increased. Objects remain protected until they satisfy the applicable retention period. Administrative ownership is not documented as a bypass for reducing the locked retention requirement.

VAREXIS-INDEX Single Request

Relevant public records

Does a Cloud Storage lifecycle eligibility timestamp establish when an object was actually deleted?

Cloud Storage evaluates lifecycle actions asynchronously and warns against relying on execution within a fixed interval after eligibility. Configuration changes can take up to 24 hours to take effect, during which actions may still follow the previous rules. Deletion can also enter soft delete rather than immediately erase the stored object.

VAREXIS-INDEX Single Request

Relevant public records

Does overwriting an Azure blob remove the data stored in its previous versions when versioning is enabled?

Azure Blob versioning preserves previous versions as immutable content and assigns version IDs to changes. Earlier versions can remain available after modification or deletion of the current blob. Microsoft recommends separate lifecycle or storage-action cleanup for old versions. Versioning itself does not protect against deletion of the storage account or container.

VAREXIS-INDEX Single Request

Relevant public records

Does Azure Blob point-in-time restore recover every blob type and a container deleted during the restore period?

Azure point-in-time restore is limited to block blobs in supported standard general-purpose v2 accounts and supported access tiers. It does not restore append, page or premium block blobs, and it does not restore a deleted container. A restore range containing blobs in a deleted container can fail. Recovery scope depends on resource type and history.

VAREXIS-INDEX Single Request

Relevant public records

Does clearing an Azure Blob legal hold permit deletion while a separate time-based retention policy still applies?

Azure immutable storage permits legal holds and time-based retention together. A hold lasts until explicitly cleared, while time-based protection follows its configured period. The documentation requires the absence of an applicable legal hold and time-based retention restriction for deletion to succeed. Clearing only one protection does not resolve the other.

VAREXIS-INDEX Single Request

Relevant public records

Does setting an Azure Key Vault key to disabled prove that its key material has been destroyed?

Key Vault exposes enabled as a key attribute controlling cryptographic use and documents key deletion as a separate operation. Deleted keys can themselves remain recoverable under soft delete. A disabled attribute is therefore not a key-destruction receipt, and even a deletion response must be interpreted with the vault’s retention and purge protections.

VAREXIS-INDEX Single Request

Relevant public records

Does removing an Azure object-replication policy itself demonstrate cleanup of destination blob copies?

Microsoft’s removal procedure deletes policy objects and their rules on both source and destination accounts. Recreating a policy establishes a new relationship with a new ID and does not reuse the old replication state. The replication guide separately describes destination blob versions and asynchronous copying. Policy removal is control-plane evidence, not a destination erasure report.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful Pinecone delete response establish that an immediate query cannot return the deleted records?

Pinecone documents eventual consistency and a possible delay before changed records are visible to queries. Its delete guide directs users to check data freshness after changes. A successful deletion request and the subsequent read view are separate observations; the response alone does not establish immediate disappearance from every query.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a Pinecone index establish that all of its independently created backups are gone?

The Pinecone Python SDK documentation states that backups outlive their source index. Project-wide backup listings include deleted-index backups, while an index-scoped lookup can return 404 after the active index is removed. It documents include_deleted for looking up backups across historical uses of the index name. Index absence is not backup absence.

VAREXIS-INDEX Single Request

Relevant public records

Does a Pinecone record count or paginated list of IDs establish a complete export of stored vector values and metadata?

Pinecone’s list operation returns IDs within a namespace, optionally filtered by prefix, without the data behind them. Fetching the records is a separate operation that returns stored values and metadata. Matching a count or enumerating IDs therefore does not establish that the exported content contains every required record and field.

VAREXIS-INDEX Single Request

Relevant public records

Does a completed Pinecone import prove every source record was successfully imported when error_mode is continue?

Pinecone documents abort and continue import error modes. Continue permits the operation to proceed after record errors without notifying which records failed; the describe operation reports how many were imported. The guide also describes silently skipped namespace directories containing no supported import files. Completion is not a record-by-record reconciliation of the source.

VAREXIS-INDEX Single Request

Relevant public records

Does a Qdrant write completed with wait=true establish that every configured replica has applied the change?

Qdrant distinguishes a queued acknowledgement from a completed operation through wait. Replica acknowledgement is separately governed by write_consistency_factor, whose default is one. Offline replicas may receive updates after recovery. An error caused by insufficient acknowledgements can still leave a change partially applied. Completion must be interpreted with the configured replication and consistency requirements.

VAREXIS-INDEX Single Request

Relevant public records

Does recovering a Qdrant snapshot always replace existing collection data with the snapshot contents?

Qdrant snapshot recovery supports replica, snapshot and no_sync priorities. The default replica priority favours existing replicas during conflict resolution; snapshot priority favours the snapshot. The guide warns that restoring into a new collection requires snapshot priority because empty existing state can otherwise win. Recovery is not a universal replace-or-merge operation independent of these settings.

VAREXIS-INDEX Single Request

Relevant public records

Does deleting a Qdrant payload index remove the indexed values from stored point payloads?

Qdrant exposes a field-index deletion operation separately from payload mutation. Its payload guide documents deleting selected keys and clearing all payload fields as distinct operations on points. Removing an index therefore does not establish that the underlying field values were removed; payload cleanup requires its own scoped request and resulting-state evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does atomically moving a Qdrant alias to a replacement collection remove the old collection and its data?

Qdrant aliases are names that refer to collections. Its documented migration pattern creates a replacement collection and atomically switches alias operations so callers can use the new collection. Alias changes and collection deletion are different operations. A successful alias switch establishes routing, not removal of the old collection or its snapshots.

VAREXIS-INDEX Single Request

Relevant public records

Does Qdrant read-only collection access prevent a permitted user from downloading a collection snapshot?

Qdrant’s access matrix permits listing and downloading collection and shard snapshots for collection read access as well as broader roles. Collection snapshots include points, payload and collection configuration. Read-only is therefore not an export prohibition within the authorised collection scope. Full-storage snapshots have different permissions and must not be inferred from collection access.

VAREXIS-INDEX Single Request

Relevant public records

Does a Snowflake transient table retain the same historical recovery window as a permanent table?

Snowflake transient tables support zero or one day of Time Travel and have no Fail-safe period. Permanent tables have a separate seven-day Fail-safe period and edition-dependent Time Travel settings. Selecting a transient table changes the recovery boundary; neither a table name nor a general account retention assumption establishes the applicable history.

VAREXIS-INDEX Single Request

Relevant public records

Does expiry of a Snowflake Time Travel retention period prove the historical data has already moved into Fail-safe?

Snowflake documents that a long-running Time Travel query delays moving the data and objects it uses into Fail-safe until the query completes. The configured retention period is therefore not, by itself, proof of the observed storage transition. This does not grant a general right to start new historical queries after their retention window has expired.

VAREXIS-INDEX Single Request

Relevant public records

Can a transient clone retain shared Snowflake micro-partitions after its permanent source table is dropped?

Snowflake zero-copy clones initially share micro-partitions with their source. The documentation explains that a transient clone can keep shared bytes in use after the permanent source table is dropped, delaying their entry into Fail-safe until the clone no longer needs them. Dropping the source does not establish that every copy or shared partition is gone.

VAREXIS-INDEX Single Request

Relevant public records

Does access to a Snowflake secure data share give the consumer an independently stored exit copy?

Snowflake Secure Data Sharing provides access through the services layer without copying or transferring the shared data between accounts. Consumers receive permitted read access to shared objects. Access to a share therefore does not establish possession of a separate export that remains usable independently of the provider’s sharing and object availability.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful Snowflake COPY INTO location export prove that all unmasked source rows and their governance policies were preserved?

COPY INTO location unloads a table or query result. Snowflake masking policies can transform unloaded values, and row access policies govern rows visible to the query under their evaluated context. A successful unload therefore reflects its query and policy context; it does not establish an unfiltered, unmasked source copy or a portable enforcement implementation in the output files.

VAREXIS-INDEX Single Request

Relevant public records

Does DROP EXTERNAL TABLE in Snowflake delete the underlying files from external storage?

Snowflake documents that DROP EXTERNAL TABLE removes only table metadata; none of the underlying data files are dropped. External tables also cannot be restored with UNDROP. Removing the Snowflake object and deleting externally held files are separate operations, with different recovery and evidence requirements.

VAREXIS-INDEX Single Request

Relevant public records

Does a Delta row deletion using deletion vectors immediately remove the row bytes from all underlying data files?

Databricks deletion vectors mark rows as removed without immediately rewriting the underlying data files. REORG TABLE with APPLY PURGE rewrites files containing soft-deleted data, but the old files remain until eligible VACUUM cleanup. Other compaction operations do not necessarily rewrite every affected file. Logical deletion, file rewrite and retained-file cleanup are distinct stages.

VAREXIS-INDEX Single Request

Relevant public records

Does a scoped Exchange application RBAC assignment restrict an existing unscoped Entra application grant?

Microsoft describes Exchange application RBAC and Entra application permissions as additive. An unscoped Entra grant can therefore provide access beyond a scoped RBAC assignment. Application Access Policies constrain the Entra grant path; they do not turn the separate RBAC assignment into a restriction on all other grants.

VAREXIS-INDEX Single Request

Relevant public records

Does owning an app registration establish authority to grant every Microsoft Graph application permission?

Microsoft lists specific roles for tenant-wide consent. Privileged Role Administrator can consent to any API permission, while the listed Cloud Application, Application and AI Administrator roles exclude Microsoft Graph application permissions. Appropriately configured custom roles are another documented path. App ownership alone is not the required tenant-wide consent evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does an Entra federated credential for one GitHub branch automatically trust every branch in that repository?

The standard federated-credential guide requires issuer and subject values to match the external token. Its GitHub configuration distinguishes environment, branch, pull request and tag subjects. The documented branch and tag setup does not support wildcard patterns. Repository identity alone does not describe the configured subject boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does Playwright saved storage state automatically preserve every authentication mechanism?

The current authentication guide covers cookies, local storage, IndexedDB and passkey-based authentication, but separately states that Playwright has no API to persist session storage. It supplies a custom save/load example for that case. Supported mechanisms and relevant storage-state options must be checked for the installed version.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful Playwright click establish that a server accepted the intended business action?

Playwright auto-waits for actionability checks such as visibility, stability, event reception and enabled state. Its navigation guide describes a hydration case where an enabled button is clicked before listeners attach and the click has no effect. Passing the click operation therefore does not itself establish a server-side business result.

VAREXIS-INDEX Single Request

Relevant public records

Does supplying a subject token and requested audience automatically grant delegated OAuth authority?

RFC 8693 distinguishes the subject token from an optional actor token representing the party receiving delegated rights. Issuing a composite token depends on authorization-server policy and configuration. Request parameters describe desired delegation; they do not themselves establish an approved grant to the actor for the target resource.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent treat a retained refresh token or an invalid_grant response as proof of continuing authority?

RFC 6749 requires the server to validate a refresh token and bind it to the client. Its invalid_grant error can mean an invalid, expired or revoked grant or refresh token, a redirect mismatch, or issuance to another client. Possessing saved credentials does not establish validity, and the error alone does not identify one unique revocation cause.

VAREXIS-INDEX Single Request

Relevant public records

Does TokenReview authenticated=true establish that a Kubernetes token is valid for any service audience?

TokenReview accepts intended audience identifiers and reports compatible audiences in its status. A caller that requested audiences must check that a compatible audience was returned; when no audiences are requested the API-server audience is the default. An authenticated result alone does not establish validity for an arbitrary relying service.

VAREXIS-INDEX Single Request

Relevant public records

Can a GitHub installation token request broader permissions or repositories than the app installation allows?

GitHub allows installation-token requests to narrow repositories and permissions, but not exceed the installation’s grants. Omitting those restrictions gives the token the installation’s permitted repositories and permissions. The documented token lifetime is one hour; an organization owner’s identity does not enlarge this token’s grant ceiling.

VAREXIS-INDEX Single Request

Relevant public records

Can a newly generated fine-grained GitHub token access private organization resources while required approval is pending?

When an organization requires approval, a fine-grained personal access token remains pending until an administrator reviews it and can only read public resources before approval. An organization owner’s request is automatically approved. Token generation and effective private-resource authorization are therefore separate states.

VAREXIS-INDEX Single Request

Relevant public records

Does repository contents-write permission establish that a GitHub App can bypass repository rulesets?

GitHub rulesets have an explicit bypass list that can include selected apps, roles and teams. Bypass can be limited to pull requests or allowed always, depending on configuration. A token’s contents-write permission does not identify whether the app is on that list or which bypass mode applies.

VAREXIS-INDEX Single Request

Relevant public records

Does Slack administrator preapproval establish that an app is already installed and active in the workspace?

Slack describes preapproval as allowing members to install and use an app. Approval and installation are separate operations. The same guide warns that restricting an app already installed does not stop its use unless it is uninstalled. Policy status alone is therefore not an inventory of active installations.

VAREXIS-INDEX Single Request

Relevant public records

Can a Slack app-level token replace a bot token for arbitrary Web API operations?

Slack describes app-level tokens as supporting specific app-wide APIs, including operations spanning installations. Bot and user tokens represent different identities and scopes. App-level status does not supply the token type or authority required by every Web API method. The method’s accepted token types remain decisive.

VAREXIS-INDEX Single Request

Relevant public records

Does approval of chat:write.customize alone justify posting a Slack message as a user?

Slack permits customized message appearance with the additional chat:write.customize scope, but says the feature should respond to an inciting user action and be clearly signposted in advance. Scope approval alone is not the user-specific permission described for posting on their behalf. The method also documents deletion limitations for impersonated messages.

VAREXIS-INDEX Single Request

Relevant public records

Do OAuth scopes restrict which users a Google Workspace domain-wide delegated account can impersonate?

Google’s domain-wide delegation guidance states that OAuth scopes limit types of data but do not restrict which users the service account can impersonate. Choosing narrower scopes is therefore not a per-user impersonation allowlist. The guide recommends limiting use of domain-wide delegation and protecting the delegated service account.

VAREXIS-INDEX Single Request

Relevant public records

Can an external Google OAuth app assume the same refresh-token lifetime in testing and production?

Google documents seven-day refresh-token expiry for an external app in Testing, except when requested scopes are limited to the specified name, email and profile subset including OpenID equivalents. Other revocation and expiry causes remain relevant. Leaving Testing does not establish that a refresh token will remain valid indefinitely.

VAREXIS-INDEX Single Request

Relevant public records

Does seeing Google Drive file metadata establish that an agent can download or export its content?

The Drive guide instructs callers to check capabilities.canDownload before downloading or exporting content. Blob downloads and Google Workspace exports use different methods; exports require a supported format and are subject to documented limits. A known file ID or readable metadata does not establish those content-access conditions.

VAREXIS-INDEX Single Request

Relevant public records

Can the documented Salesforce connected-app client-credentials flow operate without a configured run-as user?

Salesforce’s connected-app guide requires enabling client credentials and selecting an execution or run-as user. API actions use that user’s permissions, with the integration-user licence and permission configuration considered separately. A client identifier and secret do not replace the execution identity. This is the documented 2024 connected-app flow, not a claim about new-app provisioning defaults.

VAREXIS-INDEX Single Request

Relevant public records

Does editing a Salesforce permission-set group immediately change its assigned users’ effective permissions?

Salesforce distinguishes Updated, Outdated, Updating and Failed permission-set-group states. Users do not receive the revised combined permissions until recalculation succeeds; failure leaves changes unpropagated. The guide also documents different recalculation timing for standard Salesforce-owned permission sets. Saving an edit is not proof that the effective combined permission set changed.

VAREXIS-INDEX Single Request

Relevant public records

Does every Apex version enforce the same default field and object permissions as the Salesforce user interface?

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.

VAREXIS-INDEX Single Request

Relevant public records

Does Salesforce OAuth full scope grant data access beyond the logged-in user’s assigned authority?

Salesforce defines full as access to data accessible by the logged-in user. It does not independently return a refresh token; refresh_token must be requested explicitly. API scope names describe access paths within the user context, not a replacement for the user’s underlying permissions and sharing boundary.

VAREXIS-INDEX Single Request

Relevant public records

Does locking a Notion page prevent edits through its API by an otherwise authorized connection?

Notion’s update-page reference states that is_locked controls editing in the Notion interface and does not affect API updates. API capability and page-access requirements remain separate. A visible page lock therefore is not evidence that a connected integration has lost update authority.

VAREXIS-INDEX Single Request

Relevant public records

Does sharing one Notion database guarantee complete relation and rollup values from its related databases?

Notion instructs integrations to share the related database as well. Missing access can leave relation values empty or make formula and rollup results incomplete. An empty relationship is therefore not sufficient evidence that no related data exists. This review concerns documented database relations, not every arbitrary external link.

VAREXIS-INDEX Single Request

Relevant public records

Does access to a ServiceNow REST endpoint establish permission to every table and field it exposes?

The Brazil REST guide separates endpoint role and ACL requirements from table and field access. Fields denied by ACLs are omitted from REST query responses. Direct table web-service access also has a dedicated enablement setting; application CRUD flags such as Can read or Can create do not apply to web-service requests.

VAREXIS-INDEX Single Request

Relevant public records

Does hiding or restricting a field with a ServiceNow UI policy establish the same restriction for REST writes?

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.

VAREXIS-INDEX Single Request

Relevant public records

Can an MCP client safely open an authorization URL merely because an MCP server supplied it?

The 2026-07-28 MCP security guidance requires validation of server-supplied authorization URLs, rejection of dangerous schemes and avoidance of shell execution when opening them. HTTP is restricted to loopback development; production authorization servers use HTTPS. This is a client URL-handling requirement, separate from the token’s resource-audience validation.

VAREXIS-INDEX Single Request

Relevant public records

Does SMART launch/patient context grant an agent permission to read that patient’s clinical records?

SMART App Launch 2.2 distinguishes launch context from clinical resource scopes. launch/patient requests patient context; patient, user and system scopes describe different access contexts. Granted scopes remain constrained by the underlying system permissions. A patient identifier in a launch response is not itself a clinical read grant.

VAREXIS-INDEX Single Request

Relevant public records

Does a SMART Backend Services access token establish patient consent for an administrative workflow?

SMART Backend Services 2.2 uses preauthorized access: the client and server establish permitted scopes before runtime, and the client authenticates using asymmetric credentials to request a token. This flow does not require an end-user authorization interaction at runtime. Its token therefore documents a system grant rather than a patient consent decision.

VAREXIS-INDEX Single Request

Relevant public records

Does every FHIR CapabilityStatement describe the controls enforced by a deployed endpoint?

FHIR R5 distinguishes instance, capability and requirements statements. An instance statement describes a deployed configured solution; a capability statement describes software capabilities independently of a particular installation; a requirements statement describes desired capabilities. The statement kind and implementation reference therefore matter when assessing a concrete endpoint.

VAREXIS-INDEX Single Request

Relevant public records

Does HTTP 200 from a SMART-authorized FHIR search prove that every matching clinical record was returned?

SMART 2.2 states that scopes cannot exceed underlying system permissions. Its permission examples allow a successful 200 response while records are omitted because access is unavailable, or a forbidden response. A successful request is therefore not a completeness certificate for the clinical dataset.

VAREXIS-INDEX Single Request

Relevant public records

Does a successful FHIR R5 DELETE erase all historical versions and physical copies of a resource?

FHIR R5 defines DELETE as removing a resource from ordinary search and non-version-specific access. For servers maintaining version history, the interaction does not remove that history. Resource deletion also does not imply a change to the corresponding real-world object unless the resource documentation specifies it.

VAREXIS-INDEX Single Request

Relevant public records

Does a completed FHIR Bulk Data export with HTTP 200 guarantee a complete error-free dataset?

Bulk Data Access 3.0 permits partial success to use HTTP 200. Its output manifest has an error array linking OperationOutcome files, including warnings and information, and can link further manifests when partial manifests are enabled. Clients must reconcile those files and links with requested types and authorization scope.

VAREXIS-INDEX Single Request

Relevant public records

Does storing a FHIR Consent resource cause the server to enforce its privacy choices?

FHIR R5 describes Consent as a record of permission choices. The resource scope excludes enforcement of the privacy directive and the detailed access-control meaning of its elements. Implementers must supply enforcement through their chosen mechanisms, such as role, attribute or token-based controls.

VAREXIS-INDEX Single Request

Relevant public records

Does a FHIR Provenance resource or signature establish that its clinical content is true?

FHIR R5 defines Provenance as record-keeping assertions about activities and agents that created, revised, deleted or signed a resource version. Applications prepare these assertions; signatures can target the resource. The information supports assessment and further investigation of origins, rather than independently establishing the truth of clinical facts.

VAREXIS-INDEX Single Request

Relevant public records

Does trusting an OPC UA application certificate authorize every node operation for its user?

OPC UA Part 4 separates application certificate trust and user authentication from authorization. Even when an external authorization service is involved, the server remains responsible for enforcing node permissions. Trusting an application does not describe the user’s permitted operations on each node.

VAREXIS-INDEX Single Request

Relevant public records

Does a Good OPC UA DataValue status prove the underlying measurement is fresh?

OPC UA Part 4 distinguishes a value’s status from sourceTimestamp and serverTimestamp. The source timestamp identifies the source’s value or status change, while the server timestamp reflects the server’s knowledge of the value. A Good status is not a freshness threshold or independent sensor calibration result.

VAREXIS-INDEX Single Request

Relevant public records

Does receiving OPC UA subscription updates prove every intermediate value was preserved?

OPC UA monitored items sample values and queue notifications. When a queue larger than one overflows, the specified overflow indication records loss while discard settings decide which queued value is removed. A queue of one behaves differently and does not use that overflow indication. Sampling itself can miss changes between samples.

VAREXIS-INDEX Single Request

Relevant public records

Can OPC UA Republish reconstruct every missing notification after a sequence gap?

OPC UA subscriptions sequence NotificationMessages and may retain them in a retransmission queue. Republish requests a particular retained sequence number; Bad_MessageNotAvailable indicates the requested message is unavailable. Detecting a sequence gap therefore does not establish that the missing content can still be recovered.

VAREXIS-INDEX Single Request

Relevant public records

Does an OPC UA Call result alone prove that the intended physical operation completed?

OPC UA Call returns per-method execution status and outputs under the method’s application-defined semantics. The specification says results can be discarded when a session terminates independently of the actual server task, and execution order for multiple operations is undefined. A generic call outcome does not supply a universal physical-completion criterion.

VAREXIS-INDEX Single Request

Relevant public records

Can an OPC UA endpoint be accepted when its ApplicationURI differs from the certificate identity?

OPC UA Part 4 version 1.05.07 requires application URI consistency between the certificate and application description. CreateSession specifies client and server checks, including Bad_CertificateUriInvalid for a client mismatch. Certificate trust alone does not satisfy this application-identity binding.

VAREXIS-INDEX Single Request

Relevant public records

Does an approved Coupa document establish authority for a later purchase-order change?

Coupa’s Approvals API binds an approval to an approvable object and type, an approval chain, status and approver information. Approve and reject actions require a Pending approval. Purchase-order changes have their own operations and approval handling. A past approval record therefore does not, by itself, identify approval for a changed order.

VAREXIS-INDEX Single Request

Relevant public records

Does an unchanged Coupa purchase-order version prove no order data changed before ERP synchronization?

Coupa documents that not every PO change increments the supplier version; updated-at can identify changes. Edits that create a new version and resend reset exported to false. For ERP revisions, the change API guide directs integrations to the PO GET API with exported=false and version, rather than treating change-request retrieval as the revision feed.

VAREXIS-INDEX Single Request

Relevant public records

Does submitting a Coupa requisition through the API establish that its approval chain completed?

Coupa documents a submit_for_approval requisition action separately from approval actions and approval status. The Approvals API exposes the approvable object, chain, approver and status, with Pending required for approve or reject. Submission starts the relevant approval workflow; it is not evidence that every required approval has occurred.

VAREXIS-INDEX Single Request

Relevant public records

Does a Purview eDiscovery estimate or successful process status prove that the exported evidence is complete?

Purview process reports distinguish estimates from exported or collected items. Summary information explains count changes, and item reports identify retrieval exceptions. Differences can arise from attachments, versions, conversations and duplicates as well as errors; equality of headline counts is not a substitute for reconciliation.

VAREXIS-INDEX Single Request

Relevant public records

Does a Purview eDiscovery search automatically include content that was not fully indexed?

Purview’s process-report guidance states that search results exclude partially indexed content by default, including unsupported formats and processing failures. Settings.csv records whether partially indexed items were included. A zero-hit result therefore does not establish absence of relevant content in those unsearched items.

VAREXIS-INDEX Single Request

Relevant public records

Does naming a custodian in a Purview eDiscovery hold establish that every intended location is successfully held?

Purview process reports use Locations.csv to expose included locations, processing status and errors. Hold failures can include ineligible objects; the guide distinguishes eligible mailbox and site locations from objects such as distribution groups. A hold action must therefore be reconciled with actual location outcomes.

VAREXIS-INDEX Single Request

Relevant public records

Does a Purview eDiscovery search hit guarantee that encrypted content can be reviewed or exported in plaintext?

Purview decryption requires the relevant RMS Decrypt role and supported encryption configuration. The guide describes documents found through metadata that remain encrypted on export, and states that nested encrypted content inside containers is not recursively decrypted. A search hit, decryption eligibility and accessible content are separate observations.

VAREXIS-INDEX Single Request

Relevant public records

Does current AWS Cost Explorer or Cost and Usage Report data prove the final charge for a completed workflow?

AWS refreshes Cost Explorer data at least daily but notes upstream delays. Cost and Usage Reports are estimates during the month; service usage can arrive at different times. Usage charges are finalized after invoicing, and later credits, refunds or support adjustments can still update reports.

VAREXIS-INDEX Single Request

Relevant public records

Can activating an AWS cost-allocation tag today reconstruct attribution for resources that were never tagged?

AWS permits management accounts to request cost-allocation tag backfill for up to twelve months. Backfill uses tags historically assigned to resources and applies the current activation state. It does not invent past resource tags; activation and historical assignment are different conditions.

VAREXIS-INDEX Single Request

Relevant public records

Can an agent estimate OpenAI prompt cost by charging every input token at one uncached rate?

OpenAI’s current prompt-caching guide distinguishes uncached input, cached input and cache-write rates, with model-specific pricing. Cache-write pricing is not an additive fee in that guide. Cached-token usage and the applicable model’s rate categories therefore matter when reconciling a request.

VAREXIS-INDEX Single Request

Relevant public records

Does using one AI Gateway endpoint mean every fallback request used the same model and cost basis?

Vercel AI Gateway can try different models and providers after a failure, and providers have different pricing characteristics. The modelAttempts metadata identifies attempted models and provider attempts. The guide warns that some normalized Python beta metadata can omit routing details, requiring the raw response or request logs.

VAREXIS-INDEX Single Request

Relevant public records

Does a compatible dependency range alone guarantee that npm installs the previously reviewed dependency tree?

npm’s package lock records a resolved dependency tree. npm ci requires a lockfile and fails when its dependencies disagree with package.json instead of updating the lock. Its installation does not rewrite the lock, and tree-shaping flags must match those used to create it. A version range alone is not this frozen-install evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does an A2A task’s completed state establish that the buyer accepted the delivered service?

The captured A2A specification defines completed as a terminal successful task state. Task status and output artifacts describe the protocol operation. The core task model does not itself supply the buyer’s contractual acceptance criteria or an independent verification of artifact quality.

VAREXIS-INDEX Single Request

Relevant public records

Does advertising an A2A extension guarantee compatible semantics with every version of that extension?

The captured A2A specification requires a new extension URI for breaking changes. An unsupported optional extension should be ignored; a required unsupported extension must produce an error. Automatic fallback to an older extension version is prohibited. Advertising an extension without matching its version and required status is not compatibility evidence.

VAREXIS-INDEX Single Request

Relevant public records

Does receiving an authenticated A2A push notification establish a final task outcome?

A2A push notifications can carry a task, message, status update or artifact update. Clients must check the expected task ID, and duplicate delivery is possible. Authentication identifies the configured notification path; it does not turn every event type into a terminal outcome.

VAREXIS-INDEX Single Request

Relevant public records

Can an OpenTelemetry Collector memory limiter refuse telemetry before durable storage?

The reviewed Collector memory-limiter implementation returns a non-permanent error when memory limits require refusal. The preceding component is expected to retry and may apply backpressure. Its documentation warns that telemetry is permanently lost if that component fails to retry correctly. Garbage collection is not a persistence acknowledgement.

VAREXIS-INDEX Single Request

Relevant public records

Does a W3C sampled trace flag require every downstream component to record the operation?

W3C Trace Context treats trace flags as recommendations rather than strict downstream instructions. Trust decisions, implementation defects and downsampling can affect recording. The sampled bit conveys a caller recording decision; it is not confirmation that every downstream span was stored.

VAREXIS-INDEX Single Request

Relevant public records

Can an unfamiliar traceparent version or all-zero identifier be accepted without validation?

The pinned W3C Recommendation makes all-zero trace and parent identifiers invalid. Its higher-version parsing rules require checks of length, separators and known fields rather than blindly applying a current-format parser. Valid parsing establishes a usable context format, not an authenticated event history.

VAREXIS-INDEX Single Request

Relevant public records

Does the W3C parent-id field contain the complete upstream request history?

The W3C parent-id identifies the caller’s current request or span, while trace-id identifies the overall distributed trace. Neither field contains the full upstream sequence. Reconstructing earlier operations requires the corresponding recorded spans and their parent relationships.

VAREXIS-INDEX Single Request

Relevant public records

Can customer identifiers or sensitive business data be embedded in W3C trace context?

The pinned W3C Recommendation prohibits personally identifiable and other sensitive information in traceparent and tracestate. It also cautions against identifiable random-number generation seeds. Correlation identifiers travel across components and must not become a covert customer-data channel.

VAREXIS-INDEX Single Request

Relevant public records

Can different Stripe Event IDs still represent duplicate processing of the same underlying effect?

Stripe distinguishes repeated delivery of one Event from cases where two separate Event objects are generated. Its webhook guidance recommends using the underlying object ID together with event type to identify the latter. Application idempotency must still respect legitimate later transitions; different Event IDs alone do not prove distinct business effects.

VAREXIS-INDEX Single Request

Relevant public records

Does a new Stripe webhook signature timestamp mean the business event was created again?

Stripe’s Event created field records object creation time. A retry delivery receives a new signature and signature timestamp. These observations refer to different stages: the Event’s creation and a particular delivery attempt. Neither timestamp alone establishes causal order across concurrent business actions.

VAREXIS-INDEX Single Request

Relevant public records

Does retrieving an old Stripe Event with a newer API version upgrade its stored data schema?

Stripe documents that an Event’s data is rendered using its api_version when created and remains unchanged. Updating the account version or retrieving an older Event through a newer API version does not retroactively rewrite that stored Event. The parser must respect the recorded version.

VAREXIS-INDEX Single Request

Relevant public records

Can a parsed and reserialized Stripe webhook body be substituted for the original bytes during signature verification?

Stripe requires the unmodified raw request body for webhook signature verification. Framework parsing or other changes can cause verification to fail. Verification also depends on the correct endpoint signing secret; a CLI listener secret is distinct from the Dashboard endpoint’s secret.

VAREXIS-INDEX Single Request

Relevant public records

Can a Stripe event be reconciled against an arbitrary account when it originated from a connected account or organisation context?

The Event account field identifies the originating connected account, while context supplies authentication context for relevant event/object retrieval. Stripe’s organisation guidance requires the corresponding Stripe-Context when fetching manually; documented SDK fetch helpers apply that context automatically. Event identity does not remove account scoping.

VAREXIS-INDEX Single Request

Relevant public records

Can more than one Stripe webhook signing secret remain valid during a planned rotation?

Stripe allows immediate secret expiration or a delayed expiration of up to twenty-four hours. During the overlap, multiple secrets can be active and Stripe generates a signature for each active secret. Rotation completion therefore requires checking the old secret’s expiry rather than assuming it stopped working when the new one appeared.

VAREXIS-INDEX Single Request

Relevant public records

Does fetching the related object for a Stripe thin event reconstruct its exact historical state?

Stripe thin notifications contain limited event information. The event and its related object can be retrieved separately; retrieving the related object returns its latest state, not necessarily the state when the notification was generated. A current object must not be silently presented as the historical event snapshot.

VAREXIS-INDEX Single Request

Relevant public records

Can the Stripe v1 Event retrieval API reconstruct events older than its documented retrieval window?

The reviewed v1 Retrieve Event reference makes events available for retrieval only for thirty days. That endpoint is not a permanent audit archive. Failure to retrieve an older Event cannot by itself establish that the underlying payment never occurred.

VAREXIS-INDEX Single Request

Relevant public records

Can a GitHub Actions rerun keep the same run ID while producing different attempt evidence?

GitHub documents that GITHUB_RUN_ID and GITHUB_RUN_NUMBER remain unchanged on rerun, while GITHUB_RUN_ATTEMPT increments for each attempt. A run ID alone therefore cannot distinguish the logs, results and artifacts produced by separate attempts.

VAREXIS-INDEX Single Request

Relevant public records

For MCP 2025-11-25, does successful initialization permit calls to every client-advertised capability?

MCP 2025-11-25 requires initialize first, negotiation of version and capabilities, and a subsequent initialized notification before normal operation. Successful initialization does not mean every capability advertised by one participant is supported by the other. The reviewed 2026-07-28 protocol instead documents per-request version compatibility without that initialization handshake.

VAREXIS-INDEX Single Request

Relevant public records

Does absence of an MCP tools/list_changed notification prove a cached tool schema is unchanged?

In the reviewed 2026-07-28 tools specification, servers advertising listChanged should notify clients whose subscriptions/listen stream requests toolsListChanged. This is a SHOULD requirement tied to capability and subscription context. Silence alone is not a verified immutable tool inventory or schema.

VAREXIS-INDEX Single Request

Relevant public records

Does publishing an AgentCore Runtime update put every endpoint and existing session on the new version?

AgentCore Runtime updates create immutable versions. DEFAULT tracks the latest version, while custom endpoints require an explicit version update. The lifecycle guidance states that an existing microVM continues with the version used when it was created until termination; a version publication is not evidence that every active execution changed.

VAREXIS-INDEX Single Request

Relevant public records

Does an AgentCore idle timeout necessarily invalidate the session identifier and erase every persisted state?

AgentCore documents that idle or maximum-lifetime limits can stop the session’s compute. A later invocation can provision new compute; the session identifier remains valid until the Runtime ARN is deleted. Configured session storage can preserve its mounted filesystem across stop/resume, while ordinary in-memory or ephemeral disk state does not gain that persistence.

VAREXIS-INDEX Single Request

Relevant public records

Does creating a Google Cloud log sink always grant its writer permission at the destination?

Google Cloud requires the sink’s writer identity to have appropriate destination permissions. Some console creation paths can grant permissions when the operator has the necessary authority; other configurations require an explicit grant. A sink targeting a log bucket in the same project has a documented no-writer-identity exception.

VAREXIS-INDEX Single Request

Relevant public records

Does one granted authorizationInfo entry prove every permission required for a Google Cloud action was granted?

Cloud Audit Logs defines authorizationInfo for resource-and-permission pairs. The granted field applies to the permission and resource represented by that entry. A single granted tuple is not a statement that every required permission, policy condition or downstream business effect succeeded.

VAREXIS-INDEX Single Request

Relevant public records

Does total Azure Log Analytics retention guarantee the same interactive query window for every table plan?

Azure distinguishes analytics retention from long-term retention. Analytics and Basic long-term data is retrieved through search jobs, while Auxiliary data remains queryable throughout its total retention period. The table plan and retention state therefore determine the available retrieval method; retained data is not always available through the same query path.

VAREXIS-INDEX Single Request

Relevant public records

Can an Azure diagnostic setting deliver to a firewalled Storage or Event Hubs destination without the required network allowance?

Azure diagnostic guidance requires the trusted Microsoft services network bypass for supported Storage or Event Hubs destinations with firewalls enabled. Creating a diagnostic setting does not itself establish reachable, authorized delivery. These destination-specific rules should not be generalized to every Log Analytics configuration.

VAREXIS-INDEX Single Request

Relevant public records

Does A2A task resubscription guarantee replay of every event missed while disconnected?

The reviewed A2A SubscribeToTask operation begins with the current Task object and then streams updates for a nonterminal task. Its initial snapshot closes a current-state observation gap; the operation does not promise a complete replay of every intermediate event missed during disconnection.

VAREXIS-INDEX Single Request

Relevant public records

Does an A2A artifact’s lastChunk flag mean the entire task has completed?

A2A TaskArtifactUpdateEvent can append content to an artifact with the same ID. Its lastChunk flag identifies the final chunk of that artifact. Task lifecycle status is separate, so one finished artifact cannot be substituted for the terminal task outcome or acceptance of all outputs.

VAREXIS-INDEX Single Request

Relevant public records

Does omitting A2A historyLength guarantee the server returns the complete retained conversation?

A2A historyLength limits the most recent messages requested. Zero requests no messages; an unset value imposes no client limit. The server may still apply a lower limit. An unrestricted client request is therefore not a protocol guarantee of complete retained history.

VAREXIS-INDEX Single Request

Relevant public records

Can an authenticated A2A Agent Card expose different capabilities from its public card or another client’s card?

A2A requires authentication for Get Extended Agent Card and permits different content according to client identity or authorization level. Extended cards may include additional skills. Retrieving a card does not independently verify that the client has every credential required for a later operation.

VAREXIS-INDEX Single Request

Relevant public records

Does a Foundry classic run in requires_action state prove its requested external function has executed?

The reviewed Foundry classic function-calling guide uses requires_action to request application-side function execution. The application performs the work and submits output associated with the tool_call_id; the run can then continue. A requested call or application-submitted output is not independent verification of the external action.

VAREXIS-INDEX Single Request

Relevant public records

Does deploying an Agent Engine mean downstream tools run with the deploying caller’s identity?

The reviewed AgentEngine reference supports an explicit service_account or AGENT_IDENTITY, with mutually exclusive configuration. AGENT_IDENTITY is resource-scoped and has no default project permissions. Otherwise the configured service account, or default Reasoning Engine Service Agent, is used. Deployment and runtime authority must be established separately.

VAREXIS-INDEX Single Request

Relevant public records

Does an x402 v2 successful verify response establish that funds have moved?

The pinned x402 v2 specification defines verify as read-only. It checks an authorization without committing payment state. Settle is a separate operation whose effect depends on the selected scheme and payment flow. An isValid response therefore cannot substitute for the applicable settlement evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must every x402 v2 payment settle after the protected resource executes?

The reviewed v2 specification defines authorization, upfront and escrow flows with different ordering around resource execution. A non-authorization flow must be declared in the offered requirements. Clients must not construct payments for an unrecognised flow, and servers must reject unsupported method-and-flow combinations.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does x402 settlement_pending mean that no payment transaction was broadcast?

The reviewed EVM exact binding permits settlement_pending when a transaction was broadcast but confirmation could not be established. The response carries its transaction hash so the caller can reconcile the chain outcome before retrying. This state is different from proof that no transfer occurred.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does x402 exact upfront define an automatic refund when the resource handler fails?

The pinned exact scheme allows upfront settlement before resource execution. It explicitly notes that a handler failure can leave the client charged without delivery and that this scheme defines no refund for that situation. Any remedy is an arrangement made by the resource server.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the x402 upto amount mean the same thing during verification and settlement?

For the reviewed upto scheme, verification-time amount is the authorised maximum and settlement-time amount is the actual charge. The actual amount cannot exceed the signed maximum and may be zero. The facilitator must verify the signature against the original authorised maximum rather than the later charge.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an x402 upto authorization be charged again for its unused allowance?

The reviewed upto specification requires at most one settlement per authorization. Settlement consumes it regardless of the amount charged. Repeated settlements, recurring charges and open-ended allowances are outside this scheme; a lower first charge does not preserve the remainder as reusable authority.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an x402 payment identifier safely identify different paid operations across tenants?

The reviewed payment-identifier extension calls for binding an identifier to a normalized request fingerprint. Reuse with changed operation details should produce a conflict. It also recommends scoping keys by tenant, merchant, route or facilitator account where those boundaries exist, rather than using the identifier alone for authorization.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a successful x402 ERC-7710 simulation guarantee that the later transfer will execute?

The pinned EVM binding verifies ERC-7710 authority through simulation. Its security discussion identifies a race in which the client invalidates delegation before execution, leaving the facilitator paying gas for a failed transaction. The permission context depends on the particular delegation-manager implementation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is the facilitator the signed spender in x402 exact Permit2 authorization?

The reviewed EVM exact binding identifies the x402ExactPermit2Proxy as the signed spender, rather than the facilitator. Its witness binds the destination address. The setup separately requires token approval to Permit2, with ordinary or supported sponsored approval paths; these roles should not be collapsed into one recipient identity.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does x402 Solana exact require the matching transfer amount to equal the quoted amount exactly?

The pinned Solana exact binding permits a matching transfer greater than or equal to the required amount, including rounding-related overpayment. It nevertheless requires exactly one matching transfer across top-level and inner instructions, with the correct mint, destination and token program. Zero or multiple matching transfers must be rejected.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must a sponsor accept every transaction valid under x402 Solana exact?

The pinned binding separates the required payment outcome from sponsor acceptance policy. A sponsor may reject an otherwise valid payment on local policy grounds. Recommended controls include compute and priority-fee limits and program restrictions; successful payment validation does not entitle the client to sponsorship.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an x402 Solana sponsor sign before resolving the transaction address lookup tables?

The reviewed binding requires address lookup tables to be resolved before fee-payer isolation checks, making the reachable accounts visible. If the sponsor cannot resolve them, including a transient resolution failure, it must reject rather than verify an incomplete account set. The rule applies before signing.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a successful smart-wallet simulation alone establish x402 Solana settlement success?

The pinned Solana binding requires post-confirmation transfer verification for its smart-wallet path. The primary check inspects confirmed inner instructions; a documented fallback checks destination balance change when those instructions are unavailable. Simulation establishes expected behaviour, while settlement success must reflect actual chain effects.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Solana transaction deduplication alone prevent repeated x402 resource access?

The reviewed binding describes a settlement race in which repeated submissions can receive successful responses although the chain executes the transfer once. It recommends tracking in-flight payloads to reject duplicate settlements. Chain-level transfer deduplication and application-level resource access are separate controls.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful x402 batch-settlement response prove that value has already transferred?

The pinned batch-settlement scheme accepts and stores a cryptographic commitment during the request; its network binding redeems value later. A successful response must include a non-empty commitment identifier. That identifier is not necessarily a chain transaction hash and does not itself establish completed redemption.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Are all x402 batch-settlement commitments backed by the client on-chain funds?

The reviewed scheme permits capital-backed and credit-backed commitments. In the latter model, a trusted intermediary associates identity with a billing account and settles later. Each network binding must specify its trust model, redemption process and seller guarantee; the shared scheme name does not make those protections identical.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an x402 signed offer be bound to checkout terms using acceptIndex alone?

The reviewed offer extension describes acceptIndex as an unsigned convenience field. Clients should check its range and compare the selected payment requirements with the signed fields. The signature-covered terms, including network, asset, payee and amount, are the binding evidence; the index itself is not authoritative.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid x402 receipt signature prove that its key was authorised for the service when issued?

The reviewed extension distinguishes signature validity from authority to sign for the resource URL. Historical verification should evaluate authority at receipt issuance. Removing a key from a current authorization source does not by itself establish that it was unauthorised earlier; dated authority evidence is therefore relevant.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does every x402 signed receipt contain a transaction reference and payment amount?

The pinned receipt format deliberately permits omission of the transaction reference for privacy. Its canonical fields identify the resource, payer, network and issuance time, without requiring a payment amount. A signature authenticates the server statement; independent financial reconciliation may require additional transaction evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an x402 MCP payment error prove that the tool did not execute?

The reviewed MCP transport uses isError tool results for payment requirements and failures. It specifically covers settlement failing after tool execution and says the tool content should then be withheld. An error result therefore does not establish absence of a prior tool effect; the failure phase matters.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does x402 A2A payment-submitted or payment-verified establish completed payment?

The pinned A2A transport distinguishes submitted, verified and completed payment statuses. Payment payloads carry task correlation, and settlement results appear as receipts in task-status metadata. The submitted or verified labels are earlier states; they must not be treated as the completed settlement result.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Open Payments outgoing grant always identify the recipient before consent is obtained?

The reviewed future-payments guide supports obtaining sender-side authority before the recipient is known. Its example authorises a bounded monthly amount for future destinations, as used by Web Monetization. Possession of that grant does not establish that a particular later merchant was individually identified during the initial consent.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does unused Open Payments recurring-grant allowance roll into the next interval?

The pinned future-payments guide describes an amount that resets for each configured interval, without carrying forward the unused portion. Its example also bounds the number of repetitions and the start time. A monthly allowance is not a cumulative balance that grows when earlier periods are underspent.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Open Payments spent-amount retrieval return the lifetime total for a recurring grant?

The reviewed API guide identifies the current grant through the supplied access token and returns its debit and receive amounts. For a recurring grant, the reported amounts cover the current interval only. A lifetime spend history cannot be inferred from that one response.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does marking an Open Payments incoming resource complete prove that a target amount was paid?

The reviewed completion API tells the recipient account servicing entity that no further payments will be sent toward an unexpired incoming resource. The resource model also permits sessions without an incomingAmount. Completion therefore needs to be reconciled with received-amount evidence rather than interpreted as proof of an independently specified purchase total.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Open Payments recurring payment keep using the original quote after it expires?

The reviewed guide states that quote responses include expiresAt and the outgoing payment should be created before that time. If creation fails because the quote expired, a new quote is required. A reusable grant does not extend the lifetime of the separately quoted payment terms.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Open Payments fixed-send quote guarantee the recipient receives that same amount?

The reviewed resource model distinguishes fixed-send quotes, which specify the amount debited from the sender, from fixed-receive quotes, which specify the amount received. A quote accounts for applicable costs and is time-limited. The debit and receipt objectives are different and should be preserved separately in reconciliation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does obtaining an Open Payments recurring grant automatically initiate every later payment?

The reviewed recurring-payment guide requires the application to create a new incoming payment, quote and outgoing payment at each later interval. Existing grants may remain usable, but they do not replace those resource requests. Authority to make periodic payments is separate from scheduling and successfully initiating them.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does creating an Open Payments outgoing resource prove that inter-provider settlement completed?

The reviewed resource model says an outgoing resource can represent a payment that will be, is being or was sent. It is an instruction to the sender account servicing entity. Open Payments supplies payment instructions; settlement between the account servicing entities uses a separate shared rail.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Open Payments incomingAmount require exactly one payment of that amount?

The pinned resource model describes incomingAmount as the maximum to pay into the recipient account. One or more payments may use the incoming resource details, but their combined amounts cannot exceed that maximum. The field is an aggregate ceiling, not proof of one exact transfer or complete commercial payment.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a JWT-SVID jti claim make a SPIFFE workload token single-use?

The pinned JWT-SVID specification permits jti but does not require validators to track its uniqueness. JWT-SVIDs remain bearer tokens: audience and expiry constrain exposure without eliminating replay. A token with multiple audiences can be replayed by one recipient to another listed recipient. Single-use acceptance therefore needs separately evidenced controls.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an X509-SVID with two URI SAN identities be accepted if its certificate chain verifies?

The pinned X509-SVID specification requires exactly one URI subject alternative name and one SPIFFE ID. Validators must reject more than one URI SAN, even when ordinary certificate-path validation succeeds. Other SAN types may be present. The identity selection rule prevents a verifier from arbitrarily choosing which workload identity to authorize.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a SPIFFE CA signing certificate authenticate as the workload it issues credentials for?

The pinned X509-SVID specification reserves caller authentication for leaf certificates and prohibits using signing certificates for authentication. A leaf must have cA false, lack keyCertSign and cRLSign, and carry a SPIFFE ID with a non-root path. Possessing valid signing material is not interchangeable with presenting a valid workload leaf.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should a workload keep an old SPIFFE bundle when a later API response omits it?

SPIFFE Workload API stream responses are complete replacements, not incremental patches. Default or empty fields must replace previous values; omitted material should be treated as redacted. The X509 profile says clients should cease using redacted SVIDs or bundles, including withdrawal indicated by PermissionDenied. Retaining previously cached authority can contradict that update.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a downloaded SPIFFE trust bundle identify which trust domain it is authorized to represent?

The pinned federation specification says a bundle does not contain its trust-domain name. Clients must configure the endpoint URL, profile and associated trust domain before retrieval. Bundles from different domains must remain separate; merging them allows one domain to forge identities in another under the combined trust store. HTTPS success alone does not supply the missing domain binding.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a new SPIFFE signing key be used before foreign verifiers can fetch its bundle?

The pinned federation specification requires new externally used keys to appear at the bundle endpoint before issuing SVIDs with them. It recommends publication three to five refresh-hint intervals in advance and removing deprecated keys after no valid SVIDs remain. These are rollout conditions; a successful local issuance does not prove foreign verifiers have refreshed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can separate file reads load a mismatched SPIFFE private key and certificate despite atomic rotation?

The pinned, incubating filesystem delivery specification recommends loading the credential bundle in one open/read/close cycle. Separate cycles for key and certificate can straddle a rotation and produce a mismatched pair, even when the provisioning system writes atomically. Applications must reload updated bundles promptly and must not assume the new key type or chain matches the old one.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an empty SPIFFE credential file mean the client should keep its last cached identity?

The pinned, incubating filesystem delivery specification defines an empty credential or trust-bundle file as deliberate redaction. Consumers should unload the withdrawn material, including individual anchors removed from a remaining bundle. An absent file can instead reflect remounting or repopulation; emptiness is the stronger intentional signal. Keeping cached identity indefinitely would erase that distinction.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an OpenFGA authorization check change when the request omits authorization_model_id?

OpenFGA models are immutable, but a write creates a new model version. The pinned documentation says requests without authorization_model_id use the store’s latest model. Passing the ID binds evaluation and validation to that version. Immutability therefore does not guarantee stable authorization when applications implicitly select whichever model was created last.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does publishing a renamed relation in OpenFGA migrate existing relationship tuples automatically?

The pinned immutable-model guide describes relation renaming as a coordinated migration: create the new model, update application relation names, copy existing tuples to the new relation and deploy against the new model ID. Creating an immutable model version alone is not the tuple or application migration. Rollout evidence must connect all three states.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a successful OpenFGA tuple update be followed by a stale Check response?

The pinned consistency guide says MINIMIZE_LATENCY can use cached results, so an immediate check may omit a recent tuple change when caching is enabled. HIGHER_CONSISTENCY bypasses the cache and queries the database. Caching is documented as disabled by default. The actual configuration and request mode matter; a write receipt alone does not establish a fresh authorization decision.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a contextual tuple override the same stored relationship in an OpenFGA request?

The pinned contextual-tuples guide says request-local tuples participate in evaluation as stored tuples would, but are not persisted and affect only that request. When user, relation and object match a stored tuple, the contextual tuple takes precedence. Reviewing the database alone therefore does not reconstruct the relationships used by that specific decision.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does removing a directory group immediately remove OpenFGA access based on an unexpired token claim?

The pinned OpenFGA token-claims guide warns that relationships supplied from token claims can continue granting access until the token expires even if the underlying directory relationship changes. Contextual tuples avoid persistent synchronization but do not make the token’s claim live directory evidence. Offboarding must account for that residual acceptance window and the deployed token-handling policy.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can OpenFGA Read Changes alone reconstruct decisions that used contextual tuples?

OpenFGA contextual tuples exist only for a request and are not stored. Read Changes reports stored tuple writes and deletes, and the token-claims guide warns that permission-aware indexes built from it may not account for contextual tuples. A complete reconstruction needs the request-local inputs as well as the stored changes; the change stream is not an execution trace.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an OpenFGA temporal grant independently establish the current time used for authorization?

The pinned conditions guide models access using current_time, grant_time and grant_duration, and its query examples supply current_time in request context. The documented expression evaluates those inputs; it is not evidence of how the caller obtained or protected the clock value. A buyer must establish the provenance and freshness of time supplied for the decision.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can request context replace a condition parameter already stored in an OpenFGA relationship tuple?

The pinned conditions guide specifies a merge of persisted tuple context and request context for condition evaluation. Persisted values take precedence when both provide the same parameter. A request that sends a different grant duration does not, by that act alone, replace the stored duration. Reconstruction requires both inputs and their documented precedence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does reaching the current end of OpenFGA Read Changes make its continuation token disposable?

The pinned Read Changes guide says to persist continuation tokens across errors and restarts. At the current end, the API returns the same token, which should be saved for later polling. A token produced by an object-type filter must be reused with that type. Losing the cursor or its filter context can undermine a claimed continuous audit export.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do the pinned OpenFGA guides agree that Expand accepts contextual tuples?

At the pinned documentation revision, the contextual-tuples guide lists Expand among supported query methods, while the token-claims guide says contextual tuples are not supported on Expand. These statements conflict. The reviewed documentation alone cannot settle support for a buyer version; inspect that version’s API contract and validate the intended request before relying on an Expand result.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent trust a new tool repository by downloading its own TUF root metadata from that repository?

The pinned TUF client workflow begins with a trusted root copy supplied through an out-of-band process. Repository-supplied metadata cannot independently establish that initial trust. Later root updates must continue from the accepted root. A buyer must identify who approved the starting root and how its bytes and keys reached the updater.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is a new TUF root trusted when only the new root keys signed it?

The pinned TUF root-update procedure requires the next root to satisfy signature thresholds from both the previously trusted root and the new root itself. A self-signed replacement alone does not establish continuity. Failed verification must abort that update cycle and retain the previous starting point for the next attempt.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can repeated signatures from one TUF key satisfy a multi-key approval threshold?

The pinned TUF verification rules count each key only once toward a role’s signature threshold. Repeating a KEYID in the signatures list does not add another verified signer. A threshold review must therefore count distinct authorized key identifiers after signature verification, rather than count signature entries or signature blobs.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a TUF client skip unavailable intermediate root versions and trust the latest signed root?

The pinned root-update workflow fetches the next numbered root and requires its version to be exactly one greater than the trusted version. Intermediate roots establish the chain across key changes. A higher version number or a latest-root URL alone does not establish that chain; missing continuity requires investigation rather than bypassing the required verification.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an expired intermediate TUF root necessarily prevent reaching a valid current root?

The pinned TUF workflow allows trusted starting and intermediate root expiry to remain unchecked while following verified root updates. It checks expiry after reaching the final trusted root, against the fixed update start time. This recovery rule does not allow an expired final root or relax the intervening version and signature checks.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid TUF timestamp signature prove that the update metadata is fresh enough to use?

TUF timestamp verification includes distinct signature, version and expiry checks. The pinned workflow rejects rollback and an expiry no later than the fixed update start time, even if the signature is valid. Signing authenticity therefore does not replace freshness evidence; the buyer also needs a defensible client clock and retained version state.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a repeated TUF timestamp version mean a tool update failed or an attack was proven?

The pinned timestamp workflow distinguishes lower versions from equal versions. A lower version is a rollback failure; an equal version is discarded and the update cycle ends normally without an error, because metadata should not have changed under that version. A no-change stop is not evidence of installation or independently proven malicious activity.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can separately valid TUF signatures establish that timestamp, snapshot and targets metadata belong together?

The pinned client workflow also binds metadata versions and any listed hashes across roles: snapshot must match the trusted timestamp, and targets must match the trusted snapshot. These checks address mixed metadata sets. Valid signatures on independently selected files are not a substitute for verifying the required cross-file relationships.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a delegated TUF signer authorize a tool path allowed by its own metadata but excluded by an ancestor?

The pinned TUF delegation rules require the target path to satisfy trusted paths at every role in the delegation chain. Matching only the leaf role’s path is insufficient. A descendant cannot enlarge authority beyond an ancestor’s delegated path scope merely by signing metadata that names additional targets.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a TUF updater fall back to another signer after a terminating delegation has no matching tool target?

TUF terminating delegations stop consideration of later matching trust statements after that role and its descendants have been processed. The pinned workflow does not treat a missing target as permission to seek a more permissive later signer. This restriction preserves the authority boundary deliberately assigned to the terminating delegation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does delegating a TUF target role remove the parent publisher’s authority over those targets?

The pinned TUF roles description says a delegating role remains trusted after it delegates full or partial target scope. Delegation is therefore not evidence that the parent has surrendered publishing authority. A buyer seeking exclusive control by a subsidiary signer must inspect the entire trust arrangement rather than infer exclusivity from a delegation entry.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must FOCUS BilledCost and EffectiveCost totals match within every billing month?

FOCUS 1.4 assigns BilledCost to invoiced charges in the billing period and EffectiveCost to recognised resource, service or commitment cost in the charge period. Their billing-period totals can differ when a covering purchase and its usage cross periods, accounts or datasets. The specified equality applies across related covering and covered charges over the covering charge period when both sides are present.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a zero FOCUS BilledCost or EffectiveCost row establish that a service was free?

FOCUS 1.4 requires BilledCost to be zero for records generated by an entity that does not invoice the charge, and EffectiveCost to be zero for records generated by an entity that did not originate it. These rules prevent duplicate cost across datasets. Covered usage can also have zero BilledCost. Zero in one dataset therefore does not establish that no charge exists elsewhere.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can I sum every FOCUS ListCost and ContractedCost row to calculate commitment savings?

FOCUS 1.4 warns that commitment-covered costs require excluding either covering Purchase rows or covered Usage rows when aggregating ListCost and ContractedCost, depending on cash or accrual purpose. Including both can count the same coverage twice. These price baselines require their applicable unit and quantity rules; their difference is not independently verified realised savings.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can I multiply FOCUS ConsumedQuantity by a unit price instead of PricingQuantity?

FOCUS 1.4 distinguishes metered ConsumedQuantity in ConsumedUnit from PricingQuantity in PricingUnit. Their granularity or interval may differ. PricingQuantity is used with the applicable SKU unit price to produce ListCost or ContractedCost when the required values are present. Substituting consumption without its documented conversion can produce an invalid charge estimate.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a null FOCUS ConsumedQuantity mean the record has no usage-related cost?

FOCUS 1.4 requires ConsumedQuantity to be null for non-Usage categories, unused commitment Usage charges and records with null SkuPriceId. Correction records can also have null consumption under the stated conditions. Null has a defined applicability meaning; treating it as measured zero can hide unused commitment cost or distort a usage denominator.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can I compare FOCUS CommitmentDiscountQuantity directly with raw GPU hours or token counts?

FOCUS 1.4 expresses CommitmentDiscountQuantity in CommitmentDiscountUnit, depending on the provider commitment category and flexibility rules. It can differ from consumption and pricing quantities. Purchase quantities and Used or Unused usage quantities describe different sides of coverage. Mixing raw workload units or both sides without reconciliation need not measure commitment utilisation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FOCUS CommitmentProgramEligibilityDetails prove a commitment can be bought or applied now?

FOCUS 1.4 lists programs that could potentially cover a charge whether or not a commitment was applied. The field must not reflect temporary purchase restrictions such as account configuration or quotas, and excludes commitment periods and payment options. It identifies an eligible pool, not current availability, approved terms or achieved coverage.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FOCUS CapacityReservationStatus Used prove the reserved GPU was busy?

FOCUS 1.4 uses CapacityReservationStatus to describe whether a charge consumes the identified reservation or represents its unused portion. This is a charge-allocation status. It does not supply GPU occupancy, useful work or successful inference measurements; those require workload and hardware evidence correlated to the same resource and interval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

What must remain consistent when a FOCUS origin charge is split across teams?

FOCUS 1.4 requires summable costs and quantities across allocated charges to reproduce the origin charge, while dimensions and non-summable metrics such as unit prices retain origin values when present. A split redistributes a charge rather than creating cost. Arithmetic conservation supports consistency review but does not establish fair allocation or correct metering.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FOCUS AllocatedMethodId establish how a shared AI bill was divided?

FOCUS 1.4 requires an AllocatedMethodId for generator-calculated splits and documentation identifying that method. AllocatedMethodDetails should be present for these charges and, when present, describes factors and ratios; ratios across allocated charges must total one. The identifier alone does not expose measured factors or demonstrate correct application.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can origin resource tags alone identify the team charged by a FOCUS cost split?

FOCUS 1.4 separates AllocatedTags for allocated charges from resource tags already present in Tags. AllocatedTags must not repeat those resource tags and may be null even for a split charge. The originating resource owner and allocated recipient need not be interchangeable; absence of allocation tags does not prove the origin owner accepted that share.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should I append a corrected FOCUS Replacement snapshot to the previous export?

FOCUS 1.4 Replacement corrections use a complete snapshot superseding earlier artifacts for the same delivery scope. Adding both can double count unchanged records. Because changes are not separate entries, the latest snapshot alone does not preserve correction history; versioned artifacts need separate retention when that history is required.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the latest FOCUS Delta artifact contain the complete corrected bill?

FOCUS 1.4 Delta corrections append additive changes while preserving earlier artifacts. A complete view requires all artifacts for the delivery scope. Net changes adjust totals without necessarily reversing the original record explicitly, providing less inherent change detail than Ledger corrections. A latest-delta-only calculation can omit the original amount and previous adjustments.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

How should I distinguish a FOCUS Ledger reversal from a second charge?

FOCUS 1.4 Ledger corrections append explicit reversals and re-entries as applicable: a reversal changes additive metric signs while other columns match the original, and a corrected record can follow. All artifacts remain relevant to the scope aggregate. Negative and positive rows need their correction context; their presence alone does not establish duplicate billing or a cash refund.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can one FOCUS import use the same append rule for open and closed billing periods?

FOCUS 1.4 permits hybrid Overwrite and Append delivery with documented conditions for each mechanism. An implementation may overwrite open-period snapshots and append closed-period corrections. Artifacts must be interpreted within their delivery scope and mode; treating every file as additive or every file as replacement can respectively duplicate or lose charges.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FOCUS 1.4 export automatically preserve every native billing field?

FOCUS 1.4 requires custom columns for native fields not represented by standard columns, except publicly documented justified exclusions unrelated to invoice reconciliation. Reconciliation-required fields cannot use that exclusion. Included custom values must retain fidelity and summable totals. Providers may require explicit column selection, so a delivered export still needs its configuration and exclusions checked.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FOCUS DatasetInstanceComplete or TimeSectorComplete prove every expected charge is present?

FOCUS 1.4 describes these flags as the generator assessment under its documented definition of completeness. DatasetInstanceComplete applies to non-time-series instances; TimeSectorComplete applies to time sectors. A true flag does not independently reconcile expected workloads, excluded accounts or late charges. The declared scope must be compared with the scope the buyer actually needs.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a recent FOCUS RecencyLastUpdated timestamp mean the underlying cost data is recent?

FOCUS 1.4 distinguishes when the recency metadata object was updated from when dataset-instance or time-sector data was updated. RecencyLastUpdated alone cannot establish charge freshness for the period being assessed. Inspect DatasetInstanceLastUpdated and the relevant TimeSectorLastUpdated alongside completeness and delivery scope.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an InvoiceId in FOCUS prove the supplier has issued the invoice?

FOCUS 1.4 permits InvoiceId and InvoiceDetailId to be generated for provisional invoices before issuance. Their presence identifies an association, not final publication or payment. Check InvoiceIssueStatus and the issuer document before treating an identifier as a final obligation; a provisional identifier can accompany preliminary data.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May a FOCUS invoice silently return from Issued to Open during a correction?

FOCUS 1.4 prohibits Issued-to-Open status transitions unless the customer explicitly requests or approves them. Corrections not affecting invoice reconciliation may occur regardless of status, yet can affect allocation and traceability. Consumers need the transition, approval and correction context rather than assuming issued data never changes.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can FOCUS invoice lines be reconciled by SKU alone across an invoice?

FOCUS 1.4 allows InvoiceDetailGrain to vary between records within one invoice. It must include every property defining line granularity, including custom properties without a standard equivalent. InvoiceDetailId identifies a record within its InvoiceId. A fixed SKU-only join can merge distinct lines or multiply charges when the actual grain differs.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

How does FOCUS distinguish a corrective invoice from a self-contained invoice?

FOCUS 1.4 requires ReferenceInvoiceId to point to the original InvoiceId when the current invoice adjusts another, and to the current InvoiceId otherwise. This supplies adjustment lineage rather than proof of refund or payment. Reconcile the referenced document, issuer and affected charges before closing a correction.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does zero PaymentCurrencyBilledCost on a FOCUS line mean nothing is payable for that line?

FOCUS 1.4 permits payment-currency amounts in a separate aggregate record. A granular line can have non-zero BilledCost and zero PaymentCurrencyBilledCost, while the aggregate has the opposite pattern. The documented PaymentCurrencyInvoiceDetailId relationship links the grains. Reconcile the group and currency basis before interpreting a zero line amount as no obligation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can FOCUS pricing currency, billing currency and payment currency be treated as one monetary unit?

FOCUS 1.4 permits PricingCurrency to be national or virtual, while PaymentCurrency is the national currency in which settlement is made or expected. PricingCurrencyEffectiveCost is the pricing-denominated equivalent of EffectiveCost with the same recognition basis. These denominations and roles require documented conversion; amounts cannot simply be added as one unit.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FOCUS ServiceProviderName identify both the cloud host and the invoice issuer?

FOCUS 1.4 distinguishes service provider, underlying host and invoice issuer. Marketplace services identify the seller; white-label reseller services identify the reseller. HostProviderName can default to ServiceProviderName when the underlying host is not exposed or selected. Reporting names do not independently authenticate a merchant or prove the physical host.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a ContractApplied entry establish that an entire commitment has been fulfilled?

FOCUS 1.4 associates a charge with one or more commitments and reports applied cost or quantity and unit. Commitment IDs are unique within the provider and have one parent contract; applied cost uses BillingCurrency. A charge association supplies a progress input, not a complete balance or proof of fulfilment across every relevant charge and interval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a proposed or superseded FOCUS commitment be treated as currently available coverage?

FOCUS 1.4 separates Proposed, Pending, Active, Exhausted, Expired, Canceled and Superseded states. Proposed has no current financial impact, Pending begins later, and Exhausted has no remaining value despite being in effect. A modification requiring a new ID makes the previous record Superseded. Current coverage needs applicable dates, state and version lineage.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can later usage recover unused coverage from an earlier FOCUS Continuous commitment interval?

FOCUS 1.4 describes Continuous commitments as fixed coverage per fulfilment interval without unused benefits carrying forward. Discontinuous commitments use an aggregate window; Full Period must be Discontinuous. Annual usage alone cannot establish utilisation of an hourly Continuous commitment. The model and interval must match the calculation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a missing FOCUS ContractCommitmentCost mean the commitment has no value?

FOCUS 1.4 requires ContractCommitmentCost for Spend but permits null for Usage. ContractCommitmentQuantity is required for Usage and may be null for Spend. Quantity uses the provider commitment unit, while cost uses BillingCurrency. Missing cost can indicate a quantity-based obligation rather than zero value.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does hiding expired Weaviate objects from queries establish that TTL deletion ran?

The pinned Weaviate TTL documentation separates expiry from scheduled deletion. The OBJECTS_TTL_DELETE_SCHEDULE setting enables the background deletion schedule; without it expired objects are not deleted. Query exclusion can hide expired objects before that deletion. A query with no expired results therefore does not establish that the deletion job ran or that residual copies were removed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can one successful Weaviate filter deletion remove every matching object?

The pinned Weaviate deletion guide limits a multi-object deletion to QUERY_MAXIMUM_RESULTS, whose documented default is 10,000. It instructs callers to repeat deletion until no matching objects remain; deletion order is by UUID. Dry-run counts and verbose per-object outcomes are available. A successful bounded batch alone does not establish exhaustion of the intended tenant and filter scope.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful Weaviate delete prove that the target object existed before deletion?

The pinned guide distinguishes deletion responses by replication topology. A missing ID on an unreplicated single shard with replication factor one returns 404, while replicated configurations can return success for a missing object. Client handling of 404 also differs. The acknowledgement must be interpreted with topology and client semantics; it does not reconstruct prior existence or establish deletion of every replica or backup.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful Weaviate Parquet export include later writes and all tenants?

The pinned export guide describes a preview feature introduced in v1.37, disabled by default and unavailable in Weaviate Cloud. Its snapshot fixes the data and tenant list when export starts. Later writes and newly created tenants are outside that snapshot; HOT and COLD tenants are included while OFFLOADED tenants are skipped with shard status. A completion status needs reconciliation against that declared scope before an exit export is accepted.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does deleting a Weaviate collection automatically remove every alias that points to it?

The pinned collection-alias guide defines an alias as a routing pointer for object operations and queries. Removing it removes the pointer, not its target collection. Conversely, deleting a collection does not automatically remove its aliases. An alias change or disappearance is therefore routing evidence, not proof of collection deletion or a complete migration.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a completed Weaviate batch import conceal failed objects or references?

The pinned import guide permits individual objects to fail while other objects continue. It exposes per-object failures and client-specific error reporting, including failed objects and references after Python batching. Completion of the surrounding batch is not an all-records receipt. Migration acceptance needs submitted identifiers reconciled against per-object results and the intended reference graph.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the Weaviate offload timeout bound completion of tenant data transfer?

The pinned tenant-offloading documentation describes OFFLOAD_TIMEOUT as a limit for starting the offload operation, with a documented default of 120 seconds. Transfer proceeds asynchronously after initiation. That setting is not a maximum transfer duration, nor does successful initiation establish that the tenant data reached the offload destination.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an older Weaviate full backup be deleted while dependent incremental backups are retained?

The pinned backup guide states that incremental backups can reference unchanged files in earlier backups, including through a chain of incremental bases. Restore follows the chain to obtain those files. Every base and intermediate backup on which a retained backup depends must therefore remain available. Keeping only the newest incremental archive is not evidence of an independently restorable copy.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an empty Weaviate backup base ID prove that a backup is full?

The pinned guide says the list-side incremental_base_backup_id field, introduced in v1.37.6, is only populated for a confirmed root user. Other callers receive an empty value even when a backup is incremental and they otherwise have backup permissions. An empty list value is therefore ambiguous without caller identity and independent chain evidence; it cannot classify the backup as self-contained.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restoring a Weaviate collection automatically restore its RBAC users and roles?

The pinned backup guide states that RBAC roles and users are not restored by default. The restore options rolesOptions and usersOptions default to noRestore; selecting all enables restoration, with those options documented from v1.32.0. A data restore must therefore be reconciled separately with the intended access configuration rather than treated as proof that previous authority boundaries were recreated.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Weaviate restore still be cancelled once it reaches FINALIZING?

The pinned backup guide permits cancellation in STARTED, TRANSFERRING and TRANSFERRED, but not FINALIZING, when schema changes are being committed through Raft. CANCELLING and CANCELED are separate states. A cancellation request must therefore be reconciled with the operation phase and terminal result; it cannot be represented as a guaranteed rollback after finalisation begins.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restic forget immediately remove the backed-up file data from its repository?

In restic v0.19.1, forget removes snapshot references. Repository data no longer needed by retained snapshots is reclaimed by prune, which checks remaining references and may repack partly used files. Data still referenced by another snapshot remains needed. Removing a snapshot reference is therefore distinct from repository reclamation and from physical erasure by the underlying storage service.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restic keep-last apply one retention count across every backed-up host and path?

restic v0.19.1 groups snapshots by host name and paths before applying a retention policy independently to each group. group-by can change those keys or disable grouping, while host and tag filters further restrict selection. A keep count without its grouping and filtering context cannot establish which backup sets were retained or removed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is restic keep-within measured back from the time the retention job runs?

The v0.19.1 retention guide measures keep-within against the latest snapshot, rather than simply the current wall clock. Calendar keep options count periods containing snapshots and use natural boundaries; future-dated snapshots are ignored by duration-related options and are not removed by them. An apparently old snapshot set therefore needs its timestamps and policy basis reconciled before declaring a retention breach or deletion completion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an append-only restic repository prevent a compromised writer from influencing later retention?

The v0.19.1 guide warns that an append-only writer can add misleading snapshots whose timestamps displace legitimate snapshots under some count or calendar retention policies when an administrator later runs forget. It recommends separate secured maintenance access and a keep-within policy, while documenting that protection still depends on the retention window and correct time. Append-only access alone does not validate the snapshots chosen for retention.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful default restic check verify every stored backup payload byte?

restic v0.19.1 distinguishes the default repository-structure check from reading actual pack data. check --read-data reads all packs, while data-subset options limit that work. A successful default check therefore supports structural consistency within its checks, not a claim that every stored data payload was read or that an application restore succeeded.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do repeated random restic data-subset checks guarantee that every pack has been inspected?

The v0.19.1 guide allows a fixed n/t subset partition or a random percentage/size subset for pack-data checking. Repeating random subsets does not guarantee complete repository coverage, even across many runs. A partitioned plan can cover the specified partitions, but its receipts and repository scope must be retained rather than inferred from the number of successful random checks.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restic restore --path restrict restoration to only that path inside the snapshot?

The restic v0.19.1 restore guide says --path selects a snapshot and does not restrict which files inside it are restored. A snapshot selected by one path can contain other paths that are also restored. File-scope selection instead uses include/exclude options or snapshot:subfolder syntax, with filter paths interpreted relative to that selected subfolder.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restic restore --overwrite if-changed compare all existing file bytes before deciding they match?

The v0.19.1 guide says if-changed assumes files with matching size and modification time are current, checking full content when those attributes differ. The default always mode verifies existing content and restores mismatching parts. Interrupted in-place restoration can leave partial results. Matching metadata under if-changed therefore does not establish byte equality or completed recovery.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restic restore --delete remove every extra file from the entire target tree?

The v0.19.1 guide defines --delete as removal of target files absent from the snapshot within the selected restore scope. Include/exclude options restrict which files or directories are subject to deletion. Using --target with --delete requires an include or exclude option, and the guide recommends a verbose dry run. Completion cannot establish removal of extras outside that selected scope.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restoring files with restic on Windows always restore their complete security descriptors?

The v0.19.1 restore guide requires SeRestorePrivilege, SeSecurityPrivilege and SeTakeOwnershipPrivilege, or administrator operation, for full Windows security-descriptor restoration. Without all required privileges only the DACL is restored. Symlink restoration has a separate privilege requirement. File-content recovery alone therefore does not establish equivalent security metadata on the destination.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Velero existing-resource-policy update restore the data in an existing persistent volume?

The v1.18.4 restore guide limits existing-resource update to Kubernetes resource data such as its spec. It explicitly says PVC update does not restore or overwrite the PV data. Updates are best effort; a failed patch can produce a warning and fall back to non-destructive handling without failing the restore. Restore labels or a completed workflow therefore do not establish that volume contents were recovered.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Velero default non-destructive restore leave every existing ServiceAccount unchanged?

The v1.18.4 guide documents ServiceAccounts as an exception to default existing-resource skipping. Velero attempts to merge backed-up fields into an existing ServiceAccount, appending Secrets and ImagePullSecrets and adding absent labels and annotations while retaining existing ones. Default non-destructive restore is therefore not a promise that every existing identity configuration is untouched.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Velero restore the status of every Kubernetes object along with its spec?

The v1.18.4 guide says status is removed by default before object restoration because controllers typically reconcile it. Selected resource types or object annotations can request status restoration, which requires a separate update after creation. A restored spec therefore cannot stand in for retained status history, and restored historical status alone does not establish current runtime health.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does reaching a Velero backup TTL prove that its backup files and snapshots were deleted?

The v1.18.4 guide applies expiry through the garbage-collection controller, whose documented default reconciliation interval is one hour. Expiry targets the backup resource, object-storage backup file, PV snapshots and associated restores. Failed deletion can be labelled with reasons including an unavailable or read-only backup storage location. A passed TTL alone does not establish successful removal of those objects.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does deleting a Kubernetes Velero Backup object establish removal of its object-storage archive?

The v1.18.4 guide treats object storage as the source of truth and synchronises properly formatted stored backups back into missing Kubernetes Backup resources. A Completed resource missing its archive is removed from Kubernetes; Failed and PartiallyFailed resources are not removed by that sync rule. Resource presence or absence alone therefore does not establish the corresponding archive disposition.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Velero File System Backup capture all files at a single atomic point in time?

The v1.18.4 File System Backup guide describes beta-quality support that reads the live filesystem rather than taking a single storage snapshot. Files are consequently not captured at the same point in time. Suitability for a stateful application depends on its consistency controls and recovery validation, not only a successful transfer of files.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does enabling Velero File System Backup also produce a native snapshot of the same volume?

The v1.18.4 guide states that File System Backup and native/CSI snapshots are mutually exclusive for the same volume. When FSB runs, the snapshot is skipped; opting out of FSB allows a snapshot attempt if configured. Neither a global feature setting nor an opt-out establishes that both mechanisms completed, so recovery coverage must be mapped per volume to its actual backup result.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can changing the Velero repository credential secret after the first backup preserve access to earlier backups automatically?

The v1.18.4 FSB guide says the backup repository is created on the first backup targeting it and the custom repository password should be set before that operation. Changing the secret password after repository creation prevents Velero from connecting to older backups. Editing the Kubernetes secret is therefore not documented as an automatic re-encryption or password migration of existing archives.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Velero restore a resource when the target cluster lacks the API version used in the backup?

The v1.18.4 guide backs up resources using the source Kubernetes API server preferred version for each group/resource. That same API group/version must exist on the target for restoration; it need not be the target preferred version. A target cluster exposing a different version of the resource does not by itself establish compatibility.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Velero backup completing establish that its pre-backup consistency hook succeeded?

The v1.18.4 hook guide allows Fail or Continue handling for non-zero hook exit codes, with Fail as the default, and treats a hook exceeding its timeout as an error. The documented default timeout is 30 seconds. A backup configured to continue after a hook error needs the hook result reconciled separately before it can support an application-consistency claim.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can CloudEvents id alone identify duplicate business actions across several sources?

CloudEvents 1.0.2 requires the source and id combination to identify a distinct event; a resent duplicate may retain that pair. The specification also permits one occurrence to produce more than one event. Event-level deduplication therefore needs source as well as id, while distinct event pairs alone do not establish distinct business actions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a CloudEvents source URI identify exactly one authenticated emitting process?

CloudEvents 1.0.2 defines source as the context of the occurrence, which may include multiple producers. An external producer may create an event on behalf of a source that is unaware of CloudEvents. The source URI and its producer-defined semantics therefore do not by themselves identify or authenticate the individual process that emitted the event.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does CloudEvents time always represent the actual time the underlying action happened?

CloudEvents 1.0.2 makes time optional. If the occurrence time cannot be determined, a producer may use another time, such as the current time, provided producers sharing that source use a consistent determination policy. A timestamp must therefore be interpreted with that source policy; presence of time alone does not establish the actual action instant or cross-system order.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does CloudEvents specversion 1.0 identify the exact payload schema or specification patch version?

CloudEvents 1.0.2 requires specversion to be 1.0, retaining only major and minor numbers across specification patch changes. The separate optional dataschema URI identifies the payload schema, and incompatible schema changes should use a different URI. The envelope version therefore cannot establish a particular payload contract or the exact specification patch used by an implementation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a CloudEvents envelope with missing data mean the same as an explicit null payload?

CloudEvents 1.0.2 permits an event without data. Its JSON format separately permits an explicit null JSON payload and distinguishes it from absence of the data member. Normalising both into one state can discard a documented distinction. Event-envelope validity therefore does not establish that an action payload was captured or retained.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should a CloudEvents JSON consumer parse a string-valued JSON data field again as a JSON document?

The 1.0.2 JSON format requires JSON-formatted data to be interpreted directly as a JSON value. A string-valued data member remains a JSON string and must not be decoded again as a JSON document. Binary values instead use data_base64, mutually exclusive with data. Missing datacontenttype is interpreted as application/json. Evidence interpretation must preserve those distinctions rather than infer a nested document from its appearance.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an HTTP Content-Type header always describe only the CloudEvents event payload?

The 1.0.2 HTTP binding distinguishes binary, structured and batched modes. In binary mode, the HTTP body carries event data and Content-Type reflects datacontenttype, while other attributes use headers. Structured and batched modes place event metadata and data in the body using the event-format media type. Interpreting the header without the content mode can confuse envelope encoding with payload encoding.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a sender use CloudEvents HTTP batched mode without receiver solicitation and mix specification versions?

The 1.0.2 HTTP binding forbids batched mode unless it is solicited and recommends allowing the receiver to choose the maximum batch size. A batch may be empty, but all its events must have the same specversion; other attributes, including datacontenttype, can differ. A shared HTTP envelope is not specified here as a transactional or all-events-processed guarantee.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a CloudEvents HTTP webhook response of 202 establish that its event was processed?

The 1.0.2 Web Hooks specification assigns 202 Accepted when delivery is accepted but processing has not occurred or its status is unknown. It distinguishes processed responses and their optional details, while leaving error-detail payloads undefined. A 202 receipt therefore records acceptance, not completed business processing; later application evidence is needed to close the outcome.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the CloudEvents webhook OPTIONS handshake authenticate the sender or authorise its business action?

The 1.0.2 Web Hooks specification describes the validation handshake as abuse protection: the destination agrees to receive notifications so a sender cannot be directed at an unsuspecting endpoint. It explicitly does not establish authentication or authorisation context. The separate delivery access-control model must be assessed independently of that subscription consent.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should ce-traceparent be replaced by each intermediary HTTP hop traceparent when forwarding a CloudEvent?

The distributed-tracing extension published with version 1.0.2 retains the starting trace across multi-hop event transmission; individual-hop tracing is carried by protocol-specific headers. For a single hop the contexts must agree. Middleware may add the extension when absent. Extension support is optional and these listed extensions have no official core standing, so implementations and their forwarding behaviour must be confirmed separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a CloudEvents sequence value be sorted as an unbounded global event counter?

The sequence extension published with version 1.0.2 requires interpretation through sequencetype or an out-of-band agreement if that type is absent or unknown. Its defined Integer type uses string-encoded signed 32-bit values, starts at one, advances contiguously and wraps from the maximum to the minimum signed value. This optional, non-core extension therefore does not supply an unbounded global ordering or independently prove complete capture.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does retaining a CloudEvent with dataref preserve its payload for a later audit?

The dataref extension published with version 1.0.2 permits a reference to externally stored data and allows middleware to replace embedded data with that reference. The referenced content may require separate access information and is only recommended to remain available long enough for consumers, not for an extended archive period. This optional, non-core extension is therefore not a durable payload-preservation receipt.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an unchanged CloudEvents source guarantee that partitionkey remains stable through every hop?

The partitioning extension published with version 1.0.2 provides a grouping key for broker partitioning, but explicitly permits that value to change or disappear across hops because of protocol semantics or processing logic. The extension is optional and has no official core standing. A partition key therefore needs hop-specific provenance before it is treated as an end-to-end correlation identifier.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does successful in-toto verification establish that every reported command exactly matched expected_command?

The in-toto 1.0.0 specification describes expected_command as a suggested command and says a mismatch should produce a warning rather than verification failure. It also warns that command text can be forged after key compromise, including through environment changes. A passing artifact verification therefore does not establish exact command execution or a trustworthy runtime environment.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does in-toto default verification check a step return-value and its stdout or stderr?

The in-toto 1.0.0 specification treats byproducts as opaque information that default verification does not verify. It recommends retaining stdout, stderr and return-value for further scrutiny, including by inspections. This differs from an inspection executed during verification, whose non-zero return value halts validation. Signed step byproducts therefore require an explicit review before they support a successful-step conclusion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is in-toto layout verification always a read-only signature check?

The in-toto 1.0.0 specification defines inspections as commands run on the final product during verification. Their run field spawns a process on the verifying system and produces inspection metadata before artifact rules are checked. A verification plan containing inspections therefore needs an execution-authority and environment review; signature verification alone does not make those commands harmless or read-only.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an in-toto artifact rule list reject every artifact that its explicit rules did not match?

The in-toto 1.0.0 rule-processing specification has an implicit ALLOW * at the end of each artifact rule list. It recommends an explicit trailing DISALLOW * to reject artifacts left unconsumed by earlier rules. Successful verification without that closing restriction can therefore accept additional reported materials or products outside the intended explicit matches.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a later in-toto DISALLOW rule reject an artifact already consumed by an earlier ALLOW rule?

The in-toto 1.0.0 specification applies artifact rules sequentially to a queue. An artifact successfully consumed by one rule is removed and cannot be consumed by later rules. DISALLOW tests remaining artifacts. Rule order therefore changes the effective boundary; a broad earlier allowance can remove an artifact before a later restriction examines it.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an in-toto MATCH rule by itself fail verification when artifact hashes differ?

The in-toto 1.0.0 MATCH algorithm consumes source artifacts only when corresponding destination names and hashes match. Missing counterparts or unequal hashes remain unconsumed. The specification identifies DISALLOW and REQUIRE as the rules that can stop rule processing, so a MATCH non-match must be interpreted with the rest of the ordered policy rather than assumed to be an automatic rejection.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an in-toto MODIFY rule prove that a required business or security fix was implemented?

The in-toto 1.0.0 specification defines MODIFY through artifact presence in both materials and products with different hashes. That structural condition records a content change, not the intended meaning or correctness of the change. A passing MODIFY check therefore needs separate acceptance evidence before it supports a claim that a particular defect or business requirement was resolved.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a correctly signed in-toto layout remain trusted after its expiry date?

The in-toto 1.0.0 specification says clients must not trust expired layout metadata and verifies expiry against the system date. A valid signature does not override that expiry check. A reliance record therefore needs the selected layout expiry and verifier clock context; it cannot infer current policy freshness from signature validity alone.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a signed in-toto link prove that a step ran freshly for one particular layout verification?

The in-toto 1.0.0 specification does not bind link metadata directly to a particular layout and explicitly allows multiple layouts to use the same link during verification. A valid reused link can describe an earlier step. Fresh execution for a specific workflow therefore needs additional run identity and timing evidence beyond link acceptance.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a parent in-toto layout directly receive every intermediate artifact from a verified sublayout?

The in-toto 1.0.0 specification represents a verified sublayout to its parent using the materials of the first sublayout step and products of the last. The parent rules apply to that boundary representation while sublayout verification checks the delegated steps. The parent summary therefore is not an inventory of every intermediate artifact or every inspection result within the delegated chain.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a DSSE keyid be used as authenticated evidence of the signer or signature algorithm?

DSSE 1.0.2 defines KEYID as an optional unauthenticated hint. It may narrow the set of keys to try but must not be used for security decisions. Verification instead checks the signature with acceptable trusted keys under cryptographic details agreed out of band. A matching keyid string therefore does not establish a trusted signer or algorithm.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid DSSE signature permit an application to interpret its payload under any JSON schema?

DSSE 1.0.2 signs both the payload bytes and the payload-type string through its pre-authentication encoding. The type is intended to identify encoding and meaning, with application-specific types recommended over generic application/json. Verification must reject unsupported types and parsing failures. A valid signature therefore does not justify substituting another schema or ignoring the authenticated type.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a DSSE verifier reparse the original envelope after verification to obtain the application payload?

DSSE 1.0.2 requires the exact payload bytes verified to be the bytes passed to the application layer and explicitly forbids reparsing the envelope afterwards to retrieve the payload. A signature result over one decoded value cannot justify acting on another value obtained by a later parse. Evidence handoff therefore needs a stable binding between verification output and application input.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a CloudEvents HTTP receiver follow a redirect without changing the authorised destination?

The Web Hooks specification published with CloudEvents 1.0.2 forbids delivery responses from using 3xx redirects and forbids clients from following them. A redirect cannot be treated as a compliant continuation of this delivery contract. A replacement endpoint therefore needs separate configuration and authority review; the original subscription does not establish the new recipient.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

When must a CloudEvents sender stop delivery after a 410 Gone response?

The Web Hooks specification published with CloudEvents 1.0.2 recommends 410 Gone when a delivery target is retired while the HTTP site still exists, and recommends that the sender stop further notifications. This is retirement guidance, not an acknowledgement that earlier events were processed or that stored payloads were deleted. Closure requires separate reconciliation of outstanding deliveries and retained data.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a CloudEvents sender ignore Retry-After on a 429 response without violating its delivery contract?

The Web Hooks specification published with CloudEvents 1.0.2 recommends 429 Too Many Requests when a target exceeds a request-rate limit and requires that response to contain Retry-After. It requires the sender to respect that value and refrain from further requests until the indicated time. Immediate retry or a separately chosen shorter delay does not satisfy that delivery rule; throttling still does not establish a business outcome.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a signed in-toto sublayout inspection result be reused without rerunning its inspection command?

The in-toto 1.0.0 specification permits a sublayout inspection to be verified using presented link metadata signed with the same key that signed the sublayout. If that link is absent, the client must run the inspection while validating the sublayout. Acceptance can therefore rely on a previously signed result; it does not establish a fresh inspection of the current environment.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does in-toto disambiguate links from sublayouts that reuse the same step name?

The in-toto 1.0.0 specification places sublayout link metadata in a directory named from its sublayout link filename without the .link suffix. This separates step names that can be reused by independent layout authors. Flattening those files can lose the documented namespace distinction; a filename alone is not enough to attribute a link to the intended delegated step.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Which Sparkplug timestamp should a buyer use to distinguish sample age from publication delay?

Sparkplug 3.0.0 distinguishes the payload timestamp, representing publication time, from metric timestamps associated with captured values. The specification describes metric timestamps as UTC capture times and requires them in birth and data messages. Comparing the two can support a declared delay assessment, but neither field independently establishes clock accuracy or physical measurement time.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Sparkplug metric alias be interpreted without the associated birth-message mapping?

Sparkplug 3.0.0 permits aliases but requires each alias to be unique across the Edge Node metrics. Birth messages carry the metric name and alias together; subsequent data and command messages using aliases omit the name. A numeric alias therefore needs the applicable birth mapping, including the node context, before a consumer can identify the intended metric.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent infer a Sparkplug metric datatype from the data message alone?

Sparkplug 3.0.0 requires a metric datatype in NBIRTH and DBIRTH and says it should not be included in subsequent data and command messages. Consumers need the birth definition to interpret the metric consistently. The representation of a value in the payload is not a substitute for the declared Sparkplug datatype and its applicable node or device context.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a repeated Sparkplug seq value prove that a message is a duplicate?

Sparkplug 3.0.0 uses an Edge Node message sequence in the range 0 to 255 and wraps after 255. NDEATH is excluded from this sequence. A repeated seq value can therefore be expected after wrap and cannot serve as a globally unique message identifier. Reconstruction needs node, session and ordering context as well as the sequence value.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Sparkplug metric marked is_historical be treated as a current live reading?

Sparkplug 3.0.0 describes is_historical as marking a historical value, including data delivered through store-and-forward or batch collection. The flag separates delayed observations from real-time updates. A consumer must interpret that value with its timestamp and intended use; arrival in the latest message does not make a historical metric current.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Sparkplug metric with is_null mean that its measured value is zero?

Sparkplug 3.0.0 provides is_null to indicate a null metric value, with the value field permitted to be omitted. This is distinct from an actual numeric zero or false Boolean. A consumer must preserve that distinction when evaluating a reading, rather than silently filling an absent value with a successful measurement.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an omitted Sparkplug Quality property independently prove a sensor reading is good?

Sparkplug 3.0.0 defines an optional Quality property and requires it when quality is not GOOD. Under that convention, omission represents the default GOOD condition. This is a declaration convention, not an independent sensor or calibration check. Buyers need the producer implementation and measurement evidence before relying on an omitted property as proof of quality.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a delayed Sparkplug NDEATH be applied to a newer birth session without checking bdSeq?

Sparkplug 3.0.0 uses bdSeq to correlate NBIRTH with the corresponding NDEATH. A delayed Will can arrive after a later birth, so consumers must assess the matching session instead of treating arrival order alone as current state. A rebirth request within the same MQTT session retains bdSeq; a new birth message does not by itself prove a new connection.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the timestamp in a Sparkplug NDEATH identify when the node actually failed?

Sparkplug 3.0.0 explains that a Will payload is prepared during MQTT CONNECT, so its original NDEATH timestamp is not a reliable failure instant. Host processing marks the node offline using host time. A Sparkplug-aware broker may replace the timestamp with its attempted delivery time. These times have different meanings and do not independently establish the physical outage instant.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Will a clean MQTT disconnect automatically publish the Sparkplug node death message?

Sparkplug 3.0.0 requires an intentionally disconnecting Edge Node to publish NDEATH before sending MQTT DISCONNECT. A clean disconnect suppresses the broker Will, so relying only on the Will would omit that notification. If no DISCONNECT is sent and a later Will duplicates the death notification, the host must use the matching bdSeq to avoid duplicate processing.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Sparkplug marking every child device offline mean those physical devices have stopped?

Sparkplug 3.0.0 directs the host to mark the Edge Node and its associated devices offline after the applicable NDEATH and to mark their birth metrics STALE. This describes the host view of unavailable data through that node. It is not physical shutdown evidence for each device, which may continue operating while its reporting path is unavailable.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Sparkplug rebirth after a sequence gap recover every missing historical sample?

Sparkplug 3.0.0 recommends a configurable reorder timeout. Where configured, unresolved missing sequence messages at timeout require a rebirth request. Rebirth stops data publication temporarily and sends the complete birth sequence to restore the consumer state. This is not a promise to replay every missing sample or reconstruct the lost interval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Sparkplug consumer treat each DATA message as a complete snapshot of every metric?

Sparkplug 3.0.0 requires the birth sequence to expose the metrics for the session and recommends that subsequent DATA messages contain only changed values. Unchanged values need not recur until a new session. Reconstructing state therefore needs the applicable birth values and subsequent changes; a single DATA message is not necessarily a full snapshot.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can repeated appearances of one Sparkplug metric in a DATA payload be discarded as duplicates?

Sparkplug 3.0.0 permits multiple changes for the same metric within one DATA message when the samples have distinct timestamps. It also requires non-historical metrics in chronological order. A consumer that deduplicates by metric name alone can discard legitimate intermediate samples; interpretation needs the individual timestamps and the historical flag.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Are retained birth messages from a Sparkplug-aware broker guaranteed to contain current metric values?

Sparkplug 3.0.0 requires a Sparkplug-aware broker to store the latest NBIRTH and DBIRTH and expose them on designated retained $sparkplug topics. These remain the original birth messages: later DATA changes do not make their metric values current. The specification explicitly warns consumers to account for those subsequent updates.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Sparkplug protocol conformance prove that command-topic permissions are correctly secured?

Sparkplug 3.0.0 presents its security chapter as non-normative guidance, discussing MQTT client identity, credentials and topic access control. These considerations do not make protocol conformance an independent permission audit. A buyer must inspect the actual broker and application authorization policies for publishing and subscribing to command topics.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Sparkplug is_transient prove a metric was never retained by a downstream historian?

Sparkplug 3.0.0 describes is_transient as identifying a value that should not be stored by a historian. That expresses intended treatment of the metric; it does not demonstrate what any downstream consumer actually retained. A buyer assessing storage obligations still needs consumer configuration and retention evidence for each relevant copy.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does SensorThings phenomenonTime always come from the sensing device clock?

SensorThings Sensing 1.1 permits a client to omit phenomenonTime when creating an observation. The service must then assign its current server time. A populated phenomenonTime can therefore be a server fallback rather than a device timestamp. A freshness decision needs the submitted observation and timestamp-origin policy, not just the stored field.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a null SensorThings resultTime mean the measurement failed?

SensorThings Sensing 1.1 says that when an observation submission omits resultTime, the service assigns null. That field describes result-generation time, separately from the result value and phenomenonTime. Null therefore does not itself diagnose a failed measurement or supply a generation timestamp; the buyer must seek the missing timing evidence separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a SensorThings Thing location be substituted for the location of what was actually observed?

SensorThings Sensing 1.1 distinguishes a Thing location from an observation FeatureOfInterest. In remote sensing, the observed feature may be somewhere other than the sensing Thing. An observation is associated with its FeatureOfInterest, so geographic attribution needs that relation rather than assuming the device location identifies the target.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can two SensorThings result numbers be compared without their Datastream unit definitions?

SensorThings Sensing 1.1 groups a Datastream by a shared ObservedProperty and Sensor and defines unitOfMeasurement using name, symbol and definition. Unit properties are null for observations without a measurement unit. A number alone does not carry this context; comparison needs the stream definitions and observation types as well as the values.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can deleting a SensorThings Datastream leave all its linked observations intact?

SensorThings Sensing 1.1 deletion rules remove entity relations and specify integrity cascades, including deleting observations linked to a deleted Datastream. Deleting a Sensor or ObservedProperty also deletes linked Datastreams. Buyers should assess these dependencies before removal; API entity deletion does not independently prove erasure of backups or other stored copies.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does SensorThings CreateObservations returning 201 mean that every submitted observation was created?

SensorThings Sensing 1.1 dataArray creation returns 201 with an ordered response array. Each element is the created observation URL or the string error when that individual creation failed. A successful outer status therefore does not establish complete import; buyers need to reconcile each response position with the corresponding submitted observation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a SensorThings MultiDatastream result array be reordered without changing its meaning?

SensorThings Sensing 1.1 requires matching size and order across MultiDatastream unitOfMeasurements, ObservedProperties, observation result elements and multiObservationDataTypes. Each position carries corresponding meaning. Reordering one array without the others can associate a value with the wrong property, datatype or unit even if the payload remains syntactically valid.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a very large SensorThings $top request guarantee that all observations arrive in one response?

SensorThings Sensing 1.1 specifies that when $top exceeds the service pagination limit, the service discards that option and applies its own page limit. The API also defines next-page links. Buyers must inspect pagination and reconcile the intended result set; a large requested limit or stable ordering alone is not proof of a complete, immutable export.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does HTTP 200 for a SensorThings batch establish success of every enclosed request?

SensorThings Sensing 1.1 defines multipart batch responses and includes an example where the outer response is 200 while an enclosed query fails. The outer status must therefore be distinguished from individual operation results. This observation does not establish atomicity for every batch or changeset; the buyer must inspect the applicable operation and transaction rules.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does finding a SensorThings MQTT notification endpoint mean the same endpoint accepts new observations?

SensorThings Sensing 1.1 treats MQTT as an optional extension and advertises supported capabilities through serverSettings. Observation creation and update notifications have separate capability identifiers, and a service supporting both may use different endpoints. A buyer must discover the required capability and endpoint instead of inferring write support from a notification connection.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can the SensorThings MQTT topic determine which Datastream a new observation belongs to?

SensorThings Sensing 1.1 says that when the MQTT topic is a Datastream or FeatureOfInterest navigation link, the new observation is automatically associated with that entity. HTTP creation integrity constraints and specified defaults also apply. Reconciliation must therefore retain the publication topic as well as the payload before attributing the observation to a stream or target.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does SensorThings Sensing conformance establish authenticated access and permission enforcement?

SensorThings Sensing 1.1 states that it does not define specific security capabilities and describes use of existing security mechanisms across the architecture. Its data and operation model therefore does not independently demonstrate authentication or authorization in a deployment. Buyers need the actual service access policy and enforcement evidence for the intended read, create or delete operation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does creating a SensorThings Task prove the actuator completed the requested physical action?

SensorThings Tasking Core 1.0 describes checking submitted taskingParameters against the corresponding TaskingCapability and creating the Task when they are correct. A Task contains the control-action parameters that should run. This validates the declared task request; it does not independently demonstrate actuator execution or a verified physical result.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a SensorThings Tasking Core client create new actuators or control capabilities as part of submitting a Task?

SensorThings Tasking Core 1.0 limits client creation to Tasks. Other entities, including TaskingCapabilities, Actuators and Things, are pre-provisioned to the server. A client therefore cannot infer capability-provisioning authority from its ability to submit a valid Task under this core specification.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent submit arbitrary named fields as SensorThings taskingParameters?

SensorThings Tasking Core 1.0 defines TaskingCapability parameter descriptions and Task values using the SWE Common JSON representation. The capability defines the optional and mandatory parameters, and the server checks submitted parameters against it. Buyers should retain that definition when preparing a task; a plausible field name alone does not establish an accepted control input.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

What evidence binds a SensorThings Task to the intended TaskingCapability rather than a similarly named control?

SensorThings Tasking Core 1.0 requires each Task to link to one TaskingCapability. Creation can identify it by @iot.id in the request body or through the TaskingCapabilities identifier in the POST URL. Target reconciliation needs the effective identifier and its Actuator and Thing relations; a descriptive capability name is not a substitute for this binding.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Peppol Message Level Response accepting a document also accept its commercial terms?

The published Message Level Response profile separates transport receipt, document conformance and the business decision. An accepted technical response therefore does not establish that a supplier accepted a purchase, that an invoice was approved or that a payment was authorised. Retain the appropriate business response as a separate item of evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an AB Message Level Response establish that Peppol conformance validation ran?

In Message Level Response 3.0, AB denotes acknowledgement without validation, while AP denotes acceptance after conformance checks. RE is rejection and requires an explanatory description. An AB response should not be counted as evidence that syntax and semantic checks passed; the validation outcome must be established separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Which identifier binds a Peppol Message Level Response to the business message it assessed?

The published MLR profile assesses one business document and binds its response through the original envelope instance identifier. A buyer reconciling technical responses needs the envelope-to-document association. A displayed invoice number alone does not establish which transmitted instance received the response.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Peppol Order Response AB mean that the seller accepted the order?

Ordering 3.3 uses AB for an order that has been received but not yet processed. This response contains no order lines and anticipates a later decision. A procurement agent should retain it as receipt evidence while awaiting the seller decision required for the next commercial step.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Peppol amended Order Response omit unchanged or already delivered lines?

For an amended Ordering 3.3 response, the seller supplies all lines, including unchanged and already delivered lines. Individual line decisions may differ. A changes-only extract is insufficient to reconstruct the complete response; reconcile the supplied lines against the original order rather than interpreting omissions as agreement.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Peppol order-line code 42 establish independently confirmed receipt by the buyer?

Ordering 3.3 defines line response code 42 for items reported as already delivered. That code is part of the seller response. It is not an independent goods-receipt observation, so a buyer deciding whether to release an invoice should reconcile it with receiving evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

How should a Peppol order response be matched to the original order and individual lines?

Ordering 3.3 requires an order reference at header level. If response lines are supplied, each needs the related original order-line reference. Reconciliation should use those identifiers and the correct document context; matching by item description or response position alone can attach a decision to the wrong line.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Peppol MaximumBackorderQuantity promise delivery of the entire unfulfilled order line?

Ordering 3.3 uses MaximumBackorderQuantity for the maximum quantity that may be delivered later when its delivery date is unknown. A zero value indicates that the remaining quantity will not be delivered. Neither a positive maximum nor a missing delivery date establishes that the whole outstanding order will arrive.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Peppol Advanced Ordering seller impose arbitrary changes to an accepted order?

Advanced Ordering 3.0 permits a seller to accept with changes within a scope previously agreed by the parties. Later order changes have their own acceptance or rejection process. Receiving a syntactically valid amendment does not establish that every proposed change falls within the buyer authorised scope.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does sending a Peppol Order Cancellation establish that the seller accepted cancellation?

Advanced Ordering 3.0 distinguishes a buyer cancellation request from the seller decision. Cancellation may depend on agreed deadlines and whether delivery has already been prepared; the seller can accept or reject it. Keep the resulting decision before treating the order as cancelled or releasing its reserved budget.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

How are successive Peppol Order Change messages distinguished during reconciliation?

Advanced Ordering 3.0 requires a buyer-assigned OrderChangeSequenceNumber to distinguish successive changes. A response referring to an order change uses a header-level change document reference. Preserve both sequence and document identity: their presence identifies the proposal but does not prove that the proposed terms were accepted.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Peppol Despatch Advice prove that the buyer received the goods?

Despatch Advice 3.1 describes goods being sent and information supporting their receipt. It is a supplier notice, not an independent observation that the buyer received or accepted those goods. Match it to receiving records before treating physical delivery as complete.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can one Peppol Despatch Advice be assumed to belong to a single purchase order?

A Despatch Advice 3.1 message may cover more than one order, while an order may have several despatch notices. For a multi-order notice, references belong on individual lines rather than a single header order reference. Reconcile these relationships before counting received quantities against a purchase order.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the Peppol despatch order-line reference NA identify a matched purchase-order line?

Despatch Advice 3.1 allows NA as a placeholder where the required order-line reference is unavailable. The presence of that field therefore does not always identify a real purchase-order line. Obtain a defensible mapping before allocating received quantities, closing a line or approving a matching invoice.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Peppol OutstandingQuantity represent every ordered item that has not arrived?

Despatch Advice 3.1 uses OutstandingQuantity for the quantity expected to follow later. It does not necessarily represent every unit that has not been delivered: some remaining ordered quantity may never follow. Reconcile ordered, despatched and expected-later quantities separately before calculating an unresolved shortfall.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does receiving a Peppol Punch Out shopping cart place an order with the supplier?

Punch Out 3.1 returns a shopping cart or item list to the buyer procurement system. The buyer prepares and sends the order separately. A returned cart therefore supports selection and pricing review but does not establish that an order was placed, approved or accepted by the supplier.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a procurement agent rely on a Peppol Punch Out cart after its seller-defined validity expires?

Punch Out 3.1 permits validity periods for the cart and its lines. A date-only expiry ends at the close of that day in the seller time zone, and applicable contract terms take precedence over cart information. Recheck validity before relying on the selected price or availability.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent select only some items from a Peppol Punch Out cart marked complete?

Punch Out 3.1 marks a complete cart through ActionCode set to true. Such a cart is intended to be ordered together without changing its quantities; when that indication is absent, the documented default is false and partial selection is allowed. Preserve the flag before letting an agent remove items or change quantities.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is an omitted Peppol Catalogue action equivalent to a partial catalogue update?

Catalogue With Response 3.1 defaults an omitted header action to Replace. Update has different, partial-update semantics, and action codes are case-sensitive. Treating an unlabelled incoming catalogue as a patch can therefore leave obsolete items in the buyer system. Resolve the header action before applying the message.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should a Peppol catalogue item update be matched by CatalogueLine ID?

Catalogue With Response 3.1 identifies an item for update through its seller or standard item identifier, rather than the CatalogueLine ID. An updated line is replaced as a whole, and line update or deletion is used under a header Update. Retain the correct item key to avoid modifying an unrelated entry.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does accepting a Peppol Catalogue place an order for the listed items?

Catalogue With Response 3.1 supports accepting catalogue information into the buyer system. Ordering is a separate process outside that catalogue exchange. Catalogue acceptance therefore does not establish a purchase commitment for the listed items or permission for an agent to place an order.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Peppol Invoice Response PD prove the supplier received settled funds?

Invoice Response 3.2 uses PD when the buyer has initiated payment; it is not independent bank-settlement evidence. The documented partial-payment case combines PD with the PPD clarification and remains non-final. Read both status and clarification before counting an invoice as fully paid or the supplier as having received funds.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Peppol invoice rejection cancel the invoice content or underlying payment obligation?

Invoice Response 3.2 communicates processing status without changing the invoice content or the parties commercial responsibilities. A rejection response therefore is not, by itself, evidence that the underlying invoice was cancelled or the transaction reversed. Preserve any separate correction, cancellation or dispute resolution.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must every Peppol Invoice Response status appear before an invoice is reported paid?

Invoice Response 3.2 does not require every intermediate status to be reported. A response carries the current status and the first response may begin later in the documented sequence. Missing intermediate messages alone do not prove that approval steps were skipped; assess the reporting agreement and available workflow evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Peppol buyer report an approved invoice as under query by sending a later Invoice Response?

Invoice Response 3.2 constrains transitions: following AP, the next protocol status is PD; final RE or fully paid PD ends the response sequence. A later changed decision must be communicated by other means. The documented PD with partial-payment clarification is an exception to final payment, so inspect that clarification before closing reconciliation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Peppol invoice always direct payment to its seller?

BIS Billing distinguishes the seller from an optional payee. When a payee is omitted, the seller is the assumed recipient; a separate payee can represent a factoring arrangement. A declared name and payment account do not independently verify account ownership or authorise a changed destination.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Peppol invoice BuyerReference establish an approved purchase order?

BIS Billing requires a buyer reference or purchase-order reference. A BuyerReference can route an invoice to a person or department; it is not itself evidence of an approved purchase order. Check the referenced commercial authority separately before an agent treats the invoice as authorised spend.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is a preceding invoice number sufficient to uniquely bind a Peppol credit note correction?

BIS Billing allows correction references to preceding invoices. If an invoice number does not uniquely identify the earlier document, its issue date is also needed. Bind the correction to the intended invoice instance before reconciling balances; the correction reference does not establish that a cash refund occurred.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Peppol invoice validation verify the exchange rate used for VAT accounting currency?

BIS Billing permits a VAT accounting currency different from the invoice currency. The exchange rate is not supplied in the invoice instance, and that conversion is not validated there. Obtain the applicable rate and calculation evidence separately; successful invoice validation cannot establish the correctness of the conversion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should a Peppol card-payment invoice contain the full payment card number?

BIS Billing limits the card account identifier to the last four to six digits and includes a card-network identifier. These fields support identifying the declared payment method; they are not full card credentials or independent evidence that the card payment was authorised or completed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Peppol PriceAmount be multiplied by invoice quantity without considering BaseQuantity?

BIS Billing calculates the priced quantity using the item net price divided by its price base quantity before multiplying by invoiced quantity. Line charges, allowances and specified rounding also matter. Multiplying PriceAmount directly by quantity can therefore overstate a line when the price covers more than one unit.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does basic Peppol Billing Profile 01 guarantee a structured invoice response?

Billing 3.0.21 distinguishes basic Profile 01 from Billing with Response Profile 02. The release notes require separate SMP registration for the response profile. An invoice under the basic profile does not itself establish structured response support; check the recipient capability and the actual process agreement.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does successful UBL schema validation establish all Peppol invoice business rules passed?

BIS Billing separates UBL schema validation from semantic business rules and the applicable Peppol restrictions, including conditionally applicable country rules. Passing XML structure checks alone does not establish that those other layers passed, nor that the invoice facts are correct. Retain the validation layer, version and results.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do multiple FHIR AuditEvent records necessarily mean that the same action was executed repeatedly?

FHIR R5 expects participating actors to record an auditable event, so one activity can produce several AuditEvent records. These observations can support cross-system comparison, including finding missing actors or conflicting attributes. Counting the records alone does not establish how many times the underlying action executed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful FHIR AuditEvent outcome establish that an entire transfer completed?

The R5 AuditEvent outcome definition allows a success indication to cover a partial or interrupted transfer for accountability purposes. A successful audit status therefore does not establish that every expected item arrived. Reconcile the operation-specific scope and receiving evidence before marking the transfer complete.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should an auditor infer the FHIR event initiator from the first listed agent?

R5 AuditEvent.agent.requestor identifies the initiator, with false as the meaning when it is absent. The specification says not to select an initiator when that identity is unclear. Agent order or mere participation does not resolve an unknown initiator; preserve that uncertainty in the reconstruction.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FHIR AuditEvent.recorded establish when the underlying action occurred?

R5 AuditEvent distinguishes the optional occurred time or period from the mandatory recorded instant. A late-recorded event can therefore have a different activity time. Compare the two with the systems clock evidence; a recording timestamp alone proves neither the activity time nor clock accuracy.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an auditor interpret a FHIR AuditEvent query blob without its originating query format?

R5 AuditEvent.entity.query stores query input in a base64 container whose meaning depends on the originating event and query format. An audit consumer must understand that format before interpreting it. The encoding does not make the query self-describing or establish that its contents are safe for unrestricted disclosure.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FHIR Provenance target always identify one exact resource version?

R5 Provenance targets are usually version-specific, but the definition permits cases where a version is not assigned or the provenance belongs to a maintained document. A target reference can also cover several resources. Resolve the intended resource version before treating the assertion as evidence about one exact artifact.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FHIR Provenance.onBehalfOf independently verify the recorded delegation?

R5 Provenance.agent.onBehalfOf records the agent that delegated authority to the acting agent. Defined identity constraints prohibit specified self-delegation patterns, but structural validity is not independent verification of the delegation or its permitted scope. Retain the underlying authority evidence for the administrative action.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Are FHIR Task.basedOn and Task.focus interchangeable references to the work being fulfilled?

R5 Task.basedOn references higher-level authorization that triggered a task, while Task.focus identifies the request being fulfilled or resource being acted on. The specification distinguishes these references. Replacing one with the other can lose either the authority context or the actual target of the proposed work.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FHIR Task owner identify who actually performed the task?

R5 Task separates the owner responsible for managing execution, the requested performer and the entity reported as having performed the task. A task may be created before its owner is identified. An assignment or requested role is therefore not evidence that the named party actually performed the work.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can one FHIR Task focus identify several resources whose completion needs separate tracking?

R5 Task.focus identifies at most one resource. Its definition directs implementations to use subtasks when multiple resources need manipulation so their statuses can be tracked independently. A parent task status should not be substituted for the missing completion evidence of each resource-specific operation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a FHIR Task businessStatus replace its required workflow status?

R5 Task.status is a required coded lifecycle state. Task.businessStatus is optional and carries workflow-specific detail. A local business label therefore does not replace the standard state or establish a meaning shared by every receiving system; retain both the lifecycle state and the local code definition.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a FHIR fulfilment Task restriction period extend beyond its referenced request authorization?

R5 Task.restriction.period bounds the fulfilment sought and must fall within the overall period authorised by the referenced request. A task-local interval does not enlarge that authorization. Compare the requested interval with the applicable request before treating work outside its period as permitted.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FHIR preauthorization response mean that payment has been made?

R5 ClaimResponse distinguishes preauthorization from an actual claim. A preauthorization response does not itself make a payment, although funds may be reserved for a claim submitted later. Preserve the later claim and financial outcome rather than recording reserved or authorised benefits as money received.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FHIR predetermination guarantee the later claim will receive the same benefit?

R5 predetermination describes a hypothetical adjudication. It makes no payment and does not assure that a later claim will receive the same result; available funds may change. A buyer should retain the date and conditions of the estimate and obtain the later actual adjudication.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FHIR ClaimResponse outcome partial mean that processing errors were found?

R5 ClaimResponse.outcome distinguishes queued, error, partial and complete processing. Partial means that some adjudication has occurred without detected errors, while complete means all adjudication processing completed without errors. Do not import a generic partial-failure meaning; inspect what processing remains and the reported adjudication.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can every FHIR adjudication line be matched by position to the originally submitted claim?

R5 ClaimResponse permits payors to add lines or repackage submitted products and services. The addItem structure can link those lines to submitted item, detail or sub-detail identities. Matching response lines by position alone can lose that relationship; retain the explicit links before reconciling an adjudicated amount.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a FHIR claim payment adjustment be assumed to arise from that claim adjudication?

R5 ClaimResponse.payment.adjustment describes adjustments not arising from the current claim adjudication, such as recovery of an earlier overpayment. A difference between benefit and payment can therefore have another origin. Reconcile the adjustment and its reason separately from the current claim amount.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does listing several FHIR claim coverages request adjudication from all those policies?

R5 Claim.insurance identifies one focal coverage for adjudication of that claim. Other listed coverages have a coordination sequence, and claims against them are separate. Listing several policies does not request or establish successful adjudication against all of them, nor verify that any policy remains effective.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Are the effective period of a FHIR consent provision and the time period of covered data the same?

R5 Consent separates the provision effective period from dataPeriod, which bounds the relevant data controlled by that provision. Permission duration and the age or dates of the covered records are therefore different constraints. Retain both before interpreting the declared permission for an administrative data transfer.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a FHIR consent permit decision be read without its exception provisions?

R5 Consent.decision sets a default permit or deny action, while provision entries describe exceptions that can add or remove permissions. Reading the default without its provisions can misstate the declared scope. This interpretation still does not establish that a live system enforced the consent.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FHIR Consent sourceReference contain the original consent document?

R5 Consent supports source material through attachments or references to other records, including repository documents. A sourceReference is a pointer rather than a guarantee that the original document is present in the returned resource or remains retrievable. Establish the source identity and availability separately before relying on it.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a current FHIR DocumentReference mean its underlying document is final?

R5 DocumentReference.status describes the reference object; docStatus describes the underlying document lifecycle. A current reference can point to a document with another lifecycle state. Read both rather than treating current metadata as evidence that the content is final, approved or unchanged.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a FHIR document that appends another document be reviewed as a complete standalone record?

R5 DocumentReference identifies relationships between documents. Where a document appends another, the definition says it cannot be fully understood without the referenced target. A standalone export of the appended material may therefore omit required context even when its own file is complete.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do DocumentReference.meta.security labels necessarily describe the referenced document sensitivity?

R5 distinguishes DocumentReference.meta.security, describing the reference metadata, from DocumentReference.securityLabel, describing the referenced document. Their sensitivity can differ. A receiver should not infer that access appropriate for the metadata is also appropriate for the document content.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does provenance of a FHIR DocumentReference establish who created the underlying document?

R5 describes two provenance histories: the underlying document and the DocumentReference that points to it. Another actor may create the reference later, and its metadata describes that reference history. Preserve the document origin separately rather than attributing authorship of the content to whoever created its reference.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does HTTP 200 for a FHIR batch mean every requested change succeeded?

FHIR R5 batches process entries independently. HTTP 200 means the batch was processed correctly, even when individual operations failed; their response entries carry the relevant statuses. A transaction has different all-or-nothing rules. Inspect the bundle type and every entry before marking work complete or deciding what to retry.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a FHIR batch create one resource and rely on another entry referencing that new resource?

FHIR R5 requires batch changes to be independent. References from one batch entry to a resource being created by another are non-conformant. Linked changes need the appropriate transaction and server-support contract; merely putting them in one HTTP request does not establish atomic execution.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FHIR Bundle fullUrl uniquely identify the version of every included resource?

R5 Bundle.fullUrl is version-independent and must not contain a history-version reference. Subject to the documented bundle rules, entries can share a fullUrl when their resource versions differ; history bundles have their own exception. Retain the resource version and bundle context before treating the URL as an exact artifact identity.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a FHIR Bundle entry response outcome always represent an operation failure?

R5 Bundle.entry.response.outcome carries hints or warnings for an entry. It is not the error location for every failed operation: batch failures are represented in the entry response, while a failed transaction returns a single OperationOutcome instead of a response bundle. Interpret the status and response structure together.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FHIR eventsSinceSubscriptionStart count only successfully delivered notifications?

R5 SubscriptionStatus.eventsSinceSubscriptionStart counts generated events whether or not they were successfully communicated. Handshake and heartbeat notifications do not increment it. The counter therefore cannot be used directly as a count of delivered notifications or completed consumer processing.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is a FHIR subscription event number always a global monotonically increasing sequence?

R5 subscription event numbering depends on channel guarantees. For channels without guaranteed delivery, it is unique and increasing within the subscription; guaranteed-delivery channels may use a relative index within the notification. Interpret gaps or repeats with the channel and subscription context, not as globally unique event numbers.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does every FHIR subscription notification contain the complete resource content?

R5 Subscription.content can request empty, identifier-only or full-resource payloads. A notification therefore does not always carry the resource content needed for a saved evidence snapshot. Check the configured mode and actual payload; any follow-up retrieval has its own access and version context.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does FHIR Subscription.maxCount limit the total number of entries in a notification bundle?

R5 Subscription.maxCount limits the number of events grouped in a notification. It is not a strict limit on the total number of bundle entries, because dependent resources can also be included. Count events using their event structure rather than truncating or rejecting a bundle solely by its entry count.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an OAuth RAR client treat its requested payment amount and recipient as the granted authority?

RFC 9396 requires the authorization details granted to the access token to be returned. They can differ from the request: consent can reduce permissions, a type can permit enrichment, and the server can omit values. Interpret the returned grant using that type before relying on the requested transaction terms. This does not establish payment execution.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does one OAuth RAR object pair each action with just one listed resource location?

RFC 9396 applies the common actions, locations and datatypes of one authorization-details object as a cross-product. Arrays do not implicitly pair their positions. Separate authorization-details objects can express distinct combinations. A client must inspect the type-specific semantics and the complete combinations before treating a request as narrowly scoped.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a JSON subset comparison establish that revised OAuth RAR details reduce authority?

RFC 9396 permits authorization_details on a token request to reduce the permissions of the issued token. The server must use type-specific semantics to decide whether the requested permissions are a subset; structural JSON comparison alone is insufficient. Issuing the reduced token does not change the underlying authorization grant.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent ignore OAuth scope when authorization_details is present in the same request?

RFC 9396 allows scope and authorization_details in the same request. Their permissions are combined according to the applicable API semantics, and the authorization server must present the combined authorization requirements to the user. Neither field should be assumed to cancel or supersede the other without the relevant definition.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an OAuth resource parameter automatically narrow authorization_details to that server?

RFC 9396 states that the resource parameter does not change how an authorization server processes authorization_details. A resource value is therefore not a filter that silently removes other detailed permissions. The RAR type, its locations and the actual granted details need separate review before relying on a restricted target.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May an OAuth RAR server silently ignore unknown fields in a known authorization-details type?

RFC 9396 requires rejection with invalid_authorization_details for unknown types, invalid fields or values, and missing required fields. A type definition can expressly permit extension fields, so not every unfamiliar field is automatically invalid. Validation must use the supported type definition rather than silently accepting malformed authority terms.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does sending payment authorization_details through a browser protect them from replacement?

RFC 9396 warns that authorization details sent through the front channel can be tampered with or swapped. It recommends integrity protection such as signed request objects or pushed authorization requests. Protecting those request terms does not establish that the server granted them, that the client may execute them, or that a payment settled.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May an OAuth RAR verifier normalize differently spelled identifiers before comparing authority?

RFC 9396 requires strings in authorization_details to be compared as defined by RFC 8259, without additional transformation or normalization. This is a rule for string values, not a requirement that serialized JSON documents be byte-identical. Applying an extra case or Unicode transformation can change the permission comparison.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must an access token audience equal the exact OAuth resource parameter string?

RFC 8707 permits resource to identify a protected resource with an absolute URI, including an abstract identifier rather than a network locator. The authorization server can map that value to a more general URI or abstract audience. Endpoint location, resource identifier and issued audience therefore need an established mapping; none authorizes an arbitrary destination.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does omitting OAuth resource mean a token is valid at every resource server?

RFC 8707 allows an authorization server receiving no resource parameter to process the request without a specific resource, use a default resource, or reject it for lacking a resource. Omission does not establish unrestricted access or one universal default. Inspect the applicable policy and the resulting token restrictions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a multi-resource OAuth grant produce a token limited to one selected resource?

RFC 8707 allows a token request to select a subset of the resources authorized by the grant. The resulting access token can be restricted to that subset while a refresh token remains associated with the full authorized set. Resource selection must remain within the grant and authorization-server policy; a narrow access token does not prove the underlying grant was reduced.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is a multi-audience OAuth bearer token isolated from replay between its accepted recipients?

RFC 8707 explains that a bearer token usable at multiple resources can be replayed by one recipient at another. It recommends issuing access tokens for one resource at a time where possible, with authorization-server discretion over multi-resource requests. This is an issuance-policy decision; it does not introduce a new rule that every token is safe merely because an audience is present.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Google Cloud invoice totals be reconciled by filtering only the usage calendar month?

Google Cloud detailed billing export distinguishes invoice.month from the timestamps of usage. Late-reported usage and adjustments can appear on a later invoice. Reconcile invoice totals by the invoice field and retain the usage interval separately; filtering only by usage month can omit or misplace invoiced charges.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does each Google Cloud adjustment_info.id identify exactly one billing line?

The detailed billing export uses adjustment_info.id to associate lines with the same adjustment issue. It is not a unique row identifier. Adjustment modes include partial correction and complete negation followed by remonetization. Keep the relevant rows, type and mode together before calculating the net correction; deduplicating solely on the issue ID can discard necessary entries.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does summing Google Cloud exported cost alone include all credits in the invoice net amount?

Google Cloud detailed billing examples reconcile cost with signed credit amounts and include charges whose resource identity is unavailable. A resource-only filter can drop valid costs, and credits must be aggregated at the intended row grain without multiplying costs through repeated-field expansion. The resulting arithmetic is not proof that the export is complete or that an invoice has been paid.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an existing Google Cloud billing export table prove it is still receiving new records?

Google documents that removing the export service account's permissions prevents billing-export tables from updating. The setup guidance distinguishes the standard and detailed export writer from the CUD metadata case. A prior successful table is not evidence of continuing updates. Restore appropriate permissions and inspect actual freshness; this record makes no automatic backfill guarantee.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is the BigQuery Cloud Billing export schema guaranteed not to change after integration?

Google warns that billing-export schemas can change and that queries referencing them directly can fail. It recommends normalization through views, which may themselves require maintenance as fields change. A once-valid query or view does not establish that current exports are still consumed completely or correctly.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the Google-provided FOCUS export retain every historical billing row indefinitely?

Google's setup guidance assigns a two-year time-to-live to Google-provided FOCUS export tables. This constraint is specific to that export arrangement and is not a statement that all Cloud Billing tables expire after two years. Preserve the relevant data under the buyer's approved retention process if a longer reconstruction window is required.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an ordinary Cloud Storage object listing include retained soft-deleted copies?

Google Cloud Storage excludes soft-deleted objects and buckets from ordinary listings unless soft-deleted resources are specifically requested. To list soft-deleted objects inside a deleted bucket, the bucket must first be restored. An empty default listing is therefore not evidence that no recoverable objects remain.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restoring a Cloud Storage soft-deleted object consume its retained original version?

Restoring a soft-deleted Cloud Storage object creates a new live copy while retaining the original soft-deleted object until its retention period ends. If restoration replaces an existing live object, that replaced object can itself become soft deleted. A successful restore therefore does not establish that only one copy or generation remains.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Are object name and generation always sufficient to restore a soft-deleted hierarchical Cloud Storage object?

With hierarchical namespace, folder operations can produce soft-deleted objects sharing the same name and generation. Google documents restoreToken as the additional identifier used to select the intended object for restoration. Name and generation alone can therefore be ambiguous in this case; a restore token is an identity discriminator, not an access grant.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does MODBUS exception 05 ACKNOWLEDGE establish that the requested programming command is complete?

MODBUS Application Protocol 1.1b3 defines exception 05 as acceptance of a specialized long-duration programming request, with a completion poll available. Exception 06 reports that the server is busy processing a long-duration program. Neither response proves completed physical work, and a busy response does not identify the current program or authorize a generic retry.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does MODBUS Illegal Data Value establish whether a submitted register value is acceptable to the application?

MODBUS exception 03 reports a value in the query data field that is not allowed, such as an incorrectly structured request. The specification explicitly distinguishes this from an application judging whether a value submitted for storage is meaningful or acceptable. Protocol acceptance is not validation of a process range, calibration or engineering limit.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does one MODBUS Read Device Identification response necessarily contain the complete identity object set?

MODBUS Read Device Identification uses More Follows and Next Object Id to continue stream access across multiple transactions when the response does not fit one message. Access modes 01 through 03 have different scope from individual-object mode 04. One successful response is not automatically a complete identity inventory, nor authenticated proof of a physical device.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

In MODBUS function 23, is the returned register data captured before the write operation?

MODBUS function 23 decimal, 0x17, combines a write and a read of holding registers, with the write performed before the read. Returned data must be interpreted in that order, especially when the ranges overlap. This ordering does not establish physical actuator completion, safe repetition after a lost response, or a broader database transaction guarantee.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does valid HTTP signature verification establish that every decision-relevant field was protected?

RFC 9421 requires applications to enforce their additional signature requirements, including required components. Unsigned portions of a message can be changed without invalidating the signature. A cryptographic pass is therefore insufficient when the application relies on an unsigned field or a component missing from its verification policy.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid HTTP message signature prove that this request has not already been used?

RFC 9421 explains that a signature can remain valid when attached to another sufficiently similar message. Component coverage, a per-message nonce checked for repetition, and creation or expiry limits can help detect replay. The application must establish those controls; signature validity alone is not evidence of one execution or an idempotent business operation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a response signature using req be validated after the original request components have been discarded?

RFC 9421 permits a response signature to cover components from the triggering request using the req parameter. Those values are not repeated in the response, so the requester must retain the original components long enough to validate it. Proxy changes can prevent a match. A response signature alone does not reconstruct discarded request context.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an HTTP signature label establish the signer's approval role?

RFC 9421 signature labels connect entries in Signature and Signature-Input, but are chosen when attaching the signature and are not covered by the signing process. An intermediary may relabel them. A name such as approved therefore does not establish an approval role; application-specific meaning must use suitable covered parameters and the expected signer policy.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a verifier accept an HTTP message because any one attached signature is valid?

RFC 9421 requires a verifier to account for the expected signers, rather than accepting any cryptographically valid signature attached to a message. Applications must also decide how invalid additional signatures affect acceptance: rejecting a message for any invalid signature can permit denial of service by injection. Key, algorithm and acceptance policy must be assessed together.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does verifying a signature over Content-Digest alone establish the integrity of the received body?

RFC 9421 does not directly sign message content. A digest field can bind it indirectly, but the verifier must both verify the signature and recompute the digest against the received content. Otherwise substituted content can leave the signed digest field unchanged. Content-encoding changes can also change the digest and invalidate the existing signature.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does successful signature verification behind a reverse proxy establish that the request targeted the correct service?

RFC 9421 warns that derived signature components must come from trusted context. A reverse-proxy deployment can use a configured external target URI, but a mistaken mapping may accept a request intended for another component. Signer and verifier must agree on the relevant message and authority; an arbitrary forwarded value is not trustworthy merely because it helps validation pass.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Repr-Digest on an HTTP range or HEAD response prove that all representation bytes were delivered?

RFC 9530 defines Content-Digest over actual message content and Repr-Digest over the entire selected representation. HTTP methods and ranges can make those scopes differ, including partial responses and HEAD. A representation digest therefore does not establish that the complete representation was delivered in this message; inventory the bytes and semantics actually received.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the representation digest on a state-changing request prove the final state of its target resource?

RFC 9530 ties Repr-Digest to representation data and metadata, not automatically to the target resource's final state. In a PATCH request it covers the patch document. A response can describe request status or a referenced resource; Content-Location can affect that interpretation, while Location alone does not. Establish the represented object before treating a digest as post-change evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does requesting an HTTP digest guarantee that the peer supplied and validated the preferred integrity evidence?

RFC 9530 treats Want-Content-Digest and Want-Repr-Digest as hints. A peer may use another algorithm or omit the digest without a protocol error. Applications can impose stronger requirements, and recipients may otherwise ignore supplied digests. Requested preferences do not establish delivery or validation of the integrity evidence required by a buyer.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid DPoP proof directly establish the authenticated client's identity?

RFC 9449 states that, when used with client authentication, DPoP is coincident with that authentication in the same TLS tunnel rather than directly cryptographically bound to it. The URI can partly limit copying risks, but additional authentication binding is outside this specification. A valid proof of key possession is not by itself a complete authenticated-client identity claim.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does DPoP verification prove that the request body, query terms and headers were unchanged?

RFC 9449 checks the proof's HTTP method and URI, excluding query and fragment components from URI comparison. Core DPoP does not protect the request body or general headers. A proof can therefore validate without authenticating business fields carried there. Identify the separate integrity protection before relying on an amount, recipient or payload as unchanged.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do public and confidential OAuth clients bind refresh tokens to DPoP keys in the same way?

RFC 9449 requires a refresh token issued to a public client using DPoP to be bound to that proof key, checked on later refreshes. Confidential-client refresh tokens instead use the existing client binding and authentication requirement. A reviewer must establish the client type and actual binding; the access token's DPoP status alone does not describe every refresh credential.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a client reuse one DPoP nonce across authorization and resource servers?

RFC 9449 allows authorization servers and resource servers to supply DPoP nonces. A nonce must be used only at the issuing server and must not be confused with another server's nonce or an OpenID Connect nonce. Authorization-server challenges use a 400 response; resource-server challenges use 401 with the DPoP authentication challenge. Retry state must retain the issuing-server identity.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid, recent DPoP proof establish that it has been used only once?

RFC 9449 requires accepting proofs only for a limited time and describes tracking jti values in the target-URI context to reject reuse. A valid proof can otherwise be replayed at the same endpoint. Shared-state limitations can make strict single-use tracking impractical. A server nonce can be reused with fresh proofs; nonce reuse alone is not equivalent to proof reuse.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

What establishes that a DPoP token exchange used the proof key bound to its authorization code?

RFC 9449 defines optional dpop_jkt to bind an authorization request and its code to a proof-key thumbprint. At token exchange the authorization server must reject a proof whose key does not match that original value. The parameter can be combined with PKCE; similar injection protection requires a unique DPoP key per authorization request and is not a universal PKCE replacement.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a DPoP token request guarantee sender-constrained protection at every resource server?

RFC 9449 allows an authorization server to return Bearer even when a DPoP proof was supplied; clients requiring DPoP access-token protection must discard that response. A resource supporting both schemes must reject a DPoP-bound token presented as Bearer. Legacy Bearer-only resources have different compatibility behavior, so issuance and each resource's support must be established separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful Redis WAIT response establish the requested replication level for every prior application write?

Redis WAIT reports how many replicas acknowledged earlier writes on the current connection. It returns a count on timeout as well as success, so that count must be compared with the requested level. In MULTI and other nonblocking contexts it returns immediately rather than waiting. A WAIT call on another pooled connection does not establish the original writes' barrier.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Redis WAIT guarantee that an acknowledged write survives failover?

Redis documents that WAIT does not make the store strongly consistent. Sentinel and Cluster attempt to promote a suitable replica, but this selection is best effort; even a write acknowledged by multiple replicas can be lost after failover. A replication acknowledgement is useful evidence, not a guarantee of survival under every failure sequence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a WAITAOF return establish that the requested local and replica persistence levels were met?

Redis WAITAOF, available since 7.2, reports local and replica AOF fsync acknowledgements for prior writes on the same connection. Timeout can return counts below the requested levels; MULTI or script contexts do not block. AOF configuration and documented propagation limitations apply. Inspect both counts; the command does not create global strong consistency or guarantee every failover outcome.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does QUEUED establish that a Redis transaction executed before a connection interruption?

Redis queues commands after MULTI and executes them when EXEC is called. QUEUED is therefore scheduling evidence, not execution. Disconnecting before EXEC performs none of the queued operations. If EXEC was sent and its response was lost, that earlier guarantee does not establish non-execution or make repetition safe; inspect the actual command outcomes separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an error during Redis EXEC mean that every operation was rolled back?

Redis distinguishes errors while queueing from errors during EXEC. Since 2.6.5, detected queue-time errors cause EXEC to discard the transaction. Runtime errors do not stop the other queued commands, and Redis does not roll back successful operations. An error in the reply array is therefore not proof that the transaction made no changes.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Redis WATCH transaction abort even when no other client wrote the watched key?

Redis WATCH makes EXEC conditional on watched keys remaining unchanged. Changes include client writes and Redis expiration or eviction; versions before 6.0.9 did not abort for expiration. A conflict returns a Null EXEC reply and aborts conditional execution. Merely seeing no competing client write does not establish that WATCH must succeed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Redis XACK prove completed business processing or erasure of the message payload?

Redis XACK removes entries from a consumer group's Pending Entries List and returns the number successfully acknowledged. Already absent IDs are not counted. Consumers should acknowledge after processing, but the command does not independently inspect that business outcome. Clearing the PEL entry is not itself evidence that the stream payload or every other retained copy was erased.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a completed XAUTOCLAIM scan establish that every pending Redis message was recovered and processed?

Redis XAUTOCLAIM scans pending entries and claims those meeting its idle-time condition. A returned 0-0 ends that scan, but later calls can find entries that have since become eligible. Since Redis 7.0, missing or trimmed stream entries are removed from the PEL and reported separately, not recovered. Cursor completion therefore does not prove all work was processed or all payloads were restored.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does attaching a Stripe feature to a product immediately entitle existing subscribers?

Stripe documents that product feature changes create active entitlements for existing subscriptions at the next billing-period start. A changed product definition therefore does not establish that every existing customer already has the feature. Compare the subscription period, feature mapping and current customer entitlement inventory before provisioning.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Stripe entitlement webhook establish that a customer has only the features listed in its data array?

Stripe limits the active-entitlement summary data array to ten entitlements. For larger inventories, its documented URL leads to the complete paginated list. Absence from the inline array alone is insufficient evidence for removing access; reconcile the full inventory for the exact customer.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a provisioning service recover a Stripe customer feature inventory without replaying every missed webhook?

Stripe documents listing current active entitlements by customer for startup and reconciliation after webhook delivery failure. The response is paginated and uses feature lookup keys. This supports reconstructing the current declared feature inventory; it does not prove that the application applied it or that earlier access was correct.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does accepting a Stripe meter event prove that its usage was successfully aggregated for billing?

Stripe processes meter events asynchronously. Aggregated summaries and upcoming invoices can lag received events, and processing errors can produce meter error-report or no-meter events. Retain event identity and reconcile processing outcomes before treating an accepted request as a complete billable usage record.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Will an accepted late Stripe meter event necessarily update a finalized invoice or appear on the next one?

Stripe distinguishes meter-event acceptance from invoice inclusion. Its timestamp window can permit an event after the related invoice finalized, while the event appears in summaries without updating that invoice or entering the next one. Threshold invoices have an earlier receipt cutoff. Match event receipt, service period and invoice lifecycle.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Stripe billing-credit balance pay every type of subscription charge?

Stripe billing credits apply to eligible subscription items linked to meter prices. They are applied after discounts and before taxes and invoice credit balance. Legacy usage-record prices and non-metered charges are outside the documented supported scope. Match credit applicability and eligible invoice lines rather than treating a balance as universal payment coverage.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does issuing a Stripe credit note restore billing-credit grants previously consumed by an invoice?

Stripe documents different outcomes for voiding an invoice and issuing a credit note. Voiding reinstates applied grant balance, but already expired credits expire again immediately. A credit note does not refund the applied grant; restoring those billing credits requires a new grant. Reconcile the actual grant ledger and correction type.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can invoice creation order predict which Stripe subscription consumes a shared billing-credit grant first?

Stripe applies a grant eligible for multiple invoices to the invoice that finalizes first. Subscription invoices finalize independently, so their finalization order is not guaranteed. Within one invoice, eligible lines consume credit in their listed order. Reconcile actual allocation rather than assuming creation order or equal sharing.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Auth0 rotation overlap window permit replay of any earlier refresh token?

Auth0 describes an optional rotation overlap period to tolerate concurrent exchanges. During that leeway, reuse detection does not apply to the immediately previous token; exchanging the second-to-last token triggers detection. The configured window and exact token generation matter when deciding whether a retry is tolerated.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does unlinking one Auth0 device revoke every refresh token for the user and application?

Auth0 distinguishes refresh-token revocation from deleting its authorization grant. The tenant revocation setting controls whether related tokens are invalidated with the grant; with the setting disabled, unlinking a device revokes its associated refresh token while leaving the grant intact. Verify the endpoint, setting and grant identity before claiming broader offboarding.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a GitLab job-token fine-grained allowlist restrict every API endpoint the token can use?

GitLab lists endpoints without fine-grained permissions and states that permissions on an allowlist entry do not restrict those endpoints. A fine-grained rule list is therefore not a complete description of token authority. Review the documented exceptions together with the triggering identity, project access and applicable GitLab version.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a GitLab group allowlist authorize a newly added nested project without editing the allowlist?

GitLab documents group allowlist matching across projects in the group and all nested subgroups. The match is evaluated whenever a job uses the token, so projects added later are included without an allowlist change. Permission reviews must include group membership over time as well as effective user and operation permissions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful GitLab job-token push prove that the target revision started a validation pipeline?

GitLab documents that pushes authenticated with a CI/CD job token do not trigger CI/CD pipelines. Enabling job-token push permission and recording a successful push therefore establish neither a pipeline start nor validation of the resulting revision. Retain independent pipeline evidence if validation is a release condition.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the Claude Cost API report all Priority Tier charges alongside token usage?

Claude documents Priority Tier usage in the usage endpoint through the service_tier dimension, but excludes Priority Tier costs from the cost endpoint because the billing model differs. A cost response alone is not a complete charge inventory when Priority Tier is used. Reconcile the applicable billing evidence separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can the Claude Messages usage endpoint alone account for code-execution charges?

Claude documents code-execution costs in the cost endpoint under a Code Execution Usage description, while code execution is not included in the usage endpoint. A Messages usage export cannot by itself establish complete tool charges. Reconcile the cost report and invoice scope with token usage for the same organization and period.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should a Claude usage reconciliation discard rows with null API-key or workspace identifiers?

Claude documents that Console playground usage has a null API-key identifier even when grouped by that dimension, and the default workspace has a null workspace identifier. Such rows can represent documented usage populations. Preserve them with their documented meanings rather than dropping them as missing or assigning them to a guessed customer.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is a Claude Managed Agents max_list_cost budget an exact upper bound on final session cost?

Claude documents that the model request crossing a session budget completes, potentially exceeding the cap by one model request per thread. Its returned tool calls still run and their search and runtime costs count. The budget bounds starting new work rather than guaranteeing an exact final charge; retain the usage snapshot and stop reason.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should summed Claude Managed Agents thread costs equal the session list cost exactly?

Claude documents independently rounded thread figures that exclude the session running-time cost. Session active_seconds counts overlapping thread activity once, and the session figure governs its budget. Differences between summed thread costs and session cost therefore require scope and rounding reconciliation rather than an automatic double-billing conclusion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does null or unchanged OpenAI Agents session usage prove that no cost was incurred?

OpenAI describes Agents API session and turn usage as best-effort: it can be null when unknown and recorded values may change as accounting arrives. These counts are not a final bill. Treat missing usage as unestablished, retain observation times and reconcile later accounting before concluding zero consumption or final cost.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should reasoning and cached tokens be added to OpenAI Agents input and output totals?

OpenAI documents cached tokens as a subset of input_tokens and reasoning tokens as a subset of output_tokens in Agents usage. Adding those detailed categories again to the parent counts double-counts recorded tokens. Preserve the subsets for applicable pricing analysis while keeping the totals and component categories distinct.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a sent Coupa purchase order establish supplier acknowledgement or completed confirmation?

Coupa exposes separate transmission, acknowledgement and confirmation fields. A sent transmission is not the same field as supplier acknowledgement or completed confirmation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does creating a Coupa invoice through the API submit it for approval?

The documented create action makes a draft invoice. A separate submit action sends a draft for approval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does approved Coupa invoice status prove each configured approver reviewed it?

The invoice API documents actions that bypass all approvals or the current approval. Status alone therefore does not establish which reviewers acted.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an earlier Coupa invoice approval chain be reused after restart_approvals?

The documented restart action clears the current chain and generates a new chain for a modified invoice.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does marking a Coupa Pay payment exported prove the supplier was paid?

The Payments API uses exported as an integration marker and separately exposes payment status. Its PUT operation is limited to marking export.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does pay_externally in Coupa independently verify an external payment?

The action marks an invoice payable paid and stops Coupa tracking. Separate actions stop or restart tracking without representing payment verification.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Coupa payment header total be assigned to one invoice without inspecting payment-details?

The API documents payment-detail rows with invoice identifiers, invoice references, payment amounts and currencies.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an export-once Coupa payment extract prove later payment status changes were captured?

The documented extraction guidance uses updated-at to capture payment status changes; exported separately indicates a previous integration export.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is an Issuing spending limit a strict instantaneous maximum for an agent budget?

Stripe documents best-effort spend aggregation with a possible delay, and later tips or fees that can exceed a limit.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Issuing spending limit for one merchant category block every other category?

A category-scoped limit applies only to its categories. Category restrictions use the separate allowed or blocked category controls.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does replacing an Issuing card reset its spending-limit history?

The documented card limits extend across the replacement chain, while cardholder limits apply across that cardholder's cards.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does deactivating an Issuing card block capture of an already approved authorization?

The captured documentation excludes capture from current card-status, spending-control and real-time authorization checks.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Issuing refund authorization link reliably identify the original purchase?

Stripe describes refund linkage as inexact: the authorization can be unrelated or absent.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does every Issuing transaction with type refund add a credit?

A refund reversal retains type refund but has a negative amount, unlike a standard positive refund.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does absence of an approved Issuing authorization prove no capture can occur?

Stripe documents captures following a decline or without an authorization; a transaction can therefore lack an authorization link.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does approved=true prove the agent authorization callback successfully decided the purchase?

On a missing or invalid response, configured fallback can decide the authorization. Stripe directs users to request-history error reasons when assessing callback health.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should an Issuing decision use the initial top-level amount instead of pending_request.amount?

The request stores the requested amount in pending_request while initial top-level amount is zero. The top-level fields change after the response.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can one Issuing authorization be reconciled using only one capture transaction?

Merchants can partially or repeatedly capture an authorization. The held amount depends on the authorization and all linked captures.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does no Issuing authorization-request callback mean no purchase was attempted?

Spending controls run before the synchronous callback and can decline a request before it is sent, producing a declined authorization-created event.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Whose project permissions does a GitLab pipeline trigger token use?

GitLab documents that a pipeline trigger token impersonates the creating user’s project access and permissions. Possessing the token is not independent evidence that the intended delegated action has owner approval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful upstream GitLab pipeline prove that its user may start a downstream project pipeline?

For multi-project pipelines, GitLab requires the user creating the upstream pipeline to be able to start pipelines in the downstream project. A trigger job can fail when that user lacks the required permission.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a passed GitLab trigger job prove its downstream pipeline completed successfully?

By default, a trigger job passes when the downstream pipeline is created. GitLab provides a trigger strategy to reflect downstream status; default trigger success alone does not report the downstream execution outcome.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does starting a replacement upstream GitLab pipeline automatically stop its earlier multi-project downstream work?

GitLab documents that multi-project downstream pipelines are not automatically cancelled when a new upstream pipeline starts, even when interruptible is configured. Cancellation in the downstream project has its own context.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does forwarding a masked GitLab variable to another project preserve its masking configuration?

GitLab warns against forwarding masked variables to multi-project pipelines because the masking configuration is not passed downstream. The value could be revealed in downstream job logs.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a GitLab downstream project’s variable value override a forwarded upstream value of the same name?

GitLab documents that upstream variables take precedence over same-name downstream variables. Forwarded variables become trigger variables with high precedence, so local downstream configuration alone may not identify the effective value.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does fetching downstream artifacts by branch name identify the upstream merge-request pipeline’s artifacts?

GitLab instructs merge-request artifact consumers to use the merge-request ref path through CI_MERGE_REQUEST_REF_PATH. Using the branch name retrieves artifacts from the latest branch pipeline instead of the merge-request pipeline.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does passing a repository secret to a reusable workflow establish the secret value used by a job with an environment?

GitHub documents that a called workflow’s job-level environment secret takes precedence over a same-name repository or organization secret. The caller must still pass the secret by name or inheritance; an unpassed secret can resolve to an empty value unless required. A required flag checks that the caller passes the secret, not that its value is nonempty.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

When a GitHub attestation uses a reusable workflow, which workflow identity must a verifier constrain?

The GitHub CLI identifies the reusable workflow as the signer for attestations produced through reusable workflows. Verification policy can constrain the signer workflow or repository; the caller repository alone does not fully specify the permitted signer.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can offline GitHub attestation verification detect that a repository name was later renamed or reused?

The GitHub CLI documents that offline bundle verification compares names recorded when the certificate was created. Without current GitHub API lookup it cannot detect later repository renaming or name reuse.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successfully verified GitHub artifact attestation establish that all provenance predicate claims are trustworthy?

The GitHub CLI warns that, apart from certificate information and verified timestamps, an attestation’s contents can be influenced by the workflow that produced it. A compromised producing context can falsify predicate data; verification must include trust in that context.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should a GitHub private-repository attestation be assumed to have the public Sigstore transparency-log evidence?

GitHub documents different Sigstore instances: public-repository attestations use the public instance, while private-repository attestations use GitHub’s instance without a transparency log. The private instance federates with GitHub Actions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a verifier use the message digest inside a Sigstore bundle as proof of the artifact’s own digest?

The Sigstore bundle specification marks message_digest as informational. A verifier must obtain or compute the digest for the artifact being verified rather than trusting that field to identify the supplied artifact.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Sigstore bundle’s DSSE envelope establish a multi-signer quorum?

The documented Sigstore bundle profile restricts its DSSE envelope to a single signature and an in-toto Statement payload type. Generic DSSE support for multiple signatures does not make a Sigstore bundle a threshold-approval proof.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does verifying specified Cosign annotations reject an attestation or signature that contains additional annotations?

Cosign’s verification documentation says each requested annotation must match. Additional annotations are permitted, so matching selected key/value pairs establishes a required subset rather than exact equality with a complete allowed annotation set.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Rekor’s signed integrated time be treated as an immutable independently trusted signing timestamp?

Sigstore documents that Rekor v1 integratedTime uses Rekor’s internal clock and is not included in the append-only log node, despite being signed. Rekor v2 uses a separate timestamp authority. Timestamp trust must therefore be evaluated by version and evidence type.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does recreating an IAM role preserve every trust policy that named its ARN?

AWS converts a role ARN in a trust policy's Principal element to the role's unique principal ID. Deleting and recreating the role breaks that binding. An aws:PrincipalArn condition is not converted in this way, so a condition using the same role ARN can continue to match the recreated role. The two policy forms require different offboarding and restoration checks.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do multiple Entra PIM approvers provide unanimous approval?

PIM resolves an activation request when the first approver approves or denies it and notifies the other approvers. Configuring several approvers therefore does not establish a quorum or unanimous decision.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does PIM's MFA requirement ensure a fresh challenge on each activation?

Users may satisfy PIM's MFA requirement with strong credentials or MFA already supplied in the session. The documented authentication-context approach has its own reauthentication settings; even the described Every time configuration has a ten-minute reuse window across eligible activations. An MFA setting alone does not prove a fresh interaction for each request.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a returned PAM revoke operation establish completed grant removal?

The PAM revoke guide returns a long-running operation and directs callers to query its progress. Receipt of that operation, including an unfinished response, does not establish completed revocation. This review is limited to the guide's active-grant workflow; it does not resolve broader API-state eligibility.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does activating PIM from a compliant device restrict subsequent role use to that device?

PIM authentication context governs activation. Microsoft explains that after activation the user can use another session, device or location; a separate policy targeting the activated directory role or users is needed for the intended subsequent sign-in conditions. Activation-device evidence alone does not bind all later use.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does CancelLegalHold DeleteAfterDays control how long the backups remain locked?

AWS documents DeleteAfterDays on CancelLegalHold as retention for the legal-hold record itself, defaulting to 180 days. Recovery points unlock as cancellation processes and are not governed by that metadata-retention parameter. Other holds and recovery-point lifecycles still need separate review.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does deleting a failed restore-access vault remove its underlying protected backups?

AWS describes a restore-access backup vault as a view of the underlying logically air-gapped vault, containing no recovery points of its own. Its documented FAILED-state recovery procedure allows deleting the view; Vault Lock does not prevent that deletion. Removing the view is not evidence of erasing the underlying recovery points.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does AWS Backup always restore into a new resource without overwriting existing data?

The reviewed AWS Backup restore guide generally describes new-resource restoration but explicitly identifies destructive exceptions: Redshift Serverless namespace restores overwrite target-namespace data, and SAP HANA on EC2 restores overwrite the specified target database. Target type and location must be resolved before treating a restore as non-destructive.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does re-enabling DynamoDB PITR restore the previous recovery window?

Disabling and then re-enabling DynamoDB point-in-time recovery resets the start time for the recovery window. The newly enabled window does not restore the previous continuous recovery history. Inspect the reported earliest and latest restorable times and any separately retained backups before relying on a pre-reset recovery point.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does CHARGEBACK_REVERSED establish that the dispute is finally won?

Adyen can return the disputed amount while the issuer still reviews the defence. Its dispute guidance says CHARGEBACK_REVERSED can remain Pending and a second chargeback can follow. The financial credit and final dispute outcome must be reconciled separately for the applicable scheme flow.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Wise's Completed label prove final receipt at the beneficiary bank?

Wise maps its consumer Completed label to outgoing_payment_sent, meaning it sent the payout rather than confirming beneficiary credit. Transfers support rollback transitions, and returned funds can lead to bounced_back, processing or refund outcomes. Reconciliation cannot assume that reaching the sent state makes later state changes impossible.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Wise inbound-payment return marked REFUNDED prove the originator received it?

For the documented inbound return flow, CANCELLED means the balance was debited and return processing starts; REFUNDED means the return was processed and is en route to the originator. Wise also describes reconciliation using the original inbound transfer ID in the balance statement. A processed return is not independent evidence of originator-bank receipt.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid Wise quote alone authorise a transfer to a changed recipient?

Wise documents quote.targetaccount.mismatching when quote and target recipient do not match, and requires the quote and recipient to belong to the same profile and transfer context. A missing target account must also be resolved before accepting the quote. These API checks do not verify the buyer's approval of a bank-detail change.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can every failed GoCardless payment be retried as an insufficient-funds failure?

The partner collection guide limits the described manual retry path to insufficient-funds failures, up to three retries, and separately directs cancelled or expired mandates to a new mandate. Failure reason and mandate state are necessary inputs; a generic Failed status is not a retry permission.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a refund debit in a GoCardless payout prove the customer received the refund?

GoCardless defines refund_funds_returned as a credit when a previously deducted refund failed to reach the customer. The original refund debit therefore needs reconciliation with later return items and their payment or mandate links before concluding the customer received funds.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does any Kubernetes audit-backend failure automatically fail the API operation?

Kubernetes distinguishes batch, blocking and blocking-strict audit modes. The documented blocking-strict request-failure condition applies to audit logging failure at RequestReceived; ordinary blocking waits for event processing, and batch is asynchronous. A configured backend does not establish universal fail-closed behaviour for every audit stage.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Azure Monitor data export deliver each log record exactly once despite destination outages?

Azure documents export retries for up to 12 hours when the destination lacks capacity or availability. Retries may duplicate some records, and data is discarded if the destination remains unavailable beyond that period. Both missing records and repeated delivery require reconciliation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a root management-group diagnostic setting capture every subscription activity event?

Azure documents that subscription events lacking the hierarchy property do not propagate to management-group diagnostic settings, including the root. Subscription-level settings are needed for those events. Configuring both levels may duplicate shared events, so coverage and deduplication are separate checks.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does platform-level Access Transparency support cover every AI serving component?

The captured Agent Platform guide lists component and workload exclusions, including custom-container inference or explanation, AutoML forecasting resources, RAG Engine, Vector Search 2.0 and Vizier. General support for the platform does not establish coverage of a deployment using an excluded path. Product names and support must be checked against the dated source.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does starting an unqualified state machine ARN execute the previously reviewed version?

An unqualified ARN starts the latest revision and is not associated with a version, even if a version contains that same revision. A version ARN selects that version; an alias ARN selects through the alias. Approval evidence must bind the invoked ARN and execution version rather than assume that a previously reviewed definition was used.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a principal in another AWS account directly return a Step Functions task token?

The integration guide requires task tokens to be returned by principals in the same AWS account; tokens sent from principals in a different account do not work. Returning a token is a technical callback mechanism, not proof that a reviewer had business authority or that the referenced action matches an approval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does EventBridge archive replay preserve the original event order?

Archived events are not necessarily replayed in their original arrival order. Replay selection uses event time and processes one-minute intervals; replay metadata identifies the replay. Consumers must reconcile action identities and ordering requirements rather than assume replay reproduces the original execution sequence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does AWS CUR LegalEntity always identify the party issuing the invoice?

LegalEntity identifies the seller of record for the product or service. The seller and invoicing entity are usually the same but can differ for third-party AWS Marketplace transactions. Bind the invoice issuer, seller and relevant purchase separately; the exported seller label does not authorize a changed payee or bank account.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Databricks' typical usage availability establish that later corrections are complete?

The captured guide says original billing usage records are typically available within twelve hours, with new workspaces potentially taking longer. This statement applies only to ORIGINAL records, not RETRACTION or RESTATEMENT corrections. It is not a finalization deadline; retain the observation time and reconcile later changes before closing an interval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does one downloaded Azure cost-export file preserve the complete report and its earlier version?

Enhanced exports partition data, with each file containing only a subset and the manifest describing the full set. Daily overwrite is enabled by default and replaces the previous day's file with updated data. Reconstruct a run from its manifest and all partitions, and preserve a dated copy if the earlier report is needed for reconciliation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an immutable GitHub release freeze its title, notes and latest designation?

GitHub locks an immutable release's assets and associated tag, but its title, release notes, pre-release status and latest designation remain editable. Preserve the actual asset digest and release attestation separately from a captured description. Immutability does not establish that later editorial claims were present when the artifact was approved.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does adding an npm trusted publisher disable traditional publishing tokens?

Trusted publishing adds an OIDC-authenticated publishing route alongside traditional tokens and manual publishing. Disallowing traditional tokens is a separate package setting; OIDC publishers continue to work when that restriction is applied. Review all enabled routes before describing the package as tokenless.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does every npm OIDC publication automatically include provenance?

The captured guide limits automatic provenance to supported GitHub Actions or GitLab CI/CD publication from a public repository to a public package. CircleCI provenance is not supported in that capture, and generation can be explicitly disabled. Verify the actual attestation and configuration rather than infer provenance from OIDC authentication alone.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a new GitHub account reusing a former owner's name inherit its PyPI trusted publishing authority?

PyPI stores the configured GitHub owner's immutable ID and checks repository_owner_id during token minting. A matching reused username with a different owner ID fails that check. Review the stable identity binding; a textual owner or repository name alone is not the documented authority test.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an emergency stop button establish the AI RMF intervention outcome?

AI RMF 1.0 MANAGE 2.4 pairs mechanisms for superseding, disengaging or deactivating unsuitable systems with assigned and understood responsibilities. A control shown in a user interface is not evidence that an authorized operator can apply it in the relevant scenario. Review mechanism scope, responsible roles and evidence of its application separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does collecting AI user feedback establish that it influences the system?

AI RMF 1.0 GOVERN 5.2 describes mechanisms for regularly incorporating adjudicated feedback into design and implementation. A feedback inbox or survey count does not establish review, disposition or incorporation. Trace relevant feedback to a reasoned decision and the resulting change or documented decision not to change.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful emergency-account sign-in establish that its administrative use was authorized?

Microsoft separates sign-in and audit monitoring, post-use review and periodic validation. Its guidance calls for reviewing whether emergency use was authorized and actions appropriate, and testing sign-in and administrative functionality at least every 90 days and after specified organizational changes. A successful sign-in alone establishes neither business authorization nor continued readiness.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a NotPrincipal Deny reject an IAM role despite an intended exclusion?

AWS warns that a resource policy using NotPrincipal with Deny always denies IAM principals with permissions boundaries, regardless of the NotPrincipal values. It recommends a PrincipalArn condition approach instead. An exclusion in that policy form is therefore insufficient evidence that a bounded role can still use the resource.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an unapproved Entra PIM request remain valid indefinitely?

Delegated approvers have a non-configurable 24-hour window for an Entra role activation request. If it is not approved within that period, the eligible user must submit a new request. A stale pending request is not a continuing approval opportunity.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does editing a PAM entitlement update existing grants and all pending approvals uniformly?

Google documents that updated entitlement configuration applies to grants requested after the update. Changes to an approver list also affect undecided requests. Adding or removing approval levels, or changing required approval counts, requires no grants awaiting approval. The reviewed documentation marks these structural controls as preview; multi-level or multiple-approval workflows also require Security Command Center Premium or Enterprise. Bind the request time, decision state and precise type of change to the governing configuration.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a PAM entitlement guarantee that a new temporary grant can be applied?

PAM adds time-bound IAM role bindings, and each active grant consumes IAM policy space. Google documents that new grant requests fail when the resource policy reaches its size limit. Entitlement configuration alone does not prove that a requested elevation was successfully installed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does MFA on creation of an active PIM assignment prove the assignee authenticated for later use?

The active-assignment MFA setting requires the administrator creating the assignment to satisfy MFA. Microsoft states that PIM cannot enforce MFA when the assigned user uses that already-active role. Assignment-creation authentication and assignee-use authentication are different evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a new Vault Lock minimum replace the lifecycle already assigned to each backup?

AWS describes backup retention periods as defined when each backup is created and independent of the vault lock's minimum and maximum settings. A lock configuration is therefore not evidence that every retained recovery point has the newly selected retention duration.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a completed primary-backup job prove the recovery point reached its logically air-gapped target?

For documented unsupported resources or encryption-key cases, AWS Backup can complete to the standard vault with issues while the air-gapped copy is unavailable. For copied resource types, the destination copy job must be reconciled separately with the source recovery point and target vault. Backup completion alone does not establish that protection location.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a completed AWS Backup restore test establish that its temporary resource was deleted?

Restore-test deletion has a separate Successful, Deleting or Failed status. AWS documents that failed cleanup needs manual removal and that removing the awsbackup-restore-test tag often causes this failure. Test execution or validation completion alone does not close the retained-resource inventory.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an API-driven AWS Backup restore preserve the same tags as the console default?

StartRestoreJob defaults CopySourceTagsToRestoredResource to false, while the documented console default includes tags. Resource-specific exceptions apply: some resources do not support the option, and documented snapshot behaviours can copy tags independently of it. Tag-derived governance cannot be assumed from an otherwise successful restore.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Azure Backup delete operation have the same retention effect in every region and API version?

Microsoft's reviewed secure-by-default guidance distinguishes preview-region behaviour from GA Recovery Services vault enforcement. Preview behaviour depends on client/API versions and prior configuration, while GA enforcement spans API versions. Soft-deleted data remains recoverable for the configured period. The region, vault type, rollout stage and request version are necessary to interpret a delete result.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Adyen payout booked event establish credit to the beneficiary bank?

Booked means the funds were deducted from the balance account and is not final. Adyen distinguishes later failures or returns, local-payout arrival estimates, and credited tracking for completed instant payouts. An estimate or outgoing debit does not establish the same outcome as a credit-confirmation event.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Wise transfer in incoming_payment_initiated establish received funding?

Wise describes incoming_payment_initiated as funding started but not yet received. The processing state indicates Wise has received funds and is performing its processing activities; it does not itself establish payout. Transfer submission, funding receipt and recipient outcome require distinct evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an unexpired Wise quote guarantee the originally approved rate remains locked?

Wise exposes rateType, rateExpirationTime and expirationTime as separate fields: rate expiry concerns the locked rate, while expirationTime concerns the whole quote. The guide also binds the rate promise after transfer creation to funding before its deadline. Quote validity alone is not evidence that approved conversion terms still apply.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can changing an originator reference safely resolve Wise's originator-not-allowed error?

For validation.failure.originator.externalId.not.allowed, Wise instructs integrations to investigate the restriction or a confirmed data defect and retain the same reference for the same originator. Altering the identifier is not documented as a legitimate way to clear the restriction.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a GoCardless payment still be cancelled after submission to the banking system?

GoCardless distinguishes pending submission, where cancellation is available, from submitted, where it says the payment can no longer be cancelled through that flow. The guide directs a customer seeking cancellation at that point to their bank. A local cancellation request is not evidence that the banking instruction stopped.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does enabling GitHub audit streaming backfill all earlier enterprise events?

GitHub documents that the stream exports audit and Git events for activity from the time streaming is enabled onwards. Existing searchable retention and newly enabled streaming are different coverage windows; historic export needs its own method and receipt.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does successful creation of an Azure data-export rule prove every selected table is exported?

Azure says a rule containing an unsupported table can be configured successfully while exporting no data for that table. Its support list also contains tables with only certain ingestion paths supported. Configuration success must be reconciled against each table and ingestion source.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Access Transparency contain Google personnel activity authorised by the customer's own IAM policy?

Google excludes personnel access that the customer granted through IAM from Access Transparency and directs that activity to Cloud Audit Logs when enabled. Provider support-access reporting and customer-granted access therefore require different evidence paths.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does moving a message to an SQS dead-letter queue restart its retention clock?

For standard queues the original enqueue timestamp continues to govern expiry, while the dead-letter age metric measures time since the move. FIFO queues reset the enqueue timestamp when a message moves to the dead-letter queue. Queue type and original age therefore determine the remaining recovery window.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does stopping a Step Functions workflow guarantee its synchronous service job stopped?

Cancellation of an aborted .sync integration is best effort. Missing execution-role permissions or a temporary service outage can prevent cancellation, including after the workflow stops or another parallel branch fails. The integrated job may continue and incur charges; reconcile its own status before treating the action as stopped.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an EventBridge PutEvents response establish that every entry was accepted?

A PutEvents batch can contain both successful entries with EventId and failed entries with ErrorCode and ErrorMessage. Reconcile each response entry with its corresponding request entry and retry only unresolved failures with application-level duplicate controls. Batch-level transport success is not a complete per-event outcome or downstream delivery receipt.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an immediate EventBridge archive count prove all recent events are available for replay?

Archive ingestion can lag receipt on the bus. AWS recommends delaying replay for ten minutes; DescribeArchive EventCount and SizeBytes can take 24 hours to reconcile new or expired events. These values and the recommended delay are not independent proof of complete capture; reconcile required event identities and the replay window.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must every SavingsPlanCoveredUsage row match exactly one SavingsPlanNegation row?

SavingsPlanCoveredUsage unblended cost represents what usage would have cost without the benefit and is offset by negation entries. Negations are grouped hourly by SavingsPlanARN, operation, usage type and Availability Zone, so one can offset several covered rows. Use the documented grouping and SavingsPlanEffectiveCost for the intended calculation rather than summing counterfactual charges as new payable cost.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Databricks SKU uniquely identify which product generated usage?

Several Databricks products can share a SKU. The guide identifies billing_origin_product and product_features as the fields for distinguishing the originating product and features, including shared serverless-jobs billing. SKU-only allocation can merge different workloads; preserve the applicable product fields and their documented population conditions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should Azure cost rows with missing subscription attributes be rejected as malformed?

The enhanced export experience uses null or empty values for missing attributes such as subscription IDs instead of a default empty GUID. The guide identifies unused reservations, unused savings plans and rounding adjustments as affected charges. Preserve their applicable billing context rather than silently discarding them or interpreting the placeholder change as a new subscription.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can deleting an immutable GitHub release restore reuse of its tag name?

After the immutable release is deleted its tag may be deleted, but the same tag name cannot be reused. GitHub also retains protection against reusing tags from an immutable release when a repository is deleted and recreated with the same name. Deletion is therefore not a route to replacing a previously sealed release under its old tag.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does npm trusted publishing grant direct publication and dist-tag management together?

The captured guide distinguishes staged publishing, direct npm publish and dist-tag management. Direct publishing and dist-tag permissions are independent choices, and historical configurations have date-dependent defaults. Review the actual connection's allowed actions. Other stage actions, including approval, require interactive authentication and cannot use OIDC tokens.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Which workflow identity must match npm trusted publishing when one workflow calls another?

For the workflow invocation paths described in the captured guide, validation checks the calling workflow name rather than the workflow containing npm publish. The guide also requires id-token: write on parent and child workflows. Match the documented identity to the actual call chain instead of configuring only the reusable publish file.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does recording a third-party AI dependency satisfy the AI RMF contingency outcome?

AI RMF 1.0 GOVERN 6.2 describes contingency processes for failures or incidents involving high-risk third-party AI systems or data. A dependency inventory alone does not show such a process exists. For a buyer review, identify the affected dependency, failure conditions, responsible operator and documented fallback or escalation evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a risk review close without recording remaining risks to downstream users?

AI RMF 1.0 MANAGE 1.4 describes documenting negative residual risks for downstream acquirers and end users. A list of mitigations does not by itself record what remains unmitigated or who may be affected. Review the residual-risk statement, affected uses and decision owner without treating risk documentation as acceptance by every downstream party.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an eligible federated administrator be treated as a fully independent emergency-access path?

Microsoft's emergency-access guidance recommends cloud-only accounts independent of federation and synchronization, with permanent active Global Administrator assignments rather than PIM eligibility. It also separates emergency authentication methods from normal administrator methods. These recommendations address shared failure dependencies; configuration and an actual authorized validation are still needed to establish availability.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Entra PIM requester or service principal approve the activation request?

For Microsoft Entra role activation, PIM prohibits approvers from approving their own requests and does not allow service principals to approve requests. Delegation to an approver does not remove these identity restrictions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does requiring a PIM ticket number validate the external approval ticket?

The Entra PIM ticket-information setting requires a support ticket reference but treats it as an information-only field. PIM does not enforce correlation with an external ticketing system. A populated reference is therefore not evidence that the ticket exists, is approved, or covers the action.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can deleting a PAM entitlement substitute for revoking its active grants?

Google's entitlement-management guide says an entitlement with active grants cannot be deleted; those grants must first be revoked. An attempted entitlement deletion is not evidence that active temporary access was removed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does PIM's authentication-context fallback cover a disabled or report-only Conditional Access policy?

PIM's documented fallback to MFA protects the case where no Conditional Access policy targets the configured context. It is not triggered when a targeting policy is disabled, report-only, or excludes the eligible user. Context configuration therefore cannot substitute for checking the applicable enabled policy.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can requiring PIM approval leave no available default approver?

When no specific approvers are selected, active Privileged Role Administrators or Global Administrators are the defaults. Microsoft warns of tenant lockout when all such administrators are only eligible, none are active, approval is required, and no approvers are selected. An approval requirement alone does not establish an available escalation path.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does releasing one AWS Backup legal hold make a recovery point deletable?

A recovery point can have multiple legal holds. AWS states it cannot be deleted while any hold remains; after all holds are removed its own retention lifecycle applies. Releasing one named hold neither clears other holds nor establishes immediate deletion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does DELETE_AFTER_COPY mean a temporary recovery point disappears after the first copy finishes?

For the documented temporary snapshot flow, DELETE_AFTER_COPY schedules removal after all copy jobs complete or the specified retention period, whichever comes first. Copy-triggered cleanup requires all automatic and scheduled jobs to finish and a completed air-gapped copy retained at least as long as the source. Failed copying retains the source according to its lifecycle. Continuous-backup temporary snapshots have a separate cleanup rule because the continuous source remains. Identify the backup mode and retention path before inferring removal.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do restore-testing tag conditions ensure the restored recovery point carries those tags?

AWS Backup evaluates resource-selection tags using the protected resource's latest recovery point. It then selects at most one eligible recovery point using the plan's time window and latest-or-random rule; the tag conditions do not filter that recovery-point choice. A selected resource can therefore be restored from a point with different tags.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does deleting a DynamoDB table with PITR enabled remove every recoverable table copy?

AWS documents that deleting a PITR-enabled table creates a system backup retained for 35 days. It is a snapshot immediately before deletion, supporting recovery to that single point rather than the former continuous timeline. Table deletion therefore does not establish immediate loss of recoverability.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Azure Backup soft delete protect all operational snapshots and log recovery points equally?

Microsoft distinguishes vaulted backups from operational disk and VM snapshots that can be accessed and deleted directly before their soft-delete period expires. The reviewed guide excludes operational blob and Azure Files backups from soft-delete support and excludes SQL Server and SAP HANA log recovery points from recovery-point soft delete. Vault-level settings are not universal copy protection.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent refund the original captured amount without reconciling earlier refunds and chargebacks?

Adyen's refund validation uses the remaining payment balance, and cumulative partial refunds cannot exceed the captured amount. The guide's examples deduct prior refunds or chargebacks from the available balance. The original payment amount alone is insufficient input for a further refund decision.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Wise cancelled identify the same financial outcome as funds_refunded?

Wise distinguishes funds_refunded from cancelled. The status table describes cancelled as final for an unfunded transfer, but the same documentation also shows a funded returned-payment flow passing through processing and cancelled before funds_refunded, and permits rollback transitions. A cancelled label alone therefore establishes neither absence of funding nor completion of a refund. Reconcile the state timeline, funding and provider refund evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should an uncertain Wise transfer creation be retried with a new customerTransactionId?

Wise's error guide identifies customerTransactionId as the logical transfer identifier and says to reuse it when retrying the same uncertain creation. A new identifier can create another transfer. The quote.duplicate error requires reconciliation of the existing transfer rather than reusing that quote for another one.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a GoCardless confirmed or paid-out payment prove an irreversible collection?

GoCardless documents late failure when delayed bank reporting corrects a payment previously marked confirmed. Its lifecycle also includes chargebacks returning funds under the applicable Direct Debit rules. A paid-out or confirmed state therefore needs continued outcome reconciliation rather than being treated as irrevocable finality.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a GoCardless payout amount identify which invoices were paid?

GoCardless payouts net credits and debits, including payments, fees, refunds and chargebacks. The Payout Items API exposes each item's signed amount, type and relevant resource links. The net payout amount alone cannot attribute every included payment or adjustment to an invoice.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a new Log Analytics data-export rule include records already stored in the workspace?

Azure Monitor's continuous data-export rules export new table data as it arrives, starting from configuration time. The documentation identifies separate mechanisms for historical export, each with its own availability and limits. Rule creation alone is not a backfill receipt.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the Azure Export Failures metric count permanently missing log records?

The documented Export Failures metric counts failed export requests, including throttling, access and server errors. A retry process handles those attempts, so Microsoft explicitly says the metric is not an indication of missing data. Collection-health failures and confirmed record loss must be reported separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an empty Access Transparency log rule out all Google access to customer content?

The reviewed exclusion list includes Google's standard automated systems, cases where notification is legally prohibited, access not targeting Customer Data, and specified public identifiers or resource names. Access Transparency is therefore a bounded personnel-access record, not a complete record of every processing operation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

When can a Step Functions StartExecution retry return the original execution?

For Standard workflows, the same name and input return the original response only while the execution is running. A closed execution or different input returns ExecutionAlreadyExists; names can be reused 90 days after closure. Express StartExecution is not idempotent. Retrying safely requires the workflow type, identity, input and current execution state.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Step Functions .sync task finish before its service job completes?

A job can return a task token through SendTaskSuccess or SendTaskFailure before it fully completes. Step Functions uses that response to finish the task, stops monitoring the job and continues the workflow. A task-completion event on this path is therefore not evidence that the service job itself reached completion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can EventBridge return HTTP 200 while dropping an event sent to a nonexistent bus?

AWS documents that publishing with PutEvents to a bus that does not exist can return 200 without counting the event in FailedEntryCount. Matching finds no rule and drops the event. Verify the intended account, region and bus identity rather than treating a successful response and zero failed entries as delivery evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a blank AWS CUR ResourceId mean the cost row is invalid?

Resource IDs are optional in Cost and Usage Reports. Even when enabled, data-transfer and API-request usage and items such as discounts, credits and taxes can have a blank ResourceId. A resource-only filter can therefore exclude legitimate charges or adjustments; assess the line type and reporting configuration before rejecting the row.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

How should Databricks billing usage corrections affect a cost total?

Corrections add a negative RETRACTION to cancel the original usage and normally a RESTATEMENT containing corrected fields. If the original should not have existed, there may be only a retraction. Retain record_type and signed quantities across all related rows; ignoring negatives or requiring every correction to have a restatement can leave an incorrect total.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Snowflake's cloud-services adjustment be calculated from one monthly percentage?

Snowflake calculates the cloud-services adjustment daily in UTC using ten percent of virtual-warehouse usage. The daily adjustment is capped at actual cloud-services consumption, and serverless compute does not contribute to that threshold. The monthly adjustment sums daily calculations, so applying one percentage to monthly totals can produce a different result.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Azure reservation recommendation export reconstruct a past purchasing recommendation?

Reservation recommendation exports represent the current snapshot and do not support historical backfill. Historical export support for other datasets must not be generalized to recommendations. To assess what was presented when a commitment was approved, use a retained, dated recommendation and its parameters rather than a current export requested for an earlier period.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does GitHub release immutability establish that all required deliverable assets were included?

GitHub recommends creating a draft, attaching all associated assets and then publishing so the asset set is in place before immutability applies. Treat publication as an asset-completeness checkpoint. A signed or immutable release can still omit an operationally required file if the required set was not checked beforehand.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an unused npm trusted-publisher configuration remain ready indefinitely?

A new configuration must complete its first successful publish within two days. That first publish validates it and binds the immutable repository identity. An unused configuration expires after that window and must be deleted and recreated before it can be used. Inspect validation state and date rather than treating the saved connection as operational evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a pending PyPI trusted publisher reserve the proposed project name?

A pending publisher neither creates the project nor reserves its name until publication. If another user registers the name first, the pending publisher is invalidated. Confirm actual project ownership and publication outcome before treating the configuration as evidence that the intended distribution identity is secured.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does removing an AI service from inventory establish a safely managed retirement?

AI RMF 1.0 GOVERN 1.7 describes processes for safely phasing out AI systems without increasing risk or reducing organizational trustworthiness. Inventory removal alone does not establish that transition. Identify dependencies, outstanding work, retained evidence and accountable transition decisions as buyer-specific review inputs; the source does not prescribe a universal deletion checklist.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a developer-only assessment establish the AI RMF independent-assessment outcome?

AI RMF 1.0 MEASURE 1.3 includes regular assessment involving internal experts who were not front-line developers and/or independent assessors, with relevant consultation as needed. It does not require every review to be external. Retain assessor roles, involvement in development, review scope and findings before making an independence claim.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must an Entra emergency-access account be excluded from report-only Conditional Access policies?

The captured guidance distinguishes enforced policies that block or restrict sign-in from report-only policies. It recommends excluding emergency accounts from blocking or restricting policies, while report-only policies do not require that exclusion. Review actual policy state and authorized validation rather than treating all policies as equivalent blockers.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does RabbitMQ automatic acknowledgement establish completed processing?

In the captured RabbitMQ 4.4 guide, automatic acknowledgement considers delivery successful when sent to the connection. A worker failure can therefore lose already acknowledged deliveries before processing finishes.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a replacement RabbitMQ channel acknowledge an earlier delivery tag?

Delivery tags are scoped to their channel. Acknowledging on another channel causes an unknown-delivery-tag exception and closes that channel.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can RabbitMQ multiple=true acknowledge unfinished earlier deliveries?

The multiple flag acknowledges every outstanding delivery tag up to and including the specified tag on that channel. It does not select only finished application tasks.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does cancelling a RabbitMQ consumer stop or requeue in-flight work?

Consumer cancellation prevents future dispatch but leaves previously dispatched deliveries and their acknowledgement state unchanged. Closing the channel requeues its unacknowledged deliveries.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does RabbitMQ expiry in one queue remove copies from other queues?

Message TTL is independent for each queue. A routed message can expire at different times, and expiry in one queue does not affect its copies elsewhere.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does RabbitMQ redelivered=true prove a previous business action?

The redelivered flag is a hint of prior delivery. The original delivery may never have reached a consumer, so it does not establish processing or a completed external effect.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is Service Bus session state removed after consuming every message?

Session state remains until explicitly cleared, even after all messages are consumed. Microsoft advises clearing retained state when processing finishes.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does resubmitting a Service Bus dead letter restore its session position?

Resubmission receives a new enqueue time and sequence number, losing the original ordering relative to other session messages.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Service Bus transaction roll back external database or API effects?

Downstream databases and services do not automatically participate in the Service Bus transaction scope. Broker rollback does not establish their outcome.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Service Bus automatically retry exceptions inside a transaction?

The documented transaction behavior does not retry an operation after an exception within the transaction scope. Recovery must account for the transaction and separate effects.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Service Bus scheduled sequence number survive activation?

The scheduled sequence number is valid only while scheduled. Activation enqueues the message with a new sequence number.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Service Bus activate a scheduled message while cancellation occurs?

Activation and cancellation are independent operations without mutual locking. Cancellation during activation does not reverse activation, and the message can still become active.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Will TTL clear messages already in a Service Bus dead-letter queue?

Time-to-live is not observed inside the dead-letter queue. There is no automatic cleanup; dead letters remain until explicitly retrieved and completed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling?

Counting requires correct dead-letter configuration and IAM permissions. Forwarding is best effort, counts can reset, and deliveries may exceed the configured maximum.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Pub/Sub dead-letter forwarding preserve the original envelope unchanged?

Pub/Sub wraps an undeliverable message in a new message and adds attributes identifying the source subscription before forwarding it.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does every Pub/Sub snapshot provide seven new days of recovery?

Snapshot lifetime is seven days minus the oldest unacknowledged message age. A snapshot expiring in less than one hour cannot be created.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does successful Pub/Sub seek instantly change all delivered messages?

Seek guarantees eventual delivery of messages made unacknowledged, but delivery does not change instantly. Messages outside the target state can arrive while seek takes effect.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Pub/Sub replay acknowledged messages without retained history?

Time-based replay of acknowledged messages requires topic retention or subscription retention of acknowledged messages. A timestamp alone does not create retained history.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the first OCI referrers response contain every evidence attachment?

Distribution 1.1.1 requires a next Link when referrers span responses. Each response contains a different part of the descriptor list.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an OCI artifactType query prove the response was filtered?

Filtering support is recommended rather than universal. Applied filtering must be reported in OCI-Filters-Applied.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a referrers API 404 prove no OCI evidence exists?

Distribution 1.1.1 requires referrers tag-schema fallback after a referrers API 404. API failure alone is not completed discovery.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does OCI referrer discovery cover every repository containing a digest?

The 1.1.1 response lists matching subject references within the requested repository namespace. It is not a global cross-repository inventory.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does deleting an OCI tag remove its manifest and every alias?

Tag deletion makes that tag return 404. Manifest deletion by digest makes the digest and tags pointing to it return 404.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid OCI descriptor establish trustworthy downloaded content?

Image 1.1.1 recommends checking size and digest before consuming untrusted content. A size mismatch should prevent trust; valid descriptor syntax does not establish matching bytes.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is embedded OCI descriptor data exempt from content verification?

The Base64 data field must contain the referenced content. Image 1.1.1 recommends checking decoded bytes against digest and size.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a valid OCI image index guarantee a usable image?

Image 1.1.1 requires the manifests array but permits it to be empty. Validity does not establish an available platform manifest.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an OCI subject field approve the referenced artifact?

Image 1.1.1 defines subject as a weak association used for referrer discovery. It does not define certification or approval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Notary policy pass mean every signature check passed?

The pinned specification distinguishes strict, permissive, audit and skip. Logged failures need not reject an artifact; skip performs no signature verification.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the Notary strict label establish the effective verification policy?

Custom overrides can change authenticity, timestamp, expiry and revocation validation. Integrity cannot be overridden, and skip cannot be customised.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a global Notary policy govern every artifact repository?

For OCI artifacts, an exact repository policy takes precedence over a global rule. Without either match verification must fail; URIs must be fully qualified.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Notary trustedIdentities=* select a particular builder?

The wildcard trusts signing identities issued by configured trusted authorities. It does not select one expected certificate subject.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Notary artifact success validate every attached signature?

The pinned OCI workflow can skip failed candidates and accept a policy-valid signature with matching signed digest and requested annotations.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Notation policy import merely add a rule to existing configuration?

The documented import example replaces the active trust policy after confirmation. Showing the policy afterwards confirms the resulting configuration.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Where does Service Bus retain a message that cannot be forwarded?

For failed auto-forward or send-via transfer, the message is placed in the transfer dead-letter queue of the source entity that forwarded it, not the intended destination.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does OCI cross-repository mount HTTP 202 mean the blob is available?

A successful mount returns 201 Created. If mounting is unsupported or cannot be performed, 202 indicates an upload session has begun and the client may upload the blob.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Graph delta deleted-folder marker immediately remove the local folder?

Microsoft requires a local folder to be empty after all changes are synchronised before deleting it locally. A folder marker alone is not enough to decide what remains below it.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does renaming a Graph folder emit updated paths for all descendants?

Graph documents that a folder rename does not return every descendant in delta, and parentReference.path is omitted. Clients should track items by identifier rather than infer unchanged paths from absent descendant rows.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an empty Graph sharing facet mean the item inherits its parent permissions?

With hierarchicalsharing, Graph distinguishes inheritance from unique items with no sharing links using an empty sharing facet. The root of an unshared permission hierarchy can also carry that empty facet.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a non-owner Graph permissions response inventory every sharing grant?

Graph returns all sharing permissions to an item owner or co-owner, but only permissions applicable to a non-owner caller. A successful non-owner response is therefore a caller-scoped view.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Where should a Graph sharing review locate the source of an inherited grant?

Graph sharing permissions can be direct or inherited. The inheritedFrom property identifies the ancestor supplying an inherited permission, so the child list alone is not a statement that the grant originated on that child.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can createLink remove existing permissions when a file is first shared?

Graph documents retainInheritedPermissions=true by default. On first sharing, false removes existing permissions; SharePoint Embedded does not support this parameter. The serialized request matters when reviewing a proposed sharing operation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does every successful Graph createLink response prove a new sharing link was created?

Graph returns an existing link of the requested type for the calling application when one exists. It distinguishes a newly created link with HTTP 201 from an existing link returned with HTTP 200.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does omitting scope from Graph createLink guarantee a restricted audience?

When scope is omitted, Graph creates the organisation default link type. An anonymous link permits access without sign-in where administrator policy allows it; an organisation link has a different audience.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does one Graph message delta stream cover the whole mailbox?

Message delta tracking is per folder. Microsoft requires each folder in a hierarchy to be tracked individually; completing one folder stream is not mailbox-wide coverage.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a filtered Graph message delta request establish complete coverage of a large folder?

The documented receivedDateTime filters on message delta return at most 5,000 messages. A time filter changes the coverage boundary and cannot be assumed to enumerate every matching message in a larger folder.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a created-only Graph message delta also prove that existing messages stayed unchanged?

Graph supports created, updated or deleted changeType selections. Selecting one change type limits the observed changes; the service carries the selection into continuation links.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Graph considering a webhook delivered prove the business action completed?

Graph treats a timely 2xx response as delivery. It recommends queueing a notification and returning 202 when processing cannot finish promptly, separating HTTP acceptance from subsequent application work.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a responsive Graph subscription still have an unrecoverable webhook gap?

Graph can delay slow endpoints and drop notifications for endpoints exceeding its documented timeout thresholds. Dropped notifications cannot be recovered through notification delivery, so restoring responsiveness does not prove gap closure.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does restrictToMyDrive include every file visible to a Drive user?

Drive documents that restrictToMyDrive omits changes outside the My Drive hierarchy, including application-data files and shared files not added to My Drive. Caller visibility and selected change coverage are different.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Drive return file details for an item that has left the change corpus?

includeCorpusRemovals can include the file resource when it remains accessible despite leaving the change list. There may be no further change entries for that file in the selected corpus.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Drive client advance its durable change checkpoint while nextPageToken remains?

A populated nextPageToken means the change list can be incomplete. Google documents following continuation pages and retaining newStartPageToken for later polling after reaching the current end.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a gap in Drive notification message numbers prove a missing event?

Drive notification numbers increase within a channel but are not sequential. A numerical gap by itself cannot establish how many changes or notifications were lost.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does renewing a Drive notification channel preserve one continuous delivery identity?

Drive channels do not renew automatically. Replacement requires a new unique channel identifier, and the old and new channels can overlap while both remain active.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the first Drive sync notification prove that existing files were synchronised?

The sync notification signals channel startup, and can arrive before the watch response. It is not an inventory transfer or proof that the client has processed existing content.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a working My Drive changes integration automatically include shared drives?

Shared-drive changes require the documented support and inclusion settings. If shared-drive support is false, shared drives and their files are excluded from the response.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the Slack event authorizations field enumerate every installation that can see an event?

Slack event envelopes provide a limited authorization view. The documented apps.event.authorizations.list method retrieves the full authorization list when that inventory is needed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does standard Slack retry handling guarantee delivery of substantially delayed events?

Slack describes Events API delivery as best effort. By default it does not attempt events more than two hours late; the optional Delayed Events setting changes late-delivery handling and adds hourly retries after the initial attempts.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does enabling a Slack event subscription guarantee every configured event type is delivered?

Slack states that granted OAuth scopes determine which subscribed event types an installation receives. Configuring a subscription without the required granted scopes does not supply that event class.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does one Slack 429 response require stopping every workspace and API method?

Slack applies the documented Retry-After interval to the affected method for tokens of the app in that workspace. Other methods and the same method in other workspaces are not restricted by that specific response.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do published Slack rate tiers apply unchanged when a client avoids cursor pagination?

For methods supporting cursor pagination, Slack applies the stated tier when pagination is used. Requests that avoid pagination receive stricter limits, so a tier label alone does not establish achievable inventory throughput.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a recorded LangSmith LLM trace necessarily have a calculable cost?

Automatic cost calculation needs token counts, model and provider identification, and applicable model pricing. A recorded trace alone does not establish that those inputs were supplied.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can the displayed model label alone establish which LangSmith pricing rule was applied?

LangSmith model pricing uses a model-name match pattern and optional provider match. Reviewing the actual metadata and matching entry is necessary when custom names or gateways change model labels.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a generic per-token LangSmith price map cover every custom charging formula?

LangSmith documents built-in support for specified Gemini stepwise pricing. For other non-linear models it directs clients to calculate cost and send the result in usage metadata.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does adding a thread identifier only to the parent preserve all child cost totals?

LangSmith requires thread metadata on child runs as well as the parent for thread filtering and token or cost aggregation. Unlabelled children can be omitted from that thread view.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does reaching a LangSmith evaluator budget stop the underlying agent?

The documented cap pauses evaluation on the affected project or dataset. The agent and its trace continue; the missing scores do not establish that application execution stopped.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is an evaluator weekly cap an exact ceiling on every in-flight charge?

LangSmith records spend after each evaluator run finishes. Concurrent in-flight runs can therefore push the final amount above the effective cap before new evaluations are paused.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Will LangSmith automatically score runs skipped while an evaluator was budget-paused?

After a reset or increased limit, evaluation resumes on new runs. The documentation states that skipped runs are not backfilled, leaving a distinct assessment coverage gap.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does changing the organisation evaluator limit update every attachment?

Changing the organisation default updates attachments that inherit it. Custom per-project or per-dataset overrides remain in place; clearing the default removes caps only from inheriting attachments.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does LangSmith evaluator spend independently verify the provider invoice?

Evaluator spend is calculated from configured model prices, not provider billing. Discounts, custom contracts and unconfigured variants can produce differences from an invoice.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does LANGSMITH_TRACING=true prove every invocation was recorded?

Scoped tracing_context settings take precedence over global configuration and environment variables. Nested contexts use the innermost setting, so tracing can be disabled for selected invocations despite a global enable flag.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a LangSmith SDK sampling setting control every ingestion path?

The documented sampling configuration applies to the SDK or LangChain, not direct API logging. Individual clients can also have different rates, so one environment value does not describe every producer.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does changing a Langfuse model price necessarily change an explicitly supplied cost?

Langfuse distinguishes ingested usage or cost from inferred values. When both are available, ingested values take priority, so the recorded amount may reflect the supplied payload rather than model-price inference.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can cached input tokens be counted both within input and in a separate Langfuse usage bucket?

Langfuse treats usage keys as non-overlapping buckets. Overlapping counts can double-count usage and inferred cost; directly ingested cost values are not recalculated by that overlap.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a custom Langfuse model definition override a maintained default price?

Langfuse matches model names using regular expressions and gives user-defined models priority over maintained definitions. A familiar model label does not establish which pricing definition supplied the estimate.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does updating a Langfuse pricing definition repair costs on older generations?

The documented model-definition changes apply to generations logged afterward. Updating a price is not evidence that historical amounts have been recalculated.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does every Langfuse observation type contribute native usage and cost?

Langfuse documents cost and usage on generation and embedding observations. Other observation types do not carry those fields, so a visible tool or workflow observation is not necessarily priced.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Langfuse masking sanitize the same spans sent to every other backend?

The Python mask_otel_spans hook affects the Langfuse client export. A separate OpenTelemetry exporter receives its own unmodified copy unless its path has separate masking.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a masking error cause Langfuse telemetry to disappear?

An exception or invalid overall masking result drops the export batch. An invalid span patch drops that span; invalid returned attribute values remove the affected attribute. These failure scopes differ.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the legacy Langfuse Python mask hook inspect final third-party OpenTelemetry attributes?

The legacy mask hook transforms data set through Langfuse SDK APIs at attribute creation. It does not inspect final raw OpenTelemetry attributes from third-party instrumentation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can mask_otel_spans redact every field of a Langfuse span?

The hook can change span attributes but not names, identifiers, parent relationships, resource attributes, events, links or instrumentation scope. Its configured presence is not whole-span sanitization.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can Python multi-project Langfuse routing isolate every third-party span by project?

The documented experimental routing uses a Langfuse public-key attribute. Third-party spans lacking it, if accepted by export filters, can be processed by all configured project processors.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does flushing a request-scoped Langfuse provider include spans that end later?

The documented request-scoped JS/TS pattern exports ended spans at shutdown. Observations ending after the request callback finishes are lost, including unfinished streaming or background work.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a request-scoped Langfuse routing provider also route global OpenTelemetry instrumentation?

Third-party libraries using the global tracer provider do not pass through the request routing provider. Integrations accepting an explicit tracer need the intended routing tracer supplied.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can shared background work be attributed to the wrong Langfuse project?

The documented JS/TS request-routing pattern warns that a shared queue can execute under whichever request context is active when it drains. Spans can then be routed to that request project.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does code outside a Langfuse request context fall back safely into the same project?

In the documented request-scoped pattern, spans started outside its context are dropped. Long-lived callbacks and stored observation handles can lose the request context unless correctly bound.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Where must an Entra agent identity obtain its authentication credentials?

The agent identity has no credentials of its own. Its blueprint holds credentials and acquires tokens on its behalf, subject to relevant consent. Review both objects and their credential relationship.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a multitenant Entra blueprint make one child identity valid across tenants?

No. Agent identities remain single-tenant. A multitenant blueprint can be installed elsewhere and create separate tenant-local identities; it does not make an existing child identity cross-tenant.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May an Entra agent user ID replace its agent identity ID in an audit?

The optional agent user account has a different identifier and a one-to-one relationship with its agent identity. Preserve the link and the identity used for each operation rather than collapsing identifiers.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does declaring an Entra resource inheritable grant its permissions to child agents?

No. Inheritance configuration and an actual permission grant are both required. Required resource access and inheritance are declarations; consent supplies authorization.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a blueprint's initial permission list describe all later inherited access?

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.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Entra child-agent permissions listing establish complete inherited scope?

No. Microsoft states inherited permissions are not shown on the agent identity in the admin center or Graph. They merge with direct grants at token issuance and are observable in token contents.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Entra sponsor restore an agent after disabling it?

Sponsors can disable or soft-delete an agent and change its sponsors, but cannot re-enable or restore it. Recovery needs an owner or administrator. Sponsorship does not confer all owner powers.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a dynamic-group membership change immediately authorize agent sponsor actions?

Microsoft documents up to 24 hours after a dynamic membership rule or user-property change before sponsorship authorization succeeds. Changed membership alone is insufficient evidence of effective sponsor authority.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a blueprint client ID receive a child agent's resource app-role assignment?

For an application-permission grant to the child agent, the documented assignment uses the agent identity service principal object ID as principalId, the resource service principal object ID as resourceId, and the selected appRoleId. Do not substitute the blueprint client ID. A separate grant to a blueprint for agent-user creation is a different operation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can administrator consent override Agent ID high-privilege restrictions?

The documented agent model blocks specified high-risk Graph permissions and privileged directory roles. Agents also cannot join role-assignable groups. Administrator consent is not a general override.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Entra agent identity policy also cover its agent-user and delegated-user tokens?

No. Delegated access, app-only agent identity access and agent-user access use different policy targets. A policy targeting the agent identity does not apply to its agent user account, or vice versa.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Entra Conditional Access govern an agent's direct API-key access?

API-key access bypasses Entra authentication and token issuance, so its Conditional Access policies do not apply to that path. Resource-side key controls need separate assessment.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Entra agent user account operate as an ordinary password-based user?

The account has restricted credentials tied to its parent agent identity and restricted interactive sign-in. It cannot receive ordinary passwords or passkeys merely because its tokens use a user identity type.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does disabling a blueprint affect only future agent provisioning?

No. Microsoft describes blueprint disabling as preventing new agent identities and blocking existing ones. Its scope is broader than disabling one agent.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Whose identity appears when an Entra blueprint provisions an agent?

The tenant blueprint principal is referenced by the blueprint token oid and audit records for blueprint operations. That provisioning actor differs from the child performing later resource work.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do Agent ID Developer and Administrator permit the same credential changes?

The creation guide permits Agent ID Developer to configure federated identity credentials. Adding a secret or certificate requires Agent ID Administrator. Credential type changes the required administrative authority.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an AgentCore callback accept consent from anyone opening its URL?

No. The application must match the originating user with the currently authenticated browser user before CompleteResourceTokenAuth. It supplies the session URI and identity from the active browser session, not a remote session cache.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an AgentCore vault token prove the provider still accepts it?

No. Provider-side revocation may be undetected by AgentCore. The documented forceAuthentication option clears stored refresh-token state and initiates fresh authentication; retrieval alone does not establish validity.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an AgentCore workload identity automatically isolate its credential provider?

No. The assigned IAM role controls provider access, with no extra workload-provider binding in the same account. Scope resource blocks to the intended ARNs. User-scoped OAuth retrieval still needs the relevant prior authorization.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does AgentCore OBO always transmit the same actor evidence?

No. RFC8693 mode supports an M2M token, an AWS IAM JWT, or no actor_token. NONE relies on the authorization server deriving actor identity from client authentication.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is an AgentCore user-ID header equivalent to a validated user JWT?

No. The header uses the user-ID token path and additionally requires InvokeAgentRuntimeForUser. The JWT path validates issuer, signature and expiry; AWS recommends it with a production identity provider.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can AgentCore use one OBO wire format for every identity provider?

No. AgentCore supports RFC8693 token exchange and JWT authorization-grant mode. Provider configuration determines the expected fields; Microsoft's preset adds requested_token_use=on_behalf_of unless overridden.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an enterprise ID-JAG directly serve as an MCP bearer access token?

In the optional Enterprise-Managed Authorization profile dated 2026-07-28, the enterprise IdP evaluates policy and issues an ID-JAG. The client then presents that intermediate grant to the resource authorization server, which validates it and issues the MCP access token. Corporate sign-in or the ID-JAG alone does not establish a usable resource token; profile support and both trust relationships need evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Which audience and resource identify an MCP enterprise grant?

In the optional pinned 2026-07-28 profile, the token-exchange audience is the resource authorization server's issuer identifier. The optional resource parameter, when supplied, identifies the MCP server. The profile requires the final access token to be restricted to the MCP server identified by the ID-JAG resource claim. Omission does not establish unrestricted access; this source does not resolve every omitted-resource deployment behavior.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does fetching MCP client metadata establish an acceptable redirect?

No. Checks include exact equality of document URL and client_id, required JSON fields, and matching the requested redirect against the document's list. A fetched page or familiar name is insufficient.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can MCP credentials carry over to another advertised authorization server?

Do not assume so. MCP 2026-07-28 requires separate registration state for each authorization server and association of credentials and tokens with the issuing server. An advertised alternative issuer does not establish that it accepts another issuer's credentials.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must an MCP scope challenge be a subset of advertised scopes?

No. MCP 2026-07-28 prohibits assuming a set relationship between challenged scopes and scopes_supported, and requires treating the challenge as authoritative for the current operation. For initial authorization it recommends using the challenge scope first; otherwise it recommends advertised scopes, omitting scope when scopes_supported is undefined. This does not itself grant consent.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can MCP assume authorization metadata exists only at the domain root?

No. July 2026 defines ordered OAuth and OpenID discovery candidates for issuers with paths. A root-only probe can miss a tenant issuer; returned issuer metadata still needs validation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the MCP client-credentials extension use dynamic registration?

The optional pinned 2026-07-28 client-credentials extension requires pre-registered client credentials, typically established out of band through administrative channels, and does not use Dynamic Client Registration in this flow. Adopted implementations retain baseline authorization requirements.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is the MCP client-authentication JWT itself the authorization grant?

The pinned specification uses grant_type=client_credentials with a JWT client_assertion for authentication. That differs from a JWT authorization grant. Record the actual grant type and authentication method.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can two providers in one workload pool map different identities to one principal?

Yes. Matching google.subject values across providers can collapse identities into one IAM principal and make them indistinguishable in audit logs. Google recommends one provider per pool to avoid this.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can user-editable attributes safely anchor workload federation access?

Google warns editable attributes can cause access loss or spoofing when mapped to IAM bindings. Use immutable identity attributes rather than values an external user can change.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can changing federation mappings alter access without editing IAM bindings?

Yes. A mapping edit can change which external identities match existing service-account bindings. Provider update authority therefore affects effective access even with unchanged bindings.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does account deletion retire a federation binding to a reusable name?

Not necessarily. Google recommends non-reusable attributes because a later account can inherit a reused value and match an old binding. Uniqueness must hold over time.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Claude SDK hook allow override a matching deny rule?

The captured SDK documentation evaluates deny rules after hooks. A matching deny prevents the call and skips canUseTool, even after hook allow or in bypassPermissions mode.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Claude SDK subagent independently weaken its parent permission mode?

In the captured documentation, subagents inherit parent plan, acceptEdits, auto or bypassPermissions modes. Under default or dontAsk parents, the configured subagent mode applies, except that Claude Code v2.1.267 and later do not apply a subagent bypassPermissions value; auto applies only where available to that subagent. Inherited bypassPermissions can itself confer broad autonomous access. Check the installed runtime and effective mode.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a canUseTool callback review every Claude SDK tool call?

No. The captured documentation says bypassPermissions or a bare-tool allowedTools entry can approve calls before canUseTool, subject to documented exceptions. The TypeScript SDK warns about these configurations with CLAUDE_SDK_CAN_USE_TOOL_SHADOWED; the warning does not block calls or change options. For checks required on every tool call, the documentation directs developers to PreToolUse hooks.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does creating an Entra agent user authorize its agent identity to read a mailbox?

No. The documented agent-user flow separately requires authorization for the agent identity to act on the agent user's behalf before requesting its tokens. The Principal-scoped Mail.Read example binds clientId to the agent identity service principal, principalId to the agent-user object, and resourceId to the Microsoft Graph service principal. Account creation alone does not establish that grant, mailbox provisioning or usable resource access.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an A2A client resume a completed task by sending it another message?

The captured specification rejects messages to completed, failed, canceled or rejected tasks with UnsupportedOperationError. A task identifier does not reopen a terminal lifecycle. A separate follow-up must use a supported new-task or conversation path.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May an A2A follow-up attach an existing task to a different conversation context?

The captured specification requires deriving contextId from the task when only taskId is supplied and rejecting a message whose taskId and contextId refer to different contexts. Shared conversation intent is not sufficient to relabel an existing task.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does reusing an A2A messageId guarantee that delegated work will not run twice?

Send Message operations may be idempotent and an agent may use messageId to detect duplicates. The captured specification does not require universal deduplication of Send Message. Retrying an uncertain send therefore needs the receiving agent's actual deduplication and outcome evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does every A2A streaming reply create a task that can later be polled?

A message-only stream contains exactly one Message and then closes, with no task tracking or updates. A task-lifecycle stream starts with a Task and may then carry updates. The client must distinguish the returned shape before scheduling task retrieval.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a blocking A2A Send Message response prove the delegated task finished?

Section 3.2.2 of the captured A2A specification says returnImmediately false or unset waits for a terminal or interrupted state, including INPUT_REQUIRED or AUTH_REQUIRED. Its general Send Message paragraph separately says the operation returns immediately. This source tension leaves actual timing to be checked against the implemented version; neither paragraph supports treating every returned Task as completed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an A2A client choose taskId as the identifier for creating new delegated work?

Task IDs are server-generated. A taskId in a message must reference an existing task, and an unknown one requires TaskNotFoundError. Client-generated task IDs for task creation are not supported in the captured specification.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Must a repeated A2A cancellation return the same task object to be idempotent?

The captured specification makes Cancel Task idempotent but permits TaskNotFoundError on a duplicate cancellation after the task was canceled and purged. Cancellation itself can fail for a noncancelable state. Preserve earlier responses and reconcile outcome rather than treating every later not-found as evidence of failed cancellation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does loading an ADK artifact by filename recover the exact version previously reviewed?

Loading an ADK artifact without a version retrieves the latest version; specifying version N selects that version, and saving returns the assigned version. Retain the scoped filename and version for the exact reviewed output. Separately check the configured backend: the guide distinguishes temporary in-memory storage from persistent services such as GCS, so the version number alone does not establish restart durability.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is an ADK artifact named user:report.pdf isolated to the session that created it?

The user: filename prefix scopes an artifact to app_name and user_id, allowing access or updates across that user's sessions in the app. A plain filename is session-scoped. The prefix changes the evidence-sharing boundary and is not merely a display name.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an ADK artifact_delta event contain the generated file needed for an acceptance review?

The documented Python save example puts the artifact filename and assigned version in event.actions.artifact_delta. Artifact content is loaded separately through the artifact service. This event reference alone does not establish that the recipient retrieved or retained those bytes; other ADK languages can expose different API names.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does directly changing a fetched ADK Session.state reliably persist an auditable change?

The documentation distinguishes Context.state updates, which the framework tracks, from direct mutation of a Session retrieved from SessionService. The latter bypasses event tracking and can lose data. State updates should accompany an appended event.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is ADK temp: state a private durable store for each delegated sub-agent?

Temporary state is scoped to the invocation and discarded when it completes. Parent and sub-agents sharing InvocationContext share the invocation ID and temp: state. It is neither a durable cross-invocation checkpoint nor automatically isolated per sub-agent.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does rewinding an ADK session restore shared user state and external side effects?

The documented rewind restores only session-level state and artifacts. App-level and user-level resources are not restored, and external systems require separate restoration by the operator. A session rewind cannot establish that a purchase or shared resource change was undone.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an ADK session rewind safely run while the session or its artifacts are still changing?

State updates, artifact updates and event persistence are not one atomic transaction in the documented rewind. The guide advises avoiding active-session rewinds and concurrent artifact manipulation to prevent inconsistencies.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can ADK Resume repeat a tool whose remote side effect already occurred?

The resume guide reinstates successfully returned tool results and reruns an interrupted tool request. It explicitly describes at-least-once tool execution and possible repeat execution on resume. Side-effecting tools such as purchases need their own duplicate-prevention checks.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May an operator add or remove ADK agents before resuming a stopped workflow?

The captured ADK Resume guide does not support changing a stopped workflow before resumption, such as adding or removing agents. Resume selects the earlier invocation ID with the applicable app, user and session through the API server or Runner path; the guide says ADK Web and CLI resume are not currently supported. Retain the stopped invocation and workflow definition rather than assuming a fresh request or changed graph resumes the same work.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does wrapping a function in ADK LongRunningFunctionTool execute the long job for me?

LongRunningFunctionTool manages the interaction with long-running work rather than performing the lengthy task itself; the guide recommends a separate server for substantial work. The runner pauses and the client supplies intermediate or final responses. In the Python example, the function-call ID correlates its response while the external ticket ID is tracked separately. Neither an interaction handle nor a ticket reference proves worker completion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does enabling ADK resumability automatically give a custom agent correct restart checkpoints?

The guide requires custom agents to define preservable steps and state, emit checkpoints for completed steps and mark overall completion with end_of_agent. Enabling resumability alone does not establish that a custom workflow implemented those checkpoints correctly.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a failed input guardrail prove no OpenAI Agents SDK tool already ran?

Input guardrails run in parallel with the agent by default. The documentation says a tripwire can fire after token use or tool execution. Blocking mode runs the guardrail first and prevents agent execution if it trips. A failed parallel check is not evidence that earlier effects were avoided.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an output guardrail tripwire leave the same session evidence as a guardrail exception?

The captured Python SDK guide distinguishes output-tripwire rejection from a guardrail exception. A tripwire asks the configured session to retain replay-valid completed tool context while excluding rejected final output; rejected terminal-tool payloads can be replaced with a placeholder, or the response suffix discarded when safe sanitization is unavailable. A guardrail exception leaves the verdict unknown and requests persistence of completed final-turn items; a session-write error takes precedence. Retained call metadata can still contain arguments.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does stopping the event consumer stop an OpenAI Agents SDK streaming run?

The Python SDK background run and event consumer have separate lifetimes. Breaking the event loop or failing while handling an event can leave model and tool calls running; closing the iterator alone waits rather than requests cancellation. Cancellation while awaiting the next event does request run cancellation. The guide recommends explicit cancellation and draining cleanup when one consumer owns an early exit; none of this establishes rollback of earlier effects.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does the last visible token mean an OpenAI Agents SDK streamed run is fully complete?

The guide says completion requires the stream_events iterator to finish. Session persistence, approval bookkeeping or history compaction can continue after the final visible token. Inspect the final run state only after the iterator drains.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should a new user turn be appended immediately after an OpenAI after_turn cancellation?

The captured Python SDK guide says after_turn cancellation lets the current turn finish. When manually continuing normalized input after a tool turn, rerun last_agent for the unfinished existing user turn. If new input arrives before that run resumes, convert the drained result to state, stage input and resume. Tool-approval interruptions also require draining and inspecting interruptions before resuming state; a stopped tool turn is not automatically a fresh completed user turn.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does advertising MCP Tasks once force all later tool calls to return task handles?

The optional 2026-07-28 Tasks extension requires the capability on each request. A server must not return CreateTaskResult without it, even after earlier declarations. With support declared, the server chooses per request between a direct result and a task; clients must handle both.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May a compliant MCP server return a task handle before tasks/get can find it?

The optional 2026-07-28 Tasks extension prohibits returning CreateTaskResult before durable creation such that tasks/get resolves. Eventually consistent implementations must wait for consistency before replying. This is a specification requirement, not evidence that a buyer's server meets it.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an MCP task marked completed still contain an unsuccessful tool result?

In the optional 2026-07-28 Tasks extension, completed includes tool results with isError true. Failed is reserved for execution JSON-RPC errors. A consumer must inspect the embedded original result as well as task status before accepting tool or business success.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May an MCP server reuse an inputRequests key for a different question later in a task?

The optional 2026-07-28 Tasks extension requires input request keys to stay unique over the task lifetime and prohibits reusing a satisfied key for a later request. Clients should deduplicate repeated keys across polls. Stable keys bind responses to the intended request rather than a later substituted question.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful tasks/update response prove the MCP task advanced or used my response?

The optional 2026-07-28 Tasks extension permits a tasks/update acknowledgement before processing is reflected in observable state. It recommends ignoring responses for unknown or already-satisfied input keys. Clients should continue observing the task after an update; the acknowledgement alone does not establish a particular transition or completion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does possessing an MCP task ID authorize later retrieval or input updates?

The optional 2026-07-28 Tasks extension requires authentication and authorization checks on each task-related request. Task IDs need protection against guessing, and input requests retain the ordinary elicitation or sampling trust model. A task handle is not a higher-trust channel or an access grant.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does requesting MCP task notifications establish that every requested task ID was subscribed?

In the optional 2026-07-28 Tasks extension, the acknowledgement lists the task IDs the server agreed to notify, if any. Notifications carry the complete current DetailedTask and final result, so clients may continue polling but need not. Compare the acknowledgement with requested IDs before relying on notification coverage; neither subscription nor a current-state notification supplies a promised replay of every historical transition.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Which Mcp-Name value should an HTTP client send for later MCP task operations?

For tasks/get, tasks/update and tasks/cancel over Streamable HTTP, the optional 2026-07-28 extension requires Mcp-Name equal to params.taskId. Mcp-Method remains the JSON-RPC method. This enables intermediaries to route to the instance holding task state; it does not replace authorization.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent dispute a Stripe Issuing authorization before the merchant captures it?

Stripe's Issuing guide says an authorization cannot be disputed. A dispute can be filed after authorization completes and the acquiring business captures the transaction; reversal of an authorization is at the acquiring business's discretion. Identify the captured transaction before choosing dispute recovery.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an automated Stripe Issuing dispute submit now and add evidence later?

Stripe permits submitting a dispute only once. After submission, the dispute cannot be edited or supplemented with further evidence. Incomplete or invalid submissions can lose, so the review point is before submission rather than after creation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does saving or creating a Stripe Issuing dispute prove it was sent to the card network?

The documented workflow creates a dispute on Save and submits it on Submit; the API also separates creation and submission. Evidence fields may be absent during creation while evidence is collected. A created dispute object is therefore not proof of a submitted network challenge.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an available Stripe Issuing provisional credit establish a won dispute and final recovery?

For the documented eligible UK and EU Issuing unauthorized or fraud flows, provisional credit can be spent while the dispute remains open. Stripe claws it back after resolving the dispute; a win produces a new credit for the amount recovered. A clawback can create a negative balance requiring replenishment. Reconcile provisional credit, reversal and any final credit separately instead of treating available funds as final recovery.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should an Issuing dispute always claim the original full transaction amount?

The creation guide defaults the Dispute Amount to the full transaction but directs users to account for refunds and cases where only a partial amount should be disputed. The amount to challenge must be reconciled against the actual unresolved portion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent classify a disputed purchase as a consumer dispute without a merchant resolution attempt?

For consumer reasons such as not received, canceled or not as described, Stripe's guide requires the cardholder to attempt resolution with the business and include documentation of that attempt. This is a specific submission evidence condition, not proof of fraud or a guaranteed recovery.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does approving read-only Microsoft Agent Framework skill tools also approve script execution?

For the documented Python SkillsProvider with ToolApprovalMiddleware, the read_only_tools_auto_approval_rule covers load_skill and read_skill_resource while run_skill_script still requires approval. The all_tools_auto_approval_rule includes script execution.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a downloaded Microsoft Agent Framework MCP skill archive execute its bundled scripts?

The documented archive-type MCP skill path exposes extracted resources but does not execute bundled scripts. File-based scripts and remote archive resources have different execution treatment.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does successful MCP skill discovery prove that every archive resource was extracted?

Microsoft documents archive extension, depth, count, download and uncompressed-size controls. In its described extraction path, colliding archive members keep the first content and later collisions are skipped with a warning.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does registering an Agent Framework subprocess skill runner establish a sandbox?

Microsoft marks the example subprocess runners as demonstrations and recommends separate isolation, resource limits, input validation and audit controls for production.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a custom Agent Framework SKILL.md field establish an enforced review policy?

The documented parser rejects certain malformed recognised fields but ignores unknown top-level fields. The allowed-tools field is experimental and support can vary across implementations.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Which OpenAI Responses skill version is selected when no explicit version is supplied?

The documented Responses Skills API uses default_version for an omitted version and separately tracks latest_version. An explicit version or latest reference has a different update boundary.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an OpenAI skill upload response prove that the new version can already be attached?

The guide says a newly uploaded version can briefly return 404. It instructs callers to retrieve the version with bounded backoff before attachment and use the returned version string.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a hosted OpenAI skill_reference identify the skill used by local shell execution?

The documented hosted shell accepts uploaded skill_reference attachments; local shell instead uses skill files at paths in the runtime controlled by the application.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does registering an Agents API capability directory limit all filesystem access to that directory?

Capability directories identify existing absolute, unique sandbox paths for skill discovery; the guide disallows dot path segments and limits registration to 32 directories. Discovery paths are not documented as a general filesystem permission boundary.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does putting a credential in a secrets manager prevent a skill from reading it at runtime?

OpenAI distinguishes credentials kept outside execution and supplied by a trusted proxy from secrets injected into the environment, which remain exposed to generated code. Its executor environment key is also readable inside that environment.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does enabling Claude Enterprise skill scanning cover API uploads and existing skills?

The captured guidance limits scanning to eligible uploads and edits in claude.ai or Cowork after the setting is enabled. It excludes Skills API uploads and skills already present when scanning was enabled. The guide also excludes organisations with certain data-handling configurations, including CMEK, ZDR or HIPAA readiness.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a usable Claude skill prove that it passed scanning without an exception?

The guide says pending or failed scans block use, warning results can remain usable behind a caution notice, and authorised owners or library-managing roles can allow some failed skills.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an unpinned Claude Skills API reference remain tied to a previously approved upload?

The captured enterprise guidance says omitted versions use the latest version and workspace uploads can therefore change what production agents run. It recommends explicit version pinning and evaluation before promotion.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a skill's successful isolated demonstration establish safe selection alongside existing skills?

The enterprise guide calls for isolated and coexistence evaluations covering triggering accuracy, output quality and regressions across the active skill set, separately from security review.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can malformed Claude Code skill frontmatter fail open to default invocation behaviour?

The captured Claude Code guide says unrecognised fields are ignored, frontmatter is read only when the opening marker is the first line, and unparseable YAML still loads the skill with no fields set.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does user-invocable false prevent Claude from invoking a sensitive skill?

The guide distinguishes disable-model-invocation true, which prevents autonomous invocation, from user-invocable false, which removes user invocation while allowing Claude to invoke the skill.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a local Claude Code skill run a shell command while constructing its prompt?

The documented exclamation/backtick syntax executes commands before the skill content is sent to Claude and substitutes their output. Synced skills have surface- and version-specific restrictions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can the same synced Claude skill have identical execution behaviour in cloud and local sessions?

The captured guide distinguishes cloud, Cowork and other local sessions for shell preprocessing, file references and substitutions, with relevant restrictions requiring Claude Code v2.1.228 or later.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does approving a plugin's visible skill cover its hooks and MCP servers?

Claude Code documents plugins containing skills, agents, lifecycle hooks, JavaScript hook modules and MCP servers. These components can expose capabilities beyond the visible slash command.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does enabling a Claude Code plugin in committed project settings install identical local code for every collaborator?

The guide distinguishes project enablement from each collaborator's local installation, while cloud sessions do not load local settings in the same way.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can one OpenAI skill version be retired without changing the default or remaining skill identity?

The Responses Skills guide says the default version cannot be deleted until another default is selected, deleting the last version deletes the skill, and deleting a skill removes all versions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an AgentCore namespace IAM condition omit its leading or trailing slash?

AgentCore normalises namespaces with leading and trailing slashes. The guide says an IAM condition lacking these does not match the namespace on which the service acts.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does accepting an AgentCore event prove all intended tenant-scoped extraction ran?

AWS states that when CreateEvent omits a custom namespace variable referenced by a strategy template, extraction is not initiated for that strategy even though the event succeeds and persists in short-term memory. NamespaceResolutionFailure metrics identify the skipped strategy.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does UpdateMemory append namespace keys while retaining the previous set?

The documented namespaceKeys update replaces the entire set. The guide requires preserving existing keys and rejects removing a key still used by a strategy template.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a configured memory age prove AgentCore long-term records expire automatically?

The reviewed AWS lifecycle design implements timestamp-filtered pruning in a separate workflow and states that AgentCore memory lacks a built-in auto-delete TTL in that design context.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The reviewed beta documentation says raw messages are stored verbatim alongside extracted memories and are also searched during recall.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a newer Cloudflare memory fact replace and erase the previous fact?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta documentation describes facts and instructions being superseded by topic key while retaining old versions; recall preferentially surfaces the latest version.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Cloudflare Agent Memory session identifier alone define a tenant boundary?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented hierarchy separates namespaces and profiles, with sessions scoped to a profile and the same session ID permitted in different profiles. Recall is described as confined to the selected profile.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does ending a Cloudflare Agent Memory session delete its task memories?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented task class is session-scoped and deprioritised after the session ends. Deprioritisation describes retrieval treatment rather than an asserted deletion operation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does deleting one Cloudflare memory establish deletion of its whole profile?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API distinguishes namespace, profile, session and individual-memory deletion. Its individual-memory description removes that memory and source messages linked to it, rather than asserting complete profile erasure.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does retrying Cloudflare memory ingestion always preserve the same message identity?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta design derives message IDs from content and session and can derive an omitted session ID from the conversation. Its deduplication therefore depends on those inputs.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API provides separate conversation-ingestion and direct-memory operations, allowing an application to supply a memory rather than relying only on extracted conversation content.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does telling Mem0 a corrected fact automatically remove the earlier one?

The captured Mem0 documentation describes extraction as additive and recommends explicit update or delete for correction/removal; new information can be stored without rewriting an old fact.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Mem0 user wildcard be treated as a complete project erasure?

The current documentation distinguishes scoped delete_all arguments, rejects missing/blank identifiers in SDKs, and requires all four entity filters set to wildcards for its described full-project wipe.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Mem0 immutable memory be corrected with an ordinary update?

Mem0 documents immutable memories as requiring delete and re-add rather than update. Managed and OSS interfaces report the rejected update differently.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is a Mem0 vector-store export a complete memory custody inventory?

The reviewed architecture separates facts/metadata in SQL, embeddings in a vector database and extracted entities in an entity store; managed and OSS operation differs.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Mem0 metadata-only update alter expiry without changing memory text?

The documented OSS update accepts metadata and/or expiration changes while retaining text, and explicitly allows clearing expiration with None/null.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does removing LangGraph thread state cover its cross-thread memories?

LangGraph documents checkpointers for thread-scoped graph snapshots and stores for separate cross-thread application data. Applications can use both.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts?

Microsoft distinguishes agent-written local file memory from automatically extracted managed Foundry memory. The two can be used together and have different storage and scope.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset?

The guide binds mounted skills and container files to the hosted container lifecycle, while separately describing uploaded skill versions and their deletion rules.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an agent response establish that its background memory write has finished?

The LangGraph guide distinguishes memory writes in the request path from background/asynchronous updates with different timing and complexity.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a broad exception handler around LangGraph interrupt preserve the approval pause?

LangGraph documents interrupt as a special exception used to suspend execution. A broad try/except can intercept it before the runtime receives the pause signal; the guide separates interrupts from error handling or catches specific error types.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can reordered LangGraph interrupts reuse the original approval values safely?

Within a LangGraph node, saved resume values are matched to interrupt calls by position in the task-specific list. The documented rule requires a consistent call order and warns against conditional skipping or nondeterministic loops.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a LangGraph Functional API response necessarily equal the state saved for the next invocation?

LangGraph entrypoint.final can return one value while saving another in the checkpoint. The saved value supplies previous on a later invocation; recording only the caller-visible response can omit that distinct continuation state.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does LangGraph update_state roll back the original execution history?

The LangGraph time-travel guide states that update_state creates a new checkpoint branching from the chosen point. The original execution history remains intact; the operation is a fork rather than a rollback.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a LangGraph checkpoint attributed through as_node prove that node actually ran?

For update_state, LangGraph applies the selected node writers and records that node as the update producer; execution continues at its successors. The guide explicitly allows choosing a later as_node to skip nodes.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does updating a LangGraph state field always replace its previous value?

LangGraph state updates use the configured field reducer. An additive reducer can merge new values into accumulated state; the documented Overwrite wrapper bypasses the reducer when explicit replacement is intended.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a parent LangGraph checkpoint replay only the second approval inside a default subgraph?

The time-travel guide treats a default subgraph as one parent-level super-step. Replaying from before it runs the subgraph from the start; its own checkpointer provides internal checkpoint history for finer replay selection.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a LangGraph node timeout prove that the node made no external change?

LangGraph documents per-attempt timeouts for async nodes and states that timed-out attempts do not commit buffered state writes or child-task scheduling. A configured retry may start another attempt with a fresh timeout.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can ongoing MCP progress notifications justify waiting indefinitely for a request?

MCP revision 2026-07-28 permits resetting a request timeout on progress notifications but recommends an enforced maximum timeout regardless of progress. It also recommends configurable per-request timeouts.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Mem0 memory-history response prove which exact source sentence supports each stored fact?

The Mem0 Platform history schema describes entries for a memory ID, conversation input with roles and content, old and new memory text, event type and timestamps. It describes conversation-level change context, not a guaranteed per-fact source-span mapping.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful Mem0 OSS search prove every provenance metadata filter was applied?

Mem0 OSS documents different metadata-filter support across vector stores. Some unsupported operators are ignored or reduced to equality, and the reviewed Weaviate adapter table limits filtering to exact user, agent and run identifiers.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a high Mem0 OSS search score establish that a remembered statement is factually reliable?

Mem0 documents OSS score_details as a breakdown of semantic similarity, normalized BM25, entity boost, combined score and filtering threshold. The optional explain flag exposes how a result ranked.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is the latest add payload the complete source context for a new Mem0 Platform memory?

Mem0 Platform documents automatic use of earlier messages sharing the relevant user and optional run identifiers when extracting from newly submitted turns. The latest payload can therefore be only part of the extraction context.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does storing a fact through both raw and inferred Mem0 add paths produce independent corroborating evidence?

Mem0 documents that infer=False stores the supplied payload without inference and can admit duplicates. Adding the same content later with infer=True can create a second memory.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Claude SDK session reader prove that every parallel tool call was captured?

The Python SDK changelog for 0.2.170 documents a fix to get_session_messages and get_session_messages_from_store: earlier traversal could retain only one branch of a parallel-tool turn. The fix recovers sibling calls and results. This is a documented reader correction, not proof that a particular stored transcript is complete; it does not by itself qualify separate subagent readers.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Claude SDK subagent transcript identify the parent action that spawned it?

Python SDK 0.2.140 documents recovery of parent_tool_use_id from subagent metadata. The pinned SessionMessage documentation links it to the parent Agent tool-use block, with None when metadata is unavailable. parent_agent_id identifies a spawning subagent, but None can mean either the main session or unavailable metadata. Top-level session readers return None for these fields.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Is the tool output seen by the Claude model necessarily the original tool result?

The pinned Python SDK PostToolUseHookSpecificOutput documents updatedToolOutput as a replacement before the result reaches the model. For built-in tools its shape must match the tool output schema; a mismatch is rejected and the original output is retained. The 0.1.74 changelog introduced this option beyond MCP-only output replacement.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does resuming a Claude SessionStore transcript prove the original permission and hook configuration is still effective?

The Python SDK 0.2.137 changelog documents copying settings.json and cowork_settings.json into the temporary configuration directory on SessionStore resume to preserve apiKeyHelper authentication, user hooks, environment variables and permissions. It also records an earlier apiKeyHelper-only authentication failure. This specific fix does not attest that a buyer resumed with the same effective configuration.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can one Claude SDK hook reliably gate another hook registered for the same event?

The pinned Python SDK hooks documentation states that multiple matchers for the same event dispatch concurrently. Each hook should be independent; applications must not rely on one callback finishing before another starts. The changelog records this as a documentation clarification, not a new sequencing guarantee or runtime change.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does passing mcp_servers alone establish the entire Claude SDK MCP server inventory?

The pinned Python SDK documents strict_mcp_config=False by default. Setting it to True limits the CLI to servers passed through mcp_servers and ignores other configurations it would otherwise load, including project, user/global and plugin-provided servers. This controls the configuration source set; it does not verify server identity, tool safety or effective permissions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Claude query result prove background subagent control traffic has finished?

The Python SDK 0.2.160 changelog documents a query() fix for hooks, can_use_tool and SDK MCP servers: stdin stays open until the CLI reports idle through session_state_changed instead of closing too early around background subagent completion. The wait has a configurable ceiling, default ten minutes. Older CLIs without state events retain close-at-first-result behaviour.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can refreshing an MCP access token authorise scopes that were never granted?

RFC 6749 section 6 prohibits a refresh request from including scopes not originally granted by the resource owner. MCP 2026-07-28 describes increased-scope reauthorisation after insufficient_scope, rather than treating token renewal as new authority. A refreshed token can renew existing access; possession or successful refresh alone does not establish a grant for newly challenged scopes.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should an MCP client request only the newest challenged scope during reauthorisation?

MCP 2026-07-28 describes computing the union of the client's previously requested scope set and the current challenge before reauthorisation. It also recommends including challenged scopes alongside previously granted ones to avoid losing permissions for other operations. This is request-set continuity, not evidence that the authorisation server granted the union.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

How long should an MCP client keep retrying after repeated insufficient_scope challenges?

MCP 2026-07-28 describes retrying the original request with new authorisation only a few times before treating it as a permanent authorisation failure. It recommends retry limits and tracking scope-upgrade attempts for the same resource and operation. The specification does not supply one universal numeric retry count.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Agent Framework approval response authorise a call absent from the current session?

For the documented Python default, approval must match a pending request in the same AgentSession. Unbound responses are ignored with a warning. Disabling approval-response binding restores unbound behaviour and requires equivalent application-side validation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Agent Framework approval remain valid after middleware changes the tool arguments?

The Python guidance requires replacement approval for changed values only when JSON serialization and revalidation preserve those values exactly. Otherwise invocation fails with MiddlewareFailure; the earlier approval is not reused.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a replacement Agent Framework tool inherit a saved approval through its name?

The Python harness stores standing approvals in AgentSession, not on a particular agent or tool instance. A replacement with the same name, including an MCP tool, can match a saved tool-wide or argument-specific rule.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does disabling Agent Framework harness auto-approval remove a tool approval requirement?

In the documented Python harness, disable_tool_auto_approval removes its approval middleware but does not change the tool approval_mode. The ordinary user_input_requests flow still applies to approval-required tools.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Agent Framework autonomous loop treat a pending tool approval as another iteration?

The Python AgentLoopMiddleware returns pending approval requests before evaluating its continuation predicate. It does not install approval handling itself. The host must resolve approval through the normal flow before continuing.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Agent Framework restricted checkpoint deserialization make an untrusted checkpoint safe?

Microsoft treats checkpoint storage as trusted private infrastructure. Restricted unpickling and allowed types do not make untrusted pickle data safe; permitted classes can carry reconstruction behaviour.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does registering an Agent Framework checkpoint type affect only the current storage instance?

register_checkpoint_type expands decoding permissions across the Python process, including existing storage instances. allowed_checkpoint_types instead applies to its receiving store or provider. Both extend the restricted deserializer.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Agent Framework get_latest prove it considered every checkpoint file on disk?

FileCheckpointStorage listings and get_latest skip malformed or undecodable files using the decoding path. Its save operation also refuses data that the same configured instance cannot restore.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful Agent Framework checkpoint restore prove the original agent session was preserved?

AgentExecutorCheckpointState defaults missing known fields, creating a new agent session when agent_session is absent. Unknown fields are ignored; malformed known fields raise WorkflowCheckpointException.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can rebuilding a .NET Agent Framework workflow with new agent IDs resume its old checkpoints?

The .NET resume contract requires the same workflow structure and executor identities. Agent IDs and configured names must stay stable. Assigning stable values later does not repair old checkpoints created with different identities.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does using an Agent Framework checkpoint provider imply cross-process recovery?

The documented Python providers have different durability: InMemoryCheckpointStorage is process-local, FileCheckpointStorage uses local disk, and CosmosCheckpointStorage supports distributed persistence. A shared interface does not equal shared durability.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Agent Framework AG-UI RUN_FINISHED event prove the workflow completed its task?

The Python workflow adapter emits RUN_FINISHED with outcome.type set to interrupt when awaiting input. The event can contain pending interrupt details rather than a completed business outcome.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an Agent Framework AG-UI continuation omit the thread ID returned at the start?

When the initial threadId is absent, the endpoint reports a generated ID in RUN_STARTED. Continuations use that ID. With workflow_factory, resume, tool-result or approval continuation without threadId fails before creating a new workflow.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Agent Framework checkpoint ID alone authorise AG-UI resume?

New checkpoints are bound to Snapshot Scope and threadId. Mismatches fail closed. Older ownerless checkpoints cannot resume through scoped or threaded requests; legacy unscoped, unthreaded resumes remain supported. Endpoint authorization remains separate.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can restoring an AG-UI thread snapshot resume the Agent Framework executor state?

Workflow checkpoints preserve executor/runtime state and pending requests. AG-UI snapshots preserve replayable client output, shared state and the latest interrupt. Neither persistence mechanism substitutes for the other.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does supplying one workflow instance to Agent Framework AG-UI create isolated state for every thread?

The Python adapter accepts either a direct workflow or workflow_factory. Documentation reserves a direct instance for safely shared workflows and recommends a factory when each thread requires its own workflow state.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does exposing a .NET Agent Framework workflow through AG-UI provide the Python workflow interrupt and resume mapping?

The captured .NET guidance exposes constituent-agent text and tool output but does not map workflow step events, activity snapshots, interrupts or Python-equivalent resume operations. Wrapping as AIAgent does not add them.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does ADK tool confirmation support every persistent session backend?

The captured experimental confirmation guide explicitly excludes DatabaseSessionService and VertexAiSessionService. Support for those services elsewhere in ADK does not establish support for this confirmation feature.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Which identities must an ADK REST confirmation preserve when resuming a workflow?

The response must use the confirmation call ID and adk_request_confirmation name, with confirmed status and optional payload. Resumable workflows also require the originating invocation_id; a different invocation ID starts a new invocation.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an ADK session backend automatically provide appropriate custody for refresh tokens?

ADK warns against assuming safe credential custody from session state. For self-managed interactive authentication it recommends user-bound encrypted storage; long-lived secrets belong in dedicated management rather than ordinary session memory.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an ADK service-account ID token be reused as a general Google API access token?

ADK distinguishes audience-bound ID tokens for IAM-secured services from scoped access tokens for Google APIs. The documented ID-token path fetches at request time rather than refreshing on a background timer.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does completing ADK OAuth only save credentials without restarting the blocked tool call?

The documented interactive flow exchanges the returned authorization information, stores obtained tokens in session state and automatically retries the original tool call. Authentication completion and business-action completion remain separate observations.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a cached active introspection result establish that an agent token has not since been revoked?

RFC 7662 permits response caching but warns that it can allow use after revocation until cached state expires. If exp is present, the response must not be cached past it. Cache duration is a resource-specific security and performance choice, not a guarantee of current validity.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does active false in an introspection response identify revocation as the cause?

For an authorized call, RFC 7662 returns active false when the token is inactive, unknown to that server, or unavailable for that resource to inspect. Further cause information should be withheld. Invalid credentials for the inspection call instead produce an authorization error. The result alone does not identify the cause.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

May an authorization decision inherit authority from a prior actor nested inside an OAuth act claim?

RFC 8693 identifies the current actor in the outermost act claim. Nested actors are informational delegation history. Access-control decisions must consider only the top-level token claims and current actor, rather than granting authority from prior actors.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can every value in the token-exchange access_token field be sent as an OAuth Bearer credential?

RFC 8693 uses access_token as a response field even when the issued object is not an OAuth access token. issued_token_type describes its representation; token_type describes its use. N_A indicates that an OAuth usage type does not apply. The field name alone does not establish Bearer usability.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does one scope list in a multi-target token exchange assign different scopes to different recipients?

RFC 8693 defines the request as asking for every requested scope at every requested target, rather than positional scope-to-recipient pairs. Broad requests may be refused, including with invalid_target. Requested combinations remain distinct from the rights actually issued.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an agent mark credential revocation complete after the provider returns HTTP 503?

RFC 7009 requires a client receiving HTTP 503 to assume the token still exists. It may retry after a reasonable delay; Retry-After can indicate expected unavailability. A failed revocation request is not completion evidence.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does setting an OpenAI Agents SDK on_approval callback require approval for local shell or patch calls?

In the pinned Python SDK documentation, local ShellTool and ApplyPatchTool default needs_approval to False. An on_approval callback alone does not enable approval. The callback runs only for calls that require approval and lack an existing decision; configure needs_approval separately.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do schema validation and context_override authenticate an OpenAI RunState snapshot submitted by a reviewer?

The pinned Python SDK guidance says RunState.from_json and from_string restore execution state without authenticating the snapshot or its submitter. Schema checks, tool-call fingerprints, strict_context, context_override or removing approval records do not make untrusted state safe. The application must verify complete integrity, ownership and replay protection before deserializing a client-carried snapshot.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Playwright MCP shared-browser-context isolate browser state between connected HTTP clients?

The pinned Playwright MCP README defines --shared-browser-context as reusing the same browser context across all connected HTTP clients. A separate MCP client connection therefore does not establish a separate browser context when this setting is enabled.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do unresolved OpenAI Agents SDK approvals prevent every call in the same interruption batch from continuing?

The pinned Python SDK documentation permits resolving only some pending approvals. On resume, resolved calls can continue while unresolved calls remain in interruptions and pause the run again. A remaining approval interruption is not evidence that no call from the batch has progressed.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an OpenAI hosted-MCP always-approve decision transfer to a same-named tool on another server label?

The pinned Python SDK identifies a hosted-MCP sticky decision by the combination of server_label and tool name. An always-approve decision does not approve a same-named tool on another label. A persistent always-approve or always-reject decision requires both identity fields to be non-empty.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Playwright MCP keep its default workspace and file-URL restrictions after allow-unrestricted-file-access is enabled?

The pinned README says --allow-unrestricted-file-access permits files outside workspace roots and unrestricted file:// navigation. By default the documented file access is restricted to workspace roots, or the working directory when no roots are configured, and file:// navigation is blocked.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Vercel AI Gateway provider order restrict every fallback to that list?

Vercel documents order as a preference: other eligible providers can still be tried. The only list removes providers outside it; if none of its providers can serve the model, the request fails. Review the effective restriction as well as the order.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does enabling Vercel AI Gateway Provider Allowlist immediately restrict the team to a previously reviewed provider subset?

The captured guide says initial enablement includes every currently available provider. Owners must remove unwanted providers; later new providers start disabled. A request-level only list must also satisfy the team list. Provider exclusion does not necessarily exclude a model offered by another allowed provider.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does adding a Vercel AI Gateway BYOK key establish that each successful request used that key?

Vercel selects the oldest enabled dashboard key for a provider, with a separate ZDR eligibility rule. Standby keys are not the failure fallback: system credentials can be used instead. Request-scoped BYOK excludes dashboard credentials for that request but still permits system fallback.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Vercel inferenceRegion establish that the gateway and every downstream copy stayed in that region?

The documented pin controls provider inference and configured provider storage; a request-level region must remain within a team pin. Gateway processing may occur in any Vercel region. Gateway-run tools and provider abuse or safety handling have separate location boundaries. Check the serving attempt region, not just the requested value.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Bedrock source Region or manually enabled Region list constrain every cross-Region request to that location?

Bedrock uses the selected inference profile to define eligible processing destinations. Geographic profiles stay within their specified geography; global profiles can route worldwide among supported commercial Regions. Cross-Region inference can use Regions not manually enabled in the account. Source-region selection therefore does not identify the processing destination.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can a Bedrock inference-profile exception bypass a denied originating Region?

For Geographic cross-Region inference, AWS evaluates the profile and foundation-model resources in the source and candidate destination Regions. The InferenceProfileArn condition is present for foundation-model evaluations, but absent for the profile-resource evaluation. A destination-region exception using that condition cannot bypass the originating-call Region restriction.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does an Azure Foundry resource location establish the exact geography where every model request is processed?

The captured Microsoft guides distinguish Global, Data Zone and geography-based deployments; the resource location alone does not select their processing scope. Their EU descriptions differ: the privacy page says EU member nations, while the deployment guide includes the EU Data Boundary and possible EFTA regions. An exact country set remains unresolved from these captures.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Can an old Vercel AI Gateway request row establish all attempted providers and credential sources?

Vercel documents a 30-day lifetime for routing-attempt details. Older rows can remain visible without those details. The dashboard export covers the rows currently loaded under its filters; a row or export is therefore not necessarily a complete retained provider-attempt history.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does marking a Vercel BYOK key ZDR-compliant enable zero-retention routing or verify its provider agreement?

Vercel treats a key mark as eligibility for ZDR routing, not activation. Team-wide ZDR or request zeroDataRetention must also be enabled. The mark relies on the owner's provider agreement, which Vercel cannot inspect. ZDR routing can fall back to eligible system credentials and fails if no eligible provider is available.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a Cloudflare AI Gateway payload-log opt-out eliminate the full request log?

The payload header controls request and response bodies while metadata can still be logged. The collect-log header controls the wider stored entry and overrides gateway defaults. For Unified Billing, billing details are recorded even when collection headers are false. These controls apply to gateway-stored logs, not provider retention.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Do Cloudflare AI Gateway collection headers prevent Logpush from exporting that request?

Cloudflare states that Logpush exports regardless of gateway log enablement and the collection headers. Export requires a public key, the gateway Logpush setting and an enabled destination job. Exported copies have a separate destination custody boundary; disabling gateway collection does not establish their removal.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does a successful Cloudflare AI Gateway response prove the current request reached the model provider?

Cloudflare documents returning a cached response until its TTL expires. A custom cache key makes requests sharing that key reuse the response, so the caller must group only equivalent requests. The skip-cache header bypasses that cache. Log collection and provider processing evidence remain separate questions.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does no Cloudflare AI Gateway log establish that no request occurred?

Cloudflare distinguishes legacy logging eligibility from newer Workers Logs arrangements. Legacy logs persist until deletion; at capacity the gateway can stop saving or delete its oldest logs. The documented historical absence can therefore reflect capacity or deletion rather than no traffic.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does disabling Bedrock invocation logging establish zero retained prompts and outputs?

AWS documents model-specific abuse retention separately from optional invocation logging, including flagged-traffic and all-traffic cases with stated exceptions. For affected cross-Region models, retained inputs and outputs are stored in the processing destination Region. The exact model, programme eligibility and applicable date govern the documented exception.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Does Foundry Agent Service storage configuration describe direct Responses API state and all client-held reasoning items?

Microsoft describes direct Responses API history as service-managed storage without bring-your-own-data storage, distinct from Agent Service arrangements. Resource CMK protection applies only where configured and applicable. That description does not cover application-retained material, including encrypted reasoning items returned for stateless requests.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Which Bedrock event field identifies where a cross-Region invocation was processed?

AWS records cross-Region requests in the source Region and documents additionalEventData.inferenceRegion for processing location. Its streaming-completion example uses serviceEventDetails.AdditionalEventData.additionalEntries.inferenceRegion and parentRequestId. The event type and correlation matter; awsRegion identifies where the event was recorded.

Free exact HTTP publication; outside MCP/search and paid retrieval. Complete free preview JSON

Should a supplier be excluded merely because AI helped write its bid?

PPN 017 says supplier AI use in the commercial process is not prohibited. It describes optional disclosure questions and proportionate due diligence into tender accuracy, capacity and capability. Review implication: AI-use disclosure alone cannot establish delivery capability or automatic exclusion authority. Request evidence against specific tender uncertainties.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does sharing confidential tender material with a bidder establish permission to use it for model training?

PPN 017 describes proportionate controls to prevent confidential authority information or other non-public information being used as AI training data by suppliers. Review implication: Access to tender material alone does not establish training permission or actual compliance with the agreed handling restriction.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Must every public-sector MCP supplier hold Cyber Essentials regardless of the contract?

PPN 014 requires relevant, proportionate cyber controls and rejects a blanket approach. Where relevant, suppliers without Cyber Essentials or Cyber Essentials Plus must demonstrate equivalent controls. G-Cloud inclusion does not remove the buyer call-off cyber-risk review. Review implication: Record the contract-specific risk decision and supporting evidence. A missing badge alone is not a universal exclusion rule, and framework presence is not complete award assurance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can award-time certification alone support a later transfer of data to a supplier?

PPN 014 requires certificate or equivalent evidence at the point data is passed to the supplier. Where Cyber Essentials certification is required, annual renewal applies for the contract duration. Review implication: An award-time certificate alone does not establish the state at a later handoff. Equivalent-control evidence has its own review basis; it is not necessarily a certificate with an annual expiry.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does a supplier Cyber Essentials certificate assure the particular MCP service being purchased?

PPN 014 says Cyber Essentials does not assure specific supplied products or services. Risks exceeding the scheme parameters may require additional proportionate measures and specialist input. Review implication: A general supplier certificate cannot substitute for the service-specific scope and threat evidence required by this buyer.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What processing details must be bound before relying on a UK processor agreement?

UK Article 28(3) requires a binding contract or other domestic-law act specifying processing subject, duration, nature, purpose, data types, data-subject categories and controller obligations and rights. Paragraph 9 requires writing, including electronic form. Review implication: A generic privacy notice alone does not establish the buyer-specific processing terms, binding relationship or applicable scope.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can an agent supplier add a subprocessor under general authorisation without a change-notice opportunity?

UK Article 28(2) requires prior specific or general written controller authorisation for another processor. Under general authorisation, intended additions or replacements must be notified to give the controller an opportunity to object. Review implication: A public subprocessor list alone does not establish the applicable buyer authorisation, delivery of notice or opportunity to object.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does a supplier shift its Article 28 responsibilities to the buyer simply by using a subprocessor?

UK Article 28(4) requires the same data-protection obligations to bind the further processor through a contract or other legal act. The initial processor remains fully liable to the controller for performance of those obligations if the further processor fails. Review implication: A list of subcontractors does not establish the obligation chain. Case-specific liability, damages and transfer legality need separate competent assessment.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Which controller exit choice and claimed domestic-law storage exception must be evidenced under UK Article 28(3)(g)?

UK Article 28(3)(g) sets out the controller choice of return or deletion at the end of processing services, together with deletion of existing copies unless domestic law requires storage. Review implication: Identify the controller exit choice and evidence supporting any asserted legal storage exception. This duty is separate from evidence that return or deletion actually occurred.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can a processor certificate alone establish the controller has the required Article 28 audit information and access?

UK Article 28(3)(h) requires necessary compliance information and contribution to audits including inspections by the controller or its mandated auditor. Paragraph 5 permits approved Article 40 codes or Article 42 certification as a means of demonstrating sufficient guarantees. Review implication: Even an approved scheme does not by itself establish the contractual information/audit arrangements or their exercise. An arbitrary certificate is not automatically an approved Article 42 mechanism.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

If an agent supplier determines processing purposes and means outside its processor role, is the contract label conclusive?

UK Article 28(10) treats a processor that infringes the Regulation by determining purposes and means as a controller in respect of that processing. Review implication: A contract label is not conclusive for every activity. Escalate an independent reuse purpose for a processing-specific assessment; ordinary implementation choices alone do not settle controller status.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can supplier brand or spend alone determine the assurance tier for an enterprise MCP service?

NIST SP 1305 recommends supplier-criticality criteria based on business importance, data sensitivity and system access, followed by prioritised supplier records. Review implication: Brand or spend alone does not describe this intended-use consequence. The buyer must supply its criticality criteria; this record supplies no risk score or mandatory tier.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Who owns supplier-security decisions across the buyer, agent operator and infrastructure provider?

NIST SP 1305 recommends named accountable roles, responsibility matrices, shared-responsibility obligations in policies and applicable agreements, and information-sharing protocols. Review implication: A support contact is not the complete allocation of supplier-security decisions. Include buyer, operator, MSP and underlying-provider roles where relevant; a matrix remains a declaration.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does a service uptime percentage alone define acceptable supplier security performance?

NIST SP 1305 recommends security requirements in service-level agreements to monitor acceptable supplier security performance throughout the relationship. Review implication: An uptime metric alone does not specify the relevant security requirements, reporting and verification method. Review unresolved findings and owners before renewal.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does a supplier vulnerability-process statement establish timely mitigation across its service dependencies?

NCSC Principle 5.1 recommends checking mitigation timescales and provider responsibility across service components and dependencies. It notes that the process standards it cites do not themselves specify acceptable mitigation timescales. Review implication: A process label does not establish timely mitigation of the relevant deployment. Review scoped commitments, prior performance and current mitigation evidence separately.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Who analyses provider-side events and owns escalation and response beyond making audit logs available?

NCSC Principle 5.2 separates generating and collecting events from analysing them and taking appropriate action. It cautions that collection without effective analysis does not establish prompt detection and response. Review implication: Identify who analyses provider-side events and owns escalation/action. Event export or retention alone does not establish operational detection.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What notification evidence is needed for incidents affecting the buyer data or shared service?

NCSC Principle 5.3 recommends defined reporting routes, pre-planned response and agreed notification methods and timescales for incidents affecting customer data. These arrangements are additional to customer monitoring responsibilities. Review implication: A public status page alone does not establish a buyer-specific notification trigger, recipient or agreed timing. Include relevant supplier participation without inferring a statutory deadline.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What supplier notice and buyer-impact evidence are needed before a service-use-affecting change?

NCSC Principle 5.4 recommends tracking assets and dependencies, assessing security impact, following changes to completion and giving appropriate notice before changes that affect use of the service. Review implication: Before continued reliance, identify the changed buyer dependency, relevant impact and notice. A release announcement alone does not establish that this buyer received appropriate advance notice.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can a community SaaS label alone establish the isolation controls of an MCP service built on public infrastructure?

NCSC Principle 8 distinguishes application-level separation in a layered service from underlying public-IaaS hypervisor controls. It recommends identifying which party implements each security function and understanding the underlying stack for sensitive uses. Review implication: A community SaaS label alone does not establish the complete isolation boundary or transfer assurance from an underlying provider. No tenant-isolation testing occurred.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What evidence covers persons authorised to process personal data for a UK processor?

UK Article 28(3)(b) requires the processor contract to ensure persons authorised to process personal data have committed to confidentiality or are subject to an appropriate statutory confidentiality obligation. Review implication: A service privacy page alone does not establish the commitment or statutory obligation for each relevant personnel category. This is not staff vetting or an effective-access test.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What should the buyer establish about processor assistance with data-subject requests?

UK Article 28(3)(e) requires appropriate technical and organisational assistance, insofar as possible and taking account of processing nature, for the controller response to data-subject rights requests. Review implication: A generic export feature does not establish the applicable assistance process, scope or limitations. Identify the contractual and operational assistance evidence separately.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does possession of an API credential establish the controller instruction for a personal-data transfer?

UK Article 28(3)(a) addresses documented controller instructions, including transfers, with a domestic-law exception and a duty to inform beforehand unless the stated public-interest prohibition applies. Review implication: An API credential establishes neither that documented instruction nor a lawful transfer basis. Consent, destination authority and actual execution remain separate unverified questions.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What should be agreed about continuing component information for a critical supplier product?

NIST SP 1305 recommends contractual requirements to maintain a current component inventory for critical products and disclose security features, functions and vulnerabilities through product life or the service term. Review implication: An initial SBOM does not establish a continuing inventory-maintenance or disclosure commitment. Retain dated contract, inventory and change evidence; completeness remains unverified.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the planned EU-facing chatbot make its AI identity clear at the first interaction?

Providers must design direct human interactions to disclose AI identity unless obvious to a reasonably informed, observant and circumspect person in context; notice must be clear, distinguishable and accessible at first interaction. Review implication: Map each user entry point, notice timing, accessibility and any reasoned obviousness exception before accepting the interaction design.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Is a visible AI label alone enough for the provider marking decision on a newly marketed generator?

For covered systems placed on the market on or after 2 August 2026, outputs must be machine-readably marked and detectable as artificial; effectiveness, interoperability, robustness and reliability are required as technically feasible, considering content limits, cost and state of the art. Review implication: Request output-format and detection evidence rather than treating a visible caption as machine-readable provenance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does this generator qualify for the temporary Article 50(2) marking deadline?

Article 111(4) gives providers of qualifying systems placed on the market before 2 August 2026 until 2 December 2026 to comply with Article 50(2). Review implication: Require dated placement evidence and system identity; do not extend this marking-only transition to other disclosure duties.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does an editing-only claim justify excluding this output transformation from provider marking?

The marking duty does not apply to the extent a system assists standard editing or does not substantially alter deployer input data or its semantics. Review implication: Compare representative input/output transformations and feature scope before accepting an editing exception; separate unsupported feature modes.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What notice evidence is needed before deploying an otherwise lawful emotion or biometric categorisation feature?

Covered deployers must inform exposed persons of the system operation and comply with applicable data-protection law; notice must be clear, distinguishable, accessible and no later than first exposure. Review implication: Request exposure/notice mapping and the separate lawful-use assessment; disclosure cannot legitimise a prohibited use.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

How should a publisher document its deepfake disclosure decision, including creative material?

For content constituting a deep fake, covered deployers disclose artificial generation/manipulation. Evidently artistic, creative, satirical, fictional or analogous work permits appropriate disclosure that does not hamper enjoyment; it does not remove disclosure entirely. Review implication: Assess whether the content meets the legal deepfake definition, then document format/timing of disclosure including the creative-work rationale.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can this publisher rely on human review and editorial responsibility instead of the AI-text disclosure duty?

Covered public-interest text requires artificial-generation/manipulation disclosure unless a specified exception applies; editorial exception requires human review or editorial control AND a natural or legal person holding editorial responsibility. Review implication: Identify responsible publisher and actual review/control evidence; approval by an unnamed reviewer does not establish the combined exception.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does this UK-only or EU-connected deployment fall within the relevant AI Act operator scope?

The Act includes providers marketing/putting systems into service in the EU, EU-established/located deployers, and third-country providers/deployers whose AI outputs are used in the EU, subject to Article 2 exclusions. Review implication: Map establishment, market/service placement, output use and operator roles before importing EU obligations into a UK procurement decision.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does a product-related AI feature meet the Annex I high-risk route, rather than merely belonging to a regulated product?

Article 6(1) requires both the product/safety-component link to Annex I legislation and a required third-party conformity assessment. New 1a-1c distinguish non-safety assistance and assessment for non-health/safety risks; malfunction endangering health/safety remains material. Review implication: Require the precise product law, safety-function analysis and assessment route; use Chapter III Sections 1-3 future date only after category checks.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What supports a provider claiming its Annex III system is not high-risk under Article 6(3)?

Article 6(3) requires no significant risk of harm and one specified condition, such as a narrow procedural or preparatory task. Profiling natural persons remains high-risk. Article 6(4) requires the provider assessment documented before placement/service and registration under 49(2). Review implication: Inspect intended task, influence over decisions and profiling before accepting a documented exception; an internal label is insufficient.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Which deadline should this high-risk readiness plan assign to Chapter III Sections 1-3?

Amended 113(c) applies Chapter III Sections 1-3 except 6(5) from 2 December 2027 for 6(2)/Annex III systems and 2 August 2028 for 6(1)/Annex I systems. Article 111 may alter legacy-system treatment. Review implication: Tag each obligation with chapter/section, system route and transition instead of assigning one date to the whole Act.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can a free open-source licence alone exclude this AI system from relevant AI Act duties?

Article 2(12) excludes systems released under free/open-source licences unless placed on the market or put into service as high-risk systems or systems falling under Article 5 or 50. Review implication: Check intended use and applicable exception categories separately from licence metadata.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does naming a reviewer establish the oversight arrangements needed for this planned high-risk deployment?

Article 26(2) requires oversight assigned to natural persons with necessary competence, training and authority, as well as necessary support. Review implication: Request role assignment, relevant training, decision authority and support arrangements; then distinguish documentation from observed intervention ability.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What evidence supports a claim that an overseer can interpret, disregard, override or stop the system?

Article 14 provides risk/proportionality-linked oversight design measures enabling assigned people to understand capacities/limits, recognise automation bias, interpret outputs, override/reverse outputs and interrupt via a safe-stop procedure as appropriate to context. Review implication: Map each claimed intervention to a usable mechanism and boundary, without treating design documentation as proof of live enforcement.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Is this deployer within the FRIA scope, and can existing DPIA material cover particular elements?

Article 27 covers specified public-law/public-service deployers and Annex III5(b)/(c) deployers, excluding Annex III point 2. Assessment is before deployment/first use, with updates for changed elements; amended 4 permits relevant DPIA cross-references or incorporated sections where requirements are already met. Review implication: Check deployer/use-case eligibility, then map each required FRIA element to actual evidence; do not equate a DPIA title with complete coverage.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Do the supplied high-risk-system instructions contain enough specific information for this planned operation?

Article 13 requires accessible, comprehensible instructions covering purpose, tested performance/limitations, relevant risks, appropriate input/output information, predetermined changes, oversight, resources/maintenance and relevant log mechanisms. Review implication: Build a gap map against the proposed use and system version; separate documented performance claims from independently observed results.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can a supplier retention setting establish that the deployer retains its required high-risk-system logs?

Article 26(6) addresses automatically generated logs to the extent under deployer control, for an intended-purpose-appropriate period of at least 6months unless applicable Union/national law provides otherwise, particularly data protection. Review implication: Map log custody, automatic generation, retention and competing applicable requirements before relying on a supplier dashboard setting.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What evidence supports that the system technical documentation was prepared before placement and kept current?

Article 11 requires pre-market/service technical documentation kept up to date, supplying Annex IV information; eligible SMEs/startups/SMCs may use simplified provision only via the prescribed Commission form. Product systems under Annex I Section A use a combined documentation set. Review implication: Check version/change linkage and evidence completeness rather than accepting a stale file or an invented simplified form.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the pre-existing system qualify for the legacy transition after a later design change?

Article 111(2), without prejudice toArticle 5 and excluding 111(1) systems, applies the Regulation to qualifying older high-risk systems only if significant design changes occur from the relevant Chapter III application date; providers/deployers of systems intended for public authorities must take steps to comply by 2 August 2030. Review implication: Preserve the before/after design, placing/service date and use context; evaluate significance rather than using a version label as the trigger.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What response evidence is needed when a deployer has reason to consider the system presents Article 79(1) risk?

Under 26(5), deployers monitor on instructions; where they have reason to consider instructed use may present 79(1) risk, they inform provider/distributor and relevant market-surveillance authority without undue delay and suspend use. Serious incidents have additional immediate notification rules. Review implication: Map risk trigger, accountable suspension authority and notification path; retain actual timestamps separately from written procedures.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can an ICT outsourcing contract transfer our DORA accountability?

A financial entity using ICT services for its business remains responsible for its obligations under DORA and applicable financial-services law. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Which entities must maintain the Article 28(2) strategy?

Financial entities other than Article 16(1), first-subparagraph entities and microenterprises must adopt and regularly review an ICT third-party risk strategy, including the critical/important-function ICT-services policy. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can our DORA register omit non-critical ICT services?

Financial entities must maintain and update the information register for all contractual arrangements for ICT services, distinguishing critical/important-function arrangements from others. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What conflict evidence belongs in the pre-contract ICT review?

Before entering an ICT-services contractual arrangement, the financial entity must identify and assess conflicts of interest that the arrangement may cause. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What competence evidence is needed for a technically complex ICT audit?

For ICT contractual arrangements entailing high technical complexity, the financial entity must verify appropriate skills and knowledge of internal, external or pooled auditors. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What distinguishes a documented DORA exit plan from evidence of a tested plan?

For ICT services supporting critical or important functions, financial entities must have exit strategies; exit plans must be comprehensive, documented, sufficiently tested under Article 4(2), and periodically reviewed. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What concentration evidence is needed before another critical-function ICT contract?

For envisaged ICT arrangements supporting critical or important functions, financial entities must consider difficult substitution and multiple arrangements with the same or closely connected providers, and weigh alternative solutions' costs and benefits. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What complete contract evidence should the ICT procurement file contain?

Financial-entity and ICT-provider rights and obligations must be clearly allocated in writing; the full contract includes SLAs in one written document available on paper or another downloadable, durable, accessible format. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Which location and change-notice terms belong in our ICT contract?

ICT contracts must state regions or countries for contracted/subcontracted service delivery and data processing, including storage, and require advance notification of envisaged location changes. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What cost and assistance terms should an ICT incident clause specify?

ICT contracts must require provider assistance for an ICT incident related to the supplied service, at no additional cost or at a cost determined ex ante. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can a provider audit summary replace our critical-function contractual audit rights?

Critical/important-function ICT contracts require ongoing performance-monitoring rights with access, inspection and audit provisions. The final subparagraph permits a microenterprise financial entity to agree delegation to an independent third party appointed by the provider, with information and assurance available at any time. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What transition evidence is needed for a critical ICT exit clause?

Critical/important-function ICT contracts must include exit strategies with a mandatory adequate transition period during which services continue and migration to another provider or in-house solution is possible, consistent with complexity. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What subcontractor visibility should we assess before approving the ICT arrangement?

Before entering the relevant arrangement, the financial entity must assess the provider's ability to identify all subcontractors providing critical/important-function ICT services or material parts, notify/inform the entity and supply information necessary for the Article 3 assessment. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does periodic reassessment address changes in the business environment, supported functions, ICT threats, concentration and geopolitical risks?

Financial entities using relevant subcontracted ICT services must periodically repeat the Article 3(1)(f)-(j) assessment against business-environment changes, including supported functions, ICT threats, concentration and geopolitical risks. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What chain-continuity term is needed when a subcontractor fails?

The financial-entity/provider contract must specify that the provider ensures continuity of critical/important-function ICT services throughout the subcontractor chain if a subcontractor fails to meet its contractual obligations. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

When can a material subcontracting change proceed under the agreed notice process?

The contract must provide timely information about intended material subcontracting changes and a reasonable approval/objection notice period; changes may be implemented after approval or after no objection by the end of that period. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does register rank measure supplier risk or supply-chain position?

The financial entity assigns supply-chain rank as an integer at least one: the direct provider is rank one and a subcontractor is higher than one. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Which direct providers and subcontractors belong in the register?

Register templates must include relevant information on all ICT services from direct providers, and information on all subcontractors effectively underpinning critical/important-function ICT services or material parts. Annex I B_05.02 additionally includes all ICT intra-group service providers and, where an intra-group provider uses subcontractors, at least the first extra-group subcontractor even if the service does not support a critical or important function. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Which legal identifiers must support the provider register entry?

Financial entities identify ICT providers that are legal persons with a valid active LEI or EUID, both where available; for relevant registered underpinning subcontractors they ensure this through the direct provider. Individuals acting in a business capacity are excepted. Under Annex I B_05.01.0020, legal persons not established in the Union use LEI only; the 19 September 2025 corrigendum retains this restriction. Establishment and legal-person status must be established before selecting the identifier type. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

How should multiple valid values be represented in register templates?

Each register data element must contain a single value; when multiple values are valid for a data element, the financial entity adds one corresponding-template row for each valid value. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What reporting and register-access evidence must the financial entity retain for its competent authority?

Financial entities report at least yearly on the number of new ICT arrangements, provider categories, contract types, services and functions, and make the full register or requested sections and necessary supervisory information available on competent-authority request. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Has the planned arrangement or changed function classification been notified through the applicable supervisory process?

Financial entities inform the competent authority in a timely manner about planned ICT arrangements supporting critical or important functions and when a function becomes critical or important. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Is the decision to contract supported by a dated classification, risk and provider-suitability assessment?

Before entering an ICT arrangement, financial entities assess critical-function support and supervisory contracting conditions, identify relevant risks including concentration, and undertake due diligence to establish prospective provider suitability. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What evidence supports the provider's use of security standards appropriate to the contracted service?

Financial entities may contract only with ICT providers complying with appropriate information-security standards; for critical or important functions they take due consideration, before concluding, of the provider's use of the most up-to-date and highest-quality standards. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Is the audit programme tied to risk, defined scope and applicable supervisory instructions?

When exercising provider access, inspection and audit rights, financial entities predetermine audit and inspection frequency and areas on a risk basis, following commonly accepted audit standards and supervisory instructions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the contract preserve termination rights for each relevant DORA circumstance?

Financial entities ensure ICT arrangements may be terminated for significant legal or contractual breach, monitored circumstances capable of altering the performance of functions, evidenced ICT-risk-management weaknesses, or impeded effective supervision. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Would insolvency or third-country enforcement barriers impede urgent recovery of the financial entity's data?

For critical-function ICT arrangements, financial entities consider applicable provider-insolvency law and constraints on urgent data recovery; where the provider is established in a third country they also consider Union data-protection compliance and effective enforcement there. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can the financial entity and supervisor monitor the function through the documented subcontracting chain?

Where critical-function ICT arrangements permit subcontracting, financial entities assess whether and how long or complex chains affect full monitoring of contracted functions and effective supervision by the competent authority. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the contract identify the services and any permitted critical-function subcontracting conditions?

ICT contracts include a clear and complete description of all functions and ICT services, indicating whether subcontracting of services supporting critical or important functions or material parts is permitted and the applicable conditions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Do the executed clauses cover data protection and accessible recovery across the specified exit events?

ICT contracts contain provisions on data availability, authenticity, integrity and confidentiality, and access, recovery and return of personal and non-personal data in an easily accessible format on provider insolvency, resolution, discontinuation or contract termination. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the contract provide the required authority cooperation while preserving verification of the requesting authority?

ICT contracts oblige the provider to cooperate fully with the financial entity's competent and resolution authorities, including persons appointed by them. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Are the relevant provider participation conditions documented for security awareness and resilience training?

ICT contracts state conditions for provider participation in the financial entity's security-awareness programmes and digital operational-resilience training under Article 13(6); provider inclusion is where appropriate under that provision. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can the financial entity monitor agreed critical-service performance and receive material-change reports?

Critical-function ICT contracts include full service-level descriptions with precise quantitative and qualitative performance targets for monitoring and timely corrective action, plus notice periods and provider reporting of developments that may materially affect delivery against agreed levels. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the contract require contingency implementation and testing, and what dated evidence is available for the relevant service?

Critical-function ICT contracts require the provider to implement and test business-contingency plans and maintain security measures, tools and policies appropriate to the financial entity's regulatory framework. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the contract support provider cooperation if the financial entity is subject to an authorised TLPT exercise?

Critical-function ICT contracts oblige the provider to participate and cooperate fully in the financial entity's threat-led penetration testing as referred to in Articles 26 and 27. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Who owns the group-wide consistency review of critical-function subcontracting conditions?

Where the regulation applies on a consolidated or sub-consolidated basis, the parent responsible for those financial statements ensures permitted critical-function subcontracting conditions are consistent across group financial entities and adequate at all relevant levels. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What demonstrates the direct provider's capacity to assess and monitor its proposed subcontractors?

Before contracting for permitted critical-function subcontracting, the financial entity assesses the provider's ability to select and assess subcontractors' operational and financial abilities, including testing participation when required, and the provider's expertise and resources to monitor subcontractor ICT risk. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Can the financial entity itself oversee the subcontracted service and assess a subcontractor failure?

Before permitting critical-function subcontracting, the financial entity assesses its own expertise and financial, human and technical resources to monitor related ICT risks, and the impact of subcontractor failure on its resilience and financial soundness. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Do subcontractor terms and the chain of contracts preserve exercisable access, inspection and audit rights?

The financial entity's contract specifies subcontractor access, inspection and audit rights for the entity and relevant competent and resolution authorities corresponding to DORA Article 30(3)(e); precontract assessment also checks granted access and inspection rights and obstacles to exercising them. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Are monitoring and reporting responsibilities assigned at both contractual levels?

The direct contract requires provider monitoring of relevant subcontracted services and reporting towards the financial entity; the provider's subcontract specifies monitoring and reporting back to the provider and, where agreed, to the financial entity. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Are the relevant contingency service levels and security requirements present in the subcontract?

The direct contract requires provider-subcontractor arrangements to contain the DORA Article 30(3)(c) business-contingency requirements with subcontractor service levels and the specified ICT security standards and additional requirements. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Is there a documented and justified plan for necessary subcontracting contract changes?

Contract changes necessary to comply with the subcontracting regulation are implemented in a timely manner and as soon as possible, and the financial entity documents the planned implementation timeline. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Do objection handling and termination clauses cover each of the specified subcontracting violations?

If an intended material subcontract change exceeds risk tolerance, the financial entity informs the provider, objects and requests modifications before the notice period ends. The contract preserves termination rights for implementation despite such objection and requested modifications, early implementation without approval, or subcontracting not explicitly permitted. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

What review and correction evidence supports the register's accuracy and consolidation consistency?

Financial entities ensure accurate and consistent register information, review it regularly and promptly correct detected errors or discrepancies; responsible group entities ensure entity-level information is correct and consistent with consolidation, applying the stated six data-quality principles. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the register distinguish unperformed assessments and undefined recovery objectives from assessed operational values?

The corrected function template records criticality as Yes, No or Assessment not performed, uses 9999-12-31 when its assessment is not performed, and reports RTO/RPO in hours: values below one hour as 1, and undefined objectives as 0. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Does the reporting evidence distinguish temporary storage, data at rest and processing locations without collapsing multiple countries?

The register asks whether the ICT service foresees storage even temporarily, records data-at-rest countries when storage is Yes, and processing countries where processing is foreseen; multiple countries use additional rows and the fields have their stated applicability conditions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Has the alternatives assessment been performed, and is the result represented without confusing absence of assessment with absence of alternatives?

For each provider supporting a critical or important function the alternative-provider assessment is performed; corrected B_07.01.0110 distinguishes Yes, No and option 3 Assessment not performed, while additional identification information in .0120 is optional when Yes. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement. Complete free preview JSON

Machine-readable question routes

External documentation review

1Password SaaS Manager MCP: Remote and local write boundaries

Question: Are the remote and local SaaS Manager MCP connections equally read-only?

The remote service permits reads only. The local server defaults to reads but can enable writes when the API client also permits them. Authentication uses client credentials to obtain a short-lived bearer token; remote dynamic client registration is not supported.

Source: 1Password SaaS Manager MCP Server. Documentation checked 2026-10-17; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer installation and runtime untested

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

1Password publishes the SaaS Manager connector, previously Trelica.

Documented by publisher. 1Password SaaS Manager MCP Server

Purpose

Expose SaaS Manager API capabilities to an AI client.

Documented by publisher. 1Password SaaS Manager MCP Server

Read capability

Data available through the configured SaaS Manager API client.

Documented by publisher. 1Password SaaS Manager MCP Server

Write capability

Remote reads only; local writes require enablement and suitable API grants.

Documented by publisher. 1Password SaaS Manager MCP Server

Authentication

OAuth client credentials exchanged for a bearer token.

Documented by publisher. 1Password SaaS Manager MCP Server

Permission surface

Administrator-created API client and selected remote or local mode.

Documented by publisher. 1Password SaaS Manager MCP Server

Data leaving the environment

Returned organisational information enters the selected assistant.

Review inference. 1Password SaaS Manager MCP Server

Failure modes to consider

Switching connection mode can change available write capability.

Review inference. 1Password SaaS Manager MCP Server

Unknowns and applicability

Installed flags, API grants and client retention are unverified.

Not established

Suggested refusal or clarification condition

Check connection mode and effective write grants before treating it as read-only.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Remote or local deployment, API client grants, region and token lifecycle.

Record history: 2026-10-17 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the documented mode and permission assumptions behind SaaS connector procurement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

1Password service accounts: Vault scope and allowed actions

Question: Does giving an agent a 1Password service account restrict it to the intended secrets?

1Password describes service accounts with selected vaults, Environments and permitted actions, independent of an individual identity. Effective secret access depends on those choices. Check the configured scope and usage evidence before assuming a token exposes only the secrets needed for the task.

Source: 1Password service account vault and action scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A service account token only exposes the intended automation secrets.

Buyer evidence still required

  • Dated account scope and allowed-action configuration
  • Inventory linking required secrets to approved containers
  • Usage report and credential lifecycle evidence

Suggested review condition: Require configured scope evidence before providing secret access to an agent.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck vault and Environment access, permitted actions and credential lifecycle.

Optional saved evidence: Save the secret-container and action boundaries used in an automation review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A cache response is not a fresh provider invocation

Question: Does a successful Cloudflare AI Gateway response prove the current request reached the model provider?

Cloudflare documents returning a cached response until its TTL expires. A custom cache key makes requests sharing that key reuse the response, so the caller must group only equivalent requests. The skip-cache header bypasses that cache. Log collection and provider processing evidence remain separate questions.

Source: Caching. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a successful Cloudflare AI Gateway response prove the current request reached the model provider?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require effective cache settings, key policy and hit/bypass evidence before claiming a fresh provider execution; a TTL is not an all-copy deletion receipt.

Suggested review condition: Require effective cache settings, key policy and hit/bypass evidence before claiming a fresh provider execution; a TTL is not an all-copy deletion receipt.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ### Cache TTL; ### Custom cache key; ## Skip cache

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require effective cache settings, key policy and hit/bypass evidence before claiming a fresh provider execution; a TTL is not an all-copy deletion receipt.
  • A cache miss or explicit skip can contact the provider; an enabled cache does not mean every response is a hit.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

A certification summary does not settle audit access

Question: Can a processor certificate alone establish the controller has the required Article 28 audit information and access?

UK Article 28(3)(h) requires necessary compliance information and contribution to audits including inspections by the controller or its mandated auditor. Paragraph 5 permits approved Article 40 codes or Article 42 certification as a means of demonstrating sufficient guarantees. Review implication: Even an approved scheme does not by itself establish the contractual information/audit arrangements or their exercise. An arbitrary certificate is not automatically an approved Article 42 mechanism.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a processor certificate alone establish the controller has the required Article 28 audit information and access?

Buyer evidence still required

  • Contract audit/information clauses
  • Available scoped assurance reports and restrictions
  • Controller/auditor access arrangements
  • Scoped findings, action owners and unresolved remediation evidence where available

Review inference: Even an approved scheme does not by itself establish the contractual information/audit arrangements or their exercise. An arbitrary certificate is not automatically an approved Article 42 mechanism.

Suggested review condition: No unlimited public audit entitlement, audit success, certificate approval or compliance conclusion is inferred.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No unlimited public audit entitlement, audit success, certificate approval or compliance conclusion is inferred.
  • An approved scoped scheme may contribute evidence of guarantees; it is neither worthless nor a replacement for all information and audit arrangements.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A configured personal key does not prove which credential served

Question: Does adding a Vercel AI Gateway BYOK key establish that each successful request used that key?

Vercel selects the oldest enabled dashboard key for a provider, with a separate ZDR eligibility rule. Standby keys are not the failure fallback: system credentials can be used instead. Request-scoped BYOK excludes dashboard credentials for that request but still permits system fallback.

Source: Bring Your Own Key (BYOK) to AI Gateway. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does adding a Vercel AI Gateway BYOK key establish that each successful request used that key?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require the successful attempt and credential source; do not infer a customer account or agreement from key presence or a successful key test.

Suggested review condition: Require the successful attempt and credential source; do not infer a customer account or agreement from key presence or a successful key test.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ### Use more than one key per provider; ## Request-scoped BYOK

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the successful attempt and credential source; do not infer a customer account or agreement from key presence or a successful key test.
  • A correlated successful attempt identifying BYOK supports that credential-path observation, subject to log integrity; the default fallback need not occur.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

A Cyber Essentials badge is not service assurance

Question: Does a supplier Cyber Essentials certificate assure the particular MCP service being purchased?

PPN 014 says Cyber Essentials does not assure specific supplied products or services. Risks exceeding the scheme parameters may require additional proportionate measures and specialist input. Review implication: A general supplier certificate cannot substitute for the service-specific scope and threat evidence required by this buyer.

Source: Cabinet Office PPN 014. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a supplier Cyber Essentials certificate assure the particular MCP service being purchased?

Buyer evidence still required

  • Certificate scope and issuing evidence
  • Exact service and deployment boundary
  • Threat and service-specific assurance requirements

Review inference: A general supplier certificate cannot substitute for the service-specific scope and threat evidence required by this buyer.

Suggested review condition: Do not infer current certification validity, product security or penetration-test results from this source.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK central government departments, executive agencies and non-departmental public bodies and NHS bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • Do not infer current certification validity, product security or penetration-test results from this source.
  • Specific service assurance may be separately available; the limitation concerns what the general Cyber Essentials certificate establishes.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A patch process needs scope and timing evidence

Question: Does a supplier vulnerability-process statement establish timely mitigation across its service dependencies?

NCSC Principle 5.1 recommends checking mitigation timescales and provider responsibility across service components and dependencies. It notes that the process standards it cites do not themselves specify acceptable mitigation timescales. Review implication: A process label does not establish timely mitigation of the relevant deployment. Review scoped commitments, prior performance and current mitigation evidence separately.

Source: NCSC Cloud Security Principle 5. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a supplier vulnerability-process statement establish timely mitigation across its service dependencies?

Buyer evidence still required

  • Affected service components and ownership
  • Mitigation commitment and change records
  • Relevant prior performance and current status

Review inference: A process label does not establish timely mitigation of the relevant deployment. Review scoped commitments, prior performance and current mitigation evidence separately.

Suggested review condition: No vulnerability scan, exploit test, current patch verification or mandatory deadline is provided.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • NCSC cloud/supply-chain guidance, not a standalone statutory obligation. Apply only to the relevant supplier service and responsibility boundary; cited older standards are not asserted to be current.
  • No vulnerability scan, exploit test, current patch verification or mandatory deadline is provided.
  • A scoped provider commitment with dated mitigation evidence may support a narrower review; a process certificate alone is insufficient.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A privacy notice is not the complete processor contract

Question: What processing details must be bound before relying on a UK processor agreement?

UK Article 28(3) requires a binding contract or other domestic-law act specifying processing subject, duration, nature, purpose, data types, data-subject categories and controller obligations and rights. Paragraph 9 requires writing, including electronic form. Review implication: A generic privacy notice alone does not establish the buyer-specific processing terms, binding relationship or applicable scope.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What processing details must be bound before relying on a UK processor agreement?

Buyer evidence still required

  • Identified controller and processor
  • Binding written instrument and version
  • Processing purpose, duration, data and subject categories

Review inference: A generic privacy notice alone does not establish the buyer-specific processing terms, binding relationship or applicable scope.

Suggested review condition: A document title or signed template does not establish enforceability, applicability or whole-regime compliance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • A document title or signed template does not establish enforceability, applicability or whole-regime compliance.
  • An incorporated written agreement may contain the required particulars; a generic notice is not necessarily the only binding document.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A processor export button is not the entire assistance arrangement

Question: What should the buyer establish about processor assistance with data-subject requests?

UK Article 28(3)(e) requires appropriate technical and organisational assistance, insofar as possible and taking account of processing nature, for the controller response to data-subject rights requests. Review implication: A generic export feature does not establish the applicable assistance process, scope or limitations. Identify the contractual and operational assistance evidence separately.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What should the buyer establish about processor assistance with data-subject requests?

Buyer evidence still required

  • Data/processing scope
  • Contract assistance obligations and contact process
  • Capabilities and limitations for relevant requests

Review inference: A generic export feature does not establish the applicable assistance process, scope or limitations. Identify the contractual and operational assistance evidence separately.

Suggested review condition: No legal deadline assessment, complete subject discovery or automatic rights fulfilment is provided.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No legal deadline assessment, complete subject discovery or automatic rights fulfilment is provided.
  • A supplier process may provide suitable assistance within the processing context; a missing feature does not by itself decide the entire legal duty.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A processor label does not decide every processing role

Question: If an agent supplier determines processing purposes and means outside its processor role, is the contract label conclusive?

UK Article 28(10) treats a processor that infringes the Regulation by determining purposes and means as a controller in respect of that processing. Review implication: A contract label is not conclusive for every activity. Escalate an independent reuse purpose for a processing-specific assessment; ordinary implementation choices alone do not settle controller status.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: If an agent supplier determines processing purposes and means outside its processor role, is the contract label conclusive?

Buyer evidence still required

  • Relevant processing activity and purpose
  • Who determines purposes and means
  • Contract instructions and proposed independent reuse

Review inference: A contract label is not conclusive for every activity. Escalate an independent reuse purpose for a processing-specific assessment; ordinary implementation choices alone do not settle controller status.

Suggested review condition: Do not classify an organisation globally or infer that every implementation choice makes it a controller.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • Do not classify an organisation globally or infer that every implementation choice makes it a controller.
  • A processor may choose technical implementation details without this alone establishing an independent purpose or controller role.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A public status page is not a buyer incident-notification agreement

Question: What notification evidence is needed for incidents affecting the buyer data or shared service?

NCSC Principle 5.3 recommends defined reporting routes, pre-planned response and agreed notification methods and timescales for incidents affecting customer data. These arrangements are additional to customer monitoring responsibilities. Review implication: A public status page alone does not establish a buyer-specific notification trigger, recipient or agreed timing. Include relevant supplier participation without inferring a statutory deadline.

Source: NCSC Cloud Security Principle 5. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: What notification evidence is needed for incidents affecting the buyer data or shared service?

Buyer evidence still required

  • Service/data scope and notification trigger
  • Agreed reporting method, recipient and timescale
  • Supplier contact route and response responsibilities

Review inference: A public status page alone does not establish a buyer-specific notification trigger, recipient or agreed timing. Include relevant supplier participation without inferring a statutory deadline.

Suggested review condition: Do not infer a statutory notification deadline, actual incident handling or breach-free operation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • NCSC cloud/supply-chain guidance, not a standalone statutory obligation. Apply only to the relevant supplier service and responsibility boundary; cited older standards are not asserted to be current.
  • Do not infer a statutory notification deadline, actual incident handling or breach-free operation.
  • A current agreement may establish notification arrangements; this does not itself prove an incident notification was delivered.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A release note is not the complete change-control evidence

Question: What supplier notice and buyer-impact evidence are needed before a service-use-affecting change?

NCSC Principle 5.4 recommends tracking assets and dependencies, assessing security impact, following changes to completion and giving appropriate notice before changes that affect use of the service. Review implication: Before continued reliance, identify the changed buyer dependency, relevant impact and notice. A release announcement alone does not establish that this buyer received appropriate advance notice.

Source: NCSC Cloud Security Principle 5. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: What supplier notice and buyer-impact evidence are needed before a service-use-affecting change?

Buyer evidence still required

  • Changed component/configuration and dependency map
  • Impact assessment and authorised change record
  • Notice, buyer action and completion evidence

Review inference: Before continued reliance, identify the changed buyer dependency, relevant impact and notice. A release announcement alone does not establish that this buyer received appropriate advance notice.

Suggested review condition: No runtime change enforcement, cryptographic attestation or universal notice interval is claimed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • NCSC cloud/supply-chain guidance, not a standalone statutory obligation. Apply only to the relevant supplier service and responsibility boundary; cited older standards are not asserted to be current.
  • No runtime change enforcement, cryptographic attestation or universal notice interval is claimed.
  • A supplier may provide appropriate notice and scoped impact evidence; a public release note may be part of that evidence but is not automatically complete.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A supplier contact is not a responsibility allocation

Question: Who owns supplier-security decisions across the buyer, agent operator and infrastructure provider?

NIST SP 1305 recommends named accountable roles, responsibility matrices, shared-responsibility obligations in policies and applicable agreements, and information-sharing protocols. Review implication: A support contact is not the complete allocation of supplier-security decisions. Include buyer, operator, MSP and underlying-provider roles where relevant; a matrix remains a declaration.

Source: NIST SP 1305 C-SCRM quick-start. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Who owns supplier-security decisions across the buyer, agent operator and infrastructure provider?

Buyer evidence still required

  • Buyer/supplier responsibility allocation
  • Named accountable roles and escalation path
  • Agreement and policy versions
  • MSP and underlying infrastructure roles, where present

Review inference: A support contact is not the complete allocation of supplier-security decisions. Include buyer, operator, MSP and underlying-provider roles where relevant; a matrix remains a declaration.

Suggested review condition: A matrix is declared responsibility, not proof it was exercised or a grant of authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Voluntary NIST CSF 2.0/SP 1305 guidance, final October 2024. No automatic UK/EU legal obligation or supplier certification.
  • A matrix is declared responsibility, not proof it was exercised or a grant of authority.
  • A named support contact can be one useful role within a complete matrix; its existence alone does not assign every decision.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A technical token is not the documented processing instruction

Question: Does possession of an API credential establish the controller instruction for a personal-data transfer?

UK Article 28(3)(a) addresses documented controller instructions, including transfers, with a domestic-law exception and a duty to inform beforehand unless the stated public-interest prohibition applies. Review implication: An API credential establishes neither that documented instruction nor a lawful transfer basis. Consent, destination authority and actual execution remain separate unverified questions.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does possession of an API credential establish the controller instruction for a personal-data transfer?

Buyer evidence still required

  • Documented instruction with activity and recipient scope
  • Applicable legal/contract scope
  • Transfer assessment where needed

Review inference: An API credential establishes neither that documented instruction nor a lawful transfer basis. Consent, destination authority and actual execution remain separate unverified questions.

Suggested review condition: No consent, destination authority, legal transfer basis or effective permission is verified.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No consent, destination authority, legal transfer basis or effective permission is verified.
  • A valid documented instruction may accompany a technical token; neither token possession nor this record establishes the other legal requirements.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

A visible request row can outlive its routing evidence

Question: Can an old Vercel AI Gateway request row establish all attempted providers and credential sources?

Vercel documents a 30-day lifetime for routing-attempt details. Older rows can remain visible without those details. The dashboard export covers the rows currently loaded under its filters; a row or export is therefore not necessarily a complete retained provider-attempt history.

Source: AI Gateway Request Logs. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an old Vercel AI Gateway request row establish all attempted providers and credential sources?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Refuse historical attempt or credential completeness when details have expired or export selection is unknown; retain a separately verified suitable record before relying on it.

Suggested review condition: Refuse historical attempt or credential completeness when details have expired or export selection is unknown; retain a separately verified suitable record before relying on it.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ## Retention and limits; ## Export logs

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse historical attempt or credential completeness when details have expired or export selection is unknown; retain a separately verified suitable record before relying on it.
  • A recent complete correlated routing detail can identify the recorded successful attempt; this does not establish every export is incomplete.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

A ZDR key label is eligibility, not contract verification

Question: Does marking a Vercel BYOK key ZDR-compliant enable zero-retention routing or verify its provider agreement?

Vercel treats a key mark as eligibility for ZDR routing, not activation. Team-wide ZDR or request zeroDataRetention must also be enabled. The mark relies on the owner's provider agreement, which Vercel cannot inspect. ZDR routing can fall back to eligible system credentials and fails if no eligible provider is available.

Source: AI Gateway Zero Data Retention (ZDR). Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does marking a Vercel BYOK key ZDR-compliant enable zero-retention routing or verify its provider agreement?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require the effective ZDR gate, eligible credential identity and applicable provider agreement; refuse to infer deletion or contract validity from a label.

Suggested review condition: Require the effective ZDR gate, eligible credential identity and applicable provider agreement; refuse to infer deletion or contract validity from a label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ## BYOK; ## Using both account and request-level ZDR

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the effective ZDR gate, eligible credential identity and applicable provider agreement; refuse to infer deletion or contract validity from a label.
  • A marked key with applicable agreement and enabled ZDR can be eligible; an unmarked key can be skipped even when its owner separately believes it has suitable terms.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

A2A artifact chunks and task completion

Question: Does an A2A artifact’s lastChunk flag mean the entire task has completed?

A2A TaskArtifactUpdateEvent can append content to an artifact with the same ID. Its lastChunk flag identifies the final chunk of that artifact. Task lifecycle status is separate, so one finished artifact cannot be substituted for the terminal task outcome or acceptance of all outputs.

Source: Overview - A2A Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an A2A artifact’s lastChunk flag mean the entire task has completed?

Buyer evidence still required

  • Task and artifact IDs
  • Append flags, chunk sequence and final chunk
  • Terminal task status and expected output inventory

Review inference: Reassemble by artifact identity and inspect task status and acceptance criteria separately.

Suggested review condition: Do not close a task solely because one artifact reports its last chunk.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Missing chunks, other outputs and final buyer acceptance remain unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent partial or mixed artifacts from being accepted as finished work.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed complete task output from one artifact flag
  • Missing chunks, other outputs and final buyer acceptance remain unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A authenticated Agent Card scope

Question: Can an authenticated A2A Agent Card expose different capabilities from its public card or another client’s card?

A2A requires authentication for Get Extended Agent Card and permits different content according to client identity or authorization level. Extended cards may include additional skills. Retrieving a card does not independently verify that the client has every credential required for a later operation.

Source: Overview - A2A Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an authenticated A2A Agent Card expose different capabilities from its public card or another client’s card?

Buyer evidence still required

  • Public security declaration and authenticated identity
  • Extended card content and cache context
  • Operation-specific credential and permission requirements

Review inference: Scope cached capabilities to authenticated context and verify operation-specific authority before use.

Suggested review condition: Do not transfer privileged discovery from one client context to another or infer executable authority from advertising.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual tool credentials and permission outcomes are untested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent cross-user capability leakage and unsupported authority assumptions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic authorization from card discovery
  • Actual tool credentials and permission outcomes are untested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A completed tasks and buyer acceptance

Question: Does an A2A task’s completed state establish that the buyer accepted the delivered service?

The captured A2A specification defines completed as a terminal successful task state. Task status and output artifacts describe the protocol operation. The core task model does not itself supply the buyer’s contractual acceptance criteria or an independent verification of artifact quality.

Source: Overview - A2A Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an A2A task’s completed state establish that the buyer accepted the delivered service?

Buyer evidence still required

  • Agent and task identity
  • Returned status and exact output artifacts
  • Buyer acceptance criteria and verification result

Review inference: Compare the reported result and artifacts with the separately agreed acceptance conditions.

Suggested review condition: Do not equate protocol completion with commercial acceptance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Artifact quality and the buyer’s acceptance decision are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep automated service completion separate from payment or handover acceptance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed service quality, settlement or legal acceptance
  • Artifact quality and the buyer’s acceptance decision are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A extension version negotiation

Question: Does advertising an A2A extension guarantee compatible semantics with every version of that extension?

The captured A2A specification requires a new extension URI for breaking changes. An unsupported optional extension should be ignored; a required unsupported extension must produce an error. Automatic fallback to an older extension version is prohibited. Advertising an extension without matching its version and required status is not compatibility evidence.

Source: Overview - A2A Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does advertising an A2A extension guarantee compatible semantics with every version of that extension?

Buyer evidence still required

  • Agent Card extension URI and required flag
  • Client requested extension version
  • Negotiation result and extension-specific specification

Review inference: Verify the exact extension URI and negotiated behaviour before relying on its business semantics.

Suggested review condition: Reject compatibility assumptions when required extension versions do not match.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The implementation’s actual extension semantics and conformance are untested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid silent loss of required commercial semantics between agents.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal compatibility from a protocol badge
  • The implementation’s actual extension semantics and conformance are untested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A push notifications and completion evidence

Question: Does receiving an authenticated A2A push notification establish a final task outcome?

A2A push notifications can carry a task, message, status update or artifact update. Clients must check the expected task ID, and duplicate delivery is possible. Authentication identifies the configured notification path; it does not turn every event type into a terminal outcome.

Source: Overview - A2A Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does receiving an authenticated A2A push notification establish a final task outcome?

Buyer evidence still required

  • Configured notification authentication and expected task ID
  • Event type, status and correlation evidence
  • Deduplication and current task outcome

Review inference: Validate source and task binding, handle duplicates and inspect the specific state or artifact event.

Suggested review condition: Do not close a task solely because an authenticated webhook arrived.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The task’s final outcome and artifact acceptance are not established by receipt alone.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent intermediate or repeated agent events from closing a workflow incorrectly.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exactly-once notification delivery or payment confirmation
  • The task’s final outcome and artifact acceptance are not established by receipt alone.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A resubscription and missed events

Question: Does A2A task resubscription guarantee replay of every event missed while disconnected?

The reviewed A2A SubscribeToTask operation begins with the current Task object and then streams updates for a nonterminal task. Its initial snapshot closes a current-state observation gap; the operation does not promise a complete replay of every intermediate event missed during disconnection.

Source: Overview - A2A Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does A2A task resubscription guarantee replay of every event missed while disconnected?

Buyer evidence still required

  • Task identity and current snapshot
  • Disconnection interval and retained event history
  • Subsequent status/artifact updates

Review inference: Use the current snapshot for resumption and separate retained event evidence for historical reconstruction.

Suggested review condition: Refuse complete historical replay claims from successful resubscription alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Intermediate missed states and artifacts may remain unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Resume work without inventing a complete audit trail.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exactly-once event delivery or complete retrospective history
  • Intermediate missed states and artifacts may remain unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A task-history request limits

Question: Does omitting A2A historyLength guarantee the server returns the complete retained conversation?

A2A historyLength limits the most recent messages requested. Zero requests no messages; an unset value imposes no client limit. The server may still apply a lower limit. An unrestricted client request is therefore not a protocol guarantee of complete retained history.

Source: Overview - A2A Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does omitting A2A historyLength guarantee the server returns the complete retained conversation?

Buyer evidence still required

  • Task ID and requested historyLength
  • Returned messages and server limit policy
  • Expected conversation inventory or independent archive

Review inference: Compare returned history with independent retention and completeness evidence when reconstructing a task.

Suggested review condition: Refuse completeness claims from an omitted limit alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The amount of retained or omitted history is unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid treating a truncated conversation as a full audit record.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Unlimited message retention or complete export
  • The amount of retained or omitted history is unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A: Agent interoperability

Question: What does A2A establish about communication between independent agents?

The A2A specification defines a shared interaction model for independent agent systems. A particular pair of deployments still needs compatibility checks.

Source: A2A Protocol current specification. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • universal interoperability
  • tested compatibility of a named deployment
  • permission to delegate or spend

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A: Capability discovery

Question: Can an agent discover another agent's advertised capabilities through A2A?

A2A describes capability discovery and supported interaction modes. Advertised capability is a declaration; delivery quality and access permissions require separate evidence.

Source: A2A Protocol current specification. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • capability declarations as independent validation
  • automatic access to every advertised skill
  • guaranteed task quality

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

A2A: Task collaboration boundary

Question: Does A2A task collaboration require exposing an agent's internal memory or tools?

A2A describes task collaboration and information exchange without requiring peers to expose their internal state, memory or tools. This is a protocol design statement, not proof of a deployment's confidentiality.

Source: A2A Protocol current specification. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • automatic confidentiality of a deployment
  • access to another agent's private internals
  • task completion guaranteed by protocol support

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Actions concurrency: Serialisation and cancelled work

Question: Does a concurrency group guarantee every queued workflow will run?

The default single-pending behaviour replaces an earlier pending run when a new one arrives. The documented larger queue mode has a bound and cannot be combined with cancelling in-progress work. Serialisation is not a guarantee that every dispatch executes or that external side effects are rolled back when a run is cancelled.

Source: GitHub Actions concurrency queues. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A concurrency group preserves and completes all requested work.

Buyer evidence still required

  • Workflow group expression and queue mode.
  • Cancellation settings and observed run outcomes.
  • Recovery of effects from interrupted jobs.

Suggested review condition: Check cancellation and queue semantics before interpreting a missing run as completed work.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workflow and job groups, queue mode, cancellation expressions and external side effects.

Optional saved evidence: Retain the actual queue policy used to assess a deployment or automation service.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Additive extraction versus explicit correction/removal

Question: Does telling Mem0 a corrected fact automatically remove the earlier one?

The captured Mem0 documentation describes extraction as additive and recommends explicit update or delete for correction/removal; new information can be stored without rewriting an old fact.

Source: Mem0 primary documentation: mem0 filters. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does telling Mem0 a corrected fact automatically remove the earlier one?

Buyer evidence still required

  • old/new fact IDs
  • add/update/delete calls
  • entity filters
  • retrieval verification

Review inference: Does telling Mem0 a corrected fact automatically remove the earlier one? Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations. Additive extraction versus explicit correction/removal. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. automatic extraction path is additive

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer retraction of an earlier assertion from add success; reconcile old and new IDs using the actual correction operations.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

ADK authentication response and original tool retry

Question: Does completing ADK OAuth only save credentials without restarting the blocked tool call?

The documented interactive flow exchanges the returned authorization information, stores obtained tokens in session state and automatically retries the original tool call. Authentication completion and business-action completion remain separate observations.

Source: Google ADK: authentication and credential management. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does completing ADK OAuth only save credentials without restarting the blocked tool call?

Buyer evidence still required

  • Original tool and credential-request identities
  • Authentication callback and token-exchange outcome
  • Retried call result and side-effect evidence

Review inference: Refuse a credentials-only or completed-business-action finding from the auth callback alone; reconcile the retried tool identity and result and guard side effects separately. The existing ADK review concerns interrupted-run replay on resume. This review concerns authentication completion as a separate automatic invocation trigger, relevant before returning credentials to a blocked tool. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a credentials-only or completed-business-action finding from the auth callback alone; reconcile the retried tool identity and result and guard side effects separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. ADK **automatically retries**; Authentication Logic within the Tool Function

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a credentials-only or completed-business-action finding from the auth callback alone; reconcile the retried tool identity and result and guard side effects separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

ADK confirmation call and invocation continuity

Question: Which identities must an ADK REST confirmation preserve when resuming a workflow?

The response must use the confirmation call ID and adk_request_confirmation name, with confirmed status and optional payload. Resumable workflows also require the originating invocation_id; a different invocation ID starts a new invocation.

Source: Google ADK: action confirmations. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Which identities must an ADK REST confirmation preserve when resuming a workflow?

Buyer evidence still required

  • Original confirmation FunctionCall and invocation ID
  • Response ID, name, status and payload
  • Session context and decision-maker authorization

Review inference: Refuse original-run approval continuity without matching call, session and invocation context plus an authorised decision; structured payload alone does not establish permission. The general OpenAI continuation record does not define ADK REST correlation. This review binds ADK confirmation-call identity and resumable invocation identity together, consolidating structured payload details into one operational decision. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse original-run approval continuity without matching call, session and invocation context plus an authorised decision; structured payload alone does not establish permission.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. A REST-based response; Confirmation with Resume feature

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse original-run approval continuity without matching call, session and invocation context plus an authorised decision; structured payload alone does not establish permission.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

ADK confirmation session-backend support

Question: Does ADK tool confirmation support every persistent session backend?

The captured experimental confirmation guide explicitly excludes DatabaseSessionService and VertexAiSessionService. Support for those services elsewhere in ADK does not establish support for this confirmation feature.

Source: Google ADK: action confirmations. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does ADK tool confirmation support every persistent session backend?

Buyer evidence still required

  • ADK language and installed version
  • Session service implementation
  • Confirmation feature and persistence requirements

Review inference: Refuse a supported durable-approval design without confirmation/backend compatibility for the deployed version; do not infer compatibility from general session support. The existing custom-agent review requires checkpoint implementation. This review concerns documented backend exclusions for the confirmation feature, which is a separate deployment-compatibility decision. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a supported durable-approval design without confirmation/backend compatibility for the deployed version; do not infer compatibility from general session support.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Known limitations; Experimental

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a supported durable-approval design without confirmation/backend compatibility for the deployed version; do not infer compatibility from general session support.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

ADK service ID-token target and lifetime boundary

Question: Can an ADK service-account ID token be reused as a general Google API access token?

ADK distinguishes audience-bound ID tokens for IAM-secured services from scoped access tokens for Google APIs. The documented ID-token path fetches at request time rather than refreshing on a background timer.

Source: Google ADK: authentication and credential management. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an ADK service-account ID token be reused as a general Google API access token?

Buyer evidence still required

  • Token kind and intended audience
  • Service IAM permissions
  • Issuance path and installed ADK version

Review inference: Refuse cross-service authority or unattended-refresh assumptions without the correct token type, target audience, IAM permission and issuance evidence. The MCP record concerns inbound versus upstream bearer authority. This review addresses ADK service-account token selection and request-time issuance for IAM services, not MCP token forwarding. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse cross-service authority or unattended-refresh assumptions without the correct token type, target audience, IAM permission and issuance evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Key takeaways; ServiceAccount configuration parameters

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse cross-service authority or unattended-refresh assumptions without the correct token type, target audience, IAM permission and issuance evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

ADK session token custody and authenticated user binding

Question: Does an ADK session backend automatically provide appropriate custody for refresh tokens?

ADK warns against assuming safe credential custody from session state. For self-managed interactive authentication it recommends user-bound encrypted storage; long-lived secrets belong in dedicated management rather than ordinary session memory.

Source: Google ADK: authentication and credential management. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an ADK session backend automatically provide appropriate custody for refresh tokens?

Buyer evidence still required

  • Credential types and storage locations
  • Authenticated user binding
  • Encryption, access and retention configuration

Review inference: Refuse a protected-token finding from SessionService selection alone; inspect credential location, authenticated-user binding, encryption and access controls. The Playwright record identifies browser authentication exports as sensitive. This decision concerns ADK session-held access/refresh tokens and the documented authenticated-user storage requirement, not browser export handling. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a protected-token finding from SessionService selection alone; inspect credential location, authenticated-user binding, encryption and access controls.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Credential storage and security risks; Self-managed authentication

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a protected-token finding from SessionService selection alone; inspect credential location, authenticated-user binding, encryption and access controls.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Admission webhooks: Failure policy and explicit denial

Question: Does an unavailable admission webhook always stop a Kubernetes change?

Failure policy controls webhook errors: Ignore permits the API request to continue, while Fail rejects it. This differs from a valid webhook response that explicitly denies the request, which is rejected regardless of failure policy. Matching rules and selectors also determine whether the webhook is called.

Source: Kubernetes dynamic admission control. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Installing an admission webhook proves every matching change is blocked when checks fail.

Buyer evidence still required

  • Matching rules, selectors and failure policy.
  • Timeout and error behaviour.
  • Admission outcome for the requested resource and operation.

Suggested review condition: Distinguish a missing check, a call failure and an explicit denial before claiming enforcement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Webhook rules, selectors, failure policy, availability and request outcome.

Optional saved evidence: Preserve a precise enforcement review for cluster admission controls.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

corpus staging complete not canonically imported

Advisory corpus staging: Historical pre-release checkpoint

Question: What does a completed advisory-staging run establish before public release?

At the historical staging checkpoint, the supplied report recorded 303,187 projected records from seven source snapshots, with no canonical import or public release and an upstream rights review still pending. Those statements describe that checkpoint, not the present service. A later release needs separate admission and deployment evidence; staging alone does not verify advisory truth.

Supplied evidence reviewed 2026-10-08. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • public availability established by the staging report
  • upstream redistribution review completed at that checkpoint
  • independent truth verification of the advisories
  • production retrieval or customer adoption established by staging

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

reported enrichment initial checkpoint

Advisory enrichment: Separate capture dates and coverage

Question: Does adding newer vulnerability context refresh the underlying advisory evidence?

The supplied S2 review reports enrichment of the existing advisory population with dated KEV and EPSS context, with no new OSV acquisition. The original advisory capture remains 8 October; feed acquisition and score dates are separate. Missing score joins remain unknown. At the initial 11 October review checkpoint the full archive was unavailable, so that review alone did not establish an activated import. The subsequently verified collection and its current import metadata are described at /index-advisories and /varexis-index/advisory-dataset.json; this record preserves the initial supplied-review boundary.

Supplied review examined 2026-10-11. The original archive and experiment were not independently rechecked during this intake.

Claim boundaries
  • refreshed underlying advisory assertions
  • missing scores treated as zero risk
  • new advisory acquisition
  • activation or full-output integrity established by the supplied review alone

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

reported mechanical validation only

Advisory projection: Mechanical retrieval validation

Question: Do exact-key retrieval checks establish that an advisory answer is true?

The supplied validation report records source-field and stream checks across the staged corpus, with successful exact-key probes and no reported pointer, stream or absent-key false-match failures. These are mechanical retrieval checks. They do not verify advisory truth, general question-answering quality or an affected-version decision for a buyer deployment.

Supplied evidence reviewed 2026-10-08. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • independent advisory fact checking
  • general semantic retrieval accuracy
  • full version-range evaluation
  • deployment-specific vulnerability assessment

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Adyen chargeback reversed not closed

Question: Does CHARGEBACK_REVERSED establish that the dispute is finally won?

Adyen can return the disputed amount while the issuer still reviews the defence. Its dispute guidance says CHARGEBACK_REVERSED can remain Pending and a second chargeback can follow. The financial credit and final dispute outcome must be reconciled separately for the applicable scheme flow.

Source: Adyen: Dispute process and flow. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does CHARGEBACK_REVERSED establish that the dispute is finally won?

Buyer evidence still required

  • payment and dispute PSP references
  • current dispute status
  • scheme flow
  • subsequent events and response deadline

Review inference: An operator treats returned funds as final resolution of a disputed purchase. The liability can reopen and the funds be debited again. Adds a dispute-defence lifecycle after payment processing, rather than capture validation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not close liability solely on a chargeback-reversal credit; inspect the final dispute outcome.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Chargeback Reversed

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not close liability solely on a chargeback-reversal credit; inspect the final dispute outcome.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Adyen payout booked credit evidence

Question: Does an Adyen payout booked event establish credit to the beneficiary bank?

Booked means the funds were deducted from the balance account and is not final. Adyen distinguishes later failures or returns, local-payout arrival estimates, and credited tracking for completed instant payouts. An estimate or outgoing debit does not establish the same outcome as a credit-confirmation event.

Source: Adyen: Payout webhooks. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an Adyen payout booked event establish credit to the beneficiary bank?

Buyer evidence still required

  • transfer ID
  • priority and rail
  • booked transaction
  • tracking and return events
  • beneficiary evidence

Review inference: An agent marks a supplier invoice paid after its platform balance is debited. A pending, failed or returned transfer may be mistaken for supplier receipt. The existing review addresses internal split allocation; this addresses an external-bank payout after balance-account debit. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse beneficiary-credit claims from booked or estimatedArrivalTime alone; apply the evidence available for that payout rail.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Payout transfer booked

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse beneficiary-credit claims from booked or estimatedArrivalTime alone; apply the evidence available for that payout rail.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Adyen refund remaining balance scope

Question: Can an agent refund the original captured amount without reconciling earlier refunds and chargebacks?

Adyen's refund validation uses the remaining payment balance, and cumulative partial refunds cannot exceed the captured amount. The guide's examples deduct prior refunds or chargebacks from the available balance. The original payment amount alone is insufficient input for a further refund decision.

Source: Adyen: Refund payments. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent refund the original captured amount without reconciling earlier refunds and chargebacks?

Buyer evidence still required

  • captured amount and currency
  • prior refunds and chargebacks
  • current payment balance
  • proposed refund amount and method support

Review inference: An agent issues another refund after a partial dispute adjustment. It may attempt an excessive or inconsistent return of funds. Adds remaining refundable-amount reconciliation, not selection of reversal versus cancellation/refund. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer remaining refund capacity from the original capture or authorise an amount without current reconciliation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Reasons for failed refund validation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer remaining refund capacity from the original capture or authorise an amount without current reconciliation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Adyen split instructions and actual recipient credit

Question: Does an accepted Adyen split payment prove that the intended balance account received the funds?

Adyen split instructions allocate sale proceeds, commission, fees and remainder between balance accounts. The request validates instruction format rather than the specified accounts. A nonexistent account or a closed account holder can cause the full transaction and fees to be booked to the platform liable account instead. Payment success therefore does not establish the intended allocation.

Source: Split payments at authorization | Adyen Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an accepted Adyen split payment prove that the intended balance account received the funds?

Buyer evidence still required

  • Submitted split instructions and intended balance-account identities
  • Account-holder state and relevant capabilities
  • Transfer updates and booked transaction records

Review inference: Reconcile the balance-platform transfer and transaction outcomes with the approved recipient allocation.

Suggested review condition: Do not mark the intended recipient funded from payment success or split-request acceptance alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual balance accounts, eligibility and final bookings require platform-specific evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Detect supplier-payment misallocation before treating a procurement obligation as fulfilled.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • The shopper-facing merchant label proving the eventual funds recipient
  • The actual balance accounts, eligibility and final bookings require platform-specific evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Adyen: A capture success event can be followed by failure

Question: Does an Adyen CAPTURE webhook with success true prove final settlement?

The successful CAPTURE event means the request passed validation and was submitted to the bank or processor. A later scheme rejection can produce CAPTURE_FAILED, including days after submission. Reconciliation needs later outcomes tied to the same capture reference.

Source: Capture | Adyen Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an Adyen CAPTURE webhook with success true prove final settlement?

Buyer evidence still required

  • Authorization and capture PSP references.
  • Authenticated CAPTURE and subsequent events.
  • Provider-side final outcome evidence.

Suggested review condition: Do not classify a submitted capture as independently verified settlement from CAPTURE success alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Authorization and capture PSP references. Authenticated CAPTURE and subsequent events. Provider-side final outcome evidence.

Optional saved evidence: Prevent premature closure of an agent payment reconciliation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Provider settlement verification, live recovery or a guarantee of payment success
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Adyen: Idempotency does not span regional endpoints

Question: Does reusing an Adyen idempotency key prevent duplicate payments across regional endpoints?

Adyen documents company-account scope for idempotency keys but says requests sent to multiple regional endpoints are not deduplicated across regions. Regional failover therefore needs reconciliation of the original attempt; the same key alone is not a cross-region exactly-once guarantee.

Source: Adyen API idempotency. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does reusing an Adyen idempotency key prevent duplicate payments across regional endpoints?

Buyer evidence still required

  • The company account, endpoint region and request key.
  • The original attempt and provider payment reference.
  • Regional recovery policy and verified transaction outcome.

Suggested review condition: Do not assume cross-region deduplication when retrying an unresolved payment on a different endpoint.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The company account, endpoint region and request key. The original attempt and provider payment reference. Regional recovery policy and verified transaction outcome.

Optional saved evidence: A payment platform owner must distinguish transport failover from safe recovery of an uncertain charge.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Permission to charge, live transaction reconciliation or guaranteed failover safety
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Adyen: Partial-capture modes treat the remainder differently

Question: Does an Adyen partial capture leave the unused authorization available for another shipment?

In single partial-capture mode, the unused authorized amount is cancelled. Multiple partial captures preserve the remaining amount, but that feature is disabled by default and requires enablement. A first partial capture alone does not prove authority or capacity for a second one.

Source: Capture | Adyen Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an Adyen partial capture leave the unused authorization available for another shipment?

Buyer evidence still required

  • Enabled capture mode.
  • Original authorization and cumulative captures.
  • Remaining authorization and shipment intent.

Suggested review condition: Do not plan a second capture without resolving whether the first released the remainder.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Enabled capture mode. Original authorization and cumulative captures. Remaining authorization and shipment intent.

Optional saved evidence: Review remaining declared authorization before an agent retries or captures another shipment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Issuer authorization validity, settlement or spending permission for additional captures
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Adyen: Reversal eligibility and final outcome are separate

Question: Can an agent use an Adyen reversal for every uncertain capture and treat acceptance as a completed refund?

Reversal chooses cancellation or refund according to capture state, but the documented flow excludes multiple partial captures and certain split-payment cases. A successful CANCEL_OR_REFUND validation can still be followed by refund failure or reversal. The request reference must remain linked to later outcomes.

Source: Reversal | Adyen Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent use an Adyen reversal for every uncertain capture and treat acceptance as a completed refund?

Buyer evidence still required

  • Capture history and split-payment details.
  • Reversal reference and validation event.
  • Later refund failure or reversal evidence.

Suggested review condition: Do not use the generic reversal path for an excluded case or equate request validation with final funds return.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Capture history and split-payment details. Reversal reference and validation event. Later refund failure or reversal evidence.

Optional saved evidence: Select a supported recovery path without declaring funds returned prematurely.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Execution of refunds, final bank outcome or universal reversal support
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AG-UI .NET and Python lifecycle capability boundary

Question: Does exposing a .NET Agent Framework workflow through AG-UI provide the Python workflow interrupt and resume mapping?

The captured .NET guidance exposes constituent-agent text and tool output but does not map workflow step events, activity snapshots, interrupts or Python-equivalent resume operations. Wrapping as AIAgent does not add them.

Source: Microsoft Agent Framework: AG-UI workflow integration. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does exposing a .NET Agent Framework workflow through AG-UI provide the Python workflow interrupt and resume mapping?

Buyer evidence still required

  • SDK language and installed adapter version
  • Required event and resume contract
  • Observed client/server capability mapping

Review inference: Refuse cross-language lifecycle parity based on the shared AG-UI name; require supported events and continuation operations for the installed implementation. The existing workflow overview says features vary by language. This review identifies the exact missing AG-UI lifecycle mapping relevant to a client migration or purchase decision. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse cross-language lifecycle parity based on the shared AG-UI name; require supported events and continuation operations for the installed implementation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. MAF .NET doesn't currently map; AsAIAgent

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse cross-language lifecycle parity based on the shared AG-UI name; require supported events and continuation operations for the installed implementation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AG-UI checkpoint ownership and legacy resume

Question: Does an Agent Framework checkpoint ID alone authorise AG-UI resume?

New checkpoints are bound to Snapshot Scope and threadId. Mismatches fail closed. Older ownerless checkpoints cannot resume through scoped or threaded requests; legacy unscoped, unthreaded resumes remain supported. Endpoint authorization remains separate.

Source: Microsoft Agent Framework: AG-UI workflow integration. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does an Agent Framework checkpoint ID alone authorise AG-UI resume?

Buyer evidence still required

  • Checkpoint ownership metadata and creation version
  • Authenticated request scope and thread ID
  • Endpoint authorization and legacy-path configuration

Review inference: Refuse ownership or access approval from possession of a checkpoint ID; establish endpoint authorization, scope/thread binding and legacy-path handling. The MCP record separates protocol handles from credentials. This decision adds the specific Microsoft AG-UI ownership filter and asymmetric legacy-resume boundary; it does not infer isolation from a generic handle. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse ownership or access approval from possession of a checkpoint ID; establish endpoint authorization, scope/thread binding and legacy-path handling.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Snapshot Scope; Legacy unthreaded

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse ownership or access approval from possession of a checkpoint ID; establish endpoint authorization, scope/thread binding and legacy-path handling.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AG-UI continuation thread identity

Question: Can an Agent Framework AG-UI continuation omit the thread ID returned at the start?

When the initial threadId is absent, the endpoint reports a generated ID in RUN_STARTED. Continuations use that ID. With workflow_factory, resume, tool-result or approval continuation without threadId fails before creating a new workflow.

Source: Microsoft Agent Framework: AG-UI workflow integration. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an Agent Framework AG-UI continuation omit the thread ID returned at the start?

Buyer evidence still required

  • Initial RUN_STARTED thread ID
  • Continuation request identity and kind
  • Configured workflow factory and response status

Review inference: Refuse continuity based on request order or identical text; bind continuation to the reported thread identity and retain failure evidence. The generic session record does not specify protocol continuation routing. This decision binds a concrete client continuation to the generated thread ID, separately from authenticating ownership of that ID. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse continuity based on request order or identical text; bind continuation to the reported thread identity and retain failure evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. If the initial request omits; WORKFLOW_RESUME_NOT_FOUND

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse continuity based on request order or identical text; bind continuation to the reported thread identity and retain failure evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AG-UI finished event and pending workflow interrupt

Question: Does an Agent Framework AG-UI RUN_FINISHED event prove the workflow completed its task?

The Python workflow adapter emits RUN_FINISHED with outcome.type set to interrupt when awaiting input. The event can contain pending interrupt details rather than a completed business outcome.

Source: Microsoft Agent Framework: AG-UI workflow integration. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an Agent Framework AG-UI RUN_FINISHED event prove the workflow completed its task?

Buyer evidence still required

  • RUN_FINISHED outcome and interrupt payload
  • Expected terminal workflow state
  • Action-specific completion evidence

Review inference: Refuse a completed-action finding from the event name alone; inspect the outcome and pending requests and reconcile any downstream action result. The existing Claude record concerns background control-traffic lifetime. This decision concerns a Microsoft AG-UI event whose finished label explicitly includes an interruption, a different protocol interpretation. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a completed-action finding from the event name alone; inspect the outcome and pending requests and reconcile any downstream action result.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. AG-UI Events Emitted by Workflows; outcome.type

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a completed-action finding from the event name alone; inspect the outcome and pending requests and reconcile any downstream action result.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AG-UI shared workflow instance versus thread factory

Question: Does supplying one workflow instance to Agent Framework AG-UI create isolated state for every thread?

The Python adapter accepts either a direct workflow or workflow_factory. Documentation reserves a direct instance for safely shared workflows and recommends a factory when each thread requires its own workflow state.

Source: Microsoft Agent Framework: AG-UI workflow integration. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does supplying one workflow instance to Agent Framework AG-UI create isolated state for every thread?

Buyer evidence still required

  • Direct-instance or factory configuration
  • Mutable executor state and sharing model
  • Thread construction and authorization evidence

Review inference: Refuse per-thread isolation claims from the endpoint wrapper alone; inspect shared mutable state and factory construction, alongside authorization controls. The ADK record addresses shared temporary state within an invocation. This review concerns cross-request workflow-instance reuse in a different adapter, a concrete construction decision rather than a generic isolation claim. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse per-thread isolation claims from the endpoint wrapper alone; inspect shared mutable state and factory construction, alongside authorization controls.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Direct instance; Thread-scoped factory

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse per-thread isolation claims from the endpoint wrapper alone; inspect shared mutable state and factory construction, alongside authorization controls.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AG-UI visible snapshot versus execution checkpoint

Question: Can restoring an AG-UI thread snapshot resume the Agent Framework executor state?

Workflow checkpoints preserve executor/runtime state and pending requests. AG-UI snapshots preserve replayable client output, shared state and the latest interrupt. Neither persistence mechanism substitutes for the other.

Source: Microsoft Agent Framework: AG-UI workflow integration. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can restoring an AG-UI thread snapshot resume the Agent Framework executor state?

Buyer evidence still required

  • Stored AG-UI snapshot
  • Corresponding runtime checkpoint
  • Thread, interrupt and restore evidence

Review inference: Refuse executable-recovery claims from a restored conversation display; reconcile the runtime checkpoint separately from the client-visible snapshot. The LangGraph review compares returned state with checkpointed state. This decision distinguishes two independently configured Microsoft persistence mechanisms for presentation and execution, affecting recovery design. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse executable-recovery claims from a restored conversation display; reconcile the runtime checkpoint separately from the client-visible snapshot.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Workflow checkpoints and AG-UI thread snapshots

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse executable-recovery claims from a restored conversation display; reconcile the runtime checkpoint separately from the client-visible snapshot.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Engine runtime identity selection

Question: Does deploying an Agent Engine mean downstream tools run with the deploying caller’s identity?

The reviewed AgentEngine reference supports an explicit service_account or AGENT_IDENTITY, with mutually exclusive configuration. AGENT_IDENTITY is resource-scoped and has no default project permissions. Otherwise the configured service account, or default Reasoning Engine Service Agent, is used. Deployment and runtime authority must be established separately.

Source: Class AgentEngine (2.6.0) | Python client libraries | Google Cloud Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does deploying an Agent Engine mean downstream tools run with the deploying caller’s identity?

Buyer evidence still required

  • SDK/API revision and deployed identity configuration
  • Effective runtime IAM grants
  • Separate deployment/service-agent and tool credentials

Review inference: Verify the deployed runtime identity and its grants for each downstream resource.

Suggested review condition: Do not infer runtime tool authority from the deployer’s identity or deployment success.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual runtime permissions and third-party credentials are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid overgranting or failed tool access caused by incorrect identity assumptions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic inheritance of the deployer’s permissions
  • Actual runtime permissions and third-party credentials are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Agent Framework automatic approval switch boundary

Question: Does disabling Agent Framework harness auto-approval remove a tool approval requirement?

In the documented Python harness, disable_tool_auto_approval removes its approval middleware but does not change the tool approval_mode. The ordinary user_input_requests flow still applies to approval-required tools.

Source: Microsoft Agent Framework: function tool approval. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does disabling Agent Framework harness auto-approval remove a tool approval requirement?

Buyer evidence still required

  • Harness configuration
  • Tool approval_mode declarations
  • Host handling of unresolved user_input_requests

Review inference: Refuse a no-approval-needed finding based only on the harness switch; inspect tool requirements and the host approval-response flow separately. The existing record compares the scope of two enabled skill approval rules. This review distinguishes disabling harness automation from removing a tool-level requirement, preventing an incorrect configuration inference. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a no-approval-needed finding based only on the harness switch; inspect tool requirements and the host approval-response flow separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. disable_tool_auto_approval=True; approval_mode

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a no-approval-needed finding based only on the harness switch; inspect tool requirements and the host approval-response flow separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework autonomous loop approval interruption

Question: Can an Agent Framework autonomous loop treat a pending tool approval as another iteration?

The Python AgentLoopMiddleware returns pending approval requests before evaluating its continuation predicate. It does not install approval handling itself. The host must resolve approval through the normal flow before continuing.

Source: Microsoft Agent Framework: autonomous looping. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an Agent Framework autonomous loop treat a pending tool approval as another iteration?

Buyer evidence still required

  • Loop and approval middleware configuration
  • Returned pending requests
  • Session and host continuation evidence

Review inference: Refuse task-completion or permission findings from a loop return alone; distinguish pending approval from satisfied completion and preserve the associated session. The existing SDK approval review describes resuming an interrupted run. This review addresses precedence between Microsoft autonomous-loop continuation and unresolved approval, and the absence of implicit approval middleware. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse task-completion or permission findings from a loop return alone; distinguish pending approval from satisfied completion and preserve the associated session.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Approval and session behavior; AgentLoopMiddleware

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse task-completion or permission findings from a loop return alone; distinguish pending approval from satisfied completion and preserve the associated session.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework changed arguments after approval

Question: Does an Agent Framework approval remain valid after middleware changes the tool arguments?

The Python guidance requires replacement approval for changed values only when JSON serialization and revalidation preserve those values exactly. Otherwise invocation fails with MiddlewareFailure; the earlier approval is not reused.

Source: Microsoft Agent Framework: function tool approval. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an Agent Framework approval remain valid after middleware changes the tool arguments?

Buyer evidence still required

  • Original approved tool arguments
  • Post-middleware values and conversion types
  • Replacement approval or MiddlewareFailure evidence

Review inference: Refuse approval continuity when executed arguments differ from reviewed arguments or exact revalidation cannot be demonstrated. The existing skill record distinguishes read-only and script approval rules. This decision concerns value changes after approval and exact conversion/revalidation, independently of which tool category was approved. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse approval continuity when executed arguments differ from reviewed arguments or exact revalidation cannot be demonstrated.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. If middleware changes already approved arguments; MiddlewareFailure

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse approval continuity when executed arguments differ from reviewed arguments or exact revalidation cannot be demonstrated.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework checkpoint deserialization trust

Question: Does Agent Framework restricted checkpoint deserialization make an untrusted checkpoint safe?

Microsoft treats checkpoint storage as trusted private infrastructure. Restricted unpickling and allowed types do not make untrusted pickle data safe; permitted classes can carry reconstruction behaviour.

Source: Microsoft Agent Framework: checkpoint storage and restore. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Agent Framework restricted checkpoint deserialization make an untrusted checkpoint safe?

Buyer evidence still required

  • Checkpoint provenance and content identity
  • Storage access controls
  • Allowed types and installed decoder version

Review inference: Refuse to treat a foreign or tampered checkpoint as safe solely because its types are allowed; require trusted provenance and protected storage. The existing record withholds generic persistence and isolation guarantees. This decision identifies the documented executable-deserialization trust boundary and why a type allowlist cannot establish source trust. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse to treat a foreign or tampered checkpoint as safe solely because its types are allowed; require trusted provenance and protected storage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Checkpoint storage is a trust boundary; neither makes untrusted pickle data safe

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to treat a foreign or tampered checkpoint as safe solely because its types are allowed; require trusted provenance and protected storage.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework checkpoint identity across redeployment

Question: Can rebuilding a .NET Agent Framework workflow with new agent IDs resume its old checkpoints?

The .NET resume contract requires the same workflow structure and executor identities. Agent IDs and configured names must stay stable. Assigning stable values later does not repair old checkpoints created with different identities.

Source: Microsoft Agent Framework: checkpoint storage and restore. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can rebuilding a .NET Agent Framework workflow with new agent IDs resume its old checkpoints?

Buyer evidence still required

  • Original workflow structure and executor IDs
  • Reconstructed agent IDs and names
  • Checkpoint lineage and installed .NET version

Review inference: Refuse compatible-resume claims across redeployment without matching structure, IDs and names; retain or explicitly replace the old checkpoint lineage. The existing workflow record only establishes structured orchestration. This review specifies the .NET identity conditions for cross-instance rehydration and the non-retroactive nature of correcting IDs. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse compatible-resume claims across redeployment without matching structure, IDs and names; retain or explicitly replace the old checkpoint lineage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. same structure and executor identities; Assigning stable values

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse compatible-resume claims across redeployment without matching structure, IDs and names; retain or explicitly replace the old checkpoint lineage.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework checkpoint listing completeness

Question: Does Agent Framework get_latest prove it considered every checkpoint file on disk?

FileCheckpointStorage listings and get_latest skip malformed or undecodable files using the decoding path. Its save operation also refuses data that the same configured instance cannot restore.

Source: Microsoft Agent Framework: checkpoint storage and restore. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Agent Framework get_latest prove it considered every checkpoint file on disk?

Buyer evidence still required

  • Storage file inventory and timestamps
  • Decoder and allowed types
  • Returned entries and save or decode failures

Review inference: Refuse a complete-checkpoint-inventory or newest-written-state finding from the returned list alone; reconcile file inventory and decoding failures. The existing record concerns whether session storage is durable. This decision concerns selection bias in a decodable-file listing, affecting recovery selection and audit completeness even when storage persists. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a complete-checkpoint-inventory or newest-written-state finding from the returned list alone; reconcile file inventory and decoding failures.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Before writing; skip malformed

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a complete-checkpoint-inventory or newest-written-state finding from the returned list alone; reconcile file inventory and decoding failures.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework checkpoint provider durability

Question: Does using an Agent Framework checkpoint provider imply cross-process recovery?

The documented Python providers have different durability: InMemoryCheckpointStorage is process-local, FileCheckpointStorage uses local disk, and CosmosCheckpointStorage supports distributed persistence. A shared interface does not equal shared durability.

Source: Microsoft Agent Framework: checkpoint storage and restore. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does using an Agent Framework checkpoint provider imply cross-process recovery?

Buyer evidence still required

  • Configured provider and storage location
  • Process and deployment storage lifecycle
  • Recovery access and persistence evidence

Review inference: Refuse restart or cross-instance recovery guarantees without the actual backend, storage lifecycle and recovery evidence; an in-memory checkpoint is insufficient. The generic record withholds durability claims but does not distinguish implementations. This review supplies the documented backend selection boundary needed to choose a recovery architecture without assuming interface equivalence. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse restart or cross-instance recovery guarantees without the actual backend, storage lifecycle and recovery evidence; an in-memory checkpoint is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Durability; InMemoryCheckpointStorage

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse restart or cross-instance recovery guarantees without the actual backend, storage lifecycle and recovery evidence; an in-memory checkpoint is insufficient.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework checkpoint type-registration scope

Question: Does registering an Agent Framework checkpoint type affect only the current storage instance?

register_checkpoint_type expands decoding permissions across the Python process, including existing storage instances. allowed_checkpoint_types instead applies to its receiving store or provider. Both extend the restricted deserializer.

Source: Microsoft Agent Framework: checkpoint storage and restore. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does registering an Agent Framework checkpoint type affect only the current storage instance?

Buyer evidence still required

  • Registration mechanism and timing
  • Affected stores and providers
  • Trusted class identities and reconstruction behaviour

Review inference: Refuse a store-local change assessment for global registration; inventory every decoder affected and require justification for each trusted additional type. The generic session-state record does not identify the blast radius of decoder registration. This review separates process-wide permission changes from per-store configuration, distinct from whether checkpoint bytes are trusted. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a store-local change assessment for global registration; inventory every decoder affected and require justification for each trusted additional type.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Global registration also applies; allowed_checkpoint_types

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a store-local change assessment for global registration; inventory every decoder affected and require justification for each trusted additional type.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework missing checkpoint session defaults

Question: Does a successful Agent Framework checkpoint restore prove the original agent session was preserved?

AgentExecutorCheckpointState defaults missing known fields, creating a new agent session when agent_session is absent. Unknown fields are ignored; malformed known fields raise WorkflowCheckpointException.

Source: Microsoft Agent Framework: checkpoint storage and restore. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a successful Agent Framework checkpoint restore prove the original agent session was preserved?

Buyer evidence still required

  • Original required checkpoint fields
  • Stored AgentExecutorCheckpointState
  • Restored session identity and validation outcomes

Review inference: Refuse original-session continuity based only on successful decoding; inspect required saved fields and restored identity, including defaults and ignored fields. The earlier record makes no implementation-specific continuity promise. This review identifies a concrete successful-restore path that defaults to a new session, separating parse success from retained context. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse original-session continuity based only on successful decoding; inspect required saved fields and restored identity, including defaults and ignored fields.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. AgentExecutorCheckpointState; Missing known fields

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse original-session continuity based only on successful decoding; inspect required saved fields and restored identity, including defaults and ignored fields.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework pending approval and session binding

Question: Can an Agent Framework approval response authorise a call absent from the current session?

For the documented Python default, approval must match a pending request in the same AgentSession. Unbound responses are ignored with a warning. Disabling approval-response binding restores unbound behaviour and requires equivalent application-side validation.

Source: Microsoft Agent Framework: function tool approval. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an Agent Framework approval response authorise a call absent from the current session?

Buyer evidence still required

  • Installed framework version and binding setting
  • Pending request and tool-call identity
  • Session identity and authorised decision source

Review inference: Refuse an authorised-call finding without the matching pending request, session and effective binding configuration; a supplied approval message alone is insufficient. The existing OpenAI SDK review explains interrupt continuation. This review concerns Microsoft Python pending-request matching and a specific opt-out that changes trust in caller-supplied approval responses. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse an authorised-call finding without the matching pending request, session and effective binding configuration; a supplied approval message alone is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. By default, a local approval response; disable_approval_response_binding

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse an authorised-call finding without the matching pending request, session and effective binding configuration; a supplied approval message alone is insufficient.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Framework standing approvals across tool replacement

Question: Can a replacement Agent Framework tool inherit a saved approval through its name?

The Python harness stores standing approvals in AgentSession, not on a particular agent or tool instance. A replacement with the same name, including an MCP tool, can match a saved tool-wide or argument-specific rule.

Source: Microsoft Agent Framework: function tool approval. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a replacement Agent Framework tool inherit a saved approval through its name?

Buyer evidence still required

  • Session standing rules
  • Previous and replacement tool identities and definitions
  • Required approval scope after replacement

Review inference: Refuse unchanged-authority conclusions after agent or tool replacement until saved rules and the current tool identity are reviewed; start a new session when approval must not carry forward. The existing record identifies which skill tool names an approval rule covers. This review addresses persistence of those rules across replacement instances, a separate change-admission and session-reuse decision. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse unchanged-authority conclusions after agent or tool replacement until saved rules and the current tool identity are reviewed; start a new session when approval must not carry forward.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Standing approvals persist in; replacement tool

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse unchanged-authority conclusions after agent or tool replacement until saved rules and the current tool identity are reviewed; start a new session when approval must not carry forward.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Agent Protocol: Platform superset boundary

Question: Does a platform implementing a superset of Agent Protocol guarantee every client's compatibility?

Agent Protocol documentation describes LangGraph Platform as implementing a superset of the protocol. Additional platform features do not prove that every client, extension or version interoperates; compatibility requires a match between the specific interfaces in use.

Source: Agent Protocol. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • compatibility with every client
  • portable platform-specific extensions
  • deployment conformance test

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Agent Protocol: Runs and state interface

Question: What does Agent Protocol standardise for agent runs and state?

Agent Protocol documents a framework-independent interface organised around runs, conversational threads and persistent stores. This describes an API model; it does not establish a particular server's behaviour, permissions or client compatibility.

Source: Agent Protocol. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • verified server implementation
  • permission to execute tools
  • universal client compatibility

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Agent workflows: Parallel tasks or a dependent sequence

Question: Should agents run in parallel when one task needs another agent's output?

Microsoft's Semantic Kernel guide describes concurrent orchestration as independent processing of a shared task, while sequential orchestration passes each result to the next agent in order. Choose the pattern around the actual data dependency; a later task that needs an earlier result is not independent. These orchestration features are documented as experimental. The pattern description establishes neither application correctness nor a measured speed or cost benefit.

Source: Microsoft: Semantic Kernel Agent Orchestration. Documentation checked 2026-10-11; no deployment validation is claimed.

Claim boundaries
  • application performance or reliability from a pattern name
  • independence of tasks that consume earlier outputs
  • production maturity of experimental orchestration

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AgentCore compute lifetime and session persistence

Question: Does an AgentCore idle timeout necessarily invalidate the session identifier and erase every persisted state?

AgentCore documents that idle or maximum-lifetime limits can stop the session’s compute. A later invocation can provision new compute; the session identifier remains valid until the Runtime ARN is deleted. Configured session storage can preserve its mounted filesystem across stop/resume, while ordinary in-memory or ephemeral disk state does not gain that persistence.

Source: Use isolated sessions for agents - Amazon Bedrock AgentCore. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an AgentCore idle timeout necessarily invalidate the session identifier and erase every persisted state?

Buyer evidence still required

  • Runtime lifecycle settings and compute mode
  • Session identifier and Runtime ARN
  • Session-storage mounts and separately persisted state

Review inference: Distinguish compute lifetime, session identity and configured state storage when planning recovery or offboarding.

Suggested review condition: Do not equate compute timeout with deletion of all session state or identity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual restored state and the buyer’s storage configuration are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Make recovery and offboarding decisions against the correct lifetime boundary.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed indefinite compute or verified data deletion
  • Actual restored state and the buyer’s storage configuration are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AgentCore Gateway Policy: Tool checks exclude prompts and resources

Question: Does AgentCore Gateway Policy apply its tool rules to MCP prompts and resources?

AgentCore documents Policy evaluation for MCP tools only. Its Policy layer allows the listed prompt and resource methods regardless of evaluation mode. Gateway authentication and other access controls remain separate. A tool-policy configuration therefore does not establish equivalent policy coverage for prompts or resources.

Source: Use an AgentCore Gateway with Policy in AgentCore. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does AgentCore Gateway Policy apply its tool rules to MCP prompts and resources?

Buyer evidence still required

  • Gateway identity, configured Policy mode and engine binding
  • MCP methods exposed by each target
  • Authentication and separate controls for prompts and resources

Review inference: The review should enumerate protected methods and controls outside the tool-policy layer.

Suggested review condition: Refuse a claim that tool policies govern every MCP method without method-specific evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer exposed methods, other control layers and effective request decisions are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Expose method-level gaps before relying on an agent gateway's permission declaration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Unauthenticated public access, absence of other controls or a proven bypass in a buyer deployment
  • INDEX enforcement or validation of a deployed gateway
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AgentCore Gateway: CloudTrail capture needs the Gateway data-event selector

Question: Which CloudTrail data-event resource selector is required for AgentCore Gateway requests?

The AgentCore Gateway guide requires explicitly enabled CloudTrail data events, an S3-backed trail and advanced event selectors for gateway operations. Its selector uses eventCategory Data and resources.type AWS::BedrockAgentCore::Gateway. These data events are not captured by default. A general trail configuration alone does not establish that the relevant Gateway requests were selected or delivered.

Source: Enable CloudTrail data event logging for Amazon Bedrock AgentCore Gateway resources. Documentation checked 2026-10-23; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Which CloudTrail data-event resource selector is required for AgentCore Gateway requests?

Buyer evidence still required

  • Trail configuration including eventCategory and AWS::BedrockAgentCore::Gateway resource selection
  • Target gateway, account, Region and period covered by the selector
  • Delivered S3 event evidence and filters used to reconcile the relevant requests

Review inference: A gateway-specific review should compare its resource selector and delivered events with the requested scope rather than infer coverage from a trail existing.

Suggested review condition: Refuse Gateway request-completeness claims without the specific data-event selector and delivered event evidence for the period.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer selector, logging start time, delivery state, retained events and query omissions are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a gateway audit from relying on a trail that never selected the agent operations under review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete audit capture, retrospective recovery of unlogged requests or successful S3 log delivery
  • Proof of tool execution, correct agent reasoning or downstream action completion from a logging configuration
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AgentCore Gateway: Configuration authority can disable policy enforcement

Question: Can AgentCore UpdateGateway authority downgrade or detach a gateway policy engine?

AWS documents that bedrock-agentcore:UpdateGateway permits changing policyEngineConfiguration.mode from ENFORCE to LOG_ONLY, or setting policyEngineConfiguration to null to remove the engine. The mode field has no separate protecting action or condition key beyond UpdateGateway. A review must therefore include who can change gateway configuration, as well as who can call its tools.

Source: Policy enforcement modes. Documentation checked 2026-10-23; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can AgentCore UpdateGateway authority downgrade or detach a gateway policy engine?

Buyer evidence still required

  • Principal and effective IAM authorization for the specific gateway UpdateGateway action
  • Previous and current gateway policy-engine identity and mode
  • Change approval, configuration history and request-period evidence

Review inference: Configuration-changing authority belongs in the authority review even when the agent has restricted tool-call access.

Suggested review condition: Refuse a stable-enforcement claim that omits principals able to change or remove the gateway policy engine.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Effective buyer IAM access, organisational controls, approved changes and actual configuration history are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify configuration administrators whose access can remove the permission boundary an agent workflow relies on.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A finding that a particular principal has effective UpdateGateway access after all applicable IAM controls
  • Proof that a downgrade occurred or that removing this policy engine bypasses all other controls
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AgentCore Gateway: Default listings need explicit refresh after upstream changes

Question: Does AgentCore Gateway automatically reflect independently changed MCP tools in DEFAULT listing mode?

DEFAULT listing mode discovers capabilities during target creation or updates and through explicit SynchronizeGatewayTargets calls. AWS directs operators to synchronize after upstream definitions change. Synchronization is asynchronous, so acceptance is not completion. DYNAMIC mode forwards discovery requests and has different documented compatibility limits.

Source: MCP servers targets. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does AgentCore Gateway automatically reflect independently changed MCP tools in DEFAULT listing mode?

Buyer evidence still required

  • Target listing mode and any explicitly supplied schema
  • Upstream definition revision and gateway inventory revision
  • Synchronization request identity and completed target status

Review inference: A current inventory claim needs the listing mode and completed synchronization evidence.

Suggested review condition: Refuse a current-schema claim based solely on target creation history or synchronization acceptance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer upstream changes, configured listing mode and latest completed synchronization are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid approving tools against an outdated definition or incomplete refresh.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A guarantee that a particular gateway inventory is stale or that synchronization validates tool behavior
  • Equivalence between DEFAULT, DYNAMIC and explicitly supplied schema configurations
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AgentCore Memory: Event deletion leaves derived long-term records

Question: Does deleting an AgentCore event also delete long-term memory extracted from it?

AgentCore DeleteEvent removes an individual event. AWS explicitly states that this does not remove structured information derived from it in long-term memory and points to DeleteMemoryRecord for that separate operation. Deleting the source event therefore does not establish removal of its derived memory.

Source: Delete an event. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting an AgentCore event also delete long-term memory extracted from it?

Buyer evidence still required

  • Memory, actor, session and event identifiers
  • Derived memory record inventory and available source associations
  • Separate deletion results and declared residual-data scope

Review inference: The exit review needs separate source-event and derived-memory evidence.

Suggested review condition: Refuse an all-memory-deleted claim based only on a successful DeleteEvent operation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer derived-record lineage, deletion results and other retained copies are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Account for derived agent memory when closing a data-exit or deletion request.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete deletion across backups, logs, other stores or the buyer application
  • A verified association between a specific event and every derived record
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AgentCore Policy: Active rules still depend on gateway enforcement mode

Question: Does an ACTIVE AgentCore policy enforce its decision when the gateway is in LOG_ONLY mode?

AgentCore separates gateway policy-engine mode from each policy's enforcement mode. Gateway LOG_ONLY records decisions without enforcing any policy, including ACTIVE policies. With gateway ENFORCE, ACTIVE policies contribute to the enforced decision while individual LOG_ONLY policies are evaluated separately. Both settings must be checked; a policy status or denial trace alone does not establish blocking.

Source: Test a policy in LOG_ONLY mode. Documentation checked 2026-10-23; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an ACTIVE AgentCore policy enforce its decision when the gateway is in LOG_ONLY mode?

Buyer evidence still required

  • Gateway policyEngineConfiguration mode and attached engine identity
  • Individual policy enforcementMode and applicable policy definitions
  • Dated invocation, effective decision and downstream outcome evidence

Review inference: Review evidence should bind both mode settings to the invocation period before relying on a claimed policy denial.

Suggested review condition: Refuse an enforced-denial claim based only on an ACTIVE policy label or a LOG_ONLY decision trace.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer gateway settings, applicable policies, other controls and actual request outcome are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid approving a deployment whose expected permission rules are only being observed rather than applied.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof that a particular request was blocked or that every MCP method is covered
  • A claim that LOG_ONLY disables gateway authentication or all other access controls
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AgentCore version, endpoint and existing-session binding

Question: Does publishing an AgentCore Runtime update put every endpoint and existing session on the new version?

AgentCore Runtime updates create immutable versions. DEFAULT tracks the latest version, while custom endpoints require an explicit version update. The lifecycle guidance states that an existing microVM continues with the version used when it was created until termination; a version publication is not evidence that every active execution changed.

Source: AgentCore Runtime versioning and endpoints - Amazon Bedrock AgentCore. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does publishing an AgentCore Runtime update put every endpoint and existing session on the new version?

Buyer evidence still required

  • Published version and endpoint mapping
  • Session or compute creation/version evidence
  • Cutover and termination policy

Review inference: Reconcile endpoint selection and existing compute/session version before accepting a handover.

Suggested review condition: Refuse uniform-version claims from publication or DEFAULT alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Which version the buyer’s existing sessions actually run is unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent mixed-version execution from being overlooked during deployment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic forced migration or termination of every session
  • Which version the buyer’s existing sessions actually run is unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Agents API discovery directories versus filesystem authority

Question: Does registering an Agents API capability directory limit all filesystem access to that directory?

Capability directories identify existing absolute, unique sandbox paths for skill discovery; the guide disallows dot path segments and limits registration to 32 directories. Discovery paths are not documented as a general filesystem permission boundary.

Source: OpenAI primary documentation: openai skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does registering an Agents API capability directory limit all filesystem access to that directory?

Buyer evidence still required

  • capability directories
  • discovered manifests
  • sandbox filesystem policy
  • session configuration

Review inference: Does registering an Agents API capability directory limit all filesystem access to that directory? Do not infer containment from directory registration; separately review effective sandbox filesystem permissions. Agents API discovery directories versus filesystem authority. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer containment from directory registration; separately review effective sandbox filesystem permissions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Capability directories have these requirements

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer containment from directory registration; separately review effective sandbox filesystem permissions.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AI Gateway fallback identity and cost attribution

Question: Does using one AI Gateway endpoint mean every fallback request used the same model and cost basis?

Vercel AI Gateway can try different models and providers after a failure, and providers have different pricing characteristics. The modelAttempts metadata identifies attempted models and provider attempts. The guide warns that some normalized Python beta metadata can omit routing details, requiring the raw response or request logs.

Source: AI Gateway Model Fallbacks. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does using one AI Gateway endpoint mean every fallback request used the same model and cost basis?

Buyer evidence still required

  • Requested and actual model/provider identifiers
  • Fallback attempt metadata or raw request logs
  • Usage and applicable billing records

Review inference: Reconcile the served model/provider and measured usage before assigning request cost.

Suggested review condition: Do not infer the served model or cost basis from the shared endpoint alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Which attempts were billed and the final invoice are not established by routing metadata alone.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a successful fallback from being costed against the wrong model.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A claim that every failed provider attempt is billable
  • Which attempts were billed and the final invoice are not established by routing metadata alone.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AI-assisted bids need proportionate verification

Question: Should a supplier be excluded merely because AI helped write its bid?

PPN 017 says supplier AI use in the commercial process is not prohibited. It describes optional disclosure questions and proportionate due diligence into tender accuracy, capacity and capability. Review implication: AI-use disclosure alone cannot establish delivery capability or automatic exclusion authority. Request evidence against specific tender uncertainties.

Source: Cabinet Office PPN 017. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Should a supplier be excluded merely because AI helped write its bid?

Buyer evidence still required

  • Procurement scope and start date
  • Supplier AI-use declaration tied to the tender
  • Specific ambiguous claims and dated capacity/capability evidence

Review inference: AI-use disclosure alone cannot establish delivery capability or automatic exclusion authority. Request evidence against specific tender uncertainties.

Suggested review condition: Do not infer capability or an exclusion ground from AI disclosure alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK central government departments, executive agencies and non-departmental public bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • Do not infer capability or an exclusion ground from AI disclosure alone.
  • A well-evidenced AI-assisted bid can remain eligible; disclosure is neither automatic disqualification nor proof of competence.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Aikido MCP: Submitted code and selected findings

Question: Does connecting Aikido MCP prove all generated code and repository issues were checked?

Tools distinguish files on disk, supplied code content, dependency manifests and scoped issue retrieval. Issue filters and pagination affect the returned subset. The Copilot cloud-agent integration uses a personal access token because browser login is unavailable there. An installed connector or prompt instruction does not prove a scan ran on every change.

Source: Aikido: Using MCP. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer deployment unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Aikido publishes the MCP integration and operates the associated service.

Documented by publisher. Aikido: Using MCP; Aikido: Copilot MCP configuration

Purpose

Scan selected code or dependencies and retrieve scoped security findings.

Documented by publisher. Aikido: Using MCP; Aikido: Copilot MCP configuration

Read capability

Supplied file content, selected disk paths and permitted issue-feed results.

Documented by publisher. Aikido: Using MCP; Aikido: Copilot MCP configuration

Write capability

Scan operations perform analysis; the reviewed guides do not establish arbitrary repository-write permissions.

Not established. Aikido: Using MCP; Aikido: Copilot MCP configuration

Authentication

The documented Copilot cloud-agent setup uses an Aikido personal access token.

Documented by publisher. Aikido: Using MCP; Aikido: Copilot MCP configuration

Permission surface

Input paths, account permissions and issue scope need explicit buyer review.

Documented by publisher. Aikido: Using MCP; Aikido: Copilot MCP configuration

Data leaving the environment

Code inputs and returned findings enter the scanning and assistant workflow; exact transfer and retention are unverified.

Review inference. Aikido: Using MCP; Aikido: Copilot MCP configuration

Failure modes to consider

Unsaved content, wrong paths, restrictive filters or incomplete pagination can leave gaps.

Review inference. Aikido: Using MCP; Aikido: Copilot MCP configuration

Unknowns and applicability

Actual token grants, scan execution, client configuration and transmitted payload remain untested.

Not established

Suggested refusal or clarification condition

Require approved code scope and a matching completed result before relying on coverage.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Changing tools, issue filters, client authentication and input handling.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the input and coverage questions behind an AI-assisted code review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

aiohttp: Separate HTTP client usage from static-file serving

Question: Does an agent using aiohttp only as an HTTP client match the static-file traversal conditions?

The aiohttp advisory for CVE-2024-23334 concerns web-server static routes configured with follow_symlinks enabled. It says traversal can occur even without actual symlinks. Client-only use does not establish those server conditions. Review registered static routes and configuration, not just package presence. The maintainer lists 3.9.2 as patched and still advises against enabling this option for remotely accessible production serving. The maintainer's lower-bound field and frozen range differ at 1.0.5; do not infer safety for that boundary version from this review.

Source: aiohttp maintainer advisory: CVE-2024-23334. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • client-only use classified as confirmed static-route exposure
  • absence of symlinks treated as proof of safety
  • boundary-version discrepancy resolved or file disclosure verified

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Airbyte MCP: Pipeline identity and upstream reads

Question: Does an Airbyte agent read upstream data as the signed-in person?

Pipeline operations use the signed-in Airbyte user, or the user who created an application credential. Direct source reads instead use credentials stored in the selected connector. The open-beta server can also change pipelines and start syncs. A successful sign-in does not establish row-level user impersonation in the upstream system.

Source: Airbyte MCP tools and acting identities. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; deployed buyer configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Airbyte operates the hosted Cloud server.

Documented by publisher. Airbyte MCP tools and acting identities; Install and authenticate Airbyte MCP

Purpose

Inspect and manage data replication pipelines.

Documented by publisher. Airbyte MCP tools and acting identities; Install and authenticate Airbyte MCP

Read capability

Pipeline metadata, logs and enabled direct source reads.

Documented by publisher. Airbyte MCP tools and acting identities; Install and authenticate Airbyte MCP

Write capability

Configured tools can change connectors and start or cancel syncs.

Documented by publisher. Airbyte MCP tools and acting identities; Install and authenticate Airbyte MCP

Authentication

User OAuth or an Airbyte application credential.

Documented by publisher. Airbyte MCP tools and acting identities; Install and authenticate Airbyte MCP

Permission surface

Airbyte roles select connectors; their stored credentials govern upstream records.

Documented by publisher. Airbyte MCP tools and acting identities; Install and authenticate Airbyte MCP

Data leaving the environment

Connector data and logs can reach the connected agent.

Review inference. Airbyte MCP tools and acting identities; Install and authenticate Airbyte MCP

Failure modes to consider

A different default workspace or broad connector credential can change the effective scope.

Review inference. Airbyte MCP tools and acting identities; Install and authenticate Airbyte MCP

Unknowns and applicability

Context-layer enablement and actual connector grants are unverified.

Not established

Suggested refusal or clarification condition

Require the connector identity and permitted data scope before reading business records.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Context-layer settings, connector grants, default workspace and open-beta tool changes.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the distinction between pipeline access and upstream data identity for an integration approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Airtable CSV: Attachment links are not archived files

Question: Does an Airtable CSV export preserve everything needed to leave the service?

CSV export is view/table based and includes visible field values. It omits several non-field objects, and attachments appear as filenames and expiring URLs rather than embedded files. A full exit plan needs separate attachment capture, view-filter checks and an inventory of omitted content.

Source: Airtable views and CSV export. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A CSV download is a complete portable base backup.

Buyer evidence still required

  • Exported tables, views and filters.
  • Downloaded attachment files and manifest.
  • Omitted comments, descriptions and extension data.

Suggested review condition: Require complete artifact coverage before declaring export readiness.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Exported view, filters, attachments, omitted objects and target import

Optional saved evidence: Save the file and non-tabular gaps that a procurement exit plan must resolve.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Airtable MCP: Base access and automation drafts

Question: Can an agent update my Airtable records without activating an automation?

Airtable documents record editing through MCP within the permissions of the connected user. Automation changes are saved as drafts and activation happens in the Airtable interface. Record-write access and permission to activate an automation are separate review questions; verify the selected bases, granted scopes and intended operation.

Source: Airtable MCP capabilities, permissions and automation drafts. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Airtable hosted server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Airtable operates the documented hosted MCP service.

Documented by publisher. Airtable MCP capabilities, permissions and automation drafts

Purpose

Connect an assistant to base data and supported workspace operations.

Documented by publisher. Airtable MCP capabilities, permissions and automation drafts

Read capability

Reads accessible records, interfaces and automation configuration.

Documented by publisher. Airtable MCP capabilities, permissions and automation drafts

Write capability

Creates or updates records and automation drafts; activation remains in the Airtable interface.

Documented by publisher. Airtable MCP capabilities, permissions and automation drafts

Authentication

OAuth connections and personal access tokens are documented.

Documented by publisher. Airtable MCP capabilities, permissions and automation drafts

Permission surface

Existing user permissions and the selected integration resources constrain access.

Documented by publisher. Airtable MCP capabilities, permissions and automation drafts

Data leaving the environment

Returned base data enters the connected assistant; assess that assistant separately.

Review inference. Airtable MCP capabilities, permissions and automation drafts

Failure modes to consider

Ambiguous base selection or treating a draft as active can produce a mistaken outcome.

Review inference. Airtable MCP capabilities, permissions and automation drafts

Unknowns and applicability

The actual integration grants and buyer automation state have not been inspected.

Not established

Suggested refusal or clarification condition

Require an identified base and authorised change; do not report an automation as active from draft creation alone.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck after base grants, scopes or automation capabilities change.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the access and draft/activation distinction used when approving a records task.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Aiven MCP: Read-only exceptions and service scope

Question: Can an Aiven connection marked read-only still expose selected write tools?

Yes. Aiven documents an optional write allowlist that re-enables named actions in read-only mode. Service-family selection also leaves core discovery available. Review the complete configuration and authenticated user permissions, rather than treating one read-only label as the whole permission boundary.

Source: Aiven MCP credentials, service operations and SQL. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted and local variants

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Aiven publishes the local server and hosts the remote variant.

Documented by publisher. Aiven MCP credentials, service operations and SQL

Purpose

Manage Aiven data services and applications.

Documented by publisher. Aiven MCP credentials, service operations and SQL

Read capability

Reads service information, logs, database data and Kafka messages.

Documented by publisher. Aiven MCP credentials, service operations and SQL

Write capability

Can change services, data and messages; configured exceptions can restore writes in read-only mode.

Documented by publisher. Aiven MCP credentials, service operations and SQL

Authentication

Hosted authorisation or a local Aiven API token.

Documented by publisher. Aiven MCP credentials, service operations and SQL

Permission surface

User permissions apply alongside read-only, service-scope and write-allowlist settings.

Documented by publisher. Aiven MCP credentials, service operations and SQL

Data leaving the environment

Service content and possibly connection material can reach the assistant.

Review inference. Aiven MCP credentials, service operations and SQL

Failure modes to consider

An overlooked write exception can invalidate a read-only assumption.

Review inference. Aiven MCP credentials, service operations and SQL

Unknowns and applicability

Buyer exceptions, secret exposure settings and effective account rights are unknown.

Not established

Suggested refusal or clarification condition

Inspect write exceptions before approving a read-only task.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck write allowlists, service scope and user-role changes.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the complete permission checklist for a managed-data connector review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Algolia MCP: Public search, user analytics and code examples

Question: Does every Algolia MCP connection access and modify my search indices?

No. Current documentation distinguishes application-scoped Public MCP, user-scoped Productivity MCP and DevEx code generation. Public and Productivity are read-only; DevEx does not access application data. Identify the offering before claiming either data access or write capability.

Source: Algolia MCP permission selection and index operations. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Public, Productivity and DevEx services

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Algolia operates the three documented MCP offerings.

Documented by publisher. Algolia MCP permission selection and index operations

Purpose

Expose search, internal analysis or API-client examples depending on the offering.

Documented by publisher. Algolia MCP permission selection and index operations

Read capability

Public searches selected application data; Productivity adds user-permitted analytics.

Documented by publisher. Algolia MCP permission selection and index operations

Write capability

Public and Productivity do not change indices; DevEx generates code without application-data access.

Documented by publisher. Algolia MCP permission selection and index operations

Authentication

Productivity uses individual Algolia login; DevEx needs no authentication.

Documented by publisher. Algolia MCP permission selection and index operations

Permission surface

Public is application-scoped; Productivity follows user permissions.

Documented by publisher. Algolia MCP permission selection and index operations

Data leaving the environment

Search or analytics results reach the client; generated code is a separate output.

Review inference. Algolia MCP permission selection and index operations

Failure modes to consider

Confusing code-generation access with live data access can misstate the integration.

Review inference. Algolia MCP permission selection and index operations

Unknowns and applicability

Buyer Public-MCP grants and selected indices have not been inspected.

Not established

Suggested refusal or clarification condition

Identify the offering and scope before asserting data access or change capability.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck offering definitions, selected indices and user permissions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the offering distinction for a search-connector procurement decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock AgentCore Runtime: Outbound authentication

Question: Does outbound authentication from AgentCore Runtime prove a tool action is permitted?

AWS documents AgentCore Runtime integration with Identity for outbound authentication to services using OAuth or API keys. Authenticating a connection does not establish that the requested operation, resource or delegated scope is permitted for the user’s task.

Source: Host agent or tools with Amazon Bedrock AgentCore Runtime. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • blanket downstream permission
  • correct OAuth scopes in a deployment
  • verified user delegation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock AgentCore Runtime: Tracing boundary

Question: Does AgentCore Runtime tracing prove a complete or correct agent decision?

AWS describes tracing for agent reasoning steps, tool invocations and model interactions in AgentCore Runtime. Trace support makes these interactions inspectable when configured; it does not prove complete capture, correct reasoning or successful enforcement of a deployment’s controls.

Source: Host agent or tools with Amazon Bedrock AgentCore Runtime. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • complete trace capture
  • correct reasoning or tool output
  • tested policy enforcement

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock AgentCore: Bidirectional streaming choices

Question: What should I check before using a hosted agent for two-way audio or message streaming?

AgentCore documents WebSocket and WebRTC support for bidirectional streaming. WebSocket connections support text, structured messages and audio, with SigV4 or OAuth authentication; WebRTC targets real-time media. Select the transport and authentication contract for the actual client. Documented streaming support does not establish measured latency, uninterrupted sessions or successful integration with a particular model.

Source: AgentCore Runtime: Bidirectional streaming. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • measured end-to-end latency
  • automatic model or client compatibility
  • uninterrupted connection or delivery guarantees

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock AgentCore: Configuration and provisioning

Question: Does adding memory or credentials to an agent project mean the cloud resources are already provisioned?

AWS documents that AgentCore CLI add commands update project configuration; a subsequent deploy provisions the resources through AWS CDK. Deployment requires appropriate AWS credentials and permissions. The CLI offers a dry-run preview of changes. Check the target account, region, configuration and deployment result before claiming a capability is available; a generated project or preview is not a successful provision or working integration.

Source: AgentCore CLI: Add capabilities and deploy. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • cloud resources provisioned by configuration alone
  • working memory or credentials without deployment checks
  • permission, availability or application behaviour guaranteed by a dry run

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock AgentCore: Credentials inside the execution boundary

Question: Does an isolated agent runtime hide its execution-role credentials from code running inside it?

AWS documents that code inside an AgentCore VM can obtain execution-role credentials through its metadata service, independently of network mode. The role therefore needs permissions limited to the intended operations. Runtime isolation does not establish that code inside the VM cannot use those credentials.

Source: Understanding Credentials Management in Amazon Bedrock AgentCore. Documentation checked 2026-10-08; no deployment validation is claimed.

Claim boundaries
  • credential secrecy from code inside the VM
  • verified permissions in a buyer deployment
  • authorisation of every generated action

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock AgentCore: Memory scope

Question: Does AgentCore memory support establish correct or appropriately retained agent knowledge?

AWS distinguishes short-term memory for interactions within a session from long-term extraction of information across sessions. These are documented memory capabilities. They do not establish the accuracy of retained information or the access, retention and deletion behaviour of a particular application.

Source: Amazon Bedrock AgentCore Memory. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • correct retained knowledge
  • verified retention or deletion configuration
  • application access-control assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock AgentCore: Metadata and container hardening

Question: Does enabling MMDSv2 and running a non-root container establish that an agent runtime is secure?

AWS requires AgentCore Runtime to use MMDSv2 from 30 June 2026 and recommends non-root users for custom containers. These controls address particular runtime concerns; they do not establish correct role permissions, protected application data or approval for the agent's actions. Deployment settings still require verification.

Source: Security best practices for AgentCore Runtime. Documentation checked 2026-10-08; no deployment validation is claimed.

Claim boundaries
  • complete runtime security assurance
  • verified container user or metadata settings
  • permission to execute arbitrary actions

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock AgentCore: Workload identity scope

Question: Does an AgentCore workload identity authorise every action an agent can request?

AWS documents workload identities for agents, including automatic creation with AgentCore Runtime or Gateway deployments and explicit creation for custom deployments. An identity can participate in access policies; its existence does not establish permission for every action or the end user’s intent.

Source: Understanding agent identities in Amazon Bedrock AgentCore. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • blanket tool permission
  • verified user intent
  • automatic identity creation for every custom deployment

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon Bedrock: Invocation logging and retained content

Question: Can Bedrock invocation logging retain prompts even when I only want operational diagnostics?

AWS documents optional invocation logging that can collect supported request/response content and metadata into configured CloudWatch Logs or S3 destinations. Coverage depends on the endpoint and operation. Logging settings therefore need their own review; neither enabled logging nor absent logs establishes universal capture or zero retention.

Source: Amazon Bedrock invocation logging and endpoint coverage. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Invocation logs are only technical metadata, or cover every model endpoint.

Buyer evidence still required

  • Invocation-logging configuration and selected content categories
  • Supported endpoint/operation mapping for actual requests
  • Destination access, retention and removal evidence

Suggested review condition: Do not accept metadata-only or complete-capture claims without checking content settings and endpoint coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck endpoint changes, enabled content categories and destination lifecycle.

Optional saved evidence: Save the prompt-logging boundary behind a cloud-model data-handling decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon EC2: Retry tokens and regional or zonal scope

Question: Does reusing an EC2 client token prevent duplicate creation after an agent changes Region or Availability Zone?

EC2 client-token idempotency is scoped regionally or zonally. RunInstances uses zonal scope when an Availability Zone is specified directly or through a subnet; otherwise it uses regional scope. The same token can create instances in another applicable scope. Other changed parameters can produce IdempotentParameterMismatch.

Source: Amazon EC2: Ensuring idempotency in API requests. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does reusing an EC2 client token prevent duplicate creation after an agent changes Region or Availability Zone?

Buyer evidence still required

  • Original and retry parameters, client-token reference and account.
  • Region, Availability Zone and subnet for each attempt.
  • Returned instance identifiers and reconciled intended resource count.

Suggested review condition: Decline a duplicate-free retry claim until request scope and resulting resources are reconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Original and retry parameters, client-token reference and account. Region, Availability Zone and subnet for each attempt. Returned instance identifiers and reconciled intended resource count.

Optional saved evidence: A failover retry can provision additional resources despite reusing the original request token.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Global deduplication, verified instance count or safe cross-region failover
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon S3 Inventory: Snapshot lag and exit evidence

Question: Can an S3 Inventory report prove the current absence of an object after deletion?

S3 Inventory reports are eventually consistent snapshots and may omit recent additions or reflect objects since deleted. Reports can also be restricted by prefix and version selection. AWS recommends checking current object metadata before acting. An inventory report is useful evidence, but its absence or presence alone does not establish current deletion state.

Source: Cataloging and analyzing your data with S3 Inventory. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can an S3 Inventory report prove the current absence of an object after deletion?

Buyer evidence still required

  • Inventory generation time, manifest and configured scope
  • Required object keys and version coverage
  • Current authorized metadata checks and deletion records

Review inference: Exit reconciliation needs both inventory coverage and a current-state observation.

Suggested review condition: Refuse current-absence claims from stale or incompletely scoped inventory alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Current object state, version coverage and complete storage erasure are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid false deletion sign-off from an incomplete or lagging storage report.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Real-time inventory or proof of erasure from a missing row
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amazon S3: Multi-object deletion and per-key outcomes

Question: Does an HTTP 200 DeleteObjects response prove every requested S3 object was deleted?

S3 documents a DeleteObjects response containing both Deleted and Error entries under HTTP 200. Quiet mode suppresses successful entries, and deleting an absent key is also reported as deleted. The response must be interpreted against requested keys, version IDs and response mode.

Source: Amazon S3: DeleteObjects. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does an HTTP 200 DeleteObjects response prove every requested S3 object was deleted?

Buyer evidence still required

  • Requested bucket, keys and version IDs, with the intended deletion scope.
  • Complete DeleteResult and quiet-mode setting, including per-key errors.
  • Follow-up inventory or other outcome evidence matching the required removal claim.

Suggested review condition: Decline complete-erasure claims based only on HTTP success or Deleted labels; reconcile errors and establish the required object-version scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Requested bucket, keys and version IDs, with the intended deletion scope. Complete DeleteResult and quiet-mode setting, including per-key errors. Follow-up inventory or other outcome evidence matching the required removal claim.

Optional saved evidence: An agent cleanup or offboarding report needs a per-object reconciliation; a transport status does not establish removal of every requested item or retained version.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Erasure of all versions, replicas or retained copies, or proof a reported-deleted key existed before the request
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Amplitude MCP: User identities and analytics changes

Question: Does an Amplitude analytics connection only retrieve charts?

No. Amplitude describes querying behaviour alongside cohort, experiment and taxonomy workflows. User OAuth and service-account OAuth are separate identity choices, with existing permissions applying. Distinguish organisational MCP access from public documentation access and review the allowed read and write actions.

Source: Amplitude MCP regional endpoints, user and service identities. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted organisation analytics server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Amplitude provides the hosted MCP service.

Documented by publisher. Amplitude MCP regional endpoints, user and service identities

Purpose

Use product analytics and related operational context.

Documented by publisher. Amplitude MCP regional endpoints, user and service identities

Read capability

Reads behavioural analytics and session-replay information.

Documented by publisher. Amplitude MCP regional endpoints, user and service identities

Write capability

Supports cohort, experiment and taxonomy workflows.

Documented by publisher. Amplitude MCP regional endpoints, user and service identities

Authentication

User OAuth or service-account client credentials.

Documented by publisher. Amplitude MCP regional endpoints, user and service identities

Permission surface

Existing organisation/project permissions include separate read and write rights.

Documented by publisher. Amplitude MCP regional endpoints, user and service identities

Data leaving the environment

Requested analytics data reaches the external AI client.

Review inference. Amplitude MCP regional endpoints, user and service identities

Failure modes to consider

A chart question can be confused with authority to change an experiment.

Review inference. Amplitude MCP regional endpoints, user and service identities

Unknowns and applicability

Buyer identity grants and client data handling are unverified.

Not established

Suggested refusal or clarification condition

Clarify write authority before changing cohorts, experiments or taxonomy.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck service-account permissions, regional endpoint and tool capabilities.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the identity and operational scope behind an analytics-agent decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

An account region list is not the inference destination set

Question: Does a Bedrock source Region or manually enabled Region list constrain every cross-Region request to that location?

Bedrock uses the selected inference profile to define eligible processing destinations. Geographic profiles stay within their specified geography; global profiles can route worldwide among supported commercial Regions. Cross-Region inference can use Regions not manually enabled in the account. Source-region selection therefore does not identify the processing destination.

Source: Route model inference requests across AWS Regions with cross-Region inference - Amazon Bedrock. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Bedrock source Region or manually enabled Region list constrain every cross-Region request to that location?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require the exact profile, model, destination list and request-time evidence; do not infer a single processing region from the client endpoint or account enablement.

Suggested review condition: Require the exact profile, model, destination list and request-time evidence; do not infer a single processing region from the client endpoint or account enablement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. Choosing between Geographic and Global cross-Region inference; General considerations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the exact profile, model, destination list and request-time evidence; do not infer a single processing region from the client endpoint or account enablement.
  • A geographic profile can constrain its declared pool even though its request may leave the source Region; global routing is not mandatory for every profile.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

An enabled allowlist still needs its contents reviewed

Question: Does enabling Vercel AI Gateway Provider Allowlist immediately restrict the team to a previously reviewed provider subset?

The captured guide says initial enablement includes every currently available provider. Owners must remove unwanted providers; later new providers start disabled. A request-level only list must also satisfy the team list. Provider exclusion does not necessarily exclude a model offered by another allowed provider.

Source: AI Gateway Provider Allowlist. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does enabling Vercel AI Gateway Provider Allowlist immediately restrict the team to a previously reviewed provider subset?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Refuse to treat the enabled flag or a model name as the reviewed processor set; retain the list contents and change time.

Suggested review condition: Refuse to treat the enabled flag or a model name as the reviewed processor set; retain the list contents and change time.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ## Enabling the allowlist; ## Request-level filtering

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to treat the enabled flag or a model name as the reviewed processor set; retain the list contents and change time.
  • An owner who explicitly removes other providers can establish a declared restricted set; the initial default is not permanent.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

An initial SBOM does not settle inventory maintenance

Question: What should be agreed about continuing component information for a critical supplier product?

NIST SP 1305 recommends contractual requirements to maintain a current component inventory for critical products and disclose security features, functions and vulnerabilities through product life or the service term. Review implication: An initial SBOM does not establish a continuing inventory-maintenance or disclosure commitment. Retain dated contract, inventory and change evidence; completeness remains unverified.

Source: NIST SP 1305 C-SCRM quick-start. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: What should be agreed about continuing component information for a critical supplier product?

Buyer evidence still required

  • Criticality decision
  • Contract inventory/update requirement
  • Dated inventory and change information

Review inference: An initial SBOM does not establish a continuing inventory-maintenance or disclosure commitment. Retain dated contract, inventory and change evidence; completeness remains unverified.

Suggested review condition: No inventory completeness, present deployment match or authenticity is inferred.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Voluntary NIST CSF 2.0/SP 1305 guidance, final October 2024. No automatic UK/EU legal obligation or supplier certification.
  • No inventory completeness, present deployment match or authenticity is inferred.
  • A maintained inventory can exist and be useful; its contractual maintenance commitment does not itself establish every deployed component was captured.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

An uptime SLA is not the complete security performance agreement

Question: Does a service uptime percentage alone define acceptable supplier security performance?

NIST SP 1305 recommends security requirements in service-level agreements to monitor acceptable supplier security performance throughout the relationship. Review implication: An uptime metric alone does not specify the relevant security requirements, reporting and verification method. Review unresolved findings and owners before renewal.

Source: NIST SP 1305 C-SCRM quick-start. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a service uptime percentage alone define acceptable supplier security performance?

Buyer evidence still required

  • Applicable supplier security requirements
  • Metrics, reporting periods and verification method
  • Exceptions and unresolved performance findings
  • Scoped findings, action owners and unresolved remediation evidence where available

Review inference: An uptime metric alone does not specify the relevant security requirements, reporting and verification method. Review unresolved findings and owners before renewal.

Suggested review condition: No universal SLA threshold or actual supplier performance is established.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Voluntary NIST CSF 2.0/SP 1305 guidance, final October 2024. No automatic UK/EU legal obligation or supplier certification.
  • No universal SLA threshold or actual supplier performance is established.
  • An existing SLA may include appropriate security measures beyond uptime; its label alone does not show their content or performance.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Anthropic API: Retention scope and model-specific exceptions

Question: Does an Anthropic API retention statement apply to every feature and model?

Anthropic describes a standard API deletion period with exceptions for features such as stored files, agreements, policy enforcement and legal obligations. Designated covered models have additional retention conditions, with eligibility exceptions described separately. Confirm the exact product, model, workspace and agreement before accepting an unconditional zero-retention claim.

Source: Anthropic organizational API retention and exceptions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: One API retention promise covers every model, feature and saved conversation.

Buyer evidence still required

  • Exact product/model and feature inventory
  • Workspace retention controls and applicable agreement or eligibility notice
  • Documented exceptions, feedback handling and retained-file lifecycle

Suggested review condition: Do not generalise API or zero-retention terms across features, products or model designations.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck model designation, feature use, workspace retention and agreement changes.

Optional saved evidence: Save the dated exclusions and questions behind a model-service procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Anthropic MCP connector: Defaults determine unlisted tool access

Question: Does listing a few tool overrides restrict Anthropic MCP connector access to only those tools?

In the documented MCP toolset configuration, tool-specific configs override default_config, which overrides system defaults. The enabled default is true. Listing selected overrides alone is therefore not an allowlist for all other tools; a restrictive configuration needs the appropriate disabled default. This concerns connector selection, not the upstream credential grant.

Source: MCP connector. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does listing a few tool overrides restrict Anthropic MCP connector access to only those tools?

Buyer evidence still required

  • Connector beta version and complete toolset configuration
  • Current server tool inventory and resolved enabled flags
  • Upstream credential scope and intended tool allowance

Review inference: Permission review should resolve defaults instead of inspecting only named overrides.

Suggested review condition: Refuse a closed-allowlist finding while unlisted tools inherit an enabled default or the inventory is unknown.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Resolved deployment configuration and upstream permissions are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent accidental availability of unreviewed tools after connector configuration changes.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Upstream authorization enforcement or disabled access merely from deferred loading
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Anthropic: Workspace caps and archived-key scope

Question: Do Anthropic workspace caps or archiving stop all further usage by an agent?

Anthropic separates monthly workspace spend caps from request and token rate limits. Custom workspace limits cannot be set on the Default Workspace, and organization limits still apply. Archiving deactivates a workspace and archives its keys within seconds; multi-workspace keys can no longer act in that workspace. Historical reporting data remains and archiving cannot be undone.

Source: Workspaces - Claude Platform Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Do Anthropic workspace caps or archiving stop all further usage by an agent?

Buyer evidence still required

  • Workspace ID, key type and all workspaces accessible to the agent.
  • Workspace and organization limits, archive timestamp and request outcomes.
  • In-flight usage, cost reports and independent authority to spend.

Review inference: Disabling one workspace does not establish loss of every billing path or cancellation of in-flight charges.

Suggested review condition: Refuse organization-wide offboarding or zero-future-cost conclusions from one workspace's archived state.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer key was used; remaining access and final accrued costs are unknown.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck default Workspace exceptions, multi-workspace keys and archived-key propagation after authentication changes.

Optional saved evidence: Reconcile spending authority or transaction state before approving financial reliance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Cancellation of accrued charges, universal credential revocation or tested spending prevention
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AP2 direct and autonomous mandate verification

Question: Do AP2 direct and autonomous purchases use the same signer evidence for a closed mandate?

AP2 v0.2 verifiers receive closed Checkout and Payment Mandates in both modes. In the direct mode, the closed mandate signature is validated as coming from the user. In autonomous mode, an agent signs the closed mandate and trust in that key comes through user- or provider-signed open mandates and their constraints. The common closed form does not eliminate the different authority chain.

Source: Agent Payments Protocol - AP2 - Agent Payments Protocol Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Do AP2 direct and autonomous purchases use the same signer evidence for a closed mandate?

Buyer evidence still required

  • Direct or autonomous mode and closed mandate signer
  • User credential or trusted provider evidence
  • Open mandate chain, agent key binding and evaluated constraints

Review inference: Establish the mode and signer-to-user delegation chain rather than assuming every closed mandate records direct human approval of the exact purchase.

Suggested review condition: Do not represent agent-signed autonomous approval as direct human approval without the supporting delegation chain.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the trusted surface obtained informed consent and whether deployed verifiers performed the checks are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Accept delegated B2B purchases with the correct approval evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A closed mandate format proving direct human review of each transaction
  • Whether the trusted surface obtained informed consent and whether deployed verifiers performed the checks are unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AP2 dispute evidence and unresolved outcome rules

Question: Does AP2 define a universal dispute outcome or evidence-retention service for an agent purchase?

AP2 v0.2 describes bringing Checkout and Payment Mandates and their receipts together and verifying their signatures and cross-references as dispute evidence. It explicitly leaves specific dispute-resolution use, retention and retrieval requirements outside the specification. The protocol evidence can describe what participants saw; it does not prescribe one dispute result or provide an archive service.

Source: Agent Payments Protocol - AP2 - Agent Payments Protocol Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does AP2 define a universal dispute outcome or evidence-retention service for an agent purchase?

Buyer evidence still required

  • Mandates and receipts with verified cross-references
  • Named evidence custodians and retrieval capability
  • Applicable dispute process and retention obligations

Review inference: Agree evidence custody, retention and retrieval responsibilities separately from adopting AP2.

Suggested review condition: Do not promise a dispute result, automatic retrieval or retention guarantee from AP2 conformance alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Legal admissibility, payment-network rules, retention duties and the dispute merits are not resolved by this review.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid adopting an agent-payment flow without a practical evidence-recovery plan.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Legal advice, certification or guaranteed dispute resolution
  • Legal admissibility, payment-network rules, retention duties and the dispute merits are not resolved by this review.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AP2 latest-checkout and payee binding

Question: Can an AP2 mandate be reused after the checkout terms or payment recipient have changed?

AP2 v0.2 requires the merchant to verify that checkout_hash matches the latest checkout_jwt. The Payment Mandate links to the checkout, and constraint evaluation checks amounts and payees against authorised limits. Closed mandates also bind to their presented open mandate. A previously valid signature does not by itself establish authority for changed checkout contents or a substituted payee.

Source: Security and Privacy Considerations - AP2 - Agent Payments Protocol Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an AP2 mandate be reused after the checkout terms or payment recipient have changed?

Buyer evidence still required

  • Latest merchant-signed checkout and recomputed hash
  • Closed and applicable open mandates with their bindings
  • Final amount, currency and payee constraint evaluation

Review inference: Reconcile the latest signed checkout and payment recipient with the approved mandate chain before proceeding.

Suggested review condition: Refuse changed terms or recipient when the current mandate bindings and constraints do not validate.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual checkout revision, verifier implementation and buyer approval were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent merchant or recipient substitution after delegated purchase approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A signature authorising arbitrary later cart or recipient changes
  • The actual checkout revision, verifier implementation and buyer approval were not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AP2 payment authority and outcome receipts

Question: Does an AP2 Payment Mandate replace evidence of the actual payment outcome?

AP2 v0.2 separates the Payment Mandate authorising a particular checkout from the Payment Receipt. The receipt carries Success or Error, issuer, timestamp, a reference to the closed mandate and a payment ID; provider and network confirmation IDs are optional success fields. The authorising mandate is therefore not itself the later payment outcome record.

Source: Agent Payments Protocol - AP2 - Agent Payments Protocol Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an AP2 Payment Mandate replace evidence of the actual payment outcome?

Buyer evidence still required

  • Validated closed Payment Mandate and checkout binding
  • Signed Payment Receipt, status and mandate reference
  • Provider payment confirmation and later outcome records

Review inference: Join the validated mandate, signed receipt and available provider confirmation before asserting payment; neither mandate expiry nor signature validity establishes what previously executed.

Suggested review condition: Do not declare payment completed or irrevocably settled from a mandate alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether provider confirmation is present, funds settled or later reversed requires transaction-specific evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep spending approval distinct from money movement and licensed delivery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Mandate verification as payment-network settlement or delivery proof
  • Whether provider confirmation is present, funds settled or later reversed requires transaction-specific evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AP2 v0.2 and shopping-agent redelegation

Question: Does AP2 v0.2 fully specify passing purchase mandates between independent shopping agents?

AP2 v0.2 says shopping-agent-to-shopping-agent mandate delegation is conceptually possible but outside the current specification. It separately allows a role to delegate verification responsibilities to a technology provider, which then follows that role verification rules. Outsourcing a verifier is not the same as a specified interoperable chain of spending redelegation.

Source: Agent Payments Protocol - AP2 - Agent Payments Protocol Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does AP2 v0.2 fully specify passing purchase mandates between independent shopping agents?

Buyer evidence still required

  • Roles of each agent and delegated technology provider
  • Explicit mandate delegation scope and verification rules
  • Authority continuity and evidence-custody responsibilities

Review inference: Require a separately defined delegation and verification contract before relying on agent-to-agent purchase authority.

Suggested review condition: Do not infer unrestricted mandate forwarding or a standard redelegation flow from AP2 v0.2 alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Any custom redelegation extension and its security or interoperability remain unvalidated.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid assuming an unsupported authority chain in autonomous B2B procurement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Invented AP2 redelegation capabilities or current INDEX enforcement
  • Any custom redelegation extension and its security or interoperability remain unvalidated.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AP2: Delegation requires constraint verification

Question: Does a signed AP2 open mandate authorise any purchase the agent chooses?

AP2 requires an open mandate to be bound to a transaction and its mandate chain to be verified. The verifier must check unchanged claims and evaluate every constraint against the closed mandate; unknown constraints fail evaluation. A signature alone does not establish that a proposed purchase is within the delegated authority.

Source: AP2: Agent Authorization Framework. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Does a signed AP2 open mandate authorise any purchase the agent chooses?

Buyer evidence still required

  • The user-approved mandate, issuer trust and agent key binding.
  • The closed transaction mandate and all constraint types and values.
  • Verifier evaluation and the corresponding signed mandate receipt.

Suggested review condition: Do not treat delegation as purchase authority when the transaction binding, issuer trust or any constraint evaluation is missing or unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The user-approved mandate, issuer trust and agent key binding. The closed transaction mandate and all constraint types and values. Verifier evaluation and the corresponding signed mandate receipt.

Optional saved evidence: Procurement owners need evidence that the proposed merchant transaction fits the authority actually delegated to the shopping agent.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Apify MCP: Actor discovery, execution and stored results

Question: Can I let an agent discover Apify Actors without authorizing paid execution or storage access?

Apify separates unauthenticated discovery tools from authenticated Actor execution and access to run data. Select the tools and Actors needed for the task, then check account authority and spending limits before execution. Discovering an Actor does not establish permission to collect its target data.

Source: Apify MCP authentication, Actor execution and storage. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official hosted or local MCP with selected Actors

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Apify publishes and operates the hosted service; local deployment is also documented.

Documented by publisher. Apify MCP authentication, Actor execution and storage

Purpose

Discover and run Actors, then obtain results and storage data.

Documented by publisher. Apify MCP authentication, Actor execution and storage

Read capability

Actor metadata, documentation and authenticated run or storage results.

Documented by publisher. Apify MCP authentication, Actor execution and storage

Write capability

Actor execution starts work and can produce stored outputs.

Documented by publisher. Apify MCP authentication, Actor execution and storage

Authentication

Hosted OAuth or API token; selected discovery tools can work without authentication.

Documented by publisher. Apify MCP authentication, Actor execution and storage

Permission surface

Tool selection and Actor access distinguish discovery from execution.

Documented by publisher. Apify MCP authentication, Actor execution and storage

Data leaving the environment

Review Actor inputs, collected data and result recipients before transfer.

Review inference. Apify MCP authentication, Actor execution and storage

Failure modes to consider

Wrong Actor selection or repeated runs may collect unintended data or incur charges.

Review inference. Apify MCP authentication, Actor execution and storage

Unknowns and applicability

The selected Actor implementation, target authorization and buyer spending controls are unverified.

Not established

Suggested refusal or clarification condition

Require target, budget and data-scope approval before running an Actor.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck exposed tools, Actor permissions, account billing and storage access.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the Actor selection, allowed purpose and unresolved collection permissions with the reviewed source version.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AppDynamics MCP: Controller and Events identity are different paths

Question: Does every AppDynamics MCP HTTP call validate the supplied bearer identity with the Controller?

The documented middleware checks bearer syntax, while Controller-backed calls rely on downstream validation. Events-only calls use a separate Events credential and do not contact the Controller. The publisher therefore calls for an independently authenticated shared ingress. A syntactically valid bearer header is not proof of caller authentication for every tool.

Source: AppDynamics MCP identity and data boundaries. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: SaaS integration documentation 26.7.0

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

AppDynamics, within Splunk, publishes the documented integration.

Documented by publisher. AppDynamics MCP identity and data boundaries; AppDynamics MCP read-oriented tools

Purpose

Retrieve application and event diagnostics through supported tools.

Documented by publisher. AppDynamics MCP identity and data boundaries; AppDynamics MCP read-oriented tools

Read capability

Controller-backed data and separately authenticated Events data.

Documented by publisher. AppDynamics MCP identity and data boundaries; AppDynamics MCP read-oriented tools

Write capability

The reviewed tools are diagnostic; no general change authority is established.

Documented by publisher. AppDynamics MCP identity and data boundaries; AppDynamics MCP read-oriented tools

Authentication

HTTP bearer handling differs between Controller-backed and Events-only requests.

Documented by publisher. AppDynamics MCP identity and data boundaries; AppDynamics MCP read-oriented tools

Permission surface

A shared ingress needs its own authentication boundary; credentials follow the selected backend path.

Documented by publisher. AppDynamics MCP identity and data boundaries; AppDynamics MCP read-oriented tools

Data leaving the environment

Diagnostic data reaches the agent; returned errors and request logs can reveal context.

Review inference. AppDynamics MCP identity and data boundaries; AppDynamics MCP read-oriented tools

Failure modes to consider

Bearer syntax may be mistaken for identity validation; logs are not a complete authenticated-principal lineage.

Review inference. AppDynamics MCP identity and data boundaries; AppDynamics MCP read-oriented tools

Unknowns and applicability

Buyer ingress controls, backend scopes and actual logging configuration are unknown.

Not established

Suggested refusal or clarification condition

Do not expose a shared endpoint on the assumption that bearer syntax alone validates every caller.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Middleware validation, Events credential use and ingress guidance.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the identity-path distinction that prevents a false authenticated-endpoint claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Application tenancy does not describe the whole underlying separation boundary

Question: Can a community SaaS label alone establish the isolation controls of an MCP service built on public infrastructure?

NCSC Principle 8 distinguishes application-level separation in a layered service from underlying public-IaaS hypervisor controls. It recommends identifying which party implements each security function and understanding the underlying stack for sensitive uses. Review implication: A community SaaS label alone does not establish the complete isolation boundary or transfer assurance from an underlying provider. No tenant-isolation testing occurred.

Source: NCSC Cloud Security Principle 8. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a community SaaS label alone establish the isolation controls of an MCP service built on public infrastructure?

Buyer evidence still required

  • Service stack and tenancy model
  • Separation control and responsible party by layer
  • Scope of assurance evidence for each relevant layer

Review inference: A community SaaS label alone does not establish the complete isolation boundary or transfer assurance from an underlying provider. No tenant-isolation testing occurred.

Suggested review condition: No tenant-isolation test, data-residency conclusion or inherited certification is supplied.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • NCSC cloud/supply-chain guidance, not a standalone statutory obligation. Apply only to the relevant supplier service and responsibility boundary; cited older standards are not asserted to be current.
  • No tenant-isolation test, data-residency conclusion or inherited certification is supplied.
  • Layered services can have appropriate separation; different controls at different layers do not by themselves establish an isolation failure.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Application-supplied direct memory versus extracted conversation provenance and authority

Question: Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API provides separate conversation-ingestion and direct-memory operations, allowing an application to supply a memory rather than relying only on extracted conversation content.

Source: Cloudflare primary documentation: cloudflare memory api. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion?

Buyer evidence still required

  • operation type
  • supplied memory or conversation
  • consent/use basis
  • namespace/profile
  • resulting IDs

Review inference: Does directly remembering a Cloudflare memory require the same extraction process as conversation ingestion? Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation. Application-supplied direct memory versus extracted conversation provenance and authority. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Remember a memory

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Document which path produced the stored item and the authority to retain it; neither API choice establishes user consent or factual accuracy. Private beta access and current feature applicability require separate confirmation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

reported chain valid scoped custody detail pending

Archive custody: Integrity checks and backup completeness

Question: Does a verified ledger chain prove that a backup is complete and recoverable?

The supplied archive review reports a valid 50-entry ledger chain and consistent receipts for 162 selected objects. It does not independently rehash every local copy, inspect the detailed exclusions, verify a second copy or demonstrate a restore. Preserve the distinction between the selected set and the full intended backup. This is an attributed custody-review example, not a backup certificate or scientific promotion.

Supplied review examined 2026-10-09. The original archive and experiment were not independently rechecked during this intake.

Claim boundaries
  • complete backup coverage
  • independent rehash of every local object
  • completed exclusion review
  • verified second copy or restore
  • scientific qualification from archive transfer

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Archive extraction omissions/collisions versus complete accepted inventory

Question: Does successful MCP skill discovery prove that every archive resource was extracted?

Microsoft documents archive extension, depth, count, download and uncompressed-size controls. In its described extraction path, colliding archive members keep the first content and later collisions are skipped with a warning.

Source: Microsoft primary documentation: ms skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does successful MCP skill discovery prove that every archive resource was extracted?

Buyer evidence still required

  • archive member list
  • extraction settings
  • accepted inventory
  • warnings

Review inference: Does successful MCP skill discovery prove that every archive resource was extracted? Do not approve a complete-resource assertion without comparing the archive inventory with accepted files and extraction warnings. Archive extraction omissions/collisions versus complete accepted inventory. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not approve a complete-resource assertion without comparing the archive inventory with accepted files and extraction warnings.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. ArchiveMaxUncompressedSizeBytes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not approve a complete-resource assertion without comparing the archive inventory with accepted files and extraction warnings.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Artifact Registry cleanup: Dry run and keep rules affect deletion

Question: Does configuring an Artifact Registry cleanup policy prove matching artifacts were deleted?

The service distinguishes dry-run evaluation from deletion and applies keep policies alongside delete policies. Cleanup runs as a periodic background job rather than immediate request-time deletion. Configuration alone does not establish removal of a specific version; retain policy evaluation and subsequent artifact state.

Source: Artifact Registry cleanup and keep policies. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A saved cleanup policy proves immediate deletion of every matching version.

Buyer evidence still required

  • Repository type and dry-run or deletion mode.
  • Applicable keep/delete policies and version matching.
  • Background execution evidence and subsequent artifact state.

Suggested review condition: Require observed deletion evidence before claiming cleanup completed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Repository mode, keep/delete matches, job evidence and version state

Optional saved evidence: Save the policy and execution evidence behind an artifact-removal claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Asana V2 MCP: Workspace scope and write confirmation

Question: Can an agent assume every Asana MCP change has a confirmation step or a read-only scope?

Asana's V2 reference distinguishes direct write tools from interactive preview tools. MCP authorization covers available tools without granular permission scopes, within the user's permissions and the selected workspace. Separate workspaces require separate sessions. Confirm the client, workspace and selected tool before a change; a preview interface is not a universal property of every write path.

Source: Asana V2 MCP authorization. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official Asana V2 MCP; excludes the retired V1 endpoint and the separately documented Command server.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Asana provides the hosted V2 MCP server.

Documented by publisher. Asana V2 MCP authorization

Purpose

Read and manage tasks and projects in a selected workspace.

Documented by publisher. Asana V2 MCP tool categories

Read capability

Accessible tasks, projects and related workspace information.

Documented by publisher. Asana V2 MCP tool categories

Write capability

Direct tools create, change or delete data; interactive tools offer a separate confirmation interface.

Documented by publisher. Asana V2 MCP tool categories

Authentication

OAuth requires a pre-registered MCP app; MCP tokens do not work with the ordinary REST API.

Documented by publisher. Asana V2 MCP authorization

Permission surface

No granular MCP scopes; user permissions apply and sessions are workspace-scoped, including future available tools.

Documented by publisher. Asana V2 MCP authorization; Asana V2 MCP tool categories

Data leaving the environment

Task content is returned to the client, whose model processing and retention need separate review.

Review inference. Asana V2 MCP authorization

Failure modes to consider

Assuming a confirmation UI exists for direct writes, or confusing two workspace sessions.

Review inference. Asana V2 MCP tool categories

Unknowns and applicability

Authorized workspace, user rights, effective tool schemas and client confirmation behavior.

Not established

Suggested refusal or clarification condition

Before changing work, establish workspace, object and authorized action; do not equate tool availability with approval.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck new tools, selected workspace and whether the client uses direct or interactive write tools.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain workspace, tool-selection and confirmation assumptions behind a task-management approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Atlas restore: Point-in-time selection is not a harmless read

Question: Can an agent restore an Atlas cluster to a timestamp without affecting its current data?

The Continuous Cloud Backup guide distinguishes restore scopes and warns that a cluster-level restore deletes existing target data and makes the target unavailable during restoration. Search index definitions can be restored while their data requires initial sync. Timestamp selection is not proof of a non-disruptive or immediately ready result.

Source: MongoDB Atlas point-in-time recovery. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A point-in-time restore is non-destructive and instantly ready.

Buyer evidence still required

  • Source backup point and exact target cluster identity.
  • Restore scope, required permissions and authorised replacement plan.
  • Completion evidence including index readiness and application checks.

Suggested review condition: Do not start a cluster-level restore without authority to replace the target state.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Source point, target identity, restore scope and index readiness

Optional saved evidence: Retain the target, scope and readiness questions needed for an authorised recovery decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Atlassian app rules: Covered and exempt data

Question: Does an Atlassian app access rule block every API data category?

Atlassian distinguishes covered data from exempt data in its API references. Rules can block covered data, while exempt categories are not blocked by those rules. Map the actual API operations and data categories before accepting a complete app-isolation claim.

Source: Atlassian app access rule coverage and exempt data. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An app access rule blocks every kind of data the app can retrieve.

Buyer evidence still required

  • Active rule and protected content scope
  • Coverage or exemption status for the relevant API operations
  • Other access paths and app permissions in the buyer deployment

Suggested review condition: Require operation-level coverage evidence before claiming complete isolation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck API coverage references and app capability changes.

Optional saved evidence: Preserve the covered-versus-exempt distinction for an app procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Atlassian residency evidence: App scope and excluded data

Question: Does pinning an Atlassian app to a region keep every account, integration and AI data flow there?

Atlassian Cloud residency applies to defined in-scope app data. The documentation lists exclusions and treats Marketplace app data separately. A pinned product location therefore does not establish that every account record, log, integration or AI-related flow stays in that region. Identify the app and data category before relying on the claim.

Source: Atlassian Cloud residency inclusions and exclusions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: All data associated with our Atlassian organization stays in its selected region.

Buyer evidence still required

  • The current app-level residency status
  • A mapping from the buyer data categories to published inclusions and exclusions
  • Separate evidence for each Marketplace app or external recipient

Suggested review condition: Require additional evidence for excluded categories and integrations; do not turn a residency setting into a compliance conclusion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck app type, data-category tables, region setting and integration inventory.

Optional saved evidence: Preserve the category-by-category scope behind a regional-hosting claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Atlassian Rovo MCP: Workspace search and change controls

Question: How should an agent check whether an Atlassian connector can search documents without changing them?

Atlassian documents organization controls for reading, writing and searching, alongside tool-specific scopes for Jira and Confluence. Its supported-tools page includes mutations, so a search use case does not make the entire connector read-only. Check the relevant app permissions and whether future permissions inherit an allow decision. This record does not inspect your organization's settings.

Source: Atlassian MCP permission controls. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Atlassian's remote MCP documentation, including the supported-tools page now published under Atlassian AI Gateway; selected apps and organization settings must be identified.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Atlassian publishes the remote connector and its administration guidance.

Documented by publisher. Atlassian MCP permission controls; Atlassian MCP supported tools

Purpose

Search and work with Jira and Confluence information.

Documented by publisher. Atlassian MCP permission controls; Atlassian MCP supported tools

Read capability

Jira work items and Confluence content; search scope depends on enabled app toolsets.

Documented by publisher. Atlassian MCP permission controls; Atlassian MCP supported tools

Write capability

Documented tool groups create or edit Jira and Confluence content; additional high-impact groups require separate review.

Documented by publisher. Atlassian MCP permission controls; Atlassian MCP supported tools

Authentication

The reviewed Jira and Confluence tools document OAuth 2.1 and API token authentication with named scopes.

Documented by publisher. Atlassian MCP permission controls; Atlassian MCP supported tools

Permission surface

Organization Read, Write and Search controls include app-specific choices and optional automatic allowance of future additions.

Documented by publisher. Atlassian MCP permission controls; Atlassian MCP supported tools

Data leaving the environment

Retrieved work content is delivered to the connected AI client. That client's recipients and retention are a separate review question.

Review inference. Atlassian MCP permission controls; Atlassian MCP supported tools

Failure modes to consider

Search-only intent with write access still enabled; future permission inheritance; confusing a permission error with absent content.

Review inference. Atlassian MCP permission controls; Atlassian MCP supported tools

Unknowns and applicability

Effective app settings, inherited additions, exact user permissions and downstream client data handling.

Not established

Suggested refusal or clarification condition

For a search-only task, withhold mutations; review inherited permissions before allowing newly added tool groups.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the organization-control and scope questions considered before enabling a workplace connector.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Attio MCP: CRM changes under a user's authority

Question: Can an Attio research assistant also change CRM records?

Attio documents OAuth access as the connecting user, including record and note changes, task deletion and list updates. Existing workspace permissions apply. Connecting for research does not establish approval for these actions or the external assistant's handling of CRM content.

Source: Attio MCP. Documentation checked 2026-10-17; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer installation and runtime untested

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Attio publishes the hosted MCP service.

Documented by publisher. Attio MCP; Attio MCP overview

Purpose

Read and manage CRM information through an assistant.

Documented by publisher. Attio MCP; Attio MCP overview

Read capability

Permitted records, notes, emails and meetings.

Documented by publisher. Attio MCP; Attio MCP overview

Write capability

Create or update records, notes and lists; delete tasks.

Documented by publisher. Attio MCP; Attio MCP overview

Authentication

OAuth with an Attio user account.

Documented by publisher. Attio MCP; Attio MCP overview

Permission surface

Access follows the connecting user's workspace permissions.

Documented by publisher. Attio MCP; Attio MCP overview

Data leaving the environment

Retrieved CRM information enters the external assistant's workflow.

Review inference. Attio MCP; Attio MCP overview

Failure modes to consider

Broad user access can exceed a narrowly requested research task.

Review inference. Attio MCP; Attio MCP overview

Unknowns and applicability

Client retention and actual grants have not been checked.

Not established

Suggested refusal or clarification condition

Require an authorised change scope before permitting mutations.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Workspace, connecting user, selected operations and external assistant data handling.

Record history: 2026-10-17 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the dated CRM access and change-authority basis used for admission.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Attribution V2: Claim truth boundary

Question: Does an Attribution V2 check prove the truth of all linked claims?

The public Attribution V2 source supports evidence-binding posture. It explicitly excludes the truth of all claims and does not confer authority by itself.

Derived from BDAS Fused Attribution V2 — Attribution Check Pass. No new experiment or validation is claimed.

Claim boundaries
  • truth of all claims
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Attribution V2: Private source disclosure boundary

Question: Does Attribution V2 permit public exposure of private sources?

The Attribution V2 source supports binding posture while explicitly excluding public exposure of private sources. Attribution is not disclosure permission.

Derived from BDAS Fused Attribution V2 — Attribution Check Pass. No new experiment or validation is claimed.

Claim boundaries
  • public exposure of private sources
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

experiment complete no promotion

AURIC archived study: Attention without promotion

Question: Can an experimental anomaly signal approve a vulnerability finding?

The supplied AURIC study completed an archived-anchor experiment without promotion. Its attention candidates do not certify advisory truth, discover new vulnerabilities or authorise corpus admission. The accompanying scope report does not establish calibrated cross-series probabilities. This historical result does not establish current-engine performance or security of a buyer deployment.

Supplied evidence reviewed 2026-10-08. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • new vulnerability discovery
  • calibrated risk probabilities
  • corpus admission authority
  • current-engine or production performance
  • independent replication

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Auth0 logs: Plan retention and delayed visibility

Question: Does an empty Auth0 tenant-log search establish that no authentication event occurred?

Auth0 documents plan-dependent retention and possible indexing delay. A query result needs a time-range, plan and collection check before it supports an absence claim. Longer history requires evidence of an external logging arrangement; the feature description does not establish that one was operating.

Source: Auth0 plan-based log retention and ingestion delay. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An empty tenant-log query proves no relevant authentication activity.

Buyer evidence still required

  • Tenant plan and applicable retention window
  • Dated query with filters and requested interval
  • External export continuity and storage evidence where needed

Suggested review condition: Qualify absence claims when retention or ingestion coverage is not demonstrated.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck subscription, retention, ingestion delay and external logging continuity.

Optional saved evidence: Retain the coverage limit behind an authentication-history review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Auth0 MCP: Tenant changes and local credential files

Question: Can an Auth0 onboarding assistant change the tenant and write local credentials?

Yes. The README describes onboarding that creates an application and saves its credentials to a project environment file. It also documents read-only and tool-selection controls. Assess both tenant authority and local file output; merely describing the task as setup does not narrow either.

Source: Auth0 MCP management access. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official local Auth0 management MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Auth0 publishes the management MCP server.

Documented by publisher. Auth0 MCP management access

Purpose

Inspect and configure Auth0 integrations.

Documented by publisher. Auth0 MCP management access

Read capability

Application, API, connection and log information.

Documented by publisher. Auth0 MCP management access

Write capability

Management changes and onboarding credential-file output.

Documented by publisher. Auth0 MCP management access

Authentication

OAuth device authorisation with locally stored credentials.

Documented by publisher. Auth0 MCP management access

Permission surface

Read-only mode takes priority over a broader tool pattern.

Documented by publisher. Auth0 MCP management access

Data leaving the environment

Tenant data and credential-related outputs may cross the client boundary.

Review inference. Auth0 MCP management access

Failure modes to consider

A setup request may create resources and local files.

Review inference. Auth0 MCP management access

Unknowns and applicability

Actual consent, file permissions and effective tenant access are unknown.

Not established

Suggested refusal or clarification condition

Clarify tenant changes and credential-file handling before onboarding.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Onboarding composition, tool filters and credential-storage behaviour.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep a review of tenant authority separate from permission to create local credential files.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Auth0 rotation overlap and concurrent retries

Question: Does an Auth0 rotation overlap window permit replay of any earlier refresh token?

Auth0 describes an optional rotation overlap period to tolerate concurrent exchanges. During that leeway, reuse detection does not apply to the immediately previous token; exchanging the second-to-last token triggers detection. The configured window and exact token generation matter when deciding whether a retry is tolerated.

Source: Auth0: Configure Refresh Token Rotation. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an Auth0 rotation overlap window permit replay of any earlier refresh token?

Buyer evidence still required

  • Application rotation and leeway configuration
  • Token-generation order without token secrets
  • Concurrent exchange and recovery timestamps

Review inference: Review auth0 rotation overlap and concurrent retries before accepting the buyer claim. The existing family-invalidation record does not specify the configurable previous-token concurrency exception. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: No safe-replay claim for arbitrary old tokens or assurance that the buyer configured the documented overlap.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Configure in the Dashboard; Configure with the Auth0 SPA SDK

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No safe-replay claim for arbitrary old tokens or assurance that the buyer configured the documented overlap.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Auth0 rotation: Reuse detection can invalidate the whole refresh family

Question: Does refresh-token rotation let an agent safely retry any old refresh token?

The rotation documentation describes invalidation of a refresh-token family when reuse of an invalidated token is detected. The service cannot identify the legitimate actor from that replay alone. Both recovery and access-token lifetime need consideration; rotation is not permission to retry stale credentials indefinitely.

Source: Auth0 refresh-token rotation and reuse detection. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Automatic rotation makes stale-token retries harmless and preserves uninterrupted access.

Buyer evidence still required

  • Client rotation and retry configuration.
  • Documented handling of reuse events and token-family invalidation.
  • Reauthentication flow and separate access-token lifecycle evidence.

Suggested review condition: Require recovery evidence before accepting uninterrupted-session claims.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Rotation policy, client concurrency/retry behaviour and recovery flow.

Optional saved evidence: Preserve the distinction between reuse protection and successful session recovery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Auth0 token revocation and grant scope

Question: Does unlinking one Auth0 device revoke every refresh token for the user and application?

Auth0 distinguishes refresh-token revocation from deleting its authorization grant. The tenant revocation setting controls whether related tokens are invalidated with the grant; with the setting disabled, unlinking a device revokes its associated refresh token while leaving the grant intact. Verify the endpoint, setting and grant identity before claiming broader offboarding.

Source: Auth0: Revoke Refresh Tokens. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does unlinking one Auth0 device revoke every refresh token for the user and application?

Buyer evidence still required

  • Tenant revocation setting
  • Revocation endpoint and result
  • User, application, audience and grant identifiers
  • Remaining token and access-token lifecycle evidence

Review inference: Review auth0 token revocation and grant scope before accepting the buyer claim. Administrative revocation scope depends on grant deletion settings, unlike automatic stale-token reuse detection. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not infer all-device revocation or immediate expiry of existing access tokens from one device unlink.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Choose whether token revocation deletes grants; Considerations and limitations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer all-device revocation or immediate expiry of existing access tokens from one device unlink.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS Access Analyzer: No external finding is not no access

Question: Does an empty external Access Analyzer report prove nobody else can access a resource?

External findings are defined relative to the selected account or organization as a zone of trust. Sharing within that zone does not produce an external finding. Internal and unused access are separate analyses; the absence of an external finding does not establish absence of internal access or buyer suitability.

Source: AWS IAM Access Analyzer findings. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does an empty external Access Analyzer report prove nobody else can access a resource?

Buyer evidence still required

  • Analyzer type and selected zone of trust.
  • Resources and principals relevant to the buyer's question.
  • Separate evidence for internal or unused access claims.

Suggested review condition: Do not use an external-only result as evidence of universal least privilege.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Analyzer type, trust zone, relevant resources and intended access claim.

Optional saved evidence: Save the scope interpretation behind a supplier's no-external-access claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS backup destructive restore exceptions

Question: Does AWS Backup always restore into a new resource without overwriting existing data?

The reviewed AWS Backup restore guide generally describes new-resource restoration but explicitly identifies destructive exceptions: Redshift Serverless namespace restores overwrite target-namespace data, and SAP HANA on EC2 restores overwrite the specified target database. Target type and location must be resolved before treating a restore as non-destructive.

Source: Amazon Web Services: Restore a backup. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does AWS Backup always restore into a new resource without overwriting existing data?

Buyer evidence still required

  • resource type
  • target namespace or database
  • restore metadata
  • approval scope and destination inventory

Review inference: An operator runs a recovery exercise against an existing namespace. A test can overwrite the live target rather than create a separate copy. Adds the destructive target boundary, not completion or workload validation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not apply the general new-resource assumption to the documented overwrite exceptions or authorise a destructive restore from this review.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. destructive restores

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not apply the general new-resource assumption to the documented overwrite exceptions or authorise a destructive restore from this review.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup hold record retention

Question: Does CancelLegalHold DeleteAfterDays control how long the backups remain locked?

AWS documents DeleteAfterDays on CancelLegalHold as retention for the legal-hold record itself, defaulting to 180 days. Recovery points unlock as cancellation processes and are not governed by that metadata-retention parameter. Other holds and recovery-point lifecycles still need separate review.

Source: Amazon Web Services: Backup legal holds. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does CancelLegalHold DeleteAfterDays control how long the backups remain locked?

Buyer evidence still required

  • CancelLegalHold request and outcome
  • hold record
  • recovery-point hold set and lifecycle

Review inference: A records manager uses the cancellation parameter as a data-retention deadline. An administrative-record lifetime can be mistaken for data protection or erasure. Distinguishes the administrative hold record's retention from the underlying backup data. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not use DeleteAfterDays as a backup-deletion date or continued-lock guarantee.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. DeleteAfterDays: optional

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not use DeleteAfterDays as a backup-deletion date or continued-lock guarantee.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup lock retention independent

Question: Does a new Vault Lock minimum replace the lifecycle already assigned to each backup?

AWS describes backup retention periods as defined when each backup is created and independent of the vault lock's minimum and maximum settings. A lock configuration is therefore not evidence that every retained recovery point has the newly selected retention duration.

Source: Amazon Web Services: Backup Vault Lock. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a new Vault Lock minimum replace the lifecycle already assigned to each backup?

Buyer evidence still required

  • recovery-point creation times and lifecycles
  • vault lock mode and dates
  • min/max configuration

Review inference: A retention owner increases a vault minimum and reports older backups as extended. Earlier backups may have different documented expiry obligations. Adds the separation between per-backup retention and vault-level limits, beyond lock mode and mutability. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse a uniform-retention claim based only on the current vault lock; inspect recovery-point lifecycles.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. These retention periods are defined

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a uniform-retention claim based only on the current vault lock; inspect recovery-point lifecycles.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup multiple hold release

Question: Does releasing one AWS Backup legal hold make a recovery point deletable?

A recovery point can have multiple legal holds. AWS states it cannot be deleted while any hold remains; after all holds are removed its own retention lifecycle applies. Releasing one named hold neither clears other holds nor establishes immediate deletion.

Source: Amazon Web Services: Backup legal holds. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does releasing one AWS Backup legal hold make a recovery point deletable?

Buyer evidence still required

  • all holds bound to the recovery point
  • release outcomes
  • recovery-point retention lifecycle

Review inference: An exit operator releases the litigation hold they know about. A remaining hold or retention period can keep the data recoverable. The existing review addresses which copies a hold covers; this decision addresses multiple holds on the same point and release reconciliation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not report deletion eligibility or completion from a single hold release without the complete hold set and lifecycle.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Multiple legal holds

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not report deletion eligibility or completion from a single hold release without the complete hold set and lifecycle.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup primary airgap fallback

Question: Does a completed primary-backup job prove the recovery point reached its logically air-gapped target?

For documented unsupported resources or encryption-key cases, AWS Backup can complete to the standard vault with issues while the air-gapped copy is unavailable. For copied resource types, the destination copy job must be reconciled separately with the source recovery point and target vault. Backup completion alone does not establish that protection location.

Source: Amazon Web Services: Logically air-gapped vaults as primary backup targets. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a completed primary-backup job prove the recovery point reached its logically air-gapped target?

Buyer evidence still required

  • resource type and encryption key type
  • backup job message
  • source recovery-point ARN
  • destination copy-job outcome and vault ARN

Review inference: A recovery owner sees a successful backup while migrating to an air-gapped target. The expected isolated recovery copy may never have been created. Adds actual target placement and fallback, rather than retention protection in a known vault. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse air-gapped-copy coverage based only on backup completion; verify the supported path and completed destination copy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Backup job completes with

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse air-gapped-copy coverage based only on backup completion; verify the supported path and completed destination copy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup restore access view deletion

Question: Does deleting a failed restore-access vault remove its underlying protected backups?

AWS describes a restore-access backup vault as a view of the underlying logically air-gapped vault, containing no recovery points of its own. Its documented FAILED-state recovery procedure allows deleting the view; Vault Lock does not prevent that deletion. Removing the view is not evidence of erasing the underlying recovery points.

Source: Amazon Web Services: Logically air-gapped vaults. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a failed restore-access vault remove its underlying protected backups?

Buyer evidence still required

  • restore-access vault identity and state
  • underlying vault and recovery-point inventory
  • deletion outcome

Review inference: An operator removes a failed recovery-access configuration during offboarding. The underlying retained data can disappear from the access inventory without being erased. Distinguishes access-view deletion from deleting a storage vault or its recovery points. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Limit this procedure to the documented failed restore-access view; do not infer protected-backup deletion or bypass of the source vault's retention.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Restore access backup vault in

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Limit this procedure to the documented failed restore-access view; do not infer protected-backup deletion or bypass of the source vault's retention.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup restore selection tag boundary

Question: Do restore-testing tag conditions ensure the restored recovery point carries those tags?

AWS Backup evaluates resource-selection tags using the protected resource's latest recovery point. It then selects at most one eligible recovery point using the plan's time window and latest-or-random rule; the tag conditions do not filter that recovery-point choice. A selected resource can therefore be restored from a point with different tags.

Source: Amazon Web Services: Restore testing. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Do restore-testing tag conditions ensure the restored recovery point carries those tags?

Buyer evidence still required

  • selection tag predicates
  • latest recovery-point tags
  • selection window and algorithm
  • actual restored recovery-point ARN

Review inference: An auditor relies on tag-filtered testing as proof a specific classified backup was exercised. Coverage can be assigned to the wrong backup version or classification. Adds test-sample selection identity, distinct from whether validation ran after restoration. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not claim a tagged recovery version was tested without identifying the actual selected point and its attributes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Tag conditions don't apply to recovery point selection

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim a tagged recovery version was tested without identifying the actual selected point and its attributes.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup restore tag api default

Question: Does an API-driven AWS Backup restore preserve the same tags as the console default?

StartRestoreJob defaults CopySourceTagsToRestoredResource to false, while the documented console default includes tags. Resource-specific exceptions apply: some resources do not support the option, and documented snapshot behaviours can copy tags independently of it. Tag-derived governance cannot be assumed from an otherwise successful restore.

Source: Amazon Web Services: Restore a backup. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an API-driven AWS Backup restore preserve the same tags as the console default?

Buyer evidence still required

  • restore interface and parameter
  • resource type
  • backup snapshot tags
  • restored resource tags
  • tagging permissions

Review inference: Automation replaces a manually tested console restore. Classification or access policies dependent on tags may change unnoticed. Adds AWS restoration metadata defaults and exceptions; the existing Weaviate record concerns separate RBAC objects. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Verify the actual restored tag set and resource-specific rules; do not infer policy restoration from the console default or this Boolean alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. CopySourceTagsToRestoredResource

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Verify the actual restored tag set and resource-specific rules; do not infer policy restoration from the console default or this Boolean alone.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup restore test cleanup status

Question: Does a completed AWS Backup restore test establish that its temporary resource was deleted?

Restore-test deletion has a separate Successful, Deleting or Failed status. AWS documents that failed cleanup needs manual removal and that removing the awsbackup-restore-test tag often causes this failure. Test execution or validation completion alone does not close the retained-resource inventory.

Source: Amazon Web Services: Restore testing. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a completed AWS Backup restore test establish that its temporary resource was deleted?

Buyer evidence still required

  • restore job ID
  • restored resource IDs
  • deletion status
  • restore-test tag
  • any manual removal evidence

Review inference: A recovery test is declared complete and its temporary data is omitted from exit review. Test copies can remain accessible and billable after the test. The existing record separates restore from validation; this adds the independently failing cleanup stage. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse cleanup completion while deletion is pending or failed; a successful restore is not a deletion receipt.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Deletion status notes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse cleanup completion while deletion is pending or failed; a successful restore is not a deletion receipt.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS backup temporary copy cleanup

Question: Does DELETE_AFTER_COPY mean a temporary recovery point disappears after the first copy finishes?

For the documented temporary snapshot flow, DELETE_AFTER_COPY schedules removal after all copy jobs complete or the specified retention period, whichever comes first. Copy-triggered cleanup requires all automatic and scheduled jobs to finish and a completed air-gapped copy retained at least as long as the source. Failed copying retains the source according to its lifecycle. Continuous-backup temporary snapshots have a separate cleanup rule because the continuous source remains. Identify the backup mode and retention path before inferring removal.

Source: Amazon Web Services: Logically air-gapped vaults as primary backup targets. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does DELETE_AFTER_COPY mean a temporary recovery point disappears after the first copy finishes?

Buyer evidence still required

  • resource and backup mode
  • source lifecycle
  • every scheduled and automatic copy
  • destination retention
  • observed source state

Review inference: An exit operator deletes the source inventory entry as soon as one copy succeeds. Residual recovery points or incomplete target protection can be missed. Adds temporary source-copy cleanup conditions and backup-mode exceptions, not propagation of a legal hold to destination copies. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer source removal from one successful copy, assume retention expiry waits for successful protection, or apply snapshot rules to continuous-backup flows. Observed deletion remains separate from a lifecycle policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. All automatic and scheduled copy jobs

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer source removal from one successful copy, assume retention expiry waits for successful protection, or apply snapshot rules to continuous-backup flows. Observed deletion remains separate from a lifecycle policy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS Backup: Lock mode affects later deletion authority

Question: Does an AWS Backup Vault Lock configuration prove its protection can no longer be removed?

AWS distinguishes governance locks, removable with sufficient permission, from compliance locks with a changeable grace period. After that period, a compliance lock cannot be altered while recovery points remain. Mode, LockDate and backup lifecycles matter when assessing both preservation and later exit feasibility.

Source: AWS Backup Vault Lock. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an AWS Backup Vault Lock configuration prove its protection can no longer be removed?

Buyer evidence still required

  • The lock mode and LockDate.
  • Recovery-point lifecycle and retention settings.
  • The relevant administration authority and actual vault state.

Suggested review condition: Do not call a lock immutable from configuration alone or promise early erasure of still-retained recovery points.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The lock mode and LockDate. Recovery-point lifecycle and retention settings. The relevant administration authority and actual vault state.

Optional saved evidence: An AI backup owner must establish who can remove protection and whether retained recovery points can be deleted during offboarding.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Regulatory compliance, actual backup recoverability or permission to change a lock
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS Budgets: Notifications are delayed cost signals

Question: Does an AWS budget notification threshold impose an immediate per-call spending cap?

AWS Budgets uses periodically updated billing information and documents delay between usage and notification. Additional costs can accrue beyond the threshold before notice arrives. A notification setting alone is therefore not an immediate limit on an agent call; separately configured actions and execution controls need their own review.

Source: AWS Budgets measurement and delays. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A budget alert guarantees no spend beyond the threshold.

Buyer evidence still required

  • Budget scope, cost basis and notification configuration.
  • Any separately authorised action or workload spending control.
  • Usage-to-billing delay and observed alert timing.

Suggested review condition: Do not authorise uncapped calls solely because a billing alert exists.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Budget scope, billing delay, actions and workload spending controls

Optional saved evidence: Preserve the difference between delayed cost awareness and authorised execution limits.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS CloudTrail: Management history is not every data access

Question: Does an empty CloudTrail event history prove no application data was accessed?

AWS distinguishes management events from data events. Default trail and event-store coverage does not include data events, and Event history is not a data-event search. A conclusion about application data access needs evidence of the relevant event category, resource selectors, period and destination.

Source: AWS CloudTrail management and data event coverage. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: CloudTrail is enabled, so every access to application data is searchable.

Buyer evidence still required

  • Dated trail or event-store configuration and resource/event selectors
  • Coverage of the exact API operation and Region during the period
  • Destination, retention and query evidence, including filters

Suggested review condition: Do not infer no data access from management-only history or an unverified capture period.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck event selectors, resource coverage, trail status and retention.

Optional saved evidence: Preserve the coverage questions behind an access-history review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS Config: Daily state and missing transitions

Question: Does AWS Config daily recording preserve every resource configuration change?

Daily recording captures the most recent state over the preceding day when it differs from the previous recorded configuration. Continuous recording and resource-type selection are separate settings. A daily record is not a complete transition history, and unsupported or unselected types remain outside the asserted coverage.

Source: AWS Config resource recording selection. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A daily Config record proves every intermediate configuration state was captured.

Buyer evidence still required

  • Recorder resource-type selection and frequency.
  • Region and global-resource coverage.
  • Configuration items and independent event evidence.

Suggested review condition: Do not infer a complete change history from daily state snapshots.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Resource type, region, selection, recorder health and recording frequency.

Optional saved evidence: Preserve the difference between periodic inventory and a complete change trail.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS cost-tag backfill limits

Question: Can activating an AWS cost-allocation tag today reconstruct attribution for resources that were never tagged?

AWS permits management accounts to request cost-allocation tag backfill for up to twelve months. Backfill uses tags historically assigned to resources and applies the current activation state. It does not invent past resource tags; activation and historical assignment are different conditions.

Source: Backfill cost allocation tags - AWS Billing. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can activating an AWS cost-allocation tag today reconstruct attribution for resources that were never tagged?

Buyer evidence still required

  • Historical resource-tag evidence
  • Current cost-allocation tag activation
  • Requested backfill period and completed report output

Review inference: Check historical tag presence and the selected backfill window before claiming retrospective attribution.

Suggested review condition: Refuse complete historical attribution where required tags were absent.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Untagged historical usage and business ownership cannot be reconstructed from activation alone.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Set realistic limits on retrospective agent-cost allocation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic recovery of every workflow’s past costs
  • Untaged historical usage and business ownership cannot be reconstructed from activation alone.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS CUR resource id absence

Question: Does a blank AWS CUR ResourceId mean the cost row is invalid?

Resource IDs are optional in Cost and Usage Reports. Even when enabled, data-transfer and API-request usage and items such as discounts, credits and taxes can have a blank ResourceId. A resource-only filter can therefore exclude legitimate charges or adjustments; assess the line type and reporting configuration before rejecting the row.

Source: Amazon Web Services: Cost and Usage Report line-item columns. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Does a blank AWS CUR ResourceId mean the cost row is invalid?

Buyer evidence still required

  • report resource-ID setting
  • line item type
  • usage type
  • reconciliation scope

Review inference: An automated cost audit discards every row without a resource. Valid invoice components are omitted. Adds AWS native CUR applicability and optional configuration rather than Google Cloud repeated credits. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A populated resource ID does not authenticate ownership, and a blank ID is not proof of zero cost.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. lineItem/ResourceId

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A populated resource ID does not authenticate ownership, and a blank ID is not proof of zero cost.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS CUR seller invoicing entity

Question: Does AWS CUR LegalEntity always identify the party issuing the invoice?

LegalEntity identifies the seller of record for the product or service. The seller and invoicing entity are usually the same but can differ for third-party AWS Marketplace transactions. Bind the invoice issuer, seller and relevant purchase separately; the exported seller label does not authorize a changed payee or bank account.

Source: Amazon Web Services: Cost and Usage Report line-item columns. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Does AWS CUR LegalEntity always identify the party issuing the invoice?

Buyer evidence still required

  • seller field
  • invoice issuer
  • Marketplace order
  • approved supplier identity
  • payment instruction evidence

Review inference: A buyer maps the marketplace seller directly to the invoice payee. The wrong legal entity can be selected during reconciliation. Adds the AWS native field interpretation and Marketplace exception rather than only the FOCUS standard roles. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A billing label is not merchant authentication or authority to change payment details.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. lineItem/LegalEntity

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A billing label is not merchant authentication or authority to change payment details.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS IAM: Default policy versions and authority drift

Question: Does denying CreatePolicyVersion alone prevent an agent from changing the operative IAM policy?

For customer managed policies, CreatePolicyVersion can create and select a new default, while SetDefaultPolicyVersion can select an existing version. The selected default supplies the policy in effect for attached identities. AWS says both actions must be denied to prevent changes to that default.

Source: AWS IAM: Versioning IAM policies. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does denying CreatePolicyVersion alone prevent an agent from changing the operative IAM policy?

Buyer evidence still required

  • Policy ARN, attached identities and the selected default version.
  • Retained version documents and permissions for both version-changing actions.
  • Change approval, before/after version identifiers and applicable policy context.

Suggested review condition: Decline a frozen-policy or no-escalation claim that checks only creation rights; inspect default-version selection and retained versions as well.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Policy ARN, attached identities and the selected default version. Retained version documents and permissions for both version-changing actions. Change approval, before/after version identifiers and applicable policy context.

Optional saved evidence: Authority review must cover rollback to retained policy versions as well as creation of new policy text; an unchanged policy ARN does not identify the operative document.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A complete escalation-path analysis or proof that an identity cannot gain authority through other policies
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS IAM: Missing context can still match a deny

Question: Does IfExists make an IAM deny harmless when the condition key is absent?

AWS documents that a negated condition such as StringNotEqualsIfExists in a Deny statement can still deny a request when the key is absent. The operator, statement effect and available resource context must be read together.

Source: AWS IAM: JSON policy elements, condition operators. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does IfExists make an IAM deny harmless when the condition key is absent?

Buyer evidence still required

  • Complete policy statement including Effect.
  • Action-specific request context keys.
  • Reviewed missing-key and present-key cases.

Suggested review condition: Do not infer an exemption from the IfExists suffix; preserve the full condition semantics.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Exact condition operator, statement effect and keys present for the action and resource.

Optional saved evidence: Does IfExists make an IAM deny harmless when the condition key is absent?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS IAM: Passing a role delegates service authority

Question: What evidence explains the authority an agent delegates when it passes an IAM role to a service?

PassRole permits assigning a role that a service can later assume. AWS distinguishes the role permissions, service trust and caller permission to pass it. PassRole is not a separate API event; the resource creation or modification event records the assignment.

Source: AWS IAM: Grant a user permissions to pass a role to an AWS service. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: What evidence explains the authority an agent delegates when it passes an IAM role to a service?

Buyer evidence still required

  • Role permissions and service trust policy.
  • Caller PassRole resource and service restrictions.
  • Resource creation or modification event containing the role.

Suggested review condition: Review delegated service authority as well as the caller action; do not require a nonexistent standalone PassRole event.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Passed role, receiving service, caller and resource creation or update.

Optional saved evidence: What evidence explains the authority an agent delegates when it passes an IAM role to a service?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS IAM: Permission boundaries and direct resource grants

Question: Does an IAM permissions boundary alone prove every access path is restricted?

A boundary limits identity-policy permissions and grants nothing by itself. The documentation also distinguishes direct resource grants to users, roles and sessions, including cases not limited by an implicit boundary denial. Review principal type and resource policies alongside the boundary; explicit denials are a different case.

Source: IAM boundaries and resource-policy exceptions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The attached boundary establishes the complete effective permission limit.

Buyer evidence still required

  • Exact principal and session type used by the agent.
  • Relevant identity, resource and boundary policies.
  • Evidence of explicit denials and evaluated access for the intended action.

Suggested review condition: Do not infer effective access from a boundary attachment alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Resource grants, session identities and boundary changes.

Optional saved evidence: Preserve which policy combinations still need review before accepting an access-limit claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS IAM: Simulation is not a live request

Question: Does an allowed IAM simulation prove an agent can execute the production action?

The IAM simulator evaluates supplied policy and context without making the service request or returning its response. AWS documents differences from live behaviour. Editing a simulated policy also leaves the account policy unchanged.

Source: AWS IAM: Testing policies with the policy simulator. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does an allowed IAM simulation prove an agent can execute the production action?

Buyer evidence still required

  • Simulation inputs and policy versions.
  • Effective production identity and resource context.
  • Separately authorised live outcome evidence.

Suggested review condition: Treat simulation as a policy-model result; require separate operational evidence for an execution claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Action, resource, simulated context, policy versions and the corresponding production request.

Optional saved evidence: Does an allowed IAM simulation prove an agent can execute the production action?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS KMS: Scheduled key deletion remains pending

Question: Does scheduling an AWS KMS key for deletion prove protected AI data has already been erased?

AWS KMS uses a mandatory waiting period during which deletion can be cancelled. A multi-Region primary key waits for replica deletion before its own period starts. A scheduled deletion is therefore not completed key destruction, and key state alone does not establish removal of plaintext or separately protected copies.

Source: AWS KMS key deletion. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does scheduling an AWS KMS key for deletion prove protected AI data has already been erased?

Buyer evidence still required

  • The key type, state and deletion time.
  • Replica keys and any external or custom key stores.
  • The data-copy inventory and independent completion evidence.

Suggested review condition: Do not mark data erased from a pending key deletion or without accounting for other copies and key material.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The key type, state and deletion time. Replica keys and any external or custom key stores. The data-copy inventory and independent completion evidence.

Optional saved evidence: A custody owner must distinguish a pending key operation from completed data-exit evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Cryptographic erasure certification, deletion execution or all external key-material copies
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS Lambda: Successful invocation can still be repeated

Question: Does a successful asynchronous Lambda invocation rule out a duplicate event later?

AWS documents that asynchronous Lambda delivery can repeat the same event even when the function returns no error. Events can also expire or exhaust processing attempts. Function success alone does not establish unique delivery or a complete input history.

Source: AWS Lambda: Handling errors and retries with asynchronous invocation. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a successful asynchronous Lambda invocation rule out a duplicate event later?

Buyer evidence still required

  • Event identity and idempotency design.
  • Invocation attempts and recorded business outcome.
  • Event-age, retry and failure-destination settings.

Suggested review condition: Keep delivery attempts separate from completed effects and account for discarded inputs.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Asynchronous invocation settings, event identity, processing outcome and discard handling.

Optional saved evidence: Does a successful asynchronous Lambda invocation rule out a duplicate event later?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS last-accessed data: Attempts and tracking limits

Question: Does AWS last-accessed data prove a permission was successfully used?

No. AWS says service last-accessed data includes attempted calls, including denied attempts. Tracking periods, action coverage and policy types also limit interpretation. Correlate the relevant event evidence before concluding successful use, non-use or that a permission can be removed.

Source: AWS last-accessed data scope and interpretation. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Last-accessed history proves successful use or complete non-use of a permission.

Buyer evidence still required

  • Report scope, tracking window and supported action coverage
  • Relevant successful or denied event evidence
  • Effective policies and workload requirements beyond the report

Suggested review condition: Do not infer safe removal or successful use solely from a last-accessed report.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck report coverage, identity policies and workload changes.

Optional saved evidence: Save the attempt-versus-success distinction for an access procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS MCP: Downstream IAM authority

Question: Do old MCP-specific deny actions still establish a read-only boundary for an AWS agent?

AWS's current managed MCP documentation says downstream services apply the caller's IAM permissions. It explicitly marks the earlier MCP-specific IAM actions as ineffective and describes condition keys for distinguishing MCP-originated calls. OAuth through AWS Sign-in is also documented alongside the signed-request path. A historical policy name alone does not prove the current connection is restricted.

Source: AWS MCP downstream IAM authorization. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: AWS's managed MCP service in Agent Toolkit for AWS; not the local AWS API MCP package or Bedrock AgentCore runtime.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

AWS operates the managed service covered by these documents.

Documented by publisher. AWS MCP downstream IAM authorization; AWS MCP OAuth authentication

Purpose

Let agents call AWS services through existing IAM identities.

Documented by publisher. AWS MCP downstream IAM authorization

Read capability

Permitted downstream service reads use the caller's IAM rights.

Documented by publisher. AWS MCP downstream IAM authorization

Write capability

Downstream service permissions also govern requested mutations; the interface is not inherently read-only.

Documented by publisher. AWS MCP downstream IAM authorization

Authentication

SigV4 with AWS credentials, including temporary credentials, and OAuth 2.1 through AWS Sign-in are documented paths.

Documented by publisher. AWS MCP downstream IAM authorization; AWS MCP OAuth authentication

Permission surface

Old MCP-specific actions no longer enforce access; current policies can use MCP-origin condition context keys.

Documented by publisher. AWS MCP downstream IAM authorization

Data leaving the environment

Requests traverse the managed MCP service and AWS APIs; results return to the chosen agent client.

Review inference. AWS MCP downstream IAM authorization

Failure modes to consider

Relying on retired deny actions, selecting the wrong account/role, or granting broad downstream write permissions.

Review inference. AWS MCP downstream IAM authorization

Unknowns and applicability

Effective role/session policies, organization controls, endpoint region and client data handling.

Not established

Suggested refusal or clarification condition

Resolve account, role and effective current policy before acting; do not rely on an obsolete MCP deny action.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck IAM model changes, effective role/session restrictions and MCP-origin condition keys before relying on a policy.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep a dated policy-model reference showing why legacy deny statements need rechecking before agent access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS Organizations: A ceiling is not a grant

Question: Does an SCP allow statement give an agent permission to act in an AWS account?

Service control policies limit permissions without granting them. AWS states that SCPs affect member-account principals but not users or roles in the management account, and do not restrict service-linked roles. Other permission policies remain necessary.

Source: AWS Organizations: Service control policies. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does an SCP allow statement give an agent permission to act in an AWS account?

Buyer evidence still required

  • Account placement and principal type.
  • Applicable SCP hierarchy.
  • Identity or resource policy granting the requested action.

Suggested review condition: Establish both the applicable permission ceiling and a separate grant; record documented scope exceptions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Account type, principal category, attached SCPs and policies granting the action.

Optional saved evidence: Does an SCP allow statement give an agent permission to act in an AWS account?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS RCP: Resource boundaries and external callers

Question: Does an AWS resource control policy restrict the external resources an agent can access?

RCPs constrain supported resources in organization member accounts, including access by external principals. They do not constrain resources outside that organization merely because its identities access them. Their coverage is service-specific, with documented exceptions including calls by service-linked roles.

Source: Resource control policies (RCPs) - AWS Organizations. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an AWS resource control policy restrict the external resources an agent can access?

Buyer evidence still required

  • Resource owning account and organization.
  • Supported service and principal type.
  • Applicable RCP, identity and resource policies.

Suggested review condition: Do not rely on an RCP to constrain an external target or exempt principal without another applicable control.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Resource owning account and organization. Supported service and principal type. Applicable RCP, identity and resource policies.

Optional saved evidence: Separate resource-side restrictions from principal-side authority in an agent deployment review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Effective AWS access, universal service coverage or an authority grant
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS Savings Plan negation grouping

Question: Must every SavingsPlanCoveredUsage row match exactly one SavingsPlanNegation row?

SavingsPlanCoveredUsage unblended cost represents what usage would have cost without the benefit and is offset by negation entries. Negations are grouped hourly by SavingsPlanARN, operation, usage type and Availability Zone, so one can offset several covered rows. Use the documented grouping and SavingsPlanEffectiveCost for the intended calculation rather than summing counterfactual charges as new payable cost.

Source: Amazon Web Services: Savings Plans in Cost and Usage Reports. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Must every SavingsPlanCoveredUsage row match exactly one SavingsPlanNegation row?

Buyer evidence still required

  • covered and negation rows
  • hourly grouping fields
  • Savings Plan ARN
  • effective-cost fields

Review inference: A reconciliation demands a one-to-one negation match. Offsets can be dropped or on-demand-equivalent costs double counted. Adds the native AWS many-to-one offset mechanism, distinct from general billed/effective period bases. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Report arithmetic does not establish final invoicing, payment or realized savings for an unobserved deployment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. SavingsPlanNegation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Report arithmetic does not establish final invoicing, payment or realized savings for an unobserved deployment.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

AWS STS: Session restrictions and role authority

Question: Can an AssumeRole session policy grant an agent permissions beyond its role?

AWS describes session permissions as the intersection of the role identity policy and supplied session policies. A session policy cannot add permissions beyond that role policy. The role trust policy separately controls who may assume the role.

Source: AWS STS: AssumeRole. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an AssumeRole session policy grant an agent permissions beyond its role?

Buyer evidence still required

  • Role identity and trust policies.
  • Session policy actually supplied to AssumeRole.
  • Requested resource and temporary-session identity.

Suggested review condition: Compare the session restriction with the role permission basis; do not treat a session policy as an independent grant.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Assumed role, trust relationship, session policy and requested action.

Optional saved evidence: Can an AssumeRole session policy grant an agent permissions beyond its role?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS STS: Session tags and inherited authority context

Question: Do session tags automatically persist when an agent assumes another AWS role?

AWS STS does not pass session tags into later role sessions by default. Tags marked transitive persist during role chaining, with documented replacement behaviour for matching resource tags. Policies using tags therefore need the actual passed values and transitivity settings.

Source: AWS IAM: Pass session tags in AWS STS. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Do session tags automatically persist when an agent assumes another AWS role?

Buyer evidence still required

  • Session tag values and permitted tag keys.
  • Transitive-key configuration at assumption.
  • Relevant tag-based trust and permission conditions.

Suggested review condition: Reconstruct the tag context at the target session rather than assuming inheritance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Role chain, passed session tags, transitive keys and tag-based conditions.

Optional saved evidence: Do session tags automatically persist when an agent assumes another AWS role?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS STS: Source identity across a role chain

Question: Does a shared role session name alone preserve the original identity through an AWS role chain?

AWS distinguishes source identity from a role session name. Once set, source identity cannot change during the session and persists through role chaining. Administrators can require or constrain its value; the value's origin still needs an evidenced identity mapping.

Source: AWS IAM: Monitor and control actions taken with assumed roles. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a shared role session name alone preserve the original identity through an AWS role chain?

Buyer evidence still required

  • Initial authentication and identity mapping.
  • Trust conditions controlling source identity.
  • Role-chain records retaining the value.

Suggested review condition: Use source identity as attributable context only with evidence of who was allowed to set it.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Initial identity, source-identity requirements and chained role sessions.

Optional saved evidence: Does a shared role session name alone preserve the original identity through an AWS role chain?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

AWS usage reports and final billing evidence

Question: Does current AWS Cost Explorer or Cost and Usage Report data prove the final charge for a completed workflow?

AWS refreshes Cost Explorer data at least daily but notes upstream delays. Cost and Usage Reports are estimates during the month; service usage can arrive at different times. Usage charges are finalized after invoicing, and later credits, refunds or support adjustments can still update reports.

Source: Analyzing your costs and usage with AWS Cost Explorer - AWS Cost Management. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does current AWS Cost Explorer or Cost and Usage Report data prove the final charge for a completed workflow?

Buyer evidence still required

  • Report period and refresh time
  • Relevant usage line items and service delays
  • Invoice and subsequent adjustment evidence

Review inference: Reconcile reporting coverage and invoice adjustments before treating observed usage as a final charge.

Suggested review condition: Do not equate missing or provisional usage rows with zero or final cost.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s final invoice and late adjustments are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid closing cost reconciliation while usage or adjustments remain provisional.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Settled revenue or final billing from a usage dashboard
  • The buyer’s final invoice and late adjustments are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

Axios: A base URL does not establish a destination boundary

Question: Does configuring a base URL stop an agent's HTTP tool from contacting other hosts?

The Axios advisory for CVE-2025-27152 describes supplied absolute URLs overriding the configured base URL, potentially forwarding credentials or reaching unintended destinations. Review caller control over the URL and attached credentials; a base URL alone is not a destination restriction. The maintainer lists affected versions through 1.7.9 and 0.29.0, while the frozen ranges extend to the exclusive fixes 1.8.2 and 0.30.0. Preserve that range difference. This review establishes neither the destination controls of a buyer's tool nor a currently safe Axios version.

Source: Axios maintainer advisory: CVE-2025-27152. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (2)
  • npm / axios — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-jr5f-v2jv-69x6, captured 2026-10-08
  • npm / axios — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-jr5f-v2jv-69x6, captured 2026-10-08

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • a base URL treated as a verified destination restriction
  • affected-range differences silently resolved
  • verified credential loss or general SSRF clearance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure ABAC: A grant filter is not a global denial

Question: Does an Azure role-assignment condition explicitly deny the resource through every other grant?

An Azure ABAC condition narrows the permissions supplied by its role definition and assignment for the supported action context. Microsoft states that conditions cannot explicitly deny access to specific resources. A conditional grant is therefore not evidence of an account-wide deny.

Source: What is Azure attribute-based access control (Azure ABAC)? | Microsoft Learn. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an Azure role-assignment condition explicitly deny the resource through every other grant?

Buyer evidence still required

  • Role assignment and condition expression.
  • Applicable supported actions and attributes.
  • Other effective role assignments.

Suggested review condition: Do not describe a conditional assignment as a universal deny without reviewing other access paths.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Role assignment and condition expression. Applicable supported actions and attributes. Other effective role assignments.

Optional saved evidence: Identify alternate grants before relying on a restricted agent role assignment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Effective-access testing, legal compliance or a denial policy implementation
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure Activity Log: Control plane and resource operations

Question: Does the Azure Activity Log show everything an application did inside a resource?

Microsoft describes Activity Log as control-plane evidence and resource logs as the place for data-plane operations. Activity Log has a default retention window; diagnostic routing can retain entries elsewhere. Buyers should establish the required operation and destination instead of treating one activity view as a complete application history.

Source: Azure Activity Log control-plane coverage and retention. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The subscription Activity Log is a complete record of application data operations.

Buyer evidence still required

  • Operation-to-log-category mapping for the resource
  • Dated resource logging and diagnostic-routing configuration
  • Retention settings and retrieval evidence for the requested period

Suggested review condition: Qualify completeness when only control-plane history or the default retention view is available.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck resource log categories, diagnostic routes and retention policies.

Optional saved evidence: Save the distinction between resource administration and application activity evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure AI Search: A filter string is not authentication

Question: Does an Azure AI Search security filter authenticate the user named in the filter?

The documented security-filter pattern compares principal strings to indexed values; those strings do not authenticate or authorize the caller themselves. The application must establish caller identity and consistently apply the filter. This pattern is distinct from native ACL support.

Source: Azure AI Search: Security filters. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does an Azure AI Search security filter authenticate the user named in the filter?

Buyer evidence still required

  • Trusted caller-identity derivation.
  • Indexed principal metadata and query filter construction.
  • Tests covering every query path and omitted-filter handling.

Suggested review condition: Do not accept caller-supplied identity strings as proof of access authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Search mode, application identity checks, index metadata and query paths.

Optional saved evidence: Preserve the evidence needed to distinguish a search filter from an authenticated boundary.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure AI Search: Source deletion needs index-side evidence

Question: Can source document deletion leave retrievable copies in an Azure AI Search index?

Microsoft requires a deletion-detection strategy from the first indexer run; adding one later and resetting the indexer does not remove documents deleted before the policy existed. Native blob soft deletion must remain detectable until the indexer processes it. The documented soft-delete policies do not cover one-to-many indexing, which requires explicit index deletion requests.

Source: Changed and Deleted Blobs - Azure AI Search | Microsoft Learn. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can source document deletion leave retrievable copies in an Azure AI Search index?

Buyer evidence still required

  • Indexer/data-source type, key mapping and deletion policy from initial run.
  • Soft-delete retention, deletion timestamps and successful indexer processing.
  • Index inventory and explicit deletion results for orphaned or one-to-many documents.

Review inference: Source absence alone does not establish removal from the search index.

Suggested review condition: Refuse complete-index-cleanup claims without applicable policy and observed index-side results.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Historical indexer configuration and residual search results are unobserved.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck indexer type, key mappings, one-to-many behavior and retention windows.

Optional saved evidence: Identify residual resources before closing a data-retention or exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified index erasure, universal connector coverage or removal from external copies
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure AI: No foundation-model training is not zero storage

Question: Does Azure AI not training foundation models on prompts mean every feature is stateless?

The privacy documentation separates foundation-model training from feature storage and abuse monitoring. Responses and Assistants features can retain conversation state; human abuse review has a distinct handling path, with modified monitoring subject to approval. Review the actual feature and approved configuration before making a zero-storage claim.

Source: Azure model data processing and retained features. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: No foundation-model training proves no prompt or conversation storage.

Buyer evidence still required

  • API feature and deployment type used by the workload.
  • Stateful storage and deletion configuration.
  • Evidence of the applicable abuse-monitoring approval and settings.

Suggested review condition: Do not substitute a training statement for proof of retention behaviour.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. API feature, deployment type, monitoring approval and storage settings

Optional saved evidence: Save the feature-specific retention questions behind a no-training statement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure backup operational softdelete exclusions

Question: Does Azure Backup soft delete protect all operational snapshots and log recovery points equally?

Microsoft distinguishes vaulted backups from operational disk and VM snapshots that can be accessed and deleted directly before their soft-delete period expires. The reviewed guide excludes operational blob and Azure Files backups from soft-delete support and excludes SQL Server and SAP HANA log recovery points from recovery-point soft delete. Vault-level settings are not universal copy protection.

Source: Microsoft: Enhanced soft delete for Azure Backup. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Azure Backup soft delete protect all operational snapshots and log recovery points equally?

Buyer evidence still required

  • workload and backup type
  • vaulted versus operational copy inventory
  • snapshot access
  • recovery-point type
  • applicable regional support

Review inference: A custody review applies the vault's protection label to every operational backup. Directly deletable or unsupported copies may be reported as protected. Adds Azure workload-specific preservation exclusions; the existing record concerns AWS legal-hold propagation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse blanket soft-delete protection across all copies without checking these workload and recovery-point exclusions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Soft delete of recovery points

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse blanket soft-delete protection across all copies without checking these workload and recovery-point exclusions.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure backup softdelete rollout api scope

Question: Does an Azure Backup delete operation have the same retention effect in every region and API version?

Microsoft's reviewed secure-by-default guidance distinguishes preview-region behaviour from GA Recovery Services vault enforcement. Preview behaviour depends on client/API versions and prior configuration, while GA enforcement spans API versions. Soft-deleted data remains recoverable for the configured period. The region, vault type, rollout stage and request version are necessary to interpret a delete result.

Source: Microsoft: Enhanced soft delete for Azure Backup. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an Azure Backup delete operation have the same retention effect in every region and API version?

Buyer evidence still required

  • region and rollout status
  • vault type
  • soft-delete setting
  • client or API version
  • backup-item state and retention

Review inference: An exit workflow upgrades its API or moves regions without revisiting deletion assumptions. The same nominal delete action can retain recoverable data under different rules. Adds Azure rollout- and interface-dependent deletion semantics, rather than AWS lock settings. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not apply one rollout's behaviour globally or equate a delete response with permanent deletion. Recheck the current regional matrix before reliance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. API considerations for soft delete

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not apply one rollout's behaviour globally or equate a delete response with permanent deletion. Recheck the current regional matrix before reliance.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure blob overwrites and previous versions

Question: Does overwriting an Azure blob remove the data stored in its previous versions when versioning is enabled?

Azure Blob versioning preserves previous versions as immutable content and assigns version IDs to changes. Earlier versions can remain available after modification or deletion of the current blob. Microsoft recommends separate lifecycle or storage-action cleanup for old versions. Versioning itself does not protect against deletion of the storage account or container.

Source: Blob Versioning in Azure Storage - Azure Storage | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does overwriting an Azure blob remove the data stored in its previous versions when versioning is enabled?

Buyer evidence still required

  • Account versioning state and blob version inventory
  • Overwrite/deletion events and old-version cleanup configuration
  • Container/account protection and required deletion boundary

Review inference: Reconcile all version identities and cleanup settings rather than inspect only the current blob.

Suggested review condition: Do not declare prior content erased from a successful overwrite of the current blob.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The number and state of retained versions are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Find historical data that remains after an application replaces its live blob.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Removal of historical content from an overwrite alone
  • The number and state of retained versions are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure Blob soft delete: Recovery scope and exceptions

Question: Does blob soft delete also recover a deleted container or storage account?

No. Microsoft separates blob and container protection, and blob soft delete does not cover account deletion. The documentation also lists overwrite, metadata and permanent-delete limits. Review the exact deletion scenario and enabled protection before promising recovery.

Source: Azure Blob soft delete recovery coverage. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Blob soft delete protects every storage loss scenario.

Buyer evidence still required

  • Resource level and operation that caused loss
  • Protection enabled before the event and applicable retention
  • Relevant permanent-delete, overwrite and namespace settings

Suggested review condition: Require scenario-specific protection evidence before a recovery assurance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck namespace, deletion controls and retention changes.

Optional saved evidence: Preserve the recovery-scope checklist for a storage supplier review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure budgets: Alerts do not stop consumption by themselves

Question: Does creating an Azure Cost Management budget stop resources when the amount is reached?

The guide explicitly states that budget notifications do not affect resources or stop consumption. Cost data and budget evaluation are delayed; action groups can support separate automation. Record any actual enforcement mechanism rather than present the budget amount as a hard execution cap.

Source: Azure budgets and consumption. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The budget amount is an automatic resource-spending ceiling.

Buyer evidence still required

  • Budget scope, reset period and alert configuration.
  • Separate enforcement automation and its authority.
  • Observed data freshness, evaluation timing and enforcement outcome.

Suggested review condition: Do not infer resource suspension from a budget notification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Budget scope, evaluation timing, expiry and enforcement automation

Optional saved evidence: Retain which spending controls are alerts and which actually affect execution.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure cost export missing attributes

Question: Should Azure cost rows with missing subscription attributes be rejected as malformed?

The enhanced export experience uses null or empty values for missing attributes such as subscription IDs instead of a default empty GUID. The guide identifies unused reservations, unused savings plans and rounding adjustments as affected charges. Preserve their applicable billing context rather than silently discarding them or interpreting the placeholder change as a new subscription.

Source: Microsoft: Create and manage Cost Management exports. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Should Azure cost rows with missing subscription attributes be rejected as malformed?

Buyer evidence still required

  • export experience and schema version
  • missing attribute
  • charge type
  • billing scope
  • parser null handling

Review inference: An importer requires a nonempty subscription ID on every cost row. Valid unused-commitment and rounding charges are omitted. Adds Azure export identity-null migration, distinct from FOCUS consumption applicability. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Missing attribution does not mean zero charge or establish which team authorized the cost.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. missing attributes like subscription IDs

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Missing attribution does not mean zero charge or establish which team authorized the cost.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure cost export partitions replacement

Question: Does one downloaded Azure cost-export file preserve the complete report and its earlier version?

Enhanced exports partition data, with each file containing only a subset and the manifest describing the full set. Daily overwrite is enabled by default and replaces the previous day's file with updated data. Reconstruct a run from its manifest and all partitions, and preserve a dated copy if the earlier report is needed for reconciliation.

Source: Microsoft: Create and manage Cost Management exports. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Does one downloaded Azure cost-export file preserve the complete report and its earlier version?

Buyer evidence still required

  • export configuration
  • run manifest
  • all partition files
  • data version
  • overwrite setting
  • retained prior snapshot

Review inference: A buyer saves one part file as the historical cost evidence. Rows or the previously observed version can be lost. Adds Azure's concrete partition manifest and default replacement behavior rather than only FOCUS delivery rules. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A successful file download does not establish dataset completeness or immutable history.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Manifest file

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A successful file download does not establish dataset completeness or immutable history.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure DevOps MCP: Remote and local identity are not interchangeable

Question: Can the same Azure DevOps MCP setup be assumed to work for every organisation and action?

The remote offering documents Entra-backed organisations and differs from the locally configured server. The local inventory includes writes such as wiki and work-item changes, not just retrieval. Identify the deployment, organisation identity and effective grants before authorising operations; tool-name changes can also affect an existing client.

Source: Azure DevOps MCP overview and variants. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Remote Entra-backed offering and separately configured local server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Microsoft publishes the Azure DevOps MCP implementations.

Documented by publisher. Azure DevOps MCP overview and variants; Azure DevOps MCP tools and authentication

Purpose

Retrieve and manage supported Azure DevOps project information.

Documented by publisher. Azure DevOps MCP overview and variants; Azure DevOps MCP tools and authentication

Read capability

Authorised project, work-item, repository and wiki information.

Documented by publisher. Azure DevOps MCP overview and variants; Azure DevOps MCP tools and authentication

Write capability

The local inventory includes creation and updates, including wiki content.

Documented by publisher. Azure DevOps MCP overview and variants; Azure DevOps MCP tools and authentication

Authentication

Remote access uses the documented organisation identity path; local setup offers several credential modes.

Documented by publisher. Azure DevOps MCP overview and variants; Azure DevOps MCP tools and authentication

Permission surface

Organisation membership and granted project permissions remain relevant.

Documented by publisher. Azure DevOps MCP overview and variants; Azure DevOps MCP tools and authentication

Data leaving the environment

Project content and instructions pass through the selected MCP client and Azure DevOps service.

Review inference. Azure DevOps MCP overview and variants; Azure DevOps MCP tools and authentication

Failure modes to consider

Unsupported organisation identity, renamed tools and differing local/remote coverage can break a workflow.

Review inference. Azure DevOps MCP overview and variants; Azure DevOps MCP tools and authentication

Unknowns and applicability

Buyer organisation type, identity grants and enabled tool inventory are unknown.

Not established

Suggested refusal or clarification condition

Do not turn a retrieval request into a repository, wiki or work-item change without specific authority.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Remote availability, authentication modes, tool names and project grants.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the identity and change-authority assumptions behind a project integration decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure diagnostic destination network access

Question: Can an Azure diagnostic setting deliver to a firewalled Storage or Event Hubs destination without the required network allowance?

Azure diagnostic guidance requires the trusted Microsoft services network bypass for supported Storage or Event Hubs destinations with firewalls enabled. Creating a diagnostic setting does not itself establish reachable, authorized delivery. These destination-specific rules should not be generalized to every Log Analytics configuration.

Source: Diagnostic Settings in Azure Monitor - Azure Monitor | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an Azure diagnostic setting deliver to a firewalled Storage or Event Hubs destination without the required network allowance?

Buyer evidence still required

  • Diagnostic setting and destination type
  • Destination firewall and trusted-services setting
  • Delivery errors and received records

Review inference: Check destination network settings and actual incoming evidence after configuration changes.

Suggested review condition: Do not claim continuous export from the setting alone when destination access is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s network path and delivered data are untested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify a concrete failure mode in configured audit delivery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A blanket bypass requirement for every Azure destination
  • The buyer’s network path and delivered data are untested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure Key Vault disabled keys and retained material

Question: Does setting an Azure Key Vault key to disabled prove that its key material has been destroyed?

Key Vault exposes enabled as a key attribute controlling cryptographic use and documents key deletion as a separate operation. Deleted keys can themselves remain recoverable under soft delete. A disabled attribute is therefore not a key-destruction receipt, and even a deletion response must be interpreted with the vault’s retention and purge protections.

Source: Key types, algorithms, and operations - Azure Key Vault | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does setting an Azure Key Vault key to disabled prove that its key material has been destroyed?

Buyer evidence still required

  • Key identity, version and enabled attribute
  • Delete state, soft-delete retention and purge-protection settings
  • Required destruction boundary and provider operation evidence

Review inference: Keep disablement, deletion, recoverability and purge evidence distinct in an offboarding assessment.

Suggested review condition: Do not attest key destruction from enabled=false or an unqualified delete response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The underlying key material lifecycle and any external copies are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid presenting a reversible access control as irreversible key destruction.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Cryptographic erasure or physical destruction inferred from disablement
  • The underlying key material lifecycle and any external copies are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure locks: Resource protection does not cover every data operation

Question: Does an Azure read-only resource lock prevent changes to stored data?

Resource locks apply to control-plane operations. The documentation explicitly separates data-plane activity, including changes to database or storage contents that a resource lock does not prevent. Identify the actual operation and endpoint before accepting a claim that the locked resource is entirely immutable.

Source: Azure resource lock scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A resource lock prevents all changes or deletion of the data inside it.

Buyer evidence still required

  • Lock type and inherited resource scope.
  • The actual operation and service endpoint used.
  • Data-plane authorisation and separate retention/deletion controls.

Suggested review condition: Qualify immutability claims that rely solely on a management lock.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Lock scope, operation paths and separate data controls.

Optional saved evidence: Save why a management-lock screenshot was insufficient evidence for data immutability.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure logexport failure metric interpretation

Question: Does the Azure Export Failures metric count permanently missing log records?

The documented Export Failures metric counts failed export requests, including throttling, access and server errors. A retry process handles those attempts, so Microsoft explicitly says the metric is not an indication of missing data. Collection-health failures and confirmed record loss must be reported separately.

Source: Microsoft: Log Analytics workspace data export. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the Azure Export Failures metric count permanently missing log records?

Buyer evidence still required

  • metric definition and time window
  • retry outcomes
  • destination delivery evidence
  • source reconciliation

Review inference: A reporting system turns export errors into a count of missing audit events. The incident report can overstate or understate actual evidence loss. Adds aggregate-attempt interpretation, separate from query-level partial errors or documented possible pipeline loss. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not relabel failed-attempt counts as lost records or infer zero loss from an unexamined metric.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Export Failures

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not relabel failed-attempt counts as lost records or infer zero loss from an unexamined metric.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure logexport retry duplicate loss

Question: Does Azure Monitor data export deliver each log record exactly once despite destination outages?

Azure documents export retries for up to 12 hours when the destination lacks capacity or availability. Retries may duplicate some records, and data is discarded if the destination remains unavailable beyond that period. Both missing records and repeated delivery require reconciliation.

Source: Microsoft: Log Analytics workspace data export. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Azure Monitor data export deliver each log record exactly once despite destination outages?

Buyer evidence still required

  • export rule
  • destination availability and capacity
  • retry interval
  • received event identities
  • source counts where available

Review inference: A collector counts received rows as unique audited operations during an outage. Repeated rows and dropped evidence can distort the action history. Covers pipeline delivery to a destination, rather than partial results from a successful query response. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer exactly-once or loss-free delivery from an enabled export; retain explicit unknowns where source comparison is unavailable.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Data completeness

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer exactly-once or loss-free delivery from an enabled export; retain explicit unknowns where source comparison is unavailable.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure logexport start time coverage

Question: Does a new Log Analytics data-export rule include records already stored in the workspace?

Azure Monitor's continuous data-export rules export new table data as it arrives, starting from configuration time. The documentation identifies separate mechanisms for historical export, each with its own availability and limits. Rule creation alone is not a backfill receipt.

Source: Microsoft: Log Analytics workspace data export. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a new Log Analytics data-export rule include records already stored in the workspace?

Buyer evidence still required

  • rule creation time
  • required event interval
  • table plan
  • historical export job or query coverage

Review inference: An audit archive is added after a period of unexported operations. Historical events may remain missing from the external evidence store. Adds continuous-export start time, rather than which retained table data is queryable. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not report complete historic evidence from the continuous export rule alone; bind any backfill to its own result and limits.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. starting from the configuration time

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not report complete historic evidence from the continuous export rule alone; bind any backfill to its own result and limits.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure logexport unsupported table success

Question: Does successful creation of an Azure data-export rule prove every selected table is exported?

Azure says a rule containing an unsupported table can be configured successfully while exporting no data for that table. Its support list also contains tables with only certain ingestion paths supported. Configuration success must be reconciled against each table and ingestion source.

Source: Microsoft: Log Analytics workspace data export. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does successful creation of an Azure data-export rule prove every selected table is exported?

Buyer evidence still required

  • export rule tables
  • current support matrix
  • ingestion path
  • destination records
  • configuration date

Review inference: An operator selects all audit tables in an export rule. An unsupported table can silently contribute no external evidence. Adds source-path support exclusions, distinct from intentional transformations of supported data. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse all-table export coverage based only on rule creation or generic table presence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Unsupported tables

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse all-table export coverage based only on rule creation or generic table presence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure Logs: HTTP 200 can carry partial query results

Question: Does HTTP 200 from the Azure Monitor Logs API prove an evidence query completed without errors?

A non-fatal query error can return HTTP 200 with result tables and an error object whose code is PartialError. Consumers must inspect the response error details as well as the HTTP status before using the results as complete evidence.

Source: Azure Monitor Log Analytics API response format - Azure Monitor | Microsoft Learn. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does HTTP 200 from the Azure Monitor Logs API prove an evidence query completed without errors?

Buyer evidence still required

  • Complete response body.
  • Error code and nested details.
  • Expected query scope and reconciled rerun.

Suggested review condition: Do not mark the evidence extraction complete while a PartialError remains unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Complete response body. Error code and nested details. Expected query scope and reconciled rerun.

Optional saved evidence: Avoid accepting incomplete exported query results during incident reconstruction.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed query completeness, source-log completeness or recovery of missing rows
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure managed identity: Membership changes can remain cached

Question: Does removing an Azure managed identity from a group immediately remove its access everywhere?

The App Service managed-identity guide documents a per-resource-URI backend cache lasting around 24 hours. Group or role membership changes can take that long to affect access, and a token cannot currently be forced to refresh before expiry through that mechanism.

Source: Managed Identities - Azure App Service | Microsoft Learn. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does removing an Azure managed identity from a group immediately remove its access everywhere?

Buyer evidence still required

  • Managed identity, target resource and changed membership.
  • Change time and token validity context.
  • Target-side access checks and containment evidence.

Suggested review condition: Do not declare access removed immediately while cached membership and target behavior remain unverified.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Managed identity, target resource and changed membership. Change time and token validity context. Target-side access checks and containment evidence.

Optional saved evidence: Avoid closing urgent offboarding based solely on a membership update.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • An immediate revocation guarantee, customer access testing or every Azure authorization path
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure management group export hierarchy gap

Question: Does a root management-group diagnostic setting capture every subscription activity event?

Azure documents that subscription events lacking the hierarchy property do not propagate to management-group diagnostic settings, including the root. Subscription-level settings are needed for those events. Configuring both levels may duplicate shared events, so coverage and deduplication are separate checks.

Source: Microsoft: Azure Monitor activity log. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a root management-group diagnostic setting capture every subscription activity event?

Buyer evidence still required

  • management-group hierarchy
  • subscription diagnostic settings and categories
  • event hierarchy fields
  • destination identities

Review inference: A central audit team replaces per-subscription routing with a root-group rule. Some control-plane actions can disappear from the consolidated archive. Adds an export-hierarchy gap within control-plane events, distinct from the control-plane/data-plane split. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not claim full subscription coverage from root-group routing alone or remove necessary subscription routing merely to eliminate duplicates.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Subscription-level events without this property

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim full subscription coverage from root-group routing alone or remove necessary subscription routing merely to eliminate duplicates.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure MCP: Caller identity and deployment boundaries

Question: Can an agent assume a locally running cloud connector is isolated from production or has limited authority?

Microsoft documents Azure MCP access through Entra identities and Azure RBAC. A local process can still act with the developer's cloud permissions. Remote self-hosted deployments require protection of both the caller boundary and the server's execution identity. Microsoft explicitly excludes production data and credentials from its local-server guidance; this review does not verify a deployed gateway or role assignment.

Source: Azure MCP deployment and capabilities. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Microsoft-maintained Azure MCP Server, with local developer and remote self-hosted modes distinguished; excludes Foundry-specific MCP services.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Microsoft publishes Azure MCP; the party running a local or self-hosted deployment operates that instance.

Documented by publisher. Azure MCP deployment and capabilities; Azure MCP identity and deployment security

Purpose

Inspect Azure resources and support development, diagnostics and deployment operations.

Documented by publisher. Azure MCP deployment and capabilities

Read capability

Resource listings and diagnostic/query data are documented capabilities.

Documented by publisher. Azure MCP deployment and capabilities

Write capability

Deployment workflows and other permitted cloud operations can change resources.

Documented by publisher. Azure MCP deployment and capabilities

Authentication

Entra ID via Azure Identity is documented; remote guidance requires token and caller validation.

Documented by publisher. Azure MCP identity and deployment security

Permission surface

RBAC applies; broad caller or server identities require explicit restriction and per-caller checks.

Documented by publisher. Azure MCP identity and deployment security

Data leaving the environment

A local server still calls Azure and returns results to the client; local execution alone proves no data residency.

Review inference. Azure MCP deployment and capabilities; Azure MCP identity and deployment security

Failure modes to consider

Privileged developer sessions, a server lending its identity to callers, or unreviewed tool changes.

Review inference. Azure MCP identity and deployment security

Unknowns and applicability

Tenant, subscription, role assignments, deployment mode, gateway enforcement and client recipients.

Not established

Suggested refusal or clarification condition

Do not use the local developer path for production data; verify caller, server identity and target before a remote change.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck execution identity, caller validation, roles and tool definitions when changing deployment mode.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the caller/server-identity and local-versus-remote boundaries behind a cloud-tool review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure Monitor: Ingestion transformations can remove evidence

Question: Can a Log Analytics table be assumed to contain the original unfiltered event stream?

Azure Monitor transformations can filter or modify incoming data after the source delivers it and before the destination receives it. The data collection rule defines this processing. Stored rows can therefore reflect transformation choices rather than the original stream.

Source: Azure Monitor: Data collection transformations. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a Log Analytics table be assumed to contain the original unfiltered event stream?

Buyer evidence still required

  • Active data collection rule and transformation.
  • Source fields compared with stored fields.
  • Filter criteria and evidence for omitted record classes.

Suggested review condition: Describe the transformed evidence scope; do not claim raw completeness from destination rows alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Data collection rule, supported destination table, transformation and source window.

Optional saved evidence: Can a Log Analytics table be assumed to contain the original unfiltered event stream?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure point-in-time restore coverage limits

Question: Does Azure Blob point-in-time restore recover every blob type and a container deleted during the restore period?

Azure point-in-time restore is limited to block blobs in supported standard general-purpose v2 accounts and supported access tiers. It does not restore append, page or premium block blobs, and it does not restore a deleted container. A restore range containing blobs in a deleted container can fail. Recovery scope depends on resource type and history.

Source: Point-in-time restore for block blobs - Azure Storage | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Azure Blob point-in-time restore recover every blob type and a container deleted during the restore period?

Buyer evidence still required

  • Account type, namespace configuration and blob types/tiers
  • Container deletion history and requested restore range
  • Required restore point and resource-level outcomes

Review inference: Match the required exit or recovery inventory to the documented restore coverage before relying on a single rollback operation.

Suggested review condition: Reject complete recovery claims when unsupported resources or a deleted container are unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual restore outcome and the buyer’s resource inventory are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid choosing a recovery mechanism that cannot cover the affected resources.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Recovery of every storage operation or deleted container by point-in-time restore
  • The actual restore outcome and the buyer’s resource inventory are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure Policy: Evaluation and enforcement modes

Question: Does an assigned Azure policy prove non-compliant changes are blocked?

DoNotEnforce evaluates compliance without enforcing the policy effect. Disabled effect is different because it avoids evaluation. Assignment exclusions and scoped overrides also matter. Remediation tasks for deployIfNotExists can still be started in DoNotEnforce mode; that mode is not a blanket no-change guarantee.

Source: Azure Policy assignment structure. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A policy assignment proves blocking, or DoNotEnforce prevents every change.

Buyer evidence still required

  • Assignment mode, definition and effect.
  • Scope exclusions and overrides.
  • Remediation tasks and actual enforcement evidence.

Suggested review condition: Check evaluation, enforcement and remediation separately before describing the control.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Assignment mode, definition version, scope, overrides and remediation.

Optional saved evidence: Preserve the evidence boundary between a compliance report and enforced prevention.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure private endpoints: Public access and service targets remain separate

Question: Does adding an Azure Storage private endpoint automatically disable public network access?

The storage guide treats the private endpoint and public-endpoint access rules separately. Storage services need their applicable endpoints, and name resolution must reach the private address. An endpoint's existence alone does not prove all service traffic uses it or that public access is blocked.

Source: Azure Storage private endpoints. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: One private endpoint makes all storage services private-only.

Buyer evidence still required

  • Public network-access and firewall settings.
  • Required service endpoints.
  • DNS resolution from the actual caller.

Suggested review condition: Require service-specific network evidence before claiming private-only access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Storage service, endpoint, DNS and public access settings

Optional saved evidence: Keep the endpoint, DNS and public-access conditions behind a private-network claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure replication policy removal versus data cleanup

Question: Does removing an Azure object-replication policy itself demonstrate cleanup of destination blob copies?

Microsoft’s removal procedure deletes policy objects and their rules on both source and destination accounts. Recreating a policy establishes a new relationship with a new ID and does not reuse the old replication state. The replication guide separately describes destination blob versions and asynchronous copying. Policy removal is control-plane evidence, not a destination erasure report.

Source: Configure object replication - Azure Storage | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does removing an Azure object-replication policy itself demonstrate cleanup of destination blob copies?

Buyer evidence still required

  • Source/destination accounts, policy IDs and deletion results
  • Replicated blob/version inventory and pending operations
  • Required destination cleanup scope and observed outcomes

Review inference: Inventory and reconcile destination generations separately from the removed replication relationship.

Suggested review condition: Do not confirm destination erasure solely from deleting replication rules.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual destination copies and storage cleanup are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a control-plane shutdown from being mistaken for removal of replicated data.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Deletion of destination data inferred from a policy operation
  • Actual destination copies and storage cleanup are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure reservation recommendation history

Question: Can an Azure reservation recommendation export reconstruct a past purchasing recommendation?

Reservation recommendation exports represent the current snapshot and do not support historical backfill. Historical export support for other datasets must not be generalized to recommendations. To assess what was presented when a commitment was approved, use a retained, dated recommendation and its parameters rather than a current export requested for an earlier period.

Source: Microsoft: Create and manage Cost Management exports. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Can an Azure reservation recommendation export reconstruct a past purchasing recommendation?

Buyer evidence still required

  • dated saved recommendation
  • scope
  • lookback period
  • resource type
  • purchase approval date

Review inference: A buyer audits why an agent recommended a reservation last quarter. A current recommendation can be misrepresented as the historical basis. Adds a non-backfillable recommendation evidence boundary rather than delayed billing usage. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A recommendation does not prove realized savings, historical approval or suitability of a new commitment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. current snapshot only

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A recommendation does not prove realized savings, historical approval or suitability of a new commitment.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Azure retained logs and query availability

Question: Does total Azure Log Analytics retention guarantee the same interactive query window for every table plan?

Azure distinguishes analytics retention from long-term retention. Analytics and Basic long-term data is retrieved through search jobs, while Auxiliary data remains queryable throughout its total retention period. The table plan and retention state therefore determine the available retrieval method; retained data is not always available through the same query path.

Source: Manage Data Retention in a Log Analytics Workspace - Azure Monitor | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does total Azure Log Analytics retention guarantee the same interactive query window for every table plan?

Buyer evidence still required

  • Table plan and analytics/total retention settings
  • Requested time range and query or search-job mode
  • Retrieval result and coverage assessment

Review inference: Verify table plan, time range and retrieval mode before treating an empty interactive query as missing evidence.

Suggested review condition: Do not infer deletion solely from an inappropriate query path.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s retained rows and successful recovery are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Choose the correct retrieval path during an audit or recovery investigation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal interactive access throughout every retention period
  • The buyer’s retained rows and successful recovery are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Azure SAS: Revocation depends on signature type and policy association

Question: Can one stored access policy revoke every Azure shared access signature?

Stored access policies apply to associated service SAS tokens. User-delegation and account SAS tokens do not support that association. Identify the SAS type and revocation mechanism before claiming that a policy change ends access; an ad hoc signature cannot inherit a policy it was never linked to.

Source: Azure SAS types and revocation. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Changing a stored policy revokes every issued SAS for the resource.

Buyer evidence still required

  • Inventory of SAS types and signing methods.
  • Policy association for the specific service SAS.
  • Documented and tested revocation path for each unassociated token type.

Suggested review condition: Keep universal revocation claims open until every token type is covered.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. SAS issuance patterns, policy associations and key/delegation lifecycle.

Optional saved evidence: Save the evidence needed to distinguish policy-linked revocation from other SAS lifecycles.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Background long-term memory write completion versus response completion; distinct from checkpoint durability modes

Question: Does an agent response establish that its background memory write has finished?

The LangGraph guide distinguishes memory writes in the request path from background/asynchronous updates with different timing and complexity.

Source: LangChain primary documentation: langgraph memory. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an agent response establish that its background memory write has finished?

Buyer evidence still required

  • write mode
  • job/request correlation
  • completion state
  • stored IDs
  • dependent retrieval check

Review inference: Does an agent response establish that its background memory write has finished? Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions. Background long-term memory write completion versus response completion; distinct from checkpoint durability modes. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. In the background

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat response completion as memory persistence confirmation; capture the background write outcome and the visibility point for dependent actions.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

public scale reduction with boundaries

BDAS 163M-Row Public Reduction — Public-Scale Summary

Question: What does the 163M-row public reduction record evidence?

Public-safe public-scale reduction summary. It gives the index a scale signal while preserving claim boundaries.

Claim boundaries
  • end-to-end commercial saving
  • production readiness
  • independent replication
  • broad workload applicability
  • mechanism disclosure

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

recovered frozen tranche

BDAS 7001071 — Recovered INDEX Corpus Tranche

Question: What does the 7001071 INDEX tranche evidence?

Public-safe index entry for the recovered 7001071 corpus tranche. It signals corpus existence and bounded validation posture without exposing private artefacts.

Claim boundaries
  • new performance claim
  • production readiness
  • generalised selective execution
  • customer savings

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

correctness qualified economics not qualified

BDAS 7026446 — Correctness Qualified, Economics Not Qualified

Question: How can correctness pass while economics fail?

Public-safe record showing separation between correctness qualification and economic non-qualification.

Claim boundaries
  • economic gain
  • end-to-end acceleration
  • commercial saving
  • outer holdout promotion

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

staged candidate batch

BDAS 7026447 — Candidate Batch Summary

Question: What does the 7026447 candidate batch evidence?

Public-safe summary of the 7026447 staged candidate batch. It exposes counts and status boundaries only.

Claim boundaries
  • all candidates canonical
  • all candidates public-safe
  • runtime API availability
  • external validation of every candidate

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

development characterisation no operator freeze

BDAS Backblaze D0: Development characterisation

Question: Does Backblaze D0 characterisation establish a qualified selective operator?

The D0 source records completed development characterisation with no operator freeze. Qualification and locked-outer access remain recorded as unopened. This is preparation evidence, not an acceleration result.

Supplied evidence reviewed 2026-10-07. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • qualified selective operator
  • performance acceleration
  • fresh qualification result
  • locked-outer validation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

reported development exactness failure no promotion

BDAS Backblaze D1 recovery: Exact-output gate not passed

Question: Did the later Backblaze D1 recovery establish exact output and a qualified speedup?

The supplied D1 recovery review reports acceptable operator quality and retained reference alerts on consumed development data, but an additional output caused the exact-output gate to fail. Repeated performance timing was withheld. This is a review summary, not an independently rechecked archive or rerun, and it supports no performance qualification or promotion.

Supplied review examined 2026-10-07. The original archive and experiment were not independently rechecked during this intake.

Claim boundaries
  • exact-output equivalence
  • qualified acceleration or cost savings
  • fresh holdout validation
  • independent archive verification by this intake

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

worker failed no promotion

BDAS Backblaze D1: Worker failure

Question: Can Backblaze D1 be cited as a successful performance result?

The D1 final state is worker failure. The supplied final record reports qualification and locked outer unopened and no production promotion. No successful performance result can be inferred from this run.

Supplied evidence reviewed 2026-10-07. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • successful performance campaign
  • operator correctness demonstrated by completion
  • qualification success
  • production promotion

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

reported exact development replay not performance qualified

BDAS Backblaze D2: Reported exactness without performance qualification

Question: Does the supplied Backblaze D2 review establish a performance-qualified result?

The supplied D2 review reports exact replay on consumed development data, with the evaluated path slower in its reported matched timing comparisons and no net reduction in heavy work. Its disposition is exact development replay without performance qualification. This intake reviewed the report and lineage only; it did not recheck the underlying archive, rerun the experiment or establish fresh holdout performance.

Supplied review examined 2026-10-07. The original archive and experiment were not independently rechecked during this intake.

Claim boundaries
  • performance qualification or acceleration
  • fresh holdout validation
  • production promotion
  • general exactness guarantee
  • independent replication by this intake

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

locked outer evaluation with boundaries

BDAS C1 Pump — Locked Outer Evaluation

Question: What does C1 Pump locked outer evidence?

Public-safe locked outer pump evaluation summary. Useful for pump-specific due diligence and paid bounded requests.

Claim boundaries
  • broad pump diagnostics
  • production deployment
  • customer saving
  • unrestricted acceleration
  • external generalisation beyond scope

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

promising development not promoted

BDAS C3 Info-Geometry — Promising Development Record

Question: What does C3 info-geometry evidence?

Public-safe development record. It signals promising direction while refusing premature promotion.

Claim boundaries
  • qualification promotion
  • production readiness
  • customer saving
  • external validation
  • deployed capability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

not promising development record

BDAS C4 Machine-Local Calibration — Not Promising

Question: What does C4 machine-local calibration evidence?

Public-safe negative development record. It helps show that VAREXIS preserves dead-ends and not-promising paths.

Claim boundaries
  • promoted calibration capability
  • performance improvement
  • deployment readiness
  • commercial saving
  • general method success

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

validation probe pass

BDAS Centered Live Probe V1 — Validation Probe Pass

Question: What does Centered Live Probe V1 evidence?

Public-safe probe-pass record. Useful for showing build/check discipline without implying public runtime service.

Claim boundaries
  • public API availability
  • production deployment
  • external customer use
  • commercial saving
  • unrestricted reliability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

capture complete no promotion

BDAS CK4A — Capture Complete, No Promotion

Question: What does CK4A evidence?

Public-safe record preserving capture and replay evidence without converting it into an unsupported promotion claim.

Claim boundaries
  • new acceleration claim
  • promotion decision
  • new holdout access
  • calibration fit

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

contract binding check pass

BDAS Consumer Binding V1 — Contract Binding Check

Question: What does Consumer Binding V1 evidence?

Public-safe contract-binding record. Useful for developer confidence without overstating runtime availability.

Claim boundaries
  • public runtime deployment
  • performance qualification
  • customer saving
  • external production use
  • deployment approval

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

decoder check pass

BDAS Decoder V4 — Decoder Check Pass

Question: What does Decoder V4 evidence?

Public-safe decoder validation summary. Useful as an interface-confidence record, not a performance claim.

Claim boundaries
  • performance acceleration
  • production deployment
  • mechanism disclosure
  • customer saving
  • general workload qualification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

attribution check pass

BDAS Fused Attribution V2 — Attribution Check Pass

Question: What does Fused Attribution V2 evidence?

Public-safe attribution check record. It supports the index concept of source/evidence binding without exposing private material.

Claim boundaries
  • truth of all claims
  • deployment readiness
  • independent validation
  • public exposure of private sources
  • certification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

locked synthetic confirmation

BDAS G5.2 — Locked Synthetic Confirmation

Question: What does G5.2 evidence?

Public-safe locked synthetic confirmation record. It gives the index a controlled exactness signal while preserving boundaries.

Claim boundaries
  • external generalisation
  • customer saving
  • production deployment
  • independent validation
  • real-world performance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

locked seed validation pass with boundaries

BDAS H1.3 — Locked-Seed Validation

Question: What does H1.3 evidence about BDAS selective execution?

Public-safe positive validation record for H1.3. It supports bounded selective-execution posture while refusing broader deployment and savings claims.

Claim boundaries
  • production deployment
  • customer saving
  • external generalisation
  • unrestricted performance acceleration
  • mechanism disclosure

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

safe not selective

BDAS H2.1 — Hydraulic Pump Safe But Not Selective

Question: What does H2.1 evidence about external pump evaluation?

Public-safe record showing that an external pump result may be safe but not selective. This is valuable because the index preserves refusal boundaries.

Claim boundaries
  • selective execution qualification
  • performance qualification
  • production pump monitoring readiness
  • customer saving
  • broad pump diagnostic capability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

development pass

BDAS I1 — Development Pass

Question: What does I1 evidence within the BDAS development chain?

Public-safe development-pass record. It helps show evidence progression without overstating maturity.

Claim boundaries
  • external validation
  • production readiness
  • commercial saving
  • independent replication
  • unrestricted deployment claim

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

reserved hashed holdout

BDAS I2 — Holdout Reserved and Hashed

Question: What does I2 evidence about holdout discipline?

Public-safe holdout-control record. It shows reservation and integrity posture without claiming unopened performance.

Claim boundaries
  • holdout performance
  • production readiness
  • customer saving
  • external generalisation
  • post-hoc validation upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

synthetic reduction evidence with boundaries

BDAS IIoT Synthetic 60M Logs — Public-Safe Reduction Summary

Question: What does the IIoT synthetic 60M-log record evidence?

Public-safe scale summary for synthetic IIoT-style workload reduction. It is a discovery record, not a customer ROI claim.

Claim boundaries
  • real customer environment validation
  • production deployment
  • customer saving
  • external independent replication
  • broad sensor-data generalisation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

canonical freeze bundle

BDAS INDEX Ledger 0042 — Canonical Freeze Bundle

Question: What does ledger entry 0042 evidence?

Public-safe summary of ledger bridge VRX-RL-2026-0042, binding a set of canonical INDEX freezes without exposing private logs or mechanisms.

Claim boundaries
  • production deployment
  • performance qualification
  • commercial saving
  • external generalisation
  • mechanism disclosure

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

qualification development pass with boundaries

BDAS M1 — Qualification Engine With AURIC Monitor

Question: What did the M1 qualification engine establish?

Public-safe M1 record showing qualification-engine posture and AURIC-monitor boundary without exposing implementation mechanics.

Claim boundaries
  • unrestricted external generalisation
  • production deployment
  • all workloads qualified
  • automatic commercial readiness

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

safe refusal

BDAS M3 — External Locked Safe Refusal

Question: What does M3 evidence?

Public-safe safe-refusal record. It demonstrates that VAREXIS preserves non-promotion and refusal outcomes as part of the evidence index.

Claim boundaries
  • qualification promotion
  • selective execution approval
  • external performance success
  • customer deployment suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

protocol and dataset receipt

BDAS M4 — Manufacturing External Protocol

Question: What does M4 manufacturing evidence?

Public-safe external protocol record. It signals proper protocol and receipt discipline without claiming result success.

Claim boundaries
  • performance qualification
  • deployment readiness
  • commercial saving
  • post-hoc scoring claim
  • broad manufacturing generalisation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

fresh external safe refusal

BDAS M4: Manufacturing safe refusal

Question: Does M4's manufacturing outcome demonstrate selective performance?

The supplied M4 result records non-qualification before outer scoring and use of the full-processing fallback. It supports a bounded safe-refusal outcome beyond the earlier protocol-only summary, without establishing selective performance.

Supplied evidence reviewed 2026-10-07. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • external selective validation
  • heavy-kernel speedup
  • customer savings
  • production readiness

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

fresh external safe refusal

BDAS M4B: Centrifuge safe refusal

Question: What does M4B establish when its centrifuge candidate was not qualified?

The supplied M4B evidence records non-qualification frozen before outer scoring and a full-processing fallback. Its accepted outcome is bounded safe refusal; candidate diagnostics do not establish live selective performance.

Supplied evidence reviewed 2026-10-07. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • selective-execution promotion
  • economic speedup
  • heavy-kernel performance
  • production readiness

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

model evaluation unestablished

BDAS M4B: Prospective observation limits

Question: Does the M4B prospective prediction establish a validated workload classifier?

The supplied observation record describes a prediction frozen before scoring and evaluated after the outcome. It preserves prospective evaluation evidence while the model remains unestablished; it grants no execution authority.

Supplied evidence reviewed 2026-10-07. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • validated workload-suitability classifier
  • promotion authority
  • permission to skip execution
  • broad predictive accuracy

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

fresh external safe refusal

BDAS N1: Wind SCADA safe refusal

Question: Does the N1 wind-SCADA outcome establish selective-execution performance?

The supplied N1 evidence records a fallback selected before outer truth access when candidates did not qualify. The recorded external outcome supports safe refusal, not selective-execution performance.

Supplied evidence reviewed 2026-10-07. The experiment was not rerun; protected source material is not published.

Claim boundaries
  • selective-execution promotion
  • acceleration or customer savings
  • production readiness
  • broad external generalisation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

safe but not performance qualified

BDAS NASA IMS E4.1 — Safe But Not Performance Qualified

Question: What did NASA IMS E4.1 demonstrate?

Public-safe record for NASA IMS E4.1. It is valuable because it preserves exact/safe external evidence while refusing an unsupported performance claim.

Claim boundaries
  • performance qualification
  • deployment readiness
  • general acceleration claim
  • commercial cost saving

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

development check no reduction promotion

BDAS OT3 — Frequency-Localized Development Record

Question: What does OT3 evidence?

Public-safe development record showing that no-reduction or non-promoted results remain useful in the index.

Claim boundaries
  • workload reduction
  • performance qualification
  • production deployment
  • commercial saving
  • broad diagnostic capability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

persistence check pass

BDAS Persistent Output V3 — Output Persistence Check

Question: What does Persistent Output V3 evidence?

Public-safe persistence record. It supports evidence-route discipline without publishing raw outputs.

Claim boundaries
  • claim truth
  • production readiness
  • public runtime availability
  • raw output disclosure
  • deployment approval

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

challenged negative

BDAS PUMP-E1 — Challenged Negative Evidence

Question: Why is PUMP-E1 not a promoted selective-execution claim?

PUMP-E1 is indexed as a negative/challenged record. It demonstrates that VAREXIS-INDEX preserves failed or non-promoted evidence rather than deleting it.

Claim boundaries
  • safe promotion
  • zero false skips
  • deployment suitability
  • broad pump diagnostic capability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

supported with boundaries

BDAS PUMP-E2C — Consumed Engineering Selective Execution Evidence

Question: What exactly is evidenced by PUMP-E2C?

Existing public full record for PUMP-E2C consumed engineering selective-execution evidence.

Claim boundaries
  • fresh holdout validation
  • production readiness
  • customer savings
  • external generalisation
  • full score reconstruction
  • unrestricted performance acceleration
  • broad pump-audio diagnostic capability
  • hardware-mismatched consumer contract

VAREXIS-INDEX informs evidence reliance; it does not grant authority to deploy or act.

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.

Machine-readable record · Human record · Request an answer or receipt

correctness strong economics not qualified

BDAS QV1 PCB1 Vision — Correctness Strong, Economics Not Qualified

Question: What did QV1 PCB1 vision demonstrate?

Public-safe record showing that correctness evidence was not inflated into an economics claim.

Claim boundaries
  • net end-to-end economic gain
  • production readiness
  • broad vision workload acceleration
  • unbounded deployment claim

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

reference compatibility only

BDAS S1 Spectral Alarm — Reference Compatibility Record

Question: What does the S1 spectral alarm reference evidence?

Public-safe spectral reference record. Useful for routing spectral questions while refusing deployment claims.

Claim boundaries
  • production alarm system
  • commercial deployment
  • broad sensor acceleration
  • safety certification
  • customer saving

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

exact replay diagnostic

BDAS S1 Spectral Replay — Exact Replay Evidence

Question: What does S1 spectral replay evidence?

Public-safe replay record preserving exact/diagnostic evidence while refusing production or broad deployment claims.

Claim boundaries
  • production alarm system
  • external deployment
  • general sensor acceleration
  • commercial saving

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

controlled reduction with boundaries

BDAS Stage B — Controlled Reduction Evidence

Question: What does Stage B evidence about BDAS reduction?

Public-safe controlled-reduction record for BDAS. It is useful as a positive but bounded commercial-interest signal.

Claim boundaries
  • general acceleration
  • production saving
  • external customer validation
  • independent replication
  • unrestricted workload applicability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

safe not selective

BDAS Stage F/G — Safe But Not Selective

Question: What does Stage F/G evidence?

Public-safe negative/boundary record. It demonstrates that VAREXIS preserves non-promoted outcomes.

Claim boundaries
  • selective execution qualification
  • performance qualification
  • deployment readiness
  • customer saving
  • broad workload claim

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Bedrock crawler: Source access and retrieval access differ

Question: Does a Bedrock web-crawler knowledge base preserve the source site's access controls?

The crawler guide warns that synced data is retrievable by anyone with bedrock:Retrieve permission, including content with source access controls. The source's permission model must not be assumed to survive ingestion. Review the knowledge-base audience and admitted content separately.

Source: Bedrock: Web crawler data source. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a Bedrock web-crawler knowledge base preserve the source site's access controls?

Buyer evidence still required

  • Authorised source URLs and crawl scope.
  • Knowledge-base retrieval principals.
  • Evidence of any additional application access enforcement.

Suggested review condition: Do not admit restricted content on the assumption that source permissions automatically constrain retrieval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Source permissions, crawl boundaries, knowledge-base audience and application controls.

Optional saved evidence: Retain the source-to-retrieval access review before admitting a knowledge connector.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Bedrock ingestion: Changes need a completed sync

Question: Does deleting a source file immediately remove it from a Bedrock managed knowledge base?

The managed knowledge-base guide requires synchronization after source additions, changes or removals. A sync request has an ingestion-job identity, status and document statistics; starting one is not evidence that deletion has completed. Scheduled or on-demand configuration determines when work begins.

Source: Bedrock: Sync a data source. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does deleting a source file immediately remove it from a Bedrock managed knowledge base?

Buyer evidence still required

  • Source-change time and affected document identity.
  • Matching ingestion-job status and statistics.
  • Post-sync retrieval evidence for the removed content.

Suggested review condition: Keep deletion completion unresolved until matching sync and retrieval evidence is available.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Managed knowledge base, data source, change time and ingestion job.

Optional saved evidence: Save the dated synchronization evidence required for a deletion claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Bedrock RETURN_CONTROL: Handoff and execution are separate

Question: Does Bedrock RETURN_CONTROL mean that an action group operation has already executed?

With RETURN_CONTROL configured, Bedrock returns the predicted action's inputs and an invocationId in InvokeAgent. The application performs the API or function work and supplies returnControlInvocationResults on a later invocation, using the matching invocationId and actionGroup. When those results are supplied, inputText is ignored. The returned control payload is the application's handoff point.

Source: Return control to the agent developer by sending elicited information in an InvokeAgent response - Amazon Bedrock. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Bedrock RETURN_CONTROL mean that an action group operation has already executed?

Buyer evidence still required

  • Action-group executor configuration and original invocation inputs.
  • Application action receipt, result state and external resource identifiers.
  • Matching invocationId, actionGroup and returnControlInvocationResults.

Review inference: A handoff or submitted result is insufficient to establish an external operation without its outcome evidence.

Suggested review condition: Refuse completion claims that treat the handoff as execution or cannot bind returned results to the invocation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer action-group implementation or result authenticity was assessed.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck action-group executor mode, result fields and session-state behavior after agent changes.

Optional saved evidence: Bind an action request to the outcome evidence needed for a business decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified external execution, authorization or truthful application-supplied results
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Bedrock: Deleting a data source can retain indexed data

Question: Does deleting a Bedrock knowledge-base data source remove its vector data and store?

Bedrock documents separate DELETE and RETAIN data-deletion policies. RETAIN leaves the data; DELETE removes the data without deleting the vector store itself and can fail because of vector-store configuration or access. DELETE_UNSUCCESSFUL and failureReasons identify an unsuccessful deletion. Data-source removal alone does not establish complete exit cleanup.

Source: Amazon Bedrock: Delete a knowledge-base data source. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Enterprise AI Data Custody & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a Bedrock knowledge-base data source remove its vector data and store?

Buyer evidence still required

  • The knowledge base, data source, vector store and effective deletion policy.
  • Deletion status and any failureReasons.
  • Reconciliation of retained vectors, the store and other scoped copies.

Suggested review condition: Do not mark AI data exit complete while the policy retains data, deletion has failed or the separately managed store remains outside the review.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The knowledge base, data source, vector store and effective deletion policy. Deletion status and any failureReasons. Reconciliation of retained vectors, the store and other scoped copies.

Optional saved evidence: A data owner ending an AI retrieval integration needs evidence for derived vectors and the separately managed store, not only the connector record.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Bedrock: Guardrail coverage depends on tagging and enforced controls

Question: Does attaching a Bedrock guardrail establish that every part of a prompt was evaluated?

Bedrock supports selective input evaluation, including tagged content for InvokeModel APIs. Separately enforced organisation or account controls can require comprehensive evaluation regardless of caller tags. Coverage depends on the API, content selection and effective enforcement configuration; a guardrail identifier alone is insufficient.

Source: Bedrock selective guardrail evaluation. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does attaching a Bedrock guardrail establish that every part of a prompt was evaluated?

Buyer evidence still required

  • The API and request content-selection mechanism.
  • The guardrail version and enabled filters.
  • Effective account or organisation selective/comprehensive controls.

Suggested review condition: Do not infer whole-prompt coverage or a tagging bypass without reviewing the applicable enforced configuration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The API and request content-selection mechanism. The guardrail version and enabled filters. Effective account or organisation selective/comprehensive controls.

Optional saved evidence: An AI gateway owner must establish the actual evaluated content before relying on a prompt-screening result.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Runtime enforcement by INDEX, safety certification or successful detection of harmful content
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

reported workload boundaries no new benchmark

Benchmark review: Keep different workload claims separate

Question: Can a benchmark gain on repeated work support a claim about processing new inputs?

The supplied lineage review keeps an existing result for repeated-work conditions separate from evaluations of new-input processing. Their recorded gains cannot be transferred between the two claims. The review reports no new runtime measurements and uses historical evaluation material; it does not establish fresh holdout performance or customer savings. Before comparing results, require matching workload assumptions, required outputs and cost accounting.

Supplied review examined 2026-10-11. The original archive and experiment were not independently rechecked during this intake.

Claim boundaries
  • performance gains transferred between different workloads
  • new benchmark measurements from a lineage review
  • fresh holdout validation from historical material
  • customer savings or production qualification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

BigQuery authorized views: Shared results and query authority

Question: Does a BigQuery authorized view require giving the reader direct access to source tables?

An authorized view can expose selected query results without giving readers direct access to the source dataset. Authorization on the source, access to the view and permission to run a query job are separate. Underlying row and column policies remain relevant; a view name alone is insufficient evidence of the exposed data.

Source: BigQuery authorized views. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Using a view requires full underlying dataset access.

Buyer evidence still required

  • View definition and source authorization.
  • Reader access and query-job project.
  • Applicable row and column policies.

Suggested review condition: Require the actual view definition and effective grants before approving disclosure.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. View definition, source authorization, reader grants and underlying policies

Optional saved evidence: Preserve a bounded data-sharing decision without overstating source-table authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

BigQuery deletion: Recovery windows remain material

Question: Does deleting a BigQuery table immediately remove all retained history?

Changed or deleted table data remains within the configured time-travel window, followed by a separate fail-safe period. A deleted table uses the window in force at deletion; increasing the setting later does not simply extend that earlier deletion's recovery window. These are retention boundaries, not a legal erasure conclusion.

Source: BigQuery time travel and fail-safe. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Delete removes all history immediately or later settings automatically extend recovery.

Buyer evidence still required

  • Dataset time-travel setting at deletion.
  • Deletion time and required recovery point.
  • Fail-safe and separately retained-copy scope.

Suggested review condition: Distinguish ordinary query visibility, recoverability and final retention before asserting removal.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Dataset and table identity, deletion timestamp, configured window and separate copies.

Optional saved evidence: Save the dated retention evidence used to assess deletion and recovery commitments.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

BigQuery masking: Role changes and cached results

Question: Does replacing raw-data access with Masked Reader immediately hide earlier query results?

BigQuery documents a query-cache caveat when a user queries raw data, then loses Fine-Grained Reader and gains Masked Reader within the cache period. An identical query can still return cached raw data. Masking rules and base table permissions also matter; a role-change screenshot does not establish every result is masked.

Source: BigQuery data masking introduction. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Revoking raw-column access immediately masks every repeated query result.

Buyer evidence still required

  • Prior raw query and role-change timing.
  • Cache usage and query configuration.
  • Policy bindings and effective table permissions.

Suggested review condition: Require a cache-aware check before asserting that a role change removed raw-result access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Data policy, role transition, query identity, timing and cache usage.

Optional saved evidence: Preserve the precise access-transition caveat used in a data-sharing review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

BigQuery maximum bytes: A per-query estimate is not an account budget

Question: Does maximum bytes billed cap every BigQuery charge for an agent workflow?

For on-demand queries, maximum bytes billed checks an estimate before execution and can reject a query above the limit. Clustered-table estimates can exceed the eventual billed amount. This query setting does not establish an account-wide budget or cover every storage and capacity charge.

Source: BigQuery query cost controls. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: One query byte limit bounds the entire workflow or account bill.

Buyer evidence still required

  • Billing model and per-query maximum-bytes setting.
  • Estimated query bytes and rejection/acceptance evidence.
  • Separate storage, capacity and multi-query workflow costs.

Suggested review condition: Keep account-wide cost claims separate from a single-query byte guard.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Billing model, byte estimate, query settings and other cost categories

Optional saved evidence: Save the exact guard and remaining cost categories for an authorised query workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

BigQuery MCP: Read-only queries still need data and spending authority

Question: Does selecting a read-only BigQuery MCP tool eliminate cost and permission concerns?

The documented read-only SQL tool excludes specified mutation and execution forms, while a separate execute_sql tool can modify data. IAM still controls calls, and queries remain subject to time and result limits. Read-only execution can consume billable query resources; a tool list or truncated result does not establish authorised access or complete coverage.

Source: BigQuery MCP read-only and SQL capabilities. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Google hosted BigQuery MCP tools

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Google publishes the hosted BigQuery MCP service.

Documented by publisher. BigQuery MCP read-only and SQL capabilities; BigQuery query cost controls

Purpose

Discover datasets and run supported SQL operations.

Documented by publisher. BigQuery MCP read-only and SQL capabilities; BigQuery query cost controls

Read capability

Permitted metadata and query result rows.

Documented by publisher. BigQuery MCP read-only and SQL capabilities; BigQuery query cost controls

Write capability

execute_sql is the documented mutating tool; the read-only variant has explicit exclusions.

Documented by publisher. BigQuery MCP read-only and SQL capabilities; BigQuery query cost controls

Authentication

OAuth-backed IAM access is required for tool calls; tool discovery alone is not authorisation.

Documented by publisher. BigQuery MCP read-only and SQL capabilities; BigQuery query cost controls

Permission surface

IAM permissions and tool-specific restrictions determine executable operations.

Documented by publisher. BigQuery MCP read-only and SQL capabilities; BigQuery query cost controls

Data leaving the environment

Query results leave BigQuery for the agent client; the buyer must approve that disclosure.

Review inference. BigQuery MCP read-only and SQL capabilities; BigQuery query cost controls

Failure modes to consider

Limits, unsupported external sources and query cost can affect completion or scope.

Review inference. BigQuery MCP read-only and SQL capabilities; BigQuery query cost controls

Unknowns and applicability

Caller grants, billing mode, dataset sensitivity and query limits are unverified.

Not established

Suggested refusal or clarification condition

Require data and spending authority; reject mutations outside scope and do not infer completeness from a limited result.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. IAM grants, tool restrictions, supported sources and billing controls.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the separate data-access, mutation and query-cost boundaries for an agent workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

BigQuery: Script data access is recorded on child jobs

Question: Can an agent reconstruct a BigQuery script data footprint from the parent job events alone?

For multi-statement queries, the parent job generates job events while child jobs generate table read and change events. The audit entries use parentJobName to relate child jobs to the parent. Reviewing only the parent can omit the actual table-access evidence.

Source: BigQuery audit logs overview  |  Google Cloud Documentation. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an agent reconstruct a BigQuery script data footprint from the parent job events alone?

Buyer evidence still required

  • Parent job identity.
  • All child jobs and parentJobName links.
  • TableDataRead and TableDataChange events.

Suggested review condition: Do not close data-access reconstruction from parent job completion without child-job reconciliation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Parent job identity. All child jobs and parentJobName links. TableDataRead and TableDataChange events.

Optional saved evidence: Link a declared script action to the jobs that accessed data.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete source logging, row-level data disclosure reconstruction or actual job verification
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Bitwarden MCP: Vault reads, organisation administration and file access

Question: Does protecting the master-password prompt prevent an agent from reading vault items?

The documented unlock dialog keeps the master password outside MCP, but retrieval tools can still return vault items after unlock. Organisation API credentials enable a separate administrative surface. File-based tools require an allowed-directory setting. Review these distinct authorities rather than treating secure unlock as a complete disclosure boundary.

Source: Bitwarden MCP vault access. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official local MCP with vault CLI and organisation API capabilities

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Bitwarden publishes the MCP server.

Documented by publisher. Bitwarden MCP vault access

Purpose

Vault operations and organisation administration.

Documented by publisher. Bitwarden MCP vault access

Read capability

Vault items and permitted organisation records.

Documented by publisher. Bitwarden MCP vault access

Write capability

Item, sharing, member, policy and other supported changes.

Documented by publisher. Bitwarden MCP vault access

Authentication

Vault session and organisation API credentials serve different operations.

Documented by publisher. Bitwarden MCP vault access

Permission surface

File tools are rejected without an allowed-directory configuration.

Documented by publisher. Bitwarden MCP vault access

Data leaving the environment

Retrieved vault contents can reach the model despite protected password entry.

Review inference. Bitwarden MCP vault access

Failure modes to consider

Secure unlock can be confused with preventing item disclosure.

Review inference. Bitwarden MCP vault access

Unknowns and applicability

Buyer vault scope, organisation rights and file boundaries are unknown.

Not established

Suggested refusal or clarification condition

Confirm permitted item disclosure and administration separately.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Unlock flow, file allowlist and organisation API tools.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the separate decisions for unlocking, reading items, changing organisation resources and accessing files.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Blob copy: Cancellation leaves a changed destination

Question: Does aborting an Azure Blob copy restore the destination to its pre-copy contents and metadata?

Abort Copy Blob cancels a pending copy but leaves a zero-length destination with the new copied or explicitly supplied metadata. The operation does not restore the old destination. Microsoft recommends taking a destination snapshot before copying if the original metadata must be retained. Only a pending copy can be aborted using its matching copy ID.

Source: Azure Blob Storage: Abort Copy Blob. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does aborting an Azure Blob copy restore the destination to its pre-copy contents and metadata?

Buyer evidence still required

  • Destination identity, copy ID and pre-copy snapshot or other retained state.
  • Abort response and resulting copy status, length and metadata.
  • Approved recovery steps with observations of the resulting destination.

Suggested review condition: Decline restored-destination claims from an aborted status without comparing retained prior state and current contents.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Destination identity, copy ID and pre-copy snapshot or other retained state. Abort response and resulting copy status, length and metadata. Approved recovery steps with observations of the resulting destination.

Optional saved evidence: An agent-assisted copy cancellation can leave a changed resource that still needs a separately approved recovery decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic restoration, recovery without prior evidence or authority to overwrite the destination
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Box MCP: Content operations and sharing controls

Question: Does connecting Box MCP give my agent only document-search access?

The documented Box MCP tool set includes content reads and writes. Some sharing and move operations are disabled by default until an administrator enables them. Review enabled tools, OAuth scopes and existing user permissions together before calling the connection read-only.

Source: Box hosted MCP scopes and user permissions. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Box hosted remote server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Box operates the hosted MCP endpoint.

Documented by publisher. Box hosted MCP scopes and user permissions; Box MCP read, write and default-off tools

Purpose

Expose document, folder, collaboration and Box AI operations.

Documented by publisher. Box hosted MCP scopes and user permissions; Box MCP read, write and default-off tools

Read capability

Reads file content, folder information and search results.

Documented by publisher. Box hosted MCP scopes and user permissions; Box MCP read, write and default-off tools

Write capability

Documented tools include uploads, copies and comments; sharing and moves have separate enablement.

Documented by publisher. Box hosted MCP scopes and user permissions; Box MCP read, write and default-off tools

Authentication

OAuth uses the configured integration credentials and approved redirect URI.

Documented by publisher. Box hosted MCP scopes and user permissions; Box MCP read, write and default-off tools

Permission surface

Scopes set action ceilings while existing user content permissions still apply.

Documented by publisher. Box hosted MCP scopes and user permissions; Box MCP read, write and default-off tools

Data leaving the environment

File content returned to an assistant crosses into that client; review export and AI handling.

Review inference. Box hosted MCP scopes and user permissions; Box MCP read, write and default-off tools

Failure modes to consider

Default-off tools can later be enabled, changing the connection beyond an earlier review.

Review inference. Box hosted MCP scopes and user permissions; Box MCP read, write and default-off tools

Unknowns and applicability

Buyer tool toggles, folder permissions and connected-client retention are unknown.

Not established

Suggested refusal or clarification condition

Require explicit approval for sharing or moving content and evidence of the currently enabled tools.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck after administrators change tool availability or sharing permissions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the documented capability and enablement checklist behind a document-access decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Box retention: Folder removal and retained versions

Question: Does removing a file from a Box folder prove permanent deletion under retention?

No. Box says retained files can be removed from folders but remain in trash until retention expires. Policy, assignment and file-version retention are separate objects; expiry may remove the policy or trigger disposition. Review the actual assignments and outcome rather than treating folder absence as erasure.

Source: Box retention policy scope and disposition. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A file removed from its folder has been permanently erased.

Buyer evidence still required

  • Applicable retention policies and assignments
  • File-version retention and trash state
  • Configured disposition and evidence of its completed outcome

Suggested review condition: Do not report erasure from folder absence alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck assignments, extensions and disposition settings.

Optional saved evidence: Save the retention and disposition distinction for supplier evidence review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Box: Custodian hold scope depends on preservation type

Question: Does placing a Box custodian on legal hold preserve every file they could encounter?

Box distinguishes ownership, access and interaction preservation. Ownership alone excludes a file uploaded into another owner folder; interaction and access holds have different scope. Date ranges further restrict eligible versions or interactions. A custodian name alone does not establish universal content preservation.

Source: Box legal hold policies. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does placing a Box custodian on legal hold preserve every file they could encounter?

Buyer evidence still required

  • The hold preservation types and date range.
  • File owners, access and relevant interactions.
  • The file versions actually preserved.

Suggested review condition: Do not assert universal preservation without resolving hold type, ownership, timing and version coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The hold preservation types and date range. File owners, access and relevant interactions. The file versions actually preserved.

Optional saved evidence: An evidence owner must map AI-linked repository files to the actual hold scope before relying on preservation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Legal-hold advice or independent validation that specific files are preserved
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Brave Search MCP: API plan and result-type limitations

Question: Can I assume a Brave Search MCP response is a complete local-business or factual answer?

Brave documents separate search and summary tools, with plan-dependent local capabilities and a web-search fallback. Record the result type and account entitlement before relying on a local query. A generated summary or returned search page is supporting material, not independent verification of the underlying claim.

Source: Brave Search MCP official tool and plan boundaries. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official API-backed local server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Brave publishes the server and operates the Search API.

Documented by publisher. Brave Search MCP official tool and plan boundaries

Purpose

Expose web, local, news, image, video and summary capabilities.

Documented by publisher. Brave Search MCP official tool and plan boundaries

Read capability

Search responses and generated summaries from the API.

Documented by publisher. Brave Search MCP official tool and plan boundaries

Write capability

The documented tool set retrieves information; no buyer application mutation is established.

Review inference. Brave Search MCP official tool and plan boundaries

Authentication

Brave Search API key configured for the server.

Documented by publisher. Brave Search MCP official tool and plan boundaries

Permission surface

Some local and summary capabilities depend on API entitlement and tool inputs.

Documented by publisher. Brave Search MCP official tool and plan boundaries

Data leaving the environment

Search terms and location context may leave the client for Brave processing.

Review inference. Brave Search MCP official tool and plan boundaries

Failure modes to consider

A fallback result or generated summary can be mistaken for verified local evidence.

Review inference. Brave Search MCP official tool and plan boundaries

Unknowns and applicability

Buyer plan, query coverage and factual accuracy of returned material are unverified.

Not established

Suggested refusal or clarification condition

Qualify the result type and verify cited evidence before consequential reliance.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck plan entitlements, fallback behavior and summary prerequisites.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the result-type and entitlement qualifications used in a search evidence review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Browserbase MCP: Cloud sessions, cookies and page actions

Question: Can Browserbase MCP use a logged-in browser session to make changes on a website?

Browserbase documents cloud sessions that can retain authentication state and perform navigation, clicks, typing and form actions. Treat the session identity and target website as part of the permission review. Read access to a page does not establish authority to submit a form or make a purchase.

Source: Browserbase MCP cloud sessions and browser actions. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official hosted service and local MCP client setup

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Browserbase operates the cloud browser infrastructure and publishes the MCP integration.

Documented by publisher. Browserbase MCP cloud sessions and browser actions; Browserbase MCP credentials and deployment setup

Purpose

Let agents inspect and operate web pages through browser sessions.

Documented by publisher. Browserbase MCP cloud sessions and browser actions; Browserbase MCP credentials and deployment setup

Read capability

Page contents and session state available to the selected browser.

Documented by publisher. Browserbase MCP cloud sessions and browser actions; Browserbase MCP credentials and deployment setup

Write capability

Clicks, typing and form submission can change the target service.

Documented by publisher. Browserbase MCP cloud sessions and browser actions; Browserbase MCP credentials and deployment setup

Authentication

Browserbase API credentials; additional model credentials depend on configuration.

Documented by publisher. Browserbase MCP cloud sessions and browser actions; Browserbase MCP credentials and deployment setup

Permission surface

Session identity and selected tools determine the practical action surface.

Documented by publisher. Browserbase MCP cloud sessions and browser actions; Browserbase MCP credentials and deployment setup

Data leaving the environment

Page data, inputs and authenticated state are handled beyond the user device.

Review inference. Browserbase MCP cloud sessions and browser actions; Browserbase MCP credentials and deployment setup

Failure modes to consider

Reusing cookies or submitting an unintended form can cross the approved task boundary.

Review inference. Browserbase MCP cloud sessions and browser actions; Browserbase MCP credentials and deployment setup

Unknowns and applicability

Session contents, target permissions, retention and buyer model configuration are unverified.

Not established

Suggested refusal or clarification condition

Confirm the intended action and affected account before submitting or changing state.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck session persistence, credential recipients, model choice and target permissions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the session-identity and action boundary reviewed before browser automation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Build artifacts: Names, replacement and object identity

Question: Does reusing an artifact name mean a later download contains the same approved build?

The upload-artifact documentation describes immutable artifacts and an overwrite option that deletes and replaces the named artifact with a new ID. A name alone is therefore not a durable identity. Bind acceptance to the artifact ID, digest and producing run, and distinguish retention availability from content identity.

Source: GitHub Actions: Upload artifact identity and replacement. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An unchanged artifact name proves unchanged build content.

Buyer evidence still required

  • Artifact ID and digest at approval.
  • Producing run and source revision.
  • Replacement history, retention and retrieved digest.

Suggested review condition: Do not accept name-only matching as proof that the downloaded artifact was approved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Action version, artifact ID, digest, producing run, revision and retention policy.

Optional saved evidence: Preserve the artifact identity needed to compare approval with later retrieval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Build provenance: Detail level and argument disclosure

Question: Does publishing a Docker provenance attestation keep build arguments private?

The min mode omits build-argument values, while max mode contains additional build detail including argument values and the Dockerfile. Secrets should use the documented secret mechanism rather than build arguments. Review the actual attestation and intended audience; provenance presence alone does not establish confidentiality or an approved build.

Source: Docker: Provenance attestations. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Provenance metadata never exposes build inputs.

Buyer evidence still required

  • Buildx mode and generated attestation.
  • Argument usage and secret-handling configuration.
  • Publication destination, audience and subject digest.

Suggested review condition: Review disclosure and subject identity before publishing or accepting provenance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Buildx version, mode, argument usage, secret handling, output payload and audience.

Optional saved evidence: Save the disclosure and artifact-binding basis for accepting build provenance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Buildkite hooks: Repository control can affect enforcement

Question: Does an agent-wide Buildkite hook alone enforce the same security policy for every repository?

The security guide warns that repository-local hooks can evade policies enforced by agent hooks. Disabling local hooks also disables plugins, and a checkout containing a local hook then fails. Policy review must include repository influence, job environment and the trade-off of disabled extensions.

Source: Buildkite agent security. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An agent hook alone proves untrusted jobs cannot alter enforcement.

Buyer evidence still required

  • Agent and local-hook settings.
  • Permitted plugins and environment overrides.
  • Repository trust and containment evidence.

Suggested review condition: Require repository-influence evidence before accepting a hook as an enforced boundary.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Hook settings, plugins, environment overrides and repository trust

Optional saved evidence: Preserve the repository and extension conditions behind a CI policy claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Buildkite MCP: Version control and incomplete failure evidence

Question: Does a Buildkite MCP failure summary mean the job is finished and evidence is complete?

No. The documentation distinguishes promised failure from a final job result and warns that investigation summaries can be partial. Remote endpoints update automatically; version pinning requires the local server. Confirm final status, missing evidence and write restrictions before relying on a CI review.

Source: Buildkite MCP hosting and credentials. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Remote and local Buildkite MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Buildkite hosts remote MCP and publishes a local server.

Documented by publisher. Buildkite MCP hosting and credentials; Buildkite MCP toolset restrictions

Purpose

Investigate and manage pipeline and test information.

Documented by publisher. Buildkite MCP hosting and credentials; Buildkite MCP toolset restrictions

Read capability

Builds, job logs, annotations and available test results.

Documented by publisher. Buildkite MCP hosting and credentials; Buildkite MCP toolset restrictions

Write capability

Permitted actions can retry jobs or start builds.

Documented by publisher. Buildkite MCP hosting and credentials; Buildkite MCP toolset restrictions

Authentication

Remote OAuth or token pass-through; local API token.

Documented by publisher. Buildkite MCP hosting and credentials; Buildkite MCP toolset restrictions

Permission surface

Toolsets and read-only controls complement underlying access.

Documented by publisher. Buildkite MCP hosting and credentials; Buildkite MCP toolset restrictions

Data leaving the environment

Logs and test details can be returned to the client.

Review inference. Buildkite MCP hosting and credentials; Buildkite MCP toolset restrictions

Failure modes to consider

A promised failure or partial summary can be mistaken for final evidence.

Review inference. Buildkite MCP hosting and credentials; Buildkite MCP toolset restrictions

Unknowns and applicability

Installed version, actual access and evidence completeness are unverified.

Not established

Suggested refusal or clarification condition

Do not report a final outcome until final status and missing evidence are checked.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Remote tool changes, local pinned version and investigation result coverage.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the reviewed distinction between an early failure signal and a completed, sufficiently evidenced result.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

C1 Pump: Diagnostic scope boundary

Question: Does C1 Pump locked outer evaluation establish broad pump diagnostics?

The C1 Pump source supports pump-specific evidence routing. It explicitly excludes broad pump diagnostics.

Derived from BDAS C1 Pump — Locked Outer Evaluation. No new experiment or validation is claimed.

Claim boundaries
  • broad pump diagnostics
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

C3: Promising research versus promotion

Question: Does promising C3 development establish qualification promotion?

C3 is preserved as promising development evidence, not a promoted capability. Its source excludes qualification promotion.

Derived from BDAS C3 Info-Geometry — Promising Development Record. No new experiment or validation is claimed.

Claim boundaries
  • qualification promotion
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

C4: Performance improvement boundary

Question: Does the C4 development record establish performance improvement?

The public C4 source records a not-promising development outcome. It excludes performance improvement.

Derived from BDAS C4 Machine-Local Calibration — Not Promising. No new experiment or validation is claimed.

Claim boundaries
  • performance improvement
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CAEP revocation: Match the event's session scope

Question: Does a session-revocation event apply to every session belonging to a user?

OpenID CAEP 1.0 identifies revoked sessions through the event's subject. That subject can specify a session or properties used to locate applicable sessions. For a complex subject, matching uses the claims together. A user, device and tenant combination must therefore not be reduced to a user-only match. This defines the event's scope; it does not prove that a receiver found the right local sessions or enforced revocation.

Source: OpenID Continuous Access Evaluation Profile 1.0, section 3.1. Documentation checked 2026-10-11; no deployment validation is claimed.

Claim boundaries
  • all user sessions revoked regardless of subject scope
  • correct local identity mapping from receipt alone
  • receiver enforcement proven by an event definition

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Can a Claude SDK hook allow override a matching deny rule

Question: Can a Claude SDK hook allow override a matching deny rule?

The captured SDK documentation evaluates deny rules after hooks. A matching deny prevents the call and skips canUseTool, even after hook allow or in bypassPermissions mode.

Source: Anthropic primary documentation: claude permissions valid. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a Claude SDK hook allow override a matching deny rule?

Buyer evidence still required

  • runtime version
  • hook
  • deny rules
  • mode
  • tool result

Review inference: Can a Claude SDK hook allow override a matching deny rule? Do not treat hook allow as evidence of authorization or execution. Local SDK permission precedence differs from API toolset enablement. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat hook allow as evidence of authorization or execution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. **2. Deny rules**

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat hook allow as evidence of authorization or execution.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a Claude SDK subagent independently weaken its parent permission mode

Question: Can a Claude SDK subagent independently weaken its parent permission mode?

In the captured documentation, subagents inherit parent plan, acceptEdits, auto or bypassPermissions modes. Under default or dontAsk parents, the configured subagent mode applies, except that Claude Code v2.1.267 and later do not apply a subagent bypassPermissions value; auto applies only where available to that subagent. Inherited bypassPermissions can itself confer broad autonomous access. Check the installed runtime and effective mode.

Source: Anthropic primary documentation: claude permissions valid. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a Claude SDK subagent independently weaken its parent permission mode?

Buyer evidence still required

  • parent mode
  • subagent config
  • runtime version
  • effective behavior

Review inference: Can a Claude SDK subagent independently weaken its parent permission mode? Check effective inherited mode and runtime version, not only the subagent field. Delegated subagent mode inheritance differs from API per-tool enablement. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Check effective inherited mode and runtime version, not only the subagent field.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. The subagent inherits

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Check effective inherited mode and runtime version, not only the subagent field.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a custom Langfuse model definition override a maintained default price

Question: Can a custom Langfuse model definition override a maintained default price?

Langfuse matches model names using regular expressions and gives user-defined models priority over maintained definitions. A familiar model label does not establish which pricing definition supplied the estimate.

Source: Token & Cost Tracking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a custom Langfuse model definition override a maintained default price?

Buyer evidence still required

  • generation model value
  • regex patterns
  • custom definitions
  • price units

Review inference: Can a custom Langfuse model definition override a maintained default price? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Local pricing-definition priority differs from selecting an upstream gateway model. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Inspect the matching custom definition before relying on a maintained default price assumption.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Adding custom model definitions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inspect the matching custom definition before relying on a maintained default price assumption.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a Drive client advance its durable change checkpoint while nextPageToken remains

Question: Can a Drive client advance its durable change checkpoint while nextPageToken remains?

A populated nextPageToken means the change list can be incomplete. Google documents following continuation pages and retaining newStartPageToken for later polling after reaching the current end.

Source: Method: changes.list  |  Google Drive  |  Google for Developers. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Drive client advance its durable change checkpoint while nextPageToken remains?

Buyer evidence still required

  • previous token
  • page sequence
  • nextPageToken
  • newStartPageToken
  • applied changes

Review inference: Can a Drive client advance its durable change checkpoint while nextPageToken remains? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Checkpoint advancement differs from interpreting individual removal states. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not acknowledge a complete sync interval before all returned continuation pages are reconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Response body

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not acknowledge a complete sync interval before all returned continuation pages are reconciled.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a failed input guardrail prove no OpenAI Agents SDK tool already ran

Question: Can a failed input guardrail prove no OpenAI Agents SDK tool already ran?

Input guardrails run in parallel with the agent by default. The documentation says a tripwire can fire after token use or tool execution. Blocking mode runs the guardrail first and prevents agent execution if it trips. A failed parallel check is not evidence that earlier effects were avoided.

Source: OpenAI primary documentation: openai guardrails. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a failed input guardrail prove no OpenAI Agents SDK tool already ran?

Buyer evidence still required

  • SDK version
  • run_in_parallel setting
  • tripwire
  • tool events
  • external outcomes

Review inference: Can a failed input guardrail prove no OpenAI Agents SDK tool already ran? Require the execution mode and actual action record before claiming that a rejected input caused no effects. Adds the documented timing race to the existing record about where guardrails are attached. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the execution mode and actual action record before claiming that a rejected input caused no effects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Parallel execution (default

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the execution mode and actual action record before claiming that a rejected input caused no effects.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a filtered Graph message delta request establish complete coverage of a large folder

Question: Can a filtered Graph message delta request establish complete coverage of a large folder?

The documented receivedDateTime filters on message delta return at most 5,000 messages. A time filter changes the coverage boundary and cannot be assumed to enumerate every matching message in a larger folder.

Source: Get incremental changes to messages in a folder - Microsoft Graph | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a filtered Graph message delta request establish complete coverage of a large folder?

Buyer evidence still required

  • folder identity
  • filter expression
  • returned count
  • independent inventory

Review inference: Can a filtered Graph message delta request establish complete coverage of a large folder? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. A resource-specific filtering ceiling differs from generic pagination and resets. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not accept an exhaustive export claim without accounting for the filter ceiling and source inventory.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Use query parameters in a delta query for messages

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not accept an exhaustive export claim without accounting for the filter ceiling and source inventory.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a Graph delta deleted-folder marker immediately remove the local folder

Question: Can a Graph delta deleted-folder marker immediately remove the local folder?

Microsoft requires a local folder to be empty after all changes are synchronised before deleting it locally. A folder marker alone is not enough to decide what remains below it.

Source: driveItem: delta - Microsoft Graph v1.0 | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Graph delta deleted-folder marker immediately remove the local folder?

Buyer evidence still required

  • drive and folder identifiers
  • complete change pages
  • child-state reconciliation

Review inference: Can a Graph delta deleted-folder marker immediately remove the local folder? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Local hierarchy deletion order is distinct from generic replay and reset handling. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reconcile child changes before deleting the local container; the marker does not prove physical erasure.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Permissions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile child changes before deleting the local container; the marker does not prove physical erasure.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a masking error cause Langfuse telemetry to disappear

Question: Can a masking error cause Langfuse telemetry to disappear?

An exception or invalid overall masking result drops the export batch. An invalid span patch drops that span; invalid returned attribute values remove the affected attribute. These failure scopes differ.

Source: Masking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a masking error cause Langfuse telemetry to disappear?

Buyer evidence still required

  • hook errors
  • batch identities
  • patch validation
  • exported spans and fields

Review inference: Can a masking error cause Langfuse telemetry to disappear? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Mask-validation loss differs from queue capacity and retry expiry. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Retain masking-error evidence before interpreting missing spans or fields as no activity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. MaskOtelSpansResult

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Retain masking-error evidence before interpreting missing spans or fields as no activity.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a multitenant Entra blueprint make one child identity valid across tenants

Question: Can a multitenant Entra blueprint make one child identity valid across tenants?

No. Agent identities remain single-tenant. A multitenant blueprint can be installed elsewhere and create separate tenant-local identities; it does not make an existing child identity cross-tenant.

Source: Microsoft primary documentation: entra agent identities. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a multitenant Entra blueprint make one child identity valid across tenants?

Buyer evidence still required

  • source/destination tenants
  • local agent IDs
  • blueprint installations
  • resource tenant

Review inference: Can a multitenant Entra blueprint make one child identity valid across tenants? Require the destination tenant identity and authorization evidence. Separates distributed blueprints from tenant-local agents rather than generic exchange policy. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the destination tenant identity and authorization evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. single-tenant

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the destination tenant identity and authorization evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a replacement RabbitMQ channel acknowledge an earlier delivery tag

Question: Can a replacement RabbitMQ channel acknowledge an earlier delivery tag?

Delivery tags are scoped to their channel. Acknowledging on another channel causes an unknown-delivery-tag exception and closes that channel.

Source: Consumer Acknowledgements and Publisher Confirms | RabbitMQ. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a replacement RabbitMQ channel acknowledge an earlier delivery tag?

Buyer evidence still required

  • connection and channel identity
  • delivery tag
  • acknowledgement response

Review inference: Reconcile acknowledgements after reconnecting a worker. Require the missing evidence before accepting, retrying or closing the operation. Consumer tag identity across channels differs from publish confirmation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not equate a reused numeric tag with the original delivery without channel identity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Delivery Identifiers: Delivery Tags

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not equate a reused numeric tag with the original delivery without channel identity.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can a responsive Graph subscription still have an unrecoverable webhook gap

Question: Can a responsive Graph subscription still have an unrecoverable webhook gap?

Graph can delay slow endpoints and drop notifications for endpoints exceeding its documented timeout thresholds. Dropped notifications cannot be recovered through notification delivery, so restoring responsiveness does not prove gap closure.

Source: Receive change notifications through webhooks - Microsoft Graph | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a responsive Graph subscription still have an unrecoverable webhook gap?

Buyer evidence still required

  • response latency history
  • slow or drop interval
  • source change reconciliation

Review inference: Can a responsive Graph subscription still have an unrecoverable webhook gap? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Endpoint throttling and dropped delivery differ from subscription reauthorisation lifecycle events. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reconcile affected source changes independently before treating the capture interval as complete.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Throttling

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile affected source changes independently before treating the capture interval as complete.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can ADK Resume repeat a tool whose remote side effect already occurred

Question: Can ADK Resume repeat a tool whose remote side effect already occurred?

The resume guide reinstates successfully returned tool results and reruns an interrupted tool request. It explicitly describes at-least-once tool execution and possible repeat execution on resume. Side-effecting tools such as purchases need their own duplicate-prevention checks.

Source: Google primary documentation: adk resume. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can ADK Resume repeat a tool whose remote side effect already occurred?

Buyer evidence still required

  • invocation ID
  • saved tool events
  • interrupted request
  • external operation ID
  • retry guard

Review inference: Can ADK Resume repeat a tool whose remote side effect already occurred? Do not resume an uncertain consequential tool without an outcome or deduplication check. ADK's concrete logged-result resume cut differs from Temporal activity timeout processing. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not resume an uncertain consequential tool without an outcome or deduplication check.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Event logging includes results; Tool execution behavior

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not resume an uncertain consequential tool without an outcome or deduplication check.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can administrator consent override Agent ID high-privilege restrictions

Question: Can administrator consent override Agent ID high-privilege restrictions?

The documented agent model blocks specified high-risk Graph permissions and privileged directory roles. Agents also cannot join role-assignable groups. Administrator consent is not a general override.

Source: Microsoft primary documentation: entra authorization agent id. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can administrator consent override Agent ID high-privilege restrictions?

Buyer evidence still required

  • requested permission/role
  • identity type
  • supported list
  • consent result

Review inference: Can administrator consent override Agent ID high-privilege restrictions? Check the current permitted roles and permissions; refuse reliance on blocked grants. Agent-specific prohibited grants differ from administrator-role consent limits. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Check the current permitted roles and permissions; refuse reliance on blocked grants.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. explicitly blocked

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Check the current permitted roles and permissions; refuse reliance on blocked grants.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can AgentCore use one OBO wire format for every identity provider

Question: Can AgentCore use one OBO wire format for every identity provider?

No. AgentCore supports RFC8693 token exchange and JWT authorization-grant mode. Provider configuration determines the expected fields; Microsoft's preset adds requested_token_use=on_behalf_of unless overridden.

Source: Amazon Web Services primary documentation: aws on behalf of token exchange. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can AgentCore use one OBO wire format for every identity provider?

Buyer evidence still required

  • provider
  • grant mode
  • parameters
  • exchange response

Review inference: Can AgentCore use one OBO wire format for every identity provider? Require provider-supported grant configuration; OBO labels do not establish interchangeable requests. Wire-protocol compatibility differs from authority selection. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require provider-supported grant configuration; OBO labels do not establish interchangeable requests.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. JWT_AUTHORIZATION_GRANT

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require provider-supported grant configuration; OBO labels do not establish interchangeable requests.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an A2A client choose taskId as the identifier for creating new delegated work

Question: Can an A2A client choose taskId as the identifier for creating new delegated work?

Task IDs are server-generated. A taskId in a message must reference an existing task, and an unknown one requires TaskNotFoundError. Client-generated task IDs for task creation are not supported in the captured specification.

Source: A2A Project primary documentation: a2a spec. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an A2A client choose taskId as the identifier for creating new delegated work?

Buyer evidence still required

  • server response
  • task ID
  • message ID
  • creation request

Review inference: Can an A2A client choose taskId as the identifier for creating new delegated work? Do not use a proposed taskId as a create-or-deduplicate key without a separate supported contract. Task resource creation and message replay identifiers have different roles and failure modes. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not use a proposed taskId as a create-or-deduplicate key without a separate supported contract.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. 3.4.2. Task Identifier Semantics

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not use a proposed taskId as a create-or-deduplicate key without a separate supported contract.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an A2A client resume a completed task by sending it another message

Question: Can an A2A client resume a completed task by sending it another message?

The captured specification rejects messages to completed, failed, canceled or rejected tasks with UnsupportedOperationError. A task identifier does not reopen a terminal lifecycle. A separate follow-up must use a supported new-task or conversation path.

Source: A2A Project primary documentation: a2a spec. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an A2A client resume a completed task by sending it another message?

Buyer evidence still required

  • task ID
  • terminal state
  • intended follow-up
  • server version

Review inference: Can an A2A client resume a completed task by sending it another message? Do not resend work against a terminal task as if its old authority and state were resumable. Terminal-message admission is distinct from judging whether completed output satisfies a buyer. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not resend work against a terminal task as if its old authority and state were resumable.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Messages sent to Tasks that are in a terminal state

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not resend work against a terminal task as if its old authority and state were resumable.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an ADK session rewind safely run while the session or its artifacts are still changing

Question: Can an ADK session rewind safely run while the session or its artifacts are still changing?

State updates, artifact updates and event persistence are not one atomic transaction in the documented rewind. The guide advises avoiding active-session rewinds and concurrent artifact manipulation to prevent inconsistencies.

Source: Google primary documentation: adk rewind. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an ADK session rewind safely run while the session or its artifacts are still changing?

Buyer evidence still required

  • active run state
  • concurrent writes
  • target rewind point
  • resulting state and artifact versions

Review inference: Can an ADK session rewind safely run while the session or its artifacts are still changing? Require a quiescent recovery point and consistency checks before accepting the rewound snapshot. Even within the supported session scope, concurrent non-atomic reconstruction is a separate failure mode. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require a quiescent recovery point and consistency checks before accepting the rewound snapshot.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Atomicity

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require a quiescent recovery point and consistency checks before accepting the rewound snapshot.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an agent classify a disputed purchase as a consumer dispute without a merchant resolution attempt

Question: Can an agent classify a disputed purchase as a consumer dispute without a merchant resolution attempt?

For consumer reasons such as not received, canceled or not as described, Stripe's guide requires the cardholder to attempt resolution with the business and include documentation of that attempt. This is a specific submission evidence condition, not proof of fraud or a guaranteed recovery.

Source: Stripe primary documentation: stripe issuing disputes. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent classify a disputed purchase as a consumer dispute without a merchant resolution attempt?

Buyer evidence still required

  • dispute reason
  • attempted merchant contact
  • correspondence evidence
  • transaction
  • unresolved outcome

Review inference: Can an agent classify a disputed purchase as a consumer dispute without a merchant resolution attempt? Require the applicable reason and documented merchant-resolution attempt before this consumer-dispute path. Reason-specific prerequisite evidence is different from the general post-submission lock. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the applicable reason and documented merchant-resolution attempt before this consumer-dispute path.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Consumer disputes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the applicable reason and documented merchant-resolution attempt before this consumer-dispute path.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an agent dispute a Stripe Issuing authorization before the merchant captures it

Question: Can an agent dispute a Stripe Issuing authorization before the merchant captures it?

Stripe's Issuing guide says an authorization cannot be disputed. A dispute can be filed after authorization completes and the acquiring business captures the transaction; reversal of an authorization is at the acquiring business's discretion. Identify the captured transaction before choosing dispute recovery.

Source: Stripe primary documentation: stripe issuing disputes. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent dispute a Stripe Issuing authorization before the merchant captures it?

Buyer evidence still required

  • authorization
  • capture transaction
  • linked amount
  • dispute eligibility

Review inference: Can an agent dispute a Stripe Issuing authorization before the merchant captures it? Do not represent an authorization-only hold as an eligible captured-transaction dispute. Dispute entry eligibility differs from whether a capture followed an approval. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not represent an authorization-only hold as an eligible captured-transaction dispute.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. You can’t dispute an authorization

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not represent an authorization-only hold as an eligible captured-transaction dispute.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an automated Stripe Issuing dispute submit now and add evidence later

Question: Can an automated Stripe Issuing dispute submit now and add evidence later?

Stripe permits submitting a dispute only once. After submission, the dispute cannot be edited or supplemented with further evidence. Incomplete or invalid submissions can lose, so the review point is before submission rather than after creation.

Source: Stripe primary documentation: stripe issuing disputes. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an automated Stripe Issuing dispute submit now and add evidence later?

Buyer evidence still required

  • transaction
  • dispute reason
  • evidence set
  • reviewed amount
  • submission status

Review inference: Can an automated Stripe Issuing dispute submit now and add evidence later? Require complete reason-specific evidence and operator authorization before the irreversible submission step. Issuing cardholder submission finality differs from merchant-side financial reversal after delivery. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require complete reason-specific evidence and operator authorization before the irreversible submission step.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Submitting valid disputes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require complete reason-specific evidence and operator authorization before the irreversible submission step.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an enterprise ID-JAG directly serve as an MCP bearer access token

Question: Can an enterprise ID-JAG directly serve as an MCP bearer access token?

In the optional Enterprise-Managed Authorization profile dated 2026-07-28, the enterprise IdP evaluates policy and issues an ID-JAG. The client then presents that intermediate grant to the resource authorization server, which validates it and issues the MCP access token. Corporate sign-in or the ID-JAG alone does not establish a usable resource token; profile support and both trust relationships need evidence.

Source: Model Context Protocol primary documentation: ext enterprise managed authorization. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an enterprise ID-JAG directly serve as an MCP bearer access token?

Buyer evidence still required

  • extension revision
  • issuers
  • redacted grant/access-token claims

Review inference: Can an enterprise ID-JAG directly serve as an MCP bearer access token? Require the resource-token exchange and audience validation before protected calls. Introduces the intermediate grant and enterprise two-stage exchange. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the resource-token exchange and audience validation before protected calls.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. ## 5. Access Token Request

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the resource-token exchange and audience validation before protected calls.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an Entra agent user account operate as an ordinary password-based user

Question: Can an Entra agent user account operate as an ordinary password-based user?

The account has restricted credentials tied to its parent agent identity and restricted interactive sign-in. It cannot receive ordinary passwords or passkeys merely because its tokens use a user identity type.

Source: Microsoft primary documentation: entra agent users. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an Entra agent user account operate as an ordinary password-based user?

Buyer evidence still required

  • agent user
  • parent reference
  • sign-in method
  • target API requirement

Review inference: Can an Entra agent user account operate as an ordinary password-based user? Reject designs requiring a normal interactive account; verify the parent flow. A provider-specific nonhuman user account differs from human delegation or app-only consent. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reject designs requiring a normal interactive account; verify the parent flow.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Credential limitations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reject designs requiring a normal interactive account; verify the parent flow.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an Entra child-agent permissions listing establish complete inherited scope

Question: Can an Entra child-agent permissions listing establish complete inherited scope?

No. Microsoft states inherited permissions are not shown on the agent identity in the admin center or Graph. They merge with direct grants at token issuance and are observable in token contents.

Source: Microsoft primary documentation: entra inheritance. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an Entra child-agent permissions listing establish complete inherited scope?

Buyer evidence still required

  • redacted roles/scp summary
  • issuance time
  • direct and inherited grants

Review inference: Can an Entra child-agent permissions listing establish complete inherited scope? Use a safely inspected claim summary plus grant evidence; never publish or request the token itself. A specific inherited-permission visibility gap differs from permission-probe scope. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Use a safely inspected claim summary plus grant evidence; never publish or request the token itself.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. only observable in the token

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Use a safely inspected claim summary plus grant evidence; never publish or request the token itself.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an Entra sponsor restore an agent after disabling it

Question: Can an Entra sponsor restore an agent after disabling it?

Sponsors can disable or soft-delete an agent and change its sponsors, but cannot re-enable or restore it. Recovery needs an owner or administrator. Sponsorship does not confer all owner powers.

Source: Microsoft primary documentation: entra relationships. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an Entra sponsor restore an agent after disabling it?

Buyer evidence still required

  • agent
  • sponsor/owner relationships
  • lifecycle state
  • recovery actor

Review inference: Can an Entra sponsor restore an agent after disabling it? Route recovery to an authorized owner or administrator. Agent sponsor recovery powers differ from PIM activation approval. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Route recovery to an authorized owner or administrator.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Sponsors can't re-enable

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Route recovery to an authorized owner or administrator.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can an MCP task marked completed still contain an unsuccessful tool result

Question: Can an MCP task marked completed still contain an unsuccessful tool result?

In the optional 2026-07-28 Tasks extension, completed includes tool results with isError true. Failed is reserved for execution JSON-RPC errors. A consumer must inspect the embedded original result as well as task status before accepting tool or business success.

Source: Model Context Protocol primary documentation: mcp tasks current. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an MCP task marked completed still contain an unsuccessful tool result?

Buyer evidence still required

  • extension version
  • task state
  • result
  • isError
  • business outcome evidence

Review inference: Can an MCP task marked completed still contain an unsuccessful tool result? Refuse a successful-action conclusion from completed alone when the tool result reports an error. Adds task lifecycle interpretation to the underlying tool/protocol error distinction. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse a successful-action conclusion from completed alone when the tool result reports an error.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. This includes tool calls that returned results with

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a successful-action conclusion from completed alone when the tool result reports an error.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can cached input tokens be counted both within input and in a separate Langfuse usage bucket

Question: Can cached input tokens be counted both within input and in a separate Langfuse usage bucket?

Langfuse treats usage keys as non-overlapping buckets. Overlapping counts can double-count usage and inferred cost; directly ingested cost values are not recalculated by that overlap.

Source: Token & Cost Tracking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can cached input tokens be counted both within input and in a separate Langfuse usage bucket?

Buyer evidence still required

  • provider token fields
  • normalized usage buckets
  • inferred versus ingested cost

Review inference: Can cached input tokens be counted both within input and in a separate Langfuse usage bucket? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Telemetry normalization overlap differs from interpreting provider cache prices. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reconcile bucket definitions before accepting totals or alleging duplicate billing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Usage types are mutually exclusive buckets

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile bucket definitions before accepting totals or alleging duplicate billing.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can changing federation mappings alter access without editing IAM bindings

Question: Can changing federation mappings alter access without editing IAM bindings?

Yes. A mapping edit can change which external identities match existing service-account bindings. Provider update authority therefore affects effective access even with unchanged bindings.

Source: Google primary documentation: gcp federation practices. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can changing federation mappings alter access without editing IAM bindings?

Buyer evidence still required

  • old/new mappings
  • provider update authority
  • bindings
  • change record

Review inference: Can changing federation mappings alter access without editing IAM bindings? Review mapping changes alongside grants. Identity translation can change independently of an IAM policy edit. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Review mapping changes alongside grants.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Don't allow attribute mappings to be modified

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Review mapping changes alongside grants.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can Drive return file details for an item that has left the change corpus

Question: Can Drive return file details for an item that has left the change corpus?

includeCorpusRemovals can include the file resource when it remains accessible despite leaving the change list. There may be no further change entries for that file in the selected corpus.

Source: Method: changes.list  |  Google Drive  |  Google for Developers. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can Drive return file details for an item that has left the change corpus?

Buyer evidence still required

  • includeCorpusRemovals
  • removed flag
  • returned file
  • ongoing monitoring scope

Review inference: Can Drive return file details for an item that has left the change corpus? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Last accessible state with no future corpus updates differs from the deletion-versus-access-loss cause. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not assume continued monitoring from a last accessible file representation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Query parameters

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assume continued monitoring from a last accessible file representation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can mask_otel_spans redact every field of a Langfuse span

Question: Can mask_otel_spans redact every field of a Langfuse span?

The hook can change span attributes but not names, identifiers, parent relationships, resource attributes, events, links or instrumentation scope. Its configured presence is not whole-span sanitization.

Source: Masking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can mask_otel_spans redact every field of a Langfuse span?

Buyer evidence still required

  • attribute patches
  • span names
  • resource attributes
  • events and links
  • export policy

Review inference: Can mask_otel_spans redact every field of a Langfuse span? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Maskable field scope differs from data discarded by size limits. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Keep sensitive information out of excluded fields and inspect their separate handling.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. mask_otel_spans

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep sensitive information out of excluded fields and inspect their separate handling.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can MCP assume authorization metadata exists only at the domain root

Question: Can MCP assume authorization metadata exists only at the domain root?

No. July 2026 defines ordered OAuth and OpenID discovery candidates for issuers with paths. A root-only probe can miss a tenant issuer; returned issuer metadata still needs validation.

Source: Model Context Protocol primary documentation: mcp authorization server discovery. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can MCP assume authorization metadata exists only at the domain root?

Buyer evidence still required

  • full issuer URL
  • attempted metadata URLs/results
  • validated issuer

Review inference: Can MCP assume authorization metadata exists only at the domain root? Preserve the issuer path and follow documented discovery before declaring failure. Authorization metadata path discovery differs from transport version fallback. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Preserve the issuer path and follow documented discovery before declaring failure.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. For issuer URLs with path components

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Preserve the issuer path and follow documented discovery before declaring failure.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can MCP credentials carry over to another advertised authorization server

Question: Can MCP credentials carry over to another advertised authorization server?

Do not assume so. MCP 2026-07-28 requires separate registration state for each authorization server and association of credentials and tokens with the issuing server. An advertised alternative issuer does not establish that it accepts another issuer's credentials.

Source: Model Context Protocol primary documentation: mcp authorization server discovery. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can MCP credentials carry over to another advertised authorization server?

Buyer evidence still required

  • resource metadata
  • selected issuer
  • registration
  • token issuer summary

Review inference: Can MCP credentials carry over to another advertised authorization server? Require issuer-specific registration and authorization evidence before reuse. Registration continuity differs from resource audience. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require issuer-specific registration and authorization evidence before reuse.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. separate registration state

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require issuer-specific registration and authorization evidence before reuse.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can Pub/Sub replay acknowledged messages without retained history

Question: Can Pub/Sub replay acknowledged messages without retained history?

Time-based replay of acknowledged messages requires topic retention or subscription retention of acknowledged messages. A timestamp alone does not create retained history.

Source: Replay and purge messages with seek  |  Pub/Sub  |  Google Cloud Documentation. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can Pub/Sub replay acknowledged messages without retained history?

Buyer evidence still required

  • topic or subscription retention
  • acknowledgement times
  • target time
  • retained coverage

Review inference: Determine whether lost processing can be replayed from a past timestamp. Require the missing evidence before accepting, retrying or closing the operation. Message retention eligibility differs from archived workflow history. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not promise recovery beyond retained data. Verify retention and the eligible interval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. To seek to a time in the past

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not promise recovery beyond retained data. Verify retention and the eligible interval.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can Python multi-project Langfuse routing isolate every third-party span by project

Question: Can Python multi-project Langfuse routing isolate every third-party span by project?

The documented experimental routing uses a Langfuse public-key attribute. Third-party spans lacking it, if accepted by export filters, can be processed by all configured project processors.

Source: Advanced Features - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can Python multi-project Langfuse routing isolate every third-party span by project?

Buyer evidence still required

  • project processors
  • public-key attributes
  • third-party instrumentors
  • export filters

Review inference: Can Python multi-project Langfuse routing isolate every third-party span by project? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Telemetry routing across projects differs from an MCP connector project-access boundary. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Verify instrumentor, filter and routing coverage before claiming tenant isolation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Important Limitation with Third-Party Libraries

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Verify instrumentor, filter and routing coverage before claiming tenant isolation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can RabbitMQ multiple=true acknowledge unfinished earlier deliveries

Question: Can RabbitMQ multiple=true acknowledge unfinished earlier deliveries?

The multiple flag acknowledges every outstanding delivery tag up to and including the specified tag on that channel. It does not select only finished application tasks.

Source: Consumer Acknowledgements and Publisher Confirms | RabbitMQ. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can RabbitMQ multiple=true acknowledge unfinished earlier deliveries?

Buyer evidence still required

  • channel delivery sequence
  • multiple flag
  • per-task completion references

Review inference: Decide whether a later completed task permits acknowledging earlier concurrent work. Require the missing evidence before accepting, retrying or closing the operation. Bulk consumer acknowledgement coverage is distinct from publisher confirms. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat a bulk acknowledgement as proof that every covered task completed. Reconcile each result.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Acknowledging Multiple Deliveries at Once

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat a bulk acknowledgement as proof that every covered task completed. Reconcile each result.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can Service Bus activate a scheduled message while cancellation occurs

Question: Can Service Bus activate a scheduled message while cancellation occurs?

Activation and cancellation are independent operations without mutual locking. Cancellation during activation does not reverse activation, and the message can still become active.

Source: Azure Service Bus message sequencing and timestamps - Azure Service Bus | Microsoft Learn. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can Service Bus activate a scheduled message while cancellation occurs?

Buyer evidence still required

  • scheduled time
  • cancellation response and time
  • activation evidence
  • worker outcome

Review inference: Cancel pending work immediately before its due time. Require the missing evidence before accepting, retrying or closing the operation. This broker scheduling race differs from child-task cancellation in Step Functions. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not promise stopped execution from near-deadline cancellation. Reconcile activation and worker outcomes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Scheduled messages

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not promise stopped execution from near-deadline cancellation. Reconcile activation and worker outcomes.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can shared background work be attributed to the wrong Langfuse project

Question: Can shared background work be attributed to the wrong Langfuse project?

The documented JS/TS request-routing pattern warns that a shared queue can execute under whichever request context is active when it drains. Spans can then be routed to that request project.

Source: Advanced Features - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can shared background work be attributed to the wrong Langfuse project?

Buyer evidence still required

  • queue ownership
  • originating request
  • active async context
  • span destination

Review inference: Can shared background work be attributed to the wrong Langfuse project? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Cross-request project routing differs from interpreting a service label as instance identity. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Bind work to the originating async context before treating project attribution as reliable.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Shared work queues can send spans to the wrong project.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Bind work to the originating async context before treating project attribution as reliable.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can the displayed model label alone establish which LangSmith pricing rule was applied

Question: Can the displayed model label alone establish which LangSmith pricing rule was applied?

LangSmith model pricing uses a model-name match pattern and optional provider match. Reviewing the actual metadata and matching entry is necessary when custom names or gateways change model labels.

Source: Cost tracking. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can the displayed model label alone establish which LangSmith pricing rule was applied?

Buyer evidence still required

  • ls_model_name
  • ls_provider
  • match pattern
  • applicable price entry

Review inference: Can the displayed model label alone establish which LangSmith pricing rule was applied? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Pricing-rule matching differs from identifying a gateway fallback model. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not accept a calculated amount as the applicable contracted price without checking the matching rule.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Create a new or modify an existing model price entry

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not accept a calculated amount as the applicable contracted price without checking the matching rule.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can two providers in one workload pool map different identities to one principal

Question: Can two providers in one workload pool map different identities to one principal?

Yes. Matching google.subject values across providers can collapse identities into one IAM principal and make them indistinguishable in audit logs. Google recommends one provider per pool to avoid this.

Source: Google primary documentation: gcp federation practices. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can two providers in one workload pool map different identities to one principal?

Buyer evidence still required

  • pool/providers
  • issuers
  • subject mappings
  • claim shapes
  • IAM binding

Review inference: Can two providers in one workload pool map different identities to one principal? Require collision-resistant pool/subject mappings before asserting unique attribution. Cross-provider collision differs from accepted attributes for one issuer. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require collision-resistant pool/subject mappings before asserting unique attribution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Use a single provider per workload identity pool

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require collision-resistant pool/subject mappings before asserting unique attribution.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Can user-editable attributes safely anchor workload federation access

Question: Can user-editable attributes safely anchor workload federation access?

Google warns editable attributes can cause access loss or spoofing when mapped to IAM bindings. Use immutable identity attributes rather than values an external user can change.

Source: Google primary documentation: gcp federation practices. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can user-editable attributes safely anchor workload federation access?

Buyer evidence still required

  • mapping
  • upstream mutability
  • IAM bindings
  • lifecycle evidence

Review inference: Can user-editable attributes safely anchor workload federation access? Reassess user-controlled identity mappings; matching text alone is insufficient. Attribute control over time differs from initial acceptance conditions. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reassess user-controlled identity mappings; matching text alone is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Use immutable attributes in attribute mappings

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reassess user-controlled identity mappings; matching text alone is insufficient.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Derived claim boundary

Candidate batch 7026447: Canonical status boundary

Question: Can every staged candidate in batch 7026447 be counted as canonical?

The public batch summary describes staged candidates and explicitly excludes the claim that all candidates are canonical. A staged count is not a count of qualified public records.

Derived from BDAS 7026447 — Candidate Batch Summary. No new experiment or validation is claimed.

Claim boundaries
  • all candidates canonical
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Candidate batch 7026447: Publication boundary

Question: Does the 7026447 staging summary make every candidate public-safe?

The candidate-batch source explicitly excludes the claim that every candidate is public-safe. Staging does not authorise disclosure.

Derived from BDAS 7026447 — Candidate Batch Summary. No new experiment or validation is claimed.

Claim boundaries
  • all candidates public-safe
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Canva MCP: Individual access, editing and exports

Question: Can one Canva MCP authorisation stand in for every user of an AI application?

Canva requires individual user authentication, and operations follow the access that user has to designs and assets. The server supports creation, editing, export and collaboration, with some features depending on plan. An application connection alone does not establish entitlement for another user or permission to export a design.

Source: Canva MCP design, export and collaboration capabilities. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Canva hosted MCP for AI assistants

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Canva provides the remote MCP service.

Documented by publisher. Canva MCP design, export and collaboration capabilities; Canva MCP per-user authorization and access

Purpose

Expose design creation, editing, discovery and export to assistants.

Documented by publisher. Canva MCP design, export and collaboration capabilities; Canva MCP per-user authorization and access

Read capability

Searches designs, pages, folders and accessible brand resources.

Documented by publisher. Canva MCP design, export and collaboration capabilities; Canva MCP per-user authorization and access

Write capability

Creates or edits designs, uploads assets and adds comments.

Documented by publisher. Canva MCP design, export and collaboration capabilities; Canva MCP per-user authorization and access

Authentication

Each user authenticates with OAuth through a recognised client.

Documented by publisher. Canva MCP design, export and collaboration capabilities; Canva MCP per-user authorization and access

Permission surface

Design/asset access and plan entitlement constrain available operations.

Documented by publisher. Canva MCP design, export and collaboration capabilities; Canva MCP per-user authorization and access

Data leaving the environment

Design data and exported files can reach the AI application and its storage.

Review inference. Canva MCP design, export and collaboration capabilities; Canva MCP per-user authorization and access

Failure modes to consider

Confusing client registration with user consent or plan access may break an integration.

Review inference. Canva MCP design, export and collaboration capabilities; Canva MCP per-user authorization and access

Unknowns and applicability

The actual user grants, content rights and export destination are unknown.

Not established

Suggested refusal or clarification condition

Require the intended user and approved export destination; do not reuse one user consent as organisation-wide authority.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck client registration, user access and plan-specific capabilities.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the user, plan and export questions behind an application-access decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cedar: Authorization policy scope

Question: Does using Cedar establish that an agent's actions are authorised?

Cedar provides a language and engine for authorization decisions. Correct policy, request data and application enforcement still need deployment evidence.

Source: Cedar Policy Language Reference. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • complete business policy
  • correct deployment enforcement
  • permission to spend

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cedar: Denial and evaluation errors

Question: Does Cedar's default denial mean every policy error denies the whole request?

Cedar denies when no permit applies, and a satisfied forbid overrides a permit. Policies that error are skipped; error handling must not be described as unconditional denial.

Source: How Cedar authorization works. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • every evaluation error forces denial
  • all guardrails evaluated successfully
  • complete enforcement from a default rule

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cedar: Level validation and entity slicing

Question: When can Cedar entity slicing preserve an authorisation result?

Cedar documents additional level validation and matching entity slicing to bound the entity data required for authorisation while preserving the result under the stated conditions. This is conditional on the validation and slicing rules; it does not justify arbitrary data pruning or prove a deployed policy is correct.

Source: Cedar level validation. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • arbitrary entity pruning
  • correctness of deployed policies
  • unconditional result equivalence

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cedar: Request context

Question: What context does a Cedar authorization request need?

Cedar requests identify the principal, action, resource and context. A correctly shaped request does not prove that these values accurately represent the intended operation.

Source: How Cedar authorization works. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • authentic request data
  • complete entity context
  • permission inferred from request shape

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cedar: Schema validation limits

Question: Does Cedar policy validation prove that the policy expresses the intended permissions?

Cedar can check policies against an application schema for consistency. Schema changes can invalidate earlier checks; validation alone does not establish the intended permission model.

Source: Cedar policy validation. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • business-policy correctness
  • unchanged validity after schema edits
  • deployment enforcement

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Certificate evidence has a handoff and renewal boundary

Question: Can award-time certification alone support a later transfer of data to a supplier?

PPN 014 requires certificate or equivalent evidence at the point data is passed to the supplier. Where Cyber Essentials certification is required, annual renewal applies for the contract duration. Review implication: An award-time certificate alone does not establish the state at a later handoff. Equivalent-control evidence has its own review basis; it is not necessarily a certificate with an annual expiry.

Source: Cabinet Office PPN 014. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can award-time certification alone support a later transfer of data to a supplier?

Buyer evidence still required

  • Contract requirement and scope
  • Proposed data-handoff date
  • Current certificate scope/validity or equivalent-controls evidence

Review inference: An award-time certificate alone does not establish the state at a later handoff. Equivalent-control evidence has its own review basis; it is not necessarily a certificate with an annual expiry.

Suggested review condition: No VAREXIS certificate validation, automatic expiry determination or supplier approval is performed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK central government departments, executive agencies and non-departmental public bodies and NHS bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • No VAREXIS certificate validation, automatic expiry determination or supplier approval is performed.
  • Current applicable evidence at handoff can satisfy the narrower timing question; absence of a new certificate is not proof equivalent controls ceased.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External advisory review

changed-files: Preserve incident history and conflicting fix records

Question: Does upgrading changed-files establish that earlier workflow secrets were not exposed?

The changed-files maintainer advisory describes tags redirected to malicious code during 14-15 March 2025 and secrets exposed through workflow logs. Upgrading does not establish that earlier runs were unaffected. Review execution dates, resolved code and potentially exposed credentials. The maintainer page lists 46.0.0 as patched; the frozen GHSA-mrrh-fwg8-r2c3 projection records 46.0.1 as a fix event. This review preserves that disagreement rather than choosing a universal safe version. Neither source verifies a buyer's runs or credential recovery.

Source: changed-files maintainer advisory: CVE-2025-30066. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • one verified safe version resolved from conflicting sources
  • past credential exposure disproved by an upgrade
  • buyer workflow inspection or recovery verification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Checkmarx MCP: Licensed tools and scan authority

Question: Does Checkmarx MCP access authorize every scanner and remediation operation?

The connector follows the authenticated tenant identity and licensed capabilities. It can trigger scans and retrieve findings; absence of project-deletion tools does not make it read-only. Local-directory scanning also needs the Checkmarx CLI and matching credentials. Supported authentication methods differ between clients.

Source: Checkmarx One MCP Server. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer deployment unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Checkmarx operates the Checkmarx One service.

Documented by publisher. Checkmarx One MCP Server

Purpose

Access licensed security scanning and remediation workflows.

Documented by publisher. Checkmarx One MCP Server

Read capability

Permitted projects, scan state and findings.

Documented by publisher. Checkmarx One MCP Server

Write capability

Starting scans and other licensed actions can change service state.

Documented by publisher. Checkmarx One MCP Server

Authentication

OAuth or API-key access token; client support differs.

Documented by publisher. Checkmarx One MCP Server

Permission surface

Tenant IAM permissions and licence packages jointly constrain tools.

Documented by publisher. Checkmarx One MCP Server

Data leaving the environment

Repository context and returned findings can enter the connected assistant workflow.

Review inference. Checkmarx One MCP Server

Failure modes to consider

Credential mismatch can break local scans; unavailable tools can reflect licence or permission limits.

Review inference. Checkmarx One MCP Server

Unknowns and applicability

Buyer edition, client, tenant permissions and actual data transfer were not inspected.

Not established

Suggested refusal or clarification condition

Confirm tenant, licensed operation and authority before starting a scan.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Client support, tenant registration limits, scanner licensing and tool expansion.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the licensed capability and authority boundary behind a scanner integration decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Checkpointer thread state versus independent cross-thread store

Question: Does removing LangGraph thread state cover its cross-thread memories?

LangGraph documents checkpointers for thread-scoped graph snapshots and stores for separate cross-thread application data. Applications can use both.

Source: LangChain primary documentation: langgraph persistence. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does removing LangGraph thread state cover its cross-thread memories?

Buyer evidence still required

  • checkpointer implementation
  • thread IDs
  • store implementation/namespaces
  • deletion/export evidence

Review inference: Does removing LangGraph thread state cover its cross-thread memories? Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces. Checkpointer thread state versus independent cross-thread store. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Checkpointer vs. store

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer cross-thread store deletion from a thread-state action; inventory both configured systems and namespaces.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Chrome DevTools MCP: Browser state and optional data sharing

Question: What can a Chrome DevTools agent see or change in my browser session?

The publisher exposes browser inspection and automation, including page interaction and diagnostic capture. Browser content becomes available to the connected agent. Performance features can send trace URLs to the CrUX service, and usage statistics have a documented opt-out. Browser attachment is not a general security sandbox.

Source: Chrome DevTools MCP browser and telemetry controls. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Publisher local server attached to a Chrome browser instance

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Published by the Chrome DevTools team; the buyer runs the local server and browser.

Documented by publisher. Chrome DevTools MCP browser and telemetry controls; Chrome DevTools MCP security boundaries

Purpose

Inspect, automate and diagnose a connected Chrome instance.

Documented by publisher. Chrome DevTools MCP browser and telemetry controls; Chrome DevTools MCP security boundaries

Read capability

Page contents, network information, screenshots and performance traces can be exposed.

Documented by publisher. Chrome DevTools MCP browser and telemetry controls; Chrome DevTools MCP security boundaries

Write capability

Page interaction, script execution and supported file outputs can change browser or local state.

Documented by publisher. Chrome DevTools MCP browser and telemetry controls; Chrome DevTools MCP security boundaries

Authentication

The reviewed local setup attaches to Chrome; an independent identity boundary for the buyer setup is not established here.

Not established. Chrome DevTools MCP browser and telemetry controls; Chrome DevTools MCP security boundaries

Permission surface

Attached browser targets and local process authority determine the practical reach.

Review inference. Chrome DevTools MCP browser and telemetry controls; Chrome DevTools MCP security boundaries

Data leaving the environment

Browser results reach the agent; trace URL sharing and usage telemetry need separate review.

Review inference. Chrome DevTools MCP browser and telemetry controls; Chrome DevTools MCP security boundaries

Failure modes to consider

Untrusted page text, accidental session exposure and retained diagnostic files require consideration.

Review inference. Chrome DevTools MCP browser and telemetry controls; Chrome DevTools MCP security boundaries

Unknowns and applicability

The buyer browser profile, logged-in sessions, enabled telemetry and client handling are unknown.

Not established

Suggested refusal or clarification condition

Do not attach a privileged browsing session without authority for its contents and intended actions.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Attachment modes, telemetry defaults, output storage and browser permissions.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the browser-session and data-recipient questions needed before authorising browser automation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CircleCI caches: Immutable keys can preserve the wrong result

Question: Does an immutable CircleCI cache prove a build used the correct dependencies?

A cache key cannot be overwritten after its first write. Parallel writers can therefore make the selected content depend on completion order, while later writes are discarded. Correctness requires appropriate keys and workflow ordering; immutability alone neither validates dependencies nor guarantees freshness.

Source: CircleCI dependency caching. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Cache immutability proves dependency correctness and freshness.

Buyer evidence still required

  • Cache-key inputs and lockfile identity.
  • Writer/reader job ordering.
  • Installation and dependency verification evidence.

Suggested review condition: Require dependency identity before treating a cache hit as a reproducible build.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Cache keys, writer ordering, dependency lock and verification

Optional saved evidence: Save the dependency identity and workflow assumptions behind a build claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CircleCI contexts: Group, project and expression restrictions combine

Question: Does adding a group restriction prove a CI secret is limited to the intended project?

CircleCI treats group, project and expression restrictions as separate checks. With no project restriction, the documentation allows use across projects in the organisation; defaults and integration support also matter. Review the complete context configuration and trigger path rather than treating group membership as a project allowlist.

Source: CircleCI context restriction scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The context group setting confines the secret to one approved project.

Buyer evidence still required

  • Context security groups and explicit project restrictions.
  • Expression restrictions and supported trigger/integration type.
  • Effective runtime access, including administrator authority and membership refresh.

Suggested review condition: Do not infer project confinement from a group setting alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Context settings, group synchronisation and trigger support.

Optional saved evidence: Save which context restrictions and trigger evidence support the approved secret-use scope.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CircleCI MCP: Diagnostic reads and workflow actions

Question: Can a CircleCI troubleshooting connector rerun or cancel builds?

The hosted tool list includes rerunning and cancelling workflows as well as diagnostic reads. The CLI MCP exposes a broader command surface, so it needs a separate review. Identify the variant, project and intended action before treating a troubleshooting request as permission to alter CI state.

Source: CircleCI MCP transports and authentication. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted CircleCI MCP compared with CLI MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

CircleCI provides hosted and CLI MCP options.

Documented by publisher. CircleCI MCP transports and authentication

Purpose

Investigate CI runs and perform supported CI actions.

Documented by publisher. CircleCI MCP transports and authentication

Read capability

Runs, jobs, logs, tests and artifact listings.

Documented by publisher. CircleCI MCP transports and authentication

Write capability

Hosted tools can rerun or cancel workflows; CLI capabilities are broader.

Documented by publisher. CircleCI MCP transports and authentication

Authentication

Hosted OAuth or personal API token; CLI uses its own authentication.

Documented by publisher. CircleCI MCP transports and authentication

Permission surface

Variant, user/project access and exposed tools determine the review scope.

Documented by publisher. CircleCI MCP transports and authentication

Data leaving the environment

Build logs and artifact metadata can reach the AI client.

Review inference. CircleCI MCP transports and authentication

Failure modes to consider

A diagnostic request may be expanded into a workflow change.

Review inference. CircleCI MCP transports and authentication

Unknowns and applicability

Buyer project permissions and local CLI command surface are unverified.

Not established

Suggested refusal or clarification condition

Clarify rerun or cancellation authority before changing shared CI state.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Hosted tool list, CLI command changes and deprecated client guidance.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the boundary between diagnosing a failed run and authorising its rerun or cancellation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

CK4A: Capture versus promotion

Question: Does completed CK4A capture establish a promotion decision?

The CK4A public source records capture completion with no promotion. Capture preservation does not establish a promotion decision.

Derived from BDAS CK4A — Capture Complete, No Promotion. No new experiment or validation is claimed.

Claim boundaries
  • promotion decision
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

CK4A: Holdout access boundary

Question: Does CK4A capture completion establish new holdout access?

The CK4A public source preserves capture and replay evidence. It explicitly excludes new holdout access.

Derived from BDAS CK4A — Capture Complete, No Promotion. No new experiment or validation is claimed.

Claim boundaries
  • new holdout access
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Claude API omitted-version promotion boundary, distinct from OpenAI default

Question: Can an unpinned Claude Skills API reference remain tied to a previously approved upload?

The captured enterprise guidance says omitted versions use the latest version and workspace uploads can therefore change what production agents run. It recommends explicit version pinning and evaluation before promotion.

Source: Anthropic primary documentation: claude skills enterprise. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an unpinned Claude Skills API reference remain tied to a previously approved upload?

Buyer evidence still required

  • workspace identity
  • exact version
  • reviewed checksum
  • promotion approval
  • previous version

Review inference: Can an unpinned Claude Skills API reference remain tied to a previously approved upload? Do not carry approval across an unreviewed upload; bind the deployed version and checksum with a rollback reference. Claude API omitted-version promotion boundary, distinct from OpenAI default. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not carry approval across an unreviewed upload; bind the deployed version and checksum with a rollback reference.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. If you omit version

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not carry approval across an unreviewed upload; bind the deployed version and checksum with a rollback reference.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude code execution and token-report completeness

Question: Can the Claude Messages usage endpoint alone account for code-execution charges?

Claude documents code-execution costs in the cost endpoint under a Code Execution Usage description, while code execution is not included in the usage endpoint. A Messages usage export cannot by itself establish complete tool charges. Reconcile the cost report and invoice scope with token usage for the same organization and period.

Source: Claude: Usage and Cost API. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Can the Claude Messages usage endpoint alone account for code-execution charges?

Buyer evidence still required

  • Messages usage report
  • Cost report including description grouping
  • Matching organization, period and invoice lines

Review inference: Review claude code execution and token-report completeness before accepting the buyer claim. A non-token execution charge omitted from a usage endpoint is distinct from model token rate categorization. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: No exact invoice or total-task-cost conclusion from token usage alone; applicable charges and adjustments remain buyer evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. How do I track code execution usage?

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No exact invoice or total-task-cost conclusion from token usage alone; applicable charges and adjustments remain buyer evidence.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude Enterprise: Project retention overrides chat retention

Question: Does a Claude Enterprise chat retention period bound every project conversation and cloud AI feature?

Claude documents activity-based retention and gives project retention precedence for chats inside projects, including when the project default is indefinite. Its custom chat and project periods do not apply to Claude Design, Claude Tag, Claude Managed Agents or other features running Claude Code in the cloud. A chat-period setting alone does not establish a universal enterprise data lifetime.

Source: Claude Enterprise: Custom data retention controls. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Enterprise AI Data Custody & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Claude Enterprise chat retention period bound every project conversation and cloud AI feature?

Buyer evidence still required

  • The Enterprise plan and separate chat and project retention settings.
  • Project membership and relevant last-activity or reset events.
  • The feature inventory, excluded cloud features and their separate policies.

Suggested review condition: Do not assert a universal deletion deadline from the chat period while project precedence, activity resets or excluded features remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The Enterprise plan and separate chat and project retention settings. Project membership and relevant last-activity or reset events. The feature inventory, excluded cloud features and their separate policies.

Optional saved evidence: An enterprise buyer must map each AI content location to its operative retention clock and identify features outside the selected policy.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Claude exports: Deleted content is outside later organization exports

Question: Can a later Claude organization export recover content already deleted by users or retention?

Claude states that organization exports are available to Team and Enterprise Primary Owners and contain organization conversation and user data. Messages, files and projects deleted before an export is initiated are excluded. A later export is not a recovery mechanism for already-deleted content, and its scope must be distinguished from a member export.

Source: Claude: Export organization data. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Enterprise AI Data Custody & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a later Claude organization export recover content already deleted by users or retention?

Buyer evidence still required

  • The organization, requesting role and export type.
  • The export initiation time and relevant deletion or retention events.
  • The returned inventory and reconciliation of absent or already-deleted content.

Suggested review condition: Do not describe a later organization export as a complete historical archive or recovery of content deleted before initiation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The organization, requesting role and export type. The export initiation time and relevant deletion or retention events. The returned inventory and reconciliation of absent or already-deleted content.

Optional saved evidence: An exit-planning owner needs to sequence preservation and export against deletion and retention rather than assuming a later archive recovers everything.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Claude null API-key and workspace attribution

Question: Should a Claude usage reconciliation discard rows with null API-key or workspace identifiers?

Claude documents that Console playground usage has a null API-key identifier even when grouped by that dimension, and the default workspace has a null workspace identifier. Such rows can represent documented usage populations. Preserve them with their documented meanings rather than dropping them as missing or assigning them to a guessed customer.

Source: Claude: Usage and Cost API. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Should a Claude usage reconciliation discard rows with null API-key or workspace identifiers?

Buyer evidence still required

  • Grouped usage and cost responses
  • Console versus API usage context
  • Workspace mapping and report filters

Review inference: Review claude null api-key and workspace attribution before accepting the buyer claim. Null reporting dimensions and allocation completeness are distinct from workspace authority or spending limits. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Null identifiers do not identify an independent user, customer or a verified responsible team.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. What happens with playground usage?; How is the default workspace represented?

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Null identifiers do not identify an independent user, customer or a verified responsible team.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude offboarding: Member removal does not erase account data

Question: Does removing a Claude Team or Enterprise member delete their account and organization data?

Claude states that removing a member does not delete their account or data. The Primary Owner can still export removed-member data subject to retention settings; a permanent-deletion request is a separate Support process. SCIM-provisioned users must also be removed in the identity provider to avoid reprovisioning. Loss of shared-chat access is not erasure evidence.

Source: Claude: Data after member removal. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Enterprise AI Data Custody & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does removing a Claude Team or Enterprise member delete their account and organization data?

Buyer evidence still required

  • The organization membership and identity-provider provisioning state.
  • The retained data, export scope and applicable retention settings.
  • The separately authorised permanent-deletion request and its outcome.

Suggested review condition: Do not close an erasure request from member removal or inaccessible chat links alone, or while identity-provider reprovisioning remains possible.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The organization membership and identity-provider provisioning state. The retained data, export scope and applicable retention settings. The separately authorised permanent-deletion request and its outcome.

Optional saved evidence: An organization owner must distinguish revoking membership, preserving required work and completing a separately authorised data-deletion process.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Claude Priority Tier cost-report scope

Question: Does the Claude Cost API report all Priority Tier charges alongside token usage?

Claude documents Priority Tier usage in the usage endpoint through the service_tier dimension, but excludes Priority Tier costs from the cost endpoint because the billing model differs. A cost response alone is not a complete charge inventory when Priority Tier is used. Reconcile the applicable billing evidence separately.

Source: Claude: Usage and Cost API. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Does the Claude Cost API report all Priority Tier charges alongside token usage?

Buyer evidence still required

  • Usage report grouped by service tier
  • Reporting period and organization
  • Applicable Priority Tier billing records and invoice

Review inference: Review claude priority tier cost-report scope before accepting the buyer claim. Cost-report omission for a service tier is distinct from workspace spending caps or key archival. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Missing Priority Tier costs in this endpoint do not mean zero charges or a confirmed invoice discrepancy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Cost API; How do I track Priority Tier usage?

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Missing Priority Tier costs in this endpoint do not mean zero charges or a confirmed invoice discrepancy.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude SDK concurrent hook ordering boundary

Question: Can one Claude SDK hook reliably gate another hook registered for the same event?

The pinned Python SDK hooks documentation states that multiple matchers for the same event dispatch concurrently. Each hook should be independent; applications must not rely on one callback finishing before another starts. The changelog records this as a documentation clarification, not a new sequencing guarantee or runtime change.

Source: Claude Agent SDK for Python: typed public contracts. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can one Claude SDK hook reliably gate another hook registered for the same event?

Buyer evidence still required

  • SDK/CLI versions
  • event matchers and callback dependencies
  • shared-state controls and observed callback ordering

Review inference: Refuse an ordering-dependent approval or sanitisation claim based solely on matcher list order. Verify the actual design and shared-state protection. Concurrent dispatch does not imply that all permission decisions are ignored or that tools always execute. The existing review identifies permission paths that bypass canUseTool. This review concerns concurrency between same-event hook matchers even when hooks are invoked, and rejects assumed callback ordering. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse an ordering-dependent approval or sanitisation claim based solely on matcher list order. Verify the actual design and shared-state protection. Concurrent dispatch does not imply that all permission decisions are ignored or that tools always execute.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Dispatch order; concurrently

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse an ordering-dependent approval or sanitisation claim based solely on matcher list order. Verify the actual design and shared-state protection. Concurrent dispatch does not imply that all permission decisions are ignored or that tools always execute.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude SDK explicit versus inherited MCP servers

Question: Does passing mcp_servers alone establish the entire Claude SDK MCP server inventory?

The pinned Python SDK documents strict_mcp_config=False by default. Setting it to True limits the CLI to servers passed through mcp_servers and ignores other configurations it would otherwise load, including project, user/global and plugin-provided servers. This controls the configuration source set; it does not verify server identity, tool safety or effective permissions.

Source: Claude Agent SDK for Python: typed public contracts. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does passing mcp_servers alone establish the entire Claude SDK MCP server inventory?

Buyer evidence still required

  • SDK/CLI versions and strict_mcp_config value
  • explicit mcp_servers configuration
  • effective project/user/plugin server inventory

Review inference: Refuse a complete admitted-server inventory based only on mcp_servers when inherited configuration is unresolved. Check strict_mcp_config, CLI version and effective inventory; do not claim that every default installation loads every configuration source. The existing plugin record inventories possible components. This decision concerns the explicit SDK switch that bounds which MCP configuration sources the CLI may consume. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a complete admitted-server inventory based only on mcp_servers when inherited configuration is unresolved. Check strict_mcp_config, CLI version and effective inventory; do not claim that every default installation loads every configuration source.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. strict_mcp_config

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a complete admitted-server inventory based only on mcp_servers when inherited configuration is unresolved. Check strict_mcp_config, CLI version and effective inventory; do not claim that every default installation loads every configuration source.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude SDK original and hook-modified tool output

Question: Is the tool output seen by the Claude model necessarily the original tool result?

The pinned Python SDK PostToolUseHookSpecificOutput documents updatedToolOutput as a replacement before the result reaches the model. For built-in tools its shape must match the tool output schema; a mismatch is rejected and the original output is retained. The 0.1.74 changelog introduced this option beyond MCP-only output replacement.

Source: Claude Agent SDK for Python: typed public contracts. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is the tool output seen by the Claude model necessarily the original tool result?

Buyer evidence still required

  • SDK/CLI versions and tool schema
  • original tool result and PostToolUse hook output
  • observed accepted or rejected replacement and model-facing result

Review inference: Refuse to equate a model-facing result with untouched tool evidence without retaining the original result, hook configuration, replacement and acceptance outcome. A configured replacement does not prove it was accepted or that the action succeeded. The existing hook review concerns pre-execution permission precedence. This decision concerns post-execution evidence transformation and the need to distinguish original output from what the model received. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse to equate a model-facing result with untouched tool evidence without retaining the original result, hook configuration, replacement and acceptance outcome. A configured replacement does not prove it was accepted or that the action succeeded.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. updatedToolOutput

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to equate a model-facing result with untouched tool evidence without retaining the original result, hook configuration, replacement and acceptance outcome. A configured replacement does not prove it was accepted or that the action succeeded.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude SDK parallel transcript reader completeness

Question: Does a Claude SDK session reader prove that every parallel tool call was captured?

The Python SDK changelog for 0.2.170 documents a fix to get_session_messages and get_session_messages_from_store: earlier traversal could retain only one branch of a parallel-tool turn. The fix recovers sibling calls and results. This is a documented reader correction, not proof that a particular stored transcript is complete; it does not by itself qualify separate subagent readers.

Source: Claude Agent SDK for Python: changelog. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Claude SDK session reader prove that every parallel tool call was captured?

Buyer evidence still required

  • SDK and bundled CLI versions
  • reader API and pagination options
  • retained transcript and expected tool-use/result IDs

Review inference: Refuse a complete-action-history finding until the installed reader/version, retained transcript and expected parallel call/result identities reconcile. Missing reader output alone is not evidence that the omitted action never ran. The existing GitHub review concerns provider event coverage and export retention. This decision concerns a specific Python SDK traversal defect that can omit sibling tool records even when the stored transcript contains them. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a complete-action-history finding until the installed reader/version, retained transcript and expected parallel call/result identities reconcile. Missing reader output alone is not evidence that the omitted action never ran.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 0.2.170; get_session_messages; parallel

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a complete-action-history finding until the installed reader/version, retained transcript and expected parallel call/result identities reconcile. Missing reader output alone is not evidence that the omitted action never ran.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude SDK stored-session configuration continuity

Question: Does resuming a Claude SessionStore transcript prove the original permission and hook configuration is still effective?

The Python SDK 0.2.137 changelog documents copying settings.json and cowork_settings.json into the temporary configuration directory on SessionStore resume to preserve apiKeyHelper authentication, user hooks, environment variables and permissions. It also records an earlier apiKeyHelper-only authentication failure. This specific fix does not attest that a buyer resumed with the same effective configuration.

Source: Claude Agent SDK for Python: changelog. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does resuming a Claude SessionStore transcript prove the original permission and hook configuration is still effective?

Buyer evidence still required

  • SDK/CLI versions and SessionStore resume path
  • redacted before/after effective settings and hook inventory
  • authentication method and observed resume outcome

Review inference: Refuse authority-continuity approval from transcript recovery alone. Compare effective settings, authentication method, hooks and permissions before and after resume; do not expose credential values or assume every older version loses every setting. Permission inheritance describes parent-to-subagent policy within a run. This review addresses configuration continuity when restoring a stored session into a temporary configuration directory. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse authority-continuity approval from transcript recovery alone. Compare effective settings, authentication method, hooks and permissions before and after resume; do not expose credential values or assume every older version loses every setting.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 0.2.137; SessionStore; settings.json

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse authority-continuity approval from transcript recovery alone. Compare effective settings, authentication method, hooks and permissions before and after resume; do not expose credential values or assume every older version loses every setting.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude SDK subagent parent linkage

Question: Can a Claude SDK subagent transcript identify the parent action that spawned it?

Python SDK 0.2.140 documents recovery of parent_tool_use_id from subagent metadata. The pinned SessionMessage documentation links it to the parent Agent tool-use block, with None when metadata is unavailable. parent_agent_id identifies a spawning subagent, but None can mean either the main session or unavailable metadata. Top-level session readers return None for these fields.

Source: Claude Agent SDK for Python: typed public contracts. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Claude SDK subagent transcript identify the parent action that spawned it?

Buyer evidence still required

  • SDK version and reader API
  • subagent metadata and identifiers
  • parent Agent tool-use block and session transcript

Review inference: Refuse an unambiguous parent-action attribution from a null field. Retain and reconcile the subagent metadata, parent Agent call and session identifiers; linkage does not establish authorisation or successful completion. The existing record establishes permission-mode inheritance. This review addresses evidence linkage between nested transcripts and their parent calls, including ambiguity of missing metadata. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse an unambiguous parent-action attribution from a null field. Retain and reconcile the subagent metadata, parent Agent call and session identifiers; linkage does not establish authorisation or successful completion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. parent_tool_use_id; parent_agent_id

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse an unambiguous parent-action attribution from a null field. Retain and reconcile the subagent metadata, parent Agent call and session identifiers; linkage does not establish authorisation or successful completion.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude SDK terminal result and background idle boundary

Question: Does a Claude query result prove background subagent control traffic has finished?

The Python SDK 0.2.160 changelog documents a query() fix for hooks, can_use_tool and SDK MCP servers: stdin stays open until the CLI reports idle through session_state_changed instead of closing too early around background subagent completion. The wait has a configurable ceiling, default ten minutes. Older CLIs without state events retain close-at-first-result behaviour.

Source: Claude Agent SDK for Python: changelog. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Claude query result prove background subagent control traffic has finished?

Buyer evidence still required

  • Python SDK and CLI versions
  • query configuration and background-task events
  • first result, idle state, wait ceiling and follow-up outcome

Review inference: Refuse complete-background-execution or safe-retry conclusions from the first result or wait expiry alone. Reconcile task states, control-channel lifecycle and terminal evidence. CLI idle and successful business completion are different observations. The existing MCP record concerns progress resetting request timeouts. This review concerns Python SDK stdin lifetime and CLI state events around background subagents, including older-CLI fallback. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse complete-background-execution or safe-retry conclusions from the first result or wait expiry alone. Reconcile task states, control-channel lifecycle and terminal evidence. CLI idle and successful business completion are different observations.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 0.2.160; session_state_changed; CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse complete-background-execution or safe-retry conclusions from the first result or wait expiry alone. Reconcile task states, control-channel lifecycle and terminal evidence. CLI idle and successful business completion are different observations.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude session budgets and final spend

Question: Is a Claude Managed Agents max_list_cost budget an exact upper bound on final session cost?

Claude documents that the model request crossing a session budget completes, potentially exceeding the cap by one model request per thread. Its returned tool calls still run and their search and runtime costs count. The budget bounds starting new work rather than guaranteeing an exact final charge; retain the usage snapshot and stop reason.

Source: Claude Managed Agents: Budgets. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Is a Claude Managed Agents max_list_cost budget an exact upper bound on final session cost?

Buyer evidence still required

  • Session budget and thread inventory
  • Consumed list cost and stop reason
  • Crossing requests, tool work and applicable billing evidence

Review inference: Review claude session budgets and final spend before accepting the buyer claim. Per-session request-boundary stopping differs from organization or workspace monthly caps. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: No exact charge ceiling, invoice amount or verified stop behavior is established by a configured budget alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. When a session reaches its budget

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No exact charge ceiling, invoice amount or verified stop behavior is established by a configured budget alone.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Claude thread totals and session runtime cost

Question: Should summed Claude Managed Agents thread costs equal the session list cost exactly?

Claude documents independently rounded thread figures that exclude the session running-time cost. Session active_seconds counts overlapping thread activity once, and the session figure governs its budget. Differences between summed thread costs and session cost therefore require scope and rounding reconciliation rather than an automatic double-billing conclusion.

Source: Claude Managed Agents: Budgets. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Should summed Claude Managed Agents thread costs equal the session list cost exactly?

Buyer evidence still required

  • Session and thread usage snapshots
  • Overlapping activity intervals
  • Rounding basis and runtime charge
  • Invoice and applicable rates

Review inference: Review claude thread totals and session runtime cost before accepting the buyer claim. Concurrent runtime aggregation and thread cost scope are distinct from spend-limit configuration. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Documented aggregation differences neither prove nor disprove an actual invoice error.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Monitor spend

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Documented aggregation differences neither prove nor disprove an actual invoice error.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

ClickHouse MCP: Read-only defaults and write opt-ins

Question: What evidence separates an analytical ClickHouse MCP session from one that may alter data?

The ClickHouse MCP documentation describes read-only queries by default, an explicit write-access opt-in and an additional destructive-operation control. Database restrictions still apply. Review the effective settings and whether embedded chDB is enabled before making a claim about the session boundary.

Source: ClickHouse MCP read-only and write controls. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official ClickHouse/mcp-clickhouse; remote ClickHouse and optional embedded chDB configuration

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

ClickHouse publishes the MCP server; deployment configuration belongs to the operator.

Documented by publisher. ClickHouse MCP read-only and write controls

Purpose

The server supports data exploration through ClickHouse and optional embedded chDB.

Documented by publisher. ClickHouse MCP read-only and write controls

Read capability

Database and table discovery and analytical queries are exposed.

Documented by publisher. ClickHouse MCP read-only and write controls

Write capability

Writes require explicit enablement; destructive operations have an additional documented opt-in.

Documented by publisher. ClickHouse MCP read-only and write controls

Authentication

Connection credentials identify the database user; MCP transport authentication is separately configured.

Documented by publisher. ClickHouse MCP read-only and write controls

Permission surface

Default query mode is read-only and database restrictions continue to constrain enabled writes.

Documented by publisher. ClickHouse MCP read-only and write controls

Data leaving the environment

Results reach the client; optional local backends change which data environment the tool accesses.

Review inference. ClickHouse MCP read-only and write controls

Failure modes to consider

A stale review may miss newly enabled writes or a second backend.

Review inference. ClickHouse MCP read-only and write controls

Unknowns and applicability

Database grants, effective environment settings, transport exposure and installed version are unverified.

Not established

Suggested refusal or clarification condition

Confirm the backend and effective write policy before describing a connection as analysis-only.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck write flags, destructive-operation controls, backends and database identity.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the configuration assumptions that keep analytical access distinct from data changes.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

ClickUp MCP: Task changes, time entries and usage limits

Question: Does the absence of ClickUp deletion tools make an agent connection read-only?

No. ClickUp documents task changes, comments and time tracking while its FAQ says deletion tools are not currently included. It also requires OAuth and applies plan/add-on-dependent usage limits. Review the intended write actions and workspace before treating the connection as a reporting-only integration.

Source: ClickUp hosted MCP access and workspace actions. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted OAuth server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

ClickUp hosts the MCP service.

Documented by publisher. ClickUp hosted MCP access and workspace actions; ClickUp task, document and time-tracking tools

Purpose

Search workspace content and coordinate work.

Documented by publisher. ClickUp hosted MCP access and workspace actions; ClickUp task, document and time-tracking tools

Read capability

Reads tasks, documents and comments.

Documented by publisher. ClickUp hosted MCP access and workspace actions; ClickUp task, document and time-tracking tools

Write capability

Can change tasks, post updates and manage time entries; deletion tools are currently absent.

Documented by publisher. ClickUp hosted MCP access and workspace actions; ClickUp task, document and time-tracking tools

Authentication

OAuth only; the FAQ excludes personal API-key authentication.

Documented by publisher. ClickUp hosted MCP access and workspace actions; ClickUp task, document and time-tracking tools

Permission surface

The reviewed pages do not enumerate every effective role and resource restriction.

Not established. ClickUp hosted MCP access and workspace actions; ClickUp task, document and time-tracking tools

Data leaving the environment

Workspace content and work activity can be returned to the assistant.

Review inference. ClickUp hosted MCP access and workspace actions; ClickUp task, document and time-tracking tools

Failure modes to consider

A reporting request can be confused with permission to post or record time.

Review inference. ClickUp hosted MCP access and workspace actions; ClickUp task, document and time-tracking tools

Unknowns and applicability

Buyer grants, workspace settings and remaining usage budget are unverified.

Not established

Suggested refusal or clarification condition

Require the target workspace and intended write before changing work records.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck deletion-tool availability, role restrictions and usage policy.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the task-action and usage-limit evidence behind a work-assistant review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Audit Logs permission-level interpretation

Question: Does one granted authorizationInfo entry prove every permission required for a Google Cloud action was granted?

Cloud Audit Logs defines authorizationInfo for resource-and-permission pairs. The granted field applies to the permission and resource represented by that entry. A single granted tuple is not a statement that every required permission, policy condition or downstream business effect succeeded.

Source: AuditLog | Cloud Logging | Google Cloud Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does one granted authorizationInfo entry prove every permission required for a Google Cloud action was granted?

Buyer evidence still required

  • Complete authorizationInfo entries
  • Relevant resource/request attributes and policy context
  • Operation status and downstream outcome evidence

Review inference: Review all relevant authorization entries, resource attributes and request outcome rather than promote one boolean to overall success.

Suggested review condition: Reject all-permissions or completion conclusions from one granted entry.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Unlogged checks and actual downstream completion are not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid overstating authority or completion in audit reconstruction.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Independent validation of effective IAM or business success
  • Unlogged checks and actual downstream completion are not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Billing adjustment issue grouping

Question: Does each Google Cloud adjustment_info.id identify exactly one billing line?

The detailed billing export uses adjustment_info.id to associate lines with the same adjustment issue. It is not a unique row identifier. Adjustment modes include partial correction and complete negation followed by remonetization. Keep the relevant rows, type and mode together before calculating the net correction; deduplicating solely on the issue ID can discard necessary entries.

Source: Google Cloud Billing billing-detailed documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does each Google Cloud adjustment_info.id identify exactly one billing line?

Buyer evidence still required

  • Adjustment issue ID, type and mode
  • All associated rows
  • Original and corrected charge values

Review inference: Group correction and negation lines without dropping repeated adjustment identities. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Do not invent a unique billing-line key or import FOCUS Ledger semantics into this native GCP format. Missing adjustment_info is not evidence of invalid usage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck adjustment_info.id and mode in Google Cloud Billing billing-detailed documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not invent a unique billing-line key or import FOCUS Ledger semantics into this native GCP format. Missing adjustment_info is not evidence of invalid usage.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloud Billing costs, credits and resource-less rows

Question: Does summing Google Cloud exported cost alone include all credits in the invoice net amount?

Google Cloud detailed billing examples reconcile cost with signed credit amounts and include charges whose resource identity is unavailable. A resource-only filter can drop valid costs, and credits must be aggregated at the intended row grain without multiplying costs through repeated-field expansion. The resulting arithmetic is not proof that the export is complete or that an invoice has been paid.

Source: Google Cloud Billing billing-detailed documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does summing Google Cloud exported cost alone include all credits in the invoice net amount?

Buyer evidence still required

  • Cost and repeated credits fields
  • Row grain and invoice period
  • Rows with null or unavailable resource identity

Review inference: Reconcile separately reported credit amounts and uncredited costs. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Sum signed credit amounts as documented; do not claim cost-plus-credits alone guarantees the final payable balance, completeness, settlement, or correct treatment of every contract-specific promotional credit.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck credits.amount; query examples; Return details by cost type for each resource, per invoice month in Google Cloud Billing billing-detailed documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Sum signed credit amounts as documented; do not claim cost-plus-credits alone guarantees the final payable balance, completeness, settlement, or correct treatment of every contract-specific promotional credit.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloud Billing export schema maintenance

Question: Is the BigQuery Cloud Billing export schema guaranteed not to change after integration?

Google warns that billing-export schemas can change and that queries referencing them directly can fail. It recommends normalization through views, which may themselves require maintenance as fields change. A once-valid query or view does not establish that current exports are still consumed completely or correctly.

Source: Google Cloud Billing billing-setup documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Is the BigQuery Cloud Billing export schema guaranteed not to change after integration?

Buyer evidence still required

  • Current export schema
  • Query and normalization view definitions
  • Failed jobs and field-coverage review

Review inference: Version and maintain consumer views when vendor export columns change. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. A view is not permanently immune to changes; its query must be maintained. Existing FOCUS native-column coverage does not promise schema stability or satisfy this provider-maintenance question.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Table schema for the Cloud Billing data exports in Google Cloud Billing billing-setup documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A view is not permanently immune to changes; its query must be maintained. Existing FOCUS native-column coverage does not promise schema stability or satisfy this provider-maintenance question.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloud Billing export writer access

Question: Does an existing Google Cloud billing export table prove it is still receiving new records?

Google documents that removing the export service account's permissions prevents billing-export tables from updating. The setup guidance distinguishes the standard and detailed export writer from the CUD metadata case. A prior successful table is not evidence of continuing updates. Restore appropriate permissions and inspect actual freshness; this record makes no automatic backfill guarantee.

Source: Google Cloud Billing billing-setup documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does an existing Google Cloud billing export table prove it is still receiving new records?

Buyer evidence still required

  • Export type and writer identity
  • Dataset permissions
  • Actual update timestamps and missing interval

Review inference: Check exporter permission continuity before treating stale totals as current. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Limit the account rule to the documented export types; CUD metadata export is expressly excepted. Table existence alone is weak evidence, but no stale table by itself proves this particular cause or promises backfill after repair.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck About dataset permissions in Google Cloud Billing billing-setup documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Limit the account rule to the documented export types; CUD metadata export is expressly excepted. Table existence alone is weak evidence, but no stale table by itself proves this particular cause or promises backfill after repair.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloud Billing invoice month and usage period

Question: Can Google Cloud invoice totals be reconciled by filtering only the usage calendar month?

Google Cloud detailed billing export distinguishes invoice.month from the timestamps of usage. Late-reported usage and adjustments can appear on a later invoice. Reconcile invoice totals by the invoice field and retain the usage interval separately; filtering only by usage month can omit or misplace invoiced charges.

Source: Google Cloud Billing billing-detailed documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can Google Cloud invoice totals be reconciled by filtering only the usage calendar month?

Buyer evidence still required

  • invoice.month
  • Usage start and end timestamps
  • Late usage and adjustment rows

Review inference: Retain late-monetized usage and corrections in the proper invoice comparison. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Invoice.month filtering is a comparison basis, not proof that the delivered dataset is complete or the invoice was paid. Retain export freshness, account, currency and correction scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck invoice.month; differences between exported data and invoices in Google Cloud Billing billing-detailed documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Invoice.month filtering is a comparison basis, not proof that the delivered dataset is complete or the invoice was paid. Retain export freshness, account, currency and correction scope.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloud KMS rotation: New key versions do not rewrite existing ciphertext

Question: Does rotating a Cloud KMS key prove old encrypted data no longer depends on the old version?

The documentation separates creating a new key version from re-encrypting existing data and retiring old versions. Rotation alone does neither. Establish which data still depends on each version before asserting completion; destroying a version still in use can make its data unrecoverable.

Source: Google Cloud KMS key rotation boundaries. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Automatic rotation replaces old encryption and removes all old-key dependency.

Buyer evidence still required

  • Key type, active versions and rotation configuration.
  • Evidence of re-encryption or remaining ciphertext dependencies.
  • Approved retirement checks for versions still needed by data.

Suggested review condition: Do not recommend retiring a key version from rotation status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Key type, version lifecycle and re-encryption coverage.

Optional saved evidence: Save why a rotation event was insufficient evidence of completed data-key migration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Logging sink destination authority

Question: Does creating a Google Cloud log sink always grant its writer permission at the destination?

Google Cloud requires the sink’s writer identity to have appropriate destination permissions. Some console creation paths can grant permissions when the operator has the necessary authority; other configurations require an explicit grant. A sink targeting a log bucket in the same project has a documented no-writer-identity exception.

Source: Route logs to supported destinations | Cloud Logging | Google Cloud Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does creating a Google Cloud log sink always grant its writer permission at the destination?

Buyer evidence still required

  • Sink destination and writerIdentity
  • Destination IAM grant and applicable exception
  • Delivery status and destination records

Review inference: Check the actual sink type, writer and destination grant instead of relying on sink creation success.

Suggested review condition: Refuse delivery coverage claims without effective destination authority or a documented exception.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual IAM state and delivered entries are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Find permission gaps that leave an apparently configured audit export empty.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic destination access for every sink
  • Actual IAM state and delivered entries are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Logging: A sink exclusion is a routing decision

Question: Does excluding a log from one Cloud Logging sink prove Google never received or stored it elsewhere?

Exclusion filters are applied after the Logging API receives entries and determine routing for the relevant sink. Other sinks and aggregated-routing rules can still matter. Review the complete routing topology before treating an exclusion as non-collection, global deletion or absence from every destination.

Source: Cloud Logging routing and exclusions. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: One sink exclusion proves global non-collection and non-retention.

Buyer evidence still required

  • Inclusion/exclusion filters on the relevant sink.
  • Other project and aggregated sinks and their destinations.
  • Evidence of destination retention for the relevant entry class.

Suggested review condition: Do not infer global erasure or non-collection from one routing filter.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Sink filters, aggregated routing, destinations and retention

Optional saved evidence: Preserve the routing evidence needed to distinguish filtering from data erasure.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Spanner: Cancellation requests and terminal results

Question: Does a successful long-running-operation cancel request prove the Spanner operation stopped?

The documented CancelOperation call starts a best-effort asynchronous cancellation; the operation may still complete. GetOperation can establish its later state. Successful cancellation is represented by a CANCELLED error, while DeleteOperation only discards interest in the result and does not cancel the work.

Source: Cloud Spanner: Package google.longrunning. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a successful long-running-operation cancel request prove the Spanner operation stopped?

Buyer evidence still required

  • Service and operation identity with the cancellation request time.
  • Subsequent done state and error or response from the operation.
  • Resource outcome and reconciliation evidence before a replacement action.

Suggested review condition: Decline stopped-or-rolled-back claims from the cancel acknowledgement alone; retain and inspect the terminal result and relevant resource outcome.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Service and operation identity with the cancellation request time. Subsequent done state and error or response from the operation. Resource outcome and reconciliation evidence before a replacement action.

Optional saved evidence: Recovery after an agent timeout must distinguish cancellation requested, cancellation confirmed and work completed despite the request before starting a replacement action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed cancellation, rollback of prior effects or cancellation support for every operation and service
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Storage Bucket Lock and retention changes

Question: Can a project owner unlock or shorten a Cloud Storage bucket retention policy after it is locked?

Cloud Storage describes locking a bucket retention policy as irreversible. A locked policy cannot be removed or reduced, although its period can be increased. Objects remain protected until they satisfy the applicable retention period. Administrative ownership is not documented as a bypass for reducing the locked retention requirement.

Source: Bucket Lock | Cloud Storage | Google Cloud Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a project owner unlock or shorten a Cloud Storage bucket retention policy after it is locked?

Buyer evidence still required

  • Bucket identity, lock state and retention period
  • Object creation/retention timestamps
  • Approved exit deadline and required exception handling

Review inference: Resolve future deletion requirements before locking, and retain the exact lock state and retention settings.

Suggested review condition: Reject a plan that depends on shortening or removing an already locked bucket retention policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual object ages, policy state and legal requirements are not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify irreversible preservation commitments before accepting an erasure deadline.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • An administrator override or independent compliance certification
  • The actual object ages, policy state and legal requirements are not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Storage hierarchical restore identity

Question: Are object name and generation always sufficient to restore a soft-deleted hierarchical Cloud Storage object?

With hierarchical namespace, folder operations can produce soft-deleted objects sharing the same name and generation. Google documents restoreToken as the additional identifier used to select the intended object for restoration. Name and generation alone can therefore be ambiguous in this case; a restore token is an identity discriminator, not an access grant.

Source: Google Cloud Storage soft delete documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Are object name and generation always sufficient to restore a soft-deleted hierarchical Cloud Storage object?

Buyer evidence still required

  • Hierarchical namespace configuration
  • Name, generation and restoreToken
  • Authorized restoration target

Review inference: Supply restoreToken where duplicate path and generation identities need disambiguation. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Keep the rare duplicate/HNS condition and exact object identity explicit. A restoreToken is an identity discriminator, not an access grant. Do not generalize it to ordinary non-hierarchical objects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Restoring objects with duplicate paths in Google Cloud Storage soft delete documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep the rare duplicate/HNS condition and exact object identity explicit. A restoreToken is an identity discriminator, not an access grant. Do not generalize it to ordinary non-hierarchical objects.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloud Storage lifecycle execution and policy changes

Question: Does a Cloud Storage lifecycle eligibility timestamp establish when an object was actually deleted?

Cloud Storage evaluates lifecycle actions asynchronously and warns against relying on execution within a fixed interval after eligibility. Configuration changes can take up to 24 hours to take effect, during which actions may still follow the previous rules. Deletion can also enter soft delete rather than immediately erase the stored object.

Source: Object Lifecycle Management | Cloud Storage | Google Cloud Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Cloud Storage lifecycle eligibility timestamp establish when an object was actually deleted?

Buyer evidence still required

  • Old and new lifecycle configurations with change time
  • Object eligibility and observed current/generation state
  • Soft-delete policy and required final-deletion evidence

Review inference: Track policy version, action outcome and soft-delete state separately from calculated eligibility.

Suggested review condition: Do not assert completed deletion from eligibility or from saving a revised lifecycle rule.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual scheduling and object cleanup progress are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent premature deletion claims and unexpected actions during policy transitions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Immediate execution or instant activation of a changed lifecycle rule
  • Actual scheduling and object cleanup progress are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Storage restore copy lineage

Question: Does restoring a Cloud Storage soft-deleted object consume its retained original version?

Restoring a soft-deleted Cloud Storage object creates a new live copy while retaining the original soft-deleted object until its retention period ends. If restoration replaces an existing live object, that replaced object can itself become soft deleted. A successful restore therefore does not establish that only one copy or generation remains.

Source: Google Cloud Storage soft delete documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does restoring a Cloud Storage soft-deleted object consume its retained original version?

Buyer evidence still required

  • Original and restored generations
  • Existing live object and overwrite behavior
  • Soft-delete retention and copy inventory

Review inference: Reconcile both new live and retained original copies after a restoration. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Scope to documented soft-delete object restore behavior. Do not claim restoration consumes residual copies, proves erasure, preserves all permissions, or completes buyer recovery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Object restores in Google Cloud Storage soft delete documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Scope to documented soft-delete object restore behavior. Do not claim restoration consumes residual copies, proves erasure, preserves all permissions, or completes buyer recovery.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloud Storage soft delete: Recovery has scope and retention conditions

Question: Does Cloud Storage soft delete guarantee recovery of every deleted object and its access settings?

Soft delete preserves eligible deleted data for the configured retention period, subject to supported bucket types and permissions. The guide notes that managed-folder IAM policies are not restored and that retained deleted objects can continue to incur storage costs. Recovery of content and recovery of its access context are separate questions.

Source: Cloud Storage soft delete and retained data. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Soft delete guarantees complete recovery of data and all permissions.

Buyer evidence still required

  • Bucket type and soft-delete policy at deletion time.
  • Retained object identity, retention interval and restore permissions.
  • Managed-folder IAM and storage-cost evidence.

Suggested review condition: Require policy, retained-state and access-context evidence before promising recovery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Bucket type, retention policy, object identity and restore permissions

Optional saved evidence: Save what must be available to recover both data and its required access context.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Storage soft-deleted buckets and objects

Question: Does deleting a Cloud Storage bucket with soft delete enabled prove that the bucket and its objects are permanently gone?

Cloud Storage soft delete preserves deleted buckets and objects for the configured period. A bucket restored through the CLI or JSON API is restored empty; restoring its objects is a separate operation. Project deletion can shorten preservation to the smaller of the soft-delete duration and project recovery window. Deletion and restoration scope must be checked separately.

Source: Soft delete overview | Cloud Storage | Google Cloud Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a Cloud Storage bucket with soft delete enabled prove that the bucket and its objects are permanently gone?

Buyer evidence still required

  • Bucket policy, deletion time and project state
  • Soft-deleted object generations and retention deadlines
  • Restoration method and required object inventory

Review inference: Inventory soft-deleted resources and the actual restoration path rather than use a missing live bucket as erasure proof.

Suggested review condition: Do not accept live-bucket absence as permanent erasure while soft-deleted resources remain.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s configured duration and remaining resource generations are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Distinguish live-resource removal from retained, potentially recoverable storage.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed recovery or physical erasure from a bucket deletion response
  • The buyer’s configured duration and remaining resource generations are unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Storage soft-deleted inventory visibility

Question: Does an ordinary Cloud Storage object listing include retained soft-deleted copies?

Google Cloud Storage excludes soft-deleted objects and buckets from ordinary listings unless soft-deleted resources are specifically requested. To list soft-deleted objects inside a deleted bucket, the bucket must first be restored. An empty default listing is therefore not evidence that no recoverable objects remain.

Source: Google Cloud Storage soft delete documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an ordinary Cloud Storage object listing include retained soft-deleted copies?

Buyer evidence still required

  • Bucket state
  • Listing options and permissions
  • Soft-deleted object inventory

Review inference: Require explicit soft-deleted inventory when closing a data-exit review. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Keep the new claim at list-scope completeness; do not republish the generic retained-data fact as new. Listing contents of a soft-deleted bucket requires restoring the bucket first. Restoration is not authorized by an evidence answer.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Soft delete overview in Google Cloud Storage soft delete documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep the new claim at list-scope completeness; do not republish the generic retained-data fact as new. Listing contents of a soft-deleted bucket requires restoring the bucket first. Restoration is not authorized by an evidence answer.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloud Storage: Retry conditions and object identity

Question: Can a delayed object-delete retry remove a newer Cloud Storage object with the same name?

A delayed delete without a generation condition can affect a replacement object with the same name. A matching generation precondition binds deletion to that object generation; a mismatch returns 412. For object metadata conditions, Google recommends checking generation as well as metageneration. Retryable errors alone do not establish safe repetition.

Source: Cloud Storage: Request preconditions. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a delayed object-delete retry remove a newer Cloud Storage object with the same name?

Buyer evidence still required

  • Bucket, object name and originally observed generation/metageneration.
  • Exact request preconditions and retry settings for the API or client.
  • Per-attempt responses and subsequent resource observations.

Suggested review condition: Decline a safe-retry claim without the original target conditions; investigate a mismatch instead of silently dropping the condition.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Bucket, object name and originally observed generation/metageneration. Exact request preconditions and retry settings for the API or client. Per-attempt responses and subsequent resource observations.

Optional saved evidence: Recovery must preserve the intended resource version when another actor may replace or edit it.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authorization to delete, verified target state or a guarantee that every client retries conditionally
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloud Tasks: Task identity and handler completion

Question: Does assigning a Cloud Tasks name make the handler operation exactly-once?

A caller-selected task name supports task-creation deduplication. It does not demonstrate that a handler's external work committed once. Delivery headers distinguish retries from executions, and the scheduled ETA changes on retries; the publisher explicitly says ETA is not a deduplication key.

Source: Cloud Tasks task creation and deduplication. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A task name or ETA guarantees one completed handler effect.

Buyer evidence still required

  • Task naming and creation path.
  • Handler operation identity and commit evidence.
  • Retry and execution counters used in reconciliation.

Suggested review condition: Require a stable business identity rather than using ETA as proof of unique work.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Task creation method, naming, handler authentication, counters and downstream commit semantics.

Optional saved evidence: Retain the distinction between queue identity and a completed business operation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudEvents absent and explicit-null data

Question: Does a CloudEvents envelope with missing data mean the same as an explicit null payload?

CloudEvents 1.0.2 permits an event without data. Its JSON format separately permits an explicit null JSON payload and distinguishes it from absence of the data member. Normalising both into one state can discard a documented distinction. Event-envelope validity therefore does not establish that an action payload was captured or retained.

Source: CloudEvents v1.0.2 — spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a CloudEvents envelope with missing data mean the same as an explicit null payload?

Buyer evidence still required

  • Original serialized event
  • Content type and decoder behaviour
  • Capture policy and expected action payload

Review inference: Preserve absence and explicit-null states when assessing payload completeness. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse payload-completeness approval from a valid envelope with absent data.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether data was omitted upstream, intentionally null or lost is unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Whether data was omitted upstream, intentionally null or lost is unobserved.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents deduplication and occurrence counts

Question: Can CloudEvents id alone identify duplicate business actions across several sources?

CloudEvents 1.0.2 requires the source and id combination to identify a distinct event; a resent duplicate may retain that pair. The specification also permits one occurrence to produce more than one event. Event-level deduplication therefore needs source as well as id, while distinct event pairs alone do not establish distinct business actions.

Source: CloudEvents v1.0.2 — spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can CloudEvents id alone identify duplicate business actions across several sources?

Buyer evidence still required

  • Original source and id values
  • Producer mapping from occurrences to emitted events
  • Business action or transaction correlation evidence

Review inference: Keep event identity separate from deduplicated business-action counts. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse duplicate-action or unique-action counts based only on event IDs.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual producer uniqueness and business execution were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual producer uniqueness and business execution were not verified.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents envelope version versus data schema

Question: Does CloudEvents specversion 1.0 identify the exact payload schema or specification patch version?

CloudEvents 1.0.2 requires specversion to be 1.0, retaining only major and minor numbers across specification patch changes. The separate optional dataschema URI identifies the payload schema, and incompatible schema changes should use a different URI. The envelope version therefore cannot establish a particular payload contract or the exact specification patch used by an implementation.

Source: CloudEvents v1.0.2 — spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does CloudEvents specversion 1.0 identify the exact payload schema or specification patch version?

Buyer evidence still required

  • Declared specversion and implementation version
  • Payload schema identifier and retained schema revision
  • Producer compatibility and validation evidence

Review inference: Pin payload interpretation separately from envelope compatibility. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse exact payload-schema or patch-version attribution from specversion alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Producer schema conformance and implementation patch level were not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Producer schema conformance and implementation patch level were not assessed.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents HTTP envelope versus payload media type

Question: Does an HTTP Content-Type header always describe only the CloudEvents event payload?

The 1.0.2 HTTP binding distinguishes binary, structured and batched modes. In binary mode, the HTTP body carries event data and Content-Type reflects datacontenttype, while other attributes use headers. Structured and batched modes place event metadata and data in the body using the event-format media type. Interpreting the header without the content mode can confuse envelope encoding with payload encoding.

Source: CloudEvents v1.0.2 — http-protocol-binding. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an HTTP Content-Type header always describe only the CloudEvents event payload?

Buyer evidence still required

  • HTTP headers and body
  • Detected content mode and supported event format
  • Payload datacontenttype and decoding result

Review inference: Decode and preserve event evidence according to its actual HTTP content mode. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse payload interpretation based on HTTP Content-Type without identifying the event mode.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No actual transport message or decoder was inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No actual transport message or decoder was inspected.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents JSON decoding and original data

Question: Should a CloudEvents JSON consumer parse a string-valued JSON data field again as a JSON document?

The 1.0.2 JSON format requires JSON-formatted data to be interpreted directly as a JSON value. A string-valued data member remains a JSON string and must not be decoded again as a JSON document. Binary values instead use data_base64, mutually exclusive with data. Missing datacontenttype is interpreted as application/json. Evidence interpretation must preserve those distinctions rather than infer a nested document from its appearance.

Source: CloudEvents v1.0.2 — json-format. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Should a CloudEvents JSON consumer parse a string-valued JSON data field again as a JSON document?

Buyer evidence still required

  • Original data or data_base64 representation
  • Declared or implied content type
  • Decoder configuration and retained decoded value

Review inference: Avoid changing the meaning of retained payloads during audit ingestion. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse a reconstructed payload interpretation produced by unsupported double decoding.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer decoder or archived payload was tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No buyer decoder or archived payload was tested.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents negotiated batch scope

Question: Can a sender use CloudEvents HTTP batched mode without receiver solicitation and mix specification versions?

The 1.0.2 HTTP binding forbids batched mode unless it is solicited and recommends allowing the receiver to choose the maximum batch size. A batch may be empty, but all its events must have the same specversion; other attributes, including datacontenttype, can differ. A shared HTTP envelope is not specified here as a transactional or all-events-processed guarantee.

Source: CloudEvents v1.0.2 — http-protocol-binding. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a sender use CloudEvents HTTP batched mode without receiver solicitation and mix specification versions?

Buyer evidence still required

  • Receiver solicitation and batch-size agreement
  • Each event specversion and content type
  • Application-level per-event processing receipts

Review inference: Check negotiated batch support and per-event interpretation before accepting batch evidence. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse atomic or complete batch-processing claims from a single HTTP envelope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual processing, retries and transactionality remain application-specific.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual processing, retries and transactionality remain application-specific.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents occurrence-time interpretation

Question: Does CloudEvents time always represent the actual time the underlying action happened?

CloudEvents 1.0.2 makes time optional. If the occurrence time cannot be determined, a producer may use another time, such as the current time, provided producers sharing that source use a consistent determination policy. A timestamp must therefore be interpreted with that source policy; presence of time alone does not establish the actual action instant or cross-system order.

Source: CloudEvents v1.0.2 — spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does CloudEvents time always represent the actual time the underlying action happened?

Buyer evidence still required

  • Source timestamp policy and clock assumptions
  • Original event time and receipt observations
  • Independent action chronology or correlation evidence

Review inference: Avoid reconstructing action chronology from an undocumented timestamp basis. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse exact occurrence-time or cross-system-order claims without the source time policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Clock accuracy, fallback use and actual action time are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Clock accuracy, fallback use and actual action time are unknown.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents original trace versus transport hops

Question: Should ce-traceparent be replaced by each intermediary HTTP hop traceparent when forwarding a CloudEvent?

The distributed-tracing extension published with version 1.0.2 retains the starting trace across multi-hop event transmission; individual-hop tracing is carried by protocol-specific headers. For a single hop the contexts must agree. Middleware may add the extension when absent. Extension support is optional and these listed extensions have no official core standing, so implementations and their forwarding behaviour must be confirmed separately.

Source: CloudEvents v1.0.2 — distributed-tracing. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Should ce-traceparent be replaced by each intermediary HTTP hop traceparent when forwarding a CloudEvent?

Buyer evidence still required

  • Event extension trace fields
  • Protocol trace context for each hop
  • Producer and intermediary extension support and changes

Review inference: Preserve original event provenance without confusing it with transport-hop tracing. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse a complete causal chain from a single ce-traceparent value.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No actual trace continuity or authenticated causality was verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No actual trace continuity or authenticated causality was verified.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents partition keys across intermediaries

Question: Does an unchanged CloudEvents source guarantee that partitionkey remains stable through every hop?

The partitioning extension published with version 1.0.2 provides a grouping key for broker partitioning, but explicitly permits that value to change or disappear across hops because of protocol semantics or processing logic. The extension is optional and has no official core standing. A partition key therefore needs hop-specific provenance before it is treated as an end-to-end correlation identifier.

Source: CloudEvents v1.0.2 — partitioning. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an unchanged CloudEvents source guarantee that partitionkey remains stable through every hop?

Buyer evidence still required

  • Partition values at producer and intermediaries
  • Broker mapping and transformation rules
  • Independent action-correlation identifiers

Review inference: Avoid reconstructing a complete action group from an unstable transport partition key. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse stable end-to-end grouping based only on one observed partitionkey.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual broker partition placement and cross-hop key continuity are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual broker partition placement and cross-hop key continuity are unknown.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents rate-limit retry timing

Question: Can a CloudEvents sender ignore Retry-After on a 429 response without violating its delivery contract?

The Web Hooks specification published with CloudEvents 1.0.2 recommends 429 Too Many Requests when a target exceeds a request-rate limit and requires that response to contain Retry-After. It requires the sender to respect that value and refrain from further requests until the indicated time. Immediate retry or a separately chosen shorter delay does not satisfy that delivery rule; throttling still does not establish a business outcome.

Source: CloudEvents v1.0.2 — http-webhook. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a CloudEvents sender ignore Retry-After on a 429 response without violating its delivery contract?

Buyer evidence still required

  • 429 response with Retry-After value
  • Sender retry timestamps and clock interpretation
  • Outstanding event and business-outcome correlation

Review inference: Distinguish compliant retry scheduling from accepted or completed processing. This is a review judgment, not an observed deployment outcome.

Suggested review condition: Refuse a compliant retry claim when the sender ignored Retry-After.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer retry scheduler or downstream effect was tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No buyer retry scheduler or downstream effect was tested.
  • No verified business outcome, complete event capture, certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents referenced payload lifetime

Question: Does retaining a CloudEvent with dataref preserve its payload for a later audit?

The dataref extension published with version 1.0.2 permits a reference to externally stored data and allows middleware to replace embedded data with that reference. The referenced content may require separate access information and is only recommended to remain available long enough for consumers, not for an extended archive period. This optional, non-core extension is therefore not a durable payload-preservation receipt.

Source: CloudEvents v1.0.2 — dataref. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does retaining a CloudEvent with dataref preserve its payload for a later audit?

Buyer evidence still required

  • Original event and dataref value
  • Authorised payload retrieval and integrity record
  • Payload retention and access-expiry contract

Review inference: Retain payload access and integrity evidence before a transient reference expires. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse long-term payload availability from an archived dataref alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual external payload integrity, lifetime and access were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual external payload integrity, lifetime and access were not tested.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents retired webhook destinations

Question: When must a CloudEvents sender stop delivery after a 410 Gone response?

The Web Hooks specification published with CloudEvents 1.0.2 recommends 410 Gone when a delivery target is retired while the HTTP site still exists, and recommends that the sender stop further notifications. This is retirement guidance, not an acknowledgement that earlier events were processed or that stored payloads were deleted. Closure requires separate reconciliation of outstanding deliveries and retained data.

Source: CloudEvents v1.0.2 — http-webhook. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: When must a CloudEvents sender stop delivery after a 410 Gone response?

Buyer evidence still required

  • Target response and retirement time
  • Outstanding delivery inventory
  • Sender retry and endpoint-retirement configuration

Review inference: Separate destination retirement from completed event processing and data deletion. This is a review judgment, not an observed deployment outcome.

Suggested review condition: Refuse completed processing or deletion from a 410 retirement response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Sender compliance and earlier event outcomes were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Sender compliance and earlier event outcomes were not observed.
  • No verified business outcome, complete event capture, certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents sequence interpretation and wraparound

Question: Can a CloudEvents sequence value be sorted as an unbounded global event counter?

The sequence extension published with version 1.0.2 requires interpretation through sequencetype or an out-of-band agreement if that type is absent or unknown. Its defined Integer type uses string-encoded signed 32-bit values, starts at one, advances contiguously and wraps from the maximum to the minimum signed value. This optional, non-core extension therefore does not supply an unbounded global ordering or independently prove complete capture.

Source: CloudEvents v1.0.2 — sequence. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a CloudEvents sequence value be sorted as an unbounded global event counter?

Buyer evidence still required

  • Source stream and sequence type agreement
  • Original sequence values and wrap context
  • Producer continuity and retained-event inventory

Review inference: Interpret event order within the agreed source sequence and counter range. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse global chronology or missing-event conclusions without sequence semantics and source scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual producer compliance, counter epoch and capture completeness are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual producer compliance, counter epoch and capture completeness are unknown.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents source context and producer identity

Question: Does a CloudEvents source URI identify exactly one authenticated emitting process?

CloudEvents 1.0.2 defines source as the context of the occurrence, which may include multiple producers. An external producer may create an event on behalf of a source that is unaware of CloudEvents. The source URI and its producer-defined semantics therefore do not by themselves identify or authenticate the individual process that emitted the event.

Source: CloudEvents v1.0.2 — spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a CloudEvents source URI identify exactly one authenticated emitting process?

Buyer evidence still required

  • Source namespace and producer registry
  • Authenticated transport or signing identity
  • Event creation and forwarding provenance

Review inference: Request producer and transport identity evidence before attributing an event to an actor. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse single-process or authenticated-actor attribution from the source URI alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Emitter identity and source ownership are not independently established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Emitter identity and source ownership are not independently established.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents subscription consent and authentication

Question: Does the CloudEvents webhook OPTIONS handshake authenticate the sender or authorise its business action?

The 1.0.2 Web Hooks specification describes the validation handshake as abuse protection: the destination agrees to receive notifications so a sender cannot be directed at an unsuspecting endpoint. It explicitly does not establish authentication or authorisation context. The separate delivery access-control model must be assessed independently of that subscription consent.

Source: CloudEvents v1.0.2 — http-webhook. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the CloudEvents webhook OPTIONS handshake authenticate the sender or authorise its business action?

Buyer evidence still required

  • Validation request and destination response
  • Delivery authentication and access-control policy
  • Actor authority and intended action scope

Review inference: Distinguish notification consent from authenticated delivery and business authority. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse authenticated-sender or business-authority conclusions from handshake success.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual credential validation and action permission were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual credential validation and action permission were not inspected.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents webhook processing acknowledgements

Question: Does a CloudEvents HTTP webhook response of 202 establish that its event was processed?

The 1.0.2 Web Hooks specification assigns 202 Accepted when delivery is accepted but processing has not occurred or its status is unknown. It distinguishes processed responses and their optional details, while leaving error-detail payloads undefined. A 202 receipt therefore records acceptance, not completed business processing; later application evidence is needed to close the outcome.

Source: CloudEvents v1.0.2 — http-webhook. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a CloudEvents HTTP webhook response of 202 establish that its event was processed?

Buyer evidence still required

  • Delivery request identity and HTTP response
  • Receiver processing contract and status evidence
  • Correlated business outcome or failure receipt

Review inference: Keep accepted event delivery separate from completed downstream action. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse completed processing from 202 Accepted alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The specification does not independently verify any business result.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The specification does not independently verify any business result.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

CloudEvents webhook redirects and destination control

Question: Can a CloudEvents HTTP receiver follow a redirect without changing the authorised destination?

The Web Hooks specification published with CloudEvents 1.0.2 forbids delivery responses from using 3xx redirects and forbids clients from following them. A redirect cannot be treated as a compliant continuation of this delivery contract. A replacement endpoint therefore needs separate configuration and authority review; the original subscription does not establish the new recipient.

Source: CloudEvents v1.0.2 — http-webhook. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a CloudEvents HTTP receiver follow a redirect without changing the authorised destination?

Buyer evidence still required

  • Configured destination and subscription authority
  • Original HTTP response status and headers
  • Approved endpoint-change record

Review inference: Prevent delivery being silently redirected to a different recipient. This is a review judgment, not an observed deployment outcome.

Suggested review condition: Refuse compliant delivery attribution through a followed 3xx response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual client redirect handling and destination authority are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual client redirect handling and destination authority are unobserved.
  • No verified business outcome, complete event capture, certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cloudflare Access: Gateway sessions and SaaS sessions differ

Question: Does an Access application-session limit end the session inside a SaaS app?

Cloudflare documents that the Access duration controls entry to the SaaS application, whose own cookie manages the session inside it. Session revocation also needs to be distinguished from preventing a still-authorised identity from returning. Review both systems before accepting a complete-session-termination claim.

Source: Cloudflare Access sessions and SaaS sessions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The gateway session limit guarantees the user leaves every connected application.

Buyer evidence still required

  • Access application type and session configuration.
  • SaaS-issued session lifetime and termination mechanism.
  • Identity disablement or policy changes and observed re-entry behaviour.

Suggested review condition: Keep complete termination unproven without application-session evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Access policy, SaaS session behaviour and identity lifecycle.

Optional saved evidence: Preserve the gap between gateway reauthentication and termination of an existing SaaS session.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloudflare API MCP: API reach behind a compact tool list

Question: Does a small Cloudflare MCP tool list imply narrow account permissions?

Cloudflare's API MCP uses search and execute operations to reach a broad API surface. A small visible tool list therefore does not establish narrow authority. Check OAuth grants or API-token permissions and the intended account resources. The docs and repository describe different tool totals; this record preserves that ambiguity rather than using a count as a security claim.

Source: Cloudflare managed MCP servers. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Cloudflare API MCP at its published remote endpoint; excludes separate domain-specific Cloudflare servers.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Cloudflare operates the API MCP service.

Documented by publisher. Cloudflare managed MCP servers; Cloudflare API MCP configuration

Purpose

Discover Cloudflare API operations and work with account resources.

Documented by publisher. Cloudflare managed MCP servers; Cloudflare API MCP configuration

Read capability

Account configuration and data reachable through permitted API operations.

Documented by publisher. Cloudflare managed MCP servers; Cloudflare API MCP configuration

Write capability

Execution can call mutating API operations; effective reach depends on grants and target resources.

Documented by publisher. Cloudflare managed MCP servers; Cloudflare API MCP configuration

Authentication

OAuth permission selection or user/account API bearer tokens is documented.

Documented by publisher. Cloudflare managed MCP servers; Cloudflare API MCP configuration

Permission surface

Review actual token grants and resource scope. The repository states that API-token client IP filtering is currently unsupported.

Documented by publisher. Cloudflare managed MCP servers; Cloudflare API MCP configuration

Data leaving the environment

API requests run through the hosted MCP and results return to the client; selected results may enter the client's model workflow.

Review inference. Cloudflare managed MCP servers; Cloudflare API MCP configuration

Failure modes to consider

Using tool count as a permission limit; executing against the wrong account; relying on unsupported token IP filtering.

Review inference. Cloudflare managed MCP servers; Cloudflare API MCP configuration

Unknowns and applicability

Effective account/token grants, current deployed tool inventory, client handling and compatibility of a particular restricted token.

Not established

Suggested refusal or clarification condition

Check account and requested API method before execution; stop when the selected token cannot meet the task's required restrictions.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the evidence showing why a compact tool interface still requires an account-permission review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloudflare API tokens: Permission, resource and usage constraints

Question: Does a Cloudflare token's Read or Edit label establish its complete access boundary?

Cloudflare configures token permissions separately from selected resources. Its guide defines Edit as broader create/read/update/delete/list access, while client-IP filtering and token lifetime are optional restrictions. A label alone does not establish which zones, accounts, networks or duration were selected.

Source: Cloudflare: Create API token. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a Cloudflare token's Read or Edit label establish its complete access boundary?

Buyer evidence still required

  • Effective permission groups and levels.
  • Explicit included resources.
  • Configured client-IP and lifetime restrictions, if any.

Suggested review condition: Do not assume optional resource or usage restrictions are enabled without configuration evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token permission groups, resources, client networks and validity period.

Optional saved evidence: Retain the exact restrictions supporting infrastructure-connector procurement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloudflare Logpush evidence: Delivery gaps and retained history

Question: Does enabling Cloudflare Logpush provide a complete searchable archive of past activity?

Cloudflare describes Logpush as delivery to a destination, without its own storage or search service. It cannot backfill historical data. A usable history therefore depends on the selected dataset, successful delivery and destination retention; missing records during a failed or disabled job cannot be treated as evidence of no activity.

Source: Cloudflare Logpush storage and delivery scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Turning on Logpush creates a complete retained history, including earlier gaps.

Buyer evidence still required

  • Job configuration showing dataset and filters
  • Delivery-health history covering the claimed interval
  • Destination receipt and retention evidence for the records being relied on

Suggested review condition: Qualify the history when delivery or retention is unproven; do not infer a clean incident history from missing logs.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck job health, dataset availability, filters and destination retention.

Optional saved evidence: Retain the capture and retention gaps behind a logging-completeness claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloudflare Logpush: Filtering and sampling narrow the event set

Question: Does successful Logpush delivery prove the destination includes every event in the chosen dataset?

Cloudflare lets jobs filter dataset records using expressions and apply output sampling on top of filtering. Delivery success therefore describes the configured selection, not necessarily the whole dataset. The filter and sampling settings are part of any declared coverage claim.

Source: Cloudflare: Logpush filters. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does successful Logpush delivery prove the destination includes every event in the chosen dataset?

Buyer evidence still required

  • Job dataset and resource scope.
  • Full filter and sample-rate settings.
  • Destination window and selected-event evidence.

Suggested review condition: Describe the selected population explicitly and retain excluded or sampled-out coverage as unknown.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Dataset, account or zone, filter expression and output sample rate.

Optional saved evidence: Does successful Logpush delivery prove the destination includes every event in the chosen dataset?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloudflare Logpush: Output updates can change evidence shape

Question: Does updating one Logpush output option preserve every previously configured evidence field and format?

Cloudflare documents that an update replaces the entire output_options object; omitted options reset to defaults. Selected field names and timestamp formatting therefore need to be retained together. A partial update can change the evidence shape even while delivery continues.

Source: Cloudflare: Log output options. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does updating one Logpush output option preserve every previously configured evidence field and format?

Buyer evidence still required

  • Before and after output_options objects.
  • Selected fields and timestamp format.
  • Destination records spanning the change.

Suggested review condition: Review the complete replacement configuration and reconcile schema changes across the audit window.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Job identity, complete output options and configuration-change time.

Optional saved evidence: Does updating one Logpush output option preserve every previously configured evidence field and format?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloudflare R2: Lifecycle expiry and observed removal differ

Question: Does an R2 lifecycle rule prove that all targeted objects were deleted immediately?

Cloudflare says R2 objects are typically removed within 24 hours of x-amz-expiration. Applying a changed lifecycle configuration to existing objects can take longer depending on object count, and old rules may remain visible during migration. New objects reflect the new expiry immediately. The documented default rule for unfinished multipart uploads is a separate seven-day expiry.

Source: Object lifecycles · Cloudflare R2 docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an R2 lifecycle rule prove that all targeted objects were deleted immediately?

Buyer evidence still required

  • Bucket, rule filters, enabled actions and change timestamps.
  • Matching object inventory, expiry metadata and later retrieval/listing outcomes.
  • Separate multipart-upload inventory and other copies or retention constraints.

Review inference: A rule or elapsed expiry timestamp does not establish completed deletion of the intended inventory.

Suggested review condition: Refuse immediate or complete deletion claims based solely on configured lifecycle rules.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual object absence, inventory completeness and external copies are unobserved.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck rule filters, existing-object migration and actual state after changes.

Optional saved evidence: Identify residual resources before closing a data-retention or exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed exact deletion time, physical erasure or removal from all copies
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloudflare R2: Location hints and jurisdiction restrictions

Question: Does an R2 location hint guarantee a storage jurisdiction?

No. Cloudflare describes location hints as best-effort placement preferences and documents jurisdiction restrictions separately. A bucket jurisdiction cannot be changed after creation. Review the actual bucket configuration and relevant service path; a hint is insufficient evidence of a jurisdiction commitment.

Source: Cloudflare R2 location hints and jurisdiction restrictions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A preferred R2 location proves jurisdiction-restricted storage.

Buyer evidence still required

  • Bucket jurisdiction rather than only the location hint
  • Jurisdiction-specific access configuration where applicable
  • Scope of any additional processing or connected services

Suggested review condition: Do not infer a residency or compliance conclusion from a placement hint.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck bucket recreation, access configuration and service limitations.

Optional saved evidence: Save the distinction between placement preference and jurisdiction evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudFormation: Drift results cover only checked configuration

Question: Does an IN_SYNC CloudFormation drift result prove every agent-managed resource matches its intended configuration?

CloudFormation checks supported resources and explicitly specified property values; unsupported resources are NOT_CHECKED, and a parent-stack drift check does not inspect nested stacks. An IN_SYNC result therefore does not establish whole-environment conformity. Reconcile the checked resources and properties with the actual intended-state inventory.

Source: AWS CloudFormation: Detect unmanaged configuration changes. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Does an IN_SYNC CloudFormation drift result prove every agent-managed resource matches its intended configuration?

Buyer evidence still required

  • The intended stack templates, explicit properties and nested-stack inventory.
  • The completed detection result, resource statuses and checked scope.
  • Separate evidence for unsupported resources, omitted properties and nested stacks.

Suggested review condition: Refuse a whole-environment conformity claim while relevant properties, unsupported resources or nested stacks remain unchecked.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The intended stack templates, explicit properties and nested-stack inventory. The completed detection result, resource statuses and checked scope. Separate evidence for unsupported resources, omitted properties and nested stacks.

Optional saved evidence: A platform owner closing an agent change needs to know which intended properties the post-change drift evidence actually compared.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudFormation: Skipped rollback and unresolved resources

Question: Does CloudFormation rollback completion prove skipped resources match the stack template?

ContinueUpdateRollback can skip eligible resources using ResourcesToSkip. CloudFormation marks those resources UPDATE_COMPLETE while their state remains inconsistent with the template after rollback. AWS requires reconciling the stack or resources before another update. The completed rollback therefore does not establish restoration of each skipped resource.

Source: AWS CloudFormation: ContinueUpdateRollback. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does CloudFormation rollback completion prove skipped resources match the stack template?

Buyer evidence still required

  • Failed rollback events and exact ResourcesToSkip identifiers.
  • Actual skipped-resource state compared with the intended template.
  • Reconciliation changes, approval and subsequent verification.

Suggested review condition: Decline restored-state claims while skipped resources remain unreconciled, regardless of their displayed completion status.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Failed rollback events and exact ResourcesToSkip identifiers. Actual skipped-resource state compared with the intended template. Reconciliation changes, approval and subsequent verification.

Optional saved evidence: A recovery status must not conceal configuration drift left by an agent-assisted deployment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified application recovery, reconciled permissions or safe execution of a subsequent stack update
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cloudinary MCP: Product environments and media operations

Question: Does enabling Cloudinary media analysis also define every available asset action?

No. Cloudinary documents separate servers for asset management, configuration, metadata, analysis and MediaFlows. Their authentication options also differ. Review the enabled servers, selected product environment and available tools; analysis access alone is insufficient evidence about upload, deletion or configuration authority.

Source: Cloudinary MCP product environments and server roles. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Asset, configuration, metadata and analysis services

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Cloudinary hosts remote services and publishes local alternatives.

Documented by publisher. Cloudinary MCP product environments and server roles

Purpose

Manage, transform, analyse and configure media workflows.

Documented by publisher. Cloudinary MCP product environments and server roles

Read capability

Reads media and related metadata for supported tools.

Documented by publisher. Cloudinary MCP product environments and server roles

Write capability

Asset tools include upload, rename and deletion; other servers manage configuration and metadata.

Documented by publisher. Cloudinary MCP product environments and server roles

Authentication

OAuth is the usual remote path; credential support differs for Analysis and MediaFlows.

Documented by publisher. Cloudinary MCP product environments and server roles

Permission surface

The selected product environment and enabled server/tool set need review.

Documented by publisher. Cloudinary MCP product environments and server roles

Data leaving the environment

Media content or analysis results may enter the assistant and processing services.

Review inference. Cloudinary MCP product environments and server roles

Failure modes to consider

A plugin can enable more server roles than the immediate task requires.

Review inference. Cloudinary MCP product environments and server roles

Unknowns and applicability

Buyer tool configuration, media rights and effective credentials are unknown.

Not established

Suggested refusal or clarification condition

Identify the cloud and permitted action before asset deletion or configuration changes.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck installed plugin contents, server roles and authentication differences.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the selected-server and media-action boundary for a connector review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudTrail integrity: Digest delivery is separate from validation

Question: Does enabling CloudTrail log-file integrity validation prove the delivered files were validated?

Enabling the feature delivers signed digest files. The documentation explicitly separates that from actually validating the logs, which requires a validation operation or equivalent implementation. Retain the verification result, coverage interval and file locations before asserting that an integrity check passed.

Source: CloudTrail integrity validation scope. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The enabled setting proves an integrity validation completed successfully.

Buyer evidence still required

  • Trail configuration and delivered log/digest identities.
  • Validation method, time interval and file locations.
  • Recorded verification outcome and any missing or invalid files.

Suggested review condition: Require an actual validation outcome before claiming validated integrity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Trail settings, digest identity, validator result and interval

Optional saved evidence: Save the difference between having integrity material and demonstrating a completed check.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudTrail: Cross-account event IDs need a shared-action join

Question: Can different CloudTrail eventIDs in two accounts describe the same cross-account action?

CloudTrail documents sharedEventID for an AWS action delivered to multiple accounts. Those records share sharedEventID while retaining distinct eventID and recipientAccountID values. The shared field is absent when caller and resource owner are the same account. Counting different eventIDs alone can therefore overstate cross-account actions.

Source: AWS CloudTrail: Event record contents. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Can different CloudTrail eventIDs in two accounts describe the same cross-account action?

Buyer evidence still required

  • The account-specific event records and their provenance.
  • The sharedEventID, eventID and recipientAccountID values where present.
  • The actual action, account relationship and any unmatched evidence.

Suggested review condition: Do not count account-specific records as separate actions solely because eventIDs differ, or treat missing sharedEventID as proof that no action occurred.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The account-specific event records and their provenance. The sharedEventID, eventID and recipientAccountID values where present. The actual action, account relationship and any unmatched evidence.

Optional saved evidence: An audit team reconciling agent activity across account boundaries needs to distinguish account-specific records from separate business actions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudTrail: File order is not execution order

Question: Can an agent reconstruct an action chain from the order of CloudTrail records in a file?

AWS states that CloudTrail log files are not an ordered stack trace and events do not appear in a specified order. Record position therefore does not establish the causal sequence of API actions.

Source: AWS CloudTrail: Working with CloudTrail events. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an agent reconstruct an action chain from the order of CloudTrail records in a file?

Buyer evidence still required

  • Original events and their identifiers.
  • Event timestamps and request or resource correlations.
  • Declared causal links and unresolved ordering ambiguity.

Suggested review condition: Use scope-matched correlation evidence; do not turn file position into a causal edge.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Relevant event identifiers, timestamps, resources and application correlation evidence.

Optional saved evidence: Can an agent reconstruct an action chain from the order of CloudTrail records in a file?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudTrail: Later records can correct earlier evidence

Question: Can a saved CloudTrail event be treated as the final record without considering later addenda?

CloudTrail addenda can explain delayed delivery or correct missing or incorrect fields. For updated data, the addendum identifies updated fields and original request and event IDs. A reconstruction should retain these links rather than counting a correction as an unrelated action.

Source: AWS CloudTrail: Record contents. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a saved CloudTrail event be treated as the final record without considering later addenda?

Buyer evidence still required

  • Original event and request IDs.
  • Applicable addenda and updated fields.
  • Collection cutoff and reconciliation history.

Suggested review condition: Preserve original evidence and linked corrections with their arrival context.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Event identity, addendum reason, corrected fields and collection cutoff.

Optional saved evidence: Can a saved CloudTrail event be treated as the final record without considering later addenda?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudTrail: Present events can omit large fields

Question: Does a CloudTrail event guarantee its full request and response fields were preserved?

CloudTrail documents field-size limits and truncation or omission rules, including requestParameters and responseElements. Limits differ for event data stores configured for larger event sizes. An event can remain present while material field content is absent.

Source: CloudTrail record contents for management, data, and network activity events - AWS CloudTrail. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a CloudTrail event guarantee its full request and response fields were preserved?

Buyer evidence still required

  • Event source and event-size configuration.
  • Field presence and truncation rules.
  • Independent request or response evidence.

Suggested review condition: Do not reconstruct missing parameters as empty or absent from the original request.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Event source and event-size configuration. Field presence and truncation rules. Independent request or response evidence.

Optional saved evidence: Assess whether a log supports reconstruction of the actual requested operation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Recovery of omitted content, complete logging or independent verification of an AWS action
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudTrail: Repeated records can represent one event

Question: Do repeated CloudTrail records necessarily mean an agent performed the action twice?

AWS documents that delivered CloudTrail logs can contain duplicate events, usually sharing the same eventID. A repeated record is therefore not by itself evidence of a repeated business action, and the identifier guidance is not an absolute deduplication guarantee.

Source: AWS CloudTrail: Getting and viewing log files. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Do repeated CloudTrail records necessarily mean an agent performed the action twice?

Buyer evidence still required

  • Repeated records with source-file provenance.
  • eventID values and relevant request details.
  • Deduplication rule and retained ambiguity.

Suggested review condition: Separate duplicate delivery from repeated execution before counting actions or asserting a retry.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Source files, event identifiers, action details and downstream counting rules.

Optional saved evidence: Do repeated CloudTrail records necessarily mean an agent performed the action twice?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CloudWatch masking: Old events and privileged reads

Question: Does enabling CloudWatch masking hide sensitive content in every stored log?

Data protection detects and masks matching data as it is ingested. Earlier log events are not masked by a newly applied policy, and principals with logs:Unmask can view unmasked content. This is a presentation and access-control boundary, not evidence that the original content was erased.

Source: CloudWatch Logs data protection. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A new masking policy removes sensitive content from all stored logs.

Buyer evidence still required

  • Policy activation time and managed identifiers.
  • Log ingestion dates and policy coverage.
  • Principals with unmask authority and retained copies.

Suggested review condition: Check historical events and privileged reads before accepting an all-logs redaction claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Log group, ingestion dates, data identifiers and unmask permissions.

Optional saved evidence: Preserve the difference between masked viewing, historical coverage and removal.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CodeQL: Build mode affects what analysis can establish

Question: Does a successful CodeQL run prove generated code and every dependency were analysed?

The Action README distinguishes no-build, automatic and manual build modes. It notes that no-build analysis can miss findings involving generated code or inaccessible dependencies. A successful run alone therefore cannot establish complete coverage; review language, build mode and extraction evidence for the actual repository.

Source: CodeQL build modes and analysis limitations. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A green scan proves complete coverage of the deployed code.

Buyer evidence still required

  • Analysis configuration, languages and exact versions.
  • Build/extraction evidence for generated code and dependencies.
  • The analysed revision compared with the deployed artifact.

Suggested review condition: Do not translate successful analysis into complete coverage or absence of vulnerabilities.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Build mode, dependency access, generated code and analysed revision.

Optional saved evidence: Save the coverage qualifications behind a supplier scan-evidence review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cohere Encrypted Vault: Content isolation and metadata visibility differ

Question: Does Model Vault Encrypted mean no information about a request is visible outside its enclave?

For the documented beta, Cohere distinguishes encrypted content from routing metadata, infrastructure metrics and network observations outside the trusted execution environment. Its confidentiality claims do not eliminate those metadata categories or establish independent certification. The buyer still needs the applicable threat model and deployment evidence.

Source: Cohere Model Vault Encrypted FAQ. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Encrypted inference hides every request-related fact from the operator.

Buyer evidence still required

  • Exact Encrypted Vault variant and beta terms.
  • Attestation and deployment evidence applicable to the buyer.
  • Metadata categories and threat-model acceptance for the workload.

Suggested review condition: Do not expand a content-confidentiality claim into universal invisibility or certification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Vault variant, beta terms, attestation, metadata and threat model

Optional saved evidence: Retain the distinction between protected content and observable metadata for a supplier review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cohere: Dataset storage is time-limited

Question: Can a Cohere Datasets API upload serve as the long-term evidence archive for an embedding job?

Cohere documents automatic dataset deletion 30 days after creation, with earlier manual deletion also available. Dataset availability is therefore time-limited and cannot be assumed to provide the buyer archive needed for later reconstruction.

Source: Cohere datasets. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Cohere Datasets API upload serve as the long-term evidence archive for an embedding job?

Buyer evidence still required

  • The dataset ID and creation time.
  • The required evidence-retention interval.
  • An authorised archive and its content references.

Suggested review condition: Do not rely on the provider dataset as the sole archive beyond its documented lifecycle.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The dataset ID and creation time. The required evidence-retention interval. An authorised archive and its content references.

Optional saved evidence: An embedding pipeline owner needs a separately governed evidence copy before the provider dataset expires.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Retention of all Cohere services or permission to archive third-party data
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cohere: Encrypted inference still exposes operational metadata

Question: Does Cohere Model Vault Encrypted hide all request metadata from infrastructure operators?

The Model Vault Encrypted FAQ distinguishes prompt and response content from metadata outside its trusted execution environment. Routing information, infrastructure metrics and network timing or volume can remain visible. Content confidentiality is not a claim that every observable signal disappears.

Source: Cohere Model Vault Encrypted FAQ. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Cohere Model Vault Encrypted hide all request metadata from infrastructure operators?

Buyer evidence still required

  • The specific Encrypted Vault deployment.
  • The categories of content and metadata in scope.
  • The buyer threat model and independent attestation review.

Suggested review condition: Do not approve an all-data invisibility claim from the content-confidentiality description alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The specific Encrypted Vault deployment. The categories of content and metadata in scope. The buyer threat model and independent attestation review.

Optional saved evidence: An AI buyer must decide whether permitted metadata exposure fits the threat model and supplier agreement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Independent validation of hardware, attestation or resistance to every side channel
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Coinbase: Recurring token allowance has a defined scope

Question: Does a Coinbase spend permission give an agent arbitrary control of the wallet?

Coinbase documents Spend Permissions as recurring native-token or ERC-20 spending delegated to a spender address. The manager checks spending against the approved allowance; the design does not authorise arbitrary external calls from the user account. Permission revocation is a separate onchain operation. A recurring allowance is not evidence of a one-time procurement approval.

Source: Coinbase: Spend Permissions. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Does a Coinbase spend permission give an agent arbitrary control of the wallet?

Buyer evidence still required

  • The account, spender, token, period and approved allowance.
  • The intended purchase and the authority granted outside the transfer mechanism.
  • The applicable permission approval, spend and revocation state.

Suggested review condition: Do not infer one-time purchase approval, arbitrary call authority or completed revocation from the presence of a spend-permission signature.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The account, spender, token, period and approved allowance. The intended purchase and the authority granted outside the transfer mechanism. The applicable permission approval, spend and revocation state.

Optional saved evidence: A wallet operator must distinguish a recurring transfer allowance from a particular purchase approval or unrestricted account authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Collected logs are not demonstrated protective monitoring

Question: Who analyses provider-side events and owns escalation and response beyond making audit logs available?

NCSC Principle 5.2 separates generating and collecting events from analysing them and taking appropriate action. It cautions that collection without effective analysis does not establish prompt detection and response. Review implication: Identify who analyses provider-side events and owns escalation/action. Event export or retention alone does not establish operational detection.

Source: NCSC Cloud Security Principle 5. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Who analyses provider-side events and owns escalation and response beyond making audit logs available?

Buyer evidence still required

  • Monitoring responsibility and scoped data sources
  • Analysis and escalation arrangements
  • Relevant dated evidence of review and response

Review inference: Identify who analyses provider-side events and owns escalation/action. Event export or retention alone does not establish operational detection.

Suggested review condition: No attack-detection rate, complete log coverage or effective security control is verified.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • NCSC cloud/supply-chain guidance, not a standalone statutory obligation. Apply only to the relevant supplier service and responsibility boundary; cited older standards are not asserted to be current.
  • No attack-detection rate, complete log coverage or effective security control is verified.
  • A provider may collect, analyse and respond effectively; an export feature alone neither establishes nor disproves that.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Collector memory limits and telemetry loss

Question: Can an OpenTelemetry Collector memory limiter refuse telemetry before durable storage?

The reviewed Collector memory-limiter implementation returns a non-permanent error when memory limits require refusal. The preceding component is expected to retry and may apply backpressure. Its documentation warns that telemetry is permanently lost if that component fails to retry correctly. Garbage collection is not a persistence acknowledgement.

Source: Memory Limiter Processor. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an OpenTelemetry Collector memory limiter refuse telemetry before durable storage?

Buyer evidence still required

  • Collector revision and pipeline order
  • Refusal and upstream retry evidence
  • Durable exporter or storage acknowledgement

Review inference: Check refusal handling through the pipeline before treating accepted application work as durably observed.

Suggested review condition: Do not infer complete telemetry from a running Collector or enabled memory limiter.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual loss, queue contents and upstream retry behaviour are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify audit gaps caused by pressure and incorrect retry handling.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed loss-free telemetry
  • Actual loss, queue contents and upstream retry behaviour are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Committed enablement versus collaborator-local installation bytes

Question: Does enabling a Claude Code plugin in committed project settings install identical local code for every collaborator?

The guide distinguishes project enablement from each collaborator's local installation, while cloud sessions do not load local settings in the same way.

Source: Anthropic primary documentation: claude code plugins. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does enabling a Claude Code plugin in committed project settings install identical local code for every collaborator?

Buyer evidence still required

  • project settings
  • marketplace/source reference
  • installed version/hash
  • collaborator/session scope

Review inference: Does enabling a Claude Code plugin in committed project settings install identical local code for every collaborator? Do not infer uniform installed bytes from committed enablement; capture each relevant installation identity and session type. Committed enablement versus collaborator-local installation bytes. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer uniform installed bytes from committed enablement; capture each relevant installation identity and session type.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Each collaborator still

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer uniform installed bytes from committed enablement; capture each relevant installation identity and session type.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Compensation: Recovery progress and residual effects

Question: Does completing a compensating workflow prove every original effect was reversed?

Microsoft architecture guidance describes compensation as application-specific recovery that must account for concurrent changes. It need not restore the starting state, can itself fail, and needs resumable progress and repeat-safe steps. Irreversible actions require explicit treatment. This is design guidance, not a guarantee for any Azure service or deployed workflow.

Source: Azure Architecture Center: Compensating Transaction pattern. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does completing a compensating workflow prove every original effect was reversed?

Buyer evidence still required

  • Original effects and operation-specific undo contracts.
  • Compensation attempts, failures and concurrent changes.
  • Residual or irreversible effects, responsible owner and closure evidence.

Suggested review condition: Decline full-restoration claims without per-effect reconciliation; keep failed or irreversible steps explicitly unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Original effects and operation-specific undo contracts. Compensation attempts, failures and concurrent changes. Residual or irreversible effects, responsible owner and closure evidence.

Optional saved evidence: An operator needs to know which effects remain before closing a failed multi-service action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A universal undo mechanism, tested compensation implementation or automatic restoration of permissions
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Confidentiality needs a people-access boundary

Question: What evidence covers persons authorised to process personal data for a UK processor?

UK Article 28(3)(b) requires the processor contract to ensure persons authorised to process personal data have committed to confidentiality or are subject to an appropriate statutory confidentiality obligation. Review implication: A service privacy page alone does not establish the commitment or statutory obligation for each relevant personnel category. This is not staff vetting or an effective-access test.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What evidence covers persons authorised to process personal data for a UK processor?

Buyer evidence still required

  • Authorised personnel categories
  • Applicable commitment or statutory obligation
  • Processor contractual clause

Review inference: A service privacy page alone does not establish the commitment or statutory obligation for each relevant personnel category. This is not staff vetting or an effective-access test.

Suggested review condition: No staff vetting, actual compliance or access-control enforcement is verified.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No staff vetting, actual compliance or access-control enforcement is verified.
  • An appropriate statutory confidentiality obligation may be relevant without a separate individual promise; its applicability must be evidenced.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Confluence exports: Format and exporter identity change coverage

Question: Can a Confluence PDF or HTML export stand in for a complete space backup?

Export formats preserve different content. PDF omits comments; HTML has additional exclusions, and Team Calendars are not included. Visibility and administrator exceptions also affect coverage. Record the format and exporter identity instead of assuming every space export is a complete archival copy.

Source: Confluence Cloud export formats. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: All Confluence space export formats preserve the same evidence.

Buyer evidence still required

  • Format and selected content.
  • Exporter role and visibility.
  • Comments, calendars and unpublished-content inventory.

Suggested review condition: Require format-specific coverage before claiming archive completeness.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Export format, selected objects, exporter identity and import destination

Optional saved evidence: Retain the coverage limitations behind a knowledge-system retention or exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Confluent MCP: Regional access and client-controlled confirmation

Question: Can an agent assume Confluent MCP cannot change streaming resources?

Most documented operations read data, but connector restart/configuration and Flink statement changes are available. Global and regional endpoints accept different key types. Mutation confirmation is presented through the client, whose auto-approval may bypass a visible prompt. Credential permissions remain decisive.

Source: Confluent Cloud managed MCP servers. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Global and regional hosted servers

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Confluent operates the managed servers.

Documented by publisher. Confluent Cloud managed MCP servers

Purpose

Inspect streaming resources and perform selected operations.

Documented by publisher. Confluent Cloud managed MCP servers

Read capability

Clusters, topics, messages, schemas and metrics as permitted.

Documented by publisher. Confluent Cloud managed MCP servers

Write capability

Connector restart/configuration and Flink statement changes.

Documented by publisher. Confluent Cloud managed MCP servers

Authentication

HTTP Basic credentials using supported API-key types.

Documented by publisher. Confluent Cloud managed MCP servers

Permission surface

Key organization, resource permissions and endpoint scope.

Documented by publisher. Confluent Cloud managed MCP servers

Data leaving the environment

Streaming content and diagnostics reach the agent.

Review inference. Confluent Cloud managed MCP servers

Failure modes to consider

Wrong region, unsupported key or automatic approval can affect execution.

Review inference. Confluent Cloud managed MCP servers

Unknowns and applicability

Buyer RBAC, network topology and client approval policy are unknown.

Not established

Suggested refusal or clarification condition

Require exact change authority; do not rely on a prompt alone.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Endpoint support, mutating tools, confirmation behaviour and private connectivity.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the exact streaming operation, credential boundary and approval evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Consumer Binding V1: Runtime deployment boundary

Question: Does Consumer Binding V1 establish public runtime deployment?

The Consumer Binding V1 source supports interface discipline and consumer matching. It excludes public runtime deployment.

Derived from BDAS Consumer Binding V1 — Contract Binding Check. No new experiment or validation is claimed.

Claim boundaries
  • public runtime deployment
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Content-and-session identity bounds ingestion deduplication

Question: Does retrying Cloudflare memory ingestion always preserve the same message identity?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta design derives message IDs from content and session and can derive an omitted session ID from the conversation. Its deduplication therefore depends on those inputs.

Source: Cloudflare primary documentation: cloudflare memory how. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does retrying Cloudflare memory ingestion always preserve the same message identity?

Buyer evidence still required

  • message content hash
  • session mapping
  • retry inputs
  • ingestion responses
  • resulting inventory

Review inference: Does retrying Cloudflare memory ingestion always preserve the same message identity? Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation. Content-and-session identity bounds ingestion deduplication. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Messages are content-addressed

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not generalise retry deduplication across changed content or session mapping; retain the original input identity and returned memory references. Private beta access and current feature applicability require separate confirmation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Contentful MCP: Protected environments are an opt-in connector guard

Question: Does the Contentful MCP environment guard block every possible write?

The local server documents an opt-in, case-sensitive environment guard. It blocks environment-scoped write/delete calls but leaves reads and specified organisation-level or generation operations outside that guard. Other clients are unaffected. Review both the guard and underlying permissions before treating an environment as protected.

Source: Contentful local MCP environment guard. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official local Contentful MCP for the Management API

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Contentful publishes the local Management API server.

Documented by publisher. Contentful local MCP environment guard

Purpose

Manage content, assets and content models.

Documented by publisher. Contentful local MCP environment guard

Read capability

Entries, assets, models and version information.

Documented by publisher. Contentful local MCP environment guard

Write capability

Content creation, editing, publication and other management operations.

Documented by publisher. Contentful local MCP environment guard

Authentication

Contentful Management API personal access token.

Documented by publisher. Contentful local MCP environment guard

Permission surface

Optional protected-environment list complements role-based permissions.

Documented by publisher. Contentful local MCP environment guard

Data leaving the environment

Content and exports can reach the agent or local output files.

Review inference. Contentful local MCP environment guard

Failure modes to consider

Unset or differently capitalised environment IDs can defeat the intended guard.

Review inference. Contentful local MCP environment guard

Unknowns and applicability

Buyer roles and protection settings have not been verified.

Not established

Suggested refusal or clarification condition

Do not claim universal write prevention from the connector guard.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Guard coverage, default environment and organisation-scoped tools.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the exact scope and exceptions of a protected-environment approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Contentstack MCP: Delivery reads versus management and automation

Question: Does connecting a content delivery tool also enable publishing or deployments?

Contentstack separates delivery, management, automation and deployment tool groups. Delivery retrieves published content, while other groups expose state-changing operations and use different credentials. Review the loaded groups and corresponding credentials; a content-oriented connector name does not establish a read-only surface.

Source: Contentstack MCP product tool groups. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Local Contentstack MCP with selectable product groups

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Contentstack publishes the local server.

Documented by publisher. Contentstack MCP product tool groups

Purpose

Content delivery and selected Contentstack product operations.

Documented by publisher. Contentstack MCP product tool groups

Read capability

Published content, management data or analytics according to loaded groups.

Documented by publisher. Contentstack MCP product tool groups

Write capability

Management, automation and deployment groups include changes.

Documented by publisher. Contentstack MCP product tool groups

Authentication

OAuth and product-specific tokens; delivery and management use different credentials.

Documented by publisher. Contentstack MCP product tool groups

Permission surface

Group selection controls tools; credential and target scope also matter.

Documented by publisher. Contentstack MCP product tool groups

Data leaving the environment

Content and product information can reach the model.

Review inference. Contentstack MCP product tool groups

Failure modes to consider

Loading all groups can expose actions beyond content lookup.

Review inference. Contentstack MCP product tool groups

Unknowns and applicability

Buyer token scope, region and group selection are unknown.

Not established

Suggested refusal or clarification condition

Confirm publishing, automation and deployment authority separately from reading.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Group membership, authentication methods and endpoint overrides.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the approved product groups and the distinction between content delivery and operational changes.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Copilot connectors: Pausing or hiding content is not deletion

Question: Does pausing a Copilot connector or hiding it from search remove its indexed data?

Microsoft documents that pausing connector crawls leaves existing data searchable. Turning off Copilot visibility excludes the connection from Copilot Search and Chat results but can leave crawling active. A failed connection deletion can leave indexed data, quota usage or crawls in place. These controls are distinct from verified data removal.

Source: Microsoft 365 Copilot: Manage connectors. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Enterprise AI Data Custody & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does pausing a Copilot connector or hiding it from search remove its indexed data?

Buyer evidence still required

  • The exact connection, source type and indexed-data scope.
  • The crawl, visibility and deletion states with their effective times.
  • The deletion result and reconciliation of remaining indexed content.

Suggested review condition: Do not close a deletion or offboarding claim from paused or hidden status, or while a delete-failed state is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The exact connection, source type and indexed-data scope. The crawl, visibility and deletion states with their effective times. The deletion result and reconciliation of remaining indexed content.

Optional saved evidence: An enterprise operator disconnecting a knowledge source must distinguish refresh suspension, presentation controls and deletion completion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Copilot Pages: OneDrive collection omits the separate Embedded container

Question: Does selecting a user's OneDrive for eDiscovery include their Copilot Pages and Notebooks?

Microsoft states that selecting a user's OneDrive does not include their Copilot Pages or Notebooks in the user-owned SharePoint Embedded container; that container must be included separately. A message containing a Page link and the linked Page are separate eDiscovery items. Under a Page hold, version limits are ignored and versions are retained until the hold is released.

Source: Microsoft: eDiscovery with Copilot Pages. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Enterprise AI Data Custody & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does selecting a user's OneDrive for eDiscovery include their Copilot Pages and Notebooks?

Buyer evidence still required

  • The user-owned Embedded container and any other Page storage locations.
  • The message, linked Page and Notebook inventories and collection scope.
  • The applicable holds, retained versions and export reconciliation.

Suggested review condition: Do not claim complete AI-workspace collection from OneDrive or message links alone; hold decisions remain with the responsible records owner.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The user-owned Embedded container and any other Page storage locations. The message, linked Page and Notebook inventories and collection scope. The applicable holds, retained versions and export reconciliation.

Optional saved evidence: An enterprise exit or investigation owner needs the actual AI document storage locations and retained versions in the collection scope.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Copilot Studio: Disabling transcript saving leaves residual data

Question: Does disabling Copilot Studio transcript saving erase existing conversations and every stored copy?

The control stops future Dataverse transcript saving, with possible writes for up to 24 hours after it is disabled. Existing transcripts require separate handling. Copilot Studio also temporarily retains session information for up to 28 days independently of the Dataverse control.

Source: Copilot Studio transcript controls. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does disabling Copilot Studio transcript saving erase existing conversations and every stored copy?

Buyer evidence still required

  • The environment and transcript-saving setting change time.
  • Existing Dataverse records and configured retention.
  • The separate Copilot Studio session-storage boundary.

Suggested review condition: Do not report complete erasure from the saving toggle while existing records, delayed writes or separate storage remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The environment and transcript-saving setting change time. Existing Dataverse records and configured retention. The separate Copilot Studio session-storage boundary.

Optional saved evidence: An agent operator needs separate evidence for collection shutdown and removal of previously retained conversations.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Immediate deletion or complete control of every Microsoft Copilot product
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Copilot Studio: Publish readiness is not a universal policy verdict

Question: Does an enabled Publish button prove every Copilot Studio agent channel has passed data-policy checks?

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: Copilot Studio agent publication. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an enabled Publish button prove every Copilot Studio agent channel has passed data-policy checks?

Buyer evidence still required

  • The documented agent experience and enabled channels.
  • The publish-dialog policy results by channel.
  • Separate distribution and connector-access configuration.

Suggested review condition: Do not treat publish availability as a complete data-policy pass or authority to use a blocked endpoint.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The documented agent experience and enabled channels. The publish-dialog policy results by channel. Separate distribution and connector-access configuration.

Optional saved evidence: An agent release owner needs channel-specific policy evidence before making a deployment approval claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • 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

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Copilot Studio: Session CSV is a limited export

Question: Can a Copilot Studio session CSV establish the complete text of every agent response?

The documented CSV contains a subset of session information from the past 28 days. Each bot response in ChatTranscript is limited to its first 512 characters. A downloaded CSV therefore cannot establish complete long responses or an unrestricted conversation archive.

Source: Copilot Studio transcript downloads. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Copilot Studio session CSV establish the complete text of every agent response?

Buyer evidence still required

  • The export interval and selected sessions.
  • Response lengths and the CSV fields received.
  • A separately reviewed source for complete required activities.

Suggested review condition: Refuse a complete-transcript claim when required responses exceed the CSV limit or fall outside its available interval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The export interval and selected sessions. Response lengths and the CSV fields received. A separately reviewed source for complete required activities.

Optional saved evidence: An investigation owner must know whether the exported transcript preserves the full statements used as evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Completeness of alternative Power Apps exports or unsupported agent types
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Copilot: Conversation deletion does not delete associated memory

Question: Does deleting a Copilot conversation through eDiscovery also delete its associated memory?

Microsoft documents Copilot memories as IPM.Contact items and states that deleting a conversation or message through Purview or eDiscovery does not delete the associated memory. Memories need their own identification and deletion scope. Conversation deletion is therefore insufficient evidence of complete removal of the related AI memory.

Source: Microsoft Purview: Search for and delete AI application data. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Enterprise AI Data Custody & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a Copilot conversation through eDiscovery also delete its associated memory?

Buyer evidence still required

  • The target conversations and associated memory inventory.
  • The memory search scope, item class and authorised deletion evidence.
  • The applicable retention or hold constraints and remaining-data review.

Suggested review condition: Do not claim that associated memories were removed solely because the conversation was deleted; refer unresolved hold obligations to the responsible owner.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The target conversations and associated memory inventory. The memory search scope, item class and authorised deletion evidence. The applicable retention or hold constraints and remaining-data review.

Optional saved evidence: An enterprise data owner responding to an AI deletion request needs to identify derived memory as a separate retained item class.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Corpus 7001071: Recovery versus performance

Question: Does recovering corpus 7001071 establish a new performance result?

The public source records recovery of a frozen corpus tranche. It excludes a new performance claim.

Derived from BDAS 7001071 — Recovered INDEX Corpus Tranche. No new experiment or validation is claimed.

Claim boundaries
  • new performance claim
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cosign annotation verification subset semantics

Question: Does verifying specified Cosign annotations reject an attestation or signature that contains additional annotations?

Cosign’s verification documentation says each requested annotation must match. Additional annotations are permitted, so matching selected key/value pairs establishes a required subset rather than exact equality with a complete allowed annotation set.

Source: Sigstore: Verifying signatures. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does verifying specified Cosign annotations reject an attestation or signature that contains additional annotations?

Buyer evidence still required

  • Expected annotation constraints
  • Full observed annotation set
  • Artifact identity
  • Explicit policy on extra keys

Review inference: Review cosign annotation verification subset semantics before accepting the buyer claim. The existing review checks expected signer and digest; this question isolates subset matching versus exact metadata policy without changing those requirements. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: If policy forbids additional keys, obtain a separate complete-set comparison. Do not describe successful requested-key checks as exact annotation-schema enforcement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Verify Annotations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • If policy forbids additional keys, obtain a separate complete-set comparison. Do not describe successful requested-key checks as exact annotation-schema enforcement.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Cosign verification: Expected signer and artifact

Question: Does any valid Cosign signature establish the supplier artifact we intended to accept?

Identity-based verification checks the expected certificate identity and OIDC issuer. Container verification normally checks the signed image digest; disabling claim checks changes what is established. A cryptographically valid signature without the intended identity and artifact binding is insufficient for the buyer acceptance decision.

Source: Cosign verifying signatures. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Any valid signature is enough to accept an artifact as the intended supplier release.

Buyer evidence still required

  • Expected signer identity and issuer.
  • Artifact digest and signed payload.
  • Verification flags and policy result.

Suggested review condition: Require the intended signer and artifact binding; do not treat signature validity as a safety assessment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Artifact identity, expected signer, issuer, bundle and verification options.

Optional saved evidence: Save the acceptance criteria and source version behind an artifact-origin review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cosmos DB TTL: Hidden from queries before deletion

Question: Does an expired Cosmos DB item disappear physically as soon as queries stop returning it?

Expired items stop appearing in query responses immediately, while background deletion can wait for resources. TTL is measured from the last modification, and item-level values depend on container TTL being enabled. Query absence is therefore not proof of completed physical deletion or deletion from other stores.

Source: Cosmos DB item expiry. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: No query result proves immediate complete data erasure.

Buyer evidence still required

  • Container and item TTL configuration.
  • Last-modified time and deletion evidence.
  • Throughput mode and separately retained data.

Suggested review condition: Keep query invisibility separate from completed deletion and wider retention claims.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Container TTL, item override, last modification, throughput mode and retained copies.

Optional saved evidence: Retain the exact lifecycle boundary behind a data-retention procurement decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Couchbase MCP: Read-only mode and database credentials

Question: Does Couchbase MCP always allow an agent to modify documents?

The documented configuration defaults to read-only mode, with additional tool disabling. The wider tool inventory includes document mutations and queries, so the effective setting matters. Database authentication supports username/password or client certificates; when both are supplied, the certificate path takes precedence.

Source: Couchbase MCP server overview. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Self-hosted server for Capella or self-managed clusters

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Couchbase publishes the server; the buyer runs it.

Documented by publisher. Couchbase MCP server overview; Couchbase MCP configuration

Purpose

Inspect cluster data, schemas and query performance.

Documented by publisher. Couchbase MCP server overview; Couchbase MCP configuration

Read capability

Authorized documents, metadata and diagnostic results.

Documented by publisher. Couchbase MCP server overview; Couchbase MCP configuration

Write capability

Document mutations exist when permitted by configuration.

Documented by publisher. Couchbase MCP server overview; Couchbase MCP configuration

Authentication

Database credentials or client-certificate authentication.

Documented by publisher. Couchbase MCP server overview; Couchbase MCP configuration

Permission surface

Read-only setting, disabled tools and database roles.

Documented by publisher. Couchbase MCP server overview; Couchbase MCP configuration

Data leaving the environment

Query and document results reach the local server and client.

Review inference. Couchbase MCP server overview; Couchbase MCP configuration

Failure modes to consider

Configuration drift can expose writes or use an unexpected identity.

Review inference. Couchbase MCP server overview; Couchbase MCP configuration

Unknowns and applicability

Actual flags, roles, mounts and client retention are not verified.

Not established

Suggested refusal or clarification condition

Require the effective configuration before promising read-only access.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Read-only defaults, authentication precedence, tool list and support terms.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the reviewed configuration conditions behind a read-only approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Coupa approval objects and decision scope

Question: Does an approved Coupa document establish authority for a later purchase-order change?

Coupa’s Approvals API binds an approval to an approvable object and type, an approval chain, status and approver information. Approve and reject actions require a Pending approval. Purchase-order changes have their own operations and approval handling. A past approval record therefore does not, by itself, identify approval for a changed order.

Source: Approvals API (/approvals) | Coupa. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an approved Coupa document establish authority for a later purchase-order change?

Buyer evidence still required

  • Current order and change identifiers
  • Approval chain, status and approver/delegate evidence
  • Applicable limits and revision approval policy

Review inference: Reconcile the approval object and current change with the buyer’s approval rules.

Suggested review condition: Do not reuse a historical approval as evidence for a changed purchase without matching scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s approval limits and effective workflow are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent an agent from treating an earlier approval as open-ended purchasing authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Legal authority to increase spending from an API record alone
  • The buyer’s approval limits and effective workflow are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Coupa external payment and tracking handoff

Question: Does pay_externally in Coupa independently verify an external payment?

The action marks an invoice payable paid and stops Coupa tracking. Separate actions stop or restart tracking without representing payment verification.

Source: Coupa: Payables Invoices API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does pay_externally in Coupa independently verify an external payment?

Buyer evidence still required

  • Payable identity
  • Invoked handoff action
  • External payment and reconciliation evidence

Review inference: Review coupa external payment and tracking handoff before accepting the buyer claim. Peppol status messaging does not define Coupa state mutations. This decision distinguishes externally asserted payment from the responsibility to track it. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Require independent payment evidence before relying on a mark-paid action. A tracking handoff is not a bank confirmation or continuing monitoring guarantee.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Actions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require independent payment evidence before relying on a mark-paid action. A tracking handoff is not a bank confirmation or continuing monitoring guarantee.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Coupa invoice approval and bypass provenance

Question: Does approved Coupa invoice status prove each configured approver reviewed it?

The invoice API documents actions that bypass all approvals or the current approval. Status alone therefore does not establish which reviewers acted.

Source: Coupa: Invoices API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does approved Coupa invoice status prove each configured approver reviewed it?

Buyer evidence still required

  • Invoice revision
  • Approval and bypass action history
  • Buyer approval policy

Review inference: Review coupa invoice approval and bypass provenance before accepting the buyer claim. The existing review binds approval to an object state; this decision asks whether that state arose through the expected reviewers or an explicit bypass. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Require reviewer and action evidence for a claim of independent approval; neither status nor API availability grants authority to bypass controls.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Actions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require reviewer and action evidence for a claim of independent approval; neither status nor API availability grants authority to bypass controls.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Coupa invoice creation and approval submission

Question: Does creating a Coupa invoice through the API submit it for approval?

The documented create action makes a draft invoice. A separate submit action sends a draft for approval.

Source: Coupa: Invoices API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does creating a Coupa invoice through the API submit it for approval?

Buyer evidence still required

  • Created invoice ID and status
  • Submission action result
  • Subsequent approval evidence

Review inference: Review coupa invoice creation and approval submission before accepting the buyer claim. Requisition approval does not define invoice creation. This question checks the separate draft-to-submitted transition for supplier invoices. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not count a created draft as submitted, approved or payable without evidence of those later stages.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Actions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not count a created draft as submitted, approved or payable without evidence of those later stages.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Coupa modified invoices and restarted approval chains

Question: Can an earlier Coupa invoice approval chain be reused after restart_approvals?

The documented restart action clears the current chain and generates a new chain for a modified invoice.

Source: Coupa: Invoices API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an earlier Coupa invoice approval chain be reused after restart_approvals?

Buyer evidence still required

  • Invoice before and after modification
  • Restart action
  • New approval-chain evidence

Review inference: Review coupa modified invoices and restarted approval chains before accepting the buyer claim. This adds the documented chain-replacement action and the evidence needed to reconstruct the current chain, beyond generic object-state binding. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not apply an earlier chain to the amended invoice without reconciling its replacement and current decisions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Actions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not apply an earlier chain to the amended invoice without reconciling its replacement and current decisions.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Coupa order transmission and supplier acknowledgement

Question: Does a sent Coupa purchase order establish supplier acknowledgement or completed confirmation?

Coupa exposes separate transmission, acknowledgement and confirmation fields. A sent transmission is not the same field as supplier acknowledgement or completed confirmation.

Source: Coupa: Purchase Orders API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a sent Coupa purchase order establish supplier acknowledgement or completed confirmation?

Buyer evidence still required

  • Order identity and revision
  • Transmission status
  • Acknowledgement and confirmation records

Review inference: Review coupa order transmission and supplier acknowledgement before accepting the buyer claim. The prior review covers version and export synchronization; this decision reconciles distinct supplier communication stages before relying on an order. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Require the stage-specific record before treating an order as acknowledged, confirmed or fulfilled. Transport status does not establish goods receipt.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Elements

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the stage-specific record before treating an order as acknowledged, confirmed or fulfilled. Transport status does not establish goods receipt.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Coupa payment details and invoice allocation

Question: Can a Coupa payment header total be assigned to one invoice without inspecting payment-details?

The API documents payment-detail rows with invoice identifiers, invoice references, payment amounts and currencies.

Source: Coupa: Payments API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a Coupa payment header total be assigned to one invoice without inspecting payment-details?

Buyer evidence still required

  • Payment ID and detail rows
  • Invoice IDs and references
  • Amounts and currencies

Review inference: Review coupa payment details and invoice allocation before accepting the buyer claim. Existing order and despatch binding does not identify invoice allocations within Coupa payment details; the new decision needs invoice-level payment amounts. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Reconcile the detail population before allocating a total. These fields do not establish complete allocation, matching tolerances or final settlement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Elements;Key Data Elements

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile the detail population before allocating a total. These fields do not establish complete allocation, matching tolerances or final settlement.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Coupa payment export and accounting acknowledgement

Question: Does marking a Coupa Pay payment exported prove the supplier was paid?

The Payments API uses exported as an integration marker and separately exposes payment status. Its PUT operation is limited to marking export.

Source: Coupa: Payments API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does marking a Coupa Pay payment exported prove the supplier was paid?

Buyer evidence still required

  • Payment ID and status
  • Export acknowledgement
  • Independent provider or bank outcome

Review inference: Review coupa payment export and accounting acknowledgement before accepting the buyer claim. The prior order-export review does not define payment export. This captured payment contract resolves the narrow previously deferred export-versus-outcome question. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Treat export as an accounting handoff marker. Do not infer settlement, exactly-once ERP posting or supplier receipt from that flag.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Overview;Elements

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Treat export as an accounting handoff marker. Do not infer settlement, exactly-once ERP posting or supplier receipt from that flag.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Coupa payment status changes after an export

Question: Does an export-once Coupa payment extract prove later payment status changes were captured?

The documented extraction guidance uses updated-at to capture payment status changes; exported separately indicates a previous integration export.

Source: Coupa: Payments API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an export-once Coupa payment extract prove later payment status changes were captured?

Buyer evidence still required

  • Export checkpoint
  • Update-time query and overlap policy
  • Payment IDs and later statuses

Review inference: Review coupa payment status changes after an export before accepting the buyer claim. The prior purchase-order decision checks supplier versions; this one asks whether an incremental payment extract observes later outcome changes. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not declare status coverage from an export flag alone. Verify update coverage, pagination and deduplication in the actual integration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Overview;Elements

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not declare status coverage from an export flag alone. Verify update coverage, pagination and deduplication in the actual integration.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Coupa purchase-order revision reconciliation

Question: Does an unchanged Coupa purchase-order version prove no order data changed before ERP synchronization?

Coupa documents that not every PO change increments the supplier version; updated-at can identify changes. Edits that create a new version and resend reset exported to false. For ERP revisions, the change API guide directs integrations to the PO GET API with exported=false and version, rather than treating change-request retrieval as the revision feed.

Source: Purchase Orders API (/purchase_orders) | Coupa. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an unchanged Coupa purchase-order version prove no order data changed before ERP synchronization?

Buyer evidence still required

  • Order ID, updated-at and supplier version
  • Exported flag and ERP acknowledgement
  • Change request and resend evidence where applicable

Review inference: Reconcile update time, supplier version and export state using the intended integration path.

Suggested review condition: Do not treat version equality alone as unchanged order content or completed ERP synchronization.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Supplier receipt and the buyer ERP’s accepted state are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid sending stale or duplicated purchasing instructions downstream.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Confirmation that a supplier accepted revised contractual instructions
  • Supplier receipt and the buyer ERP’s accepted state are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Coupa requisition submission and approval completion

Question: Does submitting a Coupa requisition through the API establish that its approval chain completed?

Coupa documents a submit_for_approval requisition action separately from approval actions and approval status. The Approvals API exposes the approvable object, chain, approver and status, with Pending required for approve or reject. Submission starts the relevant approval workflow; it is not evidence that every required approval has occurred.

Source: Special Actions and API Notes | Coupa. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does submitting a Coupa requisition through the API establish that its approval chain completed?

Buyer evidence still required

  • Submitted requisition identifier and response
  • Current approval-chain states
  • Required approvers and buyer workflow configuration

Review inference: Check the resulting requisition and approval chain before committing dependent purchasing steps.

Suggested review condition: Refuse completed-approval claims based solely on requisition submission.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual configured chain and subsequent decisions remain unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep an automated procurement workflow from advancing before approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic bypass of buyer approval requirements
  • The actual configured chain and subsequent decisions remain unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CronJob: Schedule intent and actual job execution

Question: Does a Kubernetes CronJob guarantee exactly one run for each scheduled time?

CronJob scheduling can create duplicate jobs or miss a run in some circumstances; jobs should be designed for idempotent work. Its concurrency policy applies only to jobs from the same CronJob. It does not coordinate another CronJob or prove that a scheduled business operation completed.

Source: Kubernetes CronJob delivery and concurrency. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A CronJob schedule guarantees one completed operation per interval.

Buyer evidence still required

  • Schedule, timezone, deadline and suspension settings.
  • Concurrency policy and other job producers.
  • Job outcomes and business-operation reconciliation.

Suggested review condition: Check actual jobs and business results instead of inferring completion from the schedule.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. CronJob identity, schedule, timezone, deadlines, concurrency and downstream result identity.

Optional saved evidence: Preserve the distinction between schedule configuration and verified task completion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cross-project artifacts: Successful history and current builds

Question: Does GitLab needs:project wait for the current upstream pipeline before downloading its artifact?

needs:project retrieves artifacts from the latest successful specified job for the selected ref. It does not wait for an already-running pipeline on that ref. A consumer can therefore receive an earlier successful result. Record the producing job, commit and digest before equating that artifact with the current release.

Source: GitLab CI/CD YAML: needs:project. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A cross-project dependency always retrieves the current upstream build.

Buyer evidence still required

  • Project, job and ref used for retrieval.
  • Actual producer job and commit identity.
  • Artifact digest compared with the release expectation.

Suggested review condition: Require producer identity reconciliation before accepting a cross-project artifact as the current build.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Project, job, ref, actual producer run, source commit, entitlement and digest.

Optional saved evidence: Preserve the source-to-artifact binding used to approve an external pipeline result.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CVSS: Safety context

Question: Does an omitted CVSS Safety value mean there are no safety impacts?

CVSS v4.0 includes safety-related context. An omitted Supplemental Safety assessment does not establish absence of safety impacts; deployment-specific consequences require separate assessment.

Source: CVSS v4.0 Specification. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • absence of human safety impact
  • industrial safety certification
  • safe deployment from a missing metric

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CVSS: Score traceability

Question: What does a CVSS vector add to a published score?

A CVSS vector records the metric choices behind a score. FIRST's publication guidance calls for both score and vector; this makes the assessment inspectable without proving its inputs correct.

Source: CVSS v4.0 Specification. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • correct metric selection
  • independent scoring validation
  • complete risk evidence

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CVSS: Severity and context

Question: Can a CVSS score alone determine a buyer's operational risk?

CVSS v4.0 separates Base, Threat, Environmental and Supplemental metrics. Supplemental values add context without changing the score; a severity score alone does not establish local risk.

Source: CVSS v4.0 Specification. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • complete business risk assessment
  • automatic remediation priority
  • deployment safety

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Cyber controls depend on the contract risk

Question: Must every public-sector MCP supplier hold Cyber Essentials regardless of the contract?

PPN 014 requires relevant, proportionate cyber controls and rejects a blanket approach. Where relevant, suppliers without Cyber Essentials or Cyber Essentials Plus must demonstrate equivalent controls. G-Cloud inclusion does not remove the buyer call-off cyber-risk review. Review implication: Record the contract-specific risk decision and supporting evidence. A missing badge alone is not a universal exclusion rule, and framework presence is not complete award assurance.

Source: Cabinet Office PPN 014. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Must every public-sector MCP supplier hold Cyber Essentials regardless of the contract?

Buyer evidence still required

  • Authority and procurement scope
  • Contract data/access characteristics
  • Risk assessment and evidence of required or equivalent controls

Review inference: Record the contract-specific risk decision and supporting evidence. A missing badge alone is not a universal exclusion rule, and framework presence is not complete award assurance.

Suggested review condition: Do not assert all public or private contracts require certification or treat an unsupported equivalence claim as evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK central government departments, executive agencies and non-departmental public bodies and NHS bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • Do not assert all public or private contracts require certification or treat an unsupported equivalence claim as evidence.
  • A relevant higher-risk contract may properly require certification or equivalent controls; proportionality does not mean controls are optional everywhere.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

CycloneDX: Document revision traceability

Question: What do CycloneDX serial numbers and BOM versions establish?

CycloneDX 1.7 recommends unique serial numbers and increasing a BOM's version when it is modified. These identify document revisions; they do not prove the truth of a revised inventory.

Source: CycloneDX 1.7 official JSON schema. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • verified inventory changes
  • authenticity from identifiers alone
  • unchanged software from a document version

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CycloneDX: Evidence behind a not-affected assessment

Question: What should accompany a CycloneDX not_affected vulnerability assessment?

CycloneDX 1.7 distinguishes not_affected, in_triage, false_positive and resolved analysis states. It recommends justification for not_affected and details explaining why the component or service is not impacted. The analysis can carry issue and update times. A valid status field alone does not establish that its rationale applies to the deployed artifact.

Source: CycloneDX 1.7 JSON schema: Impact analysis. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • verified buyer-deployment applicability
  • absence of other vulnerabilities
  • authority to suppress an alert without review

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CycloneDX: Inventory relationship scope

Question: Can CycloneDX represent service and dependency relationships as well as components?

CycloneDX can describe components, services and dependency relationships. Representation support does not establish that a supplied BOM captures every direct or transitive relationship.

Source: CycloneDX Specification Overview. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • complete dependency graph
  • verified service boundary
  • automatic discovery of every component

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

CycloneDX: Schema identification

Question: Do CycloneDX format and version fields establish that a BOM is complete?

CycloneDX 1.7 defines format and specification-version identifiers. They identify the declared representation; completeness and correctness of the described inventory require separate evidence.

Source: CycloneDX 1.7 official JSON schema. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • complete dependency inventory
  • accurate component data
  • safe software from schema fields

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

D1 Time Travel: Restore replaces the database in place

Question: Can an agent use D1 Time Travel as a read-only way to inspect a past database?

The documented restore overwrites the database in place and cancels in-flight queries. It returns a prior bookmark for reversal, subject to the available history window. This operation is not a clone or a read-only historical query; restoration authority and preservation of the recovery bookmark are separate requirements.

Source: Cloudflare D1 Time Travel recovery. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Time Travel restore is non-destructive inspection of an independent copy.

Buyer evidence still required

  • Database identity and requested timestamp or bookmark.
  • Plan-dependent history window and authority to replace current state.
  • Prior bookmark retention and post-restore verification.

Suggested review condition: Require explicit restoration authority before replacing the database.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Database identity, bookmark, plan window and restoration authority

Optional saved evidence: Save the identity, replacement and reversal conditions behind a recovery action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Dagster+ MCP: Regional target and effective roles

Question: Does installing the Dagster plugin establish the correct deployment access?

The plugin bundles guidance with a separately authenticated Dagster+ MCP connection. Publisher documentation describes both information access and actions. Region selection matters, and deployment roles govern access; Pro overrides can add permissions rather than subtract the deployment role. Plugin installation alone does not prove the selected identity, region or effective grants.

Source: Dagster plugin and MCP authentication. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; deployed buyer configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Dagster Labs provides the Dagster+ service and plugin.

Documented by publisher. Dagster plugin and MCP authentication; Dagster AI tools and MCP capabilities; Dagster Plus roles and enforcement

Purpose

Give agents context and actions for Dagster+ deployments.

Documented by publisher. Dagster plugin and MCP authentication; Dagster AI tools and MCP capabilities; Dagster Plus roles and enforcement

Read capability

Deployment information exposed by the connected service.

Documented by publisher. Dagster plugin and MCP authentication; Dagster AI tools and MCP capabilities; Dagster Plus roles and enforcement

Write capability

Publisher guidance describes actions; inspect the actual tool list before execution.

Review inference. Dagster plugin and MCP authentication; Dagster AI tools and MCP capabilities; Dagster Plus roles and enforcement

Authentication

Account authentication through the connected MCP client.

Documented by publisher. Dagster plugin and MCP authentication; Dagster AI tools and MCP capabilities; Dagster Plus roles and enforcement

Permission surface

Organization and deployment roles, including applicable overrides.

Documented by publisher. Dagster plugin and MCP authentication; Dagster AI tools and MCP capabilities; Dagster Plus roles and enforcement

Data leaving the environment

Deployment information passes to the agent client.

Review inference. Dagster plugin and MCP authentication; Dagster AI tools and MCP capabilities; Dagster Plus roles and enforcement

Failure modes to consider

A wrong regional endpoint or assumed restrictive override can misstate access.

Review inference. Dagster plugin and MCP authentication; Dagster AI tools and MCP capabilities; Dagster Plus roles and enforcement

Unknowns and applicability

Current tool inventory, authenticated identity and effective grants are unverified.

Not established

Suggested refusal or clarification condition

Require the selected deployment and action scope before allowing operational changes.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Plugin endpoint defaults, exposed operations and deployment-role assignments.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the region and effective-role evidence needed before operational agent access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Databricks catalogs: Workspace binding and user grants

Question: Does a SELECT grant prove an agent can access a catalog from any Databricks workspace?

Catalog binding can deny access from an unassigned workspace despite a user's explicit grants. A binding can also restrict that workspace to reads. Ordinary catalogs are open across the metastore by default, while automatically created workspace catalogs have a narrower default. Both binding and identity evidence are needed.

Source: Databricks workspace-catalog bindings. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A catalog grant establishes access from every workspace.

Buyer evidence still required

  • Catalog isolation mode and assigned workspaces.
  • Binding access level.
  • User grants and metastore association.

Suggested review condition: Require both workspace and identity scope before asserting access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Catalog type, isolation mode, workspace binding and user privileges

Optional saved evidence: Keep the identity and execution-location conditions together in a saved review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Databricks clones: Data independence and omitted history

Question: Does a Databricks table clone constitute an independent, complete exit archive?

A shallow clone copies metadata and references source data files, while a deep clone copies data and metadata. The documented clone operation does not copy table history, user-defined commit metadata or certain Unity Catalog properties such as tags. Clone success alone therefore cannot establish an independent archive containing all required evidence.

Source: Clone a table on Databricks. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Databricks table clone constitute an independent, complete exit archive?

Buyer evidence still required

  • Clone type and source/target file dependencies
  • Required history, tags and commit-metadata inventory
  • Target read verification and separately retained evidence

Review inference: An exit archive needs both data independence and explicit coverage of omitted metadata.

Suggested review condition: Refuse complete-export claims without testing independence and reconciling required evidence omitted by cloning.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Clone readability, source dependencies and archive completeness are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Choose a migration deliverable that remains usable after source access ends.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete provenance export or independence from a shallow clone
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Databricks deletion vectors and physical file cleanup

Question: Does a Delta row deletion using deletion vectors immediately remove the row bytes from all underlying data files?

Databricks deletion vectors mark rows as removed without immediately rewriting the underlying data files. REORG TABLE with APPLY PURGE rewrites files containing soft-deleted data, but the old files remain until eligible VACUUM cleanup. Other compaction operations do not necessarily rewrite every affected file. Logical deletion, file rewrite and retained-file cleanup are distinct stages.

Source: Deletion vectors in Databricks | Databricks on AWS. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Delta row deletion using deletion vectors immediately remove the row bytes from all underlying data files?

Buyer evidence still required

  • Table deletion-vector support and affected operations
  • Rewrite completion and resulting file/version inventory
  • Retention eligibility, cleanup results and separate copy inventory

Review inference: Require evidence for the applicable stages and retention conditions before accepting a physical-removal assertion.

Suggested review condition: Refuse physical-erasure claims based solely on row invisibility or a logical DELETE result.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual file contents, retained versions, caches and external copies are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Determine what remains to be evidenced after data stops appearing in normal queries.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Immediate physical erasure of deleted rows or verified removal from every copy
  • Actual file contents, retained versions, caches and external copies are unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Databricks MCP: Governed and legacy connection paths

Question: Does every Databricks MCP call pass through Unity Gateway controls?

No. The current AWS documentation distinguishes system.ai MCPs through Unity Gateway from legacy workspace endpoints. Legacy calls use underlying resource permissions and bypass MCP-level Gateway grants, policies and tracing. Record the actual connection path before accepting a governance or audit claim.

Source: Databricks-provided MCPs and underlying resource access. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: AWS documentation: system.ai and legacy workspace endpoints

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Databricks provides the documented MCP services.

Documented by publisher. Databricks-provided MCPs and underlying resource access

Purpose

Expose analytics, SQL, code execution or external services according to the selected MCP.

Documented by publisher. Databricks-provided MCPs and underlying resource access

Read capability

Can retrieve analytics, SQL results or connected-service content.

Documented by publisher. Databricks-provided MCPs and underlying resource access

Write capability

SQL, code and external-service capabilities depend on the selected MCP and grants.

Documented by publisher. Databricks-provided MCPs and underlying resource access

Authentication

OAuth connection guidance and scope requirements vary by connection path.

Documented by publisher. Databricks-provided MCPs and underlying resource access

Permission surface

Gateway MCP grants and legacy underlying-resource permissions are different controls.

Documented by publisher. Databricks-provided MCPs and underlying resource access

Data leaving the environment

Returned data reaches the agent; external-service MCPs add provider-specific handling.

Review inference. Databricks-provided MCPs and underlying resource access

Failure modes to consider

Legacy traffic may be absent from Gateway tracing without indicating no activity.

Review inference. Databricks-provided MCPs and underlying resource access

Unknowns and applicability

The buyer endpoint, enabled beta features and effective resource rights are unknown.

Not established

Suggested refusal or clarification condition

Require the actual endpoint path before accepting Gateway coverage.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck endpoint migrations, Gateway availability and underlying grants.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the connection-path evidence needed for an agent governance review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Databricks original record latency boundary

Question: Does Databricks' typical usage availability establish that later corrections are complete?

The captured guide says original billing usage records are typically available within twelve hours, with new workspaces potentially taking longer. This statement applies only to ORIGINAL records, not RETRACTION or RESTATEMENT corrections. It is not a finalization deadline; retain the observation time and reconcile later changes before closing an interval.

Source: Databricks: Billable usage system table. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Does Databricks' typical usage availability establish that later corrections are complete?

Buyer evidence still required

  • workspace age
  • ingestion date
  • record type
  • usage interval
  • later correction observations

Review inference: An operator freezes the cost total twelve hours after a run. Later correction records can be excluded. Adds Databricks' explicit original-only timing limitation and new-workspace exception. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Typical availability is neither a delivery SLA nor proof of a final or complete bill.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Record availability

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Typical availability is neither a delivery SLA nor proof of a final or complete bill.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Databricks shared SKU origin attribution

Question: Can a Databricks SKU uniquely identify which product generated usage?

Several Databricks products can share a SKU. The guide identifies billing_origin_product and product_features as the fields for distinguishing the originating product and features, including shared serverless-jobs billing. SKU-only allocation can merge different workloads; preserve the applicable product fields and their documented population conditions.

Source: Databricks: Billable usage system table. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Can a Databricks SKU uniquely identify which product generated usage?

Buyer evidence still required

  • sku_name
  • billing_origin_product
  • product_features
  • workload metadata
  • attribution policy

Review inference: An operator allocates all serverless-jobs SKU cost to a single workflow. Different platform features can be charged to the wrong internal owner. Adds a native shared-SKU product attribution mechanism rather than FOCUS invoice line grain. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Billing attribution fields do not independently establish the human requester or purchasing authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Billing origin product reference

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Billing attribution fields do not independently establish the human requester or purchasing authority.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Databricks SQL: Execution success does not establish full result retrieval

Question: Does Databricks SQL SUCCEEDED mean the agent retrieved the complete evidence result?

Databricks documents that SQL Statement Execution results can span multiple chunks. The response identifies subsequent chunks, and byte or row limits can set the truncated flag. Execution success therefore does not show that the client fetched every chunk or received an untrimmed result. Reconcile the manifest, limits and collected data for the same statement.

Source: Databricks: Statement Execution API. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Does Databricks SQL SUCCEEDED mean the agent retrieved the complete evidence result?

Buyer evidence still required

  • The statement ID, query scope, parameters and execution status.
  • The manifest, truncation flag, applied limits and chunk references.
  • The collected chunks, row coverage and unresolved retrieval failures.

Suggested review condition: Do not claim a complete result from SUCCEEDED or the first chunk alone when manifest coverage and truncation have not been reconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The statement ID, query scope, parameters and execution status. The manifest, truncation flag, applied limits and chunk references. The collected chunks, row coverage and unresolved retrieval failures.

Optional saved evidence: An analyst or audit buyer must distinguish successful query execution from complete retrieval of the evidence used for a decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Databricks tool selection: Direct connection grants matter

Question: Does an MCP tool allowlist constrain identities that also have direct connection access?

Databricks warns that USE CONNECTION permits direct use outside the MCP tool selection and policies. It also documents all-tools defaults and optional inclusion of future tools. Review direct grants and selector behaviour before claiming the allowlist covers every access path.

Source: Databricks MCP tool selection and direct connection boundary. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An MCP allowlist restricts every use of the underlying connection.

Buyer evidence still required

  • Effective MCP and direct connection permissions
  • Configured selectors and future-tool inclusion setting
  • Policy scope and evidence for each access path being claimed

Suggested review condition: Require direct-grant evidence before treating the MCP allowlist as universal.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck direct grants, selectors and newly exposed tools.

Optional saved evidence: Save the distinction between governed tools and separate connection authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Databricks Unity Catalog: Dropped objects and delayed file purge

Question: Does dropping a Unity Catalog table or volume immediately delete its underlying files?

For external tables and volumes, Unity Catalog removes metadata while underlying files remain. Managed files pass through a recovery window and asynchronous purge; the captured guide allows roughly 7–30 days after deletion. Customer storage versioning or soft-delete policies can retain files beyond purge. Object type and storage policy determine the residual-data boundary.

Source: Object storage lifecycle in Unity Catalog. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does dropping a Unity Catalog table or volume immediately delete its underlying files?

Buyer evidence still required

  • Object type and managed or external storage mapping
  • Deletion time, recovery eligibility and purge observations
  • Cloud versioning, soft-delete and lifecycle settings

Review inference: A dropped catalogue entry is not a complete data-removal receipt.

Suggested review condition: Refuse verified-erasure or universal-recovery claims without object-specific storage evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Purge completion, retained versions and recovery eligibility are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid signing off data exit while underlying cloud files remain.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Immediate erasure, guaranteed recovery or removal of cloud-retained copies
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Databricks usage retraction restatement

Question: How should Databricks billing usage corrections affect a cost total?

Corrections add a negative RETRACTION to cancel the original usage and normally a RESTATEMENT containing corrected fields. If the original should not have existed, there may be only a retraction. Retain record_type and signed quantities across all related rows; ignoring negatives or requiring every correction to have a restatement can leave an incorrect total.

Source: Databricks: Billable usage system table. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: How should Databricks billing usage corrections affect a cost total?

Buyer evidence still required

  • ORIGINAL RETRACTION and RESTATEMENT rows
  • signed usage quantities
  • product and accounting dimensions
  • observation date

Review inference: A pipeline loads only original records or positive quantities. Superseded usage remains charged in the internal report. Adds Databricks record_type and retraction-only behavior rather than Google adjustment_info grouping. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Usage corrections do not establish invoice settlement or independent accuracy of the underlying meter.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Record type reference

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Usage corrections do not establish invoice settlement or independent accuracy of the underlying meter.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Databricks: Unbinding a location can leave existing tables usable

Question: Does unbinding a Databricks external location from a workspace stop access through tables already created there?

Databricks checks an external location's workspace binding when privileges against that location are exercised, such as creating an external table. Its GCP guide explicitly says that an external table continues to function if the location is subsequently unbound. Catalog bindings provide a separate way to control the workspaces in which catalog contents are available.

Source: Manage external locations | Databricks on Google Cloud. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does unbinding a Databricks external location from a workspace stop access through tables already created there?

Buyer evidence still required

  • Metastore, workspace, cloud and external-location binding state.
  • Previously created external tables, catalog bindings and effective grants.
  • Post-change access observations for each intended data path.

Review inference: A location binding change is not sufficient evidence of universal data offboarding.

Suggested review condition: Refuse all-access-removed claims based only on the external-location binding.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer tables, cloud credentials and grants were not inspected; other cloud variants need their own source check.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck external-table behavior and catalog/location bindings after workspace or privilege changes.

Optional saved evidence: Identify which declared controls can support an agent authority decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal revocation, direct cloud-storage denial or tested table isolation
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Datadog Audit Trail: Enablement, retention and archive are separate

Question: Does enabling Datadog Audit Trail guarantee indefinite searchable audit history?

The guide provides configurable retention and a separate optional archive path. Archive upload has an interval and setup delay; it is not immediate evidence that every event is retained in the buyer's bucket. Enablement, retention and verified archive delivery need distinct checks.

Source: Datadog Audit Trail. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Enabled Audit Trail guarantees permanent searchable history.

Buyer evidence still required

  • Audit Trail enablement and retention selection.
  • Archive destination and permissions.
  • Observed archive delivery and downstream retention.

Suggested review condition: Require retained-event evidence for the required review period.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Enablement, retention, archive configuration and delivery evidence

Optional saved evidence: Save the retention and export assumptions behind an audit-evidence requirement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Datadog Logs: Index exclusion is not data deletion

Question: Does excluding a Datadog log from an index mean it was deleted or never collected?

Datadog documents that index-excluded logs can still reach Live Tail, metrics and archives. Exclusion controls searchable indexing rather than proving deletion from every destination. Check the complete configured route before relying on a no-retention or no-event claim.

Source: Datadog log index exclusions and other destinations. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Logs missing from an index were not retained anywhere.

Buyer evidence still required

  • Dated index and exclusion configuration
  • Archive and downstream destination inventory
  • Evidence for the relevant event interval and retention policy

Suggested review condition: Qualify deletion or absence claims when only index-search evidence is available.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck exclusion filters, archive destinations and retention settings.

Optional saved evidence: Preserve why searchable coverage and retained data were treated separately.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Datadog MCP: Telemetry access and result completeness

Question: Can an agent treat an observability connector's returned trace as complete or assume it cannot change monitoring?

Datadog documents role and organization controls for MCP reads and writes, plus resource-specific permissions. Its tool reference warns that a large trace may be truncated without a way to retrieve every span. Incident details also omit timeline data. Treat those limits as coverage boundaries when investigating an outage; an incomplete response is not a complete incident record.

Source: Datadog MCP data access boundaries. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Datadog's main remote MCP service; excludes the separate local Code Security MCP server.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Datadog provides the hosted main MCP service.

Documented by publisher. Datadog MCP data access boundaries

Purpose

Retrieve observability context and perform permitted monitoring operations.

Documented by publisher. Datadog MCP data access boundaries

Read capability

Logs, metrics, traces and incidents are exposed by selected tools; large traces can be truncated.

Documented by publisher. Datadog MCP tools and response limitations

Write capability

Product toolsets include resource changes such as monitor creation; availability depends on write controls.

Documented by publisher. Datadog MCP authentication and role controls; Datadog MCP tools and response limitations

Authentication

OAuth is documented; token-based and API/application-key paths are also described for other clients.

Documented by publisher. Datadog MCP authentication and role controls

Permission surface

MCP role permissions, underlying resource permissions and organization-wide access switches all apply.

Documented by publisher. Datadog MCP authentication and role controls

Data leaving the environment

The AI client controls onward model disclosure; limiting returned telemetry limits potential exposure.

Review inference. Datadog MCP data access boundaries

Failure modes to consider

Missing spans or incident history treated as complete evidence, excessive log access, or unintended monitor changes.

Review inference. Datadog MCP tools and response limitations

Unknowns and applicability

Regional availability, actual roles, data-access restrictions, toolsets and client retention.

Not established

Suggested refusal or clarification condition

Mark incomplete traces and timelines explicitly; withhold monitoring changes during an evidence-only investigation.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck organization switches, toolset permissions and trace/timeline limitations before each new investigation workflow.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain access and response-completeness limits alongside an incident-review decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Datadog scanning: Redaction location and sampling

Question: Does Datadog sensitive-data scanning prove raw content never leaves our environment?

Cloud scanning receives data in the Datadog backend before redaction. Scanning within the customer environment is a different deployment choice. The supported fields differ across logs, APM, RUM and events, and optional sampling reduces the scanned fraction. A masked interface alone does not establish pre-egress redaction or complete coverage.

Source: Datadog Sensitive Data Scanner. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A redacted Datadog view proves all sensitive data was removed before transmission.

Buyer evidence still required

  • Scanner location and data-flow diagram.
  • Product-specific fields, rules and sampling.
  • Evidence from the source-side pipeline.

Suggested review condition: Require source-side evidence before describing redaction as pre-egress.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Scanner placement, product, selected fields, rules and sampling.

Optional saved evidence: Save the evidence questions for a supplier data-disclosure review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

dbt MCP: Server variants and capability uncertainty

Question: Can a dbt remote MCP connection replace every local development workflow?

No. dbt distinguishes the remote consumption service from self-hosted local development. API availability also depends on the plan. The overview contains overlapping Administrative API descriptions and a broad read-only statement, so it does not settle every operation: inspect the actual tool list before approving job or development actions.

Source: dbt MCP local and remote capabilities. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Self-hosted and remote server documentation

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

dbt provides the remote service and publishes the self-hosted server.

Documented by publisher. dbt MCP local and remote capabilities

Purpose

Expose metrics, metadata and supported dbt workflows.

Documented by publisher. dbt MCP local and remote capabilities

Read capability

Reads Semantic Layer results, metadata and available job artifacts.

Documented by publisher. dbt MCP local and remote capabilities

Write capability

The reviewed overview does not consistently establish every mutating operation across both variants.

Not established. dbt MCP local and remote capabilities

Authentication

OAuth or token authentication depends on setup.

Documented by publisher. dbt MCP local and remote capabilities

Permission surface

Plan entitlements and discovered tools must be checked together.

Review inference. dbt MCP local and remote capabilities

Data leaving the environment

Queried platform content enters the connected assistant.

Review inference. dbt MCP local and remote capabilities

Failure modes to consider

Treating variant guidance as a universal read-only guarantee can misclassify a task.

Review inference. dbt MCP local and remote capabilities

Unknowns and applicability

Effective tool definitions and Administrative API write coverage remain unverified.

Not established

Suggested refusal or clarification condition

Clarify the server variant and operation when the overview is insufficient.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck tool definitions, Administrative API wording and plan changes.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save documented variant limits and the unresolved capability question for supplier follow-up.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

dbt Semantic Layer: Tokens and warehouse identity

Question: Does each Semantic Layer service token use an independent warehouse identity?

Service tokens map to configured Semantic Layer credentials. Multiple tokens can share a credential, and available credential mappings depend on the plan. Queries follow the linked warehouse credential's data policies. Different token names alone do not establish separate warehouse access or user-specific row restrictions.

Source: dbt Semantic Layer credential mapping. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Different service tokens necessarily provide separate warehouse identities.

Buyer evidence still required

  • Token-to-credential mapping for the project.
  • Warehouse grants and data policies for that credential.
  • Plan entitlement and downstream client use.

Suggested review condition: Require the actual mapping before asserting separate data access for different clients.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Project, environment, plan, token mapping and underlying warehouse grants.

Optional saved evidence: Retain the credential-mapping evidence behind an analytical data-access decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Decoder V4: Acceleration boundary

Question: Does a Decoder V4 check establish performance acceleration?

The Decoder V4 source supports interface and consumer discipline. It explicitly excludes performance acceleration.

Derived from BDAS Decoder V4 — Decoder Check Pass. No new experiment or validation is claimed.

Claim boundaries
  • performance acceleration
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Default/last-version deletion dependencies and retirement scope

Question: Can one OpenAI skill version be retired without changing the default or remaining skill identity?

The Responses Skills guide says the default version cannot be deleted until another default is selected, deleting the last version deletes the skill, and deleting a skill removes all versions.

Source: OpenAI primary documentation: openai skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can one OpenAI skill version be retired without changing the default or remaining skill identity?

Buyer evidence still required

  • skill/version inventory
  • default pointer
  • active references
  • deletion receipt
  • residual-copy inventory

Review inference: Can one OpenAI skill version be retired without changing the default or remaining skill identity? Plan retirement against the referenced versions and default pointer; source deletion alone does not prove mounted copies or previous outputs are erased. Default/last-version deletion dependencies and retirement scope. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Plan retirement against the referenced versions and default pointer; source deletion alone does not prove mounted copies or previous outputs are erased.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Delete rules

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Plan retirement against the referenced versions and default pointer; source deletion alone does not prove mounted copies or previous outputs are erased.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Delta VACUUM: File retention, history and cached data

Question: Does keeping Delta history guarantee old table versions remain queryable after VACUUM?

VACUUM removes eligible unreferenced data files, which can remove the files needed by older table versions. Log retention is a separate process. Metadata-only deletes and cached copies have additional considerations. Retained history entries alone are not proof of recoverable data or complete removal from every execution environment.

Source: Databricks VACUUM retention and history. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Retained transaction history guarantees recovery after data-file cleanup.

Buyer evidence still required

  • Data-file and log retention settings.
  • VACUUM history and required recovery versions.
  • Deletion-vector, clone and cache scope where applicable.

Suggested review condition: Require necessary data files and applicable cache evidence before claiming recovery or erasure.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Table type, runtime, data-file retention, log retention, cleanup history and caches.

Optional saved evidence: Save a bounded recovery and retention review before depending on historical data.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Demonstration subprocess runner versus effective host isolation

Question: Does registering an Agent Framework subprocess skill runner establish a sandbox?

Microsoft marks the example subprocess runners as demonstrations and recommends separate isolation, resource limits, input validation and audit controls for production.

Source: Microsoft primary documentation: ms skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does registering an Agent Framework subprocess skill runner establish a sandbox?

Buyer evidence still required

  • runner implementation
  • runtime identity
  • filesystem/network policy
  • time/resource limits

Review inference: Does registering an Agent Framework subprocess skill runner establish a sandbox? Refuse to equate runner registration with filesystem, network or resource isolation; review the actual host controls. Demonstration subprocess runner versus effective host isolation. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse to equate runner registration with filesystem, network or resource isolation; review the actual host controls.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. provided for demonstration purposes only

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to equate runner registration with filesystem, network or resource isolation; review the actual host controls.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Dependabot alerts: Coverage and detection limits

Question: Does having no Dependabot alerts prove all dependencies are free of known issues?

Alerts depend on the default-branch dependency graph, supported ecosystems and advisories reviewed by GitHub. New disclosures can take time to appear, archived repositories are not scanned, and GitHub Actions SHA references are outside the documented semantic-version alert case. No alert is therefore not a complete dependency-safety verdict.

Source: GitHub Dependabot alerts. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Zero Dependabot alerts establishes a clean result for every deployed dependency.

Buyer evidence still required

  • Default branch and dependency graph completeness.
  • Repository status and supported package references.
  • Advisory timing and independent deployed inventory.

Suggested review condition: Identify coverage and timing gaps before interpreting a zero-alert result.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Repository status, default branch, package references, graph and advisory timing.

Optional saved evidence: Save the documented coverage basis behind a dependency-risk procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Deployment class matters more than resource location

Question: Does an Azure Foundry resource location establish the exact geography where every model request is processed?

The captured Microsoft guides distinguish Global, Data Zone and geography-based deployments; the resource location alone does not select their processing scope. Their EU descriptions differ: the privacy page says EU member nations, while the deployment guide includes the EU Data Boundary and possible EFTA regions. An exact country set remains unresolved from these captures.

Source: Understanding deployment types in Microsoft Foundry Models - Microsoft Foundry | Microsoft Learn. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an Azure Foundry resource location establish the exact geography where every model request is processed?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Refuse an exact-country, sovereign or compliance determination until the applicable deployment, model, current destination membership and governing terms resolve this source discrepancy.

Suggested review condition: Refuse an exact-country, sovereign or compliance determination until the applicable deployment, model, current destination membership and governing terms resolve this source discrepancy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ### Data Zone deployments

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse an exact-country, sovereign or compliance determination until the applicable deployment, model, current destination membership and governing terms resolve this source discrepancy.
  • A deployment-specific current agreement and destination evidence may resolve the narrower question; the discrepancy does not mean every deployment routes globally.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

reported synthetic alert burden not real precision

Detector evaluation: Alert rates and their denominators

Question: Does a low false-alert rate per check mean few monitored streams will alert?

The supplied S2 review distinguishes event recall, false emissions per check and the share of negative-control series that emitted at least once. Its reported results show why these denominators cannot be exchanged. Event-matched emissions also use a specific scoring rule and are not real-world precision. Preserve the unit, observation period and matching definition before translating a detector metric into an alert-workload claim.

Supplied review examined 2026-10-11. The original archive and experiment were not independently rechecked during this intake.

Claim boundaries
  • per-check rates presented as per-stream rates
  • event recall labelled classification accuracy
  • synthetic event matching labelled real-world precision
  • measured human workload savings

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

reported synthetic gate failed no promotion

Detector evaluation: Recall gains without qualification

Question: Can improved event detection justify promotion when a false-alert requirement fails?

The supplied S2 review reports improved synthetic event recall over independently selected simple comparators, but failure of the frozen false-emission criterion. The detector remains an unpromoted development candidate. Source enrichment was assessed separately, without detector authority over source admission. These are reported results on consumed synthetic cases, not real-incident qualification or an experiment rerun by this intake.

Supplied review examined 2026-10-11. The original archive and experiment were not independently rechecked during this intake.

Claim boundaries
  • production promotion from recall alone
  • independent real-incident validation
  • fresh confirmation from reused evaluation cases
  • source admission authorised by an anomaly signal

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Do Agent ID Developer and Administrator permit the same credential changes

Question: Do Agent ID Developer and Administrator permit the same credential changes?

The creation guide permits Agent ID Developer to configure federated identity credentials. Adding a secret or certificate requires Agent ID Administrator. Credential type changes the required administrative authority.

Source: Microsoft primary documentation: entra create blueprint. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Do Agent ID Developer and Administrator permit the same credential changes?

Buyer evidence still required

  • actor role
  • blueprint
  • credential type
  • operation

Review inference: Do Agent ID Developer and Administrator permit the same credential changes? Check the specific credential operation and actor role. Authority to configure credentials differs from consent to API permissions. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Check the specific credential operation and actor role.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. required to add a secret

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Check the specific credential operation and actor role.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Do published Slack rate tiers apply unchanged when a client avoids cursor pagination

Question: Do published Slack rate tiers apply unchanged when a client avoids cursor pagination?

For methods supporting cursor pagination, Slack applies the stated tier when pagination is used. Requests that avoid pagination receive stricter limits, so a tier label alone does not establish achievable inventory throughput.

Source: Rate limits | Slack Developer Docs. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Do published Slack rate tiers apply unchanged when a client avoids cursor pagination?

Buyer evidence still required

  • API method
  • cursor handling
  • tier
  • throttled responses
  • scan interval

Review inference: Do published Slack rate tiers apply unchanged when a client avoids cursor pagination? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Pagination-dependent throughput differs from token and channel visibility. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Check the actual pagination strategy before estimating scan coverage or completion time.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Pagination limitation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Check the actual pagination strategy before estimating scan coverage or completion time.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Docker digest pins: Repeatable identity still needs an update process

Question: Does pinning a container image digest automatically keep its security fixes current?

Digest pinning binds a build to a specific image even when a tag moves. The guide explains that this also opts out of automatic updates through the moving tag. Reproducibility and currency therefore require separate evidence: a fixed identity plus a reviewed process for updating it.

Source: Docker image digest pinning. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A pinned image remains automatically current with publisher fixes.

Buyer evidence still required

  • Exact base-image digest and platform context.
  • Publisher update monitoring and review ownership.
  • Evidence of approved digest updates and resulting builds.

Suggested review condition: Do not claim current fixes solely from a stable digest.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Image digest, platform, update ownership and build evidence

Optional saved evidence: Save the distinction between reproducible identity and maintained software.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Docker MCP Toolkit: Profile isolation and retained credentials

Question: Does removing a Docker MCP server also revoke its credentials and eliminate its previous access?

Docker documents profile-based server selection, explicit filesystem mounts and credential management. Removing a server does not itself remove its stored credentials. Container packaging and catalogue checks are useful evidence, but do not establish the permissions or safety of every tool in a selected profile.

Source: Docker Desktop MCP Toolkit profiles and runtime scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Docker Desktop Toolkit profiles and gateway; not Docker Sandboxes gateway

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Docker provides the Desktop Toolkit; individual tool publishers and downstream services remain separate operators.

Documented by publisher. Docker Desktop MCP Toolkit profiles and runtime scope; Docker MCP verification and retained credentials

Purpose

Profiles organize containerized MCP servers behind a client gateway.

Documented by publisher. Docker Desktop MCP Toolkit profiles and runtime scope; Docker MCP verification and retained credentials

Read capability

Read capability depends on the chosen server, credentials and explicitly granted file mounts.

Documented by publisher. Docker Desktop MCP Toolkit profiles and runtime scope; Docker MCP verification and retained credentials

Write capability

Tools in the profile may change downstream services or mounted data according to their grants.

Documented by publisher. Docker Desktop MCP Toolkit profiles and runtime scope; Docker MCP verification and retained credentials

Authentication

The Toolkit manages supported OAuth connections and other server credentials.

Documented by publisher. Docker Desktop MCP Toolkit profiles and runtime scope; Docker MCP verification and retained credentials

Permission surface

The profile selects available servers; host filesystem mounts require explicit configuration.

Documented by publisher. Docker Desktop MCP Toolkit profiles and runtime scope; Docker MCP verification and retained credentials

Data leaving the environment

Containers can call external services; filesystem isolation does not prove data stays on the device.

Review inference. Docker Desktop MCP Toolkit profiles and runtime scope; Docker MCP verification and retained credentials

Failure modes to consider

Removing a server can leave credentials stored; adding servers dynamically may change the reviewed tool inventory.

Review inference. Docker Desktop MCP Toolkit profiles and runtime scope; Docker MCP verification and retained credentials

Unknowns and applicability

Effective mounts, enabled servers, signatures, downstream grants and credential revocation have not been tested.

Not established

Suggested refusal or clarification condition

Review the active profile and revoke obsolete credentials explicitly; do not infer safety from catalogue inclusion.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck profile membership, dynamic discovery, mounts and residual credentials.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the reviewed server inventory and offboarding questions for a Desktop profile.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Docker: A multi-platform image contains distinct variants

Question: Does reviewing one Docker image platform establish the contents selected on every other platform?

A multi-platform image contains a manifest list referring to separate platform manifests, configurations and layers. Docker selects the variant matching the host platform on pull. Reviewing one variant therefore does not establish the contents of another.

Source: Multi-platform builds | Docker Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does reviewing one Docker image platform establish the contents selected on every other platform?

Buyer evidence still required

  • Image manifest-list identity.
  • Selected platform and child manifest.
  • Variant-specific layers, inventory and review results.

Suggested review condition: Do not carry an artifact review across platforms without checking the selected child manifest.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Image manifest-list identity. Selected platform and child manifest. Variant-specific layers, inventory and review results.

Optional saved evidence: Bind supply-chain evidence to the platform artifact an agent deployment will actually run.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Image scanning, vulnerability absence or successful execution on any architecture
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Documented managed delete wildcards require explicit full-project scope

Question: Can a Mem0 user wildcard be treated as a complete project erasure?

The current documentation distinguishes scoped delete_all arguments, rejects missing/blank identifiers in SDKs, and requires all four entity filters set to wildcards for its described full-project wipe.

Source: Mem0 primary documentation: mem0 delete. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Mem0 user wildcard be treated as a complete project erasure?

Buyer evidence still required

  • SDK/API version
  • user/agent/app/run filters
  • targeted ID inventory
  • deletion and recheck results

Review inference: Can a Mem0 user wildcard be treated as a complete project erasure? Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation. Documented managed delete wildcards require explicit full-project scope. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Wildcard deletes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Bind deletion to the documented SDK/API version and exact filters; never infer all representations or external copies were erased from a scoped confirmation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Docusign: Completion events and retained signed-document evidence

Question: Does a Docusign completion notification prove which signed document was retained and processed downstream?

Docusign recommends configuring completed documents, completion certificates where needed and document fields in completion webhooks. It also recommends accepting received messages into a queue for asynchronous processing. Document inclusion is configurable; a completion event and the listener's later processing are separate parts of the documented integration.

Source: Best practices for building your listener | Docusign. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Docusign completion notification prove which signed document was retained and processed downstream?

Buyer evidence still required

  • Envelope and account identity, event type and document-inclusion settings.
  • Retrieved signed bytes, document identifiers and retained content hashes.
  • Queue receipt and downstream processing outcome bound to that document.

Review inference: Identifying the exact retained document and completed processing requires evidence beyond the completion notification.

Suggested review condition: Refuse completed-document-processing claims when signed bytes or processing receipts cannot be bound to the event.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No envelope, signature validity or listener processing was independently verified.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Connect payload settings, document retrieval and asynchronous listener behavior.

Optional saved evidence: Bind an action request to the outcome evidence needed for a business decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Signature validation, legal validity or observed downstream processing
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Does a blocking A2A Send Message response prove the delegated task finished

Question: Does a blocking A2A Send Message response prove the delegated task finished?

Section 3.2.2 of the captured A2A specification says returnImmediately false or unset waits for a terminal or interrupted state, including INPUT_REQUIRED or AUTH_REQUIRED. Its general Send Message paragraph separately says the operation returns immediately. This source tension leaves actual timing to be checked against the implemented version; neither paragraph supports treating every returned Task as completed.

Source: A2A Project primary documentation: a2a spec. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a blocking A2A Send Message response prove the delegated task finished?

Buyer evidence still required

  • request configuration
  • returned task state
  • required input
  • authorization evidence

Review inference: Does a blocking A2A Send Message response prove the delegated task finished? Require the actual returned task state and implemented timing behavior; do not infer completion merely from a response or rely on an unqualified default-blocking claim. A blocking call can return a nonterminal interruption, before any completed-state acceptance question. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the actual returned task state and implemented timing behavior; do not infer completion merely from a response or rely on an unqualified default-blocking claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. 3.2.2. SendMessageConfiguration; 3.1.1. Send Message

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the actual returned task state and implemented timing behavior; do not infer completion merely from a response or rely on an unqualified default-blocking claim.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a canUseTool callback review every Claude SDK tool call

Question: Does a canUseTool callback review every Claude SDK tool call?

No. The captured documentation says bypassPermissions or a bare-tool allowedTools entry can approve calls before canUseTool, subject to documented exceptions. The TypeScript SDK warns about these configurations with CLAUDE_SDK_CAN_USE_TOOL_SHADOWED; the warning does not block calls or change options. For checks required on every tool call, the documentation directs developers to PreToolUse hooks.

Source: Anthropic primary documentation: claude permissions valid. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a canUseTool callback review every Claude SDK tool call?

Buyer evidence still required

  • allowedTools
  • mode
  • hook placement
  • observations
  • SDK version

Review inference: Does a canUseTool callback review every Claude SDK tool call? For every-call inspection use the documented earlier hook boundary; callback installation is not complete coverage. Claude callback coverage differs from Responses API MCP approval semantics. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: For every-call inspection use the documented earlier hook boundary; callback installation is not complete coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. CLAUDE_SDK_CAN_USE_TOOL_SHADOWED

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • For every-call inspection use the documented earlier hook boundary; callback installation is not complete coverage.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a created-only Graph message delta also prove that existing messages stayed unchanged

Question: Does a created-only Graph message delta also prove that existing messages stayed unchanged?

Graph supports created, updated or deleted changeType selections. Selecting one change type limits the observed changes; the service carries the selection into continuation links.

Source: Get incremental changes to messages in a folder - Microsoft Graph | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a created-only Graph message delta also prove that existing messages stayed unchanged?

Buyer evidence still required

  • initial changeType
  • continuation links
  • expected change classes
  • folder scope

Review inference: Does a created-only Graph message delta also prove that existing messages stayed unchanged? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Intentional change-class selection differs from accidental delivery loss. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer absence of updates or deletions from a created-only stream.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Use query parameters in a delta query for messages

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer absence of updates or deletions from a created-only stream.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a dynamic-group membership change immediately authorize agent sponsor actions

Question: Does a dynamic-group membership change immediately authorize agent sponsor actions?

Microsoft documents up to 24 hours after a dynamic membership rule or user-property change before sponsorship authorization succeeds. Changed membership alone is insufficient evidence of effective sponsor authority.

Source: Microsoft primary documentation: entra owner management. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a dynamic-group membership change immediately authorize agent sponsor actions?

Buyer evidence still required

  • sponsor group
  • change time
  • agent relationship
  • authorization result

Review inference: Does a dynamic-group membership change immediately authorize agent sponsor actions? Check effective authority before relying on a new sponsor for an urgent operation. Agent sponsor management delay differs from managed-identity resource-token caching. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Check effective authority before relying on a new sponsor for an urgent operation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. up to 24 hours

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Check effective authority before relying on a new sponsor for an urgent operation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a gap in Drive notification message numbers prove a missing event

Question: Does a gap in Drive notification message numbers prove a missing event?

Drive notification numbers increase within a channel but are not sequential. A numerical gap by itself cannot establish how many changes or notifications were lost.

Source: Notifications for resource changes  |  Google Drive  |  Google for Developers. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a gap in Drive notification message numbers prove a missing event?

Buyer evidence still required

  • channel identity
  • message numbers
  • source change feed
  • receipt timestamps

Review inference: Does a gap in Drive notification message numbers prove a missing event? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Notification numbering differs from the meaning of a content removal marker. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Use channel scope and change-feed reconciliation rather than subtracting message numbers to count missed events.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Sync message

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Use channel scope and change-feed reconciliation rather than subtracting message numbers to count missed events.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a generic per-token LangSmith price map cover every custom charging formula

Question: Does a generic per-token LangSmith price map cover every custom charging formula?

LangSmith documents built-in support for specified Gemini stepwise pricing. For other non-linear models it directs clients to calculate cost and send the result in usage metadata.

Source: Cost tracking. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a generic per-token LangSmith price map cover every custom charging formula?

Buyer evidence still required

  • model
  • usage
  • charging formula
  • supplied cost metadata
  • provider bill scope

Review inference: Does a generic per-token LangSmith price map cover every custom charging formula? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Run-level non-linear calculation differs from selecting invoice cost bases. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not equate a linear estimate with a non-linear contracted charge without the applicable calculation evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. LLM calls: Send costs directly

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not equate a linear estimate with a non-linear contracted charge without the applicable calculation evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a global Notary policy govern every artifact repository

Question: Does a global Notary policy govern every artifact repository?

For OCI artifacts, an exact repository policy takes precedence over a global rule. Without either match verification must fail; URIs must be fully qualified.

Source: Trust Store and Trust Policy Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a global Notary policy govern every artifact repository?

Buyer evidence still required

  • repository URI
  • exact and global policies
  • selected rule

Review inference: Assess acceptance after changing artifact location. Require the missing evidence before accepting, retrying or closing the operation. Rule precedence differs from offline artifact-name verification. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Resolve the exact repository and selected policy before asserting effective requirements.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Selecting a trust policy to verify a signed OCI artifact

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Resolve the exact repository and selected policy before asserting effective requirements.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a LangSmith SDK sampling setting control every ingestion path

Question: Does a LangSmith SDK sampling setting control every ingestion path?

The documented sampling configuration applies to the SDK or LangChain, not direct API logging. Individual clients can also have different rates, so one environment value does not describe every producer.

Source: Set a sampling rate for traces. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a LangSmith SDK sampling setting control every ingestion path?

Buyer evidence still required

  • SDK and direct API producers
  • client sample rates
  • tracing context
  • analysis population

Review inference: Does a LangSmith SDK sampling setting control every ingestion path? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Ingestion-path and per-client settings differ from the general incompleteness of sampled traces. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Inventory producer paths and effective client rates before comparing captured activity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Set different sampling rates per client

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inventory producer paths and effective client rates before comparing captured activity.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a non-owner Graph permissions response inventory every sharing grant

Question: Does a non-owner Graph permissions response inventory every sharing grant?

Graph returns all sharing permissions to an item owner or co-owner, but only permissions applicable to a non-owner caller. A successful non-owner response is therefore a caller-scoped view.

Source: List who has access to a file - Microsoft Graph v1.0 | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a non-owner Graph permissions response inventory every sharing grant?

Buyer evidence still required

  • caller ownership context
  • item identity
  • returned permissions
  • owner-authorised inventory

Review inference: Does a non-owner Graph permissions response inventory every sharing grant? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Response visibility differs from which permission mode authorises the API call. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not declare that no other sharing grants exist from a non-owner inventory.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Permissions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not declare that no other sharing grants exist from a non-owner inventory.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a Notary policy pass mean every signature check passed

Question: Does a Notary policy pass mean every signature check passed?

The pinned specification distinguishes strict, permissive, audit and skip. Logged failures need not reject an artifact; skip performs no signature verification.

Source: Trust Store and Trust Policy Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a Notary policy pass mean every signature check passed?

Buyer evidence still required

  • specification revision
  • tool version
  • policy level
  • validation log

Review inference: Interpret an artifact acceptance report. Require the missing evidence before accepting, retrying or closing the operation. Notary enforcement levels differ from Cosign signer selection. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not report full verification without the effective level and individual outcomes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Signature Verification details

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not report full verification without the effective level and individual outcomes.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a recorded LangSmith LLM trace necessarily have a calculable cost

Question: Does a recorded LangSmith LLM trace necessarily have a calculable cost?

Automatic cost calculation needs token counts, model and provider identification, and applicable model pricing. A recorded trace alone does not establish that those inputs were supplied.

Source: Cost tracking. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a recorded LangSmith LLM trace necessarily have a calculable cost?

Buyer evidence still required

  • run type
  • usage metadata
  • model and provider
  • pricing entry

Review inference: Does a recorded LangSmith LLM trace necessarily have a calculable cost? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Instrumentation input completeness differs from delayed provider accounting. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Treat absent cost as unknown until the usage and pricing inputs are reconciled; it is not evidence of free execution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Cost tracking

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Treat absent cost as unknown until the usage and pricing inputs are reconciled; it is not evidence of free execution.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a referrers API 404 prove no OCI evidence exists

Question: Does a referrers API 404 prove no OCI evidence exists?

Distribution 1.1.1 requires referrers tag-schema fallback after a referrers API 404. API failure alone is not completed discovery.

Source: Open Container Initiative Distribution Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a referrers API 404 prove no OCI evidence exists?

Buyer evidence still required

  • API response
  • repository and digest
  • tag-schema response
  • registry capability

Review inference: Distinguish unsupported discovery from missing attachments. Require the missing evidence before accepting, retrying or closing the operation. Registry fallback differs from private transparency-log absence. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not report absent signatures or SBOMs before evaluating the fallback result.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Listing Referrers

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not report absent signatures or SBOMs before evaluating the fallback result.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a request-scoped Langfuse routing provider also route global OpenTelemetry instrumentation

Question: Does a request-scoped Langfuse routing provider also route global OpenTelemetry instrumentation?

Third-party libraries using the global tracer provider do not pass through the request routing provider. Integrations accepting an explicit tracer need the intended routing tracer supplied.

Source: Advanced Features - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a request-scoped Langfuse routing provider also route global OpenTelemetry instrumentation?

Buyer evidence still required

  • global and routing providers
  • instrumentor tracer configuration
  • project export destination

Review inference: Does a request-scoped Langfuse routing provider also route global OpenTelemetry instrumentation? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Provider routing gaps differ from the meaning of an instrumentation scope name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Keep globally emitted spans outside a request-project completeness claim until their export path is established.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Third-party OpenTelemetry instrumentation is not routed.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep globally emitted spans outside a request-project completeness claim until their export path is established.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a Service Bus scheduled sequence number survive activation

Question: Does a Service Bus scheduled sequence number survive activation?

The scheduled sequence number is valid only while scheduled. Activation enqueues the message with a new sequence number.

Source: Azure Service Bus message sequencing and timestamps - Azure Service Bus | Microsoft Learn. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Service Bus scheduled sequence number survive activation?

Buyer evidence still required

  • scheduled sequence
  • application correlation ID
  • activation record
  • active sequence

Review inference: Reconstruct a scheduled workflow across activation. Require the missing evidence before accepting, retrying or closing the operation. Scheduled-to-active identity transition differs from MessageId deduplication. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not join scheduled and active records solely by the old sequence number. Preserve a separate correlation identity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Scheduled messages

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not join scheduled and active records solely by the old sequence number. Preserve a separate correlation identity.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a Service Bus transaction roll back external database or API effects

Question: Does a Service Bus transaction roll back external database or API effects?

Downstream databases and services do not automatically participate in the Service Bus transaction scope. Broker rollback does not establish their outcome.

Source: Transactions in Azure Service Bus - Azure Service Bus | Microsoft Learn. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Service Bus transaction roll back external database or API effects?

Buyer evidence still required

  • broker transaction result
  • database commit
  • external request identity
  • compensation policy

Review inference: Decide whether broker failure permits repeating an external operation. Require the missing evidence before accepting, retrying or closing the operation. Transaction membership is a distinct precondition from ambiguous settlement after processing. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse an all-or-nothing business outcome without independent external-effect evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Operations that don't enlist in transaction scopes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse an all-or-nothing business outcome without independent external-effect evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a successful tasks/update response prove the MCP task advanced or used my response

Question: Does a successful tasks/update response prove the MCP task advanced or used my response?

The optional 2026-07-28 Tasks extension permits a tasks/update acknowledgement before processing is reflected in observable state. It recommends ignoring responses for unknown or already-satisfied input keys. Clients should continue observing the task after an update; the acknowledgement alone does not establish a particular transition or completion.

Source: Model Context Protocol primary documentation: mcp tasks current. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a successful tasks/update response prove the MCP task advanced or used my response?

Buyer evidence still required

  • task ID
  • submitted input keys
  • update response
  • subsequent state
  • requested outcome

Review inference: Does a successful tasks/update response prove the MCP task advanced or used my response? Require subsequently observed task state and matching input identity before claiming progress. Correct key identity and eventual application are separate checks; acknowledgement need not evidence either final outcome. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require subsequently observed task state and matching input identity before claiming progress.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. The acknowledgement is eventually consistent; A server SHOULD ignore

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require subsequently observed task state and matching input identity before claiming progress.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a valid OCI descriptor establish trustworthy downloaded content

Question: Does a valid OCI descriptor establish trustworthy downloaded content?

Image 1.1.1 recommends checking size and digest before consuming untrusted content. A size mismatch should prevent trust; valid descriptor syntax does not establish matching bytes.

Source: OCI Content Descriptors. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a valid OCI descriptor establish trustworthy downloaded content?

Buyer evidence still required

  • trusted expected descriptor
  • downloaded bytes
  • byte count
  • computed digest

Review inference: Decide whether to process a registry-provided object. Require the missing evidence before accepting, retrying or closing the operation. OCI size and pre-consumption checks differ from Sigstore digest input. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse content identity without consistent checks. A matching digest does not establish publisher authority or safety.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Verification

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse content identity without consistent checks. A matching digest does not establish publisher authority or safety.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a valid OCI image index guarantee a usable image

Question: Does a valid OCI image index guarantee a usable image?

Image 1.1.1 requires the manifests array but permits it to be empty. Validity does not establish an available platform manifest.

Source: OCI Image Index Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a valid OCI image index guarantee a usable image?

Buyer evidence still required

  • index
  • manifest list
  • target platform
  • resolved manifest

Review inference: Interpret successful metadata retrieval with no usable image. Require the missing evidence before accepting, retrying or closing the operation. Index content availability differs from runtime integration. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not approve deployment from parsing alone. Require a compatible manifest and verified content.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. size of the array MAY be zero

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not approve deployment from parsing alone. Require a compatible manifest and verified content.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does a working My Drive changes integration automatically include shared drives

Question: Does a working My Drive changes integration automatically include shared drives?

Shared-drive changes require the documented support and inclusion settings. If shared-drive support is false, shared drives and their files are excluded from the response.

Source: Implement shared drive support  |  Google Drive  |  Google for Developers. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a working My Drive changes integration automatically include shared drives?

Buyer evidence still required

  • supportsAllDrives
  • includeItemsFromAllDrives
  • driveId
  • intended drive inventory

Review inference: Does a working My Drive changes integration automatically include shared drives? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Explicit shared-drive change support differs from a search response reporting incomplete corpora. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not claim shared-drive coverage solely from successful My Drive polling.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Track changes on a shared drive

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim shared-drive coverage solely from successful My Drive polling.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does account deletion retire a federation binding to a reusable name

Question: Does account deletion retire a federation binding to a reusable name?

Not necessarily. Google recommends non-reusable attributes because a later account can inherit a reused value and match an old binding. Uniqueness must hold over time.

Source: Google primary documentation: gcp federation practices. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does account deletion retire a federation binding to a reusable name?

Buyer evidence still required

  • attribute reassignment rules
  • deleted identity
  • remaining bindings

Review inference: Does account deletion retire a federation binding to a reusable name? Retire stale bindings or use a non-reassigned identifier; deletion alone is insufficient. Post-offboarding reassignment differs from current issuer scope and user editing. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Retire stale bindings or use a non-reassigned identifier; deletion alone is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Use non-reusable attributes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Retire stale bindings or use a non-reassigned identifier; deletion alone is insufficient.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does adding a thread identifier only to the parent preserve all child cost totals

Question: Does adding a thread identifier only to the parent preserve all child cost totals?

LangSmith requires thread metadata on child runs as well as the parent for thread filtering and token or cost aggregation. Unlabelled children can be omitted from that thread view.

Source: Configure threads. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does adding a thread identifier only to the parent preserve all child cost totals?

Buyer evidence still required

  • thread identifier
  • parent and child runs
  • metadata propagation
  • aggregation scope

Review inference: Does adding a thread identifier only to the parent preserve all child cost totals? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Missing attribution metadata differs from rounding and runtime-charge differences between totals. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat the thread total as complete until child metadata coverage is checked.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Group traces into threads

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat the thread total as complete until child metadata coverage is checked.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does advertising MCP Tasks once force all later tool calls to return task handles

Question: Does advertising MCP Tasks once force all later tool calls to return task handles?

The optional 2026-07-28 Tasks extension requires the capability on each request. A server must not return CreateTaskResult without it, even after earlier declarations. With support declared, the server chooses per request between a direct result and a task; clients must handle both.

Source: Model Context Protocol primary documentation: mcp tasks current. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does advertising MCP Tasks once force all later tool calls to return task handles?

Buyer evidence still required

  • extension version
  • request capabilities
  • response resultType
  • supported method

Review inference: Does advertising MCP Tasks once force all later tool calls to return task handles? Require the current request capability and actual result shape before selecting a task-processing path. Per-request opt-in and server-selected polymorphism go beyond generic extension compatibility. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the current request capability and actual result shape before selecting a task-processing path.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Capability Negotiation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the current request capability and actual result shape before selecting a task-processing path.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does AgentCore OBO always transmit the same actor evidence

Question: Does AgentCore OBO always transmit the same actor evidence?

No. RFC8693 mode supports an M2M token, an AWS IAM JWT, or no actor_token. NONE relies on the authorization server deriving actor identity from client authentication.

Source: Amazon Web Services primary documentation: aws on behalf of token exchange. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does AgentCore OBO always transmit the same actor evidence?

Buyer evidence still required

  • exchange config
  • actor mode
  • redacted fields
  • authorization response

Review inference: Does AgentCore OBO always transmit the same actor evidence? Record the actual mode and provider interpretation before claiming an explicit actor-token chain. AgentCore's actor-evidence configuration differs from the generic subject/actor distinction. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Record the actual mode and provider interpretation before claiming an explicit actor-token chain.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. actor_token_content

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Record the actual mode and provider interpretation before claiming an explicit actor-token chain.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an ADK artifact_delta event contain the generated file needed for an acceptance review

Question: Does an ADK artifact_delta event contain the generated file needed for an acceptance review?

The documented Python save example puts the artifact filename and assigned version in event.actions.artifact_delta. Artifact content is loaded separately through the artifact service. This event reference alone does not establish that the recipient retrieved or retained those bytes; other ADK languages can expose different API names.

Source: Google primary documentation: adk artifacts. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an ADK artifact_delta event contain the generated file needed for an acceptance review?

Buyer evidence still required

  • event
  • artifact filename
  • version
  • retrieved content
  • recipient receipt

Review inference: Does an ADK artifact_delta event contain the generated file needed for an acceptance review? Require retrieval of the referenced version and content before claiming delivery or content acceptance. ADK artifact_delta is a version reference, unlike A2A artifact-content chunk completion. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require retrieval of the referenced version and content before claiming delivery or content acceptance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. artifact_delta

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require retrieval of the referenced version and content before claiming delivery or content acceptance.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an AgentCore vault token prove the provider still accepts it

Question: Does an AgentCore vault token prove the provider still accepts it?

No. Provider-side revocation may be undetected by AgentCore. The documented forceAuthentication option clears stored refresh-token state and initiates fresh authentication; retrieval alone does not establish validity.

Source: Amazon Web Services primary documentation: aws identity authentication. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does an AgentCore vault token prove the provider still accepts it?

Buyer evidence still required

  • provider
  • redacted token provenance
  • rejection
  • reconsent result

Review inference: Does an AgentCore vault token prove the provider still accepts it? Reconcile rejection and reauthorization before retrying consequential work. Concrete vault validity/recovery behavior differs from introspection's active field. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reconcile rejection and reauthorization before retrying consequential work.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. not guaranteed to be valid

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile rejection and reauthorization before retrying consequential work.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an AgentCore workload identity automatically isolate its credential provider

Question: Does an AgentCore workload identity automatically isolate its credential provider?

No. The assigned IAM role controls provider access, with no extra workload-provider binding in the same account. Scope resource blocks to the intended ARNs. User-scoped OAuth retrieval still needs the relevant prior authorization.

Source: Amazon Web Services primary documentation: aws provider scope. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does an AgentCore workload identity automatically isolate its credential provider?

Buyer evidence still required

  • IAM policy
  • workload/provider ARNs
  • credential type
  • user authorization

Review inference: Does an AgentCore workload identity automatically isolate its credential provider? Inspect IAM resource scope rather than relying on workload or provider names. Credential-provider isolation differs from a workload token's existence. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Inspect IAM resource scope rather than relying on workload or provider names.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. does not enforce additional binding

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inspect IAM resource scope rather than relying on workload or provider names.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an available Stripe Issuing provisional credit establish a won dispute and final recovery

Question: Does an available Stripe Issuing provisional credit establish a won dispute and final recovery?

For the documented eligible UK and EU Issuing unauthorized or fraud flows, provisional credit can be spent while the dispute remains open. Stripe claws it back after resolving the dispute; a win produces a new credit for the amount recovered. A clawback can create a negative balance requiring replenishment. Reconcile provisional credit, reversal and any final credit separately instead of treating available funds as final recovery.

Source: Stripe primary documentation: stripe issuing provisional. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an available Stripe Issuing provisional credit establish a won dispute and final recovery?

Buyer evidence still required

  • eligible account and region
  • dispute reason
  • status
  • provisional balance entry
  • reversal
  • final credit

Review inference: Does an available Stripe Issuing provisional credit establish a won dispute and final recovery? Do not classify provisional funds as final recovery or extend this policy to every Issuing dispute or region. Cardholder provisional credit has a distinct temporary balance and clawback lifecycle. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not classify provisional funds as final recovery or extend this policy to every Issuing dispute or region.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Availability; provisional credit

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not classify provisional funds as final recovery or extend this policy to every Issuing dispute or region.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an empty Graph sharing facet mean the item inherits its parent permissions

Question: Does an empty Graph sharing facet mean the item inherits its parent permissions?

With hierarchicalsharing, Graph distinguishes inheritance from unique items with no sharing links using an empty sharing facet. The root of an unshared permission hierarchy can also carry that empty facet.

Source: driveItem: delta - Microsoft Graph v1.0 | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an empty Graph sharing facet mean the item inherits its parent permissions?

Buyer evidence still required

  • Prefer header
  • item and parent identifiers
  • sharing facets
  • permission detail response

Review inference: Does an empty Graph sharing facet mean the item inherits its parent permissions? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Interpreting incremental sharing hierarchy differs from application consent and resource grants. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Interpret the requested header and hierarchy together; an empty facet alone is not effective-access verification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Scanning permissions hierarchies

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Interpret the requested header and hierarchy together; an empty facet alone is not effective-access verification.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an Entra agent identity policy also cover its agent-user and delegated-user tokens

Question: Does an Entra agent identity policy also cover its agent-user and delegated-user tokens?

No. Delegated access, app-only agent identity access and agent-user access use different policy targets. A policy targeting the agent identity does not apply to its agent user account, or vice versa.

Source: Microsoft primary documentation: entra conditional. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does an Entra agent identity policy also cover its agent-user and delegated-user tokens?

Buyer evidence still required

  • patterns
  • subject summaries
  • audience
  • policies
  • evaluation evidence

Review inference: Does an Entra agent identity policy also cover its agent-user and delegated-user tokens? Map every actual token subject and access pattern to its policy. Agent ID's three subject patterns differ from generic workload targeting. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Map every actual token subject and access pattern to its policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Create separate policies

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Map every actual token subject and access pattern to its policy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an OCI artifactType query prove the response was filtered

Question: Does an OCI artifactType query prove the response was filtered?

Filtering support is recommended rather than universal. Applied filtering must be reported in OCI-Filters-Applied.

Source: Open Container Initiative Distribution Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does an OCI artifactType query prove the response was filtered?

Buyer evidence still required

  • artifactType query
  • OCI-Filters-Applied
  • descriptor types

Review inference: Select signatures from a mixed attachment inventory. Require the missing evidence before accepting, retrying or closing the operation. Filter execution differs from attestation predicate meaning. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not classify every descriptor from the query alone. Inspect applied-filter evidence and returned types.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Listing Referrers

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not classify every descriptor from the query alone. Inspect applied-filter evidence and returned types.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an OCI subject field approve the referenced artifact

Question: Does an OCI subject field approve the referenced artifact?

Image 1.1.1 defines subject as a weak association used for referrer discovery. It does not define certification or approval.

Source: OCI Image Manifest Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does an OCI subject field approve the referenced artifact?

Buyer evidence still required

  • subject digest
  • attachment type
  • signer and policy
  • evidence payload

Review inference: Decide whether attached evidence justifies artifact acceptance. Require the missing evidence before accepting, retrying or closing the operation. Relationship metadata differs from key-selection hints. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat attachment association as trusted approval. Verify evidence and acceptance policy separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. weak association

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat attachment association as trusted approval. Verify evidence and acceptance policy separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does an output guardrail tripwire leave the same session evidence as a guardrail exception

Question: Does an output guardrail tripwire leave the same session evidence as a guardrail exception?

The captured Python SDK guide distinguishes output-tripwire rejection from a guardrail exception. A tripwire asks the configured session to retain replay-valid completed tool context while excluding rejected final output; rejected terminal-tool payloads can be replaced with a placeholder, or the response suffix discarded when safe sanitization is unavailable. A guardrail exception leaves the verdict unknown and requests persistence of completed final-turn items; a session-write error takes precedence. Retained call metadata can still contain arguments.

Source: OpenAI primary documentation: openai guardrails. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an output guardrail tripwire leave the same session evidence as a guardrail exception?

Buyer evidence still required

  • SDK version
  • tripwire or exception
  • completed tool items
  • session write outcome

Review inference: Does an output guardrail tripwire leave the same session evidence as a guardrail exception? Do not infer absent tool work from withheld output, assume rejected payloads are retained, or treat a guardrail exception as a rejection verdict. Inspect the actual session write and retained fields. Guardrail outcome changes retained session evidence beyond control-placement coverage. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer absent tool work from withheld output, assume rejected payloads are retained, or treat a guardrail exception as a rejection verdict. Inspect the actual session write and retained fields.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. An output tripwire and an exception; Terminal function-tool output needs additional handling

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer absent tool work from withheld output, assume rejected payloads are retained, or treat a guardrail exception as a rejection verdict. Inspect the actual session write and retained fields.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does cancelling a RabbitMQ consumer stop or requeue in-flight work

Question: Does cancelling a RabbitMQ consumer stop or requeue in-flight work?

Consumer cancellation prevents future dispatch but leaves previously dispatched deliveries and their acknowledgement state unchanged. Closing the channel requeues its unacknowledged deliveries.

Source: Consumers | RabbitMQ. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does cancelling a RabbitMQ consumer stop or requeue in-flight work?

Buyer evidence still required

  • consumer tag
  • cancel time
  • in-flight deliveries
  • channel state
  • outcomes

Review inference: Determine whether a cancelled worker can still finish an action. Require the missing evidence before accepting, retrying or closing the operation. Subscription cancellation has a different protocol scope from Service Bus settlement failure. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat cancellation as proof of stopped side effects or recovered work. Inspect in-flight tasks separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Cancelling a Consumer (Unsubscribing)

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat cancellation as proof of stopped side effects or recovered work. Inspect in-flight tasks separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does changing a Langfuse model price necessarily change an explicitly supplied cost

Question: Does changing a Langfuse model price necessarily change an explicitly supplied cost?

Langfuse distinguishes ingested usage or cost from inferred values. When both are available, ingested values take priority, so the recorded amount may reflect the supplied payload rather than model-price inference.

Source: Token & Cost Tracking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does changing a Langfuse model price necessarily change an explicitly supplied cost?

Buyer evidence still required

  • cost payload
  • usage payload
  • model definition
  • ingestion timestamp

Review inference: Does changing a Langfuse model price necessarily change an explicitly supplied cost? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Cost-origin precedence differs from provisional provider accounting. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Identify the amount origin before diagnosing pricing or reconciliation discrepancies.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Model definitions and prices

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Identify the amount origin before diagnosing pricing or reconciliation discrepancies.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does changing the organisation evaluator limit update every attachment

Question: Does changing the organisation evaluator limit update every attachment?

Changing the organisation default updates attachments that inherit it. Custom per-project or per-dataset overrides remain in place; clearing the default removes caps only from inheriting attachments.

Source: Track and limit evaluator spend. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does changing the organisation evaluator limit update every attachment?

Buyer evidence still required

  • organisation default
  • attachment list
  • custom overrides
  • effective limits

Review inference: Does changing the organisation evaluator limit update every attachment? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Evaluator attachment inheritance differs from provider workspace budget scope. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Inspect effective attachment limits before claiming a uniform organisation budget policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Override the default for an attached project or dataset

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inspect effective attachment limits before claiming a uniform organisation budget policy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does code outside a Langfuse request context fall back safely into the same project

Question: Does code outside a Langfuse request context fall back safely into the same project?

In the documented request-scoped pattern, spans started outside its context are dropped. Long-lived callbacks and stored observation handles can lose the request context unless correctly bound.

Source: Advanced Features - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does code outside a Langfuse request context fall back safely into the same project?

Buyer evidence still required

  • callback creation context
  • context binding
  • stored handles
  • request lifetime

Review inference: Does code outside a Langfuse request context fall back safely into the same project? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Request-local context loss is a specific capture gap beyond an enabled tracing flag. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer no execution from absence of out-of-context spans; inspect callback context propagation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Spans started outside the request context are dropped.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer no execution from absence of out-of-context spans; inspect callback context propagation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does deleting an OCI tag remove its manifest and every alias

Question: Does deleting an OCI tag remove its manifest and every alias?

Tag deletion makes that tag return 404. Manifest deletion by digest makes the digest and tags pointing to it return 404.

Source: Open Container Initiative Distribution Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does deleting an OCI tag remove its manifest and every alias?

Buyer evidence still required

  • reference type
  • digest
  • alias inventory
  • post-delete results
  • copy scope

Review inference: Assess what remains addressable after withdrawing a release. Require the missing evidence before accepting, retrying or closing the operation. Registry addressability after deletion differs from downloaded-artifact verification. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat tag removal as proof of erasure, cache eviction or cross-repository revocation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Deleting tags;Deleting Manifests

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat tag removal as proof of erasure, cache eviction or cross-repository revocation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does directly changing a fetched ADK Session.state reliably persist an auditable change

Question: Does directly changing a fetched ADK Session.state reliably persist an auditable change?

The documentation distinguishes Context.state updates, which the framework tracks, from direct mutation of a Session retrieved from SessionService. The latter bypasses event tracking and can lose data. State updates should accompany an appended event.

Source: Google primary documentation: adk state. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does directly changing a fetched ADK Session.state reliably persist an auditable change?

Buyer evidence still required

  • session service
  • context update
  • event state delta
  • appended event
  • subsequent stored state

Review inference: Does directly changing a fetched ADK Session.state reliably persist an auditable change? Refuse durable-state or audit-history claims based solely on a mutated fetched Session object. Specifies the persistence boundary between a fetched object and tracked state events. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse durable-state or audit-history claims based solely on a mutated fetched Session object.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. How State is Updated: Recommended Methods

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse durable-state or audit-history claims based solely on a mutated fetched Session object.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does disabling a blueprint affect only future agent provisioning

Question: Does disabling a blueprint affect only future agent provisioning?

No. Microsoft describes blueprint disabling as preventing new agent identities and blocking existing ones. Its scope is broader than disabling one agent.

Source: Microsoft primary documentation: entra manage agent identities admin. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does disabling a blueprint affect only future agent provisioning?

Buyer evidence still required

  • blueprint
  • children
  • disable result
  • token/resource checks

Review inference: Does disabling a blueprint affect only future agent provisioning? Inventory affected agents; do not infer immediate revocation of every already-issued external credential. Provider-defined blueprint shutdown differs from generic exchange revocation independence. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Inventory affected agents; do not infer immediate revocation of every already-issued external credential.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Blueprint-level

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inventory affected agents; do not infer immediate revocation of every already-issued external credential.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does enabling a Slack event subscription guarantee every configured event type is delivered

Question: Does enabling a Slack event subscription guarantee every configured event type is delivered?

Slack states that granted OAuth scopes determine which subscribed event types an installation receives. Configuring a subscription without the required granted scopes does not supply that event class.

Source: The Events API | Slack Developer Docs. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does enabling a Slack event subscription guarantee every configured event type is delivered?

Buyer evidence still required

  • configured event types
  • installation grants
  • app and workspace
  • expected event class

Review inference: Does enabling a Slack event subscription guarantee every configured event type is delivered? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Push event eligibility differs from querying conversation history with a token. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Distinguish subscription configuration from actual grant coverage before interpreting silence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. App installation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Distinguish subscription configuration from actual grant coverage before interpreting silence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does enabling ADK resumability automatically give a custom agent correct restart checkpoints

Question: Does enabling ADK resumability automatically give a custom agent correct restart checkpoints?

The guide requires custom agents to define preservable steps and state, emit checkpoints for completed steps and mark overall completion with end_of_agent. Enabling resumability alone does not establish that a custom workflow implemented those checkpoints correctly.

Source: Google primary documentation: adk resume. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does enabling ADK resumability automatically give a custom agent correct restart checkpoints?

Buyer evidence still required

  • custom agent state
  • workflow steps
  • checkpoint events
  • completion marker

Review inference: Does enabling ADK resumability automatically give a custom agent correct restart checkpoints? Require custom step boundaries and saved completion events before accepting restart safety. Implementation of custom checkpoints precedes the separate risk of replaying an interrupted tool. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require custom step boundaries and saved completion events before accepting restart safety.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Add resume to custom Agents

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require custom step boundaries and saved completion events before accepting restart safety.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Entra Conditional Access govern an agent's direct API-key access

Question: Does Entra Conditional Access govern an agent's direct API-key access?

API-key access bypasses Entra authentication and token issuance, so its Conditional Access policies do not apply to that path. Resource-side key controls need separate assessment.

Source: Microsoft primary documentation: entra conditional. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does Entra Conditional Access govern an agent's direct API-key access?

Buyer evidence still required

  • credential type
  • resource
  • authentication path
  • key controls

Review inference: Does Entra Conditional Access govern an agent's direct API-key access? Do not count an Entra policy as coverage for a path outside Entra tokens. A path outside Entra differs from a token client's CAE enforcement. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not count an Entra policy as coverage for a path outside Entra tokens.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. API key

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not count an Entra policy as coverage for a path outside Entra tokens.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does every A2A streaming reply create a task that can later be polled

Question: Does every A2A streaming reply create a task that can later be polled?

A message-only stream contains exactly one Message and then closes, with no task tracking or updates. A task-lifecycle stream starts with a Task and may then carry updates. The client must distinguish the returned shape before scheduling task retrieval.

Source: A2A Project primary documentation: a2a spec. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does every A2A streaming reply create a task that can later be polled?

Buyer evidence still required

  • response type
  • initial stream object
  • task ID if present
  • requested outcome

Review inference: Does every A2A streaming reply create a task that can later be polled? Require an actual Task and its identifier before relying on later task-state polling. Task existence precedes and differs from replay limitations of an existing task. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require an actual Task and its identifier before relying on later task-state polling.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Message-only stream

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require an actual Task and its identifier before relying on later task-state polling.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does every Langfuse observation type contribute native usage and cost

Question: Does every Langfuse observation type contribute native usage and cost?

Langfuse documents cost and usage on generation and embedding observations. Other observation types do not carry those fields, so a visible tool or workflow observation is not necessarily priced.

Source: Token & Cost Tracking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does every Langfuse observation type contribute native usage and cost?

Buyer evidence still required

  • observation types
  • model calls
  • tool or retrieval charges
  • cost provenance

Review inference: Does every Langfuse observation type contribute native usage and cost? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Observability type coverage differs from a provider usage endpoint omitting a particular tool charge. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not call the visible trace total a complete business-task bill without separately accounting for excluded charges.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Troubleshooting

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not call the visible trace total a complete business-task bill without separately accounting for excluded charges.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does every Pub/Sub snapshot provide seven new days of recovery

Question: Does every Pub/Sub snapshot provide seven new days of recovery?

Snapshot lifetime is seven days minus the oldest unacknowledged message age. A snapshot expiring in less than one hour cannot be created.

Source: Replay and purge messages with seek  |  Pub/Sub  |  Google Cloud Documentation. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does every Pub/Sub snapshot provide seven new days of recovery?

Buyer evidence still required

  • snapshot creation and expiration
  • oldest unacknowledged message
  • required rollback window

Review inference: Determine whether a snapshot covers the planned release observation period. Require the missing evidence before accepting, retrying or closing the operation. Acknowledgement-state recovery lifetime differs from retained Temporal history. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not approve rollback coverage from creation time alone. Verify backlog age and actual expiration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. lifetime of a snapshot

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not approve rollback coverage from creation time alone. Verify backlog age and actual expiration.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does fetching MCP client metadata establish an acceptable redirect

Question: Does fetching MCP client metadata establish an acceptable redirect?

No. Checks include exact equality of document URL and client_id, required JSON fields, and matching the requested redirect against the document's list. A fetched page or familiar name is insufficient.

Source: Model Context Protocol primary documentation: mcp client registration. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does fetching MCP client metadata establish an acceptable redirect?

Buyer evidence still required

  • client_id URL
  • metadata
  • redirect list
  • actual redirect

Review inference: Does fetching MCP client metadata establish an acceptable redirect? Reject mismatches; protocol checks do not certify business trustworthiness. CIMD client/redirect validation differs from Registry namespace verification. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reject mismatches; protocol checks do not certify business trustworthiness.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Implementation Requirements

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reject mismatches; protocol checks do not certify business trustworthiness.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does flushing a request-scoped Langfuse provider include spans that end later

Question: Does flushing a request-scoped Langfuse provider include spans that end later?

The documented request-scoped JS/TS pattern exports ended spans at shutdown. Observations ending after the request callback finishes are lost, including unfinished streaming or background work.

Source: Advanced Features - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does flushing a request-scoped Langfuse provider include spans that end later?

Buyer evidence still required

  • request lifetime
  • observation end times
  • streaming completion
  • shutdown results

Review inference: Does flushing a request-scoped Langfuse provider include spans that end later? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Spans not yet ended differ from failure or timeout while exporting pending ended spans. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: End relevant observations before shutdown and check export results; flush invocation alone is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Spans that end after the request finishes are lost.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • End relevant observations before shutdown and check export results; flush invocation alone is insufficient.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Graph considering a webhook delivered prove the business action completed

Question: Does Graph considering a webhook delivered prove the business action completed?

Graph treats a timely 2xx response as delivery. It recommends queueing a notification and returning 202 when processing cannot finish promptly, separating HTTP acceptance from subsequent application work.

Source: Receive change notifications through webhooks - Microsoft Graph | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Graph considering a webhook delivered prove the business action completed?

Buyer evidence still required

  • notification identity
  • HTTP response
  • queue persistence
  • processing outcome

Review inference: Does Graph considering a webhook delivered prove the business action completed? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. A positive delivery acknowledgement differs from recovery after missing notifications. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require queue and processing outcome evidence before declaring the downstream operation complete.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. HTTP codes and retry logic

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require queue and processing outcome evidence before declaring the downstream operation complete.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Langfuse masking sanitize the same spans sent to every other backend

Question: Does Langfuse masking sanitize the same spans sent to every other backend?

The Python mask_otel_spans hook affects the Langfuse client export. A separate OpenTelemetry exporter receives its own unmodified copy unless its path has separate masking.

Source: Masking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Langfuse masking sanitize the same spans sent to every other backend?

Buyer evidence still required

  • span processors
  • exporter destinations
  • masking hooks
  • independent export checks

Review inference: Does Langfuse masking sanitize the same spans sent to every other backend? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Exporter-copy scope differs from redaction rule precedence within one processor. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Review every exporter path before asserting that sensitive telemetry is redacted everywhere.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. mask_otel_spans

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Review every exporter path before asserting that sensitive telemetry is redacted everywhere.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does LangSmith evaluator spend independently verify the provider invoice

Question: Does LangSmith evaluator spend independently verify the provider invoice?

Evaluator spend is calculated from configured model prices, not provider billing. Discounts, custom contracts and unconfigured variants can produce differences from an invoice.

Source: Track and limit evaluator spend. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does LangSmith evaluator spend independently verify the provider invoice?

Buyer evidence still required

  • configured prices
  • model variants
  • evaluation usage
  • provider contract and invoice

Review inference: Does LangSmith evaluator spend independently verify the provider invoice? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Evaluator cost estimation differs from invoice cost-basis selection. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reconcile pricing assumptions and provider evidence before treating a difference as incorrect billing or settlement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Troubleshooting

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile pricing assumptions and provider evidence before treating a difference as incorrect billing or settlement.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does LANGSMITH_TRACING=true prove every invocation was recorded

Question: Does LANGSMITH_TRACING=true prove every invocation was recorded?

Scoped tracing_context settings take precedence over global configuration and environment variables. Nested contexts use the innermost setting, so tracing can be disabled for selected invocations despite a global enable flag.

Source: Conditional tracing. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does LANGSMITH_TRACING=true prove every invocation was recorded?

Buyer evidence still required

  • environment value
  • global configuration
  • nested tracing contexts
  • invocation scope

Review inference: Does LANGSMITH_TRACING=true prove every invocation was recorded? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Explicit runtime override precedence adds a concrete check beyond a general capture configuration review. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Inspect runtime contexts before interpreting absent traces as absent execution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. How tracing context works

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inspect runtime contexts before interpreting absent traces as absent execution.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does loading an ADK artifact by filename recover the exact version previously reviewed

Question: Does loading an ADK artifact by filename recover the exact version previously reviewed?

Loading an ADK artifact without a version retrieves the latest version; specifying version N selects that version, and saving returns the assigned version. Retain the scoped filename and version for the exact reviewed output. Separately check the configured backend: the guide distinguishes temporary in-memory storage from persistent services such as GCS, so the version number alone does not establish restart durability.

Source: Google primary documentation: adk artifacts. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does loading an ADK artifact by filename recover the exact version previously reviewed?

Buyer evidence still required

  • app
  • user
  • session
  • filename
  • saved version
  • configured artifact service
  • recovered content

Review inference: Does loading an ADK artifact by filename recover the exact version previously reviewed? Do not substitute the latest artifact for the version used by a prior review. ADK's default latest-version retrieval differs from immutable build artifact selection. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not substitute the latest artifact for the version used by a prior review.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. load_artifact(..., version=None); InMemoryArtifactService; Persistence

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not substitute the latest artifact for the version used by a prior review.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Notary artifact success validate every attached signature

Question: Does Notary artifact success validate every attached signature?

The pinned OCI workflow can skip failed candidates and accept a policy-valid signature with matching signed digest and requested annotations.

Source: Signing and Verification Workflow. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does Notary artifact success validate every attached signature?

Buyer evidence still required

  • signature inventory
  • accepted signature
  • outcomes
  • signed digest and annotations

Review inference: Interpret a multi-signature acceptance result. Require the missing evidence before accepting, retrying or closing the operation. Multi-signature selection differs from one predicate interpretation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not report all signatures as validated from overall success. Retain the accepted signature and findings.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. OCI artifact verification workflow

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not report all signatures as validated from overall success. Retain the accepted signature and findings.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Notary trustedIdentities=* select a particular builder

Question: Does Notary trustedIdentities=* select a particular builder?

The wildcard trusts signing identities issued by configured trusted authorities. It does not select one expected certificate subject.

Source: Trust Store and Trust Policy Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does Notary trustedIdentities=* select a particular builder?

Buyer evidence still required

  • trust stores
  • trustedIdentities
  • signing subject
  • expected builder

Review inference: Determine whether accepted software identifies the expected producer. Require the missing evidence before accepting, retrying or closing the operation. Wildcard authority scope differs from explicit signer expectations. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer a specific builder from wildcard acceptance. Require explicit identity evidence and approved trust stores.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Trusted Identities Constraints;trustedIdentities

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer a specific builder from wildcard acceptance. Require explicit identity evidence and approved trust stores.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Notation policy import merely add a rule to existing configuration

Question: Does Notation policy import merely add a rule to existing configuration?

The documented import example replaces the active trust policy after confirmation. Showing the policy afterwards confirms the resulting configuration.

Source: Manage trust policies | Notary Project | A set of specifications and tools intended to provide a cross-industry standard for securing software supply chains.. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does Notation policy import merely add a rule to existing configuration?

Buyer evidence still required

  • previous policy
  • imported policy
  • confirmation
  • post-import output

Review inference: Approve a trust-policy change during release preparation. Require the missing evidence before accepting, retrying or closing the operation. Local acceptance-policy replacement differs from descriptive tool hints. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not assume a merge or preserved requirements. Compare before and after and retain a restoration copy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Confirm the new trust policy

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assume a merge or preserved requirements. Compare before and after and retain a restoration copy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does OCI cross-repository mount HTTP 202 mean the blob is available

Question: Does OCI cross-repository mount HTTP 202 mean the blob is available?

A successful mount returns 201 Created. If mounting is unsupported or cannot be performed, 202 indicates an upload session has begun and the client may upload the blob.

Source: Open Container Initiative Distribution Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does OCI cross-repository mount HTTP 202 mean the blob is available?

Buyer evidence still required

  • source and target repository
  • requested digest
  • response status and Location
  • upload completion

Review inference: Determine whether required release content exists at its intended distribution location. Require the missing evidence before accepting, retrying or closing the operation. Cross-repository transfer completion differs from runtime compatibility. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat 202 as completed blob placement. Require successful mount or completed upload evidence before accepting distribution completeness.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Mounting a blob from another repository

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat 202 as completed blob placement. Require successful mount or completed upload evidence before accepting distribution completeness.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does OCI referrer discovery cover every repository containing a digest

Question: Does OCI referrer discovery cover every repository containing a digest?

The 1.1.1 response lists matching subject references within the requested repository namespace. It is not a global cross-repository inventory.

Source: Open Container Initiative Distribution Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does OCI referrer discovery cover every repository containing a digest?

Buyer evidence still required

  • registry and repository
  • subject digest
  • intended locations
  • discovery results

Review inference: Review evidence copied between artifact repositories. Require the missing evidence before accepting, retrying or closing the operation. Repository-bounded discovery differs from offline name rebinding. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer global absence from one namespace. Record searched evidence locations.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Listing Referrers

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer global absence from one namespace. Record searched evidence locations.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does one Graph message delta stream cover the whole mailbox

Question: Does one Graph message delta stream cover the whole mailbox?

Message delta tracking is per folder. Microsoft requires each folder in a hierarchy to be tracked individually; completing one folder stream is not mailbox-wide coverage.

Source: Get incremental changes to messages in a folder - Microsoft Graph | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does one Graph message delta stream cover the whole mailbox?

Buyer evidence still required

  • mailbox and folder inventory
  • per-folder delta state
  • capture interval

Review inference: Does one Graph message delta stream cover the whole mailbox? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Coverage across mailbox folders differs from sequence and reset handling within a stream. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Keep untracked folders outside any completeness conclusion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Track message changes in a folder

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep untracked folders outside any completeness conclusion.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does one Slack 429 response require stopping every workspace and API method

Question: Does one Slack 429 response require stopping every workspace and API method?

Slack applies the documented Retry-After interval to the affected method for tokens of the app in that workspace. Other methods and the same method in other workspaces are not restricted by that specific response.

Source: Rate limits | Slack Developer Docs. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does one Slack 429 response require stopping every workspace and API method?

Buyer evidence still required

  • method
  • workspace
  • app
  • Retry-After
  • retry attempt timeline

Review inference: Does one Slack 429 response require stopping every workspace and API method? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Request throttling scope differs from event delivery retry identity. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Bind retry decisions to the returned scope; do not treat the response as proof of an app-wide outage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Responding to rate limiting conditions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Bind retry decisions to the returned scope; do not treat the response as proof of an app-wide outage.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does possessing an MCP task ID authorize later retrieval or input updates

Question: Does possessing an MCP task ID authorize later retrieval or input updates?

The optional 2026-07-28 Tasks extension requires authentication and authorization checks on each task-related request. Task IDs need protection against guessing, and input requests retain the ordinary elicitation or sampling trust model. A task handle is not a higher-trust channel or an access grant.

Source: Model Context Protocol primary documentation: mcp tasks current. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does possessing an MCP task ID authorize later retrieval or input updates?

Buyer evidence still required

  • task ID
  • caller identity
  • current authorization
  • requested operation
  • input trust decision

Review inference: Does possessing an MCP task ID authorize later retrieval or input updates? Require current caller permission and ordinary input checks before using a known task handle. Applies authorization at subsequent task operations rather than token issuance or audience alone. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require current caller permission and ordinary input checks before using a known task handle.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Auth binding; Input-request trust model

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require current caller permission and ordinary input checks before using a known task handle.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Pub/Sub dead-letter forwarding preserve the original envelope unchanged

Question: Does Pub/Sub dead-letter forwarding preserve the original envelope unchanged?

Pub/Sub wraps an undeliverable message in a new message and adds attributes identifying the source subscription before forwarding it.

Source: Dead-letter topics  |  Pub/Sub  |  Google Cloud Documentation. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Pub/Sub dead-letter forwarding preserve the original envelope unchanged?

Buyer evidence still required

  • forwarded envelope
  • wrapped original message
  • source subscription
  • processing references

Review inference: Join failure records to original workflow attempts. Require the missing evidence before accepting, retrying or closing the operation. Wrapper provenance is distinct from ordering-key redelivery. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not discard original-message and source-subscription context during reconstruction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. How dead-letter topics work

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not discard original-message and source-subscription context during reconstruction.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling

Question: Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling?

Counting requires correct dead-letter configuration and IAM permissions. Forwarding is best effort, counts can reset, and deliveries may exceed the configured maximum.

Source: Dead-letter topics  |  Pub/Sub  |  Google Cloud Documentation. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling?

Buyer evidence still required

  • subscription configuration
  • service-account IAM
  • delivery attempts
  • operation results

Review inference: Assess whether a retry policy bounds repeated external actions. Require the missing evidence before accepting, retrying or closing the operation. Dead-letter attempt accounting differs from exactly-once acknowledgement scope. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat the setting as a hard execution cap. Check actual attempts and operation-level idempotency.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. How maximum delivery attempts are calculated

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat the setting as a hard execution cap. Check actual attempts and operation-level idempotency.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does RabbitMQ automatic acknowledgement establish completed processing

Question: Does RabbitMQ automatic acknowledgement establish completed processing?

In the captured RabbitMQ 4.4 guide, automatic acknowledgement considers delivery successful when sent to the connection. A worker failure can therefore lose already acknowledged deliveries before processing finishes.

Source: Consumer Acknowledgements and Publisher Confirms | RabbitMQ. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does RabbitMQ automatic acknowledgement establish completed processing?

Buyer evidence still required

  • acknowledgement mode
  • message identity
  • worker result
  • failure timeline

Review inference: Decide whether missing worker results can be reconstructed from queue acknowledgements. Require the missing evidence before accepting, retrying or closing the operation. Consumer acknowledgement timing is distinct from publisher routing confirmation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not mark application work complete from automatic acknowledgement alone. Require a result bound to the delivery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Consumer Acknowledgement Modes and Data Safety Considerations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not mark application work complete from automatic acknowledgement alone. Require a result bound to the delivery.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does RabbitMQ expiry in one queue remove copies from other queues

Question: Does RabbitMQ expiry in one queue remove copies from other queues?

Message TTL is independent for each queue. A routed message can expire at different times, and expiry in one queue does not affect its copies elsewhere.

Source: Time-To-Live and Expiration | RabbitMQ. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does RabbitMQ expiry in one queue remove copies from other queues?

Buyer evidence still required

  • routing destinations
  • queue TTL policies
  • enqueue times
  • delivery outcomes

Review inference: Check whether expired work remains available on another subscription. Require the missing evidence before accepting, retrying or closing the operation. Residual queue copies differ from dead-letter transfer reliability. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer system-wide removal or cancellation from one queue expiry. Account for routed copies and delivered tasks.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Per-Queue Message TTL in Queues

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer system-wide removal or cancellation from one queue expiry. Account for routed copies and delivered tasks.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does RabbitMQ redelivered=true prove a previous business action

Question: Does RabbitMQ redelivered=true prove a previous business action?

The redelivered flag is a hint of prior delivery. The original delivery may never have reached a consumer, so it does not establish processing or a completed external effect.

Source: Reliability Guide | RabbitMQ. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does RabbitMQ redelivered=true prove a previous business action?

Buyer evidence still required

  • message identity
  • redelivery flag
  • prior result
  • deduplication evidence

Review inference: Decide whether retrying would duplicate an earlier action. Require the missing evidence before accepting, retrying or closing the operation. A RabbitMQ delivery hint does not carry application outcome semantics. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not discard work as completed solely from the flag. Require operation-level results or deduplication evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Data Safety on the Consumer Side

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not discard work as completed solely from the flag. Require operation-level results or deduplication evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does reaching a LangSmith evaluator budget stop the underlying agent

Question: Does reaching a LangSmith evaluator budget stop the underlying agent?

The documented cap pauses evaluation on the affected project or dataset. The agent and its trace continue; the missing scores do not establish that application execution stopped.

Source: Track and limit evaluator spend. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does reaching a LangSmith evaluator budget stop the underlying agent?

Buyer evidence still required

  • evaluator attachment
  • effective cap
  • pause state
  • agent run and score records

Review inference: Does reaching a LangSmith evaluator budget stop the underlying agent? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Evaluator-only suspension differs from provider request spending limits. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Keep evaluator availability and application execution separate when reviewing budget effects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. How enforcement works

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep evaluator availability and application execution separate when reviewing budget effects.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does renaming a Graph folder emit updated paths for all descendants

Question: Does renaming a Graph folder emit updated paths for all descendants?

Graph documents that a folder rename does not return every descendant in delta, and parentReference.path is omitted. Clients should track items by identifier rather than infer unchanged paths from absent descendant rows.

Source: driveItem: delta - Microsoft Graph v1.0 | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does renaming a Graph folder emit updated paths for all descendants?

Buyer evidence still required

  • drive and item identifiers
  • parent references
  • rename observations
  • reconstructed hierarchy

Review inference: Does renaming a Graph folder emit updated paths for all descendants? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Path reconstruction after ancestor rename is a distinct stale-location decision. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not accept stale descendant paths as current locations without resolving their identifier hierarchy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Remarks

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not accept stale descendant paths as current locations without resolving their identifier hierarchy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does renewing a Drive notification channel preserve one continuous delivery identity

Question: Does renewing a Drive notification channel preserve one continuous delivery identity?

Drive channels do not renew automatically. Replacement requires a new unique channel identifier, and the old and new channels can overlap while both remain active.

Source: Notifications for resource changes  |  Google Drive  |  Google for Developers. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does renewing a Drive notification channel preserve one continuous delivery identity?

Buyer evidence still required

  • old and new channel IDs
  • expiration values
  • resource identity
  • overlapping receipts

Review inference: Does renewing a Drive notification channel preserve one continuous delivery identity? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Channel replacement lineage differs from content deletion or access loss. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reconcile both channel identities and expiry times; do not interpret overlapping delivery as independent source actions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Renew notification channels

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile both channel identities and expiry times; do not interpret overlapping delivery as independent source actions.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does requesting MCP task notifications establish that every requested task ID was subscribed

Question: Does requesting MCP task notifications establish that every requested task ID was subscribed?

In the optional 2026-07-28 Tasks extension, the acknowledgement lists the task IDs the server agreed to notify, if any. Notifications carry the complete current DetailedTask and final result, so clients may continue polling but need not. Compare the acknowledgement with requested IDs before relying on notification coverage; neither subscription nor a current-state notification supplies a promised replay of every historical transition.

Source: Model Context Protocol primary documentation: mcp tasks current. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does requesting MCP task notifications establish that every requested task ID was subscribed?

Buyer evidence still required

  • extension version
  • requested task IDs
  • acknowledged task IDs
  • current notifications or polls
  • expected final result

Review inference: Does requesting MCP task notifications establish that every requested task ID was subscribed? Require acknowledgement for the intended task IDs and an observed outcome; do not impose the obsolete mandatory-polling rule or infer complete event history. MCP's best-effort subscription and continued-polling requirement differ from an A2A current-state resubscription. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require acknowledgement for the intended task IDs and an observed outcome; do not impose the obsolete mandatory-polling rule or infer complete event history.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Task Status Notifications

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require acknowledgement for the intended task IDs and an observed outcome; do not impose the obsolete mandatory-polling rule or infer complete event history.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does restrictToMyDrive include every file visible to a Drive user

Question: Does restrictToMyDrive include every file visible to a Drive user?

Drive documents that restrictToMyDrive omits changes outside the My Drive hierarchy, including application-data files and shared files not added to My Drive. Caller visibility and selected change coverage are different.

Source: Method: changes.list  |  Google Drive  |  Google for Developers. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does restrictToMyDrive include every file visible to a Drive user?

Buyer evidence still required

  • restrictToMyDrive value
  • spaces
  • shared-file inventory
  • caller context

Review inference: Does restrictToMyDrive include every file visible to a Drive user? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. An intentional corpus filter differs from interpreting a removed change marker. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat this restricted stream as a complete inventory of accessible content.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Query parameters

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat this restricted stream as a complete inventory of accessible content.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does resubmitting a Service Bus dead letter restore its session position

Question: Does resubmitting a Service Bus dead letter restore its session position?

Resubmission receives a new enqueue time and sequence number, losing the original ordering relative to other session messages.

Source: Azure Service Bus Enable FIFO with Sessions - Azure Service Bus | Microsoft Learn. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does resubmitting a Service Bus dead letter restore its session position?

Buyer evidence still required

  • original and new sequence references
  • session ID
  • dependency order
  • replay result

Review inference: Decide whether a recovered failed step can safely join an advancing workflow. Require the missing evidence before accepting, retrying or closing the operation. Replay position differs from duplicate send suppression. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not assume original order is restored. Reconcile dependencies and completed effects before replay.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Maximum delivery count in sessions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assume original order is restored. Reconcile dependencies and completed effects before replay.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does reusing an A2A messageId guarantee that delegated work will not run twice

Question: Does reusing an A2A messageId guarantee that delegated work will not run twice?

Send Message operations may be idempotent and an agent may use messageId to detect duplicates. The captured specification does not require universal deduplication of Send Message. Retrying an uncertain send therefore needs the receiving agent's actual deduplication and outcome evidence.

Source: A2A Project primary documentation: a2a spec. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does reusing an A2A messageId guarantee that delegated work will not run twice?

Buyer evidence still required

  • message ID
  • original request
  • server deduplication contract
  • observed outcome

Review inference: Does reusing an A2A messageId guarantee that delegated work will not run twice? Do not authorize a consequential resend from messageId reuse alone. A2A explicitly leaves Send Message deduplication optional despite a protocol message identifier. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not authorize a consequential resend from messageId reuse alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. 3.3.1. Idempotency

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not authorize a consequential resend from messageId reuse alone.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does rewinding an ADK session restore shared user state and external side effects

Question: Does rewinding an ADK session restore shared user state and external side effects?

The documented rewind restores only session-level state and artifacts. App-level and user-level resources are not restored, and external systems require separate restoration by the operator. A session rewind cannot establish that a purchase or shared resource change was undone.

Source: Google primary documentation: adk rewind. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does rewinding an ADK session restore shared user state and external side effects?

Buyer evidence still required

  • rewind point
  • session resources
  • user and app state
  • external operation outcomes

Review inference: Does rewinding an ADK session restore shared user state and external side effects? Refuse full rollback claims without reconciling shared resources and external effects separately. ADK explicitly separates session rewind from shared resources and external restoration. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse full rollback claims without reconciling shared resources and external effects separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Global agent resources; External dependencies

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse full rollback claims without reconciling shared resources and external effects separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does saving or creating a Stripe Issuing dispute prove it was sent to the card network

Question: Does saving or creating a Stripe Issuing dispute prove it was sent to the card network?

The documented workflow creates a dispute on Save and submits it on Submit; the API also separates creation and submission. Evidence fields may be absent during creation while evidence is collected. A created dispute object is therefore not proof of a submitted network challenge.

Source: Stripe primary documentation: stripe issuing how to submit. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does saving or creating a Stripe Issuing dispute prove it was sent to the card network?

Buyer evidence still required

  • dispute ID
  • creation response
  • evidence completeness
  • submission response
  • current status

Review inference: Does saving or creating a Stripe Issuing dispute prove it was sent to the card network? Require submission status or response before reporting a dispute as sent. The state transition into submission differs from the evidence lock that follows it. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require submission status or response before reporting a dispute as sent.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Creation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require submission status or response before reporting a dispute as sent.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does Service Bus automatically retry exceptions inside a transaction

Question: Does Service Bus automatically retry exceptions inside a transaction?

The documented transaction behavior does not retry an operation after an exception within the transaction scope. Recovery must account for the transaction and separate effects.

Source: Transactions in Azure Service Bus - Azure Service Bus | Microsoft Learn. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Service Bus automatically retry exceptions inside a transaction?

Buyer evidence still required

  • transaction identifier
  • exception
  • retry configuration
  • explicit recovery result

Review inference: Determine whether failed transactional work needs application or manual recovery. Require the missing evidence before accepting, retrying or closing the operation. Retry eligibility inside transactions differs from settlement response ambiguity. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not assume retry settings repaired transactional work. Require a recorded recovery result.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Operations within a transaction scope

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assume retry settings repaired transactional work. Require a recorded recovery result.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does standard Slack retry handling guarantee delivery of substantially delayed events

Question: Does standard Slack retry handling guarantee delivery of substantially delayed events?

Slack describes Events API delivery as best effort. By default it does not attempt events more than two hours late; the optional Delayed Events setting changes late-delivery handling and adds hourly retries after the initial attempts.

Source: The Events API | Slack Developer Docs. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does standard Slack retry handling guarantee delivery of substantially delayed events?

Buyer evidence still required

  • Delayed Events setting
  • event time
  • received time
  • retry headers
  • incident interval

Review inference: Does standard Slack retry handling guarantee delivery of substantially delayed events? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Age-based delivery eligibility differs from treating retry copies as new actions. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Record the setting and incident interval; retries do not establish a complete historical stream.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Delayed events retry

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Record the setting and incident interval; retries do not establish a complete historical stream.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does stopping the event consumer stop an OpenAI Agents SDK streaming run

Question: Does stopping the event consumer stop an OpenAI Agents SDK streaming run?

The Python SDK background run and event consumer have separate lifetimes. Breaking the event loop or failing while handling an event can leave model and tool calls running; closing the iterator alone waits rather than requests cancellation. Cancellation while awaiting the next event does request run cancellation. The guide recommends explicit cancellation and draining cleanup when one consumer owns an early exit; none of this establishes rollback of earlier effects.

Source: OpenAI primary documentation: openai streaming. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does stopping the event consumer stop an OpenAI Agents SDK streaming run?

Buyer evidence still required

  • SDK version
  • consumer exit
  • cancel call
  • drained iterator
  • final run state

Review inference: Does stopping the event consumer stop an OpenAI Agents SDK streaming run? Require an explicit cancellation request and final cleanup evidence before assuming work stopped. The SDK consumer/background lifetime split is distinct from a remote task cancellation acknowledgement. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require an explicit cancellation request and final cleanup evidence before assuming work stopped.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Stop when your event consumer exits early

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require an explicit cancellation request and final cleanup evidence before assuming work stopped.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does successful Pub/Sub seek instantly change all delivered messages

Question: Does successful Pub/Sub seek instantly change all delivered messages?

Seek guarantees eventual delivery of messages made unacknowledged, but delivery does not change instantly. Messages outside the target state can arrive while seek takes effect.

Source: Replay and purge messages with seek  |  Pub/Sub  |  Google Cloud Documentation. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does successful Pub/Sub seek instantly change all delivered messages?

Buyer evidence still required

  • seek target and completion time
  • delivery times
  • message IDs
  • prior results

Review inference: Interpret deliveries during a replay transition. Require the missing evidence before accepting, retrying or closing the operation. Seek convergence differs from ordering-key semantics. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer failed seek or safely repeat an effect solely from immediate deliveries. Reconcile identities and prior results.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Eventual consistency of seek operations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer failed seek or safely repeat an effect solely from immediate deliveries. Reconcile identities and prior results.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does the first Drive sync notification prove that existing files were synchronised

Question: Does the first Drive sync notification prove that existing files were synchronised?

The sync notification signals channel startup, and can arrive before the watch response. It is not an inventory transfer or proof that the client has processed existing content.

Source: Notifications for resource changes  |  Google Drive  |  Google for Developers. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the first Drive sync notification prove that existing files were synchronised?

Buyer evidence still required

  • watch request identity
  • sync receipt
  • watch response
  • initial inventory checkpoint

Review inference: Does the first Drive sync notification prove that existing files were synchronised? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Channel startup is distinct from a data-state transition or successful initial sync. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Keep channel readiness separate from initial inventory and change-feed completion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Sync message

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep channel readiness separate from initial inventory and change-feed completion.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does the first OCI referrers response contain every evidence attachment

Question: Does the first OCI referrers response contain every evidence attachment?

Distribution 1.1.1 requires a next Link when referrers span responses. Each response contains a different part of the descriptor list.

Source: Open Container Initiative Distribution Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does the first OCI referrers response contain every evidence attachment?

Buyer evidence still required

  • repository and subject digest
  • response pages
  • continuation links
  • inventory

Review inference: Determine whether required signatures and SBOMs were all discovered. Require the missing evidence before accepting, retrying or closing the operation. Inventory completeness differs from interpreting one attestation predicate. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not assert complete coverage until continuation links for the repository and digest are resolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Listing Referrers

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assert complete coverage until continuation links for the repository and digest are resolved.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does the last visible token mean an OpenAI Agents SDK streamed run is fully complete

Question: Does the last visible token mean an OpenAI Agents SDK streamed run is fully complete?

The guide says completion requires the stream_events iterator to finish. Session persistence, approval bookkeeping or history compaction can continue after the final visible token. Inspect the final run state only after the iterator drains.

Source: OpenAI primary documentation: openai streaming. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the last visible token mean an OpenAI Agents SDK streamed run is fully complete?

Buyer evidence still required

  • SDK version
  • iterator completion
  • is_complete
  • session persistence
  • approval state

Review inference: Does the last visible token mean an OpenAI Agents SDK streamed run is fully complete? Do not acknowledge durable run completion based solely on the final token event. The completion observation point applies even without any guardrail failure. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not acknowledge durable run completion based solely on the final token event.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. A streaming run is not complete until the iterator ends

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not acknowledge durable run completion based solely on the final token event.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does the legacy Langfuse Python mask hook inspect final third-party OpenTelemetry attributes

Question: Does the legacy Langfuse Python mask hook inspect final third-party OpenTelemetry attributes?

The legacy mask hook transforms data set through Langfuse SDK APIs at attribute creation. It does not inspect final raw OpenTelemetry attributes from third-party instrumentation.

Source: Masking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the legacy Langfuse Python mask hook inspect final third-party OpenTelemetry attributes?

Buyer evidence still required

  • SDK version
  • legacy hook configuration
  • third-party instrumentors
  • final exported attributes

Review inference: Does the legacy Langfuse Python mask hook inspect final third-party OpenTelemetry attributes? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Instrumentation-origin coverage differs from rule precedence on data already entering a redaction processor. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not use that hook alone as evidence that third-party span data is sanitized.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Legacy

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not use that hook alone as evidence that third-party span data is sanitized.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does the MCP client-credentials extension use dynamic registration

Question: Does the MCP client-credentials extension use dynamic registration?

The optional pinned 2026-07-28 client-credentials extension requires pre-registered client credentials, typically established out of band through administrative channels, and does not use Dynamic Client Registration in this flow. Adopted implementations retain baseline authorization requirements.

Source: Model Context Protocol primary documentation: ext oauth client credentials. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does the MCP client-credentials extension use dynamic registration?

Buyer evidence still required

  • extension support/version
  • server metadata
  • registration
  • resource scopes

Review inference: Does the MCP client-credentials extension use dynamic registration? Require supported extension and pre-registration evidence. MCP extension onboarding differs from generic app-only consent semantics. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require supported extension and pre-registration evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Dynamic Client Registration is not used

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require supported extension and pre-registration evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does the Notary strict label establish the effective verification policy

Question: Does the Notary strict label establish the effective verification policy?

Custom overrides can change authenticity, timestamp, expiry and revocation validation. Integrity cannot be overridden, and skip cannot be customised.

Source: Trust Store and Trust Policy Specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does the Notary strict label establish the effective verification policy?

Buyer evidence still required

  • policy level
  • override map
  • tool version
  • per-check outcomes

Review inference: Compare declared strict policy with effective requirements. Require the missing evidence before accepting, retrying or closing the operation. Enforcement overrides differ from annotation-subset checks. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Inspect effective overrides and implementation version rather than accepting the level name alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Custom Verification Level

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inspect effective overrides and implementation version rather than accepting the level name alone.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does the Slack event authorizations field enumerate every installation that can see an event

Question: Does the Slack event authorizations field enumerate every installation that can see an event?

Slack event envelopes provide a limited authorization view. The documented apps.event.authorizations.list method retrieves the full authorization list when that inventory is needed.

Source: The Events API | Slack Developer Docs. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the Slack event authorizations field enumerate every installation that can see an event?

Buyer evidence still required

  • event context
  • envelope authorizations
  • complete authorization listing
  • workspace and app

Review inference: Does the Slack event authorizations field enumerate every installation that can see an event? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Recipient installation visibility differs from deduplicating deliveries for one event. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer a single visible installation from the abbreviated event envelope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. authorizations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer a single visible installation from the abbreviated event envelope.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does updating a Langfuse pricing definition repair costs on older generations

Question: Does updating a Langfuse pricing definition repair costs on older generations?

The documented model-definition changes apply to generations logged afterward. Updating a price is not evidence that historical amounts have been recalculated.

Source: Token & Cost Tracking - Langfuse. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does updating a Langfuse pricing definition repair costs on older generations?

Buyer evidence still required

  • old and new price definitions
  • change time
  • generation timestamps
  • historical estimates

Review inference: Does updating a Langfuse pricing definition repair costs on older generations? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Forward-only pricing changes differ from forward-only retention policy changes. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Keep historical estimates versioned and reconcile them separately rather than silently treating them as corrected.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Troubleshooting

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep historical estimates versioned and reconcile them separately rather than silently treating them as corrected.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Does wrapping a function in ADK LongRunningFunctionTool execute the long job for me

Question: Does wrapping a function in ADK LongRunningFunctionTool execute the long job for me?

LongRunningFunctionTool manages the interaction with long-running work rather than performing the lengthy task itself; the guide recommends a separate server for substantial work. The runner pauses and the client supplies intermediate or final responses. In the Python example, the function-call ID correlates its response while the external ticket ID is tracked separately. Neither an interaction handle nor a ticket reference proves worker completion.

Source: Google primary documentation: adk function tools. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does wrapping a function in ADK LongRunningFunctionTool execute the long job for me?

Buyer evidence still required

  • ADK language and version
  • function-call ID
  • external worker or ticket ID
  • matching response ID
  • worker state
  • final result

Review inference: Does wrapping a function in ADK LongRunningFunctionTool execute the long job for me? Do not treat creation of a long-running tool interaction as worker execution or completed work. Separates ADK interaction management from provision of the actual long-running worker. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat creation of a long-running tool interaction as worker execution or completed work.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Warning: Execution handling; function_call_id

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat creation of a long-running tool interaction as worker execution or completed work.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Doppler MCP: Read-only tools and token enforcement

Question: Do Doppler MCP scope flags enforce access beyond the connector?

The documentation distinguishes tool filtering from token-enforced API access. Read-only mode hides write tools, but does not stop other ways an agent might attempt writes. Project/config flags also are not a substitute for scoped credentials. Secret reads remain part of the advertised capability.

Source: Doppler MCP tools and read-only mode. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Experimental local Doppler MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Doppler publishes the experimental MCP server.

Documented by publisher. Doppler MCP tools and read-only mode

Purpose

Secret, environment and configuration operations.

Documented by publisher. Doppler MCP tools and read-only mode

Read capability

Secret values, configurations and activity information.

Documented by publisher. Doppler MCP tools and read-only mode

Write capability

Secret and environment changes when permitted.

Documented by publisher. Doppler MCP tools and read-only mode

Authentication

Interactive login or a runtime Doppler token.

Documented by publisher. Doppler MCP tools and read-only mode

Permission surface

API token permissions enforce access; connector flags narrow its exposed tools.

Documented by publisher. Doppler MCP tools and read-only mode

Data leaving the environment

Readable secret values may reach the connected client.

Review inference. Doppler MCP tools and read-only mode

Failure modes to consider

A broad token can retain authority outside filtered MCP tools.

Review inference. Doppler MCP tools and read-only mode

Unknowns and applicability

Buyer token and other agent execution channels are unverified.

Not established

Suggested refusal or clarification condition

Do not claim enforced read-only access from a tool flag alone.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Experimental status, scope flags and token enforcement guidance.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the evidence separating connector filtering from the credential boundary.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

DORA: An exit document needs a tested and reviewed plan

Question: What distinguishes a documented DORA exit plan from evidence of a tested plan?

For ICT services supporting critical or important functions, financial entities must have exit strategies; exit plans must be comprehensive, documented, sufficiently tested under Article 4(2), and periodically reviewed. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(8) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical/important-function ICT services, proportionate testing under Article 4(2); no invented fixed test interval. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What distinguishes a documented DORA exit plan from evidence of a tested plan?

Buyer evidence still required

  • Function assessment
  • exit plan version
  • test scope and results
  • periodic review record

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A plan or vendor export promise is not proof that an exit test ran successfully.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A plan or vendor export promise is not proof that an exit test ran successfully.
  • A plan or vendor export promise is not proof that an exit test ran successfully.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Apply subcontracting conditions consistently across the group

Question: Who owns the group-wide consistency review of critical-function subcontracting conditions?

Where the regulation applies on a consolidated or sub-consolidated basis, the parent responsible for those financial statements ensures permitted critical-function subcontracting conditions are consistent across group financial entities and adequate at all relevant levels. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 2 · Operator: Parent undertaking responsible for consolidated or sub-consolidated financial statements where the regulation applies at that level; relevant group financial entities remain within DORA scope.

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Consolidated or sub-consolidated application; the stated parent undertaking has this duty and group membership is not an exemption. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Who owns the group-wide consistency review of critical-function subcontracting conditions?

Buyer evidence still required

  • Consolidation scope and responsible parent
  • Entity contract matrix
  • Consistency and adequacy review

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A group policy alone does not establish consistent implementation in each relevant financial entity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A group policy alone does not establish consistent implementation in each relevant financial entity.
  • A group policy alone does not establish consistent implementation in each relevant financial entity.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Assess appropriate information-security standards

Question: What evidence supports the provider's use of security standards appropriate to the contracted service?

Financial entities may contract only with ICT providers complying with appropriate information-security standards; for critical or important functions they take due consideration, before concluding, of the provider's use of the most up-to-date and highest-quality standards. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(5) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

All ICT contracts with the stated additional critical-function consideration; no single certification is mandated by this clause. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What evidence supports the provider's use of security standards appropriate to the contracted service?

Buyer evidence still required

  • Service-specific security requirements
  • Provider implementation evidence
  • Assessment of standards and criticality

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Naming a standard without evidence of service-specific compliance is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Naming a standard without evidence of service-specific compliance is insufficient.
  • Naming a standard without evidence of service-specific compliance is insufficient.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Assess complex subcontracting chains and supervision

Question: Can the financial entity and supervisor monitor the function through the documented subcontracting chain?

Where critical-function ICT arrangements permit subcontracting, financial entities assess whether and how long or complex chains affect full monitoring of contracted functions and effective supervision by the competent authority. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 29(2), fourth subparagraph · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical or important functions and permitted subcontracting; chain length alone is not a risk score or prohibition. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can the financial entity and supervisor monitor the function through the documented subcontracting chain?

Buyer evidence still required

  • Service-specific chain map
  • Monitoring reach and access evidence
  • Supervisory impediment assessment

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A count of subcontractors does not establish monitorability or an authorised maximum depth.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A count of subcontractors does not establish monitorability or an authorised maximum depth.
  • A count of subcontractors does not establish monitorability or an authorised maximum depth.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Assess provider ability to select and monitor subcontractors

Question: What demonstrates the direct provider's capacity to assess and monitor its proposed subcontractors?

Before contracting for permitted critical-function subcontracting, the financial entity assesses the provider's ability to select and assess subcontractors' operational and financial abilities, including testing participation when required, and the provider's expertise and resources to monitor subcontractor ICT risk. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 3(1)(a),(e) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

ICT services supporting critical or important functions or material parts; financial-entity final responsibility is retained. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What demonstrates the direct provider's capacity to assess and monitor its proposed subcontractors?

Buyer evidence still required

  • Provider due-diligence process
  • Subcontractor operational and financial assessments
  • Provider monitoring resources and controls

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A list of subcontractor names without assessment methods or monitoring capacity is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A list of subcontractor names without assessment methods or monitoring capacity is insufficient.
  • A list of subcontractor names without assessment methods or monitoring capacity is insufficient.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Assess the financial entity's own monitoring capacity

Question: Can the financial entity itself oversee the subcontracted service and assess a subcontractor failure?

Before permitting critical-function subcontracting, the financial entity assesses its own expertise and financial, human and technical resources to monitor related ICT risks, and the impact of subcontractor failure on its resilience and financial soundness. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 3(1)(f)-(g) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical or important functions or material parts; outsourcing monitoring does not remove final financial-entity responsibility. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can the financial entity itself oversee the subcontracted service and assess a subcontractor failure?

Buyer evidence still required

  • Entity monitoring roles and resources
  • Risk, incident and continuity arrangements
  • Failure-impact assessment

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Provider assurance alone does not establish the financial entity's own adequate monitoring resources.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Provider assurance alone does not establish the financial entity's own adequate monitoring resources.
  • Provider assurance alone does not establish the financial entity's own adequate monitoring resources.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Concentration review includes substitutability and connected providers

Question: What concentration evidence is needed before another critical-function ICT contract?

For envisaged ICT arrangements supporting critical or important functions, financial entities must consider difficult substitution and multiple arrangements with the same or closely connected providers, and weigh alternative solutions' costs and benefits. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 29(1) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical/important-function arrangement assessment under Article 28(4)(c); not Article 31 critical-provider designation. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What concentration evidence is needed before another critical-function ICT contract?

Buyer evidence still required

  • Provider group and relationship mapping
  • existing contracts
  • substitution assessment
  • alternative cost-benefit analysis

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Different brands or contract references do not establish independent substitutable providers.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Different brands or contract references do not establish independent substitutable providers.
  • Different brands or contract references do not establish independent substitutable providers.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Conflict assessment belongs before contracting

Question: What conflict evidence belongs in the pre-contract ICT review?

Before entering an ICT-services contractual arrangement, the financial entity must identify and assess conflicts of interest that the arrangement may cause. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(4)(e) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

In-scope financial entity and proposed ICT arrangement; not limited in this provision to critical functions. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What conflict evidence belongs in the pre-contract ICT review?

Buyer evidence still required

  • Conflict declarations
  • interests and decision roles
  • dated pre-contract assessment

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A signed contract alone does not show that conflicts were assessed before entry.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A signed contract alone does not show that conflicts were assessed before entry.
  • A signed contract alone does not show that conflicts were assessed before entry.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Consider insolvency, data recovery and foreign enforcement

Question: Would insolvency or third-country enforcement barriers impede urgent recovery of the financial entity's data?

For critical-function ICT arrangements, financial entities consider applicable provider-insolvency law and constraints on urgent data recovery; where the provider is established in a third country they also consider Union data-protection compliance and effective enforcement there. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 29(2), second and third subparagraphs · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

ICT services supporting critical or important functions; third-country considerations depend on provider establishment. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Would insolvency or third-country enforcement barriers impede urgent recovery of the financial entity's data?

Buyer evidence still required

  • Provider establishment and service scope
  • Insolvency-law and urgent-recovery assessment
  • Data-protection and enforcement analysis where applicable

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A contractual return clause does not demonstrate enforceability or successful recovery during insolvency.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A contractual return clause does not demonstrate enforceability or successful recovery during insolvency.
  • A contractual return clause does not demonstrate enforceability or successful recovery during insolvency.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Contract for implemented and tested contingency plans

Question: Does the contract require contingency implementation and testing, and what dated evidence is available for the relevant service?

Critical-function ICT contracts require the provider to implement and test business-contingency plans and maintain security measures, tools and policies appropriate to the financial entity's regulatory framework. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(3)(c) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

ICT services supporting critical or important functions; the legal requirement alone is not evidence a test was performed or passed. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does the contract require contingency implementation and testing, and what dated evidence is available for the relevant service?

Buyer evidence still required

  • Executed contingency and security requirements
  • Service-specific test records
  • Security control scope and unresolved findings

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An untested generic continuity policy does not establish the provider's tested service capability.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An untested generic continuity policy does not establish the provider's tested service capability.
  • An untested generic continuity policy does not establish the provider's tested service capability.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Contract for participation in applicable threat-led testing

Question: Does the contract support provider cooperation if the financial entity is subject to an authorised TLPT exercise?

Critical-function ICT contracts oblige the provider to participate and cooperate fully in the financial entity's threat-led penetration testing as referred to in Articles 26 and 27. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(3)(d), referring to Articles 26 and 27 · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

This contractual provision does not make every financial entity subject to mandatory TLPT or authorise any live testing; entity selection and test governance must separately be established under Articles 26 and 27. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does the contract support provider cooperation if the financial entity is subject to an authorised TLPT exercise?

Buyer evidence still required

  • Executed TLPT cooperation clause
  • Entity applicability and test scope
  • Separate authority and safeguards for any test

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A legal-source record or MCP discovery response is not permission to execute a penetration test.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A legal-source record or MCP discovery response is not permission to execute a penetration test.
  • A legal-source record or MCP discovery response is not permission to execute a penetration test.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Contract for protected data access, recovery and return

Question: Do the executed clauses cover data protection and accessible recovery across the specified exit events?

ICT contracts contain provisions on data availability, authenticity, integrity and confidentiality, and access, recovery and return of personal and non-personal data in an easily accessible format on provider insolvency, resolution, discontinuation or contract termination. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(2)(c)-(d) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

All covered ICT contracts; documentary clauses do not prove runtime protection, completed return or deletion. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do the executed clauses cover data protection and accessible recovery across the specified exit events?

Buyer evidence still required

  • Data inventory and format requirements
  • Executed protection and return clauses
  • Exit-event mapping

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A privacy policy addressing only personal data or deletion is not the complete DORA return provision.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A privacy policy addressing only personal data or deletion is not the complete DORA return provision.
  • A privacy policy addressing only personal data or deletion is not the complete DORA return provision.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Critical-function audit rights have a specific microenterprise alternative

Question: Can a provider audit summary replace our critical-function contractual audit rights?

Critical/important-function ICT contracts require ongoing performance-monitoring rights with access, inspection and audit provisions. The final subparagraph permits a microenterprise financial entity to agree delegation to an independent third party appointed by the provider, with information and assurance available at any time. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(3)(e) and Article 30(3), final subparagraph (microenterprise derogation) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical/important-function ICT arrangement; include Article 30(3)(e)(ii) alternative assurance where other clients' rights are affected; microenterprise exception is specific. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a provider audit summary replace our critical-function contractual audit rights?

Buyer evidence still required

  • Full audit-rights clause
  • parties and function scope
  • any affected-client alternative
  • microenterprise status and agreed independent delegation

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A supplier certificate does not automatically replace rights; neither may the express microenterprise derogation be ignored.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A supplier certificate does not automatically replace rights; neither may the express microenterprise derogation be ignored.
  • A supplier certificate does not automatically replace rights; neither may the express microenterprise derogation be ignored.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Define services and permitted subcontracting

Question: Does the contract identify the services and any permitted critical-function subcontracting conditions?

ICT contracts include a clear and complete description of all functions and ICT services, indicating whether subcontracting of services supporting critical or important functions or material parts is permitted and the applicable conditions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(2)(a) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

All ICT contracts for service description; the subcontract-permission limb is tied to critical or important functions or material parts. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does the contract identify the services and any permitted critical-function subcontracting conditions?

Buyer evidence still required

  • Executed service schedule
  • Function mapping
  • Subcontracting permission and conditions

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A public subprocessor list does not itself establish the negotiated permission or service scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A public subprocessor list does not itself establish the negotiated permission or service scope.
  • A public subprocessor list does not itself establish the negotiated permission or service scope.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Direct-provider and subcontractor register scopes differ

Question: Which direct providers and subcontractors belong in the register?

Register templates must include relevant information on all ICT services from direct providers, and information on all subcontractors effectively underpinning critical/important-function ICT services or material parts. Annex I B_05.02 additionally includes all ICT intra-group service providers and, where an intra-group provider uses subcontractors, at least the first extra-group subcontractor even if the service does not support a critical or important function. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Implementing Regulation (EU) 2024/2956: standard register-of-information templates. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 3(2); Annex I instructions for B_05.02 (ICT service supply chains) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

2024/2956 Article 3(2), subject to DORA scope; do not generalise the subcontractor limb to every downstream service irrespective of function. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Which direct providers and subcontractors belong in the register?

Buyer evidence still required

  • Direct ICT-service inventory
  • criticality/function map
  • effectively-underpinning chain analysis
  • register inclusion rationale
  • Intra-group status and chain map identifying the first extra-group subcontractor
  • Non-critical service review for the intra-group chain exception

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A complete direct-provider list does not prove completeness of the relevant underpinning subcontractor chain. Excluding the first extra-group subcontractor behind an intra-group provider solely because the service is non-critical conflicts with Annex I B_05.02.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A complete direct-provider list does not prove completeness of the relevant underpinning subcontractor chain. Excluding the first extra-group subcontractor behind an intra-group provider solely because the service is non-critical conflicts with Annex I B_05.02.
  • Excluding the first extra-group subcontractor behind an intra-group provider solely because the service is non-critical conflicts with Annex I B_05.02.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Distinguish alternatives from an unperformed assessment

Question: Has the alternatives assessment been performed, and is the result represented without confusing absence of assessment with absence of alternatives?

For each provider supporting a critical or important function the alternative-provider assessment is performed; corrected B_07.01.0110 distinguishes Yes, No and option 3 Assessment not performed, while additional identification information in .0120 is optional when Yes. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Implementing Regulation (EU) 2024/2956: standard register-of-information templates. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Annex I B_07.01.0110-.0120, as corrected · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical-function ICT-service assessment template; an available 'not performed' reporting code does not waive the assessment requirement or mean no alternatives exist. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Has the alternatives assessment been performed, and is the result represented without confusing absence of assessment with absence of alternatives?

Buyer evidence still required

  • Dated alternatives assessment
  • Result and evidence basis
  • Corrected .0110 code mapping and optional .0120 details

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Reporting option 3 does not establish either compliance with the assessment duty or that there are no alternative providers.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Reporting option 3 does not establish either compliance with the assessment duty or that there are no alternative providers.
  • Reporting option 3 does not establish either compliance with the assessment duty or that there are no alternative providers.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Distinguish storage and processing locations in the register

Question: Does the reporting evidence distinguish temporary storage, data at rest and processing locations without collapsing multiple countries?

The register asks whether the ICT service foresees storage even temporarily, records data-at-rest countries when storage is Yes, and processing countries where processing is foreseen; multiple countries use additional rows and the fields have their stated applicability conditions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Implementing Regulation (EU) 2024/2956: standard register-of-information templates. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Annex I B_02.02.0140-.0160 · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

B_02.02.0140 is mandatory for critical/important-function services; .0150 is mandatory if .0140 is Yes; .0160 is mandatory if the service is based on or foresees processing. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does the reporting evidence distinguish temporary storage, data at rest and processing locations without collapsing multiple countries?

Buyer evidence still required

  • Service storage and processing description
  • Country evidence for each activity
  • Conditional field and row mapping

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A supplier headquarters address is not evidence of where data is stored or processed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A supplier headquarters address is not evidence of where data is stored or processed.
  • A supplier headquarters address is not evidence of where data is stored or processed.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Document the timeline for necessary contract adjustments

Question: Is there a documented and justified plan for necessary subcontracting contract changes?

Contract changes necessary to comply with the subcontracting regulation are implemented in a timely manner and as soon as possible, and the financial entity documents the planned implementation timeline. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 4(2) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Relevant financial-entity/provider contracts for critical or important functions or material parts; no universal grace-period date is created by this clause. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Is there a documented and justified plan for necessary subcontracting contract changes?

Buyer evidence still required

  • Gap assessment against effective requirements
  • Planned implementation timeline
  • Progress and unresolved contractual constraints

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A self-selected future deadline is not an exemption from timely implementation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A self-selected future deadline is not an exemption from timely implementation.
  • A self-selected future deadline is not an exemption from timely implementation.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Exit clauses need an adequate transition period

Question: What transition evidence is needed for a critical ICT exit clause?

Critical/important-function ICT contracts must include exit strategies with a mandatory adequate transition period during which services continue and migration to another provider or in-house solution is possible, consistent with complexity. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(3)(f) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical/important-function ICT services; no fixed number of transition days is specified here. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What transition evidence is needed for a critical ICT exit clause?

Buyer evidence still required

  • Transition-period clause
  • continuity obligations
  • migration/in-house plan and service complexity assessment

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A termination right alone does not establish a transition period adequate for this service.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A termination right alone does not establish a transition period adequate for this service.
  • A termination right alone does not establish a transition period adequate for this service.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Flow down access, inspection and audit rights

Question: Do subcontractor terms and the chain of contracts preserve exercisable access, inspection and audit rights?

The financial entity's contract specifies subcontractor access, inspection and audit rights for the entity and relevant competent and resolution authorities corresponding to DORA Article 30(3)(e); precontract assessment also checks granted access and inspection rights and obstacles to exercising them. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 4(1)(j), read with Article 3(1)(d),(j) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical-function subcontracting or material parts; Article 30(3)(e) and its relevant qualifications control the rights, not a new unrestricted data entitlement. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Do subcontractor terms and the chain of contracts preserve exercisable access, inspection and audit rights?

Buyer evidence still required

  • Direct and subcontractor contract clauses
  • Rights comparison to Article 30(3)(e)
  • Obstacles and authority assessment

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A direct-provider audit clause that is not supported through the relevant subcontract cannot alone establish flow-down.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A direct-provider audit clause that is not supported through the relevant subcontract cannot alone establish flow-down.
  • A direct-provider audit clause that is not supported through the relevant subcontract cannot alone establish flow-down.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Flow down contingency and security requirements

Question: Are the relevant contingency service levels and security requirements present in the subcontract?

The direct contract requires provider-subcontractor arrangements to contain the DORA Article 30(3)(c) business-contingency requirements with subcontractor service levels and the specified ICT security standards and additional requirements. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 4(1)(h)-(i) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical-function subcontracting or material parts; contract flow-down does not establish implementation or successful tests. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Are the relevant contingency service levels and security requirements present in the subcontract?

Buyer evidence still required

  • Direct contract flow-down obligation
  • Relevant subcontract clauses and service levels
  • Security requirements mapping

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A generic promise to follow industry practice does not identify the required contingency service levels and security terms.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A generic promise to follow industry practice does not identify the required contingency service levels and security terms.
  • A generic promise to follow industry practice does not identify the required contingency service levels and security terms.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Incident assistance cost determined beforehand

Question: What cost and assistance terms should an ICT incident clause specify?

ICT contracts must require provider assistance for an ICT incident related to the supplied service, at no additional cost or at a cost determined ex ante. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(2)(f) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Related ICT incident and the contracted ICT service; does not make all supplier support universally free. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What cost and assistance terms should an ICT incident clause specify?

Buyer evidence still required

  • Incident-assistance clause
  • agreed scope
  • ex-ante cost schedule or no-additional-cost term

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A general support subscription does not establish the required related-incident assistance cost terms.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A general support subscription does not establish the required related-incident assistance cost terms.
  • A general support subscription does not establish the required related-incident assistance cost terms.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Keep missing assessments distinct from recovery targets

Question: Does the register distinguish unperformed assessments and undefined recovery objectives from assessed operational values?

The corrected function template records criticality as Yes, No or Assessment not performed, uses 9999-12-31 when its assessment is not performed, and reports RTO/RPO in hours: values below one hour as 1, and undefined objectives as 0. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Implementing Regulation (EU) 2024/2956: standard register-of-information templates. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Annex I B_06.01.0050, .0070, .0080 and .0090, as corrected · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Corrected function fields B_06.01.0050, .0070, .0080 and .0090; these are reporting conventions, not evidence of zero downtime or actual recovery performance. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does the register distinguish unperformed assessments and undefined recovery objectives from assessed operational values?

Buyer evidence still required

  • Function assessment and date
  • Actual defined RTO and RPO
  • Mapping to corrected reporting codes

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A reported 0 for undefined RTO is not a zero-hour recovery commitment; the sentinel date is not an assessment date.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A reported 0 for undefined RTO is not a zero-hour recovery commitment; the sentinel date is not an assessment date.
  • A reported 0 for undefined RTO is not a zero-hour recovery commitment; the sentinel date is not an assessment date.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Location terms include advance change notification

Question: Which location and change-notice terms belong in our ICT contract?

ICT contracts must state regions or countries for contracted/subcontracted service delivery and data processing, including storage, and require advance notification of envisaged location changes. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(2)(b) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

All in-scope ICT-service arrangements under Article 30(2); actual location and notice performance require separate facts. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Which location and change-notice terms belong in our ICT contract?

Buyer evidence still required

  • Contract location schedule
  • data processing/storage mapping
  • advance-notification clause
  • dated notices if changes occur

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A selected cloud region does not establish the full contracted/subcontracted location boundary.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A selected cloud region does not establish the full contracted/subcontracted location boundary.
  • A selected cloud region does not establish the full contracted/subcontracted location boundary.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Material subcontract changes need the contractual review window

Question: When can a material subcontracting change proceed under the agreed notice process?

The contract must provide timely information about intended material subcontracting changes and a reasonable approval/objection notice period; changes may be implemented after approval or after no objection by the end of that period. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 5(1)-(3) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical/important-function ICT services or material parts under 2025/532; timely approval may permit an earlier change; no objection is not proof of a positive approval event. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: When can a material subcontracting change proceed under the agreed notice process?

Buyer evidence still required

  • Material-change notice
  • contractual period
  • delivery/time evidence
  • approval or objection records
  • implementation timing

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Do not invent an unconditional explicit-consent requirement or infer positive approval from silence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Do not invent an unconditional explicit-consent requirement or infer positive approval from silence.
  • Do not invent an unconditional explicit-consent requirement or infer positive approval from silence.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Multiple valid register values need additional rows

Question: How should multiple valid values be represented in register templates?

Each register data element must contain a single value; when multiple values are valid for a data element, the financial entity adds one corresponding-template row for each valid value. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Implementing Regulation (EU) 2024/2956: standard register-of-information templates. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 4(2) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

2024/2956 Article 4(2); apply the relevant Annex template instructions and keys; no claim of regulator submission acceptance. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: How should multiple valid values be represented in register templates?

Buyer evidence still required

  • Applicable template version
  • field instructions
  • row/key mapping
  • multi-value source evidence

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A comma-separated list in one data element is not the specified additional-row representation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A comma-separated list in one data element is not the specified additional-row representation.
  • A comma-separated list in one data element is not the specified additional-row representation.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Notify planned critical arrangements and changed criticality

Question: Has the planned arrangement or changed function classification been notified through the applicable supervisory process?

Financial entities inform the competent authority in a timely manner about planned ICT arrangements supporting critical or important functions and when a function becomes critical or important. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(3), fifth subparagraph · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical or important functions; timely notification does not establish supervisory approval or a universal fixed deadline. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Has the planned arrangement or changed function classification been notified through the applicable supervisory process?

Buyer evidence still required

  • Function classification and change date
  • Planned arrangement scope
  • Dated authority notification

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A catalogue entry or signed supplier contract is not proof of notification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A catalogue entry or signed supplier contract is not proof of notification.
  • A catalogue entry or signed supplier contract is not proof of notification.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Outsourcing ICT does not transfer the financial entity's responsibility

Question: Can an ICT outsourcing contract transfer our DORA accountability?

A financial entity using ICT services for its business remains responsible for its obligations under DORA and applicable financial-services law. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(1)(a) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Financial entity subject to DORA Article 2; no supplier certification or transfer of statutory responsibility is inferred. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an ICT outsourcing contract transfer our DORA accountability?

Buyer evidence still required

  • Accountability allocation
  • signed ICT contract
  • financial-entity role and scope assessment

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Contractual delegation does not by itself discharge the financial entity's statutory responsibility.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Contractual delegation does not by itself discharge the financial entity's statutory responsibility.
  • Contractual delegation does not by itself discharge the financial entity's statutory responsibility.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Periodic reassessment of subcontracting risks

Question: Does periodic reassessment address changes in the business environment, supported functions, ICT threats, concentration and geopolitical risks?

Financial entities using relevant subcontracted ICT services must periodically repeat the Article 3(1)(f)-(j) assessment against business-environment changes, including supported functions, ICT threats, concentration and geopolitical risks. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 3(2) read with 3(1)(f)-(j) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical/important-function ICT services or material parts; periodic duty covers the specified f-j assessments, not an invented uniform frequency. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does periodic reassessment address changes in the business environment, supported functions, ICT threats, concentration and geopolitical risks?

Buyer evidence still required

  • Previous and current f-j assessment
  • business/function changes
  • threat, concentration and geopolitical inputs
  • review dates

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unchanged initial onboarding assessment does not show periodic reassessment against changed conditions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unchanged initial onboarding assessment does not show periodic reassessment against changed conditions.
  • An unchanged initial onboarding assessment does not show periodic reassessment against changed conditions.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Precontract classification, conditions and due diligence

Question: Is the decision to contract supported by a dated classification, risk and provider-suitability assessment?

Before entering an ICT arrangement, financial entities assess critical-function support and supervisory contracting conditions, identify relevant risks including concentration, and undertake due diligence to establish prospective provider suitability. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(4)(a)-(d) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

All ICT arrangements; enhanced critical-function conditions apply only where classification supports them. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Is the decision to contract supported by a dated classification, risk and provider-suitability assessment?

Buyer evidence still required

  • Proposed service and function map
  • Supervisory conditions assessment
  • Risk and due-diligence decision

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A provider marketing claim or ISO badge alone does not establish this financial entity's suitability assessment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A provider marketing claim or ISO badge alone does not establish this financial entity's suitability assessment.
  • A provider marketing claim or ISO badge alone does not establish this financial entity's suitability assessment.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Predetermine risk-based audit scope and frequency

Question: Is the audit programme tied to risk, defined scope and applicable supervisory instructions?

When exercising provider access, inspection and audit rights, financial entities predetermine audit and inspection frequency and areas on a risk basis, following commonly accepted audit standards and supervisory instructions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(6), first subparagraph · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Exercise of ICT-provider audit rights; no mandatory universal audit interval is imposed by this clause. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is the audit programme tied to risk, defined scope and applicable supervisory instructions?

Buyer evidence still required

  • Risk assessment
  • Audit programme and scope
  • Applicable standards and instructions

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An annual audit template without a risk-based rationale is not sufficient evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An annual audit template without a risk-based rationale is not sufficient evidence.
  • An annual audit template without a risk-based rationale is not sufficient evidence.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Preserve contractual termination circumstances

Question: Does the contract preserve termination rights for each relevant DORA circumstance?

Financial entities ensure ICT arrangements may be terminated for significant legal or contractual breach, monitored circumstances capable of altering the performance of functions, evidenced ICT-risk-management weaknesses, or impeded effective supervision. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(7)(a)-(d) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

All ICT arrangements; the provision requires terminability, not automatic termination upon every allegation. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does the contract preserve termination rights for each relevant DORA circumstance?

Buyer evidence still required

  • Executed termination clauses
  • Monitoring and escalation criteria
  • Applicable-law and supervision review

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unverified allegation is not an established breach or automatic instruction to terminate.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unverified allegation is not an established breach or automatic instruction to terminate.
  • An unverified allegation is not an established breach or automatic instruction to terminate.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Preserve remedies for unacceptable subcontract changes

Question: Do objection handling and termination clauses cover each of the specified subcontracting violations?

If an intended material subcontract change exceeds risk tolerance, the financial entity informs the provider, objects and requests modifications before the notice period ends. The contract preserves termination rights for implementation despite such objection and requested modifications, early implementation without approval, or subcontracting not explicitly permitted. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 6(a)-(c), read with Article 5(4) and Article 4(1)(l) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical-function subcontracting or material parts; these are contractual remedies, not instructions for an agent to terminate a service. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do objection handling and termination clauses cover each of the specified subcontracting violations?

Buyer evidence still required

  • Risk-tolerance decision and timely objection
  • Provider notice and implementation chronology
  • Executed termination-right clauses

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Silence at the end of a reasonable notice period is not the same as an unresolved objection; a record does not execute termination.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Silence at the end of a reasonable notice period is not the same as an unresolved objection; a record does not execute termination.
  • Silence at the end of a reasonable notice period is not the same as an unresolved objection; a record does not execute termination.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Provide cooperation with competent and resolution authorities

Question: Does the contract provide the required authority cooperation while preserving verification of the requesting authority?

ICT contracts oblige the provider to cooperate fully with the financial entity's competent and resolution authorities, including persons appointed by them. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(2)(g) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

All covered ICT arrangements; a clause does not itself grant an unverified caller authority to obtain data. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does the contract provide the required authority cooperation while preserving verification of the requesting authority?

Buyer evidence still required

  • Executed cooperation clause
  • Competent and resolution authority mapping
  • Request-authority verification procedure

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A caller declaring itself a regulator is not thereby authorised to receive records.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A caller declaring itself a regulator is not thereby authorised to receive records.
  • A caller declaring itself a regulator is not thereby authorised to receive records.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Provider names do not replace the required legal identifiers

Question: Which legal identifiers must support the provider register entry?

Financial entities identify ICT providers that are legal persons with a valid active LEI or EUID, both where available; for relevant registered underpinning subcontractors they ensure this through the direct provider. Individuals acting in a business capacity are excepted. Under Annex I B_05.01.0020, legal persons not established in the Union use LEI only; the 19 September 2025 corrigendum retains this restriction. Establishment and legal-person status must be established before selecting the identifier type. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Implementing Regulation (EU) 2024/2956: standard register-of-information templates. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 3(5)-(6); Annex I B_05.01.0020, as corrected by OJ L 90725 of 19 September 2025 · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

2024/2956 Article 3(5)-(6); direct and subcontractor scope differs; do not require both identifiers where both are not available. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Which legal identifiers must support the provider register entry?

Buyer evidence still required

  • Legal-person/individual classification
  • current LEI validity or EUID
  • availability of both
  • direct-provider subcontractor identifier evidence
  • Provider legal-person status and country of establishment
  • LEI for any legal person not established in the Union
  • Corrected B_05.01.0020 identifier-type mapping

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A trading name or an expired LEI alone does not establish the required identification; individuals have an express exception. A non-EU legal person identified only with EUID does not satisfy the LEI-only register instruction; an individual acting in a business capacity has a different permitted identifier boundary.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A trading name or an expired LEI alone does not establish the required identification; individuals have an express exception. A non-EU legal person identified only with EUID does not satisfy the LEI-only register instruction; an individual acting in a business capacity has a different permitted identifier boundary.
  • A non-EU legal person identified only with EUID does not satisfy the LEI-only register instruction; an individual acting in a business capacity has a different permitted identifier boundary.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Provider selection must assess subcontractor visibility

Question: What subcontractor visibility should we assess before approving the ICT arrangement?

Before entering the relevant arrangement, the financial entity must assess the provider's ability to identify all subcontractors providing critical/important-function ICT services or material parts, notify/inform the entity and supply information necessary for the Article 3 assessment. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 3(1)(b) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Delegated Regulation 2025/532; financial entity deciding whether the provider may subcontract critical/important-function ICT services or material parts. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What subcontractor visibility should we assess before approving the ICT arrangement?

Buyer evidence still required

  • Proposed subcontracting scope
  • provider identification/notification process
  • chain information and assessment record

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A partial supplier list does not establish the provider's ability to identify the entire relevant subcontracting scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A partial supplier list does not establish the provider's ability to identify the entire relevant subcontracting scope.
  • A partial supplier list does not establish the provider's ability to identify the entire relevant subcontracting scope.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Register rank identifies contractual distance

Question: Does register rank measure supplier risk or supply-chain position?

The financial entity assigns supply-chain rank as an integer at least one: the direct provider is rank one and a subcontractor is higher than one. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Implementing Regulation (EU) 2024/2956: standard register-of-information templates. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 2 · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

2024/2956 definitions and Article 3(2) register inclusion scope; rank indicates position, not risk quality. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does register rank measure supplier risk or supply-chain position?

Buyer evidence still required

  • Direct contractual relationship
  • chain edges
  • rank entries
  • inclusion scope

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Rank is not a trust score, criticality classification or evidence of provider quality.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Rank is not a trust score, criticality classification or evidence of provider quality.
  • Rank is not a trust score, criticality classification or evidence of provider quality.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Register reporting and supervisory access

Question: What reporting and register-access evidence must the financial entity retain for its competent authority?

Financial entities report at least yearly on the number of new ICT arrangements, provider categories, contract types, services and functions, and make the full register or requested sections and necessary supervisory information available on competent-authority request. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(3), third and fourth subparagraphs · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

All ICT contractual arrangements within DORA Article 28(3); no single EU-wide annual submission date is specified here. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What reporting and register-access evidence must the financial entity retain for its competent authority?

Buyer evidence still required

  • Annual reporting scope and submission record
  • Current register extract
  • Authority request and response record

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An internal supplier list alone is not evidence of the required reporting or response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An internal supplier list alone is not evidence of the required reporting or response.
  • An internal supplier list alone is not evidence of the required reporting or response.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Review register accuracy and correct errors promptly

Question: What review and correction evidence supports the register's accuracy and consolidation consistency?

Financial entities ensure accurate and consistent register information, review it regularly and promptly correct detected errors or discrepancies; responsible group entities ensure entity-level information is correct and consistent with consolidation, applying the stated six data-quality principles. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Implementing Regulation (EU) 2024/2956: standard register-of-information templates. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 3(3)-(4) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Register at the relevant entity, sub-consolidated or consolidated level; schema validity alone is not complete data quality. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What review and correction evidence supports the register's accuracy and consolidation consistency?

Buyer evidence still required

  • Register review record
  • Detected discrepancies and correction trail
  • Cross-level reconciliation

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A technically accepted submission does not demonstrate factual accuracy, completeness or effective correction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A technically accepted submission does not demonstrate factual accuracy, completeness or effective correction.
  • A technically accepted submission does not demonstrate factual accuracy, completeness or effective correction.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Set provider participation conditions for resilience training

Question: Are the relevant provider participation conditions documented for security awareness and resilience training?

ICT contracts state conditions for provider participation in the financial entity's security-awareness programmes and digital operational-resilience training under Article 13(6); provider inclusion is where appropriate under that provision. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(2)(i), referring to Article 13(6) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Covered ICT arrangements; contract conditions do not require every provider employee to attend every internal programme. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Are the relevant provider participation conditions documented for security awareness and resilience training?

Buyer evidence still required

  • Training needs and relevance assessment
  • Executed participation conditions
  • Programme scope

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unspecified obligation to train all subcontractor staff is not established by this clause.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unspecified obligation to train all subcontractor staff is not established by this clause.
  • An unspecified obligation to train all subcontractor staff is not established by this clause.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Specify measurable critical-service levels and change reporting

Question: Can the financial entity monitor agreed critical-service performance and receive material-change reports?

Critical-function ICT contracts include full service-level descriptions with precise quantitative and qualitative performance targets for monitoring and timely corrective action, plus notice periods and provider reporting of developments that may materially affect delivery against agreed levels. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(3)(a)-(b) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

ICT services supporting critical or important functions; no numerical availability target or universal notice period is prescribed here. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can the financial entity monitor agreed critical-service performance and receive material-change reports?

Buyer evidence still required

  • Executed SLA with measurable targets
  • Reporting and notice clauses
  • Corrective-action criteria

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A marketing uptime claim without the contracted scope, measurements and reporting duties is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A marketing uptime claim without the contracted scope, measurements and reporting duties is insufficient.
  • A marketing uptime claim without the contracted scope, measurements and reporting duties is insufficient.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Specify monitoring and reporting along the subcontract chain

Question: Are monitoring and reporting responsibilities assigned at both contractual levels?

The direct contract requires provider monitoring of relevant subcontracted services and reporting towards the financial entity; the provider's subcontract specifies monitoring and reporting back to the provider and, where agreed, to the financial entity. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 4(1)(b),(c),(f) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Critical or important functions or material parts; direct subcontractor reporting to the financial entity is qualified by 'where agreed'. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Are monitoring and reporting responsibilities assigned at both contractual levels?

Buyer evidence still required

  • Direct-provider monitoring and reporting clauses
  • Subcontractor reporting clauses
  • Agreed direct reporting where applicable

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Mandatory direct reporting from every subcontractor to the financial entity is not established without the agreement qualification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Mandatory direct reporting from every subcontractor to the financial entity is not established without the agreement qualification.
  • Mandatory direct reporting from every subcontractor to the financial entity is not established without the agreement qualification.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: Technical complexity requires competent auditors

Question: What competence evidence is needed for a technically complex ICT audit?

For ICT contractual arrangements entailing high technical complexity, the financial entity must verify appropriate skills and knowledge of internal, external or pooled auditors. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(6), second subparagraph · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Article 2 financial-entity scope; trigger is high technical complexity; separate from audit scheduling. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What competence evidence is needed for a technically complex ICT audit?

Buyer evidence still required

  • Complexity assessment
  • assigned auditor skills and knowledge
  • relevant audit scope

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A generic auditor designation does not establish skills for the actual complex service.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A generic auditor designation does not establish skills for the actual complex service.
  • A generic auditor designation does not establish skills for the actual complex service.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: The contract must place continuity responsibility across the chain

Question: What chain-continuity term is needed when a subcontractor fails?

The financial-entity/provider contract must specify that the provider ensures continuity of critical/important-function ICT services throughout the subcontractor chain if a subcontractor fails to meet its contractual obligations. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Delegated Regulation (EU) 2025/532: ICT subcontracting requirements. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22

Provision: Article 4(1)(g) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Delegated Regulation 2025/532 Article 4 conditions; critical/important-function services; contractual obligation is distinct from demonstrated continuity. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What chain-continuity term is needed when a subcontractor fails?

Buyer evidence still required

  • Main contract continuity allocation
  • relevant subcontract chain
  • contingency and performance evidence for any claim of execution

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A subcontractor's separate availability promise does not establish the provider's full chain-continuity obligation or actual continuity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A subcontractor's separate availability promise does not establish the provider's full chain-continuity obligation or actual continuity.
  • A subcontractor's separate availability promise does not establish the provider's full chain-continuity obligation or actual continuity.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: The full ICT contract must include the service levels

Question: What complete contract evidence should the ICT procurement file contain?

Financial-entity and ICT-provider rights and obligations must be clearly allocated in writing; the full contract includes SLAs in one written document available on paper or another downloadable, durable, accessible format. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 30(1) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

ICT-services contractual arrangement in DORA scope; source does not prescribe a particular file format. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What complete contract evidence should the ICT procurement file contain?

Buyer evidence still required

  • Full executed contract and SLAs
  • version and parties
  • durable accessible copy

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A marketing SLA page alone is not the full durable contractual record.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A marketing SLA page alone is not the full durable contractual record.
  • A marketing SLA page alone is not the full durable contractual record.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: The information register is broader than critical-function suppliers

Question: Can our DORA register omit non-critical ICT services?

Financial entities must maintain and update the information register for all contractual arrangements for ICT services, distinguishing critical/important-function arrangements from others. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(3), first and second subparagraphs · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Financial entities in DORA scope; entity, sub-consolidated and consolidated levels as applicable. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can our DORA register omit non-critical ICT services?

Buyer evidence still required

  • ICT contract inventory
  • function mapping
  • register scope reconciliation

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A list of critical vendors alone does not establish coverage of all in-scope ICT arrangements.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A list of critical vendors alone does not establish coverage of all in-scope ICT arrangements.
  • A list of critical vendors alone does not establish coverage of all in-scope ICT arrangements.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DORA: The third-party strategy duty has explicit entity exceptions

Question: Which entities must maintain the Article 28(2) strategy?

Financial entities other than Article 16(1), first-subparagraph entities and microenterprises must adopt and regularly review an ICT third-party risk strategy, including the critical/important-function ICT-services policy. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Source: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. Documentation checked 2026-11-16; no deployment validation is claimed.

Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17

Provision: Article 28(2) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider

DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.

Article 2 scope plus Article 28(2) exclusions; individual and, where relevant, sub-consolidated/consolidated levels. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Which entities must maintain the Article 28(2) strategy?

Buyer evidence still required

  • Entity classification
  • microenterprise assessment
  • dated strategy and policy review

Review inference: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.

Suggested review condition: Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Do not turn the strategy exception into a blanket exemption from DORA.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual entity scope and implementation are unestablished without buyer evidence,No supplier, deployment, independent buyer demand or paid-product fit verified

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck controlling official texts, corrigenda, applicable authority instructions and dated service-specific documents before relying on this condition.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Do not turn the strategy exception into a blanket exemption from DORA.
  • Do not turn the strategy exception into a blanket exemption from DORA.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

DPoP authorization-code proof-key binding

Question: What establishes that a DPoP token exchange used the proof key bound to its authorization code?

RFC 9449 defines optional dpop_jkt to bind an authorization request and its code to a proof-key thumbprint. At token exchange the authorization server must reject a proof whose key does not match that original value. The parameter can be combined with PKCE; similar injection protection requires a unique DPoP key per authorization request and is not a universal PKCE replacement.

Source: IETF RFC 9449. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What establishes that a DPoP token exchange used the proof key bound to its authorization code?

Buyer evidence still required

  • Original dpop_jkt
  • Token-request proof public key
  • PKCE and key-per-request policy

Review inference: Check the optional dpop_jkt authorization-code binding at token exchange. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. The proof-key thumbprint must match the original request binding; use is optional and is not a blanket replacement for PKCE.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 10 in IETF RFC 9449 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The proof-key thumbprint must match the original request binding; use is optional and is not a blanket replacement for PKCE.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DPoP nonce server scope

Question: Can a client reuse one DPoP nonce across authorization and resource servers?

RFC 9449 allows authorization servers and resource servers to supply DPoP nonces. A nonce must be used only at the issuing server and must not be confused with another server's nonce or an OpenID Connect nonce. Authorization-server challenges use a 400 response; resource-server challenges use 401 with the DPoP authentication challenge. Retry state must retain the issuing-server identity.

Source: IETF RFC 9449. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a client reuse one DPoP nonce across authorization and resource servers?

Buyer evidence still required

  • Issuing server and endpoint
  • Nonce challenge and response status
  • Per-server retry state

Review inference: Bind a DPoP nonce to its issuing authorization or resource server during retry. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Server-specific nonces cannot be interchanged; authorization-server and resource-server challenge status codes differ.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 8; 9 in IETF RFC 9449 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Server-specific nonces cannot be interchanged; authorization-server and resource-server challenge status codes differ.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DPoP proof and client identity binding

Question: Does a valid DPoP proof directly establish the authenticated client's identity?

RFC 9449 states that, when used with client authentication, DPoP is coincident with that authentication in the same TLS tunnel rather than directly cryptographically bound to it. The URI can partly limit copying risks, but additional authentication binding is outside this specification. A valid proof of key possession is not by itself a complete authenticated-client identity claim.

Source: IETF RFC 9449. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a valid DPoP proof directly establish the authenticated client's identity?

Buyer evidence still required

  • Client authentication mechanism
  • DPoP proof key and request URI
  • Additional identity binding, if required

Review inference: Separate DPoP key possession from cryptographic binding to authenticated client identity. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Coincidence in one TLS tunnel is not a direct cryptographic client-authentication binding; additional mechanisms are outside this RFC.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 11.11 in IETF RFC 9449 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Coincidence in one TLS tunnel is not a direct cryptographic client-authentication binding; additional mechanisms are outside this RFC.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DPoP proof replay window

Question: Does a valid, recent DPoP proof establish that it has been used only once?

RFC 9449 requires accepting proofs only for a limited time and describes tracking jti values in the target-URI context to reject reuse. A valid proof can otherwise be replayed at the same endpoint. Shared-state limitations can make strict single-use tracking impractical. A server nonce can be reused with fresh proofs; nonce reuse alone is not equivalent to proof reuse.

Source: IETF RFC 9449. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a valid, recent DPoP proof establish that it has been used only once?

Buyer evidence still required

  • Accepted proof lifetime
  • Target URI and jti tracking
  • Server nonce and shared-state behavior

Review inference: Evaluate same-endpoint DPoP proof replay within a permitted time window. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Signature and endpoint checks do not ensure single use; jti tracking and its shared-state limits must be established.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 11.1 in IETF RFC 9449 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Signature and endpoint checks do not ensure single use; jti tracking and its shared-state limits must be established.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DPoP refresh-token binding by client type

Question: Do public and confidential OAuth clients bind refresh tokens to DPoP keys in the same way?

RFC 9449 requires a refresh token issued to a public client using DPoP to be bound to that proof key, checked on later refreshes. Confidential-client refresh tokens instead use the existing client binding and authentication requirement. A reviewer must establish the client type and actual binding; the access token's DPoP status alone does not describe every refresh credential.

Source: IETF RFC 9449. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do public and confidential OAuth clients bind refresh tokens to DPoP keys in the same way?

Buyer evidence still required

  • Client type and authentication policy
  • Refresh-token issuance binding
  • Proof key used on later token requests

Review inference: Distinguish refresh-token sender constraints for public and confidential DPoP clients. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Public-client refresh tokens bind to the proof key; confidential-client refresh tokens use the existing client authentication binding.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 5 in IETF RFC 9449 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Public-client refresh tokens bind to the proof key; confidential-client refresh tokens use the existing client authentication binding.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DPoP request content limitations

Question: Does DPoP verification prove that the request body, query terms and headers were unchanged?

RFC 9449 checks the proof's HTTP method and URI, excluding query and fragment components from URI comparison. Core DPoP does not protect the request body or general headers. A proof can therefore validate without authenticating business fields carried there. Identify the separate integrity protection before relying on an amount, recipient or payload as unchanged.

Source: IETF RFC 9449. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does DPoP verification prove that the request body, query terms and headers were unchanged?

Buyer evidence still required

  • Proof htm and htu
  • Business-field locations
  • TLS and any additional message integrity mechanism

Review inference: Decide whether a DPoP proof protects the business request body, headers or query terms. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Method and URI are checked, excluding query and fragment; body and general headers are not protected by core DPoP.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 4.3; 11.7 in IETF RFC 9449 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Method and URI are checked, excluding query and fragment; body and general headers are not protected by core DPoP.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DPoP token type and downgrade boundary

Question: Does a DPoP token request guarantee sender-constrained protection at every resource server?

RFC 9449 allows an authorization server to return Bearer even when a DPoP proof was supplied; clients requiring DPoP access-token protection must discard that response. A resource supporting both schemes must reject a DPoP-bound token presented as Bearer. Legacy Bearer-only resources have different compatibility behavior, so issuance and each resource's support must be established separately.

Source: IETF RFC 9449. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a DPoP token request guarantee sender-constrained protection at every resource server?

Buyer evidence still required

  • Returned token_type and key binding
  • Client required protection
  • Resource-server scheme support

Review inference: Distinguish requested DPoP protection, returned token_type and resource-server Bearer compatibility. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. A server can issue Bearer; dual-support resources must reject downgrade of a DPoP-bound token, while legacy resources do not establish that protection.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 5; 7.2 in IETF RFC 9449 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A server can issue Bearer; dual-support resources must reject downgrade of a DPoP-bound token, while legacy resources do not establish that protection.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Dremio MCP: Deployment mode and mock-result limits

Question: Does a successful Dremio MCP demonstration prove access to real project data?

The guide distinguishes hosted OAuth connections from self-hosted token configuration. Self-hosted modes expose data exploration, introspection or metrics, with optional view creation. Mock mode preserves tool names and schemas but returns placeholders; a successful mock call therefore does not validate data access.

Source: Dremio Cloud MCP connection guide. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted Cloud endpoint and separately configured self-hosted server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Dremio publishes the service and open-source server.

Documented by publisher. Dremio Cloud MCP connection guide

Purpose

Explore project data, system state or metrics.

Documented by publisher. Dremio Cloud MCP connection guide

Read capability

Tables, query results and configured diagnostic sources.

Documented by publisher. Dremio Cloud MCP connection guide

Write capability

Optional self-hosted configuration permits view creation.

Documented by publisher. Dremio Cloud MCP connection guide

Authentication

Hosted OAuth or self-hosted personal access token.

Documented by publisher. Dremio Cloud MCP connection guide

Permission surface

Project access, chosen mode and optional capabilities.

Documented by publisher. Dremio Cloud MCP connection guide

Data leaving the environment

Results reach the client; optional metrics add another source.

Review inference. Dremio Cloud MCP connection guide

Failure modes to consider

Mock success, wrong project and client incompatibility can mislead.

Review inference. Dremio Cloud MCP connection guide

Unknowns and applicability

Buyer mode, real data connection and effective permissions are unknown.

Not established

Suggested refusal or clarification condition

Do not present mock responses as production evidence.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Deployment modes, write options, project access and support policy.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save which integration evidence came from a real project versus a client-only demonstration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Drive download and export capability checks

Question: Does seeing Google Drive file metadata establish that an agent can download or export its content?

The Drive guide instructs callers to check capabilities.canDownload before downloading or exporting content. Blob downloads and Google Workspace exports use different methods; exports require a supported format and are subject to documented limits. A known file ID or readable metadata does not establish those content-access conditions.

Source: Download and export files | Google Drive | Google for Developers. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does seeing Google Drive file metadata establish that an agent can download or export its content?

Buyer evidence still required

  • File ID, type and current caller identity
  • capabilities.canDownload and required download/export method
  • Requested format, applicable limits and actual result

Review inference: Check the caller’s download capability and applicable file-type export path before promising a deliverable.

Suggested review condition: Refuse a complete export promise supported only by metadata visibility.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Current caller permissions and the actual exported artifact are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid promising file delivery before the principal and export method are qualified.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Export of every format merely because files.get metadata succeeds
  • Current caller permissions and the actual exported artifact are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Dropbox recovery: Plan windows and permanent deletion

Question: Does a Dropbox subscription guarantee every deleted file can be restored?

No. Dropbox ties recovery to the plan window, deletion type and restoration permissions. Permanently deleted files are outside normal recovery, and the page says Support cannot recover them or files outside available history. A product subscription alone does not prove recoverability of a particular file.

Source: Dropbox recovery limits and permanent deletion. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every deleted file remains recoverable because Dropbox is subscribed.

Buyer evidence still required

  • Applicable recovery period and deletion timestamp
  • Whether deletion was permanent or recoverable
  • Restoration authority and outcome for the relevant file

Suggested review condition: Require file-specific recovery evidence before promising restoration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck plan changes, retention windows and deletion events.

Optional saved evidence: Preserve the conditions behind a supplier recovery claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Dropbox: Regional file storage has a defined scope

Question: Does a Dropbox storage region prove every data category stays in that region?

Dropbox states that the selected server location applies to team file data permanently stored at rest. Migration has eligibility conditions and needs confirmation. That statement alone does not establish the location of every metadata, processing or connected-application flow.

Source: Dropbox regional storage applicability and migration eligibility. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A regional storage option proves all Dropbox-related data processing is regional.

Buyer evidence still required

  • Team storage-location or completed-migration confirmation
  • A data-category map distinguishing files at rest from other flows
  • Applicable documentation and contractual scope for the additional categories

Suggested review condition: Keep the claim limited to confirmed file data at rest until broader evidence is supplied.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck team migration, plan and connected-application data flows.

Optional saved evidence: Preserve the scope and unresolved categories behind a regional-storage review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

DSSE authenticated payload interpretation

Question: Does a valid DSSE signature permit an application to interpret its payload under any JSON schema?

DSSE 1.0.2 signs both the payload bytes and the payload-type string through its pre-authentication encoding. The type is intended to identify encoding and meaning, with application-specific types recommended over generic application/json. Verification must reject unsupported types and parsing failures. A valid signature therefore does not justify substituting another schema or ignoring the authenticated type.

Source: DSSE v1.0.2 — protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a valid DSSE signature permit an application to interpret its payload under any JSON schema?

Buyer evidence still required

  • Exact authenticated payload type
  • Supported schema and parser version
  • Signature and parsing results for the retained bytes

Review inference: Bind accepted evidence meaning to the authenticated application-specific type. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse interpretation under an unsupported or substituted payload schema.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Schema correctness, claimed facts and intended business authority were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Schema correctness, claimed facts and intended business authority were not verified.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DSSE key identifiers and trusted signers

Question: Can a DSSE keyid be used as authenticated evidence of the signer or signature algorithm?

DSSE 1.0.2 defines KEYID as an optional unauthenticated hint. It may narrow the set of keys to try but must not be used for security decisions. Verification instead checks the signature with acceptable trusted keys under cryptographic details agreed out of band. A matching keyid string therefore does not establish a trusted signer or algorithm.

Source: DSSE v1.0.2 — protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a DSSE keyid be used as authenticated evidence of the signer or signature algorithm?

Buyer evidence still required

  • Accepted key set and provenance
  • Agreed signature algorithm and key-selection policy
  • Actual signature verification result

Review inference: Select trusted verification keys independently of the envelope hint. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse signer or algorithm trust derived only from keyid.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual trust store and key ownership were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The actual trust store and key ownership were not verified.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DSSE verified bytes and application use

Question: Can a DSSE verifier reparse the original envelope after verification to obtain the application payload?

DSSE 1.0.2 requires the exact payload bytes verified to be the bytes passed to the application layer and explicitly forbids reparsing the envelope afterwards to retrieve the payload. A signature result over one decoded value cannot justify acting on another value obtained by a later parse. Evidence handoff therefore needs a stable binding between verification output and application input.

Source: DSSE v1.0.2 — protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a DSSE verifier reparse the original envelope after verification to obtain the application payload?

Buyer evidence still required

  • Decoded payload bytes retained at verification
  • Signature result and supported payload type
  • Application input binding and parsing path

Review inference: Preserve the verified payload through the application handoff. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse authenticated-payload claims when the application consumes a separately reparsed value.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No application implementation or parser differential was tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No application implementation or parser differential was tested.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Durable Task: External events and missing instances

Question: Will a Durable Task approval event wait for an orchestration instance that has not been created?

Microsoft documents buffering when an existing orchestration is not yet waiting for the named event. If no orchestration exists with the specified instance ID, the event is discarded. An event sent before instance creation therefore must not be treated as a retained approval; instance identity, existence and receipt need separate evidence.

Source: Microsoft Durable Task: External events. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Will a Durable Task approval event wait for an orchestration instance that has not been created?

Buyer evidence still required

  • Exact target instance ID, event name and non-secret correlation reference.
  • Instance existence and lifecycle at the time the event was sent.
  • Workflow-side event receipt and the action or decision it actually released.

Suggested review condition: Decline approval-delivered claims without receiver-side evidence for the intended existing instance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Exact target instance ID, event name and non-secret correlation reference. Instance existence and lifecycle at the time the event was sent. Workflow-side event receipt and the action or decision it actually released.

Optional saved evidence: An approval or recovery signal can be lost at the workflow boundary even when the sender intended it for later use.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Pre-creation event retention, proof of valid authorization or automatic resending
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Durable Task: Termination and continuing child work

Question: Does terminating a Durable Task orchestration stop the activities and sub-orchestrations it already launched?

The documented termination request is queued and the instance reaches Terminated later. Microsoft states that instance termination currently does not propagate: activity functions and sub-orchestrations run to completion even when the calling orchestration is terminated. Querying the parent status therefore does not establish the outcome of its child work.

Source: Microsoft Durable Task: Instance management. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does terminating a Durable Task orchestration stop the activities and sub-orchestrations it already launched?

Buyer evidence still required

  • Parent instance identifier, termination request and observed terminal status.
  • Launched activity and sub-orchestration identifiers with their individual outcomes.
  • External effects and any separately authorized cleanup or compensation results.

Suggested review condition: Decline an all-work-stopped conclusion until child execution and external-effect evidence is reconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Parent instance identifier, termination request and observed terminal status. Launched activity and sub-orchestration identifiers with their individual outcomes. External effects and any separately authorized cleanup or compensation results.

Optional saved evidence: A stopped parent can leave agent actions running and producing effects that still require reconciliation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Cascading cancellation, reversal of completed effects or live task inspection
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

DynamoDB deleted table system backup

Question: Does deleting a DynamoDB table with PITR enabled remove every recoverable table copy?

AWS documents that deleting a PITR-enabled table creates a system backup retained for 35 days. It is a snapshot immediately before deletion, supporting recovery to that single point rather than the former continuous timeline. Table deletion therefore does not establish immediate loss of recoverability.

Source: Amazon Web Services: DynamoDB point-in-time recovery: how it works. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a DynamoDB table with PITR enabled remove every recoverable table copy?

Buyer evidence still required

  • PITR state at deletion
  • table ID and deletion time
  • system-backup inventory and lifecycle
  • independent backup inventory

Review inference: A customer exit deletes its table and treats the operation as final erasure. A vendor-managed recovery snapshot remains available. Separates whole-table deletion with PITR from asynchronous item TTL deletion. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer complete erasure or continued full PITR history from the table deletion; account for the system snapshot and other copies.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Delete a table with PITR enabled

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer complete erasure or continued full PITR history from the table deletion; account for the system snapshot and other copies.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DynamoDB PITR reset history boundary

Question: Does re-enabling DynamoDB PITR restore the previous recovery window?

Disabling and then re-enabling DynamoDB point-in-time recovery resets the start time for the recovery window. The newly enabled window does not restore the previous continuous recovery history. Inspect the reported earliest and latest restorable times and any separately retained backups before relying on a pre-reset recovery point.

Source: Amazon Web Services: DynamoDB point-in-time recovery considerations. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does re-enabling DynamoDB PITR restore the previous recovery window?

Buyer evidence still required

  • PITR enable and disable history
  • earliest and latest restorable timestamps
  • configured recovery period
  • separate backup inventory

Review inference: An operator briefly disables PITR then reports the original recovery coverage as intact. An incident time may fall outside the available recovery history. Adds continuous-backup history discontinuity, unrelated to item-expiration cleanup. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse full-window recovery claims without actual restorable bounds; do not treat this as evidence that independent backups were deleted.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. If you disable point-in-time recovery

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse full-window recovery claims without actual restorable bounds; do not treat this as evidence that independent backups were deleted.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

DynamoDB TTL: Expiry does not prove erasure

Question: Does an expired DynamoDB TTL make a record immediately unavailable?

TTL deletion occurs asynchronously, typically within days. Expired items awaiting deletion can still be updated and appear in reads unless the application filters them. The attribute must have the documented numeric timestamp format. An expired timestamp alone does not establish removal or fulfil an erasure commitment.

Source: DynamoDB time to live. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An expired TTL timestamp proves immediate record deletion.

Buyer evidence still required

  • Table TTL attribute and item value type.
  • Read filtering and update behaviour.
  • Deletion evidence and any separately retained copies.

Suggested review condition: Require actual deletion evidence for an erasure claim; do not infer it from expiry alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Table TTL configuration, item attributes, reads, replicas and retained-copy scope.

Optional saved evidence: Preserve the evidence needed to challenge an immediate-erasure claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

DynamoDB: Transaction boundaries in stream evidence

Question: Does a DynamoDB transaction appear as one atomic, ordered group in its change stream?

After a DynamoDB transaction completes, its changes propagate gradually to streams and indexes. Records from the same transaction can arrive at different times and interleave with other transactions. AWS says stream consumers should not assume transaction atomicity or ordering. TransactGetItems provides an atomic read of the specified items when a coherent item snapshot is required.

Source: DynamoDB: Transactions and propagation. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a DynamoDB transaction appear as one atomic, ordered group in its change stream?

Buyer evidence still required

  • Transaction request, completion result and affected item identifiers.
  • Stream records, correlation references and observation period.
  • A coherent item-state read and unresolved propagation gaps.

Suggested review condition: Decline partial-commit or complete-transaction conclusions based only on a subset of stream events.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Transaction request, completion result and affected item identifiers. Stream records, correlation references and observation period. A coherent item-state read and unresolved propagation gaps.

Optional saved evidence: A partial stream view can be mistaken for a partial database commit or used to start recovery prematurely.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Atomic stream delivery, bounded propagation time or verification of a buyer transaction
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Dynatrace MCP: Query generation is separate from data execution

Question: Does asking Dynatrace MCP to generate DQL authorise it to execute that query?

The documentation separates DQL generation from a data-analysis tool that executes queries and returns results. Execution needs the relevant user and token permissions and remains subject to result limits and capability availability. Generated query text does not establish permission, complete coverage or authority to consume query capacity.

Source: Dynatrace MCP queries and permissions. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted Dynatrace intelligence tools

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Dynatrace publishes the hosted MCP capability.

Documented by publisher. Dynatrace MCP queries and permissions; Dynatrace AI capability availability

Purpose

Generate DQL and retrieve supported analytical results.

Documented by publisher. Dynatrace MCP queries and permissions; Dynatrace AI capability availability

Read capability

The execution tool can return authorised logs and other queried data.

Documented by publisher. Dynatrace MCP queries and permissions; Dynatrace AI capability availability

Write capability

The reviewed query tools do not establish a general configuration-write capability.

Documented by publisher. Dynatrace MCP queries and permissions; Dynatrace AI capability availability

Authentication

Platform bearer tokens and OAuth authorisation-code access are documented.

Documented by publisher. Dynatrace MCP queries and permissions; Dynatrace AI capability availability

Permission surface

User and token permissions both matter; bucket and data permissions remain necessary.

Documented by publisher. Dynatrace MCP queries and permissions; Dynatrace AI capability availability

Data leaving the environment

Query context and returned records enter the connected agent workflow.

Review inference. Dynatrace MCP queries and permissions; Dynatrace AI capability availability

Failure modes to consider

Result limits, missing permissions and unavailable platform capabilities can yield incomplete or failed responses.

Review inference. Dynatrace MCP queries and permissions; Dynatrace AI capability availability

Unknowns and applicability

Buyer plan, data scope, query charges and enabled capabilities are unverified.

Not established

Suggested refusal or clarification condition

Require authorised query scope and spending context; do not treat a bounded result as a complete incident inventory.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Query limits, platform capabilities and effective data permissions.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the distinction between query text, authorised execution and limited evidence returned.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

scope engagement separation record

EAP Scope Material vs Engagement Material

Question: Why does VAREXIS separate scope material from engagement material?

Public-safe handling record for separating assessment/quote material from engagement evidence.

Claim boundaries
  • automatic review activation
  • automatic retention
  • unbounded client material use
  • truth of submitted material
  • external reliance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

burden estimate record

EAP Verification Burden Estimate

Question: What factors should drive VAREXIS review pricing and routing?

Public-safe record for verification burden variables and manual review triggers.

Claim boundaries
  • fixed quote for all work
  • automatic acceptance
  • advice pricing
  • guaranteed outcome
  • low-risk classification without review

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

intake gate record

EAP-1 Acquisition Gate

Question: What does EAP-1 do at evidence intake?

Public-safe EAP intake record for acquisition, classification, timestamping, hashing and preliminary handling.

Claim boundaries
  • truth determination
  • review conclusion
  • evidence sufficiency
  • engagement acceptance
  • advice

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

structuring gate record

EAP-2 Structuring Gate

Question: What does EAP-2 do before review scope is accepted?

Public-safe record for EAP-2 evidence structuring, claim-density signals and scope readiness.

Claim boundaries
  • final truth finding
  • client advice
  • automatic acceptance
  • complete evidence validation
  • certification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

External documentation review

Elastic MCP: Space scope and shared identity

Question: Can an agent assume a shared search connector isolates each user's permissions and project data?

Elastic distinguishes shared API-key identity from per-user OAuth connections, with OAuth documented for Serverless projects. MCP access also depends on the Kibana space in the endpoint and its cross-project search scope. Restrict keys to intended indices and application privileges; a successful connection is not proof of per-user isolation or single-project coverage.

Source: Elastic Agent Builder MCP identity and space scope. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Elastic Agent Builder acting as an MCP server for external clients; not its connector for calling external MCP servers.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Elastic publishes Agent Builder; the chosen Stack deployment or Serverless project determines the operating environment.

Documented by publisher. Elastic Agent Builder MCP identity and space scope

Purpose

Expose Agent Builder tools and search/query capabilities to external clients.

Documented by publisher. Elastic Agent Builder MCP identity and space scope

Read capability

Queries use authorized data and the space's configured cross-project search scope.

Documented by publisher. Elastic Agent Builder MCP identity and space scope; Elastic MCP API key restrictions

Write capability

Workflow tools are included, so review configured actions before treating the full catalog as read-only.

Review inference. Elastic Agent Builder MCP identity and space scope

Authentication

API keys work for Stack and Serverless; OAuth is documented for Serverless projects.

Documented by publisher. Elastic Agent Builder MCP identity and space scope

Permission surface

Shared keys use one identity. Keys require application privileges and should be restricted to intended indices.

Documented by publisher. Elastic Agent Builder MCP identity and space scope; Elastic MCP API key restrictions

Data leaving the environment

Retrieved search data is returned to the external host; selected model recipients remain a separate question.

Review inference. Elastic Agent Builder MCP identity and space scope

Failure modes to consider

A shared key mistaken for per-user isolation, default space used unintentionally, or linked projects widening search.

Review inference. Elastic Agent Builder MCP identity and space scope; Elastic MCP API key restrictions

Unknowns and applicability

Deployment type, space, linked-project scope, API-key grants, workflow actions and client retention.

Not established

Suggested refusal or clarification condition

Resolve identity, space and data scope before retrieval; do not claim user isolation for a shared key.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck API-key grants, endpoint space, linked-project search scope and workflow tools after configuration changes.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the identity, index and space-scope assumptions behind an enterprise-search connector review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Elasticsearch ILM: Age measured from rollover

Question: Does an ILM minimum age mean each log is deleted that long after its event timestamp?

After rollover, ILM phase minimum ages use the previous index rollover time rather than its creation time. The policy acts on indices, while individual events can have different timestamps. A phase-age setting alone is not evidence of exact per-event deletion timing.

Source: Elasticsearch index rollover lifecycle. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An index lifecycle minimum age guarantees a matching event-age retention period.

Buyer evidence still required

  • Rollover timestamp and lifecycle policy.
  • Index membership and event timestamps.
  • Phase progress and deletion evidence.

Suggested review condition: Check the lifecycle reference time and index contents before asserting per-event retention.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Index lifecycle policy, rollover time, event membership and phase state.

Optional saved evidence: Preserve the distinction between index lifecycle settings and event-level retention claims.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Elasticsearch redaction: Licence and skip behaviour

Question: Does a successful ingest pipeline prove the redact processor changed the document?

The redact processor can quietly leave a document unchanged when skip_if_unlicensed is enabled and the licence does not support it. Conditional execution and failure handling also affect what runs. The trace_redact option can mark actual redaction, but absence of that marker alone is not a complete coverage assessment.

Source: Elasticsearch: Redact processor. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Pipeline success proves sensitive text was redacted.

Buyer evidence still required

  • Licence eligibility and effective skip settings.
  • Conditional and failure-handler configuration.
  • Representative input/output and redaction trace where enabled.

Suggested review condition: Check actual processor execution and output before accepting pipeline success as redaction evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Elasticsearch version, licence, processor settings, patterns and failure paths.

Optional saved evidence: Save the execution and licensing boundary behind a redaction claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Elasticsearch: Combined roles can broaden data access

Question: Does one restrictive Elasticsearch role prove a user cannot read other documents or fields?

Elastic documents that permissions from multiple roles can combine to broaden access to the same index. A role without the relevant restriction can defeat the intended document or field limit. Review the complete role assignment, not one restrictive role in isolation.

Source: Elasticsearch document and field access across roles. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A restrictive role proves the identity only sees the intended subset.

Buyer evidence still required

  • Complete role assignments for the identity
  • Definitions for every role covering the target index
  • Authorized test evidence of effective read scope

Suggested review condition: Require the full role combination before accepting a restricted-data-access claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck role membership, index patterns and unrestricted grants.

Optional saved evidence: Save the role-combination evidence behind a data-separation decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Elasticsearch: Failed deletion with retained effects

Question: Does a failed Elasticsearch delete-by-query leave the original matching documents intact?

Elasticsearch 8.19 delete-by-query works from an initial snapshot using internal versioning. Concurrent changes can cause version conflicts. If processing stops after failed requests, successful earlier deletions remain; they are not rolled back. Setting conflicts to proceed changes conflict handling, not the need to reconcile remaining documents and completed deletions.

Source: Elasticsearch: Delete by query. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a failed Elasticsearch delete-by-query leave the original matching documents intact?

Buyer evidence still required

  • Exact query, index scope and conflict options submitted.
  • Task response, deletion counts, conflicts and failed items.
  • Remaining document versions and any approved restoration or further deletion plan.

Suggested review condition: Decline no-effect or fully-deleted claims until successful deletions and residual matches are separately accounted for.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Exact query, index scope and conflict options submitted. Task response, deletion counts, conflicts and failed items. Remaining document versions and any approved restoration or further deletion plan.

Optional saved evidence: A failed destructive bulk action can leave a mixed state that neither a total-failure label nor a blanket retry explains.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Atomic bulk deletion, automatic restoration or approval for a broader retry
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Elasticsearch: Snapshot success is not a full environment export

Question: Does an Elasticsearch snapshot preserve every index and setting needed for an AI application exit?

Snapshots back up open indices and supported cluster or feature state, but exclude closed indices and items such as transient cluster settings, registered repositories and node configuration files. Selected-index snapshots narrow coverage further. A successful snapshot is not a complete environment inventory.

Source: Snapshot and restore in Elasticsearch | Elastic Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an Elasticsearch snapshot preserve every index and setting needed for an AI application exit?

Buyer evidence still required

  • Index open/closed state and selected scope.
  • Feature states and snapshot manifest.
  • Excluded configuration inventory and restore compatibility.

Suggested review condition: Do not declare export completeness without reconciling excluded indices and configuration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Index open/closed state and selected scope. Feature states and snapshot manifest. Excluded configuration inventory and restore compatibility.

Optional saved evidence: Reconcile the export against data and configuration needed for a controlled exit.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Restorability in the buyer environment, deletion or completeness of unknown holdings
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Endor Labs MCP: Local process and cloud findings

Question: Does a local Endor Labs MCP process keep analysis offline or prove reachability?

The stdio process runs locally but calls the Endor Labs cloud for security context. Its documented MCP findings are not function-level reachability or action-policy-filtered results. Tools can run scans and code-diff reviews; the latter needs Enterprise enablement and a namespace. A documentation-only connector is a separate interface.

Source: Endor Labs MCP in Gemini CLI. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer deployment unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Endor Labs publishes the local integration and operates the cloud platform.

Documented by publisher. Endor Labs MCP in Gemini CLI

Purpose

Query security context and run supported scans or code reviews.

Documented by publisher. Endor Labs MCP in Gemini CLI

Read capability

Dependency findings, project context and selected local code or diffs.

Documented by publisher. Endor Labs MCP in Gemini CLI

Write capability

Tools initiate scanning and analysis rather than only retrieving documentation.

Documented by publisher. Endor Labs MCP in Gemini CLI

Authentication

Browser authentication and enterprise namespace settings depend on edition.

Documented by publisher. Endor Labs MCP in Gemini CLI

Permission surface

User permissions, namespace, tool selection and edition govern applicability.

Documented by publisher. Endor Labs MCP in Gemini CLI

Data leaving the environment

Local execution does not imply offline analysis; the server calls the cloud platform.

Review inference. Endor Labs MCP in Gemini CLI

Failure modes to consider

A cached or separately installed binary can differ from the expected version; findings can be mistaken for reachability results.

Review inference. Endor Labs MCP in Gemini CLI

Unknowns and applicability

Exact installed revision, transmitted payload and buyer configuration were not inspected.

Not established

Suggested refusal or clarification condition

Confirm code-disclosure authority and analysis scope before scanning private work.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Edition features, cloud calls, binary selection and reachability support.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the analysis scope and data-flow basis without treating a dependency finding as an application verdict.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Enterprise scanner eligibility/channel/timing coverage

Question: Does enabling Claude Enterprise skill scanning cover API uploads and existing skills?

The captured guidance limits scanning to eligible uploads and edits in claude.ai or Cowork after the setting is enabled. It excludes Skills API uploads and skills already present when scanning was enabled. The guide also excludes organisations with certain data-handling configurations, including CMEK, ZDR or HIPAA readiness.

Source: Anthropic primary documentation: claude skills enterprise. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does enabling Claude Enterprise skill scanning cover API uploads and existing skills?

Buyer evidence still required

  • organisation eligibility
  • scanning setting time
  • upload channel/time
  • existing inventory
  • scan receipt

Review inference: Does enabling Claude Enterprise skill scanning cover API uploads and existing skills? Do not represent the organisational switch as retrospective or API-wide coverage; inventory each deployment channel and scan event. Enterprise scanner eligibility/channel/timing coverage. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not represent the organisational switch as retrospective or API-wide coverage; inventory each deployment channel and scan event.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Skill content scanning

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not represent the organisational switch as retrospective or API-wide coverage; inventory each deployment channel and scan event.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra CAE: Revocation depends on the participating client and resource

Question: Does Continuous Access Evaluation guarantee immediate revocation in every application?

Continuous Access Evaluation depends on participating resources and clients, including handling of claim challenges. The guide distinguishes supported scenarios and exceptions. Its presence does not establish universal instantaneous revocation; the buyer must identify the actual application and demonstrate the relevant access outcome.

Source: Microsoft Entra continuous access evaluation coverage. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: CAE guarantees immediate access removal everywhere.

Buyer evidence still required

  • Application/resource and client compatibility.
  • Applied policies and relevant session conditions.
  • Authorised evidence of access after the revocation event.

Suggested review condition: Keep universal revocation claims qualified until each relevant application path is evidenced.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Client/resource support, access policies and session paths

Optional saved evidence: Save the application-specific gaps behind a revocation claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Entra emergency conditional access exclusion

Question: Must an Entra emergency-access account be excluded from report-only Conditional Access policies?

The captured guidance distinguishes enforced policies that block or restrict sign-in from report-only policies. It recommends excluding emergency accounts from blocking or restricting policies, while report-only policies do not require that exclusion. Review actual policy state and authorized validation rather than treating all policies as equivalent blockers.

Source: Microsoft: Manage emergency access accounts. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Must an Entra emergency-access account be excluded from report-only Conditional Access policies?

Buyer evidence still required

  • policy state
  • emergency-account membership
  • enforced conditions
  • report-only evaluations
  • validation results

Review inference: An operator removes useful report-only visibility while attempting to prevent emergency lockout. Monitoring may be lost without improving emergency access. Adds emergency-access policy-mode applicability rather than eligibility or MFA activation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: The source is planning guidance, not authorization to weaken controls or proof that a particular account can sign in.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Conditional Access considerations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The source is planning guidance, not authorization to weaken controls or proof that a particular account can sign in.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra emergency identity dependency

Question: Can an eligible federated administrator be treated as a fully independent emergency-access path?

Microsoft's emergency-access guidance recommends cloud-only accounts independent of federation and synchronization, with permanent active Global Administrator assignments rather than PIM eligibility. It also separates emergency authentication methods from normal administrator methods. These recommendations address shared failure dependencies; configuration and an actual authorized validation are still needed to establish availability.

Source: Microsoft: Manage emergency access accounts. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an eligible federated administrator be treated as a fully independent emergency-access path?

Buyer evidence still required

  • emergency account origin
  • federation dependencies
  • role assignment state
  • authentication method
  • authorized validation

Review inference: An identity-provider outage prevents normal privileged-role activation. An emergency account sharing that dependency can also be unusable. Adds emergency-path dependency and permanent-active guidance rather than ordinary PIM activation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: This guidance does not authorize creating privileged accounts or guarantee access during an outage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Create emergency access accounts

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • This guidance does not authorize creating privileged accounts or guarantee access during an outage.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra emergency use review validation

Question: Does a successful emergency-account sign-in establish that its administrative use was authorized?

Microsoft separates sign-in and audit monitoring, post-use review and periodic validation. Its guidance calls for reviewing whether emergency use was authorized and actions appropriate, and testing sign-in and administrative functionality at least every 90 days and after specified organizational changes. A successful sign-in alone establishes neither business authorization nor continued readiness.

Source: Microsoft: Manage emergency access accounts. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a successful emergency-account sign-in establish that its administrative use was authorized?

Buyer evidence still required

  • authorized-user list
  • emergency reason
  • sign-in and administrative audit events
  • post-use review
  • dated validation

Review inference: A buyer treats one historic emergency login as proof of permanent readiness and approved use. Unauthorized actions or later access failures can be missed. Adds post-emergency action review and continuing readiness evidence, distinct from granting an active role. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Monitoring and exercises do not certify compliance or establish that every action was observed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Post-mortem review

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Monitoring and exercises do not certify compliance or establish that every action was observed.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra federated credential subject matching

Question: Does an Entra federated credential for one GitHub branch automatically trust every branch in that repository?

The standard federated-credential guide requires issuer and subject values to match the external token. Its GitHub configuration distinguishes environment, branch, pull request and tag subjects. The documented branch and tag setup does not support wildcard patterns. Repository identity alone does not describe the configured subject boundary.

Source: Create a trust relationship between an app and an external identity provider - Microsoft Entra Workload ID | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an Entra federated credential for one GitHub branch automatically trust every branch in that repository?

Buyer evidence still required

  • Federated credential issuer, subject and audience
  • GitHub workflow trigger, environment and token subject
  • Credential type and applicable provider documentation

Review inference: Compare the actual token subject with the specific credential type and configured subject.

Suggested review condition: Reject repository-wide trust assumptions derived from one branch-specific credential.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer credential and presented token claims are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep a CI agent’s token-minting boundary aligned with the approved workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A claim about all flexible federated-credential features
  • The buyer credential and presented token claims are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Entra logs: A licence upgrade does not recreate expired history

Question: Does upgrading an Entra licence recover audit or sign-in records that already expired?

The retention guide says licence changes are not retroactive. An upgrade retains only data still available, unless older data was separately archived. Log types also differ; Graph activity logs require a storage or analytics integration. A new licence is not evidence that the requested historical interval exists.

Source: Entra report retention by licence. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A premium licence makes earlier expired activity available.

Buyer evidence still required

  • Log type, licence and applicable retention window.
  • Archive or analytics integration with its activation date.
  • Retrieved coverage for the requested historical interval.

Suggested review condition: Keep the historical interval unproven until retained or archived records are demonstrated.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Log type, licence dates, archive activation and requested interval

Optional saved evidence: Save why the requested historical interval needs archive evidence rather than a current licence screenshot.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Entra logs: A row can represent several sign-ins

Question: Can one non-interactive Entra sign-in log row be counted as one credential use?

Entra groups non-interactive user sign-ins with matching characteristics into one row. The sign-in count can exceed one, and rows can be expanded to inspect individual times. The selected aggregation window changes how the same activity is presented.

Source: Non-interactive sign-in logs - Microsoft Entra ID | Microsoft Learn. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can one non-interactive Entra sign-in log row be counted as one credential use?

Buyer evidence still required

  • Log category and aggregation window.
  • Per-row sign-in count.
  • Expanded event timestamps and export coverage.

Suggested review condition: Do not equate displayed row count with the number of sign-ins without resolving aggregation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Log category and aggregation window. Per-row sign-in count. Expanded event timestamps and export coverage.

Optional saved evidence: Reconstruct agent credential activity without undercounting grouped records.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Unique-user counts, full authentication coverage or proof of successful business actions
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Entra PIM activation device use separation

Question: Does activating PIM from a compliant device restrict subsequent role use to that device?

PIM authentication context governs activation. Microsoft explains that after activation the user can use another session, device or location; a separate policy targeting the activated directory role or users is needed for the intended subsequent sign-in conditions. Activation-device evidence alone does not bind all later use.

Source: Microsoft: Configure PIM role settings. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does activating PIM from a compliant device restrict subsequent role use to that device?

Buyer evidence still required

  • activation-context policy
  • directory-role or user policy
  • activation session
  • subsequent role-use sign-ins

Review inference: An operator activates on a managed workstation then uses the account elsewhere. A one-time device check can be misreported as continuous role-use control. Separates activation admission from post-activation use conditions, a distinct hand-off boundary. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse a continuing device restriction based only on the device used for activation; do not claim all subsequent actions were evaluated identically.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. After the role is activated

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a continuing device restriction based only on the device used for activation; do not claim all subsequent actions were evaluated identically.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM active assignment MFA actor

Question: Does MFA on creation of an active PIM assignment prove the assignee authenticated for later use?

The active-assignment MFA setting requires the administrator creating the assignment to satisfy MFA. Microsoft states that PIM cannot enforce MFA when the assigned user uses that already-active role. Assignment-creation authentication and assignee-use authentication are different evidence.

Source: Microsoft: Configure PIM role settings. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does MFA on creation of an active PIM assignment prove the assignee authenticated for later use?

Buyer evidence still required

  • assigning administrator identity
  • assignment type and creation event
  • assignee sign-in controls and evidence

Review inference: An audit reviewer checks a directly active role assignment. The administrator's authentication may be mistaken for the recipient's authentication. Adds which actor is challenged for an active assignment, rather than the eligible/active distinction alone. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not attribute the assigning administrator's MFA to the assignee or infer later-use MFA from this setting.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Require multifactor authentication on active assignment

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not attribute the assigning administrator's MFA to the assignee or infer later-use MFA from this setting.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM approver identity restrictions

Question: Can an Entra PIM requester or service principal approve the activation request?

For Microsoft Entra role activation, PIM prohibits approvers from approving their own requests and does not allow service principals to approve requests. Delegation to an approver does not remove these identity restrictions.

Source: Microsoft: Approve or deny PIM requests. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an Entra PIM requester or service principal approve the activation request?

Buyer evidence still required

  • requester object ID
  • approver object ID and type
  • role activation request
  • applicable PIM workflow

Review inference: An agent workflow proposes approving its own operator's role activation. The proposed approval path is unsupported or lacks a separate authorised human. The existing record establishes eligibility versus activation; this decision checks who may supply the approval evidence. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not represent a requester self-approval or a service-principal approval as a supported PIM role approval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Approve requests

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not represent a requester self-approval or a service-principal approval as a supported PIM role approval.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM auth context fallback gaps

Question: Does PIM's authentication-context fallback cover a disabled or report-only Conditional Access policy?

PIM's documented fallback to MFA protects the case where no Conditional Access policy targets the configured context. It is not triggered when a targeting policy is disabled, report-only, or excludes the eligible user. Context configuration therefore cannot substitute for checking the applicable enabled policy.

Source: Microsoft: Configure PIM role settings. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does PIM's authentication-context fallback cover a disabled or report-only Conditional Access policy?

Buyer evidence still required

  • PIM authentication context
  • targeting policy state
  • user inclusions and exclusions
  • activation evidence

Review inference: An administrator leaves a context policy in report-only mode during rollout. The intended activation condition may be absent despite a configured context. Adds the explicitly documented fallback exclusions, beyond generic PIM activation requirements. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not claim the intended context controls or fallback were enforced without checking policy state and user applicability.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. This backup protection mechanism

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim the intended context controls or fallback were enforced without checking policy state and user applicability.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM default approver lockout

Question: Can requiring PIM approval leave no available default approver?

When no specific approvers are selected, active Privileged Role Administrators or Global Administrators are the defaults. Microsoft warns of tenant lockout when all such administrators are only eligible, none are active, approval is required, and no approvers are selected. An approval requirement alone does not establish an available escalation path.

Source: Microsoft: Configure PIM role settings. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can requiring PIM approval leave no available default approver?

Buyer evidence still required

  • selected approvers
  • active and eligible administrator assignments
  • approval requirement
  • emergency-access arrangements

Review inference: An administrator enables approval after making every administrator eligible-only. No active default approver may remain to authorise elevation. Adds a circular-approval availability failure, separate from ordinary activation eligibility. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not assert a usable approval path without an available eligible approver configuration; this review does not authorise bypass.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. You'll be locked out

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assert a usable approval path without an available eligible approver configuration; this review does not authorise bypass.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM first approver decision

Question: Do multiple Entra PIM approvers provide unanimous approval?

PIM resolves an activation request when the first approver approves or denies it and notifies the other approvers. Configuring several approvers therefore does not establish a quorum or unanimous decision.

Source: Microsoft: Approve or deny PIM requests. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Do multiple Entra PIM approvers provide unanimous approval?

Buyer evidence still required

  • configured approver list
  • request ID
  • first decision and actor
  • required approval policy

Review inference: A buyer lists two approvers and treats activation as two-person approval. A single decision may be mistaken for a required quorum. Tests approval cardinality, rather than whether activation is required. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse a dual-control or unanimous-approval claim based solely on the number of configured PIM approvers.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Notifications

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a dual-control or unanimous-approval claim based solely on the number of configured PIM approvers.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM MFA session reuse

Question: Does PIM's MFA requirement ensure a fresh challenge on each activation?

Users may satisfy PIM's MFA requirement with strong credentials or MFA already supplied in the session. The documented authentication-context approach has its own reauthentication settings; even the described Every time configuration has a ten-minute reuse window across eligible activations. An MFA setting alone does not prove a fresh interaction for each request.

Source: Microsoft: Configure PIM role settings. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does PIM's MFA requirement ensure a fresh challenge on each activation?

Buyer evidence still required

  • session authentication evidence
  • PIM MFA setting
  • Conditional Access context and sign-in frequency
  • activation timestamps

Review inference: An auditor equates each privileged activation with a new human authentication. Repeated activations could be overstated as independently challenged approvals. Adds authentication freshness and reuse, not assignment eligibility or effective role state. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not claim a distinct fresh MFA interaction for every activation without event-level authentication evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. On activation, require multifactor authentication

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim a distinct fresh MFA interaction for every activation without event-level authentication evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM request expiry resubmission

Question: Can an unapproved Entra PIM request remain valid indefinitely?

Delegated approvers have a non-configurable 24-hour window for an Entra role activation request. If it is not approved within that period, the eligible user must submit a new request. A stale pending request is not a continuing approval opportunity.

Source: Microsoft: Approve or deny PIM requests. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an unapproved Entra PIM request remain valid indefinitely?

Buyer evidence still required

  • request creation time
  • current request state
  • decision time
  • replacement request ID

Review inference: An operator resumes an interrupted approval workflow the following day. Execution can be linked to an expired or different request. Adds request-lifetime and replacement identity, separate from the active assignment's duration. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not bind a later action to an expired approval request without the new request and its decision.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Approve or deny requests

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not bind a later action to an expired approval request without the new request and its decision.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM ticket reference not validation

Question: Does requiring a PIM ticket number validate the external approval ticket?

The Entra PIM ticket-information setting requires a support ticket reference but treats it as an information-only field. PIM does not enforce correlation with an external ticketing system. A populated reference is therefore not evidence that the ticket exists, is approved, or covers the action.

Source: Microsoft: Configure PIM role settings. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does requiring a PIM ticket number validate the external approval ticket?

Buyer evidence still required

  • entered ticket reference
  • external ticket state and approver
  • approved action scope
  • activation request

Review inference: An agent presents a PIM ticket number as change-management approval. An unverified reference could be mistaken for authority to perform a change. Distinguishes collecting a ticket string from verifying an external approval, absent from the activation-state record. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse external-change-approval claims based solely on the PIM ticket field; independently bind the referenced ticket.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Require ticket information on activation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse external-change-approval claims based solely on the PIM ticket field; independently bind the referenced ticket.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Entra PIM: Eligibility is not active privilege

Question: Does an eligible PIM assignment mean an agent's user already has the privileged role?

Eligible assignments require activation before use; active assignments permit use within their assigned duration. Approval is conditional on role settings, not inherent in every activation. Review assignment type, activation state, duration and configured approval rather than treating the word PIM as proof of just-in-time approval.

Source: Entra Privileged Identity Management. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every PIM assignment is inactive until independently approved.

Buyer evidence still required

  • Assignment type and duration.
  • Current activation evidence.
  • Role activation and approval settings.

Suggested review condition: Require actual activation and approval evidence appropriate to the role.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Assignment type, activation state, expiry and approval policy

Optional saved evidence: Retain the time and approval conditions behind a privileged-action decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Entra: Workload Conditional Access coverage exceptions

Question: Does an Entra Conditional Access policy assigned to a group govern service principals inside that group?

Workload Conditional Access must target eligible service principals directly; assigning a containing group does not enforce that policy for them. The documented scope excludes managed identities and Microsoft or third-party multitenant SaaS applications. Eligible workload policies require the relevant licence.

Source: Microsoft Entra Conditional Access for workload identities - Microsoft Entra ID | Microsoft Learn. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does an Entra Conditional Access policy assigned to a group govern service principals inside that group?

Buyer evidence still required

  • Service principal type and tenancy.
  • Direct workload policy assignment.
  • Licence, policy state and sign-in evidence.

Suggested review condition: Do not claim policy coverage from group membership or a managed-identity label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Service principal type and tenancy. Direct workload policy assignment. Licence, policy state and sign-in evidence.

Optional saved evidence: Check identity type and direct targeting before relying on an agent sign-in restriction.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Sign-in blocking in the buyer tenant or coverage of all non-human identities
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

EPSS: Dated lookup and bulk retrieval

Question: How should a vulnerability workflow retrieve EPSS scores and preserve the decision date?

FIRST recommends its API for individual or small-batch lookups, and daily CSV files for bulk workflows. Historical lookup can pin a score date. Preserve that date and model version: a model change can shift scores without a change in the vulnerability. This documents retrieval choices; VAREXIS does not fetch or refresh EPSS scores through this entry.

Source: FIRST: Get the EPSS Data. Documentation checked 2026-10-11; no deployment validation is claimed.

Claim boundaries
  • current scores supplied by this documentation entry
  • unchanged methodology across model versions
  • successful bulk ingestion without validation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

EPSS: Probability, percentile and asset risk

Question: Does an EPSS score establish the risk to my deployed asset?

FIRST describes EPSS as the estimated chance of observed exploitation activity for a CVE over the next 30 days. The percentile is its rank among scored vulnerabilities, not that probability. EPSS excludes asset-specific exposure, controls and impact. Use the dated score as one input alongside deployment evidence; it does not establish that your system is affected, compromised or safe.

Source: FIRST: EPSS Frequently Asked Questions. Documentation checked 2026-10-11; no deployment validation is claimed.

Claim boundaries
  • asset-specific risk from a score alone
  • percentile treated as exploitation probability
  • evidence of compromise or package safety

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

EU AI Act: Assess design support for human intervention

Question: What evidence supports a claim that an overseer can interpret, disregard, override or stop the system?

Article 14 provides risk/proportionality-linked oversight design measures enabling assigned people to understand capacities/limits, recognise automation bias, interpret outputs, override/reverse outputs and interrupt via a safe-stop procedure as appropriate to context. Review implication: Map each claimed intervention to a usable mechanism and boundary, without treating design documentation as proof of live enforcement.

Source: PE-CONS24/1/24REV1 adopted AIAct. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions

Provision: 14(3)-(4);113(c);111(2) · Operator: Provider designing a covered high-risk system; buyer assessing supplied design evidence

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

No determination of effective permissions, runtime safety or legal compliance. A button label is not evidence of successful safe interruption; risk and operating context matter.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What evidence supports a claim that an overseer can interpret, disregard, override or stop the system?

Buyer evidence still required

  • Oversight design
  • interface/override specification
  • automation-bias safeguards
  • safe-stop criteria
  • test scope and observations

Review inference: Map each claimed intervention to a usable mechanism and boundary, without treating design documentation as proof of live enforcement.

Suggested review condition: No determination of effective permissions, runtime safety or legal compliance. A button label is not evidence of successful safe interruption; risk and operating context matter. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • No determination of effective permissions, runtime safety or legal compliance. A button label is not evidence of successful safe interruption; risk and operating context matter. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • No determination of effective permissions, runtime safety or legal compliance. A button label is not evidence of successful safe interruption; risk and operating context matter.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Assign competent and empowered human oversight

Question: Does naming a reviewer establish the oversight arrangements needed for this planned high-risk deployment?

Article 26(2) requires oversight assigned to natural persons with necessary competence, training and authority, as well as necessary support. Review implication: Request role assignment, relevant training, decision authority and support arrangements; then distinguish documentation from observed intervention ability.

Source: PE-CONS24/1/24REV1 adopted AIAct. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions

Provision: 26(2);113(c);111(2) · Operator: Deployer of a covered high-risk system

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

A name or policy alone does not prove competence, authority or functioning supervision. Article 2/6/111/113 classification and transition gates apply; no current blanket duty asserted.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does naming a reviewer establish the oversight arrangements needed for this planned high-risk deployment?

Buyer evidence still required

  • Named oversight roles
  • training/competence evidence
  • delegated authority
  • support/escalation arrangements
  • optional controlled observation

Review inference: Request role assignment, relevant training, decision authority and support arrangements; then distinguish documentation from observed intervention ability.

Suggested review condition: A name or policy alone does not prove competence, authority or functioning supervision. Article 2/6/111/113 classification and transition gates apply; no current blanket duty asserted. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • A name or policy alone does not prove competence, authority or functioning supervision. Article 2/6/111/113 classification and transition gates apply; no current blanket duty asserted. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • A name or policy alone does not prove competence, authority or functioning supervision. Article 2/6/111/113 classification and transition gates apply; no current blanket duty asserted.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Check both product-safety classification conditions

Question: Does a product-related AI feature meet the Annex I high-risk route, rather than merely belonging to a regulated product?

Article 6(1) requires both the product/safety-component link to Annex I legislation and a required third-party conformity assessment. New 1a-1c distinguish non-safety assistance and assessment for non-health/safety risks; malfunction endangering health/safety remains material. Review implication: Require the precise product law, safety-function analysis and assessment route; use Chapter III Sections 1-3 future date only after category checks.

Source: Official Commission AI Act Service Desk: Article 6. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — 2028-08-02

Provision: 6(1),(1a)-(1c) as amended 2026/1744;2(2),(13);113(c)(ii) · Operator: Provider/procurement reviewer of an AI product or safety component

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

A regulated product or voluntary third-party audit alone is insufficient. Annex I SectionB has Article 2(2) limited application;2(13) is not a self-declared blanket waiver. Other law can already apply.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a product-related AI feature meet the Annex I high-risk route, rather than merely belonging to a regulated product?

Buyer evidence still required

  • Product/legal-act mapping
  • intended purpose
  • failure/safety analysis
  • required assessment route
  • AnnexI section
  • any applicable delegated limitation

Review inference: Require the precise product law, safety-function analysis and assessment route; use Chapter III Sections 1-3 future date only after category checks.

Suggested review condition: A regulated product or voluntary third-party audit alone is insufficient. Annex I SectionB has Article 2(2) limited application;2(13) is not a self-declared blanket waiver. Other law can already apply. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • A regulated product or voluntary third-party audit alone is insufficient. Annex I SectionB has Article 2(2) limited application;2(13) is not a self-declared blanket waiver. Other law can already apply. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • A regulated product or voluntary third-party audit alone is insufficient. Annex I SectionB has Article 2(2) limited application;2(13) is not a self-declared blanket waiver. Other law can already apply.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Check the editorial exception for public-interest text

Question: Can this publisher rely on human review and editorial responsibility instead of the AI-text disclosure duty?

Covered public-interest text requires artificial-generation/manipulation disclosure unless a specified exception applies; editorial exception requires human review or editorial control AND a natural or legal person holding editorial responsibility. Review implication: Identify responsible publisher and actual review/control evidence; approval by an unnamed reviewer does not establish the combined exception.

Source: Official Commission AI Act Service Desk: Article 50. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: CONDITIONAL — 2026-08-02

Provision: 50(4) second subparagraph;50(5);113 · Operator: Deployer publishing AI-generated/manipulated text to inform the public on matters of public interest

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

The criminal-law exception is separate. This is not a general exemption for every human-edited document; provider marking duties are independently assessed.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can this publisher rely on human review and editorial responsibility instead of the AI-text disclosure duty?

Buyer evidence still required

  • Publication purpose
  • editorial responsibility assignment
  • review/control record
  • publication version
  • disclosure decision

Review inference: Identify responsible publisher and actual review/control evidence; approval by an unnamed reviewer does not establish the combined exception.

Suggested review condition: The criminal-law exception is separate. This is not a general exemption for every human-edited document; provider marking duties are independently assessed. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • The criminal-law exception is separate. This is not a general exemption for every human-edited document; provider marking duties are independently assessed. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • The criminal-law exception is separate. This is not a general exemption for every human-edited document; provider marking duties are independently assessed.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Check the narrow legacy marking transition

Question: Does this generator qualify for the temporary Article 50(2) marking deadline?

Article 111(4) gives providers of qualifying systems placed on the market before 2 August 2026 until 2 December 2026 to comply with Article 50(2). Review implication: Require dated placement evidence and system identity; do not extend this marking-only transition to other disclosure duties.

Source: Official Commission AI Act Service Desk: Article 111. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: TRANSITIONAL — 2026-12-02

Provision: 111(4) added by 2026/1744 Art 1(39)(b);50(2) · Operator: Provider of a synthetic-content AI system placed on the market before 2 August 2026

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

Transition only concerns 50(2), not all of Article 50, and is not a permanent exemption. A release-note date alone may not prove placing on the market.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does this generator qualify for the temporary Article 50(2) marking deadline?

Buyer evidence still required

  • First market-placement evidence
  • version/system identity
  • provider role
  • marking implementation plan

Review inference: Require dated placement evidence and system identity; do not extend this marking-only transition to other disclosure duties.

Suggested review condition: Transition only concerns 50(2), not all of Article 50, and is not a permanent exemption. A release-note date alone may not prove placing on the market. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Transition only concerns 50(2), not all of Article 50, and is not a permanent exemption. A release-note date alone may not prove placing on the market. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • Transition only concerns 50(2), not all of Article 50, and is not a permanent exemption. A release-note date alone may not prove placing on the market.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Check the open-source exclusion boundary

Question: Can a free open-source licence alone exclude this AI system from relevant AI Act duties?

Article 2(12) excludes systems released under free/open-source licences unless placed on the market or put into service as high-risk systems or systems falling under Article 5 or 50. Review implication: Check intended use and applicable exception categories separately from licence metadata.

Source: Official Commission AI Act Service Desk: Article 2. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: CONDITIONAL — 2025-02-02 scope;2026-08-02 Article 50

Provision: 2(12);113(a);50 · Operator: Provider/deployer or buyer of a freely licensed AI system

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

An open-source label is not a universal exemption. This system-level provision does not determine every GPAI-model obligation; Article 50 marking transitions still require separate assessment.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a free open-source licence alone exclude this AI system from relevant AI Act duties?

Buyer evidence still required

  • Licence and release terms
  • system intended use
  • market/service placement
  • Article5/50 and high-risk classification analysis

Review inference: Check intended use and applicable exception categories separately from licence metadata.

Suggested review condition: An open-source label is not a universal exemption. This system-level provision does not determine every GPAI-model obligation; Article 50 marking transitions still require separate assessment. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • An open-source label is not a universal exemption. This system-level provision does not determine every GPAI-model obligation; Article 50 marking transitions still require separate assessment. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • An open-source label is not a universal exemption. This system-level provision does not determine every GPAI-model obligation; Article 50 marking transitions still require separate assessment.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Check whether legacy high-risk treatment survives a design change

Question: Does the pre-existing system qualify for the legacy transition after a later design change?

Article 111(2), without prejudice toArticle 5 and excluding 111(1) systems, applies the Regulation to qualifying older high-risk systems only if significant design changes occur from the relevant Chapter III application date; providers/deployers of systems intended for public authorities must take steps to comply by 2 August 2030. Review implication: Preserve the before/after design, placing/service date and use context; evaluate significance rather than using a version label as the trigger.

Source: Official Commission AI Act Service Desk: Article 111. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: TRANSITIONAL — Relevant Chapter III date;public-authority deadline 2030-08-02

Provision: 111(2) replaced by 2026/1744 Art 1(39)(a);113(c) · Operator: Operator of a high-risk system predating its applicable Chapter III date

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

Recital 177 explains significant design changes as equivalent in substance to substantial modification. Assess the actual design and intended-purpose change, not a version label alone. No blanket grandfathering or Article 5 exemption.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the pre-existing system qualify for the legacy transition after a later design change?

Buyer evidence still required

  • Market/service date
  • baseline design
  • dated change register
  • significance rationale
  • public-authority intended-use evidence
  • AnnexX check

Review inference: Preserve the before/after design, placing/service date and use context; evaluate significance rather than using a version label as the trigger.

Suggested review condition: Recital 177 explains significant design changes as equivalent in substance to substantial modification. Assess the actual design and intended-purpose change, not a version label alone. No blanket grandfathering or Article 5 exemption. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Recital 177 explains significant design changes as equivalent in substance to substantial modification. Assess the actual design and intended-purpose change, not a version label alone. No blanket grandfathering or Article 5 exemption. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • Recital 177 explains significant design changes as equivalent in substance to substantial modification. Assess the actual design and intended-purpose change, not a version label alone. No blanket grandfathering or Article 5 exemption.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Check whether operating instructions support the proposed use

Question: Do the supplied high-risk-system instructions contain enough specific information for this planned operation?

Article 13 requires accessible, comprehensible instructions covering purpose, tested performance/limitations, relevant risks, appropriate input/output information, predetermined changes, oversight, resources/maintenance and relevant log mechanisms. Review implication: Build a gap map against the proposed use and system version; separate documented performance claims from independently observed results.

Source: Official Commission AI Act Service Desk: Article 13. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions

Provision: 13(2)-(3);113(c);111(2) · Operator: Provider supplying instructions and deployer/procurement reviewer

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

A model card or marketing sheet is not necessarily complete instructions. This does not establish actual performance, permitted deployment or legal compliance.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do the supplied high-risk-system instructions contain enough specific information for this planned operation?

Buyer evidence still required

  • Versioned instructions
  • intended-use map
  • metric/test context
  • input constraints
  • oversight/maintenance/log collection procedures

Review inference: Build a gap map against the proposed use and system version; separate documented performance claims from independently observed results.

Suggested review condition: A model card or marketing sheet is not necessarily complete instructions. This does not establish actual performance, permitted deployment or legal compliance. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • A model card or marketing sheet is not necessarily complete instructions. This does not establish actual performance, permitted deployment or legal compliance. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • A model card or marketing sheet is not necessarily complete instructions. This does not establish actual performance, permitted deployment or legal compliance.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Design the first AI interaction notice

Question: Does the planned EU-facing chatbot make its AI identity clear at the first interaction?

Providers must design direct human interactions to disclose AI identity unless obvious to a reasonably informed, observant and circumspect person in context; notice must be clear, distinguishable and accessible at first interaction. Review implication: Map each user entry point, notice timing, accessibility and any reasoned obviousness exception before accepting the interaction design.

Source: Official Commission AI Act Service Desk: Article 50. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: CURRENTLY APPLICABLE — 2026-08-02

Provision: 50(1),(5);113 · Operator: Provider of a system intended to interact directly with natural persons

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

Obviousness is contextual, not a blanket chatbot exemption. The authorised criminal-law exception has safeguards and does not cover public crime-reporting systems. A screenshot does not establish every channel works.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does the planned EU-facing chatbot make its AI identity clear at the first interaction?

Buyer evidence still required

  • Interaction map
  • versioned notice
  • accessibility review
  • dated user-flow observation
  • reasoned exception assessment

Review inference: Map each user entry point, notice timing, accessibility and any reasoned obviousness exception before accepting the interaction design.

Suggested review condition: Obviousness is contextual, not a blanket chatbot exemption. The authorised criminal-law exception has safeguards and does not cover public crime-reporting systems. A screenshot does not establish every channel works. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Obviousness is contextual, not a blanket chatbot exemption. The authorised criminal-law exception has safeguards and does not cover public crime-reporting systems. A screenshot does not establish every channel works. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • Obviousness is contextual, not a blanket chatbot exemption. The authorised criminal-law exception has safeguards and does not cover public crime-reporting systems. A screenshot does not establish every channel works.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Document a claimed AnnexIII non-high-risk exception

Question: What supports a provider claiming its Annex III system is not high-risk under Article 6(3)?

Article 6(3) requires no significant risk of harm and one specified condition, such as a narrow procedural or preparatory task. Profiling natural persons remains high-risk. Article 6(4) requires the provider assessment documented before placement/service and registration under 49(2). Review implication: Inspect intended task, influence over decisions and profiling before accepting a documented exception; an internal label is insufficient.

Source: Official Commission AI Act Service Desk: Article 6. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — 2027-12-02

Provision: 6(2)-(4);113(c)(i) · Operator: Provider assessing a system within an Annex III use case

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

No conclusion without exact category and actual task evidence. Registration rules outside Sections 1-3 need their own applicability review; this record does not delay all of Article 49.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What supports a provider claiming its Annex III system is not high-risk under Article 6(3)?

Buyer evidence still required

  • Exact AnnexIII use-case mapping
  • intended task
  • human-decision workflow
  • profiling assessment
  • risk rationale
  • documented pre-placement assessment

Review inference: Inspect intended task, influence over decisions and profiling before accepting a documented exception; an internal label is insufficient.

Suggested review condition: No conclusion without exact category and actual task evidence. Registration rules outside Sections 1-3 need their own applicability review; this record does not delay all of Article 49. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • No conclusion without exact category and actual task evidence. Registration rules outside Sections 1-3 need their own applicability review; this record does not delay all of Article 49. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • No conclusion without exact category and actual task evidence. Registration rules outside Sections 1-3 need their own applicability review; this record does not delay all of Article 49.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Establish EU territorial connection for a UK organisation

Question: Does this UK-only or EU-connected deployment fall within the relevant AI Act operator scope?

The Act includes providers marketing/putting systems into service in the EU, EU-established/located deployers, and third-country providers/deployers whose AI outputs are used in the EU, subject to Article 2 exclusions. Review implication: Map establishment, market/service placement, output use and operator roles before importing EU obligations into a UK procurement decision.

Source: Official Commission AI Act Service Desk: Article 2. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: CONDITIONAL — 2025-02-02

Provision: 2(1)(a)-(c),2(3),(6),(8),(10);113(a) · Operator: UK-established provider or deployer, or procurement reviewer assessing its role

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

UK incorporation alone neither establishes nor excludes EU scope. Research/defence/personal exceptions have exact boundaries; real-world testing is not covered by the pre-market research exclusion. No UK-only automatic EU duty.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does this UK-only or EU-connected deployment fall within the relevant AI Act operator scope?

Buyer evidence still required

  • Legal entity/role map
  • deployment and customer territories
  • output-use flows
  • commercial/personal/research purpose
  • exclusion rationale

Review inference: Map establishment, market/service placement, output use and operator roles before importing EU obligations into a UK procurement decision.

Suggested review condition: UK incorporation alone neither establishes nor excludes EU scope. Research/defence/personal exceptions have exact boundaries; real-world testing is not covered by the pre-market research exclusion. No UK-only automatic EU duty. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • UK incorporation alone neither establishes nor excludes EU scope. Research/defence/personal exceptions have exact boundaries; real-world testing is not covered by the pre-market research exclusion. No UK-only automatic EU duty. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • UK incorporation alone neither establishes nor excludes EU scope. Research/defence/personal exceptions have exact boundaries; real-world testing is not covered by the pre-market research exclusion. No UK-only automatic EU duty.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Identify notices for biometric categorisation or emotion recognition

Question: What notice evidence is needed before deploying an otherwise lawful emotion or biometric categorisation feature?

Covered deployers must inform exposed persons of the system operation and comply with applicable data-protection law; notice must be clear, distinguishable, accessible and no later than first exposure. Review implication: Request exposure/notice mapping and the separate lawful-use assessment; disclosure cannot legitimise a prohibited use.

Source: Official Commission AI Act Service Desk: Article 50. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: CURRENTLY APPLICABLE — 2026-08-02

Provision: 50(3),(5);113 · Operator: Deployer exposing natural persons to an emotion-recognition or biometric-categorisation system

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

Article 50 is not permission to operate a prohibited system. Criminal-law exceptions are narrow and safeguard-dependent. No conclusion on actual processing or GDPR lawfulness from a notice alone.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What notice evidence is needed before deploying an otherwise lawful emotion or biometric categorisation feature?

Buyer evidence still required

  • System-purpose classification
  • affected-person map
  • notice flow
  • accessible alternatives
  • lawful-use and personal-data assessment

Review inference: Request exposure/notice mapping and the separate lawful-use assessment; disclosure cannot legitimise a prohibited use.

Suggested review condition: Article 50 is not permission to operate a prohibited system. Criminal-law exceptions are narrow and safeguard-dependent. No conclusion on actual processing or GDPR lawfulness from a notice alone. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Article 50 is not permission to operate a prohibited system. Criminal-law exceptions are narrow and safeguard-dependent. No conclusion on actual processing or GDPR lawfulness from a notice alone. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • Article 50 is not permission to operate a prohibited system. Criminal-law exceptions are narrow and safeguard-dependent. No conclusion on actual processing or GDPR lawfulness from a notice alone.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Identify the deployer-controlled log retention boundary

Question: Can a supplier retention setting establish that the deployer retains its required high-risk-system logs?

Article 26(6) addresses automatically generated logs to the extent under deployer control, for an intended-purpose-appropriate period of at least 6months unless applicable Union/national law provides otherwise, particularly data protection. Review implication: Map log custody, automatic generation, retention and competing applicable requirements before relying on a supplier dashboard setting.

Source: PE-CONS24/1/24REV1 adopted AIAct. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions

Provision: 26(6);113(c);111(2) · Operator: Deployer of a covered high-risk system

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

No universal rule to retain all personal data 6months. Supplier retention does not prove deployer access or complete event history; exact scope and transition gates apply.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a supplier retention setting establish that the deployer retains its required high-risk-system logs?

Buyer evidence still required

  • Log/control inventory
  • export/retention policy
  • system-purpose rationale
  • other-law retention constraints
  • sample history and gaps

Review inference: Map log custody, automatic generation, retention and competing applicable requirements before relying on a supplier dashboard setting.

Suggested review condition: No universal rule to retain all personal data 6months. Supplier retention does not prove deployer access or complete event history; exact scope and transition gates apply. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • No universal rule to retain all personal data 6months. Supplier retention does not prove deployer access or complete event history; exact scope and transition gates apply. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • No universal rule to retain all personal data 6months. Supplier retention does not prove deployer access or complete event history; exact scope and transition gates apply.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Keep the technical documentation aligned with the system

Question: What evidence supports that the system technical documentation was prepared before placement and kept current?

Article 11 requires pre-market/service technical documentation kept up to date, supplying Annex IV information; eligible SMEs/startups/SMCs may use simplified provision only via the prescribed Commission form. Product systems under Annex I Section A use a combined documentation set. Review implication: Check version/change linkage and evidence completeness rather than accepting a stale file or an invented simplified form.

Source: Official Commission AI Act Service Desk: Article 11. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions

Provision: 11(1)-(2) as amended;113(c);111(2) · Operator: Provider of a covered high-risk system

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

Documents do not demonstrate actual compliance automatically. No 10-year retention assertion here; that is a separate Article 18 duty. No assumption a Commission form exists or self-created form qualifies.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: What evidence supports that the system technical documentation was prepared before placement and kept current?

Buyer evidence still required

  • System/document version mapping
  • dated pre-placement documentation
  • change history
  • AnnexIV gap map
  • eligibility and actual prescribed form if relied on

Review inference: Check version/change linkage and evidence completeness rather than accepting a stale file or an invented simplified form.

Suggested review condition: Documents do not demonstrate actual compliance automatically. No 10-year retention assertion here; that is a separate Article 18 duty. No assumption a Commission form exists or self-created form qualifies. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Documents do not demonstrate actual compliance automatically. No 10-year retention assertion here; that is a separate Article 18 duty. No assumption a Commission form exists or self-created form qualifies. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • Documents do not demonstrate actual compliance automatically. No 10-year retention assertion here; that is a separate Article 18 duty. No assumption a Commission form exists or self-created form qualifies.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Prepare the deployer response to a risk indication

Question: What response evidence is needed when a deployer has reason to consider the system presents Article 79(1) risk?

Under 26(5), deployers monitor on instructions; where they have reason to consider instructed use may present 79(1) risk, they inform provider/distributor and relevant market-surveillance authority without undue delay and suspend use. Serious incidents have additional immediate notification rules. Review implication: Map risk trigger, accountable suspension authority and notification path; retain actual timestamps separately from written procedures.

Source: PE-CONS24/1/24REV1 adopted AIAct. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions

Provision: 26(5);113(c);111(2) · Operator: Deployer of a covered high-risk system

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

This does not establish that a risk or reportable incident actually occurred, nor resolve provider Article 73 deadlines. A procedure is not evidence it was executed.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: What response evidence is needed when a deployer has reason to consider the system presents Article 79(1) risk?

Buyer evidence still required

  • Provider instructions
  • monitoring/risk signal
  • decision/notification chronology
  • suspension authority/procedure
  • recipient mapping

Review inference: Map risk trigger, accountable suspension authority and notification path; retain actual timestamps separately from written procedures.

Suggested review condition: This does not establish that a risk or reportable incident actually occurred, nor resolve provider Article 73 deadlines. A procedure is not evidence it was executed. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • This does not establish that a risk or reportable incident actually occurred, nor resolve provider Article 73 deadlines. A procedure is not evidence it was executed. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • This does not establish that a risk or reportable incident actually occurred, nor resolve provider Article 73 deadlines. A procedure is not evidence it was executed.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Scope a fundamental-rights assessment and DPIA reuse

Question: Is this deployer within the FRIA scope, and can existing DPIA material cover particular elements?

Article 27 covers specified public-law/public-service deployers and Annex III5(b)/(c) deployers, excluding Annex III point 2. Assessment is before deployment/first use, with updates for changed elements; amended 4 permits relevant DPIA cross-references or incorporated sections where requirements are already met. Review implication: Check deployer/use-case eligibility, then map each required FRIA element to actual evidence; do not equate a DPIA title with complete coverage.

Source: Official Commission AI Act Service Desk: Article 27. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — 2027-12-02 subject to 111

Provision: 27(1)-(5),including amended 4-5;113(c)(i) · Operator: Covered Article 27 deployer of an Article 6(2) system

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

Not every enterprise requires a FRIA under 27. Reuse is element-specific; notification/template/exemption requirements remain separate. No fundamental-rights clearance or legal opinion.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Is this deployer within the FRIA scope, and can existing DPIA material cover particular elements?

Buyer evidence still required

  • Operator status
  • exact AnnexIII mapping
  • affected groups/processes
  • use duration/frequency
  • risks
  • oversight
  • governance/complaints
  • DPIA section map

Review inference: Check deployer/use-case eligibility, then map each required FRIA element to actual evidence; do not equate a DPIA title with complete coverage.

Suggested review condition: Not every enterprise requires a FRIA under 27. Reuse is element-specific; notification/template/exemption requirements remain separate. No fundamental-rights clearance or legal opinion. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Not every enterprise requires a FRIA under 27. Reuse is element-specific; notification/template/exemption requirements remain separate. No fundamental-rights clearance or legal opinion. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • Not every enterprise requires a FRIA under 27. Reuse is element-specific; notification/template/exemption requirements remain separate. No fundamental-rights clearance or legal opinion.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Scope deepfake disclosure and artistic presentation

Question: How should a publisher document its deepfake disclosure decision, including creative material?

For content constituting a deep fake, covered deployers disclose artificial generation/manipulation. Evidently artistic, creative, satirical, fictional or analogous work permits appropriate disclosure that does not hamper enjoyment; it does not remove disclosure entirely. Review implication: Assess whether the content meets the legal deepfake definition, then document format/timing of disclosure including the creative-work rationale.

Source: Official Commission AI Act Service Desk: Article 50. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: CURRENTLY APPLICABLE — 2026-08-02

Provision: 50(4) first subparagraph;50(5);3(60);113 · Operator: Deployer publishing AI-generated/manipulated image, audio or video constituting a deep fake

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

Not every AI image is a deep fake. The authorised criminal-law exception requires its own basis. No authenticity finding, identity adjudication or blanket satire exemption is supplied.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: How should a publisher document its deepfake disclosure decision, including creative material?

Buyer evidence still required

  • Content examples
  • depicted existing entities/events
  • authenticity-appearance assessment
  • publication context
  • disclosure design

Review inference: Assess whether the content meets the legal deepfake definition, then document format/timing of disclosure including the creative-work rationale.

Suggested review condition: Not every AI image is a deep fake. The authorised criminal-law exception requires its own basis. No authenticity finding, identity adjudication or blanket satire exemption is supplied. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Not every AI image is a deep fake. The authorised criminal-law exception requires its own basis. No authenticity finding, identity adjudication or blanket satire exemption is supplied. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • Not every AI image is a deep fake. The authorised criminal-law exception requires its own basis. No authenticity finding, identity adjudication or blanket satire exemption is supplied.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Separate machine-readable marking from visible labelling

Question: Is a visible AI label alone enough for the provider marking decision on a newly marketed generator?

For covered systems placed on the market on or after 2 August 2026, outputs must be machine-readably marked and detectable as artificial; effectiveness, interoperability, robustness and reliability are required as technically feasible, considering content limits, cost and state of the art. Review implication: Request output-format and detection evidence rather than treating a visible caption as machine-readable provenance.

Source: Official Commission AI Act Service Desk: Article 50. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: CURRENTLY APPLICABLE — 2026-08-02

Provision: 50(2);111(4);113 · Operator: Provider of a synthetic audio/image/video/text-generating AI system

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

Article 50(2) has standard-editing/non-substantial-alteration and authorised criminal-law exceptions. Marks alone do not certify compliance or establish authenticity; legacy systems require the separate 111(4) check.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Is a visible AI label alone enough for the provider marking decision on a newly marketed generator?

Buyer evidence still required

  • Market-placement date
  • output-format inventory
  • marking design
  • sample output/detector observations
  • known stripping and transformation limits

Review inference: Request output-format and detection evidence rather than treating a visible caption as machine-readable provenance.

Suggested review condition: Article 50(2) has standard-editing/non-substantial-alteration and authorised criminal-law exceptions. Marks alone do not certify compliance or establish authenticity; legacy systems require the separate 111(4) check. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • Article 50(2) has standard-editing/non-substantial-alteration and authorised criminal-law exceptions. Marks alone do not certify compliance or establish authenticity; legacy systems require the separate 111(4) check. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • Article 50(2) has standard-editing/non-substantial-alteration and authorised criminal-law exceptions. Marks alone do not certify compliance or establish authenticity; legacy systems require the separate 111(4) check.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Set provision-specific readiness deadlines

Question: Which deadline should this high-risk readiness plan assign to Chapter III Sections 1-3?

Amended 113(c) applies Chapter III Sections 1-3 except 6(5) from 2 December 2027 for 6(2)/Annex III systems and 2 August 2028 for 6(1)/Annex I systems. Article 111 may alter legacy-system treatment. Review implication: Tag each obligation with chapter/section, system route and transition instead of assigning one date to the whole Act.

Source: Official Commission AI Act Service Desk: Article 113. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: FUTURE OBLIGATION — 2027-12-02 / 2028-08-02

Provision: 113(c)(i)-(ii) replaced by 2026/1744 Art 1(40);111 · Operator: Provider/deployer programme owner

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.

This is not a blanket delay for all high-risk duties. Articles 72/73 and other chapters need their own analysis; Article 50 and prohibited-practice duties are not postponed by 113(c).

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Which deadline should this high-risk readiness plan assign to Chapter III Sections 1-3?

Buyer evidence still required

  • Obligation-to-provision inventory
  • classification rationale
  • market/service date
  • design-change history
  • public-authority use

Review inference: Tag each obligation with chapter/section, system route and transition instead of assigning one date to the whole Act.

Suggested review condition: This is not a blanket delay for all high-risk duties. Articles 72/73 and other chapters need their own analysis; Article 50 and prohibited-practice duties are not postponed by 113(c). Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • This is not a blanket delay for all high-risk duties. Articles 72/73 and other chapters need their own analysis; Article 50 and prohibited-practice duties are not postponed by 113(c). Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • This is not a blanket delay for all high-risk duties. Articles 72/73 and other chapters need their own analysis; Article 50 and prohibited-practice duties are not postponed by 113(c).
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

EU AI Act: Test the claimed standard-editing exception

Question: Does an editing-only claim justify excluding this output transformation from provider marking?

The marking duty does not apply to the extent a system assists standard editing or does not substantially alter deployer input data or its semantics. Review implication: Compare representative input/output transformations and feature scope before accepting an editing exception; separate unsupported feature modes.

Source: Official Commission AI Act Service Desk: Article 50. Documentation checked 2026-11-14; no deployment validation is claimed.

Legal status: CONDITIONAL — 2026-08-02

Provision: 50(2);113 · Operator: Provider relying on an Article 50(2) exception

Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.

The words editing assistant are insufficient. Unknown extent of alteration blocks a conclusion; no blanket exception for all outputs of a multipurpose generator.

Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an editing-only claim justify excluding this output transformation from provider marking?

Buyer evidence still required

  • Feature/mode inventory
  • paired input/output examples
  • documented semantic changes
  • provider rationale

Review inference: Compare representative input/output transformations and feature scope before accepting an editing exception; separate unsupported feature modes.

Suggested review condition: The words editing assistant are insufficient. Unknown extent of alteration blocks a conclusion; no blanket exception for all outputs of a multipurpose generator. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Source-qualified law and documentary review inference only. Buyer-specific configuration, actual notice delivery, control effectiveness, event completeness and legal compliance are unobserved.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact provisions and amendments, classification, territorial use, market-placement date and any relied-on transition before use. Guidance is nonbinding; do not substitute a summary for law.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
  • The words editing assistant are insufficient. Unknown extent of alteration blocks a conclusion; no blanket exception for all outputs of a multipurpose generator. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
  • The words editing assistant are insufficient. Unknown extent of alteration blocks a conclusion; no blanket exception for all outputs of a multipurpose generator.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Event Grid: Order, bounded retries and dead letters

Question: Does Event Grid guarantee ordered delivery until a subscriber succeeds?

Event Grid attempts at-least-once delivery without guaranteeing event order. Retry behaviour depends on error type and configured limits; some failures are not retried. Events can be dropped when limits are reached or no dead-letter destination exists. Consumers need evidence of ordering and recovery appropriate to their workflow.

Source: Azure Event Grid delivery and retry. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Event Grid guarantees ordered, indefinitely retried processing.

Buyer evidence still required

  • Subscription retry limits and endpoint error handling.
  • Dead-letter storage and write permissions.
  • Consumer ordering, deduplication and replay policy.

Suggested review condition: Do not infer ordered business processing from durable event delivery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Endpoint type, subscription limits, dead-letter destination and consumer state handling.

Optional saved evidence: Preserve the delivery limitations used to assess an event-driven supplier integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

EventBridge archive freshness coverage

Question: Can an immediate EventBridge archive count prove all recent events are available for replay?

Archive ingestion can lag receipt on the bus. AWS recommends delaying replay for ten minutes; DescribeArchive EventCount and SizeBytes can take 24 hours to reconcile new or expired events. These values and the recommended delay are not independent proof of complete capture; reconcile required event identities and the replay window.

Source: Amazon Web Services: EventBridge archives. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an immediate EventBridge archive count prove all recent events are available for replay?

Buyer evidence still required

  • archive filter
  • selected time range
  • event identities
  • capture lag
  • count observation time
  • replay results

Review inference: An incident responder immediately checks an archive before replaying recent actions. Recent events can be missed or completeness inferred from stale counts. Adds archive freshness and count reconciliation rather than rule-delivery retries. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat an archive count or recommended wait as a completeness guarantee.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. reconciliation period of 24 hours

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat an archive count or recommended wait as a completeness guarantee.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

EventBridge missing bus success response

Question: Can EventBridge return HTTP 200 while dropping an event sent to a nonexistent bus?

AWS documents that publishing with PutEvents to a bus that does not exist can return 200 without counting the event in FailedEntryCount. Matching finds no rule and drops the event. Verify the intended account, region and bus identity rather than treating a successful response and zero failed entries as delivery evidence.

Source: Amazon Web Services: EventBridge PutEvents. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can EventBridge return HTTP 200 while dropping an event sent to a nonexistent bus?

Buyer evidence still required

  • target bus identity and existence
  • account and region
  • request response
  • downstream evidence

Review inference: An environment migration leaves the producer using the wrong event bus. Events disappear despite apparently successful publishing. Adds a documented ingestion blind spot before target retry policies can apply. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Neither HTTP success nor a zero failure count proves bus existence or target execution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. event bus that does not exist

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Neither HTTP success nor a zero failure count proves bus existence or target execution.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

EventBridge PutEvents partial entry result

Question: Does an EventBridge PutEvents response establish that every entry was accepted?

A PutEvents batch can contain both successful entries with EventId and failed entries with ErrorCode and ErrorMessage. Reconcile each response entry with its corresponding request entry and retry only unresolved failures with application-level duplicate controls. Batch-level transport success is not a complete per-event outcome or downstream delivery receipt.

Source: Amazon Web Services: EventBridge PutEvents. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an EventBridge PutEvents response establish that every entry was accepted?

Buyer evidence still required

  • original batch order and identifiers
  • response entries
  • failure codes
  • retry history
  • target evidence

Review inference: A producer retries an entire batch after one event fails. Already accepted work can be emitted again. Covers producer-side batch admission rather than the existing target-delivery retry limits. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Accepted entries do not establish target delivery or business completion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. FailedEntryCount

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Accepted entries do not establish target delivery or business completion.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

EventBridge replay order not preserved

Question: Does EventBridge archive replay preserve the original event order?

Archived events are not necessarily replayed in their original arrival order. Replay selection uses event time and processes one-minute intervals; replay metadata identifies the replay. Consumers must reconcile action identities and ordering requirements rather than assume replay reproduces the original execution sequence.

Source: Amazon Web Services: EventBridge archives. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does EventBridge archive replay preserve the original event order?

Buyer evidence still required

  • archive and replay IDs
  • event timestamps
  • business action IDs
  • ordering requirements
  • resulting effects

Review inference: An operator replays a sequence containing creation, amendment and cancellation. Reordered application effects can diverge from the original state. Adds EventBridge archive replay ordering, distinct from Pub/Sub ordering-key delivery. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Replay does not validate causality, restore business state atomically or prevent repeated effects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Events aren't necessarily replayed

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Replay does not validate causality, restore business state atomically or prevent repeated effects.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

EventBridge: Retry exhaustion and retained failures

Question: Does an EventBridge rule guarantee eventual delivery to its target?

EventBridge retries retriable target failures within configured age and attempt limits. The documented defaults are bounded, and exhausted delivery attempts can end in a dropped event. A dead-letter queue needs separate configuration; a rule existing is not evidence that undelivered events are retained or recovered.

Source: EventBridge retry policy. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A configured rule retries until delivery succeeds.

Buyer evidence still required

  • Target retry age and attempt settings.
  • Dead-letter destination and permissions.
  • Failure monitoring and replay ownership.

Suggested review condition: Require an exhaustion and recovery plan before asserting eventual delivery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Rule target, retry policy, dead-letter configuration and operational replay ownership.

Optional saved evidence: Retain the documented delivery limits used to assess a supplier event integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Exa MCP: Free search access and billable research tools

Question: Can adding Exa authentication expose billable research beyond keyless search?

Exa documents keyless rate-limited access and authenticated modes. The authenticated default tool set includes a usage-billed research operation, while explicit tool selection replaces the defaults. Check the exposed tools and spending authority after connecting credentials; a successful search does not authorize a broader research run.

Source: Exa MCP search and authenticated research billing. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official hosted keyless and authenticated MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Exa operates the hosted MCP service.

Documented by publisher. Exa MCP search and authenticated research billing

Purpose

Search and fetch web content, with authenticated research capabilities.

Documented by publisher. Exa MCP search and authenticated research billing

Read capability

Web search, page content and structured research outputs.

Documented by publisher. Exa MCP search and authenticated research billing

Write capability

Research execution can consume billable usage; no business-system write capability is established here.

Review inference. Exa MCP search and authenticated research billing

Authentication

Keyless access, OAuth or API-key authentication.

Documented by publisher. Exa MCP search and authenticated research billing

Permission surface

Authenticated defaults and explicit tool selections expose different capabilities.

Documented by publisher. Exa MCP search and authenticated research billing

Data leaving the environment

Queries and research inputs go to Exa and results return to the client.

Review inference. Exa MCP search and authenticated research billing

Failure modes to consider

Adding authentication can introduce an unapproved spending path.

Review inference. Exa MCP search and authenticated research billing

Unknowns and applicability

Actual team, credits, task cost and result completeness are unverified.

Not established

Suggested refusal or clarification condition

Require an agreed research scope and budget before usage-billed execution.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck default tools, account billing and explicit tool selection.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the tool and spending boundary chosen before an authenticated research task.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Exchange application RBAC and additive grants

Question: Does a scoped Exchange application RBAC assignment restrict an existing unscoped Entra application grant?

Microsoft describes Exchange application RBAC and Entra application permissions as additive. An unscoped Entra grant can therefore provide access beyond a scoped RBAC assignment. Application Access Policies constrain the Entra grant path; they do not turn the separate RBAC assignment into a restriction on all other grants.

Source: Role Based Access Control for Applications in Exchange Online | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a scoped Exchange application RBAC assignment restrict an existing unscoped Entra application grant?

Buyer evidence still required

  • Application identity and Entra consented permissions
  • Exchange RBAC assignments and resource scopes
  • Applicable Application Access Policies and mailbox access evidence

Review inference: Evaluate the union of effective grant paths before accepting a mailbox restriction.

Suggested review condition: Reject a least-privilege conclusion based on the scoped RBAC assignment alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Effective grants and mailbox access in the buyer tenant are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid approving a mailbox integration whose other grant path remains broad.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal mailbox restriction from one scoped grant
  • Effective grants and mailbox access in the buyer tenant are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Fabric Core MCP: Resource-management authority

Question: Is Fabric Core MCP only a data-query connection?

The preview Core endpoint manages resources, including workspace and item changes and workspace role assignments. It uses the authenticated Entra identity's Fabric permissions. These resource-management tools are not general-purpose lakehouse table-query tools. Supported-operation audit records and client approval settings must be assessed separately.

Source: Fabric Core MCP capabilities and boundaries. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; deployed buyer configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Microsoft hosts the Fabric Core endpoint.

Documented by publisher. Fabric Core MCP capabilities and boundaries; Fabric Core MCP authentication

Purpose

Manage Fabric workspaces, items and permissions.

Documented by publisher. Fabric Core MCP capabilities and boundaries; Fabric Core MCP authentication

Read capability

Catalog, item, workspace and capacity information.

Documented by publisher. Fabric Core MCP capabilities and boundaries; Fabric Core MCP authentication

Write capability

Create, change or delete resources and change workspace roles.

Documented by publisher. Fabric Core MCP capabilities and boundaries; Fabric Core MCP authentication

Authentication

Microsoft Entra OAuth with a compatible HTTP client.

Documented by publisher. Fabric Core MCP capabilities and boundaries; Fabric Core MCP authentication

Permission surface

The executing identity must hold the relevant Fabric permissions.

Documented by publisher. Fabric Core MCP capabilities and boundaries; Fabric Core MCP authentication

Data leaving the environment

Resource metadata can pass to the client and its model provider.

Review inference. Fabric Core MCP capabilities and boundaries; Fabric Core MCP authentication

Failure modes to consider

Confusing Core with a read-only query server can authorize destructive actions.

Review inference. Fabric Core MCP capabilities and boundaries; Fabric Core MCP authentication

Unknowns and applicability

Tenant grants, client safeguards and operation-level audit coverage are unverified.

Not established

Suggested refusal or clarification condition

Require the exact resource-management action and executing identity before changes.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Preview tool list, role grants, audit coverage and client approval handling.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the distinction between resource administration and analytical access when selecting an agent connection.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Falcon MCP: Tool filtering and HTTP authentication

Question: Does selecting Falcon MCP modules prove the connection is read-only and authenticated?

Modules select a tool surface, while the read-only filter removes mutations and explicit tool additions can extend module selection. HTTP transport has no authentication by default and normally binds to loopback. A network-accessible deployment needs its separate authentication reviewed; Falcon API credentials alone do not authenticate incoming MCP callers.

Source: CrowdStrike Falcon MCP configuration. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer deployment unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

CrowdStrike publishes Falcon MCP; the deployment operator hosts it.

Documented by publisher. CrowdStrike Falcon MCP configuration; CrowdStrike Falcon MCP tool filtering

Purpose

Inspect Falcon security data and invoke enabled operations.

Documented by publisher. CrowdStrike Falcon MCP configuration; CrowdStrike Falcon MCP tool filtering

Read capability

Allowed detections, host and security records.

Documented by publisher. CrowdStrike Falcon MCP configuration; CrowdStrike Falcon MCP tool filtering

Write capability

Mutating tools may be exposed unless filtered out.

Documented by publisher. CrowdStrike Falcon MCP configuration; CrowdStrike Falcon MCP tool filtering

Authentication

Falcon API client credentials; separate optional HTTP API-key authentication.

Documented by publisher. CrowdStrike Falcon MCP configuration; CrowdStrike Falcon MCP tool filtering

Permission surface

API scopes, child customer ID and server tool filters all matter.

Documented by publisher. CrowdStrike Falcon MCP configuration; CrowdStrike Falcon MCP tool filtering

Data leaving the environment

Security records pass through the MCP server to the agent.

Review inference. CrowdStrike Falcon MCP configuration; CrowdStrike Falcon MCP tool filtering

Failure modes to consider

A narrow module list can be extended; network binding without caller authentication exposes credential-backed operations.

Review inference. CrowdStrike Falcon MCP configuration; CrowdStrike Falcon MCP tool filtering

Unknowns and applicability

Installed revision, enabled tools, network reachability and grants were not tested.

Not established

Suggested refusal or clarification condition

Require effective tool and caller-authentication evidence before tenant access.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Tool selection precedence, remote authentication and customer-ID configuration.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the exact access-control questions used to review a security-operations connection.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Fastly soft purge: Stale marking is not immediate removal

Question: Does a successful soft purge prove cached content can no longer be served?

Soft purge marks content stale and can leave it available during revalidation or other configured stale-serving conditions. Fastly distinguishes this from hard invalidation. Identify the purge method and cache behaviour before treating a purge response as evidence that old content is unavailable.

Source: Fastly soft purge and stale delivery. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The purge response proves immediate removal of the old content.

Buyer evidence still required

  • Exact purge method and target scope.
  • Stale-while-revalidate and stale-on-error configuration.
  • Authorised observation of the relevant content after the operation.

Suggested review condition: Do not report immediate unavailability from a soft-purge acknowledgement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Cache policy, purge type and origin revalidation behaviour.

Optional saved evidence: Save the difference between an accepted cache action and verified content-removal behaviour.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

FencedLock: Stale workers and external effects

Question: Can an old Hazelcast lock holder still act after a new worker acquires the lock?

Hazelcast 5.7 describes a paused client losing its CP session while another client acquires the lock; the old client can resume unaware that ownership changed. Monotonic fencing tokens let a cooperating external resource reject stale owners. This protection depends on the external resource using the tokens. The default CP unsafe mode has weaker consistency guarantees.

Source: Hazelcast: FencedLock. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an old Hazelcast lock holder still act after a new worker acquires the lock?

Buyer evidence still required

  • Hazelcast version, CP mode, session settings and lock ownership history.
  • Fencing token supplied with each external operation and the resource-side comparison behavior.
  • Observed acceptance or rejection of stale-owner operations and resulting resource state.

Suggested review condition: Decline stale-worker exclusion claims without evidence of the external resource enforcing token order under the deployed CP configuration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Hazelcast version, CP mode, session settings and lock ownership history. Fencing token supplied with each external operation and the resource-side comparison behavior. Observed acceptance or rejection of stale-owner operations and resulting resource state.

Optional saved evidence: Worker takeover must not be mistaken for revocation of an old worker's ability to write to an external system.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic external-resource fencing, credential revocation or an INDEX enforcement mechanism
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

FHIR Bulk Data partial export reconciliation

Question: Does a completed FHIR Bulk Data export with HTTP 200 guarantee a complete error-free dataset?

Bulk Data Access 3.0 permits partial success to use HTTP 200. Its output manifest has an error array linking OperationOutcome files, including warnings and information, and can link further manifests when partial manifests are enabled. Clients must reconcile those files and links with requested types and authorization scope.

Source: Export - Bulk Data Access IG v3.0.0. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a completed FHIR Bulk Data export with HTTP 200 guarantee a complete error-free dataset?

Buyer evidence still required

  • Kick-off parameters and authorized resource types
  • Complete manifest chain and downloaded outputs
  • OperationOutcome files and expected population

Review inference: Inspect every manifest page, output file and outcome before accepting the export.

Suggested review condition: Do not accept export completeness from the polling status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s exported population and unresolved outcomes are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Expose missing or failed export material before migration acceptance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Clinical completeness or lossless export from HTTP success
  • The buyer’s exported population and unresolved outcomes are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

FHIR capability declarations and deployed instances

Question: Does every FHIR CapabilityStatement describe the controls enforced by a deployed endpoint?

FHIR R5 distinguishes instance, capability and requirements statements. An instance statement describes a deployed configured solution; a capability statement describes software capabilities independently of a particular installation; a requirements statement describes desired capabilities. The statement kind and implementation reference therefore matter when assessing a concrete endpoint.

Source: CapabilityStatement - FHIR v5.0.0. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does every FHIR CapabilityStatement describe the controls enforced by a deployed endpoint?

Buyer evidence still required

  • CapabilityStatement kind and implementation URL
  • Software version and endpoint identity
  • Observed authorization and interaction results

Review inference: Bind the statement to the deployed instance and verify the relevant behaviour separately.

Suggested review condition: Reject deployed-control conclusions based on a requirements or generic capability statement alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer endpoint’s actual conformance and enforcement are untested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid accepting a deployment on the basis of generic feature declarations.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Certification from publishing a CapabilityStatement
  • The buyer endpoint’s actual conformance and enforcement are untested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

FHIR delete and retained version history

Question: Does a successful FHIR R5 DELETE erase all historical versions and physical copies of a resource?

FHIR R5 defines DELETE as removing a resource from ordinary search and non-version-specific access. For servers maintaining version history, the interaction does not remove that history. Resource deletion also does not imply a change to the corresponding real-world object unless the resource documentation specifies it.

Source: Http - FHIR v5.0.0. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a successful FHIR R5 DELETE erase all historical versions and physical copies of a resource?

Buyer evidence still required

  • Server history support and resource identifier
  • Deletion response and version-specific access policy
  • Separate retention, backup and purge evidence

Review inference: Require separate history-purge and storage-disposition evidence where complete erasure is required.

Suggested review condition: Decline complete-erasure claims supported only by the DELETE response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Retained histories, backups and physical deletion are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Define the residual-data checks needed for a clinical-system exit.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified deletion of clinical records or real-world treatment state
  • Retained histories, backups and physical deletion are unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

FHIR provenance assertions and clinical truth

Question: Does a FHIR Provenance resource or signature establish that its clinical content is true?

FHIR R5 defines Provenance as record-keeping assertions about activities and agents that created, revised, deleted or signed a resource version. Applications prepare these assertions; signatures can target the resource. The information supports assessment and further investigation of origins, rather than independently establishing the truth of clinical facts.

Source: Provenance - FHIR v5.0.0. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a FHIR Provenance resource or signature establish that its clinical content is true?

Buyer evidence still required

  • Target resource version and provenance author
  • Signature verification and signer authority where supplied
  • Underlying observation or source-record evidence

Review inference: Verify target versions and provenance authors, then assess the underlying clinical evidence separately.

Suggested review condition: Do not accept clinical truth solely from provenance metadata or a signature field.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The asserted activity, signer validity and clinical facts are not independently checked.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep evidence origin separate from the reliability of a clinical assertion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Medical correctness or authentication from an unverified signature field
  • The asserted activity, signer validity and clinical facts are not independently checked.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

FHIR R5 activity time versus recording time

Question: Does FHIR AuditEvent.recorded establish when the underlying action occurred?

R5 AuditEvent distinguishes the optional occurred time or period from the mandatory recorded instant. A late-recorded event can therefore have a different activity time. Compare the two with the systems clock evidence; a recording timestamp alone proves neither the activity time nor clock accuracy.

Source: HL7 FHIR R5 5.0.0 — auditevent definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does FHIR AuditEvent.recorded establish when the underlying action occurred?

Buyer evidence still required

  • Occurred time or period
  • Recorded instant
  • Clock synchronization and collection context

Review inference: Reconstruct chronology without confusing logging delay with action timing. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse action-time or clock-accuracy claims based only on recorded.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 append document completeness

Question: Can a FHIR document that appends another document be reviewed as a complete standalone record?

R5 DocumentReference identifies relationships between documents. Where a document appends another, the definition says it cannot be fully understood without the referenced target. A standalone export of the appended material may therefore omit required context even when its own file is complete.

Source: HL7 FHIR R5 5.0.0 — documentreference definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a FHIR document that appends another document be reviewed as a complete standalone record?

Buyer evidence still required

  • Relationship code
  • Referenced target document
  • Appended content and versions

Review inference: Retain the related document needed to interpret an append. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse complete-context claims from an append without its target.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 batch HTTP status and individual outcomes

Question: Does HTTP 200 for a FHIR batch mean every requested change succeeded?

FHIR R5 batches process entries independently. HTTP 200 means the batch was processed correctly, even when individual operations failed; their response entries carry the relevant statuses. A transaction has different all-or-nothing rules. Inspect the bundle type and every entry before marking work complete or deciding what to retry.

Source: HL7 FHIR R5 5.0.0 — http. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does HTTP 200 for a FHIR batch mean every requested change succeeded?

Buyer evidence still required

  • Bundle type
  • Each entry response status
  • Expected operations and resulting resources

Review inference: Reconcile individual operations before retrying a batch. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse complete batch success from the outer HTTP 200 alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 bundle identity and resource version

Question: Does a FHIR Bundle fullUrl uniquely identify the version of every included resource?

R5 Bundle.fullUrl is version-independent and must not contain a history-version reference. Subject to the documented bundle rules, entries can share a fullUrl when their resource versions differ; history bundles have their own exception. Retain the resource version and bundle context before treating the URL as an exact artifact identity.

Source: HL7 FHIR R5 5.0.0 — bundle definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a FHIR Bundle fullUrl uniquely identify the version of every included resource?

Buyer evidence still required

  • Bundle type
  • Entry fullUrl
  • Resource meta.versionId and content

Review inference: Bind bundled evidence to the correct resource version. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse exact-version identity from fullUrl alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 business status versus lifecycle status

Question: Can a FHIR Task businessStatus replace its required workflow status?

R5 Task.status is a required coded lifecycle state. Task.businessStatus is optional and carries workflow-specific detail. A local business label therefore does not replace the standard state or establish a meaning shared by every receiving system; retain both the lifecycle state and the local code definition.

Source: HL7 FHIR R5 5.0.0 — task definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a FHIR Task businessStatus replace its required workflow status?

Buyer evidence still required

  • Required Task.status
  • Business status code
  • Local workflow definition

Review inference: Avoid interpreting local workflow labels as universal completion states. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse lifecycle completion inferred only from an undocumented businessStatus label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 dependent changes need transaction semantics

Question: Can a FHIR batch create one resource and rely on another entry referencing that new resource?

FHIR R5 requires batch changes to be independent. References from one batch entry to a resource being created by another are non-conformant. Linked changes need the appropriate transaction and server-support contract; merely putting them in one HTTP request does not establish atomic execution.

Source: HL7 FHIR R5 5.0.0 — http. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a FHIR batch create one resource and rely on another entry referencing that new resource?

Buyer evidence still required

  • Referenced resources and identities
  • Batch or transaction type
  • Server support and individual results

Review inference: Avoid relying on unsupported dependencies between batched changes. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse atomic linked-change claims from a batch envelope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 event limit versus bundle entries

Question: Does FHIR Subscription.maxCount limit the total number of entries in a notification bundle?

R5 Subscription.maxCount limits the number of events grouped in a notification. It is not a strict limit on the total number of bundle entries, because dependent resources can also be included. Count events using their event structure rather than truncating or rejecting a bundle solely by its entry count.

Source: HL7 FHIR R5 5.0.0 — subscription definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does FHIR Subscription.maxCount limit the total number of entries in a notification bundle?

Buyer evidence still required

  • Subscription maxCount
  • Notification event structure
  • Dependent resource entries

Review inference: Avoid dropping dependent evidence because of an incorrect bundle-size assumption. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse event-count conclusions based solely on total bundle entries.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 event numbering depends on the channel

Question: Is a FHIR subscription event number always a global monotonically increasing sequence?

R5 subscription event numbering depends on channel guarantees. For channels without guaranteed delivery, it is unique and increasing within the subscription; guaranteed-delivery channels may use a relative index within the notification. Interpret gaps or repeats with the channel and subscription context, not as globally unique event numbers.

Source: HL7 FHIR R5 5.0.0 — subscriptionstatus definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is a FHIR subscription event number always a global monotonically increasing sequence?

Buyer evidence still required

  • Subscription identity
  • Channel delivery contract
  • Notification event numbers

Review inference: Avoid false missing-event findings from the wrong sequence scope. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse global sequencing or gap conclusions without the channel context.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 focal coverage and coordination order

Question: Does listing several FHIR claim coverages request adjudication from all those policies?

R5 Claim.insurance identifies one focal coverage for adjudication of that claim. Other listed coverages have a coordination sequence, and claims against them are separate. Listing several policies does not request or establish successful adjudication against all of them, nor verify that any policy remains effective.

Source: HL7 FHIR R5 5.0.0 — claim definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does listing several FHIR claim coverages request adjudication from all those policies?

Buyer evidence still required

  • Listed coverage references
  • Focal flag and sequence
  • Separate claims and adjudication evidence

Review inference: Identify the policy actually targeted by a claim. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse simultaneous-approval or coverage-validity claims from a policy list.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 fulfilment period within authorization

Question: Can a FHIR fulfilment Task restriction period extend beyond its referenced request authorization?

R5 Task.restriction.period bounds the fulfilment sought and must fall within the overall period authorised by the referenced request. A task-local interval does not enlarge that authorization. Compare the requested interval with the applicable request before treating work outside its period as permitted.

Source: HL7 FHIR R5 5.0.0 — task definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a FHIR fulfilment Task restriction period extend beyond its referenced request authorization?

Buyer evidence still required

  • Task restriction period
  • Referenced request authorization period
  • Requested fulfilment scope

Review inference: Prevent a local fulfilment request extending its parent authorization. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse an expanded authorization period inferred from the task interval alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 generated events versus delivered notifications

Question: Does FHIR eventsSinceSubscriptionStart count only successfully delivered notifications?

R5 SubscriptionStatus.eventsSinceSubscriptionStart counts generated events whether or not they were successfully communicated. Handshake and heartbeat notifications do not increment it. The counter therefore cannot be used directly as a count of delivered notifications or completed consumer processing.

Source: HL7 FHIR R5 5.0.0 — subscriptionstatus definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does FHIR eventsSinceSubscriptionStart count only successfully delivered notifications?

Buyer evidence still required

  • Generated-event counter
  • Received event identifiers
  • Delivery and consumer processing evidence

Review inference: Distinguish event generation from delivery and consumption. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse delivered-event or processed-event counts from the generation counter alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 metadata and content security labels

Question: Do DocumentReference.meta.security labels necessarily describe the referenced document sensitivity?

R5 distinguishes DocumentReference.meta.security, describing the reference metadata, from DocumentReference.securityLabel, describing the referenced document. Their sensitivity can differ. A receiver should not infer that access appropriate for the metadata is also appropriate for the document content.

Source: HL7 FHIR R5 5.0.0 — documentreference definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do DocumentReference.meta.security labels necessarily describe the referenced document sensitivity?

Buyer evidence still required

  • Reference metadata security labels
  • Referenced document labels
  • Applicable access policy and recipient

Review inference: Prevent metadata visibility from being treated as content permission. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse document-access authority inferred solely from metadata labels.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 multiple audit observers

Question: Do multiple FHIR AuditEvent records necessarily mean that the same action was executed repeatedly?

FHIR R5 expects participating actors to record an auditable event, so one activity can produce several AuditEvent records. These observations can support cross-system comparison, including finding missing actors or conflicting attributes. Counting the records alone does not establish how many times the underlying action executed.

Source: HL7 FHIR R5 5.0.0 — auditevent. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Do multiple FHIR AuditEvent records necessarily mean that the same action was executed repeatedly?

Buyer evidence still required

  • Participating actor identities
  • Correlated audit records
  • Independent operation identifiers and outcomes

Review inference: Separate observer count from repeated execution. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse duplicate-execution conclusions from raw audit-record counts.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 notification content coverage

Question: Does every FHIR subscription notification contain the complete resource content?

R5 Subscription.content can request empty, identifier-only or full-resource payloads. A notification therefore does not always carry the resource content needed for a saved evidence snapshot. Check the configured mode and actual payload; any follow-up retrieval has its own access and version context.

Source: HL7 FHIR R5 5.0.0 — subscription definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does every FHIR subscription notification contain the complete resource content?

Buyer evidence still required

  • Subscription content mode
  • Actual notification payload
  • Referenced resource and retrieval version

Review inference: Identify when a notification is insufficient as a retained resource snapshot. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse complete resource-content claims from an identifier-only or empty notification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 partial adjudication without detected errors

Question: Does FHIR ClaimResponse outcome partial mean that processing errors were found?

R5 ClaimResponse.outcome distinguishes queued, error, partial and complete processing. Partial means that some adjudication has occurred without detected errors, while complete means all adjudication processing completed without errors. Do not import a generic partial-failure meaning; inspect what processing remains and the reported adjudication.

Source: HL7 FHIR R5 5.0.0 — claimresponse definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does FHIR ClaimResponse outcome partial mean that processing errors were found?

Buyer evidence still required

  • Overall outcome
  • Completed adjudication details
  • Outstanding processing evidence

Review inference: Interpret incomplete adjudication without inventing an error or completion. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse to equate partial automatically with a detected processing error.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 payment adjustments outside the claim

Question: Can a FHIR claim payment adjustment be assumed to arise from that claim adjudication?

R5 ClaimResponse.payment.adjustment describes adjustments not arising from the current claim adjudication, such as recovery of an earlier overpayment. A difference between benefit and payment can therefore have another origin. Reconcile the adjustment and its reason separately from the current claim amount.

Source: HL7 FHIR R5 5.0.0 — claimresponse definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a FHIR claim payment adjustment be assumed to arise from that claim adjudication?

Buyer evidence still required

  • Current adjudicated benefit
  • Payment adjustment and reason
  • Evidence of the separate balance or obligation

Review inference: Explain payment differences without attributing every deduction to the current claim. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse to classify every payment adjustment as a change to the current adjudication.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 payor-added adjudication lines

Question: Can every FHIR adjudication line be matched by position to the originally submitted claim?

R5 ClaimResponse permits payors to add lines or repackage submitted products and services. The addItem structure can link those lines to submitted item, detail or sub-detail identities. Matching response lines by position alone can lose that relationship; retain the explicit links before reconciling an adjudicated amount.

Source: HL7 FHIR R5 5.0.0 — claimresponse definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can every FHIR adjudication line be matched by position to the originally submitted claim?

Buyer evidence still required

  • Original item and detail identifiers
  • Payor-added lines
  • Explicit linkage and adjudicated amounts

Review inference: Match adjudication to the intended submitted claim items. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse positional-only matching where the payor changed line structure.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 preauthorization versus payment

Question: Does a FHIR preauthorization response mean that payment has been made?

R5 ClaimResponse distinguishes preauthorization from an actual claim. A preauthorization response does not itself make a payment, although funds may be reserved for a claim submitted later. Preserve the later claim and financial outcome rather than recording reserved or authorised benefits as money received.

Source: HL7 FHIR R5 5.0.0 — claimresponse. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a FHIR preauthorization response mean that payment has been made?

Buyer evidence still required

  • ClaimResponse use
  • Referenced request
  • Later claim and independent payment evidence

Review inference: Separate reserved benefits from actual payment. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse paid or settled status from a preauthorization response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 predetermination and later benefit

Question: Does a FHIR predetermination guarantee the later claim will receive the same benefit?

R5 predetermination describes a hypothetical adjudication. It makes no payment and does not assure that a later claim will receive the same result; available funds may change. A buyer should retain the date and conditions of the estimate and obtain the later actual adjudication.

Source: HL7 FHIR R5 5.0.0 — claimresponse. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a FHIR predetermination guarantee the later claim will receive the same benefit?

Buyer evidence still required

  • Predetermination response and date
  • Conditions and proposed charges
  • Later claim adjudication

Review inference: Avoid treating an estimated benefit as a locked future commitment. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse guaranteed future benefit from a predetermination alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 provenance target version

Question: Does a FHIR Provenance target always identify one exact resource version?

R5 Provenance targets are usually version-specific, but the definition permits cases where a version is not assigned or the provenance belongs to a maintained document. A target reference can also cover several resources. Resolve the intended resource version before treating the assertion as evidence about one exact artifact.

Source: HL7 FHIR R5 5.0.0 — provenance definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a FHIR Provenance target always identify one exact resource version?

Buyer evidence still required

  • Provenance target references
  • Resolved resource identities and versions
  • Document or transaction context

Review inference: Bind provenance to the version actually relied on. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse exact-version provenance claims from an unresolved target reference.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 query decoding context

Question: Can an auditor interpret a FHIR AuditEvent query blob without its originating query format?

R5 AuditEvent.entity.query stores query input in a base64 container whose meaning depends on the originating event and query format. An audit consumer must understand that format before interpreting it. The encoding does not make the query self-describing or establish that its contents are safe for unrestricted disclosure.

Source: HL7 FHIR R5 5.0.0 — auditevent definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an auditor interpret a FHIR AuditEvent query blob without its originating query format?

Buyer evidence still required

  • Event type and entity role
  • Originating query format
  • Approved handling scope for the decoded content

Review inference: Retain the interpretation context for an encoded audit query. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse semantic interpretation or unrestricted disclosure justified only by base64 encoding.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 recorded delegation versus verified authority

Question: Does FHIR Provenance.onBehalfOf independently verify the recorded delegation?

R5 Provenance.agent.onBehalfOf records the agent that delegated authority to the acting agent. Defined identity constraints prohibit specified self-delegation patterns, but structural validity is not independent verification of the delegation or its permitted scope. Retain the underlying authority evidence for the administrative action.

Source: HL7 FHIR R5 5.0.0 — provenance definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does FHIR Provenance.onBehalfOf independently verify the recorded delegation?

Buyer evidence still required

  • Acting and delegating agent references
  • Applicable delegation scope
  • Independent authority evidence

Review inference: Separate a delegation assertion from verified authority to act. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse verified-delegation claims from the onBehalfOf field alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 reference and document provenance

Question: Does provenance of a FHIR DocumentReference establish who created the underlying document?

R5 describes two provenance histories: the underlying document and the DocumentReference that points to it. Another actor may create the reference later, and its metadata describes that reference history. Preserve the document origin separately rather than attributing authorship of the content to whoever created its reference.

Source: HL7 FHIR R5 5.0.0 — documentreference. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does provenance of a FHIR DocumentReference establish who created the underlying document?

Buyer evidence still required

  • Document provenance
  • Reference provenance
  • Document and reference version bindings

Review inference: Avoid confusing an indexing actor with the document creator. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse content-authorship attribution from reference provenance alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 reference currency versus final content

Question: Does a current FHIR DocumentReference mean its underlying document is final?

R5 DocumentReference.status describes the reference object; docStatus describes the underlying document lifecycle. A current reference can point to a document with another lifecycle state. Read both rather than treating current metadata as evidence that the content is final, approved or unchanged.

Source: HL7 FHIR R5 5.0.0 — documentreference definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a current FHIR DocumentReference mean its underlying document is final?

Buyer evidence still required

  • Reference status
  • Underlying document status
  • Applicable document version

Review inference: Separate a current document pointer from final document content. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse final-content claims from reference status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 separate resource completion tracking

Question: Can one FHIR Task focus identify several resources whose completion needs separate tracking?

R5 Task.focus identifies at most one resource. Its definition directs implementations to use subtasks when multiple resources need manipulation so their statuses can be tracked independently. A parent task status should not be substituted for the missing completion evidence of each resource-specific operation.

Source: HL7 FHIR R5 5.0.0 — task definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can one FHIR Task focus identify several resources whose completion needs separate tracking?

Buyer evidence still required

  • Parent task and focus
  • Resource-specific subtasks
  • Each subtask outcome

Review inference: Retain per-resource outcomes in multi-resource administrative work. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse complete multi-resource work from a parent status without the relevant individual outcomes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 success and transfer completeness

Question: Does a successful FHIR AuditEvent outcome establish that an entire transfer completed?

The R5 AuditEvent outcome definition allows a success indication to cover a partial or interrupted transfer for accountability purposes. A successful audit status therefore does not establish that every expected item arrived. Reconcile the operation-specific scope and receiving evidence before marking the transfer complete.

Source: HL7 FHIR R5 5.0.0 — auditevent definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a successful FHIR AuditEvent outcome establish that an entire transfer completed?

Buyer evidence still required

  • Audit outcome and operation type
  • Expected transfer scope
  • Receiving-side completion evidence

Review inference: Identify transfer completeness evidence missing from a success status. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse complete-transfer claims from the audit success indication alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 task authority and action target

Question: Are FHIR Task.basedOn and Task.focus interchangeable references to the work being fulfilled?

R5 Task.basedOn references higher-level authorization that triggered a task, while Task.focus identifies the request being fulfilled or resource being acted on. The specification distinguishes these references. Replacing one with the other can lose either the authority context or the actual target of the proposed work.

Source: HL7 FHIR R5 5.0.0 — task definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Are FHIR Task.basedOn and Task.focus interchangeable references to the work being fulfilled?

Buyer evidence still required

  • Task.basedOn references
  • Task.focus reference
  • Requested administrative action

Review inference: Preserve both the task target and its authority context. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse to substitute a higher-level authorization reference for the resource being acted on.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 task ownership and actual performer

Question: Does a FHIR Task owner identify who actually performed the task?

R5 Task separates the owner responsible for managing execution, the requested performer and the entity reported as having performed the task. A task may be created before its owner is identified. An assignment or requested role is therefore not evidence that the named party actually performed the work.

Source: HL7 FHIR R5 5.0.0 — task definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a FHIR Task owner identify who actually performed the task?

Buyer evidence still required

  • Task owner
  • Requested performer
  • Recorded performer and outcome evidence

Review inference: Avoid attributing execution from assignment alone. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse actual-performer attribution based only on task ownership.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 unknown event initiator

Question: Should an auditor infer the FHIR event initiator from the first listed agent?

R5 AuditEvent.agent.requestor identifies the initiator, with false as the meaning when it is absent. The specification says not to select an initiator when that identity is unclear. Agent order or mere participation does not resolve an unknown initiator; preserve that uncertainty in the reconstruction.

Source: HL7 FHIR R5 5.0.0 — auditevent definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Should an auditor infer the FHIR event initiator from the first listed agent?

Buyer evidence still required

  • Agent identities
  • Explicit requestor indicators
  • Evidence supporting initiation

Review inference: Avoid attributing an action to an unsupported initiator. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse initiator attribution based only on list position or an absent flag.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

FHIR R5 warnings versus failed operations

Question: Does a FHIR Bundle entry response outcome always represent an operation failure?

R5 Bundle.entry.response.outcome carries hints or warnings for an entry. It is not the error location for every failed operation: batch failures are represented in the entry response, while a failed transaction returns a single OperationOutcome instead of a response bundle. Interpret the status and response structure together.

Source: HL7 FHIR R5 5.0.0 — bundle definitions. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a FHIR Bundle entry response outcome always represent an operation failure?

Buyer evidence still required

  • Bundle type or standalone outcome
  • Entry response status
  • Outcome severity and context

Review inference: Avoid misclassifying warnings as failures or overlooking real errors. This is a documentation-review judgment, not an observed outcome.

Suggested review condition: Refuse failure classification from the presence of response.outcome alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The applicable implementation guide, live system and actual administrative outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.
  • No independent proof of a live access decision, completed workflow, physical action or settled payment.
  • The published R5 definition does not establish support or conformance in a buyer implementation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Figma AI evidence: Feature access and content-training settings

Question: Can Figma AI be enabled while our team content is excluded from model training?

Figma documents separate controls for AI feature access and content training. Training defaults depend on plan, and switching training off applies to new content and edits. Verify the actual team or organization setting; neither a paid plan nor an AI-enabled interface alone proves the training choice.

Source: Figma content-training controls by plan. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Our paid Figma account automatically excludes all content from AI training.

Buyer evidence still required

  • A dated admin view of the applicable content-training setting
  • The plan and team or organization to which that setting applies
  • Clarification of historical-content treatment if the review requires it

Suggested review condition: Require configuration evidence before making a customer-specific no-training claim; do not infer retroactive removal from a prospective setting.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck plan defaults, organization scope and the effect of later setting changes.

Optional saved evidence: Preserve the configuration questions behind a design-data procurement decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Figma MCP: Design extraction and canvas changes

Question: Can an agent treat a design connector as read-only when it can also capture UI and write to canvas?

Figma's remote MCP documents both design-context retrieval and canvas-changing workflows. OAuth sign-in and an eligible client are required; capabilities and file actions depend on the tool and access rights. Capturing an application UI sends information into Figma, while retrieving a design supplies context to the client. Those are different data-transfer decisions.

Source: Figma hosted MCP authorization and data flow. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Figma's official remote MCP; desktop-server behavior and third-party Figma connectors are outside this profile.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Figma hosts the remote MCP endpoint.

Documented by publisher. Figma hosted MCP authorization and data flow

Purpose

Move between design context, implementation workflows and editable canvas content.

Documented by publisher. Figma hosted MCP authorization and data flow

Read capability

Tools retrieve design context, screenshots, assets and component mappings.

Documented by publisher. Figma MCP read and write tools

Write capability

Canvas workflows create or change content; generating into an existing file requires edit permission.

Documented by publisher. Figma hosted MCP authorization and data flow; Figma MCP read and write tools

Authentication

OAuth sign-in is documented, and clients must be listed in Figma's MCP catalog.

Documented by publisher. Figma hosted MCP authorization and data flow

Permission surface

Seat, plan, file rights and selected tool affect supported actions; read and write tools are listed separately.

Documented by publisher. Figma MCP read and write tools

Data leaving the environment

Design context travels to the client; UI capture can send application content into Figma.

Review inference. Figma hosted MCP authorization and data flow

Failure modes to consider

Uploading confidential screens, modifying the wrong file, or assuming a design integration is read-only.

Review inference. Figma hosted MCP authorization and data flow; Figma MCP read and write tools

Unknowns and applicability

Actual file access, client eligibility, capture content, plan allowances and model data handling.

Not established

Suggested refusal or clarification condition

For design inspection, withhold canvas writes and UI uploads unless their content and destination are authorized.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck eligible client, file rights and new canvas or capture tools before changing the workflow.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the data-direction and file-change boundaries reviewed before a design-to-code workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Firebase MCP: CLI identity, core tools and remote requests

Question: Does limiting Firebase MCP feature groups remove every other capability?

No. Firebase says core tools remain available when feature groups are selected. The local server inherits Firebase CLI credentials, and some tools proxy requests to remote services. Review identity, project context and the complete exposed tool list rather than assuming local execution or a feature filter is complete isolation.

Source: Firebase MCP inherited identity, remote requests and feature groups. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Local stdio server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Google publishes the Firebase local MCP server.

Documented by publisher. Firebase MCP inherited identity, remote requests and feature groups

Purpose

Work with Firebase projects, application data and development context.

Documented by publisher. Firebase MCP inherited identity, remote requests and feature groups

Read capability

Reads project data, schemas and security-rule context.

Documented by publisher. Firebase MCP inherited identity, remote requests and feature groups

Write capability

Can manage projects and users, work with data and send cloud messages.

Documented by publisher. Firebase MCP inherited identity, remote requests and feature groups

Authentication

Uses the same logged-in user or Application Default Credentials as the Firebase CLI.

Documented by publisher. Firebase MCP inherited identity, remote requests and feature groups

Permission surface

Feature-group selection retains core tools; identity and project context still matter.

Documented by publisher. Firebase MCP inherited identity, remote requests and feature groups

Data leaving the environment

Some local tools call remote backends; results can enter the AI client.

Review inference. Firebase MCP inherited identity, remote requests and feature groups

Failure modes to consider

The wrong project context or broad inherited identity can misdirect an action.

Review inference. Firebase MCP inherited identity, remote requests and feature groups

Unknowns and applicability

Buyer credentials, core-tool configuration and cloud permissions are unverified.

Not established

Suggested refusal or clarification condition

Check identity and complete tool exposure before approving cloud changes.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck CLI identity, project context and core-tool changes.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the inherited-identity and feature-filter boundaries for a Firebase agent review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Firecrawl MCP: Endpoint mode, browser state and interaction

Question: Does a Firecrawl search connection also allow browser interactions or saved login state?

Firecrawl documents different hosted tool sets. Its full interface includes interaction tools that can click, type and preserve browser state, while a dedicated search-only endpoint has a restricted tool set. Review the actual endpoint and exposed tools before treating a connection as retrieval only.

Source: Firecrawl official MCP capabilities and hosted modes. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official server; hosted full, keyless and search-only modes

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Firecrawl publishes the official MCP server and hosted endpoints.

Documented by publisher. Firecrawl official MCP capabilities and hosted modes

Purpose

Retrieve web content and, with applicable tools, interact with pages.

Documented by publisher. Firecrawl official MCP capabilities and hosted modes

Read capability

Search results, scraped content and supported parsed documents.

Documented by publisher. Firecrawl official MCP capabilities and hosted modes

Write capability

Interaction tools can act on pages and save browser profile state.

Documented by publisher. Firecrawl official MCP capabilities and hosted modes

Authentication

Hosted keyless access is distinct from API-key configured server access.

Documented by publisher. Firecrawl official MCP capabilities and hosted modes

Permission surface

Endpoint mode changes the available tool set.

Documented by publisher. Firecrawl official MCP capabilities and hosted modes

Data leaving the environment

Review page inputs, browser profile data and returned content recipients.

Review inference. Firecrawl official MCP capabilities and hosted modes

Failure modes to consider

A full tool set or saved login can exceed a search-only task.

Review inference. Firecrawl official MCP capabilities and hosted modes

Unknowns and applicability

Effective endpoint configuration, profile contents and account usage controls are unverified.

Not established

Suggested refusal or clarification condition

Require action authorization before using interaction tools or saving authenticated state.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck endpoint tools, authentication, browser profiles and credit consumption.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve which endpoint and browser-state boundary supported a retrieval-only decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Fivetran Agent Context: Warehouse query identity

Question: Does Fivetran Agent Context query with each user's warehouse permissions?

This hosted public-preview interface exposes context-layer SQL reads and feedback submission. Setup selects a warehouse query role or credential; it is not evidence of per-user warehouse impersonation. Dedicated read-only options differ by warehouse, and the reviewed setup says role-based query access is not yet supported for Databricks.

Source: Fivetran Agent Context MCP. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; deployed buyer configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Fivetran operates the Agent Context endpoint.

Documented by publisher. Fivetran Agent Context MCP; Fivetran Agent Context MCP setup

Purpose

Query a configured business context layer.

Documented by publisher. Fivetran Agent Context MCP; Fivetran Agent Context MCP setup

Read capability

Read-only SQL against the connected destination.

Documented by publisher. Fivetran Agent Context MCP; Fivetran Agent Context MCP setup

Write capability

A separate tool submits response feedback.

Documented by publisher. Fivetran Agent Context MCP; Fivetran Agent Context MCP setup

Authentication

Authorized user connection or system key for automated use.

Documented by publisher. Fivetran Agent Context MCP; Fivetran Agent Context MCP setup

Permission surface

Context access and the configured warehouse query identity both matter.

Documented by publisher. Fivetran Agent Context MCP; Fivetran Agent Context MCP setup

Data leaving the environment

Business definitions and query results reach the client.

Review inference. Fivetran Agent Context MCP; Fivetran Agent Context MCP setup

Failure modes to consider

Assuming user-level warehouse isolation can misstate the data boundary.

Review inference. Fivetran Agent Context MCP; Fivetran Agent Context MCP setup

Unknowns and applicability

Actual grants, selected schemas and warehouse-specific support are unverified.

Not established

Suggested refusal or clarification condition

Require the query identity and allowed datasets before disclosing results.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Preview capabilities, warehouse-specific role support and schema grants.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the warehouse identity and feature-support boundary behind a procurement decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Fivetran management MCP: Scope and approval enforcement

Question: Does a Fivetran MCP confirmation warning enforce approval?

The publisher repository separates read, write and delete tool scopes and supports explicit action exclusions. Its confirmation wording is advisory, not a server-enforced approval step. Credential-related endpoints also need review. The documented HTTP OAuth resource-server mode is unfinished; it must not be represented as verified token authentication.

Source: Fivetran management MCP repository. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; deployed buyer configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Fivetran publishes the server; the buyer runs it.

Documented by publisher. Fivetran management MCP repository

Purpose

Discover and invoke Fivetran management API operations.

Documented by publisher. Fivetran management MCP repository

Read capability

Connection status, configuration and allowed API reads.

Documented by publisher. Fivetran management MCP repository

Write capability

Raised scopes expose write and deletion operations.

Documented by publisher. Fivetran management MCP repository

Authentication

Fivetran API key and secret; HTTP transport has separate documented limitations.

Documented by publisher. Fivetran management MCP repository

Permission surface

Server scope and action denylist constrain the underlying credential.

Documented by publisher. Fivetran management MCP repository

Data leaving the environment

Management responses pass to the agent through the selected deployment.

Review inference. Fivetran management MCP repository

Failure modes to consider

Client warnings can be ignored; an incomplete authentication mode cannot establish access control.

Review inference. Fivetran management MCP repository

Unknowns and applicability

Installed revision, effective denylist and credential privileges are untested.

Not established

Suggested refusal or clarification condition

Require enforced authority and a supported authentication mode before management changes.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. HTTP authentication implementation, credential endpoints and scope filtering.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the source version that distinguishes advisory approval language from enforced control.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

FOCUS allocation method and measured factors

Question: Does a FOCUS AllocatedMethodId establish how a shared AI bill was divided?

FOCUS 1.4 requires an AllocatedMethodId for generator-calculated splits and documentation identifying that method. AllocatedMethodDetails should be present for these charges and, when present, describes factors and ratios; ratios across allocated charges must total one. The identifier alone does not expose measured factors or demonstrate correct application.

Source: FOCUS 1.4 — Allocated Method ID. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does a FOCUS AllocatedMethodId establish how a shared AI bill was divided?

Buyer evidence still required

  • Method ID and provider documentation
  • Complete allocated ratios and factor quantities
  • Origin charge and recipient charges

Review inference: Request the calculation basis before accepting a shared-service chargeback. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not infer reproducible allocation from an identifier without calculation evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual factors and implementation were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual factors and implementation were not observed.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS applied contract commitments

Question: Does a ContractApplied entry establish that an entire commitment has been fulfilled?

FOCUS 1.4 associates a charge with one or more commitments and reports applied cost or quantity and unit. Commitment IDs are unique within the provider and have one parent contract; applied cost uses BillingCurrency. A charge association supplies a progress input, not a complete balance or proof of fulfilment across every relevant charge and interval.

Source: FOCUS 1.4 — Contract Applied. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does a ContractApplied entry establish that an entire commitment has been fulfilled?

Buyer evidence still required

  • Provider-scoped contract and commitment IDs
  • Applied amounts and units across charges
  • Contract terms, interval and complete balance

Review inference: Reconcile charge contributions before claiming a contractual minimum is satisfied. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not treat one applied charge as complete fulfilment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Complete progress and commercial terms are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Complete progress and commercial terms are unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS commitment eligibility versus availability

Question: Does FOCUS CommitmentProgramEligibilityDetails prove a commitment can be bought or applied now?

FOCUS 1.4 lists programs that could potentially cover a charge whether or not a commitment was applied. The field must not reflect temporary purchase restrictions such as account configuration or quotas, and excludes commitment periods and payment options. It identifies an eligible pool, not current availability, approved terms or achieved coverage.

Source: FOCUS 1.4 — Commitment Program Eligibility Details. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does FOCUS CommitmentProgramEligibilityDetails prove a commitment can be bought or applied now?

Buyer evidence still required

  • Program eligibility and applied commitment
  • Current account restrictions and purchase options
  • Approved term, budget and authority

Review inference: Separate an optimisation candidate from an authorised, available purchase. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not use eligibility metadata as purchase approval or availability proof.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Current restrictions, negotiated options and authority are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Current restrictions, negotiated options and authority are unknown.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS commitment quantity and coverage units

Question: Can I compare FOCUS CommitmentDiscountQuantity directly with raw GPU hours or token counts?

FOCUS 1.4 expresses CommitmentDiscountQuantity in CommitmentDiscountUnit, depending on the provider commitment category and flexibility rules. It can differ from consumption and pricing quantities. Purchase quantities and Used or Unused usage quantities describe different sides of coverage. Mixing raw workload units or both sides without reconciliation need not measure commitment utilisation.

Source: FOCUS 1.4 — Commitment Discount Quantity. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can I compare FOCUS CommitmentDiscountQuantity directly with raw GPU hours or token counts?

Buyer evidence still required

  • Commitment category, unit and conversion
  • Purchase and Used or Unused usage quantities
  • Workload quantities and reporting interval

Review inference: Choose a consistent commitment-unit denominator before reporting utilisation. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not label a mixed-unit or double-counted ratio as commitment utilisation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Physical GPU activity and workload efficiency are not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Physical GPU activity and workload efficiency are not established.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS commitment savings without double counting

Question: Can I sum every FOCUS ListCost and ContractedCost row to calculate commitment savings?

FOCUS 1.4 warns that commitment-covered costs require excluding either covering Purchase rows or covered Usage rows when aggregating ListCost and ContractedCost, depending on cash or accrual purpose. Including both can count the same coverage twice. These price baselines require their applicable unit and quantity rules; their difference is not independently verified realised savings.

Source: FOCUS 1.4 — List Cost. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can I sum every FOCUS ListCost and ContractedCost row to calculate commitment savings?

Buyer evidence still required

  • Covering and covered charge identities
  • Accounting basis and aggregation filters
  • List, contracted and invoiced prices with quantities

Review inference: Avoid overstating savings when purchase and consumption are represented together. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not publish savings from totals including both sides of the same coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual savings and the counterfactual purchase price remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual savings and the counterfactual purchase price remain unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS commitment status and replacement

Question: Can a proposed or superseded FOCUS commitment be treated as currently available coverage?

FOCUS 1.4 separates Proposed, Pending, Active, Exhausted, Expired, Canceled and Superseded states. Proposed has no current financial impact, Pending begins later, and Exhausted has no remaining value despite being in effect. A modification requiring a new ID makes the previous record Superseded. Current coverage needs applicable dates, state and version lineage.

Source: FOCUS 1.4 — Contract Commitment Lifecycle Status. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can a proposed or superseded FOCUS commitment be treated as currently available coverage?

Buyer evidence still required

  • Commitment state and effective period
  • Old and replacement IDs
  • Remaining value and charge application

Review inference: Reject stale, proposed or exhausted coverage in current cost decisions. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not count proposed, superseded or exhausted value as available coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual remaining balance and signed terms are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual remaining balance and signed terms are unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS completeness flags and coverage

Question: Does FOCUS DatasetInstanceComplete or TimeSectorComplete prove every expected charge is present?

FOCUS 1.4 describes these flags as the generator assessment under its documented definition of completeness. DatasetInstanceComplete applies to non-time-series instances; TimeSectorComplete applies to time sectors. A true flag does not independently reconcile expected workloads, excluded accounts or late charges. The declared scope must be compared with the scope the buyer actually needs.

Source: FOCUS 1.4 — Dataset Instance Complete. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does FOCUS DatasetInstanceComplete or TimeSectorComplete prove every expected charge is present?

Buyer evidence still required

  • Generator completeness definition
  • Dataset or sector scope with expected accounts and periods
  • Independent expected workload and charge inventory

Review inference: Check the scope of a completeness assertion before closing a review. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not equate a provider flag with an independently complete buyer evidence set.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual coverage and missing charges have not been checked.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual coverage and missing charges have not been checked.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS continuous commitment intervals

Question: Can later usage recover unused coverage from an earlier FOCUS Continuous commitment interval?

FOCUS 1.4 describes Continuous commitments as fixed coverage per fulfilment interval without unused benefits carrying forward. Discontinuous commitments use an aggregate window; Full Period must be Discontinuous. Annual usage alone cannot establish utilisation of an hourly Continuous commitment. The model and interval must match the calculation.

Source: FOCUS 1.4 — Contract Commitment Model. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can later usage recover unused coverage from an earlier FOCUS Continuous commitment interval?

Buyer evidence still required

  • Commitment model and interval
  • Usage and coverage per interval
  • Contract term and application rules

Review inference: Avoid masking interval waste with long-period aggregation. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not offset an unused Continuous interval with later consumption as carried coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual interval utilisation has not been measured.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual interval utilisation has not been measured.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS corrective invoice lineage

Question: How does FOCUS distinguish a corrective invoice from a self-contained invoice?

FOCUS 1.4 requires ReferenceInvoiceId to point to the original InvoiceId when the current invoice adjusts another, and to the current InvoiceId otherwise. This supplies adjustment lineage rather than proof of refund or payment. Reconcile the referenced document, issuer and affected charges before closing a correction.

Source: FOCUS 1.4 — Reference Invoice ID. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: How does FOCUS distinguish a corrective invoice from a self-contained invoice?

Buyer evidence still required

  • Current and referenced invoice identities
  • Issuer documents and adjusted charges
  • Payment evidence if financial movement is claimed

Review inference: Trace an adjustment to the obligation it changes. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not infer cash movement from a corrective reference alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Referenced documents and transfers have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Referenced documents and transfers have not been inspected.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS currency conversion at different grains

Question: Does zero PaymentCurrencyBilledCost on a FOCUS line mean nothing is payable for that line?

FOCUS 1.4 permits payment-currency amounts in a separate aggregate record. A granular line can have non-zero BilledCost and zero PaymentCurrencyBilledCost, while the aggregate has the opposite pattern. The documented PaymentCurrencyInvoiceDetailId relationship links the grains. Reconcile the group and currency basis before interpreting a zero line amount as no obligation.

Source: FOCUS 1.4 — Payment Currency Billed Cost. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does zero PaymentCurrencyBilledCost on a FOCUS line mean nothing is payable for that line?

Buyer evidence still required

  • Granular and aggregate invoice records
  • Payment-currency detail references and currencies
  • Issuer conversion basis and aggregate payable amount

Review inference: Follow conversion grouping before reconciling payment-currency amounts. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not infer no obligation or duplicate billing from cross-grain zero patterns.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual conversion and settlement remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual conversion and settlement remain unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS delta corrections and aggregation

Question: Does the latest FOCUS Delta artifact contain the complete corrected bill?

FOCUS 1.4 Delta corrections append additive changes while preserving earlier artifacts. A complete view requires all artifacts for the delivery scope. Net changes adjust totals without necessarily reversing the original record explicitly, providing less inherent change detail than Ledger corrections. A latest-delta-only calculation can omit the original amount and previous adjustments.

Source: FOCUS 1.4 — Correction Handling. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does the latest FOCUS Delta artifact contain the complete corrected bill?

Buyer evidence still required

  • Original scope artifacts
  • All delta deliveries and sequence evidence
  • Aggregation and correction-style documentation

Review inference: Retain the full delta chain before accepting a corrected aggregate. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not treat the latest delta as a complete snapshot or reconstructed change history.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Completeness of the buyer delivery chain is unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Completeness of the buyer delivery chain is unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS hybrid delivery mechanisms

Question: Can one FOCUS import use the same append rule for open and closed billing periods?

FOCUS 1.4 permits hybrid Overwrite and Append delivery with documented conditions for each mechanism. An implementation may overwrite open-period snapshots and append closed-period corrections. Artifacts must be interpreted within their delivery scope and mode; treating every file as additive or every file as replacement can respectively duplicate or lose charges.

Source: FOCUS 1.4 — Delivery Handling. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can one FOCUS import use the same append rule for open and closed billing periods?

Buyer evidence still required

  • Delivery documentation and switching conditions
  • Artifact scope and period state
  • Import state and retained earlier deliveries

Review inference: Apply the declared import mechanism to each delivery scope. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not apply one global mode when delivery mechanisms are conditional.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual provider delivery and importer behavior have not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual provider delivery and importer behavior have not been tested.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS invoice line identity and grain

Question: Can FOCUS invoice lines be reconciled by SKU alone across an invoice?

FOCUS 1.4 allows InvoiceDetailGrain to vary between records within one invoice. It must include every property defining line granularity, including custom properties without a standard equivalent. InvoiceDetailId identifies a record within its InvoiceId. A fixed SKU-only join can merge distinct lines or multiply charges when the actual grain differs.

Source: FOCUS 1.4 — Invoice Detail Grain. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can FOCUS invoice lines be reconciled by SKU alone across an invoice?

Buyer evidence still required

  • Issuer, invoice and detail identifiers
  • Complete per-line grain properties
  • Usage mappings to each invoice line

Review inference: Use declared line grain and invoice-scoped identity for reconciliation. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not assume a global SKU grain or globally unique detail IDs.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer invoice joins have not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Buyer invoice joins have not been tested.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS invoiced and amortised cost

Question: Must FOCUS BilledCost and EffectiveCost totals match within every billing month?

FOCUS 1.4 assigns BilledCost to invoiced charges in the billing period and EffectiveCost to recognised resource, service or commitment cost in the charge period. Their billing-period totals can differ when a covering purchase and its usage cross periods, accounts or datasets. The specified equality applies across related covering and covered charges over the covering charge period when both sides are present.

Source: FOCUS 1.4 — Billed Cost. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Must FOCUS BilledCost and EffectiveCost totals match within every billing month?

Buyer evidence still required

  • Billing and charge periods with currencies
  • Covering purchase and covered usage records across relevant accounts
  • Issuer invoice and the chosen cash or accrual reporting basis

Review inference: Select the cost basis before investigating an apparent monthly invoice discrepancy. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not flag missing money solely because monthly BilledCost and EffectiveCost differ.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer commitment or invoice reconciliation was inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No buyer commitment or invoice reconciliation was inspected.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS issued invoice reopening

Question: May a FOCUS invoice silently return from Issued to Open during a correction?

FOCUS 1.4 prohibits Issued-to-Open status transitions unless the customer explicitly requests or approves them. Corrections not affecting invoice reconciliation may occur regardless of status, yet can affect allocation and traceability. Consumers need the transition, approval and correction context rather than assuming issued data never changes.

Source: FOCUS 1.4 — Invoice Issue Status. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: May a FOCUS invoice silently return from Issued to Open during a correction?

Buyer evidence still required

  • Previous and current status
  • Customer request or approval
  • Changed records and reconciliation impact

Review inference: Distinguish authorised reopening from an unexplained state regression. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not accept an Issued-to-Open transition as authorised without customer evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Approval and actual correction behavior were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Approval and actual correction behavior were not observed.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS ledger correction reconstruction

Question: How should I distinguish a FOCUS Ledger reversal from a second charge?

FOCUS 1.4 Ledger corrections append explicit reversals and re-entries as applicable: a reversal changes additive metric signs while other columns match the original, and a corrected record can follow. All artifacts remain relevant to the scope aggregate. Negative and positive rows need their correction context; their presence alone does not establish duplicate billing or a cash refund.

Source: FOCUS 1.4 — Correction Handling. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: How should I distinguish a FOCUS Ledger reversal from a second charge?

Buyer evidence still required

  • Original, reversal and corrected entries
  • Additive metrics and matching dimensions
  • Delivery scope, order and correction policy

Review inference: Reconstruct corrected charges without confusing reversals with new transactions. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not infer duplicate billing or refunded cash from a ledger sign pattern alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Financial transfers and the complete buyer ledger are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Financial transfers and the complete buyer ledger are unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS metadata versus charge freshness

Question: Does a recent FOCUS RecencyLastUpdated timestamp mean the underlying cost data is recent?

FOCUS 1.4 distinguishes when the recency metadata object was updated from when dataset-instance or time-sector data was updated. RecencyLastUpdated alone cannot establish charge freshness for the period being assessed. Inspect DatasetInstanceLastUpdated and the relevant TimeSectorLastUpdated alongside completeness and delivery scope.

Source: FOCUS 1.4 — Recency Last Updated. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does a recent FOCUS RecencyLastUpdated timestamp mean the underlying cost data is recent?

Buyer evidence still required

  • Recency metadata timestamp
  • Dataset and relevant sector update timestamps
  • Required observation cutoff and delivery scope

Review inference: Measure charge freshness rather than metadata-wrapper freshness. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not label charges current using only the metadata-object update time.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer feed freshness has not been measured.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer feed freshness has not been measured.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS native data exclusions

Question: Does a FOCUS 1.4 export automatically preserve every native billing field?

FOCUS 1.4 requires custom columns for native fields not represented by standard columns, except publicly documented justified exclusions unrelated to invoice reconciliation. Reconciliation-required fields cannot use that exclusion. Included custom values must retain fidelity and summable totals. Providers may require explicit column selection, so a delivered export still needs its configuration and exclusions checked.

Source: FOCUS 1.4 — Dataset Completeness. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does a FOCUS 1.4 export automatically preserve every native billing field?

Buyer evidence still required

  • Native schema and FOCUS mapping
  • Documented exclusions and custom-column definitions
  • Export configuration and delivered columns

Review inference: Determine whether a portable export retains reconciliation fields. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not claim export completeness solely from a FOCUS label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer export conformance and field coverage remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Buyer export conformance and field coverage remain unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS non-originator zero-cost rows

Question: Does a zero FOCUS BilledCost or EffectiveCost row establish that a service was free?

FOCUS 1.4 requires BilledCost to be zero for records generated by an entity that does not invoice the charge, and EffectiveCost to be zero for records generated by an entity that did not originate it. These rules prevent duplicate cost across datasets. Covered usage can also have zero BilledCost. Zero in one dataset therefore does not establish that no charge exists elsewhere.

Source: FOCUS 1.4 — Billed Cost. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does a zero FOCUS BilledCost or EffectiveCost row establish that a service was free?

Buyer evidence still required

  • Data generator and invoice issuer identities
  • Related originator and invoicing datasets
  • Commitment coverage and complete charge lineage

Review inference: Find the authoritative charging dataset before treating an agent service as free. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not infer free service from a zero-cost intermediary or covered-usage row.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Related invoicing data has not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Related invoicing data has not been inspected.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS null consumption and unused commitments

Question: Does a null FOCUS ConsumedQuantity mean the record has no usage-related cost?

FOCUS 1.4 requires ConsumedQuantity to be null for non-Usage categories, unused commitment Usage charges and records with null SkuPriceId. Correction records can also have null consumption under the stated conditions. Null has a defined applicability meaning; treating it as measured zero can hide unused commitment cost or distort a usage denominator.

Source: FOCUS 1.4 — Consumed Quantity. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does a null FOCUS ConsumedQuantity mean the record has no usage-related cost?

Buyer evidence still required

  • Charge category and correction class
  • SKU identity and commitment status
  • Cost fields and consumption applicability

Review inference: Keep unavailable or inapplicable consumption separate from measured zero. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not convert missing consumption to zero without checking the null conditions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Missing measurement and true zero have not been distinguished in buyer data.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Missing measurement and true zero have not been distinguished in buyer data.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS origin tags versus allocated tags

Question: Can origin resource tags alone identify the team charged by a FOCUS cost split?

FOCUS 1.4 separates AllocatedTags for allocated charges from resource tags already present in Tags. AllocatedTags must not repeat those resource tags and may be null even for a split charge. The originating resource owner and allocated recipient need not be interchangeable; absence of allocation tags does not prove the origin owner accepted that share.

Source: FOCUS 1.4 — Allocated Tags. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can origin resource tags alone identify the team charged by a FOCUS cost split?

Buyer evidence still required

  • Origin resource tags
  • Allocated resource identity and allocated tags
  • Approved recipient mapping and allocation method

Review inference: Avoid assigning shared-service costs to the wrong organisational owner. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not infer a recipient or business approval solely from original resource tags.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer ownership and approval mappings are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Buyer ownership and approval mappings are unknown.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS pricing quantity versus consumption

Question: Can I multiply FOCUS ConsumedQuantity by a unit price instead of PricingQuantity?

FOCUS 1.4 distinguishes metered ConsumedQuantity in ConsumedUnit from PricingQuantity in PricingUnit. Their granularity or interval may differ. PricingQuantity is used with the applicable SKU unit price to produce ListCost or ContractedCost when the required values are present. Substituting consumption without its documented conversion can produce an invalid charge estimate.

Source: FOCUS 1.4 — Pricing Quantity. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can I multiply FOCUS ConsumedQuantity by a unit price instead of PricingQuantity?

Buyer evidence still required

  • Consumed and pricing quantities with both units
  • Applicable SKU price and interval
  • Supplier conversion or aggregation method

Review inference: Reconcile metered usage to the supplier pricing unit before estimating cost. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not multiply quantities and rates expressed in incompatible units.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The supplier meter and conversion have not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The supplier meter and conversion have not been tested.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS pricing, billing and payment currencies

Question: Can FOCUS pricing currency, billing currency and payment currency be treated as one monetary unit?

FOCUS 1.4 permits PricingCurrency to be national or virtual, while PaymentCurrency is the national currency in which settlement is made or expected. PricingCurrencyEffectiveCost is the pricing-denominated equivalent of EffectiveCost with the same recognition basis. These denominations and roles require documented conversion; amounts cannot simply be added as one unit.

Source: FOCUS 1.4 — Pricing Currency. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Can FOCUS pricing currency, billing currency and payment currency be treated as one monetary unit?

Buyer evidence still required

  • Pricing, billing and payment currency identifiers
  • Cost amounts and conversion evidence
  • Recognition periods and invoice totals

Review inference: Keep pricing credits, billed money and payment obligations on explicit bases. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not aggregate credits and national-currency amounts without conversion evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Conversion rates, bank fees and settlement are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Conversion rates, bank fees and settlement are unknown.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS provisional invoice identifiers

Question: Does an InvoiceId in FOCUS prove the supplier has issued the invoice?

FOCUS 1.4 permits InvoiceId and InvoiceDetailId to be generated for provisional invoices before issuance. Their presence identifies an association, not final publication or payment. Check InvoiceIssueStatus and the issuer document before treating an identifier as a final obligation; a provisional identifier can accompany preliminary data.

Source: FOCUS 1.4 — Invoice ID. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does an InvoiceId in FOCUS prove the supplier has issued the invoice?

Buyer evidence still required

  • Invoice and detail identifiers with issuer
  • Current issue status and issuer document
  • Billing account and period

Review inference: Avoid treating a pre-generated reference as a final invoice. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not use an identifier alone as issuance or payment evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual invoice publication and payment state are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual invoice publication and payment state are unknown.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS replacement corrections

Question: Should I append a corrected FOCUS Replacement snapshot to the previous export?

FOCUS 1.4 Replacement corrections use a complete snapshot superseding earlier artifacts for the same delivery scope. Adding both can double count unchanged records. Because changes are not separate entries, the latest snapshot alone does not preserve correction history; versioned artifacts need separate retention when that history is required.

Source: FOCUS 1.4 — Correction Handling. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Should I append a corrected FOCUS Replacement snapshot to the previous export?

Buyer evidence still required

  • Delivery scope and correction style
  • Ordered artifact versions and hashes
  • Separate audit-retention requirements

Review inference: Choose replacement rather than accumulation for a corrected snapshot. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not sum old and replacement snapshots for the same scope as independent charges.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer import and audit-retention behavior is unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Buyer import and audit-retention behavior is unknown.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS reserved capacity and physical use

Question: Does FOCUS CapacityReservationStatus Used prove the reserved GPU was busy?

FOCUS 1.4 uses CapacityReservationStatus to describe whether a charge consumes the identified reservation or represents its unused portion. This is a charge-allocation status. It does not supply GPU occupancy, useful work or successful inference measurements; those require workload and hardware evidence correlated to the same resource and interval.

Source: FOCUS 1.4 — Capacity Reservation Status. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does FOCUS CapacityReservationStatus Used prove the reserved GPU was busy?

Buyer evidence still required

  • Reservation ID and charge status
  • Resource-bound hardware and workload measurements
  • Aligned intervals and successful-work outcomes

Review inference: Distinguish reservation consumption from useful machine activity. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not report physical utilisation or task success from reservation Used status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No hardware utilisation or agent outcome was measured.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No hardware utilisation or agent outcome was measured.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS seller, host and invoice issuer roles

Question: Does FOCUS ServiceProviderName identify both the cloud host and the invoice issuer?

FOCUS 1.4 distinguishes service provider, underlying host and invoice issuer. Marketplace services identify the seller; white-label reseller services identify the reseller. HostProviderName can default to ServiceProviderName when the underlying host is not exposed or selected. Reporting names do not independently authenticate a merchant or prove the physical host.

Source: FOCUS 1.4 — Service Provider Name. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does FOCUS ServiceProviderName identify both the cloud host and the invoice issuer?

Buyer evidence still required

  • The three provider-role fields
  • Marketplace or reseller terms and issuer document
  • Independent supplier and hosting evidence if needed

Review inference: Identify which party supplies, hosts and invoices a service. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not infer infrastructure ownership or recipient identity from reporting names alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual identity and hosting remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual identity and hosting remain unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS spend versus usage commitments

Question: Does a missing FOCUS ContractCommitmentCost mean the commitment has no value?

FOCUS 1.4 requires ContractCommitmentCost for Spend but permits null for Usage. ContractCommitmentQuantity is required for Usage and may be null for Spend. Quantity uses the provider commitment unit, while cost uses BillingCurrency. Missing cost can indicate a quantity-based obligation rather than zero value.

Source: FOCUS 1.4 — Contract Commitment Cost. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does a missing FOCUS ContractCommitmentCost mean the commitment has no value?

Buyer evidence still required

  • Commitment category and amount
  • Currency or provider commitment unit
  • Signed terms and applied progress

Review inference: Select the applicable monetary or usage progress measure. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not convert inapplicable cost or quantity to zero.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Monetary valuation of buyer usage commitments is unestablished.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Monetary valuation of buyer usage commitments is unestablished.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

FOCUS split charge conservation

Question: What must remain consistent when a FOCUS origin charge is split across teams?

FOCUS 1.4 requires summable costs and quantities across allocated charges to reproduce the origin charge, while dimensions and non-summable metrics such as unit prices retain origin values when present. A split redistributes a charge rather than creating cost. Arithmetic conservation supports consistency review but does not establish fair allocation or correct metering.

Source: FOCUS 1.4 — Data Generator-Calculated Split Cost Allocation Handling. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: What must remain consistent when a FOCUS origin charge is split across teams?

Buyer evidence still required

  • Origin charge and all allocated children
  • Summable and non-summable column definitions
  • Allocation method and recipient mapping

Review inference: Check whether a cost-allocation transformation conserves the original charge. This is a proposed evidence review, not an observed billing reconciliation.

Suggested review condition: Do not accept an allocation that creates or loses cost without an explained adjustment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Underlying metering and allocation fairness remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Underlying metering and allocation fairness remain unverified.
  • FOCUS conformity, invoice correctness, physical utilisation, actual payment or business outcome has not been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

use boundary record

Forge Authorised-Use Boundary

Question: What is Forge authorised to support?

Public-safe record for Forge authorised-use and operator-control boundaries.

Claim boundaries
  • permission to test third-party systems
  • guaranteed vulnerability discovery
  • autonomous exploitation
  • unscoped internet scanning
  • security certification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

External documentation review

Foundry classic function requests and submitted results

Question: Does a Foundry classic run in requires_action state prove its requested external function has executed?

The reviewed Foundry classic function-calling guide uses requires_action to request application-side function execution. The application performs the work and submits output associated with the tool_call_id; the run can then continue. A requested call or application-submitted output is not independent verification of the external action.

Source: Use Foundry Agent Service with function calling (classic) - Microsoft Foundry (classic) portal | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Foundry classic run in requires_action state prove its requested external function has executed?

Buyer evidence still required

  • Classic API/run and tool_call_id
  • Application execution and external result evidence
  • Submitted output and subsequent run status

Review inference: Correlate the request, actual application execution and submitted output before treating the run as completed business work.

Suggested review condition: Refuse completed-action claims from requires_action or submitted text alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the application performed the requested work is not independently observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Separate model requests from execution evidence at enterprise handover.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Live external-action verification by INDEX
  • Whether the application performed the requested work is not independently observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Foundry: Stateful agent data needs explicit deletion

Question: Does ending a Foundry Agent Service run remove its stored agent data?

Foundry Agent Service retains state and uploaded data. Its FAQ says data persists until explicitly deleted through the API or SDK, including threads, files and vector stores. The documented no-training statement does not make the service stateless.

Source: Foundry Agent Service FAQ. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does ending a Foundry Agent Service run remove its stored agent data?

Buyer evidence still required

  • Agent setup and storage inventory.
  • Thread, file and vector-store identifiers.
  • Deletion results and subsequent scoped retrieval checks.

Suggested review condition: Do not close the exit review from a completed run or no-training statement without object-level deletion evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Agent setup and storage inventory. Thread, file and vector-store identifiers. Deletion results and subsequent scoped retrieval checks.

Optional saved evidence: An AI platform owner must inventory persistent objects before closing an agent data-exit request.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual deletion of customer objects, backups or separately connected tools
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Front MCP: Drafting and sending are separate permissions

Question: Can I connect a Front drafting assistant without allowing it to send?

Front distinguishes read, write and send permissions. Draft creation does not send a message; sending requires the separate send capability and the authorizing teammate's access. Its custom connection requires a confidential OAuth client, and permission changes require reauthorization.

Source: Front MCP Server. Documentation checked 2026-10-17; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer installation and runtime untested

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Front operates its conversation MCP endpoint.

Documented by publisher. Front MCP Server

Purpose

Assist with shared-inbox research and conversation work.

Documented by publisher. Front MCP Server

Read capability

Conversation content available to the authorizing teammate.

Documented by publisher. Front MCP Server

Write capability

Drafts, comments, assignments and other permitted changes; sending is separate.

Documented by publisher. Front MCP Server

Authentication

OAuth; custom clients need a client ID and secret, without dynamic client registration.

Documented by publisher. Front MCP Server

Permission surface

Requested resource permissions are bounded by the teammate's access.

Documented by publisher. Front MCP Server

Data leaving the environment

Conversation content can be returned to the selected AI client.

Review inference. Front MCP Server

Failure modes to consider

A write-capable assistant may alter workflow state without sending mail.

Review inference. Front MCP Server

Unknowns and applicability

Actual scopes and client confirmation behaviour remain untested.

Not established

Suggested refusal or clarification condition

Require explicit recipient and message authority before enabling send.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Teammate, inboxes, OAuth resource permissions, client and authorised outbound actions.

Record history: 2026-10-17 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the distinction between drafting, workflow writes and customer-facing sends.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

G5.2: Real-world performance boundary

Question: Does G5.2 synthetic confirmation establish real-world performance?

G5.2 supports a locked synthetic confirmation and regression posture. Its public source excludes real-world performance.

Derived from BDAS G5.2 — Locked Synthetic Confirmation. No new experiment or validation is claimed.

Claim boundaries
  • real-world performance
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Gatekeeper: Violation reporting and admission mode

Question: Does a Gatekeeper constraint violation prove that the corresponding request was blocked?

Gatekeeper supports deny, dryrun and warn enforcement actions. Dryrun records violations without enforcing denial; warn supplies warnings. A violation must be interpreted with its constraint enforcementAction and audit time rather than as proof of an admission rejection.

Source: Handling Constraint Violations | Gatekeeper. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a Gatekeeper constraint violation prove that the corresponding request was blocked?

Buyer evidence still required

  • Constraint revision and enforcementAction.
  • Admission response and request identity.
  • Audit timestamp and matching resource.

Suggested review condition: Do not report a request blocked from a dryrun or warn violation without an actual denial response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Constraint revision and enforcementAction. Admission response and request identity. Audit timestamp and matching resource.

Optional saved evidence: Avoid treating an agent policy observation as an executed control.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Cluster inspection, deployed webhook availability or current resource 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

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Gemini and Vault: Preservation has content-type boundaries

Question: Does a Vault hold or export cover every type of data in Gemini activity?

Google documents Vault support for Gemini app prompts and responses, but excludes attached media or Gems, generated media and Google Workspace with Gemini data from that Gemini coverage. Active Vault retention rules and holds take precedence over Gemini history or user settings for supported conversations. Neither a hold nor an export establishes coverage of the excluded data types.

Source: Google Vault: Supported services and data types. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Enterprise AI Data Custody & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Vault hold or export cover every type of data in Gemini activity?

Buyer evidence still required

  • The Workspace edition, Vault licensing and Gemini product used.
  • The prompts, responses, media, Gems and Workspace AI data in scope.
  • The effective hold or retention rules and export coverage by data type.

Suggested review condition: Refuse an all-Gemini preservation or export claim when excluded data types lack separate evidence; do not infer erasure from hidden history.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The Workspace edition, Vault licensing and Gemini product used. The prompts, responses, media, Gems and Workspace AI data in scope. The effective hold or retention rules and export coverage by data type.

Optional saved evidence: A records owner must map the AI content inventory to the actual preservation and export coverage before relying on an exit or hold process.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Gemini API: Data use depends on the applicable service terms

Question: Does a free Gemini API request always have the same data-use terms as an unbilled service?

The terms distinguish Paid and Unpaid Services, with billing-account and regional provisions affecting applicability. Paid-service prompts and responses are not used for product improvement under the reviewed terms, but limited abuse-prevention logging remains described. Verify the applicable category instead of equating no charge with a universal retention or training rule.

Source: Gemini API paid and unpaid data terms. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A zero-cost request establishes one universal training and retention policy.

Buyer evidence still required

  • Cloud project billing association and applicable service category.
  • Relevant regional terms and feature-specific provisions.
  • Contractual and configuration evidence for retention and data use.

Suggested review condition: Require the applicable terms and feature context before claiming no training or no retention.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Terms version, billing association, region and API feature

Optional saved evidence: Preserve the applicable service and feature distinctions without asserting legal clearance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Gemini explicit caching: Expiry and usage metadata have limited scope

Question: What do Gemini explicit cache expiry, deletion and usage metadata establish about retained context?

Google's GenerateContent explicit-caching guide provides TTL or expire_time controls, cache deletion and metadata retrieval. Cached content itself cannot be retrieved or viewed through cache listing/get operations; metadata includes identity, model, times and usage. Usage metadata reports token accounting. The data-retention guide treats explicit cache lifetime, separately uploaded files and abuse-monitoring data as different concerns.

Source: Context caching  |  Gemini Generate Content API (Legacy)  |  Google AI for Developers. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: What do Gemini explicit cache expiry, deletion and usage metadata establish about retained context?

Buyer evidence still required

  • API/feature version, cache name, model, expiry and source-content inventory.
  • Deletion response or expiry evidence and usage metadata.
  • Separate Files API, logging and downstream-copy retention evidence.

Review inference: Cache metadata or removal alone cannot establish exact input identity and erasure of every retained copy.

Suggested review condition: Refuse complete-context-erasure or exact-content claims from token counts or cache deletion alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer cache, source binding or provider-side erasure was independently observed.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck generateContent versus other API cache semantics, feature maturity and separate file/log controls.

Optional saved evidence: Identify residual resources before closing a data-retention or exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Retrieved cached contents, verified provider erasure or deletion of all uploaded and downstream files
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Gemini in Workspace: Auto-deletion follows inactivity

Question: Does Gemini in Workspace conversation auto-deletion run from the chat creation date?

Google defines inactivity by the time since messages were last added or edited. The administrator can choose an inactivity interval or indefinite retention; deletion normally follows within a day but can be delayed. These controls are separate from Gemini app history settings.

Source: Gemini in Workspace conversation history. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Gemini in Workspace conversation auto-deletion run from the chat creation date?

Buyer evidence still required

  • The effective organisation or group setting.
  • The last message addition or edit time.
  • Subsequent deletion evidence and processing delays.

Suggested review condition: Do not calculate deletion from creation time or apply Gemini app settings to Workspace conversations without verification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The effective organisation or group setting. The last message addition or edit time. Subsequent deletion evidence and processing delays.

Optional saved evidence: A Workspace administrator needs the correct clock and effective user policy before promising a deletion deadline.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed deletion time or override of separately applicable preservation requirements
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Gemini Notebook: Export scope excludes deleted chats

Question: Which Gemini Notebook artifacts does Workspace export preserve, and can it recover deleted chats?

Google lists chat history excluding deleted history, audio overviews, uploaded content and generated notes in Gemini Notebook data exports. The documented export is not a recovery mechanism for previously deleted chats.

Source: Google Workspace Gemini Notebook data export. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Which Gemini Notebook artifacts does Workspace export preserve, and can it recover deleted chats?

Buyer evidence still required

  • The Notebook accounts and requested export scope.
  • Expected chats, uploads, notes and audio artifacts.
  • The actual export inventory and unresolved omissions.

Suggested review condition: Do not describe a later export as complete historical recovery when required chats were already deleted.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The Notebook accounts and requested export scope. Expected chats, uploads, notes and audio artifacts. The actual export inventory and unresolved omissions.

Optional saved evidence: An enterprise exit owner must inventory notebook artifacts before destructive cleanup removes needed history.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual export completeness or recovery of undocumented artifact types
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

General authorisation still needs change notice

Question: Can an agent supplier add a subprocessor under general authorisation without a change-notice opportunity?

UK Article 28(2) requires prior specific or general written controller authorisation for another processor. Under general authorisation, intended additions or replacements must be notified to give the controller an opportunity to object. Review implication: A public subprocessor list alone does not establish the applicable buyer authorisation, delivery of notice or opportunity to object.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an agent supplier add a subprocessor under general authorisation without a change-notice opportunity?

Buyer evidence still required

  • Applicable written authorisation
  • Current and proposed processor identity and purpose
  • Notice record and objection process

Review inference: A public subprocessor list alone does not establish the applicable buyer authorisation, delivery of notice or opportunity to object.

Suggested review condition: No universal notice period, automatic veto outcome or actual runtime processor use is inferred.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No universal notice period, automatic veto outcome or actual runtime processor use is inferred.
  • Specific prior written authorisation may cover a named subprocessor; the general-authorisation change-notice rule must not be applied as an invented universal notice interval.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

GitGuardian MCP: Scanning, identity and planned-capability limits

Question: Does GitGuardian MCP automatically revoke secrets or fix code after detecting an incident?

The Developer profile documents scanning, incident review and guided remediation, with limited honeytoken creation. Broader SecOps actions are described as planned, not established here as available. OAuth and personal-token modes have different credential handling. Publisher statements about secret handling are documentation evidence, not an independent execution test.

Source: GitGuardian MCP developer profile. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Documented beta Developer profile; planned SecOps features excluded

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

GitGuardian publishes the beta Developer MCP profile.

Documented by publisher. GitGuardian MCP developer profile; GitGuardian MCP authentication; GitGuardian MCP scanning and redaction

Purpose

Support secret scanning, incident understanding and guided remediation.

Documented by publisher. GitGuardian MCP developer profile; GitGuardian MCP authentication; GitGuardian MCP scanning and redaction

Read capability

Authorised incident context and scanning results.

Documented by publisher. GitGuardian MCP developer profile; GitGuardian MCP authentication; GitGuardian MCP scanning and redaction

Write capability

Limited honeytoken creation is described; planned SecOps revocation and code fixing are not treated as live.

Documented by publisher. GitGuardian MCP developer profile; GitGuardian MCP authentication; GitGuardian MCP scanning and redaction

Authentication

OAuth is the documented default; personal access tokens support non-interactive use.

Documented by publisher. GitGuardian MCP developer profile; GitGuardian MCP authentication; GitGuardian MCP scanning and redaction

Permission surface

The selected GitGuardian identity and its API permissions constrain access.

Documented by publisher. GitGuardian MCP developer profile; GitGuardian MCP authentication; GitGuardian MCP scanning and redaction

Data leaving the environment

Scanning uses GitGuardian APIs; its claim that secret values are withheld from the model remains publisher evidence.

Review inference. GitGuardian MCP developer profile; GitGuardian MCP authentication; GitGuardian MCP scanning and redaction

Failure modes to consider

Expired credentials, unavailable beta functions and mistaken assumptions about automatic remediation can interrupt work.

Review inference. GitGuardian MCP developer profile; GitGuardian MCP authentication; GitGuardian MCP scanning and redaction

Unknowns and applicability

Actual scopes, client logs and secret-handling behaviour have not been tested.

Not established

Suggested refusal or clarification condition

Do not promise revocation, code repair or secret non-disclosure without the corresponding current evidence and authority.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Beta release status, secret-handling documentation and permission scopes.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve which remediation claims are supported, planned or still untested.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitGuardian: Revocation and incident state

Question: Does a resolved GitGuardian incident prove the exposed credential was revoked?

Integrated revocation requires a supported provider, a valid secret and Full Access to the incident. The documented auto-resolution path also depends on a playbook. Many provider APIs do not directly confirm revocation; GitGuardian uses later validity checks. Preserve the revocation and validity evidence separately from the incident label.

Source: GitGuardian: Remediate incidents. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A resolved incident is sufficient proof of credential revocation.

Buyer evidence still required

  • Provider support and revocation event.
  • Subsequent validity result with time.
  • Incident timeline and enabled resolution playbook.

Suggested review condition: Require provider and validity evidence before asserting the credential is no longer usable.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Provider, incident timeline, revocation event, validity timestamps and playbook configuration.

Optional saved evidence: Save the distinction between workflow closure and credential invalidation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Actions: Job permissions and omitted scopes

Question: Does a workflow permission declaration describe every job token without checking job overrides?

GitHub supports workflow-level and job-level GITHUB_TOKEN permissions. When individual permissions are specified, omitted permissions become none. The job configuration and applicable default and trigger restrictions therefore matter when describing the token used by an action.

Source: GitHub: Workflow syntax for GitHub Actions. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a workflow permission declaration describe every job token without checking job overrides?

Buyer evidence still required

  • Workflow and job permission blocks.
  • Repository defaults and trigger context.
  • Credential type actually used by the action.

Suggested review condition: Review the executed job token separately from other credentials supplied to the workflow.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workflow revision, job, trigger and applicable token defaults.

Optional saved evidence: Does a workflow permission declaration describe every job token without checking job overrides?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Actions: Jobs that continue during cancellation

Question: Does canceling a GitHub Actions workflow immediately stop every running job and unfinished step?

GitHub re-evaluates running-job conditions during cancellation; a true condition such as always() lets the job continue. Conditions for unfinished steps in continuing jobs are also re-evaluated. Steps selected for cancellation receive process signals before forced termination. A cancel request is therefore not immediate evidence that every job or external action has stopped.

Source: GitHub Actions: Workflow cancellation. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does canceling a GitHub Actions workflow immediately stop every running job and unfinished step?

Buyer evidence still required

  • Workflow revision and job/step conditions in the canceled run.
  • Cancellation request, selected jobs and runner termination observations.
  • Outcomes and external effects of continuing jobs or cleanup steps.

Suggested review condition: Decline all-jobs-stopped conclusions until condition-selected continuations and their effects are accounted for.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workflow revision and job/step conditions in the canceled run. Cancellation request, selected jobs and runner termination observations. Outcomes and external effects of continuing jobs or cleanup steps.

Optional saved evidence: Recovery or cleanup automation can remain active after workflow cancellation and needs its own outcome review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Instant external-action cancellation, automatic rollback or authority to rerun jobs
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Actions: OIDC token requests and resource authority

Question: Does id-token: write give a GitHub workflow write permission over cloud resources?

GitHub states that id-token: write permits requesting an OIDC token; it does not grant write access to other resources. The receiving provider evaluates token claims against its trust conditions. Resource authority still needs a separate declared permission basis.

Source: GitHub: OpenID Connect reference. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does id-token: write give a GitHub workflow write permission over cloud resources?

Buyer evidence still required

  • Workflow OIDC permission.
  • Non-secret claim values and provider trust conditions.
  • Provider role and resource-action permissions.

Suggested review condition: Separate identity-token issuance from the downstream authority granted after token exchange.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workflow token permission, issued claims, provider trust and target resource.

Optional saved evidence: Does id-token: write give a GitHub workflow write permission over cloud resources?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Actions: Privileged workflows and untrusted contributions

Question: Does a pull-request workflow prove external contributions cannot access privileged execution?

GitHub warns that privileged workflow triggers combined with untrusted checkout can expose secrets or repository write access. Review triggers, checked-out revisions and job permissions together. A pull-request label or successful workflow run does not establish an isolated execution boundary.

Source: GitHub Actions privileged workflow and secret boundaries. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: All contribution checks run without privileged access.

Buyer evidence still required

  • Dated workflow definition and actual trigger
  • Effective job token and secret access
  • Evidence identifying the revision executed and runner isolation

Suggested review condition: Require workflow evidence before accepting a blanket claim that contributor code cannot reach privileged execution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck workflow triggers, action revisions, runner placement and credential scope.

Optional saved evidence: Save the privilege assumptions behind a supplier CI review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Actions: Rerun mode changes revision selection

Question: Does rerunning a GitHub job guarantee that a reusable workflow uses the same approved revision?

For reusable workflows referenced by a branch or tag, GitHub distinguishes rerun modes. Rerunning all jobs resolves the specified reference again; rerunning failed jobs or a specific job uses the called workflow commit from the first attempt. Record the resolved revision and rerun mode.

Source: GitHub: Reusing workflow configurations. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does rerunning a GitHub job guarantee that a reusable workflow uses the same approved revision?

Buyer evidence still required

  • Original referenced workflow and resolved SHA.
  • All-jobs versus failed-or-specific-job rerun selection.
  • Resolved revision and approval evidence for the rerun.

Suggested review condition: Bind approval to the code actually selected for the rerun rather than its unchanged reference label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Reusable workflow reference, rerun selection and resolved commit.

Optional saved evidence: Does rerunning a GitHub job guarantee that a reusable workflow uses the same approved revision?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub App keys: Rotation requires retiring the old signer

Question: Does generating a new GitHub App private key automatically retire the old one?

The guide supports multiple concurrent private keys for rotation and states that keys do not expire automatically. A new key therefore does not establish that the old signer is revoked. Inventory, consumer handoff and explicit old-key removal need evidence separate from successful generation.

Source: GitHub App private-key management. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Generating a replacement key completes key retirement.

Buyer evidence still required

  • Current key inventory without secret values.
  • Consumer migration evidence.
  • Old-key deletion/revocation record.

Suggested review condition: Require retirement evidence before declaring rotation complete.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Key inventory, consumers, storage and explicit retirement

Optional saved evidence: Preserve the migration and retirement evidence for application signing credentials.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Apps: Installation and user tokens carry different authority

Question: Does a GitHub App user token have the same effective access as its installation token?

Installation tokens act for an installation, while user tokens act on behalf of a user. The guide describes user-token access as constrained by both the app and the user. Select the token type and repository scope explicitly; an app permission list alone does not identify the complete effective actor.

Source: GitHub App token identity boundaries. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: All tokens issued to one GitHub App have equivalent authority.

Buyer evidence still required

  • Token type and installation or user identity.
  • App permissions and selected repository access.
  • User permissions and observed action attribution where applicable.

Suggested review condition: Do not approve an operation from app permissions alone when its identity path is unspecified.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token type, installation scope, user rights and app permissions

Optional saved evidence: Save which actor and permission intersection were considered before approving a repository action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Apps: Permission changes and installation approval

Question: Does changing a GitHub App registration prove every existing installation has the new permissions?

Added repository or organization permissions require approval by each installing account; added account permissions require approval by each authorizing user. Updated grants do not take effect there until approved. GitHub documents permission removals as taking effect immediately.

Source: GitHub: Modifying a GitHub App registration. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does changing a GitHub App registration prove every existing installation has the new permissions?

Buyer evidence still required

  • App registration permission change and its timestamp.
  • Installation or user-authorization identity and permission approval state.
  • Current token permission inventory and the intended action and repository.

Suggested review condition: Decline a uniform-authority claim based on registration settings alone; reconcile the specific installation grant before relying on the declared change.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. App registration permission change and its timestamp. Installation or user-authorization identity and permission approval state. Current token permission inventory and the intended action and repository.

Optional saved evidence: A supplier or operator comparing old and new agent declarations must distinguish a requested expansion from the grant accepted for the particular installation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Approval by every installation, current effective repository access or a verified successful action
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Apps: Refresh invalidates the previous token pair

Question: Can an agent keep using its old GitHub App user token after refreshing the token pair?

For expiring GitHub App user tokens, access lasts eight hours and refresh tokens last six months. Refreshing issues a new pair and invalidates both the old refresh token and old access token. Expired refresh tokens require a fresh user authorization flow.

Source: Refreshing user access tokens - GitHub Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an agent keep using its old GitHub App user token after refreshing the token pair?

Buyer evidence still required

  • Whether expiring user tokens are enabled.
  • Refresh generation and atomic credential update.
  • Worker rollout and reauthorization recovery evidence.

Suggested review condition: Do not rely on the previous pair remaining usable after a refresh succeeds.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Whether expiring user tokens are enabled. Refresh generation and atomic credential update. Worker rollout and reauthorization recovery evidence.

Optional saved evidence: Coordinate concurrent agent workers around token rotation and recovery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Installation-token behavior, credential rotation execution or guaranteed uninterrupted service
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Apps: Review the token actually issued

Question: Does a GitHub App installation token automatically have the narrow scope intended for one agent task?

GitHub allows repository and permission restrictions when generating installation tokens. Omitted restrictions inherit the documented installation or app scope, while requested rights cannot exceed the grant. The response reports token permissions, applicable repositories and expiry.

Source: GitHub: Generating an installation access token for a GitHub App. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a GitHub App installation token automatically have the narrow scope intended for one agent task?

Buyer evidence still required

  • Installation repositories and granted app permissions.
  • Token-generation repository and permission parameters.
  • Returned scope and expiry without exposing the token.

Suggested review condition: Review the issued scope against the task; do not infer downscoping from the task description.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Installation grant, token request restrictions and returned token scope.

Optional saved evidence: Does a GitHub App installation token automatically have the narrow scope intended for one agent task?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub attestation predicate trust boundary

Question: Does a successfully verified GitHub artifact attestation establish that all provenance predicate claims are trustworthy?

The GitHub CLI warns that, apart from certificate information and verified timestamps, an attestation’s contents can be influenced by the workflow that produced it. A compromised producing context can falsify predicate data; verification must include trust in that context.

Source: GitHub CLI: gh attestation verify. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a successfully verified GitHub artifact attestation establish that all provenance predicate claims are trustworthy?

Buyer evidence still required

  • Verified signer and digest
  • Predicate claims
  • Expected builder/workflow policy
  • Evidence about the producing context

Review inference: Review github attestation predicate trust boundary before accepting the buyer claim. The SLSA record checks expected parameter agreement. This decision asks whether the producer can control the asserted predicate, even when values match an expectation. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not infer predicate truth from signature validity alone. Require an appropriate trusted-builder policy and leave unsupported build claims unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. gh attestation verify

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer predicate truth from signature validity alone. Require an appropriate trusted-builder policy and leave unsupported build claims unresolved.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub attestation reusable-workflow signer policy

Question: When a GitHub attestation uses a reusable workflow, which workflow identity must a verifier constrain?

The GitHub CLI identifies the reusable workflow as the signer for attestations produced through reusable workflows. Verification policy can constrain the signer workflow or repository; the caller repository alone does not fully specify the permitted signer.

Source: GitHub CLI: gh attestation verify. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: When a GitHub attestation uses a reusable workflow, which workflow identity must a verifier constrain?

Buyer evidence still required

  • Artifact digest
  • Attestation
  • Expected signer workflow/repository and revision
  • Caller context

Review inference: Review github attestation reusable-workflow signer policy before accepting the buyer claim. The prior record covers general provenance versus safety. This question narrows the expected signer to the called workflow rather than conflating caller and signing workflow. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Require a deliberate expected signer policy. Do not treat a valid attestation associated with the caller as approval of every reusable workflow signer.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. gh attestation verify

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require a deliberate expected signer policy. Do not treat a valid attestation associated with the caller as approval of every reusable workflow signer.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub attestations: Verified provenance is not a security verdict

Question: Does a valid GitHub artifact attestation prove the artifact is secure to run?

Attestations bind artifacts to source and build context. The documentation says they must be verified to provide benefit and explicitly rejects treating them as a guarantee of artifact security. The consumer still needs policy criteria and evaluation of the referenced build and content.

Source: GitHub artifact attestation provenance. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A published attestation independently clears an artifact for execution.

Buyer evidence still required

  • Exact artifact digest and verified attestation result.
  • Expected source, workflow and build identity.
  • Consumer policy evaluation and unresolved content risks.

Suggested review condition: Do not substitute signature verification for an execution-suitability decision.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Artifact digest, build identity, verification result and consumer policy

Optional saved evidence: Preserve the provenance check and remaining policy questions for an artifact decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub audit evidence: Event coverage and export history

Question: Does a GitHub audit export establish a complete history of repository activity?

GitHub documents different audit access methods and coverage for web and Git events. Plan, export method and retention affect what can be obtained. A returned export therefore needs an event-type and time-range check; an absent row does not by itself establish that no activity occurred.

Source: GitHub organization audit access and retention. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An audit export contains every repository action needed for this review.

Buyer evidence still required

  • A dated export showing its query and event categories
  • Plan entitlement and exporter role
  • Streaming-destination continuity and retention, if longer history is required

Suggested review condition: Require additional evidence when the needed event type or time range is outside the demonstrated export coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck plan, available event categories, export method and archive retention.

Optional saved evidence: Preserve why an activity-history claim was limited to a specific export method and interval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub audit stream start time coverage

Question: Does enabling GitHub audit streaming backfill all earlier enterprise events?

GitHub documents that the stream exports audit and Git events for activity from the time streaming is enabled onwards. Existing searchable retention and newly enabled streaming are different coverage windows; historic export needs its own method and receipt.

Source: GitHub: Stream the enterprise audit log. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does enabling GitHub audit streaming backfill all earlier enterprise events?

Buyer evidence still required

  • stream enable timestamp
  • required audit interval
  • received event times
  • separate historical export and retention limits

Review inference: An operator enables an external audit archive after an incident. Pre-enable actions can be absent while the archive appears operational. Adds initial-enable coverage, distinct from recovery of an already existing paused stream. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse historic completeness from a newly enabled stream without a separately reconciled backfill.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. from the time the stream is enabled onwards

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse historic completeness from a newly enabled stream without a separately reconciled backfill.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub audit streaming: Recovery depends on pause and fault duration

Question: Can a GitHub Enterprise audit stream recover every event after a prolonged pause or configuration failure?

GitHub documents a seven-day buffer for paused streams; longer pauses resume from a bounded recent point, and pauses of three weeks or more restart from the current time. Misconfigured streams must be fixed within six days to avoid dropped events. At-least-once delivery can also produce duplicates.

Source: Streaming the audit log for your enterprise. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a GitHub Enterprise audit stream recover every event after a prolonged pause or configuration failure?

Buyer evidence still required

  • Stream identity, destination and pause or fault timeline
  • Health-check notifications and restoration times
  • Destination event coverage, duplicate handling and any independent backfill

Review inference: Stream recovery should be reconciled against the actual interruption interval and destination coverage.

Suggested review condition: Refuse continuous-coverage claims based only on restored delivery without reconciling the missing interval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer stream health, retained destination events and available backfill sources are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify evidence that must be recovered separately before an audit window is declared complete.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A complete audit archive, automatic backfill of missing periods or proof that missing events never occurred
  • Equivalence between paused-stream behavior, configuration faults and other GitHub export methods
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub checks: Successful status and skipped execution

Question: Does a passing required GitHub check prove its test job actually ran?

Required checks accept success, skipped and neutral conclusions. A job skipped by a condition can report success, while a whole workflow skipped by path or branch filtering can remain pending. Review job execution and the applicable commit, not just the merge badge, before claiming a release passed a specific test.

Source: GitHub: Troubleshooting required status checks. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A green required-check badge proves test execution.

Buyer evidence still required

  • Required check identity and applicable commit.
  • Job conditions, execution steps and conclusion.
  • Test output bound to the accepted revision.

Suggested review condition: Require actual execution evidence before describing a skipped or neutral check as a passed test.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Branch rules, workflow version, check identity, conditions and commit-bound test output.

Optional saved evidence: Preserve the difference between merge eligibility and demonstrated test execution.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub CODEOWNERS: Matching and enforcement

Question: Does a CODEOWNERS file prove the right owner must approve every change?

Code-owner review must be required through the applicable branch controls. Invalid lines are skipped, later matching patterns take precedence, and owners need suitable repository access. A file in the repository therefore does not prove complete matching or enforced review of the target branch.

Source: GitHub code owners. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The presence of CODEOWNERS guarantees all changes receive mandatory owner approval.

Buyer evidence still required

  • Target-branch CODEOWNERS version and syntax errors.
  • Matched file patterns and owner access.
  • Applicable required-review configuration.

Suggested review condition: Confirm matching and enforcement separately before asserting owner approval coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Target branch, ownership file, matched paths, team access and review settings.

Optional saved evidence: Save the versioned ownership and enforcement questions for release procurement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub Copilot: Content exclusion has surface limits

Question: Does a GitHub Copilot content-exclusion rule protect the same files in every agent mode?

GitHub documents content exclusion as unsupported in Copilot Chat Edit and Agent modes, and its support matrix marks Copilot CLI as not applicable. A configured exclusion must be assessed against the actual client and mode rather than treated as a universal agent access boundary.

Source: GitHub Copilot content exclusion. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a GitHub Copilot content-exclusion rule protect the same files in every agent mode?

Buyer evidence still required

  • The exclusion policy and repository scope.
  • The client, version and selected mode.
  • Separate file-access controls and verification for unsupported surfaces.

Suggested review condition: Do not approve universal file exclusion from a rule whose client or mode is unsupported.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The exclusion policy and repository scope. The client, version and selected mode. Separate file-access controls and verification for unsupported surfaces.

Optional saved evidence: A repository owner must identify supported surfaces before relying on an exclusion to protect sensitive files.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof that a particular file was read or excluded, or coverage of every Copilot feature
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub deploy keys: Member removal leaves repository credentials active

Question: Does removing a GitHub user revoke repository deploy keys that the user created?

GitHub deploy keys belong to repositories rather than personal accounts or organization membership. Removing their creator from the repository leaves those keys active. Deploy keys have no expiry date and are read-only unless write access was enabled. Offboarding therefore needs a separate deploy-key inventory and removal decision.

Source: Managing deploy keys. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does removing a GitHub user revoke repository deploy keys that the user created?

Buyer evidence still required

  • Repository deploy-key identifiers and read or write settings
  • Key custody and systems holding the private credential
  • Member-removal and separate key-removal evidence

Review inference: Removing membership and removing repository credentials are separate offboarding actions.

Suggested review condition: Refuse a complete-offboarding claim based only on membership removal while deploy-key status is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer key inventory, private-key copies and effective post-offboarding access are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Close deployment access that can survive an employee or agent-owner offboarding.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof that a particular key was copied, used or revoked
  • Equivalence with GitHub App tokens, personal tokens or SSH agent forwarding
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub deployment approvals: Reviewer lists and independence

Question: Does listing several required reviewers mean every reviewer must approve a deployment?

The documentation says one required reviewer can approve a job. Preventing self-review and restricting administrator bypass are separate settings, with plan and repository conditions. Review the actual environment and job reference before claiming independent multi-person approval from the reviewer list.

Source: GitHub deployment approval and bypass controls. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A list of required reviewers establishes unanimous independent approval.

Buyer evidence still required

  • Environment reviewer, self-review and bypass settings.
  • Plan/repository entitlement and job environment binding.
  • Approval evidence for the specific deployment.

Suggested review condition: Do not infer multiple approvals or independence from a reviewer list.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Environment settings, workflow references and plan conditions.

Optional saved evidence: Save the settings and observed approval evidence needed for a deployment-governance claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub fine-grained token pending approval

Question: Can a newly generated fine-grained GitHub token access private organization resources while required approval is pending?

When an organization requires approval, a fine-grained personal access token remains pending until an administrator reviews it and can only read public resources before approval. An organization owner’s request is automatically approved. Token generation and effective private-resource authorization are therefore separate states.

Source: Managing your personal access tokens - GitHub Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a newly generated fine-grained GitHub token access private organization resources while required approval is pending?

Buyer evidence still required

  • Token resource owner and requested repositories
  • Organization approval policy and token review status
  • Required endpoint permissions and actual access result

Review inference: Check the organization approval state before treating token creation as ready access.

Suggested review condition: Do not report private-resource access as provisioned while required approval is pending.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The organization policy and token approval state are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Distinguish provisioning completion from a credential awaiting organization approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Unrestricted private access merely because a token was generated
  • The organization policy and token approval state are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub immutable release asset completeness

Question: Does GitHub release immutability establish that all required deliverable assets were included?

GitHub recommends creating a draft, attaching all associated assets and then publishing so the asset set is in place before immutability applies. Treat publication as an asset-completeness checkpoint. A signed or immutable release can still omit an operationally required file if the required set was not checked beforehand.

Source: GitHub: Immutable releases. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does GitHub release immutability establish that all required deliverable assets were included?

Buyer evidence still required

  • required deliverable list
  • draft assets
  • version and licence files
  • digest inventory
  • publication state

Review inference: A release is published before its required schema or licence file is attached. Consumers receive an integrity-protected but incomplete package. Adds pre-publication deliverable completeness rather than verification of an already selected artifact. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: An integrity attestation does not prove that the chosen asset set satisfies a buyer's requirements.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Attach all associated assets to the draft release

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • An integrity attestation does not prove that the chosen asset set satisfies a buyer's requirements.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub immutable release mutable description

Question: Does an immutable GitHub release freeze its title, notes and latest designation?

GitHub locks an immutable release's assets and associated tag, but its title, release notes, pre-release status and latest designation remain editable. Preserve the actual asset digest and release attestation separately from a captured description. Immutability does not establish that later editorial claims were present when the artifact was approved.

Source: GitHub: Immutable releases. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does an immutable GitHub release freeze its title, notes and latest designation?

Buyer evidence still required

  • release tag and commit
  • asset digests
  • attestation
  • dated notes and title
  • approval evidence

Review inference: A buyer relies on revised release notes as the description approved with a sealed artifact. Editorial changes can be confused with immutable provenance. Adds mutable release-description scope rather than artifact identity alone. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Integrity protection is not code safety certification or approval of mutable description text.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Only the assets and tag are locked

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Integrity protection is not code safety certification or approval of mutable description text.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub immutable release tag reuse

Question: Can deleting an immutable GitHub release restore reuse of its tag name?

After the immutable release is deleted its tag may be deleted, but the same tag name cannot be reused. GitHub also retains protection against reusing tags from an immutable release when a repository is deleted and recreated with the same name. Deletion is therefore not a route to replacing a previously sealed release under its old tag.

Source: GitHub: Immutable releases. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can deleting an immutable GitHub release restore reuse of its tag name?

Buyer evidence still required

  • release identity
  • immutable status
  • tag history
  • intended replacement version

Review inference: A maintainer plans to replace a faulty published binary under its original version tag. The replacement plan can fail or confuse downstream version selection. Adds the release deletion and tag-reuse boundary beyond verifying an artifact subject. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: This does not establish continued artifact availability after release deletion or software suitability.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. cannot reuse the same tag name

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • This does not establish continued artifact availability after release deletion or software suitability.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub installation token narrowing

Question: Can a GitHub installation token request broader permissions or repositories than the app installation allows?

GitHub allows installation-token requests to narrow repositories and permissions, but not exceed the installation’s grants. Omitting those restrictions gives the token the installation’s permitted repositories and permissions. The documented token lifetime is one hour; an organization owner’s identity does not enlarge this token’s grant ceiling.

Source: Generating an installation access token for a GitHub App - GitHub Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a GitHub installation token request broader permissions or repositories than the app installation allows?

Buyer evidence still required

  • App and installation identity
  • Requested repository and permission restrictions
  • Installation grants and returned expiration/scope metadata

Review inference: Request only the approved subset and retain the resulting token-scope evidence.

Suggested review condition: Refuse a least-privilege claim without comparing the request and resulting token with the installation grant.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual installation and issued token restrictions are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Issue task-scoped GitHub credentials without assuming the app grant is already minimal.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authority beyond the app installation through administrator status
  • The actual installation and issued token restrictions are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub MCP: Repository access and write controls

Question: How can an agent review repository access without enabling GitHub MCP writes?

GitHub documents a read-only server mode that removes write tools and a separate choice of toolsets. Review both the credential's repository access and the configured server mode. Lockdown is a content filter with stated limitations. This profile helps scope a repository-review connection; it does not verify your token, server configuration or resistance to prompt injection.

Source: GitHub MCP server: hosting and authentication. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: GitHub-hosted remote MCP and the documented local server configuration; deployment, release and organization policies must be supplied by the buyer.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

GitHub publishes the server and hosts the remote service; a local deployment has its own operator.

Documented by publisher. GitHub MCP server: hosting and authentication; GitHub MCP server configuration

Purpose

Review repository content, issues and pull requests.

Documented by publisher. GitHub MCP server: hosting and authentication; GitHub MCP server configuration

Read capability

Repository files, issues and pull requests accessible through the selected tools and credential.

Documented by publisher. GitHub MCP server: hosting and authentication; GitHub MCP server configuration

Write capability

Write-capable toolsets exist; documented read-only mode excludes their write tools.

Documented by publisher. GitHub MCP server: hosting and authentication; GitHub MCP server configuration

Authentication

Remote OAuth or PAT authentication is documented; actual repository grants and organization policy require inspection.

Documented by publisher. GitHub MCP server: hosting and authentication; GitHub MCP server configuration

Permission surface

Toolset selection, exclusions and read-only mode are configurable. Lockdown does not reduce the underlying credential's authority.

Documented by publisher. GitHub MCP server: hosting and authentication; GitHub MCP server configuration

Data leaving the environment

Repository results return to the connected client. If that client uses a hosted model, selected content may leave the repository service; inspect that client's data policy.

Review inference. GitHub MCP server: hosting and authentication; GitHub MCP server configuration

Failure modes to consider

Overbroad credentials; assuming lockdown prevents all hostile content; enabling a write tool during a review-only task.

Review inference. GitHub MCP server: hosting and authentication; GitHub MCP server configuration

Unknowns and applicability

Actual token grants, effective tool list, enterprise hosting configuration and client retention/training terms.

Not established

Suggested refusal or clarification condition

For a review-only task, stop before writes; resolve unknown repository grants before reading private repositories.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the documented read-only and credential boundaries used when reviewing a repository connector.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub merge queue: Checks on the combined change

Question: Does a green pull-request check prove the queued merge combination passed?

A merge queue creates a temporary combined change with a different SHA. GitHub Actions must handle merge_group for required checks; third-party CI must handle the queue branch. A pull-request result is not automatically evidence for that combined state, and missing required reports can prevent the merge.

Source: GitHub merge queue. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An approved pull-request check automatically validates the queued merge SHA.

Buyer evidence still required

  • Pull-request and merge-group SHAs.
  • Required-check trigger configuration.
  • Check reports for the temporary merge group.

Suggested review condition: Bind acceptance evidence to the merge-group identity rather than reusing an unrelated green check.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Queue configuration, CI provider, triggers, required checks and merge-group identity.

Optional saved evidence: Preserve the source-bound distinction between isolated and combined release validation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub OAuth: Requested scopes are not the final grant

Question: Can an agent infer GitHub access from the scopes listed in an OAuth installation link?

GitHub distinguishes requested scopes from granted scopes: users can reduce access, including after authorization. Scope lists are also normalized, omitting narrower scopes implied by a broader one. Evaluate the current grant and its meaning rather than counting requested scope names.

Source: GitHub: Scopes for OAuth apps. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an agent infer GitHub access from the scopes listed in an OAuth installation link?

Buyer evidence still required

  • Requested scopes and current granted scopes.
  • Normalized scope implications.
  • Actual user role and operation-specific access evidence.

Suggested review condition: Do not infer permission loss or least privilege from an omitted implied scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. OAuth app identity, current granted scopes and intended GitHub operations.

Optional saved evidence: Save the effective-grant reasoning used in an app permission review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub offline attestation repository-name binding

Question: Can offline GitHub attestation verification detect that a repository name was later renamed or reused?

The GitHub CLI documents that offline bundle verification compares names recorded when the certificate was created. Without current GitHub API lookup it cannot detect later repository renaming or name reuse.

Source: GitHub CLI: gh attestation verify. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can offline GitHub attestation verification detect that a repository name was later renamed or reused?

Buyer evidence still required

  • Original certificate names and time
  • Attestation bundle
  • Intended current repository identity
  • Current API-backed identity evidence when required

Review inference: Review github offline attestation repository-name binding before accepting the buyer claim. Generic provenance qualification does not cover repository name rebinding after signing; this review bounds offline identity decisions across time. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse a current-owner identity claim based only on offline name matching. Keep historical signing identity distinct from present repository ownership.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. gh attestation verify

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a current-owner identity claim based only on offline name matching. Keep historical signing identity distinct from present repository ownership.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub private attestation transparency-log scope

Question: Should a GitHub private-repository attestation be assumed to have the public Sigstore transparency-log evidence?

GitHub documents different Sigstore instances: public-repository attestations use the public instance, while private-repository attestations use GitHub’s instance without a transparency log. The private instance federates with GitHub Actions.

Source: GitHub: Artifact attestations. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Should a GitHub private-repository attestation be assumed to have the public Sigstore transparency-log evidence?

Buyer evidence still required

  • Repository visibility at signing
  • Signing instance
  • Attestation evidence
  • Required transparency policy

Review inference: Review github private attestation transparency-log scope before accepting the buyer claim. The existing log review explains transparency evidence generally; this decision determines whether the GitHub private signing environment provides that evidence at all. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Identify the signing instance before requiring or claiming public log inclusion. A private attestation does not satisfy a public-transparency requirement merely because it is signed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Sigstore

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Identify the signing instance before requiring or claiming public log inclusion. A private attestation does not satisfy a public-transparency requirement merely because it is signed.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub push protection: Exceptions and reviewer authority

Question: Does enabled push protection prove no secret can be pushed?

GitHub documents bypass paths. With delegated bypass, contributors without bypass privileges need reviewer approval; without it, contributors can bypass at their discretion. Review exception permissions and decisions before interpreting the feature as a no-secret guarantee.

Source: GitHub push protection bypass review. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Push protection prevents every secret-containing push.

Buyer evidence still required

  • Effective bypass configuration and privileged identities
  • Designated human or app reviewers and their authority
  • Exception decisions for the relevant repository and period

Suggested review condition: Do not accept an absolute prevention claim from enablement alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck reviewer permissions, bypass policy and app approvals.

Optional saved evidence: Preserve the exception checks used in a source-control procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub repository recovery: Fork networks and permissions matter

Question: Does restoring a deleted GitHub repository restore its original access configuration?

The guide describes a bounded restoration window and fork-network conditions, with some cases requiring paid-plan support. It explicitly states that team permissions are not restored. Recovering repository content therefore does not prove that collaboration access or every dependent workflow has been recovered.

Source: GitHub deleted repository recovery. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Repository restoration recreates content and team access exactly as before.

Buyer evidence still required

  • Deleted repository identity, timing and fork-network state.
  • Plan and restoration path eligibility.
  • Re-established team permissions and dependent workflow checks.

Suggested review condition: Do not claim complete service recovery from repository restoration alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Deletion interval, fork network, plan and team permissions

Optional saved evidence: Retain the access and eligibility gaps behind a repository-recovery claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub REST: One successful response is one page

Question: Does a successful GitHub REST list response establish that every matching evidence item was collected?

GitHub paginates large list responses and provides continuation URLs in the Link header. Increasing per_page changes page size, not the need to follow remaining pages. The requested endpoint, filters and completed pagination define the retrieved evidence set.

Source: GitHub: Using pagination in the REST API. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a successful GitHub REST list response establish that every matching evidence item was collected?

Buyer evidence still required

  • Initial endpoint and filters.
  • Link headers and completed continuation requests.
  • Collection time and unresolved request failures.

Suggested review condition: Keep pagination completion evidence before describing a list as exhaustive within its requested scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Endpoint, query filters, response headers and continuation history.

Optional saved evidence: Does a successful GitHub REST list response establish that every matching evidence item was collected?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub reusable-workflow environment secret selection

Question: Does passing a repository secret to a reusable workflow establish the secret value used by a job with an environment?

GitHub documents that a called workflow’s job-level environment secret takes precedence over a same-name repository or organization secret. The caller must still pass the secret by name or inheritance; an unpassed secret can resolve to an empty value unless required. A required flag checks that the caller passes the secret, not that its value is nonempty.

Source: GitHub: Reuse workflows. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does passing a repository secret to a reusable workflow establish the secret value used by a job with an environment?

Buyer evidence still required

  • Caller secret-passing declaration
  • Called workflow revision
  • Job environment
  • Secret names and required flags without values

Review inference: Review github reusable-workflow environment secret selection before accepting the buyer claim. Nested forwarding is already reviewed; this decision concerns same-name environment selection and missing-secret behavior at the called job, which forwarding alone does not resolve. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Check both secret admission and environment selection before relying on the credential source. Do not infer a live credential value or successful authentication from workflow syntax.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Passing inputs and secrets to a reusable workflow

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Check both secret admission and environment selection before relying on the credential source. Do not infer a live credential value or successful authentication from workflow syntax.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitHub ruleset bypass authority

Question: Does repository contents-write permission establish that a GitHub App can bypass repository rulesets?

GitHub rulesets have an explicit bypass list that can include selected apps, roles and teams. Bypass can be limited to pull requests or allowed always, depending on configuration. A token’s contents-write permission does not identify whether the app is on that list or which bypass mode applies.

Source: Creating rulesets for a repository - GitHub Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does repository contents-write permission establish that a GitHub App can bypass repository rulesets?

Buyer evidence still required

  • Target repository, branch or tag and applicable rulesets
  • App identity and explicit bypass-list entries
  • Bypass mode and planned update path

Review inference: Inspect applicable rulesets and app-specific bypass entries separately from repository write permission.

Suggested review condition: Reject a bypass-authority claim based only on contents-write scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The repository’s effective rulesets and bypass assignments are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid promising a protected repository update that the app is not authorised to bypass.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic ruleset exemption from write access
  • The repository’s effective rulesets and bypass assignments are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub rulesets: Bypass actors and modes

Question: Does requiring a pull request prevent every authorised GitHub ruleset bypass?

GitHub rulesets can grant bypass to selected actors. The pull-request-only bypass mode requires a pull request but still lets the actor bypass protections when merging it. An active rule must therefore be read together with its targets and bypass list.

Source: GitHub: Creating rulesets for a repository. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does requiring a pull request prevent every authorised GitHub ruleset bypass?

Buyer evidence still required

  • Active ruleset and target patterns.
  • Bypass actors and selected modes.
  • Pull-request and merge evidence for the actor.

Suggested review condition: Do not treat the existence of a pull request as proof that every rule was satisfied.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Ruleset status, branch target, acting identity and bypass mode.

Optional saved evidence: Does requiring a pull request prevent every authorised GitHub ruleset bypass?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub runners: One-job registration and host cleanup

Question: Does an ephemeral self-hosted runner registration prove the underlying machine was wiped?

The runner reference recommends ephemeral autoscaling and describes one-job assignment with automatic deregistration. Host cleanup and external preservation of runner logs remain operator responsibilities. A vanished runner registration is therefore not evidence that residual workspace data or host state was destroyed.

Source: GitHub self-hosted runners reference. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Ephemeral runner registration proves complete host disposal.

Buyer evidence still required

  • One-job runner configuration.
  • Host cleanup/disposal evidence.
  • External runner-log retention.

Suggested review condition: Require host lifecycle evidence before asserting isolation between jobs.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Runner registration, host lifecycle, log forwarding and version

Optional saved evidence: Preserve the distinction between scheduler lifecycle and demonstrated environment disposal.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub tokens: SSO authorization has its own lifecycle

Question: Does possessing a GitHub personal token prove it can access an SSO-linked organization?

Classic personal tokens need SSO authorization for the organization; fine-grained tokens are authorized during creation. A linked SSO identity can require authorized credentials even without enforced SSO. Scope edits, regeneration, expiry or revocation can change that authorization.

Source: GitHub personal-token SSO authorization. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A valid personal token automatically retains organization SSO access.

Buyer evidence still required

  • Token type and linked organization identity.
  • SSO authorization state.
  • Token changes, expiry and organization membership.

Suggested review condition: Require current organization authorization without asking the user to disclose the token.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token type, SSO linkage, authorization and lifecycle

Optional saved evidence: Save the authorization-state checks needed to diagnose access without widening credentials.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub validity checks: Issuer contact and unknown results

Question: Does an unknown GitHub secret-validity result mean the credential is inactive?

GitHub checks supported secrets by contacting issuer APIs and may need host or URL context. Results can be active, inactive or unknown. Coverage varies by provider. An unknown result does not establish inactivity, and enabling verification involves disclosure to the issuer rather than a wholly local check.

Source: GitHub: Secret validity checks. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Unknown validity establishes that a detected secret cannot be used.

Buyer evidence still required

  • Supported secret type and enabled validity checks.
  • Check time, returned state and required context.
  • Approved issuer-contact and remediation process.

Suggested review condition: Keep unknown unresolved; do not interpret missing validation as an inactive credential.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Provider, secret type, validity setting, context and dated check result; exclude secret values.

Optional saved evidence: Retain a dated interpretation of a secret alert without exposing the secret.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub webhooks: Authenticity and replay are separate

Question: Does validating a GitHub webhook secret prove that a delivery has not already been processed?

GitHub distinguishes secret-based delivery validation from replay protection using X-GitHub-Delivery. Requested redeliveries keep the original delivery identifier. An authenticated payload therefore still needs delivery-identity handling before triggering another action.

Source: GitHub: Best practices for using webhooks. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does validating a GitHub webhook secret prove that a delivery has not already been processed?

Buyer evidence still required

  • Signature-validation configuration without secrets.
  • Delivery identifier and previous processing state.
  • Redelivery handling and authorised retry rules.

Suggested review condition: Require authenticity and duplicate handling separately before allowing webhook-triggered actions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Webhook verification, delivery identifier, processing record and redelivery policy.

Optional saved evidence: Does validating a GitHub webhook secret prove that a delivery has not already been processed?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub webhooks: Failed deliveries need recovery ownership

Question: Does GitHub automatically retry every failed webhook delivery?

GitHub documents that failed webhook deliveries are not automatically redelivered. Manual redelivery or a separately implemented scheduled recovery process is required. Failure records and available delivery APIs depend on webhook type. A configured webhook alone does not establish an automatic recovery service.

Source: GitHub failed webhook delivery recovery. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: GitHub webhook failure always triggers automatic provider retry.

Buyer evidence still required

  • Webhook type and delivery history.
  • Recovery schedule and authorization.
  • Receiver deduplication and replay results.

Suggested review condition: Require evidence of a working recovery process before claiming automatic redelivery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Webhook type, delivery records, recovery scheduler and receiver idempotency.

Optional saved evidence: Preserve the evidence basis for an integration recovery commitment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub workflow run and attempt identity

Question: Can a GitHub Actions rerun keep the same run ID while producing different attempt evidence?

GitHub documents that GITHUB_RUN_ID and GITHUB_RUN_NUMBER remain unchanged on rerun, while GITHUB_RUN_ATTEMPT increments for each attempt. A run ID alone therefore cannot distinguish the logs, results and artifacts produced by separate attempts.

Source: Variables reference - GitHub Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a GitHub Actions rerun keep the same run ID while producing different attempt evidence?

Buyer evidence still required

  • Repository, run ID and attempt number
  • Workflow revision and referenced reusable workflows
  • Attempt-specific logs, results and artifact identities

Review inference: Bind reconstruction to run ID, attempt and the relevant revision and outputs.

Suggested review condition: Reject evidence that merges separate attempts solely by run ID.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s attempt outcomes and served deployment are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid attaching a later attempt’s output to an earlier approval or failure.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof of deployment success from a workflow identifier
  • The buyer’s attempt outcomes and served deployment are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub: Dependency submissions have source precedence

Question: Does enabling automatic dependency submission replace a user-submitted manifest snapshot in GitHub graph?

GitHub describes one displayed manifest instance selected through source precedence: user submissions outrank Dependabot graph jobs, automatic submissions and static analysis. Same-detector correlators can be merged. Enabling automation therefore does not establish that its snapshot is the evidence currently displayed.

Source: GitHub dependency graph data sources. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does enabling automatic dependency submission replace a user-submitted manifest snapshot in GitHub graph?

Buyer evidence still required

  • The manifest and contributing submission methods.
  • Detector, correlator and build revision metadata.
  • The displayed dependency set and source precedence.

Suggested review condition: Do not assume the latest enabled collection method controls the graph without resolving higher-priority submissions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The manifest and contributing submission methods. Detector, correlator and build revision metadata. The displayed dependency set and source precedence.

Optional saved evidence: A build owner must identify which dependency submission actually supplies the graph before relying on its freshness and coverage.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Independent validation of submitted dependencies or automatic correction of stale snapshots
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub: Deployment reviewer quorum and bypass

Question: Does naming several GitHub environment reviewers require every reviewer to approve an agent deployment?

Only one listed required reviewer needs to approve a referencing job. Preventing the initiator from self-review is a separate setting. Administrators can bypass protection rules by default unless that bypass is disabled. Feature availability depends on plan and repository visibility.

Source: Deployments and environments - GitHub Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does naming several GitHub environment reviewers require every reviewer to approve an agent deployment?

Buyer evidence still required

  • Environment reviewer and bypass configuration.
  • Initiator and approving actor.
  • Referencing job, repository visibility and plan.

Suggested review condition: Do not claim multi-party approval from the reviewer list alone; resolve self-review and bypass settings.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Environment reviewer and bypass configuration. Initiator and approving actor. Referencing job, repository visibility and plan.

Optional saved evidence: Assess whether deployment approval actually matches the intended separation of duties.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual reviewer independence, runtime enforcement or approval of the deployed artifact
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitHub: Static dependency analysis cannot resolve build variables

Question: Will GitHub dependency graph include packages whose names or versions are supplied through build variables?

GitHub states that manifest analysis lacks the project build environment and cannot resolve variables used for dependency names or versions. Such dependencies are not automatically included through that analysis. A graph review must reconcile build-resolved inputs before claiming inventory completeness.

Source: GitHub dependency graph troubleshooting. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Will GitHub dependency graph include packages whose names or versions are supplied through build variables?

Buyer evidence still required

  • The manifest and variable-based declarations.
  • The build-resolved names, versions and lock information.
  • The graph or submitted snapshot used for comparison.

Suggested review condition: Do not claim complete dependency coverage while unresolved build variables omit required packages.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The manifest and variable-based declarations. The build-resolved names, versions and lock information. The graph or submitted snapshot used for comparison.

Optional saved evidence: A software buyer needs to know whether the graph covers the dependencies actually selected by the build.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual scan completeness or a vulnerability-free assessment
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab approvals: Independent people and revisions

Question: Does a GitLab approval count prove independent review of the latest revision?

Approval settings separately govern authors, committers, rule overrides and reset behaviour after changes. Committers can approve by default unless restricted. Changed diffs normally reset approvals, but that behaviour can be changed. Counts alone do not identify reviewer independence or the revision accepted.

Source: GitLab merge request approval settings. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Two recorded approvals prove independent acceptance of the current code.

Buyer evidence still required

  • Author and committer identities.
  • Approval-rule override and reset settings.
  • Approved revision and later diff changes.

Suggested review condition: Bind approvers and approvals to the accepted revision before claiming independent review.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Project tier, approval settings, identities and revision history.

Optional saved evidence: Retain the documented evidence required to substantiate a supplier review claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab audit streaming: Event delivery is not exactly once

Question: Can an audit receiver count each GitLab streamed event as a unique action?

GitLab documents that one event can be streamed more than once to the same destination and recommends deduplication using its event identifier. Destinations can also be deactivated independently. Receiver counts need event identity and destination-state context before being presented as counts of distinct actions.

Source: GitLab audit event streaming reliability. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every received audit message represents one distinct user action.

Buyer evidence still required

  • Event identifier handling and receiver deduplication.
  • Destination configuration and active-state history.
  • Reconciliation of unique events for the stated reporting interval.

Suggested review condition: Do not equate message count with unique action count without deduplication.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Event IDs, receiver deduplication, destination state and reporting interval

Optional saved evidence: Preserve how duplicate messages and destination state affect audit counts.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab deployment: Approval and execution are distinct

Question: Does an approved GitLab deployment mean the deployment job has run?

Protected-environment approvals allow a deployment to proceed, but the job must then be run manually. Pipeline-triggerer self-approval is separately configurable, and administrators can approve or reject deployments. Approval state is not execution success or proof of the resulting environment.

Source: GitLab deployment approvals. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Approved deployment status proves successful release to the environment.

Buyer evidence still required

  • Environment approval rules and approver identities.
  • Job execution and completion status.
  • Resulting deployment identity and environment evidence.

Suggested review condition: Keep authorization, execution and environment verification as separate evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Protected environment, approval rules, identities and job outcome.

Optional saved evidence: Save a release-review record that does not confuse approval with delivery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab downstream pipeline initiating-user permission

Question: Does a successful upstream GitLab pipeline prove that its user may start a downstream project pipeline?

For multi-project pipelines, GitLab requires the user creating the upstream pipeline to be able to start pipelines in the downstream project. A trigger job can fail when that user lacks the required permission.

Source: GitLab: Downstream pipelines. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a successful upstream GitLab pipeline prove that its user may start a downstream project pipeline?

Buyer evidence still required

  • Upstream pipeline and initiating user
  • Downstream project
  • Applicable protected-ref restrictions
  • Trigger-job result

Review inference: Review gitlab downstream pipeline initiating-user permission before accepting the buyer claim. The prior record addresses API token allowlisting. This decision binds a pipeline-to-pipeline creation attempt to its initiating user and target project rather than to a generic allowlist. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Check the initiating user and target-ref access before relying on downstream creation. Upstream success alone does not establish cross-project authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Multi-project pipelines

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Check the initiating user and target-ref access before relying on downstream creation. Upstream success alone does not establish cross-project authority.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab fine-grained job-token exceptions

Question: Does a GitLab job-token fine-grained allowlist restrict every API endpoint the token can use?

GitLab lists endpoints without fine-grained permissions and states that permissions on an allowlist entry do not restrict those endpoints. A fine-grained rule list is therefore not a complete description of token authority. Review the documented exceptions together with the triggering identity, project access and applicable GitLab version.

Source: GitLab: Fine-grained permissions for CI/CD job tokens. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a GitLab job-token fine-grained allowlist restrict every API endpoint the token can use?

Buyer evidence still required

  • GitLab version and allowlist rules
  • Required API method and endpoint
  • Documented exception list
  • Triggering user and target-project access

Review inference: Review gitlab fine-grained job-token exceptions before accepting the buyer claim. Endpoint exceptions to fine-grained rules are distinct from the existing rule that allowlisting does not grant user permissions. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: This does not establish unauthenticated access or bypass of every other project and user authorization check.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Endpoints without fine-grained permissions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • This does not establish unauthenticated access or bypass of every other project and user authorization check.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab forwarded-variable masking boundary

Question: Does forwarding a masked GitLab variable to another project preserve its masking configuration?

GitLab warns against forwarding masked variables to multi-project pipelines because the masking configuration is not passed downstream. The value could be revealed in downstream job logs.

Source: GitLab: Downstream pipelines. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does forwarding a masked GitLab variable to another project preserve its masking configuration?

Buyer evidence still required

  • Variable source and masking configuration
  • Forwarding configuration
  • Downstream project and logging policy

Review inference: Review gitlab forwarded-variable masking boundary before accepting the buyer claim. The prior review covers masking limits in a job. This boundary concerns losing masking metadata when a value crosses project pipeline boundaries. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not treat upstream masking as a downstream secrecy guarantee. Require an approved downstream secret mechanism and avoid exposing secret values in evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Pass a predefined variable

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat upstream masking as a downstream secrecy guarantee. Require an approved downstream secret mechanism and avoid exposing secret values in evidence.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab forwarded-variable precedence

Question: Can a GitLab downstream project’s variable value override a forwarded upstream value of the same name?

GitLab documents that upstream variables take precedence over same-name downstream variables. Forwarded variables become trigger variables with high precedence, so local downstream configuration alone may not identify the effective value.

Source: GitLab: Downstream pipelines. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a GitLab downstream project’s variable value override a forwarded upstream value of the same name?

Buyer evidence still required

  • Upstream values and forwarding policy
  • Downstream variable declarations
  • Effective job configuration
  • Target ref

Review inference: Review gitlab forwarded-variable precedence before accepting the buyer claim. Masking addresses disclosure; this review addresses configuration authority when a higher-precedence forwarded value replaces a downstream declaration. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Reconcile precedence and permitted overrides before treating downstream configuration as the effective policy. Do not include secret values in public records.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Pass CI/CD variables to a downstream pipeline;Control what type of variables to forward to downstream pipelines

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile precedence and permitted overrides before treating downstream configuration as the effective policy. Do not include secret values in public records.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab group allowlists and later project membership

Question: Can a GitLab group allowlist authorize a newly added nested project without editing the allowlist?

GitLab documents group allowlist matching across projects in the group and all nested subgroups. The match is evaluated whenever a job uses the token, so projects added later are included without an allowlist change. Permission reviews must include group membership over time as well as effective user and operation permissions.

Source: GitLab: CI/CD job token. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a GitLab group allowlist authorize a newly added nested project without editing the allowlist?

Buyer evidence still required

  • Target allowlist and group path
  • Group and subgroup membership at request time
  • Triggering user and operation permissions

Review inference: Review gitlab group allowlists and later project membership before accepting the buyer claim. Dynamic membership changes the eligible origin set without editing the policy entry; prior evidence covers effective user rights. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Group membership is not proof that the triggering user has the target permissions or that a specific call succeeded.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Add a group or project to the job token allowlist

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Group membership is not proof that the triggering user has the target permissions or that a specific call succeeded.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab immutable tags: Rule scope and propagation still matter

Question: Does an immutable container-tag rule make every tag permanently undeletable?

Immutable rules match patterns and differ from role-based protected-tag rules. The guide allows an Owner to delete an immutable rule and describes propagation delays tied to existing tokens. Inspect the actual pattern, rule state and effective time before treating a tag label as permanent or universal protection.

Source: GitLab immutable container tag rules. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An immutable-tag setting permanently protects every registry tag.

Buyer evidence still required

  • Matching immutable/protected rules and current ownership rights.
  • Rule-change time and token propagation interval.
  • The exact tag and authorised evidence of enforced behaviour.

Suggested review condition: Do not claim permanent universal immutability from a rule label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Rule patterns, owner authority, token propagation and tag identity

Optional saved evidence: Preserve the pattern and lifecycle evidence behind an image-protection claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab job tokens: Allowlist and effective user access

Question: Does a GitLab job-token allowlist grant the pipeline user access to another project?

GitLab states that adding a project to the job-token allowlist does not grant extra permissions to its members. Access also depends on the triggering user and allowed token capabilities. Review both the source-project allowlist and the effective identity before accepting a cross-project access claim.

Source: GitLab job token allowlist and effective permissions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The job-token allowlist fully defines cross-project pipeline authority.

Buyer evidence still required

  • Target project allowlist and access settings
  • Triggering user identity and target permissions
  • Required operation and token capability evidence

Suggested review condition: Require identity and operation evidence when an allowlist alone is presented as proof of effective access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck membership, job-token settings and supported operations.

Optional saved evidence: Retain the distinction between an allowed pipeline origin and authorized target operations.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab job-token pushes and missing validation pipelines

Question: Does a successful GitLab job-token push prove that the target revision started a validation pipeline?

GitLab documents that pushes authenticated with a CI/CD job token do not trigger CI/CD pipelines. Enabling job-token push permission and recording a successful push therefore establish neither a pipeline start nor validation of the resulting revision. Retain independent pipeline evidence if validation is a release condition.

Source: GitLab: CI/CD job token. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a successful GitLab job-token push prove that the target revision started a validation pipeline?

Buyer evidence still required

  • Push identity and target commit
  • Job-token push settings
  • Independent pipeline trigger and result for that commit

Review inference: Review gitlab job-token pushes and missing validation pipelines before accepting the buyer claim. The missing automatic validation trigger after a token push differs from deployment approval versus job completion. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: A successful push is not evidence of a tested revision, and documentation does not prove the buyer enabled push access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Allow Git push requests to your project repository; Allow cross-project Git push requests from allowlisted projects

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A successful push is not evidence of a tested revision, and documentation does not prove the buyer enabled push access.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab manual jobs: Optional steps and blocking gates

Question: Does a manual GitLab job necessarily block release until someone approves it?

Manual jobs can be optional or blocking. Outside rules, when: manual defaults to allow_failure true; inside rules, its default is false. Explicit configuration can alter the outcome. A pipeline can succeed despite optional manual-job failures, so inspect the effective gate rather than relying on the manual button.

Source: GitLab: Control jobs. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every manual job is a mandatory approval gate.

Buyer evidence still required

  • Expanded job configuration and effective allow_failure.
  • Rules matched for the release event.
  • Pipeline state and authorized operator evidence.

Suggested review condition: Require evidence of a blocking gate before treating a manual job as mandatory release approval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. GitLab version, expanded rules, allow_failure, release event and operator permissions.

Optional saved evidence: Save the enforcement basis behind a manual-release-control claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab MCP: Project permission and tool discovery

Question: Does a GitLab MCP tool listing establish permission to change a project?

GitLab documents separate tool discovery and per-call project permissions. Its tool reference includes both reading project data and changing work items, merge requests or files. Some tool availability depends on release, licensing and enabled features. Before approving a task, establish the actual instance, authenticated identity and project rights. A listed tool is not evidence of authorization for a particular change.

Source: GitLab MCP server. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official GitLab MCP on GitLab.com, Self-Managed or Dedicated; rolling documentation includes release-specific features that must be matched to the actual instance.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

GitLab publishes the implementation; GitLab.com and a buyer-operated instance have different operators.

Documented by publisher. GitLab MCP server; GitLab MCP tools

Purpose

Inspect project evidence and manage development work through GitLab.

Documented by publisher. GitLab MCP server; GitLab MCP tools

Read capability

Project information, work items, merge requests and repository data through available tools.

Documented by publisher. GitLab MCP server; GitLab MCP tools

Write capability

The tool reference includes work-item changes, merge-request changes and commits, subject to applicable permissions.

Documented by publisher. GitLab MCP server; GitLab MCP tools

Authentication

OAuth dynamic client registration and user authorization are documented; MCP access must be allowed for the relevant group or instance.

Documented by publisher. GitLab MCP server; GitLab MCP tools

Permission surface

Tool selection controls discovery. GitLab documents project and namespace permission checks when tools are called.

Documented by publisher. GitLab MCP server; GitLab MCP tools

Data leaving the environment

Selected project data is returned to the connected client. Self-hosting GitLab does not establish where that client's model processes it.

Review inference. GitLab MCP server; GitLab MCP tools

Failure modes to consider

Assuming discovery grants authority; mismatching documented release and deployed release; acting on instructions embedded in project content.

Review inference. GitLab MCP server; GitLab MCP tools

Unknowns and applicability

Instance release, enabled tool groups, licensed features, identity grants and client handling of confidential work items.

Not established

Suggested refusal or clarification condition

Resolve the project and identity before mutation; do not treat a tool listing as approval to commit or modify work.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the distinction between tool availability and project authorization for a development-tool procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab merge-request artifact ref identity

Question: Does fetching downstream artifacts by branch name identify the upstream merge-request pipeline’s artifacts?

GitLab instructs merge-request artifact consumers to use the merge-request ref path through CI_MERGE_REQUEST_REF_PATH. Using the branch name retrieves artifacts from the latest branch pipeline instead of the merge-request pipeline.

Source: GitLab: Downstream pipelines. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does fetching downstream artifacts by branch name identify the upstream merge-request pipeline’s artifacts?

Buyer evidence still required

  • Merge-request ID and ref path
  • Upstream pipeline/job
  • Artifact digest
  • Downstream needs configuration

Review inference: Review gitlab merge-request artifact ref identity before accepting the buyer claim. The prior record separates GitHub run attempts. This decision addresses GitLab’s distinct branch-versus-merge-request artifact selection mechanism. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Require the intended merge-request ref and artifact identity. A matching branch name is not sufficient evidence that the artifact came from the reviewed merge-request pipeline.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Fetch artifacts from an upstream merge request pipeline

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the intended merge-request ref and artifact identity. A matching branch name is not sufficient evidence that the artifact came from the reviewed merge-request pipeline.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab multi-project cancellation boundary

Question: Does starting a replacement upstream GitLab pipeline automatically stop its earlier multi-project downstream work?

GitLab documents that multi-project downstream pipelines are not automatically cancelled when a new upstream pipeline starts, even when interruptible is configured. Cancellation in the downstream project has its own context.

Source: GitLab: Downstream pipelines. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does starting a replacement upstream GitLab pipeline automatically stop its earlier multi-project downstream work?

Buyer evidence still required

  • Upstream and downstream pipeline IDs
  • Cancellation events
  • Project/ref context
  • Downstream final status

Review inference: Review gitlab multi-project cancellation boundary before accepting the buyer claim. The existing deployment review distinguishes approval and completion, not independently continuing multi-project work after an upstream change. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Verify the downstream state independently before assuming superseded upstream work cannot still execute. A replacement upstream pipeline is not evidence of downstream cancellation or rollback.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Multi-project pipelines

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Verify the downstream state independently before assuming superseded upstream work cannot still execute. A replacement upstream pipeline is not evidence of downstream cancellation or rollback.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab protected tags: Matching rules and deletion authority

Question: Does a protected GitLab tag mean nobody can create or delete a matching release tag?

Protected tags restrict creation to authorized roles or users; matching wildcard rules require joint review rather than assuming one restrictive pattern wins. Authorized maintainers can delete protected tags through GitLab's UI or API. Protection is an access-control setting, not evidence that a release reference is immutable.

Source: GitLab protected tag rules. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Protected release tags are unchangeable by every project user.

Buyer evidence still required

  • All matching protected-tag rules.
  • Allowed creators and project roles.
  • Tag deletion history and release identity binding.

Suggested review condition: Do not treat tag protection as an immutable release seal.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Project roles, matching tag patterns, allowed creators and release commit identity.

Optional saved evidence: Retain access-rule evidence without overstating release immutability.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab runners: Executor choice and cross-job trust

Question: Does running a GitLab job in Docker establish isolation from the runner host?

GitLab distinguishes shell, non-privileged and privileged container execution. Privileged mode exposes substantially more host authority; reusable runners can also carry effects across projects. A container label alone is insufficient: executor, privileges, reuse and network reach determine the review scope.

Source: GitLab self-managed runner security. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A Docker executor is automatically an adequate isolation boundary.

Buyer evidence still required

  • Executor and privilege configuration.
  • Runner reuse and project assignment.
  • Host identity and network access.

Suggested review condition: Do not approve untrusted execution based only on the word container.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Executor, privileges, reuse, project scope and host network

Optional saved evidence: Retain the concrete executor and reuse evidence behind CI access approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab token rotation: Old-token invalidation needs a consumer handoff

Question: Does rotating a GitLab personal access token preserve uninterrupted access for existing consumers?

Rotation creates a replacement and invalidates the previous token immediately while retaining the original permissions and scope. Consumers still need the new credential. Rotation is a lifecycle action, not evidence that every dependent integration has switched successfully or that access was narrowed.

Source: GitLab personal token rotation and expiry. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Rotating the token guarantees uninterrupted and more restricted access.

Buyer evidence still required

  • Original and replacement scope and expiry metadata.
  • Inventory of dependent integrations and their update path.
  • Authorised verification of old-token failure and new-token use.

Suggested review condition: Require a consumer handoff before claiming successful continuity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token scopes, expiry, dependent consumers and credential handoff

Optional saved evidence: Preserve the integration handoff and scope questions behind a rotation decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab trigger success and downstream completion

Question: Does a passed GitLab trigger job prove its downstream pipeline completed successfully?

By default, a trigger job passes when the downstream pipeline is created. GitLab provides a trigger strategy to reflect downstream status; default trigger success alone does not report the downstream execution outcome.

Source: GitLab: Downstream pipelines. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a passed GitLab trigger job prove its downstream pipeline completed successfully?

Buyer evidence still required

  • Trigger configuration and strategy
  • Trigger-job result
  • Downstream pipeline identity and final status

Review inference: Review gitlab trigger success and downstream completion before accepting the buyer claim. Approval-versus-job execution is already covered. This question addresses the separate creation-versus-completion semantics of a pipeline trigger job. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Require the linked downstream result or an applicable status-propagating strategy before declaring downstream work complete.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Trigger a downstream pipeline from a job in the .gitlab-ci.yml file

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the linked downstream result or an applicable status-propagating strategy before declaring downstream work complete.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab trigger-token user authority

Question: Whose project permissions does a GitLab pipeline trigger token use?

GitLab documents that a pipeline trigger token impersonates the creating user’s project access and permissions. Possessing the token is not independent evidence that the intended delegated action has owner approval.

Source: GitLab: Trigger pipelines with the API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Whose project permissions does a GitLab pipeline trigger token use?

Buyer evidence still required

  • Trigger identity and creator
  • Current creator permissions
  • Target project and ref
  • Declared delegation scope

Review inference: Review gitlab trigger-token user authority before accepting the buyer claim. The existing review covers CI job-token allowlists. A separately created pipeline trigger token has a different authority principal and must not be assigned the job-token permission model. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Require the creator, current target access and intended delegation to agree. Do not infer narrowly scoped authority from the token’s pipeline-trigger label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Create a pipeline trigger token

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the creator, current target access and intended delegation to agree. Do not infer narrowly scoped authority from the token’s pipeline-trigger label.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GitLab variables: Masking and pipeline trust

Question: Does masking a GitLab variable prevent a job from disclosing it?

GitLab warns that masking is not a guarantee against malicious scripts and that both masked and protected variables can be compromised by code given access. Log display controls and job-access restrictions address different questions. Review the pipeline and variable availability before accepting an isolation claim.

Source: GitLab CI variable masking, protection and script exposure. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Masked or protected variables cannot leave CI jobs.

Buyer evidence still required

  • Variable availability in the exact pipeline context
  • Review of code and dependencies allowed to use the variable
  • Relevant masking, hiding and protection settings

Suggested review condition: Do not equate log masking with isolation from executing code.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck pipeline changes, variable availability and branch rules.

Optional saved evidence: Save the evidence checklist for a supplier CI-secret handling claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GitLab.com SCIM: Group removal is not account deletion

Question: Does GitLab.com group SCIM deprovisioning delete the user's GitLab account?

After the identity provider sync, group SCIM removes access to the top-level group and its subgroups and projects. The GitLab.com account remains, and the linked SAML identity is retained. Enabling SCIM also does not automatically remove existing users without a SAML identity.

Source: GitLab.com: Configure group SCIM. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does GitLab.com group SCIM deprovisioning delete the user's GitLab account?

Buyer evidence still required

  • GitLab offering, managed top-level group and linked identity.
  • Completed IdP synchronization and membership state.
  • Review of unlinked existing users and any separate account-deletion requirement.

Suggested review condition: Do not report account erasure or universal offboarding from group removal alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. GitLab.com group, identity linkage, synchronization and intended removal scope.

Optional saved evidence: Retain the specific access-removal result without overstating identity or data deletion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Glean Loopio: Permission and deletion timing need reconciliation

Question: Does removing a Loopio user or project immediately remove it from Glean search?

Glean documents daily participant updates and weekly full synchronization, with deletions detected by the full sync. Its page also warns that removed-user or deleted-project results can persist until that full sync, while its timing table describes daily access updates. The applicable access window needs clarification rather than an immediate-removal assumption.

Source: Glean: Loopio connector overview. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does removing a Loopio user or project immediately remove it from Glean search?

Buyer evidence still required

  • Affected user, project and removal timestamp.
  • Relevant participant sweep and full-sync completion.
  • Clarification of the documented timing discrepancy and a denied-access check.

Suggested review condition: Do not assert immediate access removal while the connector's effective synchronization window is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Loopio role, participant changes, Glean crawl evidence and documented timing ambiguity.

Optional saved evidence: Preserve the permission-removal question and unresolved window in supplier review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Glean MCP: Tenant access and configured tools

Question: Does enabling Glean MCP mean any assistant can access all company knowledge?

No. Glean documents per-user access, tenant-controlled server availability and application-registration controls. The organisational connector is distinct from the public documentation MCP. Review the selected tenant server, permitted client and configured tools; connection success alone does not establish the audience or allowed actions.

Source: Glean tenant MCP access, OAuth and configured tools. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Tenant-specific knowledge and configured tools

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Glean operates the tenant-specific remote MCP service.

Documented by publisher. Glean tenant MCP access, OAuth and configured tools

Purpose

Connect assistants to organisational knowledge and configured tools.

Documented by publisher. Glean tenant MCP access, OAuth and configured tools

Read capability

Returns indexed content within the connected user access.

Documented by publisher. Glean tenant MCP access, OAuth and configured tools

Write capability

The overview does not enumerate write actions for every tenant-configured tool.

Not established. Glean tenant MCP access, OAuth and configured tools

Authentication

OAuth with organisational SSO; API-token fallback for incompatible hosts.

Documented by publisher. Glean tenant MCP access, OAuth and configured tools

Permission surface

Tenant enablement, approved application registration and user access all matter.

Documented by publisher. Glean tenant MCP access, OAuth and configured tools

Data leaving the environment

Accessible organisational content enters the chosen assistant.

Review inference. Glean tenant MCP access, OAuth and configured tools

Failure modes to consider

Confusing public documentation access with tenant access can misstate what was connected.

Review inference. Glean tenant MCP access, OAuth and configured tools

Unknowns and applicability

Buyer client approval, configured actions and user entitlements are unknown.

Not established

Suggested refusal or clarification condition

Require the tenant server and enabled tool list before approving organisational access.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck application registration policy, configured tools and user access.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the identity and client-registration checks used for enterprise search onboarding.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Gmail history: An expired cursor needs resynchronization

Question: Does a Gmail history 404 mean there were no mailbox changes?

Gmail history is available for a bounded period that can be shorter than expected. An out-of-range startHistoryId produces HTTP 404; the documented response is a full synchronization. Treating this as an empty change list would leave an unsupported coverage gap.

Source: Gmail: Synchronize clients. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a Gmail history 404 mean there were no mailbox changes?

Buyer evidence still required

  • Stored history identifier and its last successful use.
  • History error and account identity.
  • Completed replacement full sync and new history baseline.

Suggested review condition: Do not advance a completeness claim past an expired history cursor without resynchronization.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Mailbox, history cursor, outage interval and replacement synchronization.

Optional saved evidence: Preserve the evidence needed to close a communications-history gap.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Gmail: Sending does not require full mailbox access

Question: Does an agent that only sends Gmail messages need permission to read and delete the mailbox?

Gmail publishes separate scopes for sending, managing drafts and broader mailbox operations. gmail.send permits sending without read or modify privileges; gmail.compose includes managing drafts and sending. A send-only task does not by itself justify full-mailbox scope.

Source: Gmail: Choose API scopes. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does an agent that only sends Gmail messages need permission to read and delete the mailbox?

Buyer evidence still required

  • Operations actually required by the workflow.
  • Granted token scopes rather than the consent request alone.
  • Any separate need for reading, drafts or permanent deletion.

Suggested review condition: Request or use only permissions justified by the authorised communications task.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Intended mail operations, granted scopes and disclosure needs.

Optional saved evidence: Retain the operation-to-scope justification for a communications supplier.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

Go netip: Check the toolchain and affected method usage

Question: Is checking third-party dependencies enough to assess Go CVE-2024-24790?

The Go vulnerability report GO-2024-2887 concerns net/netip in the standard library. Certain address-classification methods, including IsPrivate and IsLoopback, can misclassify IPv4-mapped IPv6 addresses. The report lists affected toolchains before 1.21.11 and from 1.22.0-0 before 1.22.4. A third-party dependency list alone is insufficient context. Our review implication is to identify the toolchain used to build the deployed binary and whether affected methods process relevant inputs. An affected toolchain match does not prove reachable exploitation.

Source: Go vulnerability report GO-2024-2887. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • exploitable reachability established by toolchain version alone
  • the local toolchain assumed to match a deployed binary
  • a new binary scan or customer-specific assessment

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

GoCardless confirmed late failure

Question: Does a GoCardless confirmed or paid-out payment prove an irreversible collection?

GoCardless documents late failure when delayed bank reporting corrects a payment previously marked confirmed. Its lifecycle also includes chargebacks returning funds under the applicable Direct Debit rules. A paid-out or confirmed state therefore needs continued outcome reconciliation rather than being treated as irrevocable finality.

Source: GoCardless: Overview of payment statuses. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a GoCardless confirmed or paid-out payment prove an irreversible collection?

Buyer evidence still required

  • payment ID
  • bank-debit scheme
  • full event history
  • payout association
  • later failure or chargeback entries

Review inference: An order is fulfilled and the receivable permanently closed on confirmation. Later bank corrections may leave the order unreconciled. Adds direct-debit delayed bank-failure reporting after apparent confirmation, distinct from card capture rejection. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer irreversibility, settled revenue or absence of future reversal from a lifecycle snapshot.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Late failure

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer irreversibility, settled revenue or absence of future reversal from a lifecycle snapshot.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GoCardless payout net components

Question: Does a GoCardless payout amount identify which invoices were paid?

GoCardless payouts net credits and debits, including payments, fees, refunds and chargebacks. The Payout Items API exposes each item's signed amount, type and relevant resource links. The net payout amount alone cannot attribute every included payment or adjustment to an invoice.

Source: GoCardless: Reconciling payouts. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a GoCardless payout amount identify which invoices were paid?

Buyer evidence still required

  • payout ID
  • all payout items
  • item types and signs
  • payment/mandate links
  • buyer invoice mapping

Review inference: A finance agent allocates a bank payout to open invoices by total alone. Fees or old chargebacks can be assigned to the wrong invoices. Adds payout composition and payment/adjustment linkage for reconciliation, not a requested split instruction. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer invoice-level settlement from a net payout total or count fee and reversal items as new collections.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Using the Payout Items API

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer invoice-level settlement from a net payout total or count fee and reversal items as new collections.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GoCardless refund returned credit

Question: Does a refund debit in a GoCardless payout prove the customer received the refund?

GoCardless defines refund_funds_returned as a credit when a previously deducted refund failed to reach the customer. The original refund debit therefore needs reconciliation with later return items and their payment or mandate links before concluding the customer received funds.

Source: GoCardless: Reconciling payouts. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a refund debit in a GoCardless payout prove the customer received the refund?

Buyer evidence still required

  • refund and payout references
  • original debit
  • later return credits
  • linked payment or mandate
  • customer receipt if required

Review inference: An operator closes a customer refund when it is deducted from a payout. A failed refund can return to the merchant while the customer remains unpaid. Adds the specific returned-refund ledger item used in GoCardless payout reconciliation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse customer-receipt claims based only on the payout debit; reconcile subsequent refund-return evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. refund_funds_returned

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse customer-receipt claims based only on the payout debit; reconcile subsequent refund-return evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GoCardless retry reason mandate gate

Question: Can every failed GoCardless payment be retried as an insufficient-funds failure?

The partner collection guide limits the described manual retry path to insufficient-funds failures, up to three retries, and separately directs cancelled or expired mandates to a new mandate. Failure reason and mandate state are necessary inputs; a generic Failed status is not a retry permission.

Source: GoCardless: Partner integration: collecting payments. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can every failed GoCardless payment be retried as an insufficient-funds failure?

Buyer evidence still required

  • failure cause
  • mandate state
  • prior retry count
  • payment method
  • any scheduled Success+ retry

Review inference: An agent retries every failed debit with a standard recovery rule. It may retry an invalid mandate or duplicate another scheduled attempt. Adds failure-class and mandate preconditions for retry, rather than uncertain-response idempotency. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat every failed payment as retriable or issue a competing retry without reconciling scheduled recovery; confirm applicability of the partner flow.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Retries

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat every failed payment as retriable or issue a competing retry without reconciling scheduled recovery; confirm applicability of the partner flow.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

GoCardless submitted cancellation boundary

Question: Can a GoCardless payment still be cancelled after submission to the banking system?

GoCardless distinguishes pending submission, where cancellation is available, from submitted, where it says the payment can no longer be cancelled through that flow. The guide directs a customer seeking cancellation at that point to their bank. A local cancellation request is not evidence that the banking instruction stopped.

Source: GoCardless: Overview of payment statuses. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a GoCardless payment still be cancelled after submission to the banking system?

Buyer evidence still required

  • payment ID
  • current state
  • submission timestamp
  • cancellation response
  • subsequent bank or payment outcome

Review inference: A buyer cancels an order after the collection instruction has left the platform. The debit may still proceed despite the local order cancellation. Adds the GoCardless bank-submission cutoff for cancellation, whereas the existing Adyen reversal record concerns its separate card-payment reversal lifecycle. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse completed cancellation from a local request after submission; do not infer a refund or bank stop from this documentation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Submitted

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse completed cancellation from a local request after submission; do not infer a refund or bank stop from this documentation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Google ADK: Documentation MCP scope

Question: Does ADK’s documentation MCP server deploy or run an application agent?

Google ADK describes a documentation MCP server that lets coding tools search and read ADK documentation. This is a documentation-access integration. It does not itself establish deployment, execution or authorisation of an application agent.

Source: Coding with AI — Agent Development Kit. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • application deployment through the documentation server
  • agent execution capability
  • application tool authorisation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google ADK: Language support versus feature evidence

Question: Can an agent use an ADK feature matrix as proof that a feature is supported in its chosen language?

The ADK repository warns that its feature matrix is AI-generated from documentation examples and may be inaccurate. The reviewed table covers Python and Java; it is not a complete inventory of every ADK runtime. Use it as a pointer, then check the feature-specific documentation and installed package. A language listing or missing example does not establish feature parity or absence.

Source: Google ADK documentation repository: Feature Support Matrix. Documentation checked 2026-10-12; no deployment validation is claimed.

Claim boundaries
  • the generated matrix as verified runtime evidence
  • feature parity across languages
  • a missing example proving no support

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google ADK: Machine-readable documentation

Question: What do Google ADK’s machine-readable documentation files provide?

Google ADK documents an llms.txt index and an llms-full.txt documentation export for coding assistants. These provide access to documentation; they do not demonstrate that an assistant has read the current material, generated correct code or validated a deployment.

Source: Coding with AI — Agent Development Kit. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • assistant ingestion of current documentation
  • correct generated implementation
  • tested deployed agent

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Calendar: Event creation and conference readiness differ

Question: Does creating a Calendar event prove its meeting link is ready?

Conference generation can be asynchronous: the immediate event response may show pending before conference creation succeeds and entry points appear. The guide also requires a full event sync before enabling conference support in an existing client that stores events locally, to avoid losing existing conference data.

Source: Google Calendar: Create events. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does creating a Calendar event prove its meeting link is ready?

Buyer evidence still required

  • Event identity and requested conference operation.
  • Conference creation status and returned entry points.
  • Existing-client synchronization state before conference support changes.

Suggested review condition: Do not present a pending conference as a usable meeting link.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Event identity, conference request, result status and client synchronization.

Optional saved evidence: Save the difference between a scheduled event and a confirmed conference.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Cloud agent platform transparency component scope

Question: Does platform-level Access Transparency support cover every AI serving component?

The captured Agent Platform guide lists component and workload exclusions, including custom-container inference or explanation, AutoML forecasting resources, RAG Engine, Vector Search 2.0 and Vizier. General support for the platform does not establish coverage of a deployment using an excluded path. Product names and support must be checked against the dated source.

Source: Google Cloud: Access Transparency in Agent Platform. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does platform-level Access Transparency support cover every AI serving component?

Buyer evidence still required

  • actual service and component versions
  • serving path and custom-container use
  • dated support matrix
  • required access evidence

Review inference: A buyer relies on platform branding when assessing support-access evidence for its RAG service. The deployed component can lie outside the stated logging coverage. Adds provider-specific component exclusions; the existing record concerns Databricks Gateway versus legacy endpoints. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not apply a platform-wide logging claim to an excluded component or infer observed deployment behaviour from this review.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Limitations of Access Transparency in Agent Platform

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not apply a platform-wide logging claim to an excluded component or infer observed deployment behaviour from this review.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Google Cloud budgets: Alerts-only and spend-cap modes differ

Question: Does every Google Cloud budget automatically pause services at its threshold?

Current documentation distinguishes Alerts-only budgets from Spend cap budgets. Alerts-only settings do not impose a cap. Spend-cap state and supported project scope require separate inspection, and usage-reporting delays remain relevant. A generic budget screenshot cannot identify the enforcement mode or prove an absolute instantaneous ceiling.

Source: Google Cloud budgets and spending limits. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every configured Google Cloud budget automatically enforces the amount.

Buyer evidence still required

  • Budget mode, project scope and current cap status.
  • Supported services and enforcement configuration for that mode.
  • Usage delay and observed pause or resumption evidence.

Suggested review condition: Identify the actual budget mode before claiming enforced spending limits.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Budget mode, project scope, cap state and reporting delay

Optional saved evidence: Save the current mode and enforcement evidence behind an agent spending boundary.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Cloud IAM: Deny rules have permission and exception scope

Question: Does a Google Cloud IAM deny policy automatically block every action by a named principal?

Google documents supported permissions and permission groups for deny policies, with optional principal and permission exceptions and scoped conditions. A deny policy must match the requested permission and principal in its effective resource context. Its mere presence is not evidence of a universal block.

Source: Google Cloud IAM deny policies. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a Google Cloud IAM deny policy automatically block every action by a named principal?

Buyer evidence still required

  • The operation permission and resource hierarchy.
  • The effective deny rules and supported permission mapping.
  • Principal exceptions, permission exceptions and conditions.

Suggested review condition: Do not conclude an action is denied when permission support, resource scope or an exception is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The operation permission and resource hierarchy. The effective deny rules and supported permission mapping. Principal exceptions, permission exceptions and conditions.

Optional saved evidence: An authority reviewer must reconcile the requested operation with the actual deny-rule coverage and exceptions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A live effective-permission verdict or complete coverage of all Google Cloud services
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Cloud keys: Expiry, rotation and workload continuity

Question: Do user-managed Google Cloud service-account keys expire automatically by default?

Google states that keys created through IAM have no expiry by default and remain valid until deleted. Expiry and rotation are separate lifecycle choices, and expiry can interrupt workloads. Request the actual key inventory and replacement process rather than assuming automatic expiration proves credential hygiene.

Source: Google Cloud service account key lifecycle. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Service-account keys automatically expire and therefore need no lifecycle review.

Buyer evidence still required

  • Key inventory, age and configured expiry without disclosing secret values
  • Documented replacement and removal process
  • Evidence that dependent workloads use the intended current credential

Suggested review condition: Do not infer expiry or completed rotation from a policy statement alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck key creation, rotation records and workload authentication changes.

Optional saved evidence: Save the lifecycle evidence checklist for a supplier service identity.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Cloud Logging: A sink defines destination coverage

Question: Does an empty destination log search prove that no matching Google Cloud action occurred?

Log sinks route entries according to inclusion and exclusion filters. Google also distinguishes intercepting and non-intercepting aggregated routing. A destination search reflects the applicable routing scope, not necessarily every entry received elsewhere in the hierarchy.

Source: Google Cloud Logging: Routing and storage overview. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does an empty destination log search prove that no matching Google Cloud action occurred?

Buyer evidence still required

  • Relevant sink filters and intercepting status.
  • Origin resource and destination mapping.
  • Query window and evidence from other applicable sinks.

Suggested review condition: State the destination coverage before drawing a negative conclusion from a log search.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Resource hierarchy, aggregated sinks, filters, destination and query window.

Optional saved evidence: Does an empty destination log search prove that no matching Google Cloud action occurred?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Cloud logs: Query deduplication does not guarantee export uniqueness

Question: Does a duplicate-free Google Cloud log query prove that exported records are unique?

Google Cloud Logging uses matching project, timestamp and insertId values to remove duplicates within a single query result. It explicitly gives no deduplication guarantee for log exports. Export consumers therefore need their own declared identity and duplicate-handling basis.

Source: Google Cloud Logging: LogEntry. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a duplicate-free Google Cloud log query prove that exported records are unique?

Buyer evidence still required

  • Record identifiers and timestamps.
  • Retrieval path and export configuration.
  • Consumer deduplication and retained raw counts.

Suggested review condition: Do not transfer query-result uniqueness assumptions to exported evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Project, log timestamp, insertId and query or export path.

Optional saved evidence: Does a duplicate-free Google Cloud log query prove that exported records are unique?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Cloud pam delete active grant precondition

Question: Can deleting a PAM entitlement substitute for revoking its active grants?

Google's entitlement-management guide says an entitlement with active grants cannot be deleted; those grants must first be revoked. An attempted entitlement deletion is not evidence that active temporary access was removed.

Source: Google Cloud: View, update and delete PAM entitlements. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can deleting a PAM entitlement substitute for revoking its active grants?

Buyer evidence still required

  • entitlement ID
  • active grant inventory
  • revoke outcomes
  • entitlement deletion outcome

Review inference: An offboarding operator tries to remove the entitlement as a shortcut to grant revocation. Temporary access can remain while the administrative delete is blocked. Covers PAM's deletion precondition, a different operation and platform from IAM session cutoffs. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse completed-access-removal claims based only on an entitlement delete request; reconcile the grants first.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. To delete the entitlement

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse completed-access-removal claims based only on an entitlement delete request; reconcile the grants first.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Google Cloud pam edit grant version boundary

Question: Does editing a PAM entitlement update existing grants and all pending approvals uniformly?

Google documents that updated entitlement configuration applies to grants requested after the update. Changes to an approver list also affect undecided requests. Adding or removing approval levels, or changing required approval counts, requires no grants awaiting approval. The reviewed documentation marks these structural controls as preview; multi-level or multiple-approval workflows also require Security Command Center Premium or Enterprise. Bind the request time, decision state and precise type of change to the governing configuration.

Source: Google Cloud: View, update and delete PAM entitlements. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does editing a PAM entitlement update existing grants and all pending approvals uniformly?

Buyer evidence still required

  • entitlement revisions
  • grant request time
  • approval state
  • approver-list versus structural change
  • applicable service tier and preview availability

Review inference: A governance operator changes a temporary-access policy while requests are pending. The wrong revision or approver set can be attributed to an elevated action. The existing record concerns IAM policy update integrity; this review concerns PAM configuration applicability to old, new and undecided grants. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not apply all configuration changes retrospectively, treat approver-list changes as approval-level or count changes, or assume preview controls are available in every tier.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Keep the following things in mind when updating an entitlement

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not apply all configuration changes retrospectively, treat approver-list changes as approval-level or count changes, or assume preview controls are available in every tier.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Google Cloud pam policy capacity grant failure

Question: Does a PAM entitlement guarantee that a new temporary grant can be applied?

PAM adds time-bound IAM role bindings, and each active grant consumes IAM policy space. Google documents that new grant requests fail when the resource policy reaches its size limit. Entitlement configuration alone does not prove that a requested elevation was successfully installed.

Source: Google Cloud: PAM best practices. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a PAM entitlement guarantee that a new temporary grant can be applied?

Buyer evidence still required

  • resource policy size and current bindings
  • grant request and outcome
  • active grant inventory

Review inference: An incident workflow depends on just-in-time elevation on a heavily used resource. A validly configured escalation can fail when needed. Adds a documented grant-capacity failure mode rather than policy-version preservation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse active-authority claims without successful grant state and applicable policy evidence; do not infer success from entitlement existence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. IAM policy size limits

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse active-authority claims without successful grant state and applicable policy evidence; do not infer success from entitlement existence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Google Cloud pam revoke operation completion

Question: Does a returned PAM revoke operation establish completed grant removal?

The PAM revoke guide returns a long-running operation and directs callers to query its progress. Receipt of that operation, including an unfinished response, does not establish completed revocation. This review is limited to the guide's active-grant workflow; it does not resolve broader API-state eligibility.

Source: Google Cloud: Revoke Privileged Access Manager grants. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a returned PAM revoke operation establish completed grant removal?

Buyer evidence still required

  • grant ID and active state
  • operation name
  • final operation outcome
  • resulting grant and access state

Review inference: An offboarding agent logs the first revoke response as a completed removal. Unfinished or failed removal can be reported as complete. Adds asynchronous PAM operation reconciliation, not AWS issuance-cutoff semantics. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not close revocation on the initial operation response or infer propagation to every access path; verify completion and applicable downstream state.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. To check on the progress of a revoke operation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not close revocation on the initial operation response or infer propagation to every access path; verify completion and applicable downstream state.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Google Cloud transparency automation and notice exclusions

Question: Does an empty Access Transparency log rule out all Google access to customer content?

The reviewed exclusion list includes Google's standard automated systems, cases where notification is legally prohibited, access not targeting Customer Data, and specified public identifiers or resource names. Access Transparency is therefore a bounded personnel-access record, not a complete record of every processing operation.

Source: Google Cloud: Access Transparency exclusions. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an empty Access Transparency log rule out all Google access to customer content?

Buyer evidence still required

  • service support
  • access actor and mechanism
  • content type
  • applicable exclusions
  • other available access evidence

Review inference: A custody reviewer interprets an empty transparency export as no vendor processing. Excluded processing can be incorrectly ruled out. Adds enumerated provider-transparency exclusions, not telemetry sampling. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse universal no-access claims from log absence; this review cannot determine whether an excluded event actually occurred.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Access Transparency exclusions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse universal no-access claims from log absence; this review cannot determine whether an excluded event actually occurred.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Google Cloud transparency customer IAM access exclusion

Question: Does Access Transparency contain Google personnel activity authorised by the customer's own IAM policy?

Google excludes personnel access that the customer granted through IAM from Access Transparency and directs that activity to Cloud Audit Logs when enabled. Provider support-access reporting and customer-granted access therefore require different evidence paths.

Source: Google Cloud: Access Transparency exclusions. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Access Transparency contain Google personnel activity authorised by the customer's own IAM policy?

Buyer evidence still required

  • personnel grant and IAM scope
  • supported service
  • Cloud Audit Logs configuration
  • relevant access interval

Review inference: A customer grants support personnel access then checks only Access Transparency. Permitted support activity may be omitted from the reviewed evidence set. Adds Google's explicit division between customer-granted access and provider transparency logs. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not conclude no provider-personnel access from Access Transparency alone when customer IAM grants exist.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. You've granted the Google personnel access

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not conclude no provider-personnel access from Access Transparency alone when customer IAM grants exist.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Google Cloud: A permission probe has a declared scope

Question: Does projects.testIamPermissions produce a complete inventory of an agent identity's authority?

The Resource Manager method tests the caller against a specified project and explicit permission names. Wildcard permissions are not accepted. Its request scope must therefore be retained when interpreting the result; it is not a wildcard inventory of every possible action.

Source: Google Cloud Resource Manager: projects.testIamPermissions. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does projects.testIamPermissions produce a complete inventory of an agent identity's authority?

Buyer evidence still required

  • Caller identity and selected project.
  • Explicit permission list sent to the method.
  • Returned permissions and separately defined action inventory.

Suggested review condition: Describe only the tested permission set and resource; do not generalise it to all authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Authenticated caller, project identifier and exact permissions requested.

Optional saved evidence: Does projects.testIamPermissions produce a complete inventory of an agent identity's authority?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Cloud: Data Access defaults and viewer permissions

Question: Can a missing Google Cloud Data Access result mean the event was never logged?

Google documents that Data Access logging usually needs explicit enablement, with service-specific exceptions including parts of BigQuery. Viewing those logs also needs appropriate permissions. Check service settings, inherited configuration, exemptions and viewer access before interpreting an empty result.

Source: Google Cloud Data Access logging defaults, exemptions and viewer permissions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A general log viewer can establish complete Data Access history without checking configuration.

Buyer evidence still required

  • Applicable audit configuration and inherited settings for the service
  • Exempted principals and routing/retention evidence
  • Viewer permissions and the exact search scope

Suggested review condition: Do not turn absent results into an absence-of-access claim without capture and viewer evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck audit configuration, exemptions, service exceptions and viewer roles.

Optional saved evidence: Preserve the enablement and visibility conditions used in a cloud-data review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Cloud: Disabling a key leaves issued credentials distinct

Question: Does disabling a Google service-account key revoke tokens already issued from it?

Google states that disabling a service-account key does not revoke short-lived credentials already issued from it. The guide distinguishes the key from the service account represented by those credentials. A key-disabled result therefore does not by itself establish a completed access cutoff.

Source: Google Cloud: Disable and enable service account keys. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does disabling a Google service-account key revoke tokens already issued from it?

Buyer evidence still required

  • Key identity and disable timestamp.
  • Service-account identity and issued-credential exposure.
  • Authorised containment decision and observed access after it.

Suggested review condition: Do not declare all access revoked using key-disable evidence alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Key, represented service account, issued credentials and authorised response.

Optional saved evidence: Preserve the distinction between disabling a key and ending effective access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Developer Knowledge MCP: Documentation access and API identity

Question: Does Google Developer Knowledge MCP inspect or change my Google Cloud resources?

The documented tools search, fetch and answer questions from developer documentation. API keys or OAuth-based credentials support access and project attribution; that is separate from inspecting a buyer Cloud deployment. A documentation answer cannot establish actual resource state or a control being enabled.

Source: Google Developer Knowledge MCP credentials and retrieval. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Google hosted documentation service

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Google publishes the Developer Knowledge MCP endpoint.

Documented by publisher. Google Developer Knowledge MCP credentials and retrieval

Purpose

Search and retrieve developer documentation and answer documentation questions.

Documented by publisher. Google Developer Knowledge MCP credentials and retrieval

Read capability

Documentation search results, full documents and generated documentation answers.

Documented by publisher. Google Developer Knowledge MCP credentials and retrieval

Write capability

No cloud-resource mutation is described in the reviewed tool inventory.

Documented by publisher. Google Developer Knowledge MCP credentials and retrieval

Authentication

API-key and OAuth/ADC approaches are documented.

Documented by publisher. Google Developer Knowledge MCP credentials and retrieval

Permission surface

API restrictions and project attribution need configuration; ADC can require service-usage permission.

Documented by publisher. Google Developer Knowledge MCP credentials and retrieval

Data leaving the environment

Queries are sent to Google and returned material enters the client context.

Review inference. Google Developer Knowledge MCP credentials and retrieval

Failure modes to consider

Expired credentials, missing project permissions and documentation applicability can affect results.

Review inference. Google Developer Knowledge MCP credentials and retrieval

Unknowns and applicability

Buyer API restrictions, billing project and actual Cloud configuration are not inspected.

Not established

Suggested refusal or clarification condition

Do not substitute documentation retrieval for resource-state evidence or send secrets as search text.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Authentication prerequisites, project attribution and tool definitions.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve which answer came from documentation and which deployment facts remain unverified.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Drive changes: Removal can mean lost access

Question: Does removed=true in a Google Drive change record prove that the underlying file was deleted?

The Drive API v3 Change resource uses removed when a file or shared drive leaves the changes list, including through deletion or loss of access. The marker does not distinguish those causes by itself. An agent can lose visibility while data remains, so offboarding and deletion findings need additional evidence.

Source: Drive API v3 Change resource. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does removed=true in a Google Drive change record prove that the underlying file was deleted?

Buyer evidence still required

  • Change identity, timestamp and caller context
  • Permission changes and independently supported deletion records
  • Residual file or shared-drive inventory available to its owner

Review inference: A visibility loss cannot alone support a deletion conclusion.

Suggested review condition: Refuse confirmed deletion when the only evidence is removed=true from a caller that may have lost access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Removal cause and physical retention are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid misclassifying disconnected data as deleted during agent offboarding.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified erasure or a unique deletion cause from the removed flag
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Drive: An incomplete search is not absence

Question: Can an agent treat no Google Drive search match as proof a document does not exist?

Drive can mark searches across large combined corpora as incomplete. The publisher advises checking incompleteSearch and narrowing the corpus when results were omitted. Query scope and returned fields therefore matter; no match alone does not establish absence from the organisation.

Source: Drive: Search for files and folders. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an agent treat no Google Drive search match as proof a document does not exist?

Buyer evidence still required

  • Selected corpus and query filters.
  • Returned incompleteSearch value and pagination state.
  • Known document control cases within the permitted scope.

Suggested review condition: Do not assert organisational absence from an incomplete or narrowly scoped search.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Caller identity, corpus, query and result completeness.

Optional saved evidence: Preserve what a document search actually covered before relying on a negative result.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Drive: Folder inheritance and limited access

Question: Can a file-level sharing change remove access inherited from a Drive folder?

Google explains that folder access is inherited by contained files and subfolders. Reducing inherited access requires addressing the folder-level permission; limited-access folders provide a separate boundary. Review the path and explicit grants rather than interpreting a single file setting in isolation.

Source: Google Drive inherited and limited folder access. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Changing one file permission removes all inherited folder access.

Buyer evidence still required

  • Parent-folder access and relevant group membership
  • Direct grants and limited-access folder configuration
  • Observed access for the intended identities after changes

Suggested review condition: Require inherited-permission evidence before claiming file access is removed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck folder moves, group membership and limited-access changes.

Optional saved evidence: Save the inheritance checks behind a document-access procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google IAM: Every impersonation hop needs authority

Question: Does a Google service-account delegation list itself grant permission to impersonate the final account?

A delegated short-lived-credential request needs the required Service Account Token Creator grants along the chain. The delegates array specifies intermediate service accounts in order; it excludes the initiating caller and final target. Listing an account does not supply the required grant.

Source: Create short-lived credentials for multiple service accounts  |  Identity and Access Management (IAM)  |  Google Cloud Documentation. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a Google service-account delegation list itself grant permission to impersonate the final account?

Buyer evidence still required

  • Caller and final target identities.
  • Ordered intermediate service accounts.
  • Token Creator assignments for every hop.

Suggested review condition: Do not accept a delegation declaration when an intermediate grant or chain order is missing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Caller and final target identities. Ordered intermediate service accounts. Token Creator assignments for every hop.

Optional saved evidence: Review each delegation edge rather than only the final agent identity.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Live token issuance, effective permissions or automatic refresh of expiring credentials
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google IAM: Preserving conditions during policy updates

Question: Can an agent overwrite a conditional Google IAM policy without preserving its version and etag?

Google directs API and client-library callers working with IAM Conditions to use the version 3 policy representation and preserve its etag. Without the etag, IAM permits overwriting a version 3 policy with version 1, which removes the conditions. A successful write alone does not establish preserved restrictions.

Source: Google Cloud IAM: Understanding allow policies. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an agent overwrite a conditional Google IAM policy without preserving its version and etag?

Buyer evidence still required

  • Complete retrieved policy, including conditions, representation version and etag.
  • Exact proposed policy diff and setIamPolicy request.
  • Returned policy and review of retained restrictions after the write.

Suggested review condition: Decline a condition-preservation claim without the full version 3 read and matching update evidence; re-read and review any stale or incomplete policy before another write.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Complete retrieved policy, including conditions, representation version and etag. Exact proposed policy diff and setIamPolicy request. Returned policy and review of retained restrictions after the write.

Optional saved evidence: Automated grant edits can unintentionally remove time or context restrictions even when the intended change concerns a different member.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified preservation of buyer policy conditions or proof that concurrent grant changes were safely reconciled
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google OAuth testing refresh-token expiry

Question: Can an external Google OAuth app assume the same refresh-token lifetime in testing and production?

Google documents seven-day refresh-token expiry for an external app in Testing, except when requested scopes are limited to the specified name, email and profile subset including OpenID equivalents. Other revocation and expiry causes remain relevant. Leaving Testing does not establish that a refresh token will remain valid indefinitely.

Source: Using OAuth 2.0 to Access Google APIs | Authorization | Google for Developers. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an external Google OAuth app assume the same refresh-token lifetime in testing and production?

Buyer evidence still required

  • OAuth consent publishing status and user type
  • Requested scopes and token issuance time
  • Observed refresh outcome and reauthorization procedure

Review inference: Record publishing status, requested scopes and provider expiry conditions when designing recovery.

Suggested review condition: Do not promise indefinite access from production status or apply the testing exception to broader scopes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The app’s settings and current token validity are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid an integration failure caused by undocumented testing-to-production token assumptions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A guaranteed perpetual refresh token in production
  • The app’s settings and current token validity are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google OAuth: Revocation can span a user's project grant

Question: Does revoking one Google OAuth token only disconnect that one client?

Google documents revocation of the associated user's project authorization across previously granted scopes and tokens for clients under that project. This can be broader than a single client. The guide also notes that full effect may take time after a successful response.

Source: Google: OAuth 2.0 web server applications. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does revoking one Google OAuth token only disconnect that one client?

Buyer evidence still required

  • Associated user and OAuth project/client inventory.
  • Combined scopes and tokens affected by that authorization.
  • Revocation response and post-revocation checks.

Suggested review condition: Confirm the authorised revocation scope and dependent clients before treating it as a single-client action.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. User authorization, project clients, combined scopes and observed revocation effect.

Optional saved evidence: Preserve the scope and dependencies of an OAuth disconnect decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Vault: Gemini export counts and errors need reconciliation

Question: Does receiving a Gemini app Vault export ZIP establish that all matching conversation evidence was exported?

Vault provides Gemini conversation XML, a result-count CSV and an error XML file. AccountStatus can indicate complete, partial or failed retrieval; SuccessCount counts prompt-response pairs. The ZIP alone does not resolve account errors or establish coverage beyond the search and supported data scope.

Source: Google Vault export contents. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does receiving a Gemini app Vault export ZIP establish that all matching conversation evidence was exported?

Buyer evidence still required

  • The search scope, accounts and interval.
  • Conversation XML and result-count CSV.
  • The error XML and any documented re-export resolution.

Suggested review condition: Do not declare a complete export while accounts, pair counts or retrieval errors remain unreconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The search scope, accounts and interval. Conversation XML and result-count CSV. The error XML and any documented re-export resolution.

Optional saved evidence: An evidence custodian must reconcile requested accounts and prompt-response pairs with the export error reports.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • All historical conversations, buyer-specific export validation or legal evidentiary sufficiency
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Vault: User and licence preservation scope

Question: Does a Vault retention arrangement survive deletion of the user or required licence?

Vault requires appropriate licences for users and administrators. The overview warns that deleting a user or required licence can irreversibly purge data and remove Vault availability. Retention rules act on supported service data; an export or retained matter should not be assumed to cover an unverified offboarding change.

Source: Google Vault overview. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A retention arrangement guarantees data remains available after any offboarding action.

Buyer evidence still required

  • User status and applicable Vault licences.
  • Retention or hold scope and supported services.
  • Preservation evidence before the proposed lifecycle change.

Suggested review condition: Confirm the documented user and licence lifecycle before relying on retained evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Account lifecycle, licences, supported services and preservation scope.

Optional saved evidence: Save the documented preservation questions before a supplier account-exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google Workspace: Delegation scopes and impersonated users

Question: Does Google Workspace domain-wide delegation give a service account unlimited direct access to user data?

Google describes domain-wide delegation as authority to impersonate a specified user for API calls, bounded by authorized OAuth scopes and the permissions of that user. Review the delegated client, scopes and selected user. Approval to delegate is distinct from permission for every proposed collection or action.

Source: Google Workspace domain-wide delegation and impersonation. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Domain-wide delegation establishes unlimited direct access to all Workspace data.

Buyer evidence still required

  • Admin delegation record for the client and scopes
  • Selected user and relevant resource permissions
  • Approved operation and evidence of effective access

Suggested review condition: Require the intended user, scopes and task purpose before relying on a domain-wide delegation claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck delegation grants, impersonated identity, resource access and service-account custody.

Optional saved evidence: Preserve the impersonation and scope boundary behind a Workspace integration review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Google-provided FOCUS export table expiry

Question: Does the Google-provided FOCUS export retain every historical billing row indefinitely?

Google's setup guidance assigns a two-year time-to-live to Google-provided FOCUS export tables. This constraint is specific to that export arrangement and is not a statement that all Cloud Billing tables expire after two years. Preserve the relevant data under the buyer's approved retention process if a longer reconstruction window is required.

Source: Google Cloud Billing billing-setup documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Infrastructure, Metering & FinOps Verification

Evidence to request before relying on this claim

Claim to check: Does the Google-provided FOCUS export retain every historical billing row indefinitely?

Buyer evidence still required

  • Exact FOCUS export arrangement
  • Table expiry settings
  • Approved retention copies and reconstruction period

Review inference: Arrange independently retained history before the documented two-year TTL removes it. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Apply only to the Google-provided FOCUS table described in the capture, not all standard/detailed billing exports or buyer-owned copies. Retention is not a legal compliance guarantee.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck FOCUS export and data retention in Google Cloud Billing billing-setup documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Apply only to the Google-provided FOCUS table described in the capture, not all standard/detailed billing exports or buyer-owned copies. Retention is not a legal compliance guarantee.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Grafana MCP: Query access and write restrictions

Question: Does a read-only monitoring connector prevent every database query or disclosure?

Grafana's MCP repository separates disabling writes from disabling queries. Read-only mode removes raw SQL query tools unless explicitly re-enabled, while other queries can remain. Query-free mode removes query tools but is not a universal block on every datasource path. Credential and datasource privileges still need inspection. A read-only label therefore does not establish a no-query or no-disclosure boundary.

Source: Grafana MCP credential, query and write controls. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Grafana's official MCP package operated against Grafana Cloud or a local instance; deployment flags, transport and credentials must be identified.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Grafana publishes the server package; the deployer operates the MCP process.

Documented by publisher. Grafana MCP credential, query and write controls

Purpose

Inspect observability resources and perform enabled Grafana operations.

Documented by publisher. Grafana MCP credential, query and write controls

Read capability

Dashboards, datasource queries and observability metadata through enabled tools.

Documented by publisher. Grafana MCP credential, query and write controls

Write capability

Dashboard and alert operations can mutate state; raw SQL authority also depends on datasource credentials.

Documented by publisher. Grafana MCP credential, query and write controls

Authentication

Service-account tokens authenticate Grafana API access and inherit the account's permissions.

Documented by publisher. Grafana service account authority

Permission surface

Write and query flags differ; service accounts are organization-bound, with role-based access.

Documented by publisher. Grafana MCP credential, query and write controls; Grafana service account authority

Data leaving the environment

Query results leave the datasource for the MCP/client workflow even if resource writes are disabled.

Review inference. Grafana MCP credential, query and write controls

Failure modes to consider

Re-enabling SQL with write-capable credentials, or treating query-free mode as a complete datasource barrier.

Review inference. Grafana MCP credential, query and write controls

Unknowns and applicability

Installed version, flags, transport protection, service account, datasource rights and client recipients.

Not established

Suggested refusal or clarification condition

For metadata-only work, resolve alternate datasource paths and credential rights before allowing queries.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck installed release, query/write flag combinations and datasource credential rights before expanding access.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the distinction between write prevention, query exposure and datasource authority for monitoring-tool approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Graph notifications: Reconnecting does not restore missed changes

Question: Does restoring a Microsoft Graph subscription recover every notification missed during an outage?

Graph lifecycle events distinguish reauthorization, removed subscriptions and missed notifications, with resource-specific support. Changes during a delivery pause can be lost from notification delivery; after restoring the subscription the application must separately fetch missed changes, such as through supported delta queries.

Source: Microsoft Graph: Lifecycle notifications. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does restoring a Microsoft Graph subscription recover every notification missed during an outage?

Buyer evidence still required

  • Subscribed resource and lifecycle-event support.
  • Pause interval and subscription recovery evidence.
  • Separate resynchronization or delta result for the gap.

Suggested review condition: Keep the observation window incomplete until missed changes are reconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Resource type, subscription interval and separate change reconciliation.

Optional saved evidence: Save the gap and recovery basis behind event-driven agent decisions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

gVisor: Limits of host protection

Question: Does gVisor's security model eliminate every host-side risk?

gVisor aims to reduce host system-interface exposure through mediation and restriction. Its documented scope does not remove every attack vector or replace a secure surrounding architecture.

Source: gVisor Security Model. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • elimination of all host risks
  • protection against every side channel
  • security certification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

gVisor: OCI runtime integration

Question: Can gVisor integrate with container tooling through runsc?

gVisor provides the runsc OCI runtime for container integration. Runtime integration support does not establish that a particular image or workload is compatible.

Source: What is gVisor?. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • all container images are compatible
  • a working installation in a named environment
  • unchanged workload performance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

gVisor: Sentry interface boundary

Question: Does a sandboxed workload directly use the host kernel's full interface through gVisor?

gVisor's Sentry handles workload system calls in userspace and mediates necessary host interaction. Workload compatibility and the configured access boundary need separate assessment.

Source: Introduction to gVisor security. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • complete Linux compatibility
  • absence of all host interaction
  • a measured performance advantage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

gVisor: Workload isolation

Question: What isolation model does gVisor provide for agent-executed code?

gVisor documents an application-kernel sandbox between workloads and the host. This supports a design description, not a security guarantee for a specific agent deployment.

Source: Introduction to gVisor security. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • immunity to escape or compromise
  • security assurance for a customer deployment
  • permission to run arbitrary code

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

H1.3: Generalisation boundary

Question: Does H1.3 locked-seed validation establish external generalisation?

H1.3 is a positive locked-seed validation summary with explicit boundaries. Its public source excludes external generalisation.

Derived from BDAS H1.3 — Locked-Seed Validation. No new experiment or validation is claimed.

Claim boundaries
  • external generalisation
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

H1.3: Mechanism disclosure boundary

Question: Does H1.3 validation justify disclosing protected mechanisms?

H1.3 supports bounded locked-seed validation. Its public source excludes mechanism disclosure, including through paid request handling.

Derived from BDAS H1.3 — Locked-Seed Validation. No new experiment or validation is claimed.

Claim boundaries
  • mechanism disclosure
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

H2.1: Pump diagnostics boundary

Question: Does H2.1 establish broad pump diagnostic capability?

H2.1 is publicly recorded as safe but not selective. Its source excludes broad pump diagnostic capability.

Derived from BDAS H2.1 — Hydraulic Pump Safe But Not Selective. No new experiment or validation is claimed.

Claim boundaries
  • broad pump diagnostic capability
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Harness MCP: Default targets are separate from access restrictions

Question: Do Harness MCP default organisation and project settings prevent other targets?

The README describes those settings as defaults used when calls omit identifiers; agents can discover and supply other targets. Read-only mode separately blocks mutating operations and defaults off. Hosted OAuth and local credentials also differ. Review effective permissions rather than treating defaults as an access allowlist.

Source: Harness MCP access and read-only mode. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Local/self-hosted MCP and managed hosted alternative

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Harness publishes the server and offers a managed hosted option.

Documented by publisher. Harness MCP access and read-only mode

Purpose

Inspect and manage Harness platform resources.

Documented by publisher. Harness MCP access and read-only mode

Read capability

Permitted project, pipeline and other selected resource data.

Documented by publisher. Harness MCP access and read-only mode

Write capability

Create, update, delete and execute operations unless read-only restrictions apply.

Documented by publisher. Harness MCP access and read-only mode

Authentication

Local single-user token or mode-specific per-user credentials; hosted OAuth.

Documented by publisher. Harness MCP access and read-only mode

Permission surface

Read-only controls and credentials are separate from default targets.

Documented by publisher. Harness MCP access and read-only mode

Data leaving the environment

Configuration, execution and resource data can reach the client.

Review inference. Harness MCP access and read-only mode

Failure modes to consider

A default project may be mistaken for a hard scope restriction.

Review inference. Harness MCP access and read-only mode

Unknowns and applicability

Buyer roles, deployment mode and actual target are unverified.

Not established

Suggested refusal or clarification condition

Confirm effective target permissions before relying on default identifiers.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Mode-specific authentication, read-only defaults and target selection.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the distinction between convenience defaults, credential authority and write restrictions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Hosted MCP sticky approval identity

Question: Can an OpenAI hosted-MCP always-approve decision transfer to a same-named tool on another server label?

The pinned Python SDK identifies a hosted-MCP sticky decision by the combination of server_label and tool name. An always-approve decision does not approve a same-named tool on another label. A persistent always-approve or always-reject decision requires both identity fields to be non-empty.

Source: OpenAI Agents Python human-in-the-loop guide, v0.24.0. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an OpenAI hosted-MCP always-approve decision transfer to a same-named tool on another server label?

Buyer evidence still required

  • Exact installed version, provider variant and effective non-secret configuration
  • Relevant pending-call identifiers, declared arguments and decision provenance without secrets
  • Application-owned review policy and independently observed outcomes where needed

Review inference: Bind standing decisions to the documented server-label/tool tuple; labels do not authenticate the remote operator, version, endpoint or effective permissions. The Agent Framework record describes name-based standing approval inheritance. OpenAI hosted MCP uses a compound identity with two non-empty fields, so the older provider-specific conclusion cannot be transferred. Operational review inference; no deployment outcome was observed.

Suggested review condition: Bind standing decisions to the documented server-label/tool tuple; labels do not authenticate the remote operator, version, endpoint or effective permissions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Approval decisions / HostedMCPTool sticky decisions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Bind standing decisions to the documented server-label/tool tuple; labels do not authenticate the remote operator, version, endpoint or effective permissions.
  • The tuple does not distinguish changed implementations presented under the same label and name, and does not describe local MCP approval identity.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Hosted skill_reference versus local path/byte identity

Question: Can a hosted OpenAI skill_reference identify the skill used by local shell execution?

The documented hosted shell accepts uploaded skill_reference attachments; local shell instead uses skill files at paths in the runtime controlled by the application.

Source: OpenAI primary documentation: openai skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a hosted OpenAI skill_reference identify the skill used by local shell execution?

Buyer evidence still required

  • execution mode
  • local paths or hosted reference
  • file hashes
  • runtime adapter

Review inference: Can a hosted OpenAI skill_reference identify the skill used by local shell execution? A hosted skill ID does not bind local file bytes; capture the local bundle and runtime mapping separately. Hosted skill_reference versus local path/byte identity. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A hosted skill ID does not bind local file bytes; capture the local bundle and runtime mapping separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Use skills with local shell mode

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A hosted skill ID does not bind local file bytes; capture the local bundle and runtime mapping separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP content and representation digest scope

Question: Does a Repr-Digest on an HTTP range or HEAD response prove that all representation bytes were delivered?

RFC 9530 defines Content-Digest over actual message content and Repr-Digest over the entire selected representation. HTTP methods and ranges can make those scopes differ, including partial responses and HEAD. A representation digest therefore does not establish that the complete representation was delivered in this message; inventory the bytes and semantics actually received.

Source: IETF RFC 9530. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Repr-Digest on an HTTP range or HEAD response prove that all representation bytes were delivered?

Buyer evidence still required

  • HTTP method, status and range
  • Selected representation metadata
  • Actual content bytes and digest type

Review inference: Select Content-Digest versus Repr-Digest for a partial or HEAD evidence response. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Content and selected representation are distinct byte scopes; digest presence does not prove full content was delivered.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 2; 3 in IETF RFC 9530 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Content and selected representation are distinct byte scopes; digest presence does not prove full content was delivered.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP digest preferences and actual validation

Question: Does requesting an HTTP digest guarantee that the peer supplied and validated the preferred integrity evidence?

RFC 9530 treats Want-Content-Digest and Want-Repr-Digest as hints. A peer may use another algorithm or omit the digest without a protocol error. Applications can impose stronger requirements, and recipients may otherwise ignore supplied digests. Requested preferences do not establish delivery or validation of the integrity evidence required by a buyer.

Source: IETF RFC 9530. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does requesting an HTTP digest guarantee that the peer supplied and validated the preferred integrity evidence?

Buyer evidence still required

  • Sent integrity preferences
  • Received digest fields and algorithms
  • Application validation policy and result

Review inference: Decide whether a requested digest algorithm guarantees that a response supplied or validated integrity evidence. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. The peer may ignore preferences without a protocol error; application policy and actual digest validation must establish the requirement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 4 in IETF RFC 9530 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The peer may ignore preferences without a protocol error; application policy and actual digest validation must establish the requirement.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP multiple-signature acceptance policy

Question: Can a verifier accept an HTTP message because any one attached signature is valid?

RFC 9421 requires a verifier to account for the expected signers, rather than accepting any cryptographically valid signature attached to a message. Applications must also decide how invalid additional signatures affect acceptance: rejecting a message for any invalid signature can permit denial of service by injection. Key, algorithm and acceptance policy must be assessed together.

Source: IETF RFC 9421. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a verifier accept an HTTP message because any one attached signature is valid?

Buyer evidence still required

  • Expected signer/key set
  • All signature validation results
  • Any-valid or required-signature acceptance policy

Review inference: Decide which HTTP signatures satisfy an expected-signer policy when a message carries several signatures. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. A valid attacker signature is insufficient; any-valid versus all-valid policy and invalid-signature denial of service require explicit handling.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 7.2.6; 7.3.4 in IETF RFC 9421 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A valid attacker signature is insufficient; any-valid versus all-valid policy and invalid-signature denial of service require explicit handling.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP response signature request context

Question: Can a response signature using req be validated after the original request components have been discarded?

RFC 9421 permits a response signature to cover components from the triggering request using the req parameter. Those values are not repeated in the response, so the requester must retain the original components long enough to validate it. Proxy changes can prevent a match. A response signature alone does not reconstruct discarded request context.

Source: IETF RFC 9421. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a response signature using req be validated after the original request components have been discarded?

Buyer evidence still required

  • Original request components
  • Response Signature-Input with req flags
  • Intermediary transformations

Review inference: Retain the request components needed to validate a response signature using req. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. The signed response does not repeat original component values; proxy alterations and exact request context matter.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 2.4 in IETF RFC 9421 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The signed response does not repeat original component values; proxy alterations and exact request context matter.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP signature context behind a proxy

Question: Does successful signature verification behind a reverse proxy establish that the request targeted the correct service?

RFC 9421 warns that derived signature components must come from trusted context. A reverse-proxy deployment can use a configured external target URI, but a mistaken mapping may accept a request intended for another component. Signer and verifier must agree on the relevant message and authority; an arbitrary forwarded value is not trustworthy merely because it helps validation pass.

Source: IETF RFC 9421. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does successful signature verification behind a reverse proxy establish that the request targeted the correct service?

Buyer evidence still required

  • Trusted proxy configuration
  • External and internal target mapping
  • Component derivation and intended recipient

Review inference: Establish the trusted source of authority and target URI components across a reverse proxy. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Configured external context must match the intended recipient; an untrusted forwarded value can contaminate signature-base derivation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 7.4.3 in IETF RFC 9421 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Configured external context must match the intended recipient; an untrusted forwarded value can contaminate signature-base derivation.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP signature labels and covered meaning

Question: Does an HTTP signature label establish the signer's approval role?

RFC 9421 signature labels connect entries in Signature and Signature-Input, but are chosen when attaching the signature and are not covered by the signing process. An intermediary may relabel them. A name such as approved therefore does not establish an approval role; application-specific meaning must use suitable covered parameters and the expected signer policy.

Source: IETF RFC 9421. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an HTTP signature label establish the signer's approval role?

Buyer evidence still required

  • Signature and Signature-Input labels
  • Covered application parameters
  • Expected signer and role policy

Review inference: Distinguish an HTTP signature dictionary label from a signature-covered approval role. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Labels can be changed by intermediaries; application semantics need covered parameters and trusted signer policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 7.2.5 in IETF RFC 9421 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Labels can be changed by intermediaries; application semantics need covered parameters and trusted signer policy.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP signature replay controls

Question: Does a valid HTTP message signature prove that this request has not already been used?

RFC 9421 explains that a signature can remain valid when attached to another sufficiently similar message. Component coverage, a per-message nonce checked for repetition, and creation or expiry limits can help detect replay. The application must establish those controls; signature validity alone is not evidence of one execution or an idempotent business operation.

Source: IETF RFC 9421. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a valid HTTP message signature prove that this request has not already been used?

Buyer evidence still required

  • Covered components and message identity
  • Nonce uniqueness state
  • Creation/expiry acceptance policy

Review inference: Distinguish a valid HTTP signature from evidence that the request has not been replayed. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Require the application replay policy, nonce uniqueness and time-window checks; a timestamp alone is not exactly-once execution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 7.2.2 in IETF RFC 9421 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the application replay policy, nonce uniqueness and time-window checks; a timestamp alone is not exactly-once execution.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP signature required component coverage

Question: Does valid HTTP signature verification establish that every decision-relevant field was protected?

RFC 9421 requires applications to enforce their additional signature requirements, including required components. Unsigned portions of a message can be changed without invalidating the signature. A cryptographic pass is therefore insufficient when the application relies on an unsigned field or a component missing from its verification policy.

Source: IETF RFC 9421. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does valid HTTP signature verification establish that every decision-relevant field was protected?

Buyer evidence still required

  • Application required-component policy
  • Signature-Input covered components
  • Actual fields used for the decision

Review inference: Decide whether a valid HTTP signature covers every component required by the application. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Cryptographic validity alone does not protect unsigned fields or satisfy application coverage rules.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 3.2.1; 7.2.1 in IETF RFC 9421 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Cryptographic validity alone does not protect unsigned fields or satisfy application coverage rules.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP signed digest and actual content

Question: Does verifying a signature over Content-Digest alone establish the integrity of the received body?

RFC 9421 does not directly sign message content. A digest field can bind it indirectly, but the verifier must both verify the signature and recompute the digest against the received content. Otherwise substituted content can leave the signed digest field unchanged. Content-encoding changes can also change the digest and invalidate the existing signature.

Source: IETF RFC 9421. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does verifying a signature over Content-Digest alone establish the integrity of the received body?

Buyer evidence still required

  • Received content bytes and encoding
  • Digest field and hash algorithm
  • Signature coverage and recomputed digest

Review inference: Verify the received body against the signed digest before treating HTTP content as integrity checked. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Signature verification covers the digest field value, not automatic recomputation of the actual content; content encoding changes matter.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 7.2.8 in IETF RFC 9421 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Signature verification covers the digest field value, not automatic recomputation of the actual content; content encoding changes matter.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HTTP state-changing representation digest

Question: Does the representation digest on a state-changing request prove the final state of its target resource?

RFC 9530 ties Repr-Digest to representation data and metadata, not automatically to the target resource's final state. In a PATCH request it covers the patch document. A response can describe request status or a referenced resource; Content-Location can affect that interpretation, while Location alone does not. Establish the represented object before treating a digest as post-change evidence.

Source: IETF RFC 9530. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the representation digest on a state-changing request prove the final state of its target resource?

Buyer evidence still required

  • Method and representation metadata
  • Request or response represented object
  • Content-Location and independently observed final state

Review inference: Identify the representation covered by a digest on a state-changing request or its status response. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. A PATCH request digest covers the patch document, not the resulting target state; response representation metadata determines its digest scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck 3.1 in IETF RFC 9530 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A PATCH request digest covers the patch document, not the resulting target state; response representation metadata determines its digest scope.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

HubSpot MCP: CRM visibility and content publication

Question: What should an agent check before treating a CRM connector's search results as complete or allowing publication?

HubSpot's hosted MCP can read CRM content and perform permitted updates, including some publishing actions. Access depends on the user, subscription, granted tools and account configuration. With Sensitive Data enabled, the documented MCP restrictions block activity and conversation data. Missing results therefore do not establish that no records exist. New scopes require a renewed installation grant.

Source: HubSpot remote MCP data and permissions. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: HubSpot's remote account-data MCP; not the separate local developer MCP for building HubSpot apps.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

HubSpot operates the remote MCP service.

Documented by publisher. HubSpot remote MCP data and permissions

Purpose

Query CRM information and perform supported business-content changes.

Documented by publisher. HubSpot remote MCP data and permissions

Read capability

CRM and marketing data are available subject to account restrictions; Sensitive Data blocks activities and conversations.

Documented by publisher. HubSpot remote MCP data and permissions

Write capability

Supported tools update CRM objects and can create, edit or publish web content.

Documented by publisher. HubSpot remote MCP data and permissions

Authentication

The connector uses OAuth with PKCE.

Documented by publisher. HubSpot remote MCP data and permissions

Permission surface

User rights and installation grants apply; changed scopes require reinstalling to grant them.

Documented by publisher. HubSpot remote MCP data and permissions

Data leaving the environment

Customer information reaches the external client; minimize fields and check its recipients.

Review inference. HubSpot remote MCP data and permissions

Failure modes to consider

Mistaking blocked data for no data, publishing during analysis, or confusing local developer and remote CRM tools.

Review inference. HubSpot remote MCP data and permissions; HubSpot remote and developer MCP release distinctions

Unknowns and applicability

Sensitive Data setting, installed grants, subscription, inbox restrictions and client retention.

Not established

Suggested refusal or clarification condition

Withhold publication or CRM changes during analysis; label results incomplete when access is unresolved.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck installation grants, Sensitive Data configuration and tool availability after account or subscription changes.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the documented visibility and publication limits behind a CRM integration review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Hugging Face MCP: Discovery can extend into jobs and third-party tools

Question: Is Hugging Face MCP limited to searching public models and datasets?

The reviewed offering combines discovery with optional repository contributions, jobs, sandboxes and Space tools. Enabled capabilities depend on configuration. A Space introduces its own execution and data-handling context; authorising Hub search does not establish authority for every optional write or compute operation.

Source: Hugging Face MCP tools and account scope. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted Hub MCP with configurable tools and optional Spaces

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Hugging Face publishes the Hub server; selected Spaces may have other operators.

Documented by publisher. Hugging Face MCP tools and account scope

Purpose

Discover Hub resources and, when enabled, use selected operational tools.

Documented by publisher. Hugging Face MCP tools and account scope

Read capability

Model, dataset, paper, Space and documentation discovery.

Documented by publisher. Hugging Face MCP tools and account scope

Write capability

Optional repository contributions, job execution and sandbox file operations are described.

Documented by publisher. Hugging Face MCP tools and account scope

Authentication

Configuration is associated with a Hugging Face account; exact buyer credential scopes are unverified.

Not established. Hugging Face MCP tools and account scope

Permission surface

The selected tool set and underlying account or Space permissions require inspection.

Review inference. Hugging Face MCP tools and account scope

Data leaving the environment

Tool inputs may reach the Hub or a selected Space; identify the actual recipient.

Review inference. Hugging Face MCP tools and account scope

Failure modes to consider

Dynamic tool availability, remote execution and compute charges can change the task boundary.

Review inference. Hugging Face MCP tools and account scope

Unknowns and applicability

Enabled tools, private-resource access, Space operator and costs are unknown.

Not established

Suggested refusal or clarification condition

Require separate authority for writes, compute and disclosure to an unfamiliar Space.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Enabled tools, Space ownership, credentials and compute terms.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve which optional tools and recipients were authorised for the intended workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

I1: Independent replication boundary

Question: Does the I1 development pass establish independent replication?

The I1 public source records development progression. It lists independent replication as not demonstrated.

Derived from BDAS I1 — Development Pass. No new experiment or validation is claimed.

Claim boundaries
  • independent replication
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

I2: Holdout reservation versus performance

Question: Does I2 holdout reservation demonstrate holdout performance?

The I2 public source establishes holdout-control posture. It explicitly excludes holdout performance; reservation by itself is not a scored result.

Derived from BDAS I2 — Holdout Reserved and Hashed. No new experiment or validation is claimed.

Claim boundaries
  • holdout performance
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

IAM changes: Acknowledgement and propagation differ

Question: Does an accepted IAM policy update prove the new permission is effective everywhere immediately?

IAM documents eventual consistency across replicated services and caches. An accepted change can take time to become visible. The buyer needs effective-access evidence for the intended operation; neither an immediate denial nor a successful configuration response alone proves the final permission state.

Source: IAM troubleshooting and eventual consistency. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An accepted IAM change is immediately enforced everywhere.

Buyer evidence still required

  • Change identifier and intended permission.
  • Affected service and identity.
  • Subsequent effective-access observation.

Suggested review condition: Do not retry a consequential operation blindly while permission state is uncertain.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. IAM change, affected identity, service and propagation evidence

Optional saved evidence: Save the distinction between configuration acknowledgement and observed authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

IAM notprincipal boundary denial

Question: Can a NotPrincipal Deny reject an IAM role despite an intended exclusion?

AWS warns that a resource policy using NotPrincipal with Deny always denies IAM principals with permissions boundaries, regardless of the NotPrincipal values. It recommends a PrincipalArn condition approach instead. An exclusion in that policy form is therefore insufficient evidence that a bounded role can still use the resource.

Source: Amazon Web Services: IAM permissions boundaries. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a NotPrincipal Deny reject an IAM role despite an intended exclusion?

Buyer evidence still required

  • complete resource policy
  • principal ARN
  • attached permissions boundary
  • intended exception

Review inference: A platform operator adds a boundary to an agent role previously exempted from a resource denial. A supposedly preserved exception can become an operational outage. Adds the specific NotPrincipal-Deny incompatibility that can defeat a named exception; the existing record covers general boundary and resource-grant interactions. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse an access-preservation claim based only on a NotPrincipal exclusion when the principal has a boundary; effective access remains untested.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. NotPrincipal

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse an access-preservation claim based only on a NotPrincipal exclusion when the principal has a boundary; effective access remains untested.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

IAM role recreation principal binding

Question: Does recreating an IAM role preserve every trust policy that named its ARN?

AWS converts a role ARN in a trust policy's Principal element to the role's unique principal ID. Deleting and recreating the role breaks that binding. An aws:PrincipalArn condition is not converted in this way, so a condition using the same role ARN can continue to match the recreated role. The two policy forms require different offboarding and restoration checks.

Source: Amazon Web Services: IAM Principal policy element. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does recreating an IAM role preserve every trust policy that named its ARN?

Buyer evidence still required

  • role ARN and unique principal ID
  • trust-policy Principal and Condition fields
  • deletion and recreation timeline

Review inference: An operator replaces a delegated execution role while reusing its name. Trust may unexpectedly fail or survive the replacement. The existing review distinguishes resource grants and boundary limits; this decision concerns identity continuity across role deletion and recreation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer either restored trust or complete revocation from a reused role name. Inspect each policy form and its current principal binding.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. IAM role principals

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer either restored trust or complete revocation from a reused role name. Inspect each policy form and its current principal binding.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

IAM role revocation: Existing sessions and new assumptions differ

Question: Does revoking active IAM role sessions prevent the role from being assumed again?

The documented operation adds a deny policy for temporary credentials issued before a cutoff time. It does not by itself remove the ability to obtain later sessions. Review the trust relationship and assumption permissions separately from invalidating existing sessions.

Source: AWS role session revocation. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Revoking sessions permanently disables all access through the role.

Buyer evidence still required

  • Revocation cutoff and attached deny policy.
  • Role trust policy and current assumption permissions.
  • Evidence covering both old-session denial and new-session issuance.

Suggested review condition: Do not treat a session cutoff as permanent role disablement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Role trust, assumption grants, revocation time and session inventory

Optional saved evidence: Retain the distinction between cancelling current sessions and closing future access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

IAM validation: Policy checks and effective authority

Question: Does a clean IAM policy-validation result prove the deployed role has only intended access?

Policy validation checks grammar and AWS best-practice findings. It does not itself execute the buyer workflow or establish the combined effect of every deployed grant. A separate custom check can compare new access with a baseline; AWS still calls for testing new or edited policies before production use.

Source: IAM Access Analyzer policy validation. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A policy with no validation findings is a completed effective-access assessment.

Buyer evidence still required

  • Exact validated policy and check type.
  • All deployed permission sources and intended tasks.
  • Positive and negative operational access evidence.

Suggested review condition: Keep static validation separate from effective-authority and workflow testing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Policy version, validator mode, baseline, deployed grants and intended operations.

Optional saved evidence: Save an evidence-bound interpretation of policy-check output.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Ignored custom frontmatter and experimental allowed-tools versus enforced policy

Question: Can a custom Agent Framework SKILL.md field establish an enforced review policy?

The documented parser rejects certain malformed recognised fields but ignores unknown top-level fields. The allowed-tools field is experimental and support can vary across implementations.

Source: Microsoft primary documentation: ms skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a custom Agent Framework SKILL.md field establish an enforced review policy?

Buyer evidence still required

  • exact frontmatter
  • recognised field list
  • runtime version
  • effective approval policy

Review inference: Can a custom Agent Framework SKILL.md field establish an enforced review policy? Do not rely on an unrecognised policy key or experimental declaration as enforced permission; require the consumer's interpretation. Ignored custom frontmatter and experimental allowed-tools versus enforced policy. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not rely on an unrecognised policy key or experimental declaration as enforced permission; require the consumer's interpretation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Unknown top-level fields are ignored

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not rely on an unrecognised policy key or experimental declaration as enforced permission; require the consumer's interpretation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Immutable memory correction requires delete/re-add, with old/new identity linkage

Question: Can a Mem0 immutable memory be corrected with an ordinary update?

Mem0 documents immutable memories as requiring delete and re-add rather than update. Managed and OSS interfaces report the rejected update differently.

Source: Mem0 primary documentation: mem0 update. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Mem0 immutable memory be corrected with an ordinary update?

Buyer evidence still required

  • immutable status
  • original ID
  • rejected update
  • delete/add receipts
  • replacement ID

Review inference: Can a Mem0 immutable memory be corrected with an ordinary update? Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes. Immutable memory correction requires delete/re-add, with old/new identity linkage. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Immutable memories must be deleted and re-added

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not report correction complete from an attempted update; preserve the old/new identity link and require both operation outcomes.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto command alignment warnings

Question: Does successful in-toto verification establish that every reported command exactly matched expected_command?

The in-toto 1.0.0 specification describes expected_command as a suggested command and says a mismatch should produce a warning rather than verification failure. It also warns that command text can be forged after key compromise, including through environment changes. A passing artifact verification therefore does not establish exact command execution or a trustworthy runtime environment.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does successful in-toto verification establish that every reported command exactly matched expected_command?

Buyer evidence still required

  • Signed layout and reported link command
  • Verifier warnings and artifact-rule results
  • Independent execution and environment evidence

Review inference: Separate artifact-policy acceptance from exact-command execution evidence. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse exact-command execution assurance from verification success alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual command execution and host integrity were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual command execution and host integrity were not observed.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto delegated sublayout boundaries

Question: Does a parent in-toto layout directly receive every intermediate artifact from a verified sublayout?

The in-toto 1.0.0 specification represents a verified sublayout to its parent using the materials of the first sublayout step and products of the last. The parent rules apply to that boundary representation while sublayout verification checks the delegated steps. The parent summary therefore is not an inventory of every intermediate artifact or every inspection result within the delegated chain.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a parent in-toto layout directly receive every intermediate artifact from a verified sublayout?

Buyer evidence still required

  • Parent and signed sublayout definitions
  • Complete delegated link and inspection evidence
  • Boundary summary and parent rule results

Review inference: Retain delegated evidence when a review needs more than the parent boundary summary. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse full intermediate-artifact coverage from the parent summary alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual delegated execution and completeness of retained sublayout evidence are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual delegated execution and completeness of retained sublayout evidence are unknown.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto layout expiry and verifier time

Question: Can a correctly signed in-toto layout remain trusted after its expiry date?

The in-toto 1.0.0 specification says clients must not trust expired layout metadata and verifies expiry against the system date. A valid signature does not override that expiry check. A reliance record therefore needs the selected layout expiry and verifier clock context; it cannot infer current policy freshness from signature validity alone.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a correctly signed in-toto layout remain trusted after its expiry date?

Buyer evidence still required

  • Layout expiry and signature
  • Verifier time and clock assurance
  • Approved current layout and validation result

Review inference: Check policy freshness separately from signature integrity. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse current layout trust from signature validity without a valid expiry check.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual verifier clock and current owner policy are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual verifier clock and current owner policy are unknown.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto MATCH and explicit rejection

Question: Does an in-toto MATCH rule by itself fail verification when artifact hashes differ?

The in-toto 1.0.0 MATCH algorithm consumes source artifacts only when corresponding destination names and hashes match. Missing counterparts or unequal hashes remain unconsumed. The specification identifies DISALLOW and REQUIRE as the rules that can stop rule processing, so a MATCH non-match must be interpreted with the rest of the ordered policy rather than assumed to be an automatic rejection.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an in-toto MATCH rule by itself fail verification when artifact hashes differ?

Buyer evidence still required

  • Source and destination artifact maps
  • MATCH prefixes and hash comparisons
  • Subsequent rules and final unconsumed queue

Review inference: Check that failed artifact linkage reaches an explicit rejection condition. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse enforced artifact continuity from a MATCH rule without the closing policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual artifact origin and complete policy execution remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual artifact origin and complete policy execution remain unverified.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto MODIFY and intended changes

Question: Does an in-toto MODIFY rule prove that a required business or security fix was implemented?

The in-toto 1.0.0 specification defines MODIFY through artifact presence in both materials and products with different hashes. That structural condition records a content change, not the intended meaning or correctness of the change. A passing MODIFY check therefore needs separate acceptance evidence before it supports a claim that a particular defect or business requirement was resolved.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an in-toto MODIFY rule prove that a required business or security fix was implemented?

Buyer evidence still required

  • Material and product identities and hashes
  • Specified change requirement
  • Independent acceptance or test result

Review inference: Separate content-change evidence from acceptance of the intended change. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse semantic correctness or defect-remediation assurance from a changed hash alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual change correctness and security effect were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual change correctness and security effect were not verified.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto ordered artifact consumption

Question: Can a later in-toto DISALLOW rule reject an artifact already consumed by an earlier ALLOW rule?

The in-toto 1.0.0 specification applies artifact rules sequentially to a queue. An artifact successfully consumed by one rule is removed and cannot be consumed by later rules. DISALLOW tests remaining artifacts. Rule order therefore changes the effective boundary; a broad earlier allowance can remove an artifact before a later restriction examines it.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a later in-toto DISALLOW rule reject an artifact already consumed by an earlier ALLOW rule?

Buyer evidence still required

  • Exact ordered rule list
  • Artifact names and hashes
  • Per-rule consumption or equivalent verification trace

Review inference: Review the effective ordered rule policy rather than the presence of a deny clause. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse an effective-denial claim based solely on a later DISALLOW clause.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer rule execution or complete filesystem inventory was observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No buyer rule execution or complete filesystem inventory was observed.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto signed inspection reuse

Question: Can a signed in-toto sublayout inspection result be reused without rerunning its inspection command?

The in-toto 1.0.0 specification permits a sublayout inspection to be verified using presented link metadata signed with the same key that signed the sublayout. If that link is absent, the client must run the inspection while validating the sublayout. Acceptance can therefore rely on a previously signed result; it does not establish a fresh inspection of the current environment.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a signed in-toto sublayout inspection result be reused without rerunning its inspection command?

Buyer evidence still required

  • Sublayout and authorised signing key
  • Inspection link and signature verification result
  • Inspection execution time and current-environment requirements

Review inference: Distinguish signed inspection reuse from a newly performed check. This is a review judgment, not an observed deployment outcome.

Suggested review condition: Refuse a fresh-inspection claim from acceptance of a previously signed link.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Inspection freshness and current environment equivalence were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inspection freshness and current environment equivalence were not observed.
  • No verified business outcome, complete event capture, certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto step outputs and exit results

Question: Does in-toto default verification check a step return-value and its stdout or stderr?

The in-toto 1.0.0 specification treats byproducts as opaque information that default verification does not verify. It recommends retaining stdout, stderr and return-value for further scrutiny, including by inspections. This differs from an inspection executed during verification, whose non-zero return value halts validation. Signed step byproducts therefore require an explicit review before they support a successful-step conclusion.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does in-toto default verification check a step return-value and its stdout or stderr?

Buyer evidence still required

  • Step byproducts and expected success criteria
  • Verifier or inspection policy examining those fields
  • Correlated execution outcome evidence

Review inference: Do not mistake retained step diagnostics for an enforced success condition. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse a successful-step conclusion based solely on default in-toto verification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual step result and diagnostic truth were not independently verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The actual step result and diagnostic truth were not independently verified.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto unmatched artifact acceptance

Question: Does an in-toto artifact rule list reject every artifact that its explicit rules did not match?

The in-toto 1.0.0 rule-processing specification has an implicit ALLOW * at the end of each artifact rule list. It recommends an explicit trailing DISALLOW * to reject artifacts left unconsumed by earlier rules. Successful verification without that closing restriction can therefore accept additional reported materials or products outside the intended explicit matches.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an in-toto artifact rule list reject every artifact that its explicit rules did not match?

Buyer evidence still required

  • Ordered material and product rule lists
  • Link artifact inventory
  • Unconsumed artifacts and verification outcome

Review inference: Check whether artifact allowlisting is actually closed. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse a closed allowlist claim when unmatched artifacts are implicitly allowed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual rule coverage and unreported filesystem content are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual rule coverage and unreported filesystem content are unknown.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

in-toto verification can execute inspections

Question: Is in-toto layout verification always a read-only signature check?

The in-toto 1.0.0 specification defines inspections as commands run on the final product during verification. Their run field spawns a process on the verifying system and produces inspection metadata before artifact rules are checked. A verification plan containing inspections therefore needs an execution-authority and environment review; signature verification alone does not make those commands harmless or read-only.

Source: in-toto specification v1.0.0 — in-toto-spec. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is in-toto layout verification always a read-only signature check?

Buyer evidence still required

  • Trusted layout and inspection commands
  • Verifier execution permissions and filesystem scope
  • Isolation policy and authorised inspection effects

Review inference: Assess inspection commands before executing a supplied verification layout. This is a review judgment, not an observed execution or deployment result.

Suggested review condition: Refuse a read-only verification classification without reviewing inspections.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No inspection command was executed by INDEX or assessed for safety here.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No inspection command was executed by INDEX or assessed for safety here.
  • No verified business outcome, complete event capture, deployment certification or authority to act.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Individual memory/source-message deletion versus whole-profile scope

Question: Does deleting one Cloudflare memory establish deletion of its whole profile?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The HTTP API distinguishes namespace, profile, session and individual-memory deletion. Its individual-memory description removes that memory and source messages linked to it, rather than asserting complete profile erasure.

Source: Cloudflare primary documentation: cloudflare memory api. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting one Cloudflare memory establish deletion of its whole profile?

Buyer evidence still required

  • exact deletion endpoint
  • namespace/profile/session/memory IDs
  • response
  • residual representations

Review inference: Does deleting one Cloudflare memory establish deletion of its whole profile? Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation. Individual memory/source-message deletion versus whole-profile scope. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Delete a memory

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Match the deletion target to the intended custody claim; independent exports, downstream outputs and wider profile contents require separate evidence. Private beta access and current feature applicability require separate confirmation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Infisical MCP: Tool restrictions and secret-value masking

Question: Does a read-only Infisical tool list keep secret values out of model context?

Read tools can return values. The README documents a separate masking option that defaults off and still returns metadata when enabled. A tool allowlist limits exposed operations, while identity scope limits underlying access. Review all three before claiming that the connector hides secrets.

Source: Infisical MCP secret operations. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official local Infisical MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Infisical publishes the MCP server.

Documented by publisher. Infisical MCP secret operations

Purpose

Secret and project operations through Infisical APIs.

Documented by publisher. Infisical MCP secret operations

Read capability

Secret values and metadata, unless values are masked.

Documented by publisher. Infisical MCP secret operations

Write capability

Secret changes, project setup and member invitations.

Documented by publisher. Infisical MCP secret operations

Authentication

Machine universal authentication or a personal/machine access token.

Documented by publisher. Infisical MCP secret operations

Permission surface

Optional tool allowlist and value masking complement identity scope.

Documented by publisher. Infisical MCP secret operations

Data leaving the environment

Secret metadata remains visible even with value masking.

Review inference. Infisical MCP secret operations

Failure modes to consider

Read-only tools can disclose values when masking is unset.

Review inference. Infisical MCP secret operations

Unknowns and applicability

Buyer identity scope and selected host are unverified.

Not established

Suggested refusal or clarification condition

Require explicit value-handling approval before unmasked secret reads.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Masking defaults, allowlist enforcement and new secret tools.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve which control limits operations, which limits identity scope and which masks returned values.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Instrumentation scope and remote tool identity

Question: Does an OpenTelemetry instrumentation scope identify the vendor of the remote tool being called?

OpenTelemetry instrumentation scope identifies the logical software unit that emits telemetry, using a name and optional version, schema URL and attributes. When an instrumentation library emits telemetry for another library, the scope identifies the instrumentation library. It is not a standard attestation of the remote service vendor or tool operator.

Source: Instrumentation scope | OpenTelemetry. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an OpenTelemetry instrumentation scope identify the vendor of the remote tool being called?

Buyer evidence still required

  • Instrumentation scope and emitter library version
  • Remote endpoint, tool identity and operator evidence
  • Request-to-response linkage for the actual call

Review inference: Bind the remote endpoint, operator and tool version separately instead of treating the emitter's scope as supplier identity.

Suggested review condition: Do not accept a supplier-identity claim supported only by the instrumentation scope name.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The remote operator, recipient substitution and integrity of emitted scope fields are not independently established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Reconcile telemetry provenance with the actual supplier receiving an agent call.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified vendor identity or attestation of the called tool
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Intercom MCP: Regional access and internal notes

Question: Can an Intercom agent add a note when I only asked it to inspect a conversation?

Current Intercom documentation includes internal-note and article writes alongside conversation and contact reads. A note can affect conversation state. The service documents US and EU endpoints, with AU unsupported at review. Confirm the workspace region, consented permissions and exact task before allowing writes.

Source: Intercom MCP regional availability, article writes and scopes. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Regional hosted Intercom MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Intercom operates regional hosted MCP endpoints.

Documented by publisher. Intercom MCP regional availability, article writes and scopes

Purpose

Connect assistants to customer conversations, contacts and Help Center content.

Documented by publisher. Intercom MCP regional availability, article writes and scopes

Read capability

Reads conversations, contacts, companies and articles.

Documented by publisher. Intercom MCP regional availability, article writes and scopes

Write capability

Creates or updates articles and adds internal conversation notes.

Documented by publisher. Intercom MCP regional availability, article writes and scopes

Authentication

OAuth with consent or bearer API tokens is documented.

Documented by publisher. Intercom MCP regional availability, article writes and scopes

Permission surface

Internal notes require conversation-write permission; note authorship follows the authorising admin.

Documented by publisher. Intercom MCP regional availability, article writes and scopes

Data leaving the environment

Customer content reaches the assistant; endpoint region alone does not describe the client retention.

Review inference. Intercom MCP regional availability, article writes and scopes

Failure modes to consider

A note may reopen a conversation; wrong-region connections or missing pagination can mislead.

Review inference. Intercom MCP regional availability, article writes and scopes

Unknowns and applicability

Buyer consent, workspace region and client data policy are unverified.

Not established

Suggested refusal or clarification condition

Do not turn inspection into a note or article edit without approval; clarify region and subject first.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck after new scopes, regional support or note behaviour changes.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the dated region, note-side-effect and consent evidence behind a support-agent decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Invocation-log opt-out does not govern abuse-retention copies

Question: Does disabling Bedrock invocation logging establish zero retained prompts and outputs?

AWS documents model-specific abuse retention separately from optional invocation logging, including flagged-traffic and all-traffic cases with stated exceptions. For affected cross-Region models, retained inputs and outputs are stored in the processing destination Region. The exact model, programme eligibility and applicable date govern the documented exception.

Source: Amazon Bedrock abuse detection - Amazon Bedrock. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does disabling Bedrock invocation logging establish zero retained prompts and outputs?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Refuse zero-retention or source-region-only storage conclusions from invocation-log settings; require the exact model policy and account agreement, including expiry of any exception.

Suggested review condition: Refuse zero-retention or source-region-only storage conclusions from invocation-log settings; require the exact model policy and account agreement, including expiry of any exception.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. Model-specific abuse detection; stored in destination regions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse zero-retention or source-region-only storage conclusions from invocation-log settings; require the exact model policy and account agreement, including expiry of any exception.
  • A model or approved programme may have different documented treatment; do not generalize one model's retention interval to every Bedrock model.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Is ADK temp: state a private durable store for each delegated sub-agent

Question: Is ADK temp: state a private durable store for each delegated sub-agent?

Temporary state is scoped to the invocation and discarded when it completes. Parent and sub-agents sharing InvocationContext share the invocation ID and temp: state. It is neither a durable cross-invocation checkpoint nor automatically isolated per sub-agent.

Source: Google primary documentation: adk state. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is ADK temp: state a private durable store for each delegated sub-agent?

Buyer evidence still required

  • invocation ID
  • agent chain
  • state keys
  • required retention
  • intended isolation

Review inference: Is ADK temp: state a private durable store for each delegated sub-agent? Require an appropriate persisted scope and isolation evidence before using temp: values as recovery or agent-private evidence. State lifetime and sharing remain distinct even when updates use correct event persistence. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require an appropriate persisted scope and isolation evidence before using temp: values as recovery or agent-private evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Temporary Invocation State; Sub-Agents and Invocation Context

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require an appropriate persisted scope and isolation evidence before using temp: values as recovery or agent-private evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Is an ADK artifact named user:report.pdf isolated to the session that created it

Question: Is an ADK artifact named user:report.pdf isolated to the session that created it?

The user: filename prefix scopes an artifact to app_name and user_id, allowing access or updates across that user's sessions in the app. A plain filename is session-scoped. The prefix changes the evidence-sharing boundary and is not merely a display name.

Source: Google primary documentation: adk artifacts. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is an ADK artifact named user:report.pdf isolated to the session that created it?

Buyer evidence still required

  • app
  • user
  • session
  • artifact filename
  • namespace
  • access policy

Review inference: Is an ADK artifact named user:report.pdf isolated to the session that created it? Do not claim session isolation for a user-scoped artifact without separate controls. Concrete artifact namespace determines cross-session availability rather than language support. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not claim session isolation for a user-scoped artifact without separate controls.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Namespacing (Session vs. User)

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim session isolation for a user-scoped artifact without separate controls.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Is an AgentCore user-ID header equivalent to a validated user JWT

Question: Is an AgentCore user-ID header equivalent to a validated user JWT?

No. The header uses the user-ID token path and additionally requires InvokeAgentRuntimeForUser. The JWT path validates issuer, signature and expiry; AWS recommends it with a production identity provider.

Source: Amazon Web Services primary documentation: aws runtime oauth. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Is an AgentCore user-ID header equivalent to a validated user JWT?

Buyer evidence still required

  • auth mode
  • IAM permission
  • user-ID provenance
  • JWT validation

Review inference: Is an AgentCore user-ID header equivalent to a validated user JWT? Do not describe caller-supplied user labels as cryptographically proven user identity. Distinguishes caller identity labels from validated JWT ingress. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not describe caller-supplied user labels as cryptographically proven user identity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. cryptographic proof

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not describe caller-supplied user labels as cryptographically proven user identity.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Is an evaluator weekly cap an exact ceiling on every in-flight charge

Question: Is an evaluator weekly cap an exact ceiling on every in-flight charge?

LangSmith records spend after each evaluator run finishes. Concurrent in-flight runs can therefore push the final amount above the effective cap before new evaluations are paused.

Source: Track and limit evaluator spend. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is an evaluator weekly cap an exact ceiling on every in-flight charge?

Buyer evidence still required

  • effective cap
  • running evaluations
  • completion times
  • recorded cost

Review inference: Is an evaluator weekly cap an exact ceiling on every in-flight charge? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Evaluator post-run accounting differs from API-provider limit enforcement. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Retain in-flight completion and cost evidence before asserting an exact maximum.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. How enforcement works

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Retain in-flight completion and cost evidence before asserting an exact maximum.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Is embedded OCI descriptor data exempt from content verification

Question: Is embedded OCI descriptor data exempt from content verification?

The Base64 data field must contain the referenced content. Image 1.1.1 recommends checking decoded bytes against digest and size.

Source: OCI Content Descriptors. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Is embedded OCI descriptor data exempt from content verification?

Buyer evidence still required

  • descriptor data
  • decoded bytes
  • expected size and digest

Review inference: Accept a small artifact embedded in metadata. Require the missing evidence before accepting, retrying or closing the operation. Inline descriptor resolution differs from external bundle digest input. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not bypass validation for inline data or treat encoding as integrity evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Embedded Content;decoded data MUST be identical

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not bypass validation for inline data or treat encoding as integrity evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Is Service Bus session state removed after consuming every message

Question: Is Service Bus session state removed after consuming every message?

Session state remains until explicitly cleared, even after all messages are consumed. Microsoft advises clearing retained state when processing finishes.

Source: Azure Service Bus Enable FIFO with Sessions - Azure Service Bus | Microsoft Learn. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is Service Bus session state removed after consuming every message?

Buyer evidence still required

  • session identifier
  • GetState result
  • cleanup operation
  • retention requirements

Review inference: Check residual workflow data after draining a queue. Require the missing evidence before accepting, retrying or closing the operation. Session-level state differs from deferred messages outside ordinary receives. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not equate an empty session with erased workflow state or completed cleanup.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Message session state

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not equate an empty session with erased workflow state or completed cleanup.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Is the MCP client-authentication JWT itself the authorization grant

Question: Is the MCP client-authentication JWT itself the authorization grant?

The pinned specification uses grant_type=client_credentials with a JWT client_assertion for authentication. That differs from a JWT authorization grant. Record the actual grant type and authentication method.

Source: Model Context Protocol primary documentation: ext oauth client credentials. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Is the MCP client-authentication JWT itself the authorization grant?

Buyer evidence still required

  • grant_type
  • assertion type
  • supported auth methods
  • token response

Review inference: Is the MCP client-authentication JWT itself the authorization grant? Do not infer wire-format equivalence from JWT presence. Separates JWT client authentication from JWT authorization grant. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer wire-format equivalence from JWT presence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. JWT Authentication Example

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer wire-format equivalence from JWT presence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

JFrog MCP: Artifact discovery and administrative operations

Question: Can an agent treat the JFrog MCP server as an artifact search-only integration?

No. The published tool inventory includes repository configuration, access-token operations and other administrative capabilities as well as reads. A Platform Admin enables the integration, and experimental tools require a separate selection. Review the actual available tools and effective identity before authorising a search-only workflow.

Source: JFrog MCP enablement and privileges. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Platform-enabled server with separately selectable Beta tools

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

JFrog publishes the integration within the JFrog Platform.

Documented by publisher. JFrog MCP enablement and privileges; JFrog MCP tool capabilities

Purpose

Retrieve artifact and security context and perform supported platform operations.

Documented by publisher. JFrog MCP enablement and privileges; JFrog MCP tool capabilities

Read capability

Artifact metadata, repositories, security information and evidence records.

Documented by publisher. JFrog MCP enablement and privileges; JFrog MCP tool capabilities

Write capability

The inventory includes token, repository and other configuration-changing operations.

Documented by publisher. JFrog MCP enablement and privileges; JFrog MCP tool capabilities

Authentication

The enabling guide does not by itself establish the buyer authentication method or token scope.

Not established. JFrog MCP enablement and privileges; JFrog MCP tool capabilities

Permission surface

Platform activation and optional Beta availability are separate from authority for each operation.

Review inference. JFrog MCP enablement and privileges; JFrog MCP tool capabilities

Data leaving the environment

Tool parameters and returned platform data pass through the configured client and JFrog environment.

Review inference. JFrog MCP enablement and privileges; JFrog MCP tool capabilities

Failure modes to consider

An over-broad identity or optional tool can turn discovery into an administrative action.

Review inference. JFrog MCP enablement and privileges; JFrog MCP tool capabilities

Unknowns and applicability

Buyer permissions, enabled Beta tools and exact server version are unknown.

Not established

Suggested refusal or clarification condition

Decline token or configuration changes outside the expressly authorised task.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Platform tool inventory, Beta enablement and identity grants.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep a version-bound record of the search-versus-administration boundary.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

Jinja: Distinguish template authorship from template data

Question: Does a Jinja sandbox establish that agent-supplied templates are safe to execute?

The Jinja maintainer advisory for CVE-2025-27516 requires attacker control of template content and describes an attribute-filter path around sandbox handling. Supplying data to a fixed trusted template does not by itself establish that condition. Review who authors the template and which environment executes it. The frozen source records 3.1.6 as a fix, while the maintainer page's patched-version field lists none. Preserve that difference; an empty patch field does not prove no fix exists. A sandbox label alone is not evidence that arbitrary generated templates are safe.

Source: Jinja maintainer advisory: CVE-2025-27516. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • a sandbox label proving arbitrary-template safety
  • user-controlled variables equated with template authorship
  • empty patch metadata treated as proof of no remediation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Jira Cloud export: App data and automation need separate handling

Question: Does a Jira Cloud backup include third-party app data and automation configuration?

The export guide excludes third-party apps and app data, and automation flows require their own export/import. Cloud and Data Center destinations have different compatibility constraints. A backup file therefore needs an inventory and target-specific restore evidence before it supports a full migration claim.

Source: Jira Cloud data export. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The native backup captures the entire operational Jira environment.

Buyer evidence still required

  • Backup type and intended destination.
  • App-data and automation export inventory.
  • Restore validation and missing configuration list.

Suggested review condition: Require excluded-component evidence before approving migration completeness.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Backup type, destination, app data, automation and restore eligibility

Optional saved evidence: Preserve the excluded integrations and destination constraints behind a migration decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

jsonwebtoken: Check missing-key and algorithm defaults together

Question: Can a missing JWT verification key change how an unsigned token is handled?

The jsonwebtoken advisory for CVE-2022-23540 identifies three combined conditions in versions through 8.5.1: an unsigned token, no specified algorithms and a falsy verification key or secret. Under those conditions, verification can default to the none algorithm. The maintainer lists 9.0.0 as removing that default. Review missing-key handling and algorithm selection together rather than assuming one matching condition proves bypass. This is a historical library behaviour review, not verification of an application's authentication or of every issue fixed in a major upgrade.

Source: jsonwebtoken maintainer advisory: CVE-2022-23540. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • one matching condition promoted to a confirmed bypass
  • an application authentication test claimed from documentation
  • all upgrade behaviour or current library safety established

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kafka: Transaction guarantees at external destinations

Question: Do Kafka transactions make an agent's writes to an external service exactly once?

Kafka 4.3 describes exactly-once processing between Kafka topics using transactions and read-committed consumers. For an external destination, the consumer position must be coordinated with the stored output; cooperation from that destination is needed. Kafka transaction success alone does not extend its guarantee to an arbitrary external API or database write.

Source: Apache Kafka: Message delivery semantics. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Do Kafka transactions make an agent's writes to an external service exactly once?

Buyer evidence still required

  • Input topic offsets, transaction identifiers and consumer isolation configuration.
  • External destination write results and the mechanism coordinating them with progress.
  • Crash or retry recovery evidence linking stored output to the committed consumer position.

Suggested review condition: Decline end-to-end exactly-once claims without evidence that the external destination coordinates effects and progress.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Input topic offsets, transaction identifiers and consumer isolation configuration. External destination write results and the mechanism coordinating them with progress. Crash or retry recovery evidence linking stored output to the committed consumer position.

Optional saved evidence: A connector can replay or lose external effects despite transactional handling within the message system.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic atomicity with external APIs or verification of a buyer connector
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kestra flow MCP: Caller and workflow execution scope

Question: Do read-only annotations prevent a Kestra flow from changing systems?

Flow tools invoke registered Kestra workflows; their effects depend on the flow. The trigger's annotations are informational and do not change execution. Private and public server modes differ materially: a public server admits unauthenticated callers. Authentication choices and flow-scoped permissions depend on edition and configuration.

Source: Kestra flow MCP servers. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; deployed buyer configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Kestra publishes the workflow platform; deployment ownership varies.

Documented by publisher. Kestra flow MCP servers; Kestra flow tool trigger and annotations

Purpose

Expose registered workflows as agent-callable tools.

Documented by publisher. Kestra flow MCP servers; Kestra flow tool trigger and annotations

Read capability

Tool metadata and declared flow outputs.

Documented by publisher. Kestra flow MCP servers; Kestra flow tool trigger and annotations

Write capability

Invoked flows can perform their configured external actions.

Documented by publisher. Kestra flow MCP servers; Kestra flow tool trigger and annotations

Authentication

Private servers support edition-dependent Basic, API-token or OAuth modes.

Documented by publisher. Kestra flow MCP servers; Kestra flow tool trigger and annotations

Permission surface

Registered flows and applicable execution permissions determine the exposed surface.

Documented by publisher. Kestra flow MCP servers; Kestra flow tool trigger and annotations

Data leaving the environment

Inputs reach workflow tasks; outputs return to the client.

Review inference. Kestra flow MCP servers; Kestra flow tool trigger and annotations

Failure modes to consider

An inaccurate annotation or public server mode can create an unintended action surface.

Review inference. Kestra flow MCP servers; Kestra flow tool trigger and annotations

Unknowns and applicability

Actual flow effects, secret use, edition and effective permissions are unverified.

Not established

Suggested refusal or clarification condition

Review the flow and caller authority before invoking a changing workflow.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Server visibility, authentication support, trigger registrations and changed flow effects.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the distinction between tool descriptions and the actual workflow authority being approved.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Key Vault recovery: Soft delete and purge protection

Question: Does recovering a Key Vault restore every surrounding integration?

Soft deletion retains recoverable vault objects for a configured interval, and purge protection prevents early permanent removal during that interval. Recovering the vault does not automatically restore associated Azure RBAC assignments or Event Grid subscriptions. Recovery of secret material and recovery of the surrounding service are separate checks.

Source: Key Vault soft deletion and purge protection. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Soft-delete recovery restores the entire integrated service automatically.

Buyer evidence still required

  • Vault retention and purge-protection settings.
  • Recovered objects and required permissions.
  • RBAC and event-subscription restoration evidence.

Suggested review condition: Require integration verification before declaring the recovered service operational.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Vault identity, retention, purge protection, RBAC assignments and dependent event subscriptions.

Optional saved evidence: Save a recovery checklist grounded in the documented limits of vault restoration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kinesis: Partial producer retries and action order

Question: Can retrying a failed Kinesis PutRecords item change the intended action sequence?

PutRecords returns one result per submitted item in corresponding array order. A failed item does not stop subsequent items from being processed; failed items must be detected and resubmitted. PutRecords does not include SequenceNumberForOrdering. Consequently, request-array order alone cannot establish execution order after partial failures and later retries.

Source: Kinesis Data Streams: Producers using the API. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can retrying a failed Kinesis PutRecords item change the intended action sequence?

Buyer evidence still required

  • Original item order, partition keys and intended dependencies.
  • Per-item success or error results and sequence numbers across retry attempts.
  • Consumer-observed order and reconciliation of dependent business effects.

Suggested review condition: Decline preserved-action-order claims based only on batch position; reconcile successful later items and retried earlier items.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Original item order, partition keys and intended dependencies. Per-item success or error results and sequence numbers across retry attempts. Consumer-observed order and reconciliation of dependent business effects.

Optional saved evidence: Dependent agent actions may reach a stream out of the intended sequence even when every item eventually succeeds.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Global stream ordering, atomic batch publication or verified consumer execution
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

KMS disablement: Existing data keys and access

Question: Does disabling a KMS key immediately stop every read of the protected data?

Disabled customer-managed keys cannot perform KMS cryptographic operations, subject to eventual consistency. Resources already using data keys are not affected until they need KMS again, for example to decrypt a data key. Disabling the parent key is not evidence that every application has discarded plaintext or cached key material.

Source: AWS KMS enabling and disabling keys. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Disabling the KMS key immediately revokes all access to every protected resource.

Buyer evidence still required

  • Key state and change time.
  • Service use of data keys and caching.
  • Observed application access and retained plaintext scope.

Suggested review condition: Check the consuming service and cached material before claiming immediate universal revocation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Key type, service, data-key caching, transition time and retained copies.

Optional saved evidence: Preserve the distinction between a KMS state change and effective application access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kong Konnect MCP: Diagnostics and portal publication

Question: Is Kong Konnect MCP limited to reading gateway configuration?

The documented service combines configuration queries and diagnostics with Dev Portal content creation, editing and publication. PAT and system-account access follow the associated permissions. Optional KAi knowledge search uses additional model processing, so selected tools and data recipients need explicit review.

Source: Kong Konnect MCP server. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Publisher-hosted Konnect server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Kong operates the Konnect MCP service.

Documented by publisher. Kong Konnect MCP server

Purpose

Inspect API infrastructure and manage supported portal content.

Documented by publisher. Kong Konnect MCP server

Read capability

Configuration entities, analytics and diagnostic information.

Documented by publisher. Kong Konnect MCP server

Write capability

Debug sessions and Dev Portal content operations.

Documented by publisher. Kong Konnect MCP server

Authentication

Personal or system-account access token; client sign-in options vary.

Documented by publisher. Kong Konnect MCP server

Permission surface

Associated identity permissions and regional boundaries.

Documented by publisher. Kong Konnect MCP server

Data leaving the environment

Results reach the client; optional knowledge search adds Bedrock processing.

Review inference. Kong Konnect MCP server

Failure modes to consider

An inspection task can accidentally expand into publication.

Review inference. Kong Konnect MCP server

Unknowns and applicability

Buyer roles, KAi availability and data-recipient settings are untested.

Not established

Suggested refusal or clarification condition

Require explicit authority before publishing content or opening diagnostics.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Tools, role mapping, regional endpoint and optional model processing.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the scope and recipient decisions for API operations.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes additive RBAC grants

Question: Can a Kubernetes RBAC Role deny a permission granted through another RoleBinding?

Kubernetes RBAC permissions are purely additive and do not include deny rules. A restrictive Role does not cancel an allow supplied by another applicable RoleBinding or ClusterRoleBinding. Review all applicable RBAC grants; this statement does not describe every other authorization or admission mechanism that a cluster may use.

Source: Using RBAC Authorization | Kubernetes. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a Kubernetes RBAC Role deny a permission granted through another RoleBinding?

Buyer evidence still required

  • Subject identity and group membership
  • Applicable RoleBindings, ClusterRoleBindings and referenced rules
  • Other configured authorizers or admission controls relevant to the action

Review inference: Remove or narrow the effective grant at its source rather than treating an additional restrictive role as a subtraction.

Suggested review condition: Do not report an RBAC permission removed while another applicable binding still grants it.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Effective group membership, current bindings and other cluster controls were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Assess permission reduction without overlooking surviving additive grants.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A complete effective-access test or a claim that all Kubernetes authorization mechanisms lack denial
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes audit: Collection settings can leave gaps

Question: Does enabling Kubernetes auditing establish that every selected event reached storage?

Kubernetes documents event loss when a batch backend buffer overflows and exposes an audit error metric for export losses. Backend modes and size limits also shape collection. An enabled audit policy alone does not establish complete delivery.

Source: Kubernetes: Auditing. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does enabling Kubernetes auditing establish that every selected event reached storage?

Buyer evidence still required

  • Audit backend and batch-buffer configuration.
  • Audit event and export-error metrics for the window.
  • Destination receipt reconciliation and size-limit settings.

Suggested review condition: Keep delivery gaps unresolved until backend loss and destination evidence are reconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Audit backend mode, buffer settings, event volume and export-error observations.

Optional saved evidence: Does enabling Kubernetes auditing establish that every selected event reached storage?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes audit: Multiple stages can describe one request

Question: Do Kubernetes audit records with the same auditID necessarily represent duplicate delivery?

Kubernetes generates an auditID for each request and records the handling stage on each audit event. One request can generate events at different stages. ResponseStarted applies to long-running requests; it is distinct from ResponseComplete, so stage-aware correlation is necessary.

Source: Kubernetes: audit.k8s.io/v1 API. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Do Kubernetes audit records with the same auditID necessarily represent duplicate delivery?

Buyer evidence still required

  • Audit IDs and stages for the relevant request.
  • Policy stage omissions and request type.
  • Response status and completion evidence.

Suggested review condition: Group by request identity while retaining distinct stages; do not discard them as duplicate events.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Audit ID, event stage, request type and configured stage omissions.

Optional saved evidence: Do Kubernetes audit records with the same auditID necessarily represent duplicate delivery?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes audit: Rule order and recorded detail

Question: Does enabling Kubernetes auditing prove every request body is retained?

The first matching audit rule selects the level. None omits events; Metadata excludes bodies; Request and RequestResponse include different content. Policy and stage exclusions govern coverage, and omitting the API-server audit-policy flag means no policy-based events are logged. Export and retention are separate evidence.

Source: Kubernetes auditing. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An audit feature being enabled guarantees complete request and response evidence.

Buyer evidence still required

  • Effective ordered audit policy and omitted stages.
  • Backend configuration and delivery health.
  • Retained event samples for intended operations.

Suggested review condition: Confirm event and content coverage before relying on an audit export as complete.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. API-server configuration, ordered policy, event stages, backend and retained samples.

Optional saved evidence: Save the distinction between audit availability and usable evidential coverage.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes blocking strict audit stage

Question: Does any Kubernetes audit-backend failure automatically fail the API operation?

Kubernetes distinguishes batch, blocking and blocking-strict audit modes. The documented blocking-strict request-failure condition applies to audit logging failure at RequestReceived; ordinary blocking waits for event processing, and batch is asynchronous. A configured backend does not establish universal fail-closed behaviour for every audit stage.

Source: Kubernetes: Kubernetes auditing. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does any Kubernetes audit-backend failure automatically fail the API operation?

Buyer evidence still required

  • API-server version
  • backend mode
  • audit stages and policy
  • stage-specific errors
  • request outcome

Review inference: An audit owner claims every unauditable API action is refused. Later-stage or asynchronous audit failure can be misrepresented as action prevention. Adds the precise stage and mode required for request rejection, rather than merely documenting export loss. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not generalise the RequestReceived failure condition to every stage or mode, or infer rollback of an already performed action.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. blocking-strict

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not generalise the RequestReceived failure condition to every stage or mode, or infer rollback of an already performed action.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Kubernetes Jobs: Overlap during worker replacement

Question: Does a Kubernetes Job parallelism setting prevent replacement workers overlapping terminating Pods?

The Kubernetes v1.34 documentation explains that replacement on TerminatingOrFailed can start a new Pod while the old one is still terminating, temporarily exceeding parallelism and allowing two Pods for one indexed task. The Failed replacement policy waits for terminal failure. This controls replacement timing; it does not prove external effects occur only once.

Source: Kubernetes: Pod replacement policy for Jobs. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a Kubernetes Job parallelism setting prevent replacement workers overlapping terminating Pods?

Buyer evidence still required

  • Cluster version, Job replacement policy, parallelism and completion mode.
  • Old and replacement Pod identifiers, index values and termination timelines.
  • Worker outputs and external-effect reconciliation during the overlap period.

Suggested review condition: Decline exclusive-worker claims from parallelism alone without the replacement policy and Pod lifecycle evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Cluster version, Job replacement policy, parallelism and completion mode. Old and replacement Pod identifiers, index values and termination timelines. Worker outputs and external-effect reconciliation during the overlap period.

Optional saved evidence: Recovery can run overlapping workers even when the declared parallelism appears to allow only one.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exactly-once effects, external fencing or verification of the deployed cluster
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes RBAC: Permission to delegate permissions

Question: Can permission to edit Kubernetes roles or bindings be treated as ordinary configuration access?

Kubernetes restricts role creation to permissions the caller holds unless escalation is authorised. Binding creation similarly requires the referenced permissions or bind authority. These checks distinguish ordinary object edits from permission delegation.

Source: Kubernetes: Using RBAC authorization. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can permission to edit Kubernetes roles or bindings be treated as ordinary configuration access?

Buyer evidence still required

  • Role or ClusterRole rules and scope.
  • Caller bind and escalate permissions.
  • Proposed binding subjects and referenced role.

Suggested review condition: Review permission delegation explicitly before admitting a role-management action.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Cluster version, namespace scope, role rules and bind or escalate privileges.

Optional saved evidence: Can permission to edit Kubernetes roles or bindings be treated as ordinary configuration access?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes service tokens: Audience, lifetime and object binding

Question: Can an agent reuse a projected Kubernetes service-account token as a permanent general API credential?

Projected tokens obtained through TokenRequest are time-bound and normally bound to the Pod and Kubernetes API audience. Long-lived manually created tokens are a different mechanism. Credential review must identify token type, audience and object lifetime rather than assume all service-account tokens behave alike.

Source: Kubernetes service-account credentials. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every service-account token is a permanent general credential.

Buyer evidence still required

  • Token issuance mechanism and audience.
  • Expiry and bound object identity.
  • Effective service-account permissions.

Suggested review condition: Decline reuse outside the token's intended audience or lifetime.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token type, audience, expiry, object binding and RBAC

Optional saved evidence: Retain issuance, lifetime and audience boundaries for workload identity procurement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes TokenReview audience verification

Question: Does TokenReview authenticated=true establish that a Kubernetes token is valid for any service audience?

TokenReview accepts intended audience identifiers and reports compatible audiences in its status. A caller that requested audiences must check that a compatible audience was returned; when no audiences are requested the API-server audience is the default. An authenticated result alone does not establish validity for an arbitrary relying service.

Source: TokenReview | Kubernetes. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does TokenReview authenticated=true establish that a Kubernetes token is valid for any service audience?

Buyer evidence still required

  • TokenReview requested audiences
  • Returned authenticated status and audiences
  • Relying service’s intended audience identifier

Review inference: Retain both requested and returned audience evidence in the verification result.

Suggested review condition: Reject audience-specific authentication when no compatible returned audience is established.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual token and relying service configuration are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid accepting a token at a service for which it was not verified.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal audience validity from a positive authentication flag
  • The actual token and relying service configuration are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: A dry-run admission result is not a saved change

Question: Can an admitted Kubernetes dry-run request prove that the requested action took effect?

Kubernetes marks dry-run admission requests as not persisted. Webhooks with side effects are expected to avoid those effects for dry-run requests. The result describes the dry-run evaluation, not a completed resource mutation.

Source: Kubernetes: Dynamic Admission Control. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an admitted Kubernetes dry-run request prove that the requested action took effect?

Buyer evidence still required

  • Admission request and dryRun value.
  • Webhook sideEffects declaration.
  • Separate evidence of the persisted resource change.

Suggested review condition: Label dry-run evidence explicitly and do not substitute it for a real mutation outcome.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Request dryRun flag, webhook sideEffects declaration and resource observation.

Optional saved evidence: Can an admitted Kubernetes dry-run request prove that the requested action took effect?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: Cached authorisation and access changes

Question: Does changing a webhook authorisation policy guarantee every Kubernetes request immediately uses the new decision?

Kubernetes supports separate caching controls and lifetimes for authorised and unauthorised webhook responses. The configured cache can therefore affect when a fresh webhook decision is requested. Configuration syntax distinguishes disabling caching from setting a duration.

Source: Kubernetes: Authorization overview. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does changing a webhook authorisation policy guarantee every Kubernetes request immediately uses the new decision?

Buyer evidence still required

  • Authorised and unauthorised cache settings.
  • Policy activation and request timestamps.
  • Evidence of cache expiry or a fresh webhook evaluation.

Suggested review condition: Retain the applicable cache window when reviewing a revocation or policy-change claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. API server version, webhook authoriser configuration and policy-change timing.

Optional saved evidence: Does changing a webhook authorisation policy guarantee every Kubernetes request immediately uses the new decision?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: Caller identity and impersonated authority

Question: Do Kubernetes impersonation headers alone establish authority to act as another identity?

The API server authenticates the caller and checks impersonation privileges before evaluating the request with impersonated user information. The documented impersonate permission covers the kinds of attributes supplied, including user, group, UID and extra fields.

Source: Kubernetes: User Impersonation. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Do Kubernetes impersonation headers alone establish authority to act as another identity?

Buyer evidence still required

  • Original authenticated identity and impersonation headers.
  • Authorisation for requested identity attributes and configured mode.
  • Audit evidence linking caller, effective identity and action.

Suggested review condition: Preserve both identities and verify the configured impersonation mode; a header declaration alone is insufficient.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Cluster version, impersonation mode, original caller and requested identity attributes.

Optional saved evidence: Do Kubernetes impersonation headers alone establish authority to act as another identity?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: Missing policy parameters have a configured outcome

Question: Does a Kubernetes validating admission policy always reject requests when its parameter is missing?

For a binding with paramRef, parameterNotFoundAction determines the missing-parameter behavior. Allow treats no matched parameter as success; Deny invokes the policy failurePolicy. The presence of a policy object alone does not establish a fail-closed missing-parameter decision.

Source: Kubernetes validating admission policy. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a Kubernetes validating admission policy always reject requests when its parameter is missing?

Buyer evidence still required

  • The policy, binding and matching request.
  • The paramRef selector and available parameter objects.
  • parameterNotFoundAction, failurePolicy and validationActions.

Suggested review condition: Do not assert rejection for absent parameters without checking the complete binding and failure configuration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The policy, binding and matching request. The paramRef selector and available parameter objects. parameterNotFoundAction, failurePolicy and validationActions.

Optional saved evidence: A policy owner must review parameter selection and failure behavior before relying on a parameterised admission rule.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Live cluster behavior or a guarantee that every request matches the policy
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: Mutations need final-state validation

Question: Can an agent rely on a fixed ordering of Kubernetes mutating admission webhooks?

Kubernetes does not guarantee a consistent mutating-webhook order. The documentation recommends idempotent individual and combined mutations, with validation after mutation to check the resulting object. Reinvocation can observe later changes but is not a fixed-order contract.

Source: Admission Webhook Good Practices | Kubernetes. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an agent rely on a fixed ordering of Kubernetes mutating admission webhooks?

Buyer evidence still required

  • Mutating webhook configuration and revisions.
  • Final admitted object and mutation evidence.
  • Validating admission response.

Suggested review condition: Do not accept a claimed final invariant based only on one mutator running successfully.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Mutating webhook configuration and revisions. Final admitted object and mutation evidence. Validating admission response.

Optional saved evidence: Prevent approval based on an intermediate object that another mutator changes.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual cluster configuration, convergence testing or validation of any customer workload
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: Offline JWT validation after object deletion

Question: Does offline validation of a Kubernetes service-account JWT detect that its bound Pod was deleted?

An external service validating a service-account JWT offline does not check that its embedded object claims remain current. A token bound to a deleted object can still pass that validation until expiry. Kubernetes directs clients needing current bound-claim validation to the TokenReview API.

Source: Kubernetes: Managing Service Accounts. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does offline validation of a Kubernetes service-account JWT detect that its bound Pod was deleted?

Buyer evidence still required

  • Token audience, expiry and bound object identity, without disclosing the token.
  • Relying-service validation method and TokenReview response where applicable.
  • Deletion time and dated evidence of the relying service access decision.

Suggested review condition: Decline immediate external-access cutoff claims supported only by object deletion and offline signature validation; require current validation and access evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token audience, expiry and bound object identity, without disclosing the token. Relying-service validation method and TokenReview response where applicable. Deletion time and dated evidence of the relying service access decision.

Optional saved evidence: An agent offboarding plan must identify how each relying service validates workload tokens, rather than assume Pod deletion ends every external session.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Revocation of every external session or proof that a relying service currently denies the token
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: Role administration has explicit escalation exceptions

Question: Do Kubernetes RBAC escalation checks prevent every role administrator from delegating stronger permissions?

Kubernetes normally requires a role author to possess the permissions being added and a binding author to possess the permissions being delegated. The explicit escalate and bind verbs provide exceptions. Reviewing ordinary create or update privileges alone misses these distinct delegation authorities.

Source: Kubernetes RBAC authorization. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do Kubernetes RBAC escalation checks prevent every role administrator from delegating stronger permissions?

Buyer evidence still required

  • The acting principal and effective RBAC grants.
  • The target role permissions and binding scope.
  • Any bind or escalate permissions and the requested change.

Suggested review condition: Do not approve a bounded role-administration claim without checking explicit bind and escalate authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The acting principal and effective RBAC grants. The target role permissions and binding scope. Any bind or escalate permissions and the requested change.

Optional saved evidence: A platform owner must inspect special RBAC privileges before allowing an agent to administer roles or bindings.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Effective authorisation in a buyer cluster or admission-policy enforcement
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: Secret listing is not metadata-only access

Question: Can a Kubernetes inventory role reveal secrets without a get permission?

Kubernetes documents that list and watch access can reveal Secret contents. It also identifies workload-creation permissions as another route to namespace resources. A review confined to the get verb therefore cannot establish secret isolation; inspect the complete role and workload authority.

Source: Kubernetes RBAC secret and workload permissions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The inventory role cannot retrieve secret values.

Buyer evidence still required

  • Effective roles and bindings for the inventory identity.
  • Secret list/watch permissions and namespace scope.
  • Workload creation authority and applicable admission controls.

Suggested review condition: Keep secret isolation unproven until all relevant permissions are evidenced.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. RBAC bindings, workload authority and admission policy changes.

Optional saved evidence: Save the specific permission gaps that prevent approving an inventory role as metadata-only.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Kubernetes: Warn and Audit are not Deny

Question: Does a failing ValidatingAdmissionPolicy necessarily reject a Kubernetes request?

The binding selects validationActions. Kubernetes documents Deny as rejection, Warn as a client warning and Audit as inclusion in the request audit event. A validation failure must be interpreted with the binding action rather than as an automatic refusal.

Source: Kubernetes: Validating Admission Policy. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a failing ValidatingAdmissionPolicy necessarily reject a Kubernetes request?

Buyer evidence still required

  • Policy expression and matching scope.
  • Binding validationActions.
  • Request response and corresponding audit annotation.

Suggested review condition: Require a matching Deny action and separate outcome evidence before claiming a request was refused.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Policy, matching binding, validationActions and observed request outcome.

Optional saved evidence: Does a failing ValidatingAdmissionPolicy necessarily reject a Kubernetes request?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Lambda and SQS: Partial failures and repeated actions

Question: Can one failed SQS batch item cause an agent to repeat actions that already succeeded?

By default, a failed Lambda SQS batch makes all its messages visible again, including successfully processed items. Partial reporting requires ReportBatchItemFailures plus the failed message identifiers. An uncaught function exception still fails the entire batch; FIFO handling also retains failed and unprocessed items after the first failure.

Source: AWS Lambda: Handling errors for an SQS event source. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can one failed SQS batch item cause an agent to repeat actions that already succeeded?

Buyer evidence still required

  • Event-source mapping settings, queue type and message identifiers.
  • Per-item outcomes and the returned batchItemFailures response or thrown exception.
  • Business-effect identifiers and deduplication or reconciliation evidence for retries.

Suggested review condition: Decline once-only completion claims from a batch status alone; reconcile successful effects and the actual retry set before treating reprocessing as safe.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Event-source mapping settings, queue type and message identifiers. Per-item outcomes and the returned batchItemFailures response or thrown exception. Business-effect identifiers and deduplication or reconciliation evidence for retries.

Optional saved evidence: An agent performing external changes needs item-level evidence before retrying a mixed-result batch, rather than counting each delivery as a new authorized action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exactly-once external effects or proof that partial reporting was configured correctly in the buyer deployment
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Lambda async: Accepted events, duplicates and expiry

Question: Does successful asynchronous Lambda invocation prove the function completed?

Asynchronous invocation uses a service queue. Function errors and throttling follow different retry behaviour; duplicate delivery is possible even without a function error. Events can expire or exhaust attempts. Dead-letter queues and failure destinations capture different failure information and require configuration.

Source: Lambda asynchronous error handling. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An accepted asynchronous request guarantees one completed function execution.

Buyer evidence still required

  • Asynchronous retry and maximum event-age settings.
  • Failure destination or dead-letter configuration.
  • Function idempotency and completion evidence.

Suggested review condition: Keep request acceptance separate from verified completion and failure recovery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Invocation mode, event age, retry policy, concurrency and failure destinations.

Optional saved evidence: Preserve the acceptance-versus-completion boundary for automated integration review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Lambda/Kinesis: Checkpoint replay after partial failure

Question: Does Lambda retry only the failed Kinesis records listed in a partial batch response?

With ReportBatchItemFailures enabled on the event source mapping, Lambda uses the lowest reported failed sequence number as its checkpoint and retries all records from there. Later successful records can therefore repeat. Returning partial-failure data in function code is insufficient unless that response type is enabled on the mapping.

Source: AWS Lambda: Kinesis partial batch responses. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does Lambda retry only the failed Kinesis records listed in a partial batch response?

Buyer evidence still required

  • Event source mapping response types, retry and batch-bisection settings.
  • Reported failed sequence numbers and the actual checkpoint.
  • Later-record effects and their handling on repeated delivery.

Suggested review condition: Decline failed-items-only retry claims without checking the stream checkpoint and all later records that can replay.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Event source mapping response types, retry and batch-bisection settings. Reported failed sequence numbers and the actual checkpoint. Later-record effects and their handling on repeated delivery.

Optional saved evidence: A handler that retries only failed-item logic conceptually may still repeat already successful downstream effects.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exactly-once downstream effects or equivalence to SQS partial-batch behavior
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Langfuse deletion: Accepted requests and completed removal differ

Question: Does a Langfuse trace deletion response prove all related personal data is gone?

Tracing deletion is asynchronous and the guide recommends querying again to check completion. Removing traces does not necessarily remove data held in other objects such as datasets, and later ingestion can add data again. Scope, timing and verification need separate evidence.

Source: Langfuse data deletion. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A trace-deletion request proves complete immediate erasure.

Buyer evidence still required

  • Selected trace IDs and related object inventory.
  • Ingestion state and completion checks.
  • Separate dataset and other retained-object review.

Suggested review condition: Do not convert deletion acceptance into a complete-erasure assertion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Deletion selection, ingestion, related objects and completion evidence

Optional saved evidence: Preserve deletion scope and outstanding completion checks without inventing an erasure guarantee.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Langfuse MCP: Project keys expose more than documentation

Question: Is the Langfuse MCP connection a public documentation-only tool?

The data-platform endpoint is authenticated and project-scoped. Read and write tools are available by default; the guide recommends a client allowlist for read-only workflows. It is separate from the public documentation server. Endpoint region, key scope and permitted operations must be identified.

Source: Langfuse project MCP server. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Authenticated project endpoint, distinct from public docs MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Langfuse operates Cloud; buyers can self-host.

Documented by publisher. Langfuse project MCP server

Purpose

Retrieve project evidence and manage supported platform objects.

Documented by publisher. Langfuse project MCP server

Read capability

Project prompts and observability data.

Documented by publisher. Langfuse project MCP server

Write capability

Supported prompt and other write tools are available.

Documented by publisher. Langfuse project MCP server

Authentication

Project API-key pair through Basic authentication.

Documented by publisher. Langfuse project MCP server

Permission surface

Project scope and effective client tool allowlist.

Documented by publisher. Langfuse project MCP server

Data leaving the environment

Project content becomes available to the connected agent.

Review inference. Langfuse project MCP server

Failure modes to consider

Confusing docs access with project access can disclose sensitive data.

Review inference. Langfuse project MCP server

Unknowns and applicability

Buyer allowlist, key ownership and data retention are untested.

Not established

Suggested refusal or clarification condition

Require project disclosure and write authority separately.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Tool set, project key scope, endpoint region and client enforcement.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the project-data disclosure and write-authority conditions for an observability integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangGraph interrupts: Resumption repeats preceding node code

Question: Does resuming a LangGraph approval interrupt avoid repeating actions earlier in the same node?

LangGraph resumes an interrupted node from its beginning, so code before the interrupt runs again. The guide requires preceding side effects to be idempotent and recommends placing effects after the interrupt or in separate nodes where appropriate. A saved checkpoint does not make arbitrary earlier effects execute only once.

Source: LangGraph interrupts. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does resuming a LangGraph approval interrupt avoid repeating actions earlier in the same node?

Buyer evidence still required

  • Node code ordering, interrupt location and workflow version
  • Thread identity, checkpoint and resume history
  • External-operation identity and idempotency or reconciliation evidence

Review inference: A review needs the effect location and external deduplication evidence, not just the existence of a checkpoint.

Suggested review condition: Refuse an exactly-once or approval-before-effect claim without reviewing node ordering and prior external effects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer node code, idempotency behavior and external action history are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent repeated writes or purchases when an agent resumes after approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exactly-once external effects, valid approval binding or tested recovery of a buyer workflow
  • A conclusion that every replay repeats an external effect despite application deduplication
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangGraph: Approval interrupts must reach the runtime

Question: Does a broad exception handler around LangGraph interrupt preserve the approval pause?

LangGraph documents interrupt as a special exception used to suspend execution. A broad try/except can intercept it before the runtime receives the pause signal; the guide separates interrupts from error handling or catches specific error types.

Source: LangGraph interrupts. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a broad exception handler around LangGraph interrupt preserve the approval pause?

Buyer evidence still required

  • node exception handling
  • runtime interruption result
  • persisted checkpoint
  • installed version

Review inference: Refuse to infer that an approval gate paused the run merely because the code called interrupt; inspect exception propagation and the persisted interruption before allowing the dependent action. Whether the approval pause reaches the runtime is distinct from whether earlier code repeats after an established pause. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse to infer that an approval gate paused the run merely because the code called interrupt; inspect exception propagation and the persisted interruption before allowing the dependent action.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Do not wrap `interrupt` calls in try/except

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to infer that an approval gate paused the run merely because the code called interrupt; inspect exception propagation and the persisted interruption before allowing the dependent action.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

LangGraph: Durability mode changes the process-crash recovery boundary

Question: Do LangGraph exit, async and sync modes preserve the same recovery state after a process crash?

LangGraph documents three durability modes. exit persists at successful exit, error or interrupt, leaving intermediate state unavailable after a mid-run process crash. async writes checkpoints while the next step runs and can lose an unwritten checkpoint in a crash. sync writes each checkpoint before the next step starts. The selected mode changes the checkpoint recovery boundary.

Source: LangGraph checkpointers. Documentation checked 2026-10-23; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Do LangGraph exit, async and sync modes preserve the same recovery state after a process crash?

Buyer evidence still required

  • Installed LangGraph version, invocation durability mode and checkpointer backend
  • Last committed checkpoint, crash timing and resume configuration
  • External effect identifiers and evidence reconciling effects with saved state

Review inference: A crash-recovery claim should identify both the chosen mode and the last confirmed persistence boundary.

Suggested review condition: Refuse equivalent crash-recovery or exactly-once claims based only on using LangGraph or enabling a checkpointer.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer's persistence backend, crash timing, saved checkpoint and external effects are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Choose and review a recovery configuration without treating every saved agent workflow as equally crash durable.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Atomicity between a checkpoint and an external API effect, or exactly-once payment or write execution
  • Tested durability of the buyer's checkpointer, database, filesystem or installed package
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangGraph: Durable execution boundary

Question: Does LangGraph's durable execution support establish recovery for a deployed agent?

LangGraph documents orchestration capabilities including durable execution, persistence, streaming and human oversight. A deployment still needs suitable configuration and recovery testing; the documented capabilities alone do not prove that a particular interrupted action resumes correctly.

Source: LangGraph overview. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • tested deployment recovery
  • exactly-once external effects
  • configured persistence

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangGraph: Forking preserves the original history

Question: Does LangGraph update_state roll back the original execution history?

The LangGraph time-travel guide states that update_state creates a new checkpoint branching from the chosen point. The original execution history remains intact; the operation is a fork rather than a rollback.

Source: LangGraph time travel. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does LangGraph update_state roll back the original execution history?

Buyer evidence still required

  • source checkpoint
  • new fork checkpoint
  • original execution history
  • external effect references

Review inference: Do not treat a fork as reversal of original external actions or deletion of earlier history. Reconcile branch identity and any required external compensation separately. A deliberate history branch has different lineage from normal failed-step recovery using retained pending writes. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not treat a fork as reversal of original external actions or deletion of earlier history. Reconcile branch identity and any required external compensation separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Fork

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat a fork as reversal of original external actions or deletion of earlier history. Reconcile branch identity and any required external compensation separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

LangGraph: Framework dependency scope

Question: Is LangChain required to use LangGraph?

The official LangGraph overview states that LangGraph can be used without LangChain. That package-level flexibility does not establish that a particular application's tools, integrations or migration path are independent of their own dependencies.

Source: LangGraph overview. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • dependency-free application
  • automatic migration compatibility
  • tested integration portability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangGraph: Pending writes preserve successful siblings after a step failure

Question: Must LangGraph rerun every parallel node when one node in the same super-step fails?

LangGraph documents pending checkpoint writes for nodes that finish successfully within a super-step. When another node in that step fails, the retained writes allow normal recovery to resume without rerunning those successful nodes. These per-task writes are not complete StateSnapshot checkpoints; time travel uses full super-step checkpoints. This recovery mechanism does not independently reconcile external side effects.

Source: LangGraph checkpointers. Documentation checked 2026-10-23; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Must LangGraph rerun every parallel node when one node in the same super-step fails?

Buyer evidence still required

  • Graph topology, node identities, failed super-step and installed LangGraph version
  • Persisted pending writes, full checkpoint and intended resume versus replay operation
  • External effect identities and independent outcome reconciliation for affected nodes

Review inference: A recovery review should distinguish successful persisted sibling outputs from the failed node and from an intentional historical replay.

Suggested review condition: Refuse a claim that every sibling must rerun, or that no external effect can repeat, without inspecting saved writes and the chosen recovery operation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Persisted buyer writes, failed-node effects, saver behaviour and the selected recovery operation are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid unnecessary repeated actions while reconstructing which parts of a parallel agent step completed before failure.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exactly-once external actions or recovery when the required writes were not persisted
  • Equivalence between normal failure recovery and deliberately replaying an earlier checkpoint
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangGraph: Resume values follow interrupt position

Question: Can reordered LangGraph interrupts reuse the original approval values safely?

Within a LangGraph node, saved resume values are matched to interrupt calls by position in the task-specific list. The documented rule requires a consistent call order and warns against conditional skipping or nondeterministic loops.

Source: LangGraph interrupts. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can reordered LangGraph interrupts reuse the original approval values safely?

Buyer evidence still required

  • original and resumed node definitions
  • interrupt sequence
  • resume values
  • reviewed action payload

Review inference: Refuse an approval-to-action match when interrupt order or branch selection changed; establish the exact question, payload and resume position for the paused run. This checks which question receives a saved approval, rather than whether pre-interrupt side effects execute again. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse an approval-to-action match when interrupt order or branch selection changed; establish the exact question, payload and resume position for the paused run.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Do not reorder `interrupt` calls within a node

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse an approval-to-action match when interrupt order or branch selection changed; establish the exact question, payload and resume position for the paused run.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

LangGraph: Returned output can differ from saved state

Question: Does a LangGraph Functional API response necessarily equal the state saved for the next invocation?

LangGraph entrypoint.final can return one value while saving another in the checkpoint. The saved value supplies previous on a later invocation; recording only the caller-visible response can omit that distinct continuation state.

Source: LangGraph Functional API. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a LangGraph Functional API response necessarily equal the state saved for the next invocation?

Buyer evidence still required

  • entrypoint.final value and save fields
  • thread ID
  • checkpoint ID
  • subsequent previous value

Review inference: Do not reconstruct the next invocation from the response alone when entrypoint.final is used; retain both returned and saved values with their thread and checkpoint identities. Returned-versus-saved state within one entrypoint is separate from the inventory distinction between thread checkpoints and cross-thread stores. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not reconstruct the next invocation from the response alone when entrypoint.final is used; retain both returned and saved values with their thread and checkpoint identities.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. entrypoint.final; Short-term memory

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not reconstruct the next invocation from the response alone when entrypoint.final is used; retain both returned and saved values with their thread and checkpoint identities.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

LangGraph: State attribution is not node execution

Question: Does a LangGraph checkpoint attributed through as_node prove that node actually ran?

For update_state, LangGraph applies the selected node writers and records that node as the update producer; execution continues at its successors. The guide explicitly allows choosing a later as_node to skip nodes.

Source: LangGraph time travel. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a LangGraph checkpoint attributed through as_node prove that node actually ran?

Buyer evidence still required

  • update_state arguments
  • as_node value
  • graph edges
  • independent node execution evidence

Review inference: Refuse to use as_node attribution alone as evidence of executed approval, payment or validation work; obtain independent execution and outcome evidence for any skipped node. Operator-supplied producer attribution can skip work; retained successful sibling writes instead describe normal recovery of work already completed. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse to use as_node attribution alone as evidence of executed approval, payment or validation work; obtain independent execution and outcome evidence for any skipped node.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. From a specific node

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to use as_node attribution alone as evidence of executed approval, payment or validation work; obtain independent execution and outcome evidence for any skipped node.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

LangGraph: State repair uses configured reducers

Question: Does updating a LangGraph state field always replace its previous value?

LangGraph state updates use the configured field reducer. An additive reducer can merge new values into accumulated state; the documented Overwrite wrapper bypasses the reducer when explicit replacement is intended.

Source: LangGraph Graph API. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does updating a LangGraph state field always replace its previous value?

Buyer evidence still required

  • field reducer
  • repair input
  • resulting state
  • required retained or replaced items

Review inference: Do not assume a repair removed an earlier approval or evidence item. Inspect the reducer, resulting state and deliberate replacement operation before relying on the corrected state. The decision concerns merge-versus-replacement of a repaired field, not persistence or rerunning of parallel tasks. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not assume a repair removed an earlier approval or evidence item. Inspect the reducer, resulting state and deliberate replacement operation before relying on the corrected state.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Bypass reducers with `Overwrite`

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assume a repair removed an earlier approval or evidence item. Inspect the reducer, resulting state and deliberate replacement operation before relying on the corrected state.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

LangGraph: Subgraph replay needs the right checkpoint scope

Question: Can a parent LangGraph checkpoint replay only the second approval inside a default subgraph?

The time-travel guide treats a default subgraph as one parent-level super-step. Replaying from before it runs the subgraph from the start; its own checkpointer provides internal checkpoint history for finer replay selection.

Source: LangGraph time travel. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a parent LangGraph checkpoint replay only the second approval inside a default subgraph?

Buyer evidence still required

  • parent and child checkpoint configuration
  • selected checkpoint namespace
  • internal approval sequence
  • external effect references

Review inference: Do not promise selective replay of one internal approval without a matching subgraph checkpoint. Identify the replay scope and separately reconcile any repeated external actions. Intentional replay granularity inside a nested graph differs from pending-write retention during ordinary parallel-node failure recovery. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not promise selective replay of one internal approval without a matching subgraph checkpoint. Identify the replay scope and separately reconcile any repeated external actions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Subgraphs; Inherited checkpointer

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not promise selective replay of one internal approval without a matching subgraph checkpoint. Identify the replay scope and separately reconcile any repeated external actions.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

LangGraph: Timed-out state writes do not settle external outcomes

Question: Does a LangGraph node timeout prove that the node made no external change?

LangGraph documents per-attempt timeouts for async nodes and states that timed-out attempts do not commit buffered state writes or child-task scheduling. A configured retry may start another attempt with a fresh timeout.

Source: LangGraph Graph API. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a LangGraph node timeout prove that the node made no external change?

Buyer evidence still required

  • node timeout and retry policy
  • attempt IDs
  • buffered-state outcome
  • downstream operation identity and result

Review inference: Local buffered-write suppression does not establish reversal or absence of an external API effect. Reconcile that effect before retrying; per-attempt limits do not establish a whole-workflow deadline. Node timeout support requires LangGraph 1.2 or later. An async attempt timeout discards buffered writes while permitting retries; the prior record concerns checkpoint durability across process crashes. Operational review inference; no deployment outcome was observed.

Suggested review condition: Local buffered-write suppression does not establish reversal or absence of an external API effect. Reconcile that effect before retrying; per-attempt limits do not establish a whole-workflow deadline. Node timeout support requires LangGraph 1.2 or later.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Set node timeouts; Configure node timeouts

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Local buffered-write suppression does not establish reversal or absence of an external API effect. Reconcile that effect before retrying; per-attempt limits do not establish a whole-workflow deadline. Node timeout support requires LangGraph 1.2 or later.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

LangSmith MCP: Trace reads, prompt writes and experiments

Question: Can a LangSmith MCP agent inspect traces without also being authorised to run evaluations?

The remote tool surface includes trace reads alongside prompt publishing, dataset changes and experiment execution. OAuth and API-key access are documented. Self-hosted availability also depends on version and signing configuration. Connection success does not grant task authority for every exposed operation.

Source: LangSmith remote MCP. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted service or supported self-hosted deployment

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

LangChain operates Cloud; buyers can self-host LangSmith.

Documented by publisher. LangSmith remote MCP

Purpose

Inspect traces and manage supported development/evaluation objects.

Documented by publisher. LangSmith remote MCP

Read capability

Runs, projects, prompts, datasets, threads and billing usage.

Documented by publisher. LangSmith remote MCP

Write capability

Prompt publishing, dataset/example changes and experiments.

Documented by publisher. LangSmith remote MCP

Authentication

OAuth or a LangSmith API key.

Documented by publisher. LangSmith remote MCP

Permission surface

Authenticated access and available tool permissions require review.

Documented by publisher. LangSmith remote MCP

Data leaving the environment

Trace and dataset content reaches the agent.

Review inference. LangSmith remote MCP

Failure modes to consider

An experiment may invoke configured work beyond passive inspection.

Review inference. LangSmith remote MCP

Unknowns and applicability

Buyer scope, evaluation cost and client compatibility are unverified.

Not established

Suggested refusal or clarification condition

Require separate authority for writes and experiment execution.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Tool surface, authentication support, self-hosted prerequisites and experiment scope.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve why trace inspection did or did not authorise a later evaluation or change.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangSmith shared traces: Read-only links can widen the audience

Question: Does a read-only LangSmith trace link keep its content restricted to account members?

A publicly shared trace can be viewed by anyone holding its link without a LangSmith account. Self-hosted network constraints can limit reach. Read-only describes editing, not confidentiality; inspect the trace and deployment before sharing, and distinguish unsharing from deleting the underlying trace.

Source: LangSmith trace sharing. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Read-only trace sharing preserves account-only confidentiality.

Buyer evidence still required

  • Public sharing state and deployment reachability.
  • Trace content review.
  • Unshare and deletion procedures.

Suggested review condition: Require disclosure authority before sharing a trace outside its existing audience.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Sharing state, network reachability, trace content and revocation

Optional saved evidence: Retain the audience and content-disclosure decision for diagnostic collaboration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangSmith: Function completion can precede trace delivery

Question: Does a returned serverless function prove its LangSmith traces were delivered?

The LangSmith JavaScript SDK guide describes background tracing and the risk of execution ending before pending data is flushed. It documents waiting for pending batches or disabling background tracing; manual flush mode requires an explicit flush. Function return is not trace-delivery evidence.

Source: LangSmith tracing in serverless environments. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a returned serverless function prove its LangSmith traces were delivered?

Buyer evidence still required

  • The LangSmith JS SDK version and tracing mode.
  • Shutdown handling and pending-batch or flush results.
  • The expected run IDs and server-side trace availability.

Suggested review condition: Do not treat application return as complete tracing without delivery or retrieval evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The LangSmith JS SDK version and tracing mode. Shutdown handling and pending-batch or flush results. The expected run IDs and server-side trace availability.

Optional saved evidence: An agent operator must reconcile application completion with asynchronous observability delivery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Execution of the SDK, guaranteed delivery or business-action completion
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangSmith: Retention changes apply prospectively

Question: Does reducing LangSmith retention shorten the lifetime of already stored traces?

LangSmith documents that retention changes apply to new traces only. Existing traces are unaffected; shortening a workspace policy is not a deletion action for prior trace data.

Source: LangSmith data purging and compliance. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does reducing LangSmith retention shorten the lifetime of already stored traces?

Buyer evidence still required

  • The policy effective time.
  • Creation times of affected traces.
  • Separate historical deletion and retrieval evidence.

Suggested review condition: Do not claim historical cleanup solely from a shorter retention setting.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The policy effective time. Creation times of affected traces. Separate historical deletion and retrieval evidence.

Optional saved evidence: An observability owner must distinguish future retention settings from historical trace cleanup.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Confirmation that historical traces were deleted
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LangSmith: Soft deletion preserves example history

Question: Does deleting a LangSmith dataset example remove its inputs and outputs from all versions?

LangSmith distinguishes default soft deletion from hard deletion. Soft deletion preserves historical versions; hard deletion removes the selected example inputs, outputs and metadata across dataset versions. The requested mode and affected example IDs matter.

Source: LangSmith data purging and compliance. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a LangSmith dataset example remove its inputs and outputs from all versions?

Buyer evidence still required

  • The affected example IDs.
  • The deletion mode requested.
  • Checks across relevant dataset versions.

Suggested review condition: Do not report removal from history when only soft deletion is evidenced.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The affected example IDs. The deletion mode requested. Checks across relevant dataset versions.

Optional saved evidence: A dataset custodian must establish whether historical training or evaluation examples remain retrievable.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Execution or independent confirmation of hard deletion
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

LaunchDarkly MCP: Flag changes and environment scope

Question: How can I review a feature-flag agent without granting broad change authority?

The local LaunchDarkly MCP uses an API access token. Its documentation recommends both a read-only token role and read scope for a read-only setup, and supports selecting tools. Review the token, environment and enabled operations together; a flag change can affect application behaviour even without a new deployment.

Source: LaunchDarkly local MCP token permissions and tool restrictions. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Local MCP server with API token; hosted OAuth variant excluded

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

LaunchDarkly publishes the MCP; the buyer operates this local variant.

Documented by publisher. LaunchDarkly local MCP token permissions and tool restrictions; LaunchDarkly MCP flag operations and local deployment

Purpose

Use supported LaunchDarkly operations through an assistant.

Documented by publisher. LaunchDarkly local MCP token permissions and tool restrictions; LaunchDarkly MCP flag operations and local deployment

Read capability

Retrieves flag and related account context through exposed tools.

Documented by publisher. LaunchDarkly local MCP token permissions and tool restrictions; LaunchDarkly MCP flag operations and local deployment

Write capability

Includes feature-flag creation and updates when permitted.

Documented by publisher. LaunchDarkly local MCP token permissions and tool restrictions; LaunchDarkly MCP flag operations and local deployment

Authentication

The local server uses a LaunchDarkly API access token.

Documented by publisher. LaunchDarkly local MCP token permissions and tool restrictions; LaunchDarkly MCP flag operations and local deployment

Permission surface

Documentation pairs read scope with a read-only token role and permits tool selection.

Documented by publisher. LaunchDarkly local MCP token permissions and tool restrictions; LaunchDarkly MCP flag operations and local deployment

Data leaving the environment

Local execution still sends API requests to LaunchDarkly and returns context to the assistant.

Review inference. LaunchDarkly local MCP token permissions and tool restrictions; LaunchDarkly MCP flag operations and local deployment

Failure modes to consider

Wrong-environment changes or overbroad token permissions can have operational effects.

Review inference. LaunchDarkly local MCP token permissions and tool restrictions; LaunchDarkly MCP flag operations and local deployment

Unknowns and applicability

The installed version, token grants and actual flag evaluation paths are unverified.

Not established

Suggested refusal or clarification condition

Require an explicit target environment and change approval; do not treat local hosting as read-only authority.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck token roles, selected tools and deployment variant.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the token, tool and environment evidence used for a flag-agent review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Ledger 0042: Deployment boundary

Question: Does Ledger 0042 establish production deployment?

Ledger 0042 publicly groups canonical corpus freezes. Its existence and grouping claims do not establish production deployment.

Derived from BDAS INDEX Ledger 0042 — Canonical Freeze Bundle. No new experiment or validation is claimed.

Claim boundaries
  • production deployment
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Linear MCP: Workspace identity and posting authority

Question: What should an agent check before using Linear MCP across more than one workspace?

Linear documents a separate authentication context for each workspace; reconnecting alone does not switch an existing session's workspace. Its MCP supports OAuth and direct tokens, including a restricted read-only API key. Check the active workspace, actor and granted scopes before posting or updating work. This profile does not verify your current session.

Source: Linear MCP server. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Linear's hosted MCP and documented OAuth scope model; actual client auth context and workspace membership are unspecified.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Linear operates the documented hosted MCP.

Documented by publisher. Linear MCP server; Linear OAuth scope reference

Purpose

Retrieve planning information and manage issues, projects and comments.

Documented by publisher. Linear MCP server; Linear OAuth scope reference

Read capability

Accessible Linear work information through the authenticated connection.

Documented by publisher. Linear MCP server; Linear OAuth scope reference

Write capability

Documented workflows create work and post updates; OAuth distinguishes general write from narrower issue/comment creation scopes.

Documented by publisher. Linear MCP server; Linear OAuth scope reference

Authentication

OAuth sessions or direct bearer tokens/API keys; a Read-only API key is documented for restricted retrieval.

Documented by publisher. Linear MCP server; Linear OAuth scope reference

Permission surface

Workspace authentication contexts must be separated. OAuth actor and scope settings affect whose authority is used.

Documented by publisher. Linear MCP server; Linear OAuth scope reference

Data leaving the environment

Selected work data is returned to the client; local auth storage does not demonstrate local-only model processing.

Review inference. Linear MCP server; Linear OAuth scope reference

Failure modes to consider

Updating the wrong workspace; unnecessary broad write scopes; confusing an app actor with a user actor.

Review inference. Linear MCP server; Linear OAuth scope reference

Unknowns and applicability

Active workspace, actual actor, key scope, membership and downstream client policy.

Not established

Suggested refusal or clarification condition

Do not post updates until workspace and actor match the task; use an approved read-only connection for reporting-only work.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain workspace, actor and permission questions behind a planning-connector review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Linear SCIM evidence: Provisioning and offboarding coverage

Question: Does enabling Linear SCIM prove every former user and integration has lost access?

Linear documents SCIM provisioning and suspension driven by the identity provider, including group mapping and exceptions requiring attention. Disabling SCIM stops synchronization; changes may need to be pushed again after re-enablement. A supported feature is not proof of complete offboarding across users, guests and independent integration credentials.

Source: Linear SCIM provisioning scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: SCIM support alone proves every access path is revoked when someone leaves.

Buyer evidence still required

  • The relevant identity-provider change and its successful synchronization
  • The resulting user and team state in Linear
  • A separate inventory and review of credentials not covered by the user update

Suggested review condition: Require account-state and integration evidence before claiming complete offboarding; resolve synchronization gaps.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck synchronization, manually managed guests, plan changes and integrations.

Optional saved evidence: Retain the demonstrated provisioning scope and outstanding offboarding questions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Live Probe V1: Public API availability boundary

Question: Does a Centered Live Probe V1 pass prove public API availability?

The probe source supports pipeline and check integrity. It excludes public API availability; the public discovery surface and launch-phase onboarding do not change that evidence boundary.

Derived from BDAS Centered Live Probe V1 — Validation Probe Pass. No new experiment or validation is claimed.

Claim boundaries
  • public API availability
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Local harness file memory versus opt-in managed Foundry facts

Question: Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts?

Microsoft distinguishes agent-written local file memory from automatically extracted managed Foundry memory. The two can be used together and have different storage and scope.

Source: Microsoft primary documentation: ms harness memory. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts?

Buyer evidence still required

  • provider configuration
  • local folder/session mapping
  • Foundry store/user scope
  • separate deletion evidence

Review inference: Does clearing a Microsoft harness local memory folder remove Foundry-extracted facts? Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts. Local harness file memory versus opt-in managed Foundry facts. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. File memory (coarse, explicit)

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inventory both configured memory providers; clearing a local folder cannot establish disposal of managed facts.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Local prompt preprocessing executes before model sees skill body

Question: Can a local Claude Code skill run a shell command while constructing its prompt?

The documented exclamation/backtick syntax executes commands before the skill content is sent to Claude and substitutes their output. Synced skills have surface- and version-specific restrictions.

Source: Anthropic primary documentation: claude code skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a local Claude Code skill run a shell command while constructing its prompt?

Buyer evidence still required

  • raw skill body
  • preprocessing commands
  • client version
  • local/synced surface
  • permission policy

Review inference: Can a local Claude Code skill run a shell command while constructing its prompt? Include load-time commands in admission review; do not classify a skill as instructions-only because its displayed body contains substituted output. Local prompt preprocessing executes before model sees skill body. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Include load-time commands in admission review; do not classify a skill as instructions-only because its displayed body contains substituted output.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Inject dynamic context

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Include load-time commands in admission review; do not classify a skill as instructions-only because its displayed body contains substituted output.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Local shell and patch approval opt-in

Question: Does setting an OpenAI Agents SDK on_approval callback require approval for local shell or patch calls?

In the pinned Python SDK documentation, local ShellTool and ApplyPatchTool default needs_approval to False. An on_approval callback alone does not enable approval. The callback runs only for calls that require approval and lack an existing decision; configure needs_approval separately.

Source: OpenAI Agents Python human-in-the-loop guide, v0.24.0. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does setting an OpenAI Agents SDK on_approval callback require approval for local shell or patch calls?

Buyer evidence still required

  • Exact installed version, provider variant and effective non-secret configuration
  • Relevant pending-call identifiers, declared arguments and decision provenance without secrets
  • Application-owned review policy and independently observed outcomes where needed

Review inference: Do not count a callback declaration as an active approval gate without the effective needs_approval policy and existing decision state. Existing Claude callback shadowing and Agent Framework auto-approval records concern different policy orderings. This decision tests whether the local OpenAI callback opts in at all, with a separate default-false switch. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not count a callback declaration as an active approval gate without the effective needs_approval policy and existing decision state.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Approval configuration: local shell and file edits

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not count a callback declaration as an active approval gate without the effective needs_approval policy and existing decision state.
  • A needs_approval=True call without an existing decision can invoke the callback; not every callback is bypassed.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External advisory review

Lodash templates: Match the exact package before applying a fix

Question: Does the lodash 4.17.21 fix also cover lodash.template and lodash-template?

GitHub's reviewed advisory GHSA-35jh-r3h4-6jhm lists lodash before 4.17.21 as affected by CVE-2021-23337, with 4.17.21 patched. It separately lists lodash.template through 4.5.0 and lodash-template through 1.0.0 without a patched version. Those package names must not inherit lodash's fix by similarity. Retain the exact npm package and its own source range. No patch listed is a statement about this record, not proof that remediation is impossible or that the application is exploitable.

Source: GitHub reviewed advisory: GHSA-35jh-r3h4-6jhm. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (3)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • a fix inherited across similarly named packages
  • absence of a listed patch proving no possible remediation
  • customer exploitability or current all-vulnerability clearance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

Log4j: Separate the affected component from a historical fix

Question: Does a Log4j name match or a recorded 2.15.0 fix establish deployment safety?

Apache identifies log4j-core as the affected component for CVE-2021-44228; log4j-api alone is not affected by that vulnerability. Its historical fixes include 2.3.1, 2.12.2 and 2.15.0 for different Java branches. Apache separately reports that the 2.15.0 fix was incomplete in certain configurations, tracked under CVE-2021-45046. Therefore a fix event for the first CVE is not general deployment clearance. Identify the actual component, branch and configuration, then review applicable advisories. These historical versions are not current upgrade recommendations.

Source: Apache Logging Services security: CVE-2021-44228 and CVE-2021-45046. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (3)
  • Maven / org.apache.logging.log4j:log4j-core — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-jfh8-c2jp-5v3q, captured 2026-10-08
  • Maven / org.apache.logging.log4j:log4j-core — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-jfh8-c2jp-5v3q, captured 2026-10-08
  • Maven / org.apache.logging.log4j:log4j-core — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-jfh8-c2jp-5v3q, captured 2026-10-08

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • a Log4j name match proving exposure
  • historical versions recommended as safe today
  • clearance of related advisories or buyer deployments

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Logpush exports are independent of gateway log opt-outs

Question: Do Cloudflare AI Gateway collection headers prevent Logpush from exporting that request?

Cloudflare states that Logpush exports regardless of gateway log enablement and the collection headers. Export requires a public key, the gateway Logpush setting and an enabled destination job. Exported copies have a separate destination custody boundary; disabling gateway collection does not establish their removal.

Source: Logpush. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Do Cloudflare AI Gateway collection headers prevent Logpush from exporting that request?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require the Logpush job, destination and retained-copy evidence separately; do not use gateway log absence or one enabled toggle as an export or deletion receipt.

Suggested review condition: Require the Logpush job, destination and retained-copy evidence separately; do not use gateway log absence or one enabled toggle as an export or deletion receipt.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. Logpush exports logs whether; ## 3. Set up Logpush

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the Logpush job, destination and retained-copy evidence separately; do not use gateway log absence or one enabled toggle as an export or deletion receipt.
  • Without an enabled destination job, enabling the gateway toggle alone does not start exports; configured independence is not proof that a particular export arrived.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Long-term expiry requires deployed/executed timestamp-based pruner in reviewed design, distinct from DeleteEvent-derived residue

Question: Does a configured memory age prove AgentCore long-term records expire automatically?

The reviewed AWS lifecycle design implements timestamp-filtered pruning in a separate workflow and states that AgentCore memory lacks a built-in auto-delete TTL in that design context.

Source: Amazon Web Services primary documentation: aws memory lifecycle. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a configured memory age prove AgentCore long-term records expire automatically?

Buyer evidence still required

  • memory class
  • configured policy
  • scheduler/workflow
  • record timestamps
  • deletion/reconciliation results

Review inference: Does a configured memory age prove AgentCore long-term records expire automatically? A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence. Long-term expiry requires deployed/executed timestamp-based pruner in reviewed design, distinct from DeleteEvent-derived residue. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. doesn’t provide a built-in auto-delete TTL

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A proposed TTL or event expiry is not proof that the long-term pruner ran; require its scope, execution and deletion evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Derived claim boundary

M1: Workload qualification scope

Question: Does the M1 qualification-engine record establish that all workloads qualify?

The M1 source supports bounded development evidence for a qualification engine and monitor. It explicitly excludes the claim that all workloads qualify.

Derived from BDAS M1 — Qualification Engine With AURIC Monitor. No new experiment or validation is claimed.

Claim boundaries
  • all workloads qualified
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

M3: Qualification promotion boundary

Question: Does the M3 safe-refusal record qualify the workload for promotion?

The M3 public source preserves a locked external safe refusal. It explicitly excludes qualification promotion.

Derived from BDAS M3 — External Locked Safe Refusal. No new experiment or validation is claimed.

Claim boundaries
  • qualification promotion
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

M4: Protocol versus performance

Question: Does the M4 protocol and dataset receipt establish performance qualification?

The M4 public source records protocol and dataset-receipt discipline. It explicitly excludes performance qualification.

Derived from BDAS M4 — Manufacturing External Protocol. No new experiment or validation is claimed.

Claim boundaries
  • performance qualification
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Macie discovery: Sampling and inventory coverage

Question: Does Macie automated discovery prove every object in an S3 bucket was inspected?

Automated discovery evaluates bucket inventory and selects representative objects through sampling. Discovery jobs allow more targeted scope and depth. The existence of automated discovery or no findings does not establish exhaustive inspection. Keep selected objects, configured identifiers and analysis results distinct from the total bucket inventory.

Source: Amazon Macie: Discovering sensitive data. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Automated discovery scans every stored object.

Buyer evidence still required

  • Discovery mode and selected bucket/object scope.
  • Analysis results, identifiers and allow lists.
  • Inventory reconciliation and unassessed objects.

Suggested review condition: Require explicit scope reconciliation before asserting complete bucket coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Discovery mode, object inventory, selection criteria, identifiers and dated analysis results.

Optional saved evidence: Save the distinction between sampled discovery and an exhaustive-inspection claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Malformed or ignored Claude Code frontmatter versus intended invocation restriction

Question: Can malformed Claude Code skill frontmatter fail open to default invocation behaviour?

The captured Claude Code guide says unrecognised fields are ignored, frontmatter is read only when the opening marker is the first line, and unparseable YAML still loads the skill with no fields set.

Source: Anthropic primary documentation: claude code skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can malformed Claude Code skill frontmatter fail open to default invocation behaviour?

Buyer evidence still required

  • raw SKILL.md bytes
  • parser/client version
  • intended invocation restrictions
  • loaded metadata

Review inference: Can malformed Claude Code skill frontmatter fail open to default invocation behaviour? Do not assume a misspelled or malformed restriction prevents loading; inspect parsed behaviour in the pinned client. Malformed or ignored Claude Code frontmatter versus intended invocation restriction. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not assume a misspelled or malformed restriction prevents loading; inspect parsed behaviour in the pinned client.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. If the YAML between the markers

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assume a misspelled or malformed restriction prevents loading; inspect parsed behaviour in the pinned client.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

May a compliant MCP server return a task handle before tasks/get can find it

Question: May a compliant MCP server return a task handle before tasks/get can find it?

The optional 2026-07-28 Tasks extension prohibits returning CreateTaskResult before durable creation such that tasks/get resolves. Eventually consistent implementations must wait for consistency before replying. This is a specification requirement, not evidence that a buyer's server meets it.

Source: Model Context Protocol primary documentation: mcp tasks current. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: May a compliant MCP server return a task handle before tasks/get can find it?

Buyer evidence still required

  • extension version
  • creation response
  • task ID
  • get response
  • consistency evidence

Review inference: May a compliant MCP server return a task handle before tasks/get can find it? Treat an unresolvable newly returned task as unresolved implementation evidence, not successful completion. Initial read-after-create durability differs from later retention expiry. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Treat an unresolvable newly returned task as unresolved implementation evidence, not successful completion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Task Creation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Treat an unresolvable newly returned task as unresolved implementation evidence, not successful completion.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

May an A2A follow-up attach an existing task to a different conversation context

Question: May an A2A follow-up attach an existing task to a different conversation context?

The captured specification requires deriving contextId from the task when only taskId is supplied and rejecting a message whose taskId and contextId refer to different contexts. Shared conversation intent is not sufficient to relabel an existing task.

Source: A2A Project primary documentation: a2a spec. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: May an A2A follow-up attach an existing task to a different conversation context?

Buyer evidence still required

  • task ID
  • context ID
  • stored task context
  • follow-up message

Review inference: May an A2A follow-up attach an existing task to a different conversation context? Refuse cross-context continuation without a matching task-context pair. Concrete task-context consistency differs from generic opaque collaboration and confidentiality. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse cross-context continuation without a matching task-context pair.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. 3.4.3. Multi-Turn Conversation Patterns

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse cross-context continuation without a matching task-context pair.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

May an MCP server reuse an inputRequests key for a different question later in a task

Question: May an MCP server reuse an inputRequests key for a different question later in a task?

The optional 2026-07-28 Tasks extension requires input request keys to stay unique over the task lifetime and prohibits reusing a satisfied key for a later request. Clients should deduplicate repeated keys across polls. Stable keys bind responses to the intended request rather than a later substituted question.

Source: Model Context Protocol primary documentation: mcp tasks current. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: May an MCP server reuse an inputRequests key for a different question later in a task?

Buyer evidence still required

  • task ID
  • input request key
  • original question
  • prior response
  • poll history

Review inference: May an MCP server reuse an inputRequests key for a different question later in a task? Reject ambiguous request-key reuse before applying a delayed input response. Binds delayed in-task input to a unique request, distinct from consent versus external completion. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Reject ambiguous request-key reuse before applying a delayed input response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Each request key in inputRequests MUST be unique

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reject ambiguous request-key reuse before applying a delayed input response.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

May an operator add or remove ADK agents before resuming a stopped workflow

Question: May an operator add or remove ADK agents before resuming a stopped workflow?

The captured ADK Resume guide does not support changing a stopped workflow before resumption, such as adding or removing agents. Resume selects the earlier invocation ID with the applicable app, user and session through the API server or Runner path; the guide says ADK Web and CLI resume are not currently supported. Retain the stopped invocation and workflow definition rather than assuming a fresh request or changed graph resumes the same work.

Source: Google primary documentation: adk resume. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: May an operator add or remove ADK agents before resuming a stopped workflow?

Buyer evidence still required

  • ADK language and version
  • stopped invocation ID
  • app, user and session
  • workflow definition
  • saved completion state
  • resume API or Runner request

Review inference: May an operator add or remove ADK agents before resuming a stopped workflow? Require the applicable workflow definition before relying on recorded completion checkpoints. ADK states a specific unsupported resume mutation rather than Temporal replay compatibility rules. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the applicable workflow definition before relying on recorded completion checkpoints.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Workflow modification with Resume not supported; Resume a stopped workflow

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the applicable workflow definition before relying on recorded completion checkpoints.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MCP authorization URL handling

Question: Can an MCP client safely open an authorization URL merely because an MCP server supplied it?

The 2026-07-28 MCP security guidance requires validation of server-supplied authorization URLs, rejection of dangerous schemes and avoidance of shell execution when opening them. HTTP is restricted to loopback development; production authorization servers use HTTPS. This is a client URL-handling requirement, separate from the token’s resource-audience validation.

Source: Security Best Practices - Model Context Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an MCP client safely open an authorization URL merely because an MCP server supplied it?

Buyer evidence still required

  • Supplied authorization URL and parsed scheme/target
  • Expected authorization server and client URL-opening mechanism
  • Applicable MCP version and redirect validation evidence

Review inference: Validate the actual URL before opening it and preserve the authorization-server binding across the flow.

Suggested review condition: Refuse an unvalidated server-supplied URL or a shell-based opening path.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer client or redirect chain has been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent the authorization handoff from becoming an unreviewed client execution path.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A universal redirect-safety attestation or runtime protection from INDEX
  • No buyer client or redirect chain has been tested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP clients: Protocol fallback and explicit version requirements

Question: Does connecting successfully prove that an MCP client used the required protocol version?

The TypeScript SDK v2 guide documents a legacy default, automatic discovery with legacy fallback, and an explicit version pin that rejects an incompatible server. Successful automatic connection therefore does not prove use of the newer protocol. Check the negotiated mode and required features. This is documented client behaviour, not a test of your installed client or server.

Source: MCP TypeScript SDK v2: Protocol versions. Documentation checked 2026-10-12; no deployment validation is claimed.

Claim boundaries
  • successful connection proving the required protocol
  • identical defaults across SDK languages
  • tested buyer compatibility

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP discovery: Pagination and valid empty cursors

Question: Does one successful MCP tools/list response establish the complete tool inventory?

MCP specification 2026-07-28 supports cursor-based tools/list pagination. Servers choose page sizes and return nextCursor when more results exist. Cursors are opaque; an empty string is valid and must not be mistaken for end-of-results. A successful first page does not establish a complete inventory.

Source: MCP pagination. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does one successful MCP tools/list response establish the complete tool inventory?

Buyer evidence still required

  • Protocol version and authorization context
  • All list responses and continuation cursors
  • Terminal response and reconciled tool identifiers

Review inference: Tool admission review needs a complete inventory for the applicable caller context.

Suggested review condition: Refuse completeness when pagination stopped on a non-null cursor or used an assumed page size.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Server honesty, inventory stability and deployment permissions are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent an admission review from silently omitting tools on later pages.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete server inventory or authority from a first-page response
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP elicitation: Credentials belong outside form responses

Question: May an MCP server collect API keys or payment credentials through form elicitation?

MCP 2026-07-28 prohibits requesting passwords, API keys, access tokens or payment credentials through form elicitation and requires URL mode for those interactions. General contact information is not categorically prohibited. URL elicitation is separate from authorizing the MCP client's access to the server.

Source: MCP elicitation. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: May an MCP server collect API keys or payment credentials through form elicitation?

Buyer evidence still required

  • Negotiated MCP version, elicitation mode and requested fields
  • Requesting server and external URL identity with user consent
  • Credential routing, logging boundaries and client-to-server authorization

Review inference: A declaration review should classify requested fields and identify where secrets travel.

Suggested review condition: Refuse reliance on a credential-safe flow when secrets are requested through form elicitation or the external recipient is unverified.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer host behavior, recipient trust, credential storage and logging are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Recognize an inappropriate credential-collection path before delegating access to a tool.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof that a hosted page is trustworthy, a deployment follows the specification or credentials were never logged
  • A blanket ban on all personal information in forms or automatic permission to open an external URL
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP HTTP resumption depends on protocol revision

Question: Can an MCP client assume that Streamable HTTP always supports resuming a stream with Last-Event-ID?

MCP Streamable HTTP revision 2026-07-28 does not support resumable SSE streams through Last-Event-ID and instructs servers to ignore that header. Its compatibility section distinguishes earlier revisions that used session IDs and resumable streams; supporting those clients requires the corresponding older behaviour. A transport name alone therefore does not establish replay or resumption support.

Source: Streamable HTTP - Model Context Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an MCP client assume that Streamable HTTP always supports resuming a stream with Last-Event-ID?

Buyer evidence still required

  • Client and server protocol revisions actually used
  • Documented transport recovery and state behaviour
  • Request outcome evidence and authority before any repeat invocation

Review inference: Pin the implemented revision and recovery contract before assuming that a dropped response can be recovered without a new operation.

Suggested review condition: Do not retry a consequential tool call as though Last-Event-ID guaranteed recovery when the implemented revision provides no such mechanism.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Installed compatibility support, lost response content and external effects are not established by the specification.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid an unsafe repeat invocation caused by an incorrect transport compatibility assumption.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal stream replay, exactly-once actions or changes to INDEX's existing MCP transport
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP July 2026: Core and application state

Question: Does MCP's July 2026 stateless core mean an application cannot keep state?

The MCP July 2026 release describes a stateless protocol core. Applications may still maintain their own state explicitly; the protocol model alone does not establish application retention, isolation or recovery behaviour.

Source: MCP July 2026 release. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • stateless application storage
  • configured retention policy
  • tested recovery or isolation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP July 2026: Extension support boundary

Question: Does MCP's extension framework establish support for every optional capability?

The MCP July 2026 release introduces a formal extension framework and authorisation changes. An extension mechanism does not establish that a client and server implement the same optional capabilities or enforce them correctly; review their declared versions and behaviour.

Source: MCP July 2026 release. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • universal optional-feature support
  • tested extension interoperability
  • correct authorisation enforcement

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP legacy initialization and capability boundaries

Question: For MCP 2025-11-25, does successful initialization permit calls to every client-advertised capability?

MCP 2025-11-25 requires initialize first, negotiation of version and capabilities, and a subsequent initialized notification before normal operation. Successful initialization does not mean every capability advertised by one participant is supported by the other. The reviewed 2026-07-28 protocol instead documents per-request version compatibility without that initialization handshake.

Source: Lifecycle - Model Context Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: For MCP 2025-11-25, does successful initialization permit calls to every client-advertised capability?

Buyer evidence still required

  • Client/server protocol versions
  • Initialization exchange for the legacy edition
  • Capability declarations and intended operation

Review inference: Apply the lifecycle rules for the negotiated protocol edition and verify the specific capability before use.

Suggested review condition: Refuse capability assumptions from handshake success or from applying another edition’s lifecycle.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual consumer compatibility and operation support remain untested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent version-mismatched integration assumptions at handover.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A change to the existing INDEX MCP contract
  • Actual consumer compatibility and operation support remain untested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP progress and terminal action evidence

Question: Can MCP progress notifications establish that an external action completed successfully?

MCP progress guidance for revision 2026-07-28 permits optional progress notifications for an active request. A total value is optional, progress values increase, and notifications must stop after the operation completes. Progress updates are not the terminal request result, and their numeric values do not independently establish the external business outcome.

Source: Progress - Model Context Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can MCP progress notifications establish that an external action completed successfully?

Buyer evidence still required

  • Progress token and corresponding request identity
  • Terminal result or failure for the operation
  • External outcome evidence required by the buyer

Review inference: Retain the terminal result and action-specific evidence instead of turning a progress display into a success receipt.

Suggested review condition: Do not close an action as successful from a progress notification or apparent completion percentage alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The meaning chosen for progress units, whether the request completed and the external effect remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Distinguish user-interface progress from evidence that delegated work actually finished.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authoritative completion from progress values or an assurance that every server emits progress
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP reauthorisation scope accumulation

Question: Should an MCP client request only the newest challenged scope during reauthorisation?

MCP 2026-07-28 describes computing the union of the client's previously requested scope set and the current challenge before reauthorisation. It also recommends including challenged scopes alongside previously granted ones to avoid losing permissions for other operations. This is request-set continuity, not evidence that the authorisation server granted the union.

Source: MCP HTTP authorization, specification 2026-07-28. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Should an MCP client request only the newest challenged scope during reauthorisation?

Buyer evidence still required

  • client/resource and authorisation-server context
  • previous requested/granted scope sets and new challenge
  • reauthorisation request and resulting effective grant

Review inference: Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers. The existing record compares a challenge with advertised scopes and initial selection. This review concerns accumulation across successive operation challenges and avoiding accidental loss of earlier requested permissions. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Step-Up Authorization Flow; previously requested scope set

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MCP refresh versus additional authority

Question: Can refreshing an MCP access token authorise scopes that were never granted?

RFC 6749 section 6 prohibits a refresh request from including scopes not originally granted by the resource owner. MCP 2026-07-28 describes increased-scope reauthorisation after insufficient_scope, rather than treating token renewal as new authority. A refreshed token can renew existing access; possession or successful refresh alone does not establish a grant for newly challenged scopes.

Source: RFC 6749: OAuth 2.0, section 6 refresh scope. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can refreshing an MCP access token authorise scopes that were never granted?

Buyer evidence still required

  • resource/operation and sanitised scope challenge
  • originally granted and requested scopes
  • grant type, provider reauthorisation result and effective new scope

Review inference: Refuse additional-authority approval from refresh success alone. Distinguish expiry from insufficient scope, verify the existing grant and perform the applicable reauthorisation flow or stop. A fresh interactive consent prompt is not guaranteed for every provider. The existing OAuth review concerns token validity, binding and ambiguous invalid_grant causes. This decision concerns the separate scope ceiling on refresh and the evidence required for additional authority. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse additional-authority approval from refresh success alone. Distinguish expiry from insufficient scope, verify the existing grant and perform the applicable reauthorisation flow or stop. A fresh interactive consent prompt is not guaranteed for every provider.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Refreshing an Access Token; Step-Up Authorization Flow

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse additional-authority approval from refresh success alone. Distinguish expiry from insufficient scope, verify the existing grant and perform the applicable reauthorisation flow or stop. A fresh interactive consent prompt is not guaranteed for every provider.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MCP Registry: Publisher namespace is a limited identity check

Question: Does an authenticated MCP Registry publisher establish that its server is approved for our tools?

The official MCP Registry requires publication authentication tied to a GitHub user or organization namespace, or to a domain namespace established through DNS or HTTP proof. This identifies the publication namespace. It does not establish the buyer-approved executable, deployed endpoint or permission policy; those require separate review.

Source: MCP Registry: Publishing authentication. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Does an authenticated MCP Registry publisher establish that its server is approved for our tools?

Buyer evidence still required

  • The registry server name, version and authenticated namespace.
  • The expected publisher and the exact package or endpoint selected.
  • The buyer-approved tool inventory, permission scope and deployment identity.

Suggested review condition: Do not use registry publication authentication as certification or as approval of executable behavior and granted permissions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The registry server name, version and authenticated namespace. The expected publisher and the exact package or endpoint selected. The buyer-approved tool inventory, permission scope and deployment identity.

Optional saved evidence: A tool buyer needs to distinguish registry publication identity from approval of the server that will actually run.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP repeated scope-challenge retry boundary

Question: How long should an MCP client keep retrying after repeated insufficient_scope challenges?

MCP 2026-07-28 describes retrying the original request with new authorisation only a few times before treating it as a permanent authorisation failure. It recommends retry limits and tracking scope-upgrade attempts for the same resource and operation. The specification does not supply one universal numeric retry count.

Source: MCP HTTP authorization, specification 2026-07-28. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: How long should an MCP client keep retrying after repeated insufficient_scope challenges?

Buyer evidence still required

  • resource/operation and sanitised challenge sequence
  • configured retry cap and tracked scope-upgrade attempts
  • grant outcomes, terminal refusal and separate action evidence

Review inference: Refuse unbounded reauthorisation loops or automatic widening of authority to make a request pass. Set and record a bounded policy, stop on exhaustion and retain sanitised failure evidence. This limit does not establish idempotency or prove a prior business action did not execute. The existing record caps request duration despite progress. This review bounds repeated authority upgrades and retries by resource/operation, a different failure and refusal decision from transport timeout. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse unbounded reauthorisation loops or automatic widening of authority to make a request pass. Set and record a bounded policy, stop on exhaustion and retain sanitised failure evidence. This limit does not establish idempotency or prove a prior business action did not execute.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Retry the original request; same resource and operation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse unbounded reauthorisation loops or automatic widening of authority to make a request pass. Set and record a bounded policy, stop on exhaustion and retain sanitised failure evidence. This limit does not establish idempotency or prove a prior business action did not execute.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MCP state handles and authentication

Question: Can an MCP application state handle or legacy session ID replace authentication?

MCP security guidance for revision 2026-07-28 requires verification of inbound requests and prohibits using application state handles for authentication. It recommends unpredictable handles bound to the authenticated principal. The 2025-11-25 guidance applies the same authentication warning to that revision's session IDs. These are version-specific state mechanisms, not bearer authority to act.

Source: Security Best Practices - Model Context Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an MCP application state handle or legacy session ID replace authentication?

Buyer evidence still required

  • Implemented MCP revision and state mechanism
  • Request authentication and principal-to-state binding
  • State lifecycle and access checks for the resumed operation

Review inference: Verify identity and state ownership separately when resuming an interaction; possession of a handle alone is insufficient.

Suggested review condition: Do not accept a resumed action using a state handle or legacy session ID as its only authentication evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The deployed version, authentication checks and state isolation were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Check identity continuity when an agent resumes stateful work across requests.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authentication or authorisation from a state identifier or an INDEX protocol upgrade
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP Tasks: Cancellation acknowledgement does not establish stopped work

Question: Does a successful MCP tasks/cancel response prove the underlying work stopped?

In the MCP Tasks extension 2026-07-28, tasks/cancel acknowledges cancellation intent. Processing is eventually consistent: observable status may remain non-terminal, and work may reach another terminal state. Cancellation is cooperative; the server is not required to stop the work or eventually report cancelled. The ordinary notifications/cancelled notification must not be used to cancel a task.

Source: MCP Tasks extension. Documentation checked 2026-10-23; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a successful MCP tasks/cancel response prove the underlying work stopped?

Buyer evidence still required

  • Negotiated Tasks extension version, task identifier and original action identity
  • Cancellation request, acknowledgement and any subsequently observed status
  • External outcome and deduplication or reconciliation evidence before repeating the action

Review inference: A retry decision needs action-specific outcome evidence; acknowledgement alone cannot establish that a replacement action is safe.

Suggested review condition: Refuse a stopped-work or safe-retry conclusion supported only by the tasks/cancel acknowledgement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the server honoured cancellation and whether an external effect occurred are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid duplicate purchases or writes when a client interprets a cancellation acknowledgement as stopped work.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Rollback of external effects or permission to repeat a potentially completed action
  • Applicability to older experimental MCP task protocols or evidence that INDEX implements task execution
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP Tasks: Expiry limits result availability, not external outcome certainty

Question: Does expiry of an MCP task prove its external action failed or never happened?

The MCP Tasks extension 2026-07-28 defines ttlMs from task creation, with null representing no limit. The value can change during the task lifetime. After expiry, a server may mark the task failed and later delete it; the task may no longer be usable. These retention and protocol-state rules do not establish the outcome of an external payment or write.

Source: MCP Tasks extension. Documentation checked 2026-10-23; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does expiry of an MCP task prove its external action failed or never happened?

Buyer evidence still required

  • Task creation timestamp, observed ttlMs values and Tasks extension version
  • Previously captured task results, errors and action correlation identifiers
  • External system outcome evidence and retry deduplication state

Review inference: Clients that need later reconciliation should retain bounded result and action identifiers before relying on a server task record that may expire.

Suggested review condition: Refuse an external-failure or safe-retry claim inferred solely from task expiry, disappearance or an expiry-related failed status.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual result retention, discarded state and the external action outcome are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Preserve enough evidence to reconcile a purchase or write when its asynchronous task result is no longer available.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof that expired work was cancelled, rolled back or never completed
  • Guaranteed availability of task results after expiry or safe repetition without reconciliation
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP tool-change notification coverage

Question: Does absence of an MCP tools/list_changed notification prove a cached tool schema is unchanged?

In the reviewed 2026-07-28 tools specification, servers advertising listChanged should notify clients whose subscriptions/listen stream requests toolsListChanged. This is a SHOULD requirement tied to capability and subscription context. Silence alone is not a verified immutable tool inventory or schema.

Source: Tools - Model Context Protocol. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does absence of an MCP tools/list_changed notification prove a cached tool schema is unchanged?

Buyer evidence still required

  • Pinned protocol edition and tool description
  • Server listChanged capability
  • Subscription state and refreshed inventory

Review inference: Recheck the authorized tool description when freshness matters and record the capability and subscription evidence.

Suggested review condition: Do not approve unchanged schema solely from notification silence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual server changes, missed notifications and cache freshness are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid executing against an unverified stale tool definition.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Live drift detection supplied by current INDEX
  • Actual server changes, missed notifications and cache freshness are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP: A result envelope can contain a failed tool action

Question: Does a successful MCP JSON-RPC result mean the underlying tool action succeeded?

MCP 2026-07-28 separates protocol errors from tool execution errors. API, validation and business-logic failures can be returned in a normal result with isError set to true. A JSON-RPC result envelope alone does not establish action success, and a reported success still needs the action-specific outcome evidence required by the buyer.

Source: MCP: Tools. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Does a successful MCP JSON-RPC result mean the underlying tool action succeeded?

Buyer evidence still required

  • The correlated tools/call request and complete returned result.
  • The isError value, result content and action-specific outcome fields.
  • The downstream record or other evidence required to close the action.

Suggested review condition: Refuse a completed-action claim based only on transport or JSON-RPC success, or while a tool error remains unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The correlated tools/call request and complete returned result. The isError value, result content and action-specific outcome fields. The downstream record or other evidence required to close the action.

Optional saved evidence: An audit owner must classify tool execution outcomes from the tool result, rather than counting all received protocol responses as completed actions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP: Access tokens must match the resource audience

Question: Can an MCP server accept a valid token issued for a different service?

MCP 2026-07-28 requires HTTP resource servers to validate that access tokens were issued for their own intended audience. Clients must not send unrelated tokens, and servers must not accept or transit tokens for other resources. Token validity alone is not evidence of authority for the target MCP resource.

Source: MCP: Authorization. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Can an MCP server accept a valid token issued for a different service?

Buyer evidence still required

  • The intended MCP resource and its authorization-server metadata.
  • Token audience and issuer validation evidence without disclosing token secrets.
  • The gateway credential flow and separately authorised upstream access.

Suggested review condition: Refuse a claim of valid target authority when audience binding is missing, mismatched or replaced by token passthrough.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The intended MCP resource and its authorization-server metadata. Token audience and issuer validation evidence without disclosing token secrets. The gateway credential flow and separately authorised upstream access.

Optional saved evidence: Platform buyers need to verify the credential-to-resource binding when gateways connect an agent to multiple services.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP: Progress resets do not remove the maximum deadline

Question: Can ongoing MCP progress notifications justify waiting indefinitely for a request?

MCP revision 2026-07-28 permits resetting a request timeout on progress notifications but recommends an enforced maximum timeout regardless of progress. It also recommends configurable per-request timeouts.

Source: MCP cancellation and timeouts, revision 2026-07-28. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can ongoing MCP progress notifications justify waiting indefinitely for a request?

Buyer evidence still required

  • negotiated protocol revision
  • request and maximum timeout settings
  • progress timestamps
  • terminal or cancellation evidence

Review inference: Do not equate a refreshed idle timer with a bounded total duration or successful action. Check the maximum deadline and reconcile any ambiguous external result after cancellation. These are SHOULD requirements, not verified client behaviour. This selects an absolute waiting bound despite progress, rather than deciding whether a progress value proves completion. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not equate a refreshed idle timer with a bounded total duration or successful action. Check the maximum deadline and reconcile any ambiguous external result after cancellation. These are SHOULD requirements, not verified client behaviour.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Timeouts

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not equate a refreshed idle timer with a bounded total duration or successful action. Check the maximum deadline and reconcile any ambiguous external result after cancellation. These are SHOULD requirements, not verified client behaviour.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MCP: SDK support and migration checks

Question: Does an SDK supporting a protocol release make an existing MCP integration a drop-in upgrade?

The MCP 2026-07-28 announcement identifies TypeScript, Python, Go and C# SDK support and Rust support in beta at that release. It also flags migration work, especially for integrations using session identifiers. Pin the package and protocol versions and review the applicable migration notes. A release-support statement does not verify an installed client's compatibility, optional features or successful deployment.

Source: MCP: The 2026-07-28 Specification, SDK support. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • current maturity inferred from a historical announcement
  • drop-in package or protocol compatibility
  • tested client-server interoperability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP: Tool annotations describe hints, not enforced authority

Question: Can an agent rely on MCP readOnlyHint, destructiveHint or idempotentHint as enforced permissions?

MCP 2026-07-28 defines ToolAnnotations as hints that are not guaranteed to describe behavior faithfully, and warns against tool-use decisions based on untrusted servers' annotations. readOnlyHint describes mutation, destructiveHint concerns destructive rather than additive updates, and idempotentHint concerns repeated arguments. These declarations do not establish a tested authorization or execution boundary.

Source: Schema Reference - Model Context Protocol. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an agent rely on MCP readOnlyHint, destructiveHint or idempotentHint as enforced permissions?

Buyer evidence still required

  • Negotiated MCP version, server identity and complete annotated tool schema.
  • Effective execution identity, permissions and independently enforced restrictions.
  • Action-specific side effects, retry behavior and authorized task scope.

Review inference: A hint cannot replace an authority check or evidence that repeated external effects are prevented.

Suggested review condition: Refuse automatic approval or safe-retry guarantees derived solely from tool annotations.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The server's actual behavior and permission enforcement have not been tested.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck negotiated specification, server version and annotation changes before relying on a tool inventory.

Optional saved evidence: Identify which declared controls can support an agent authority decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Certified read-only execution, granted permission or verified idempotency
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCP: Tool inventory depends on request authority

Question: Can an earlier MCP tools list prove which tools remain available under changed credentials?

MCP 2026-07-28 allows the available tool set to change over time and vary with the authorization presented on each request. Tool listing supports pagination and caching; list-change notifications use an opted-in subscription. An earlier inventory does not establish the current inventory for a different credential context.

Source: MCP: Tools. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Can an earlier MCP tools list prove which tools remain available under changed credentials?

Buyer evidence still required

  • The negotiated protocol version and authorization context for each inventory.
  • All tool-list pages, cache metadata and relevant change notifications.
  • The current credential context and a refreshed comparison of affected tools.

Suggested review condition: Do not approve continued tool access from a stale or incomplete inventory whose authorization context differs from the proposed request.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The negotiated protocol version and authorization context for each inventory. All tool-list pages, cache metadata and relevant change notifications. The current credential context and a refreshed comparison of affected tools.

Optional saved evidence: An agent gateway operator needs a current, correctly scoped inventory when credentials or permissions change.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MCPB: Registry hash metadata still needs client verification

Question: Does an MCPB fileSha256 in the Registry prove the downloaded bundle was verified?

The MCP Registry package guide requires MCPB metadata to include a fileSha256 value, but states that the Registry does not validate that hash. Clients validate the hash before installation; downstream registries may also validate it. A published hash is therefore a reference to check, not evidence that a particular download was checked or is safe to execute.

Source: MCP Registry: Supported package types. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Authority & Action Evidence

Evidence to request before relying on this claim

Claim to check: Does an MCPB fileSha256 in the Registry prove the downloaded bundle was verified?

Buyer evidence still required

  • The exact MCPB URL, registry version and declared fileSha256.
  • The downloaded bundle digest and the client verification result.
  • The expected publisher and separately reviewed execution permissions.

Suggested review condition: Do not mark bundle integrity verified from metadata alone or infer safe behavior merely from a matching digest.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The exact MCPB URL, registry version and declared fileSha256. The downloaded bundle digest and the client verification result. The expected publisher and separately reviewed execution permissions.

Optional saved evidence: An installer operator must bind the reviewed MCPB package metadata to the actual bundle before granting local tool authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration, actual data erasure, effective access or completed business actions
  • Legal advice, compliance determination, vendor certification or safety assurance
  • Runtime enforcement, permission to act or expanded licensed-checker coverage

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Mem0: History inputs are not a per-fact source proof

Question: Does a Mem0 memory-history response prove which exact source sentence supports each stored fact?

The Mem0 Platform history schema describes entries for a memory ID, conversation input with roles and content, old and new memory text, event type and timestamps. It describes conversation-level change context, not a guaranteed per-fact source-span mapping.

Source: Mem0 Platform memory history API. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Mem0 memory-history response prove which exact source sentence supports each stored fact?

Buyer evidence still required

  • memory ID and history entries
  • source message identifiers
  • fact-to-source mapping
  • Platform API version

Review inference: Use history to reconstruct the recorded change, but refuse exact sentence attribution or factual verification without a separately retained fact-to-source mapping. This review does not assert absence of other product features. This assesses attribution granularity in a history response, not whether an export includes every backing store. Operational review inference; no deployment outcome was observed.

Suggested review condition: Use history to reconstruct the recorded change, but refuse exact sentence attribution or factual verification without a separately retained fact-to-source mapping. This review does not assert absence of other product features.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. old_memory; conversation input

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Use history to reconstruct the recorded change, but refuse exact sentence attribution or factual verification without a separately retained fact-to-source mapping. This review does not assert absence of other product features.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Mem0: Mixed raw and inferred inserts can duplicate a fact

Question: Does storing a fact through both raw and inferred Mem0 add paths produce independent corroborating evidence?

Mem0 documents that infer=False stores the supplied payload without inference and can admit duplicates. Adding the same content later with infer=True can create a second memory.

Source: Mem0 memory add. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does storing a fact through both raw and inferred Mem0 add paths produce independent corroborating evidence?

Buyer evidence still required

  • original input identity
  • inference mode per insert
  • returned memory IDs
  • source relationships

Review inference: Do not count matching memories as independent corroboration without comparing original sources and ingestion mode. Reconcile duplicate identities rather than inferring multiple independent observations. Duplicate provenance from mixed ingestion modes differs from explicit correction or removal of a contradicted fact. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not count matching memories as independent corroboration without comparing original sources and ingestion mode. Reconcile duplicate identities rather than inferring multiple independent observations.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. infer=False; duplicates

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not count matching memories as independent corroboration without comparing original sources and ingestion mode. Reconcile duplicate identities rather than inferring multiple independent observations.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Mem0: New-turn extraction can use earlier conversation context

Question: Is the latest add payload the complete source context for a new Mem0 Platform memory?

Mem0 Platform documents automatic use of earlier messages sharing the relevant user and optional run identifiers when extracting from newly submitted turns. The latest payload can therefore be only part of the extraction context.

Source: Mem0 memory add. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is the latest add payload the complete source context for a new Mem0 Platform memory?

Buyer evidence still required

  • new message payload
  • earlier scoped messages
  • user and run identifiers
  • resulting memory IDs

Review inference: Do not assign sole-source provenance to the latest payload without reconciling earlier contextual messages and entity scope. This documented Platform behaviour is not an OSS guarantee or proof that the inferred fact is correct. The source context used to derive a new memory differs from whether adding a corrected fact removes an older one. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not assign sole-source provenance to the latest payload without reconciling earlier contextual messages and entity scope. This documented Platform behaviour is not an OSS guarantee or proof that the inferred fact is correct.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Automatic conversation context

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not assign sole-source provenance to the latest payload without reconciling earlier contextual messages and entity scope. This documented Platform behaviour is not an OSS guarantee or proof that the inferred fact is correct.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Mem0: Provenance filters depend on the storage adapter

Question: Does a successful Mem0 OSS search prove every provenance metadata filter was applied?

Mem0 OSS documents different metadata-filter support across vector stores. Some unsupported operators are ignored or reduced to equality, and the reviewed Weaviate adapter table limits filtering to exact user, agent and run identifiers.

Source: Mem0 OSS metadata filtering. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a successful Mem0 OSS search prove every provenance metadata filter was applied?

Buyer evidence still required

  • OSS SDK and vector-store adapter version
  • submitted filter tree
  • returned metadata
  • known included and excluded fixtures

Review inference: Refuse a provenance-filtered result claim from request success alone. Check the exact adapter/version and returned records against each requested clause; metadata labels are not independently verified source facts. Backend translation of search metadata predicates differs from the existing managed delete-all entity wildcard and project-erasure boundary. Operational review inference; no deployment outcome was observed.

Suggested review condition: Refuse a provenance-filtered result claim from request success alone. Check the exact adapter/version and returned records against each requested clause; metadata labels are not independently verified source facts.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Vector store support varies widely; If an operator is unsupported

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a provenance-filtered result claim from request success alone. Check the exact adapter/version and returned records against each requested clause; metadata labels are not independently verified source facts.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Mem0: Retrieval score explains ranking, not truth

Question: Does a high Mem0 OSS search score establish that a remembered statement is factually reliable?

Mem0 documents OSS score_details as a breakdown of semantic similarity, normalized BM25, entity boost, combined score and filtering threshold. The optional explain flag exposes how a result ranked.

Source: Mem0 memory search. Documentation checked 2026-10-31; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a high Mem0 OSS search score establish that a remembered statement is factually reliable?

Buyer evidence still required

  • query and explain output
  • retrieval configuration
  • memory text
  • underlying source and attribution

Review inference: Treat the score as retrieval evidence, not calibrated factual confidence or proof of user assertion. Verify source content and attribution separately before acting on the remembered statement. Interpreting ranking evidence is distinct from export completeness or memory-retention inventory. Operational review inference; no deployment outcome was observed.

Suggested review condition: Treat the score as retrieval evidence, not calibrated factual confidence or proof of user assertion. Verify source content and attribution separately before acting on the remembered statement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Explain OSS search scores

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Treat the score as retrieval evidence, not calibrated factual confidence or proof of user assertion. Verify source content and attribution separately before acting on the remembered statement.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Metadata/expiry-only update can change retention without changing text

Question: Can a Mem0 metadata-only update alter expiry without changing memory text?

The documented OSS update accepts metadata and/or expiration changes while retaining text, and explicitly allows clearing expiration with None/null.

Source: Mem0 primary documentation: mem0 update. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Mem0 metadata-only update alter expiry without changing memory text?

Buyer evidence still required

  • SDK version
  • before/after text hash
  • expiration and metadata
  • update payload
  • approval

Review inference: Can a Mem0 metadata-only update alter expiry without changing memory text? Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy. Metadata/expiry-only update can change retention without changing text. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. None clears it

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Review retention fields independently of text diffs; unchanged content does not prove an unchanged expiry policy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Microsoft Agent Framework: Explicit workflows

Question: What does Microsoft Agent Framework workflow support establish about execution?

Microsoft describes workflows that connect agents and functions through explicit execution paths, with functional and graph-based approaches. This supports structured orchestration. Available features depend on language and version; documentation alone does not verify a particular workflow’s ordering, failure handling or permissions.

Source: Microsoft Agent Framework overview. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • uniform feature parity across languages
  • verified failure recovery
  • authorisation of workflow actions

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Agent Framework: Middleware and streaming output

Question: Can adding agent middleware change streaming behaviour or leave output unchecked?

Microsoft's .NET Agent Framework guide distinguishes run and streaming middleware. Supplying only the non-streaming handler makes streaming invocations use non-streaming mode. Its shared handler preserves streaming but cannot intercept or override output. Choose the handler for the required input or output check, then test the installed version. This documents API behaviour, not a verified safety control.

Source: Microsoft Agent Framework: Agent Middleware (.NET). Documentation checked 2026-10-11; no deployment validation is claimed.

Claim boundaries
  • output inspection by an input-only handler
  • unchanged streaming after middleware registration
  • tested enforcement in an application

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Agent Framework: Migration compatibility checks

Question: Is moving from Semantic Kernel to Microsoft Agent Framework a drop-in replacement?

Microsoft provides a migration guide with changes to packages, agent construction, session handling, tool registration and invocation results. The Python and .NET paths have language-specific mappings. Treat these as migration work items and verify the application behaviour after conversion. The successor relationship alone does not demonstrate equivalent outputs, preserved state or improved performance for an existing agent.

Source: Semantic Kernel to Microsoft Agent Framework Migration Guide. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • drop-in compatibility
  • equivalent application behaviour
  • preserved stored sessions without migration checks
  • measured performance improvement

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Agent Framework: Session-state boundary

Question: Does Agent Framework session-state support prove durable or isolated recovery?

Microsoft lists session-state management among Agent Framework’s building blocks for context and memory. That capability does not establish a particular application’s persistence guarantees, cross-user isolation or recovery behaviour. Those depend on the selected implementation and need separate evidence.

Source: Microsoft Agent Framework overview. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • durable recovery guarantee
  • verified session isolation
  • correct memory retention

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Copilot: Attachment retention labels cover a copy

Question: Does an automatic retention label for a Copilot cloud attachment label the original file and chat too?

Microsoft describes creating a retained copy of supported cloud attachments in the Preservation Hold library. The label applies to that copy, not the original file or message. Supported Copilot references can therefore create a separately governed evidence copy requiring its own inventory.

Source: Microsoft Purview automatic retention labels. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an automatic retention label for a Copilot cloud attachment label the original file and chat too?

Buyer evidence still required

  • The supported attachment and reference event.
  • The retained copy and applied label.
  • Separate original-file and message policies.

Suggested review condition: Do not claim that one attachment label establishes retention or deletion for all three objects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The supported attachment and reference event. The retained copy and applied label. Separate original-file and message policies.

Optional saved evidence: A data custodian must distinguish the cited version, original document and conversation before retention or exit decisions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete capture of unsupported, draft or unavailable attachments
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Copilot: Offboarding can preserve AI messages

Question: Does deleting a Microsoft 365 user account erase Copilot messages that are subject to retention?

Microsoft documents that retained Copilot and other covered AI-app messages remain in an inactive mailbox after the user account is deleted. Previously applicable retention continues, and the content remains discoverable through eDiscovery. Account removal is not equivalent to message erasure.

Source: Microsoft Purview retention for Copilot. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a Microsoft 365 user account erase Copilot messages that are subject to retention?

Buyer evidence still required

  • The deleted account and covered AI applications.
  • Policies applied before mailbox inactivation.
  • Inactive-mailbox and eDiscovery evidence.

Suggested review condition: Do not close an erasure claim solely from account deletion while retained mailbox content remains in scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The deleted account and covered AI applications. Policies applied before mailbox inactivation. Inactive-mailbox and eDiscovery evidence.

Optional saved evidence: An offboarding owner must reconcile retained AI messages with the user-account closure.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Legal justification for retention or verified deletion of a particular mailbox
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Copilot: Recipient conversations survive sharing changes

Question: Does disabling Copilot content sharing remove conversations recipients already continued?

Microsoft explains that continuing a shared session or response creates a separate conversation in the recipient history. Sharing-setting changes affect new sharing attempts and do not remove existing recipient copies. The source conversation and its sharing link are not a complete downstream-copy inventory.

Source: Microsoft Copilot content sharing. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does disabling Copilot content sharing remove conversations recipients already continued?

Buyer evidence still required

  • The shared session or response.
  • Recipients who created continued conversations.
  • Current sharing settings and separate copy-handling evidence.

Suggested review condition: Do not assert recall or erasure of recipient conversations from a sharing-setting change alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The shared session or response. Recipients who created continued conversations. Current sharing settings and separate copy-handling evidence.

Optional saved evidence: An AI information owner must account for recipient-held copies when restricting sharing or reviewing an exit.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof that no recipient copied or exported content elsewhere
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Graph delta: Replays and synchronization resets

Question: Can Microsoft Graph delta responses be treated as an ordered, duplicate-free action ledger?

Graph delta responses can repeat entities and replay changes across responses; clients must not assume a particular sequence. A 410 Gone reset can require a new full synchronization. Delta supports state synchronization, but these behaviors prevent treating its responses alone as an ordered, duplicate-free history of agent actions.

Source: Use delta query to track changes in Microsoft Graph data. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can Microsoft Graph delta responses be treated as an ordered, duplicate-free action ledger?

Buyer evidence still required

  • Resource-specific delta scope and continuation history
  • Stable entity identifiers and replay handling
  • Reset intervals and independent action evidence

Review inference: Synchronization records need separate causal evidence before supporting an action audit.

Suggested review condition: Refuse exact action counts or chronology derived only from repeated delta rows or an unresolved reset.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Missed changes, actor identity and causal ordering are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid counting synchronization replays as new agent actions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Ordered audit history, unique action counts or gap-free synchronization
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Graph mail: Accepted is not delivered

Question: Does a successful Microsoft Graph sendMail response prove the recipient received the message?

sendMail returns 202 Accepted without a response body. Microsoft states this does not establish completed processing; Exchange Online limits and throttling still affect delivery. An agent should distinguish accepted submission from verified delivery.

Source: Microsoft Graph: user sendMail. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a successful Microsoft Graph sendMail response prove the recipient received the message?

Buyer evidence still required

  • Authorised sender, recipients and message scope.
  • Submission status and correlation evidence.
  • Available transport outcome or delivery evidence.

Suggested review condition: Report submission acceptance accurately; do not claim recipient delivery from 202 alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Sender, recipients, submission result and transport evidence.

Optional saved evidence: Save the evidence boundary behind a claimed outbound communication.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Graph: Batch success and individual failures

Question: Does HTTP 200 for a Microsoft Graph batch prove every agent action in it succeeded?

A parseable Graph batch can return HTTP 200 while individual responses fail. Each response has its own identifier and status; throttling applies per request, and requests depending on a failed request receive 424. Recovery must use those individual results rather than the outer status alone.

Source: Microsoft Graph: Combine multiple HTTP requests using JSON batching. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does HTTP 200 for a Microsoft Graph batch prove every agent action in it succeeded?

Buyer evidence still required

  • Batch request identifiers, target API versions and dependsOn relationships.
  • Every individual response status, headers and business result.
  • A justified retry or reconciliation plan for each failed or uncertain operation.

Suggested review condition: Decline all-actions-complete claims based on the batch HTTP code; inspect each result and dependency before selecting recovery actions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Batch request identifiers, target API versions and dependsOn relationships. Every individual response status, headers and business result. A justified retry or reconciliation plan for each failed or uncertain operation.

Optional saved evidence: Multi-step directory or content automation needs to separate completed operations, rejected requests and failed dependencies before deciding what to repeat.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Atomic batch execution, automatic rollback or safe replay of already completed operations
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Graph: Delegated and application authority

Question: Does a Microsoft Graph permission name mean the same access with and without a signed-in user?

Microsoft distinguishes delegated access on behalf of a user from application access under the app identity. Delegated permissions are bounded by the access of that user, while application permissions can reach data without a user present. Review the permission type, consent and resource controls before judging the scope from its name.

Source: Microsoft Graph delegated and application permission scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The permission name alone describes the app data-access boundary.

Buyer evidence still required

  • Granted permissions including delegated or application type
  • User permissions or application resource restrictions
  • Consent record and any additional role requirements

Suggested review condition: Require permission-type and effective-resource evidence before approving broad organizational access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck grants, consent, user roles and application resource limits.

Optional saved evidence: Retain the access-model distinction behind a Microsoft 365 integration decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Learn MCP: Public documentation, not tenant inspection

Question: Can Microsoft Learn MCP verify how my Microsoft tenant is configured?

The public server searches and fetches Microsoft documentation and code samples without authentication. It does not inspect the buyer tenant. Its tool definitions can change, and optional search token budgets can truncate results. A documentation answer is therefore a starting point for a configuration review, not evidence that a control is enabled.

Source: Microsoft Learn MCP public documentation tools. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Public hosted documentation server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Microsoft publishes the hosted Learn documentation server.

Documented by publisher. Microsoft Learn MCP public documentation tools

Purpose

Find documentation, fetch an article and locate code samples.

Documented by publisher. Microsoft Learn MCP public documentation tools

Read capability

Public Microsoft documentation and published examples.

Documented by publisher. Microsoft Learn MCP public documentation tools

Write capability

No tenant-changing operation is described in the reviewed tool set.

Documented by publisher. Microsoft Learn MCP public documentation tools

Authentication

No authentication is required for the public endpoint.

Documented by publisher. Microsoft Learn MCP public documentation tools

Permission surface

Public documentation access does not grant tenant or subscription access.

Documented by publisher. Microsoft Learn MCP public documentation tools

Data leaving the environment

Search text and document requests go to the hosted service; the client receives returned content.

Review inference. Microsoft Learn MCP public documentation tools

Failure modes to consider

Cached tool definitions and truncated search output can affect retrieval.

Review inference. Microsoft Learn MCP public documentation tools

Unknowns and applicability

Tenant settings, licensed features and current application behaviour are not observed.

Not established

Suggested refusal or clarification condition

Require tenant evidence before converting a documentation description into an enabled-control claim.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Tool schema, document versions and search-output limits.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the distinction between a published feature and a control demonstrated in the buyer environment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Microsoft Purview: Retention depends on licences and policies

Question: Does buying an audit licence preserve every existing Microsoft 365 audit record for longer?

Microsoft ties audit retention to licensing, record coverage and policy priority. Custom policies can override defaults, and later changes do not update previously committed audit items. Verify the applicable identity, record type and policy at ingestion before claiming a complete extended history.

Source: Microsoft Purview audit retention licensing and policy priority. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A premium audit purchase automatically extends all historical audit records.

Buyer evidence still required

  • Licence assignment and audited identity for the relevant period
  • Matching retention policies and their priorities
  • Ingestion dates and available historical records

Suggested review condition: Do not promise retrospective retention or uniform coverage from a product licence alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck policy priority, record categories and licence assignments.

Optional saved evidence: Save the licence, policy and historical-scope questions used in an audit procurement decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Miro MCP: Team selection and board changes

Question: Can my agent use a Miro board from a different team after one connection?

Miro documents a team-specific OAuth connection and existing board-access controls. Its tools can read and change board content, so a request to summarise a board should identify both the authorised team and allowed actions. Enterprise availability also depends on administrative enablement.

Source: Miro MCP capabilities, team authorization and Enterprise approval. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Miro hosted server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Miro provides the hosted MCP service.

Documented by publisher. Miro MCP capabilities, team authorization and Enterprise approval

Purpose

Use board context for summaries, diagrams and collaborative work.

Documented by publisher. Miro MCP capabilities, team authorization and Enterprise approval

Read capability

Reads board content and comments available to the user.

Documented by publisher. Miro MCP capabilities, team authorization and Enterprise approval

Write capability

Creates or updates board content and can act on comments.

Documented by publisher. Miro MCP capabilities, team authorization and Enterprise approval

Authentication

OAuth authorisation selects a Miro team.

Documented by publisher. Miro MCP capabilities, team authorization and Enterprise approval

Permission surface

Board permissions apply; Enterprise administrators control MCP availability.

Documented by publisher. Miro MCP capabilities, team authorization and Enterprise approval

Data leaving the environment

Board material can be returned to the connected AI client.

Review inference. Miro MCP capabilities, team authorization and Enterprise approval

Failure modes to consider

A wrong-team connection may look like missing content; editing may exceed a summary request.

Review inference. Miro MCP capabilities, team authorization and Enterprise approval

Unknowns and applicability

The selected team, active board grants and client data handling are unverified.

Not established

Suggested refusal or clarification condition

Clarify the board and team before access; do not convert a summary request into edits or comment resolution.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck when the connection changes team or board permissions change.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the team, board and action boundaries used in an assistant onboarding review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Missing legacy logs can reflect storage policy

Question: Does no Cloudflare AI Gateway log establish that no request occurred?

Cloudflare distinguishes legacy logging eligibility from newer Workers Logs arrangements. Legacy logs persist until deletion; at capacity the gateway can stop saving or delete its oldest logs. The documented historical absence can therefore reflect capacity or deletion rather than no traffic.

Source: Legacy Logs. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does no Cloudflare AI Gateway log establish that no request occurred?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require the account's logging cohort, capacity, deletion mode and relevant time interval; refuse a zero-activity conclusion from missing rows.

Suggested review condition: Require the account's logging cohort, capacity, deletion mode and relevant time interval; refuse a zero-activity conclusion from missing rows.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. Legacy Logs persists; When you reach a storage limit

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the account's logging cohort, capacity, deletion mode and relevant time interval; refuse a zero-activity conclusion from missing rows.
  • An independently complete observation interval can support a narrower count; the existence of capacity limits does not prove a specific gap occurred.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Mistral ZDR: Stateful products and training opt-out are separate

Question: Does enabling Mistral zero data retention cover every model and stateful product?

The reviewed documentation applies ZDR to supported stateless API calls on eligible paid plans, excluding Labs models and stateful products. It explicitly separates ZDR from training opt-out. Approval and the actual endpoint matter; one organisation setting does not establish universal non-retention across all features.

Source: Mistral AI Studio zero data retention. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: ZDR covers every endpoint and also establishes the training preference.

Buyer evidence still required

  • Organisation approval and eligible plan.
  • Exact endpoint/model and stateless or stateful behaviour.
  • Separate training preference and applicable feature terms.

Suggested review condition: Keep unsupported endpoints outside the ZDR claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Organisation approval, plan, endpoint, model and training preference

Optional saved evidence: Preserve the endpoint and model exceptions behind a retention decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Mixpanel MCP: Verified labels and operational tools

Question: Does Mixpanel Verified Mode exclude unverified entities from MCP results?

No. Mixpanel says requested entities remain in results; unverified ones are flagged and verified equivalents are preferred where available. The connector also exposes write tools. Review result labels and operation permissions separately rather than treating Verified Mode as either data exclusion or read-only access.

Source: Mixpanel MCP read/write tools, identity and verified-mode limits. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted analytics server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Mixpanel operates the hosted MCP service.

Documented by publisher. Mixpanel MCP read/write tools, identity and verified-mode limits

Purpose

Query product analytics and manage supported analytics objects.

Documented by publisher. Mixpanel MCP read/write tools, identity and verified-mode limits

Read capability

Reads event, funnel, retention and related analysis results.

Documented by publisher. Mixpanel MCP read/write tools, identity and verified-mode limits

Write capability

Includes dashboard and metadata changes; some features have beta or plan limits.

Documented by publisher. Mixpanel MCP read/write tools, identity and verified-mode limits

Authentication

User OAuth or beta service-account credentials.

Documented by publisher. Mixpanel MCP read/write tools, identity and verified-mode limits

Permission surface

User roles and project access, or service-account project grants, apply.

Documented by publisher. Mixpanel MCP read/write tools, identity and verified-mode limits

Data leaving the environment

Analytics outputs and entity labels are returned to the assistant.

Review inference. Mixpanel MCP read/write tools, identity and verified-mode limits

Failure modes to consider

An unverified entity can be mistaken for excluded data or an approved metric.

Review inference. Mixpanel MCP read/write tools, identity and verified-mode limits

Unknowns and applicability

Buyer grants and availability of individual beta tools are unknown.

Not established

Suggested refusal or clarification condition

Preserve verification labels and clarify the authority for writes.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck Verified Mode behaviour, beta availability and project grants.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save how verified/unverified evidence was interpreted for an analytics review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MODBUS combined register operation order

Question: In MODBUS function 23, is the returned register data captured before the write operation?

MODBUS function 23 decimal, 0x17, combines a write and a read of holding registers, with the write performed before the read. Returned data must be interpreted in that order, especially when the ranges overlap. This ordering does not establish physical actuator completion, safe repetition after a lost response, or a broader database transaction guarantee.

Source: MODBUS Application Protocol V1.1b3. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: In MODBUS function 23, is the returned register data captured before the write operation?

Buyer evidence still required

  • Function code and register ranges
  • Written values and returned data
  • Device semantics and independent physical outcome

Review inference: Interpret combined read/write evidence with the documented write-before-read ordering. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Ordering alone is not an atomicity, concurrency isolation, physical actuator completion, or non-idempotent retry guarantee. It does not close ICE02-F036.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 6.17 in MODBUS Application Protocol V1.1b3 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Ordering alone is not an atomicity, concurrency isolation, physical actuator completion, or non-idempotent retry guarantee. It does not close ICE02-F036.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MODBUS device-identification response continuation

Question: Does one MODBUS Read Device Identification response necessarily contain the complete identity object set?

MODBUS Read Device Identification uses More Follows and Next Object Id to continue stream access across multiple transactions when the response does not fit one message. Access modes 01 through 03 have different scope from individual-object mode 04. One successful response is not automatically a complete identity inventory, nor authenticated proof of a physical device.

Source: MODBUS Application Protocol V1.1b3. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does one MODBUS Read Device Identification response necessarily contain the complete identity object set?

Buyer evidence still required

  • Read Device ID access mode
  • More Follows and Next Object Id
  • Collected object set and independent physical identity

Review inference: Reassemble device-identification continuation responses before asserting completeness. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Scope completeness to the requested access mode and supported conformity level. Codes01-03 stream; code04 returns an individual object and More Follows is00. Do not claim authenticated physical device identity or all optional identity attributes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 6.21 in MODBUS Application Protocol V1.1b3 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Scope completeness to the requested access mode and supported conformity level. Codes01-03 stream; code04 returns an individual object and More Follows is00. Do not claim authenticated physical device identity or all optional identity attributes.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MODBUS illegal data value boundary

Question: Does MODBUS Illegal Data Value establish whether a submitted register value is acceptable to the application?

MODBUS exception 03 reports a value in the query data field that is not allowed, such as an incorrectly structured request. The specification explicitly distinguishes this from an application judging whether a value submitted for storage is meaningful or acceptable. Protocol acceptance is not validation of a process range, calibration or engineering limit.

Source: MODBUS Application Protocol V1.1b3. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does MODBUS Illegal Data Value establish whether a submitted register value is acceptable to the application?

Buyer evidence still required

  • Function and request structure
  • Register/application semantics
  • Independent allowed-range or calibration evidence

Review inference: Separate request-format rejection from the physical meaning of register values. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Reword measured register value to value submitted for storage: that is the exact source contrast. The protocol cannot establish physical thresholds, device safety, measurement validity or a safe corrective action.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 7, exception code 03 in MODBUS Application Protocol V1.1b3 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reword measured register value to value submitted for storage: that is the exact source contrast. The protocol cannot establish physical thresholds, device safety, measurement validity or a safe corrective action.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MODBUS long-running programming response status

Question: Does MODBUS exception 05 ACKNOWLEDGE establish that the requested programming command is complete?

MODBUS Application Protocol 1.1b3 defines exception 05 as acceptance of a specialized long-duration programming request, with a completion poll available. Exception 06 reports that the server is busy processing a long-duration program. Neither response proves completed physical work, and a busy response does not identify the current program or authorize a generic retry.

Source: MODBUS Application Protocol V1.1b3. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does MODBUS exception 05 ACKNOWLEDGE establish that the requested programming command is complete?

Buyer evidence still required

  • Programming function and request identity
  • Exception response
  • Completion poll and independent outcome evidence

Review inference: Separate accepted long-running work from completed equipment programming. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. The source marks both codes as specialized for programming commands. This does not prove physical equipment completion or make arbitrary retries safe; prior timeout/idempotency and broadcast candidate gaps remain open.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 7, exception code 05; Section 7, exception code 06 in MODBUS Application Protocol V1.1b3 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The source marks both codes as specialized for programming commands. This does not prove physical equipment completion or make arbitrary retries safe; prior timeout/idempotency and broadcast candidate gaps remain open.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

monday.com MCP: Board access and GraphQL actions

Question: Can a monday.com agent connection do more than read task boards?

The Platform MCP exposes board operations and broader GraphQL queries and mutations, with calls tied to the authenticated user. Tool availability is therefore wider than task lookup. Confirm token permissions, permitted actions and the target board; distinguish this connection from the separate app-development MCP.

Source: monday Platform MCP identity, authentication and API scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted Platform MCP; Apps MCP excluded

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

monday.com maintains the hosted Platform MCP.

Documented by publisher. monday Platform MCP identity, authentication and API scope; monday Platform MCP data, notification and GraphQL tools

Purpose

Work with platform data through structured tools and GraphQL.

Documented by publisher. monday Platform MCP identity, authentication and API scope; monday Platform MCP data, notification and GraphQL tools

Read capability

Reads boards, items, documents and user context.

Documented by publisher. monday Platform MCP identity, authentication and API scope; monday Platform MCP data, notification and GraphQL tools

Write capability

Can create or update platform data and send notifications; GraphQL mutations are exposed.

Documented by publisher. monday Platform MCP identity, authentication and API scope; monday Platform MCP data, notification and GraphQL tools

Authentication

OAuth or a bearer personal API token is documented.

Documented by publisher. monday Platform MCP identity, authentication and API scope; monday Platform MCP data, notification and GraphQL tools

Permission surface

Calls use the authenticated user context; app scopes and personal-token permissions differ.

Documented by publisher. monday Platform MCP identity, authentication and API scope; monday Platform MCP data, notification and GraphQL tools

Data leaving the environment

Tool results can disclose board data to the assistant; writes can notify other people.

Review inference. monday Platform MCP identity, authentication and API scope; monday Platform MCP data, notification and GraphQL tools

Failure modes to consider

Broad GraphQL access, wrong board selection and API limits can exceed a narrow task.

Review inference. monday Platform MCP identity, authentication and API scope; monday Platform MCP data, notification and GraphQL tools

Unknowns and applicability

The buyer grants, account settings and effective available tools are unverified.

Not established

Suggested refusal or clarification condition

Require approval for mutations and notifications; do not infer read-only access from a board-search use case.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck token type, exposed tools, API version and board permissions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve a decision about permitted board operations and the wider GraphQL surface.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MongoDB Atlas: Cluster termination and protected backup residue

Question: Does terminating an Atlas cluster remove snapshots governed by a Backup Compliance Policy?

Atlas retains existing snapshots after cluster termination according to the backup policy. With Backup Compliance Policy enabled, snapshot deletion and reduced retention are restricted. Extra snapshot retention can extend storage beyond the protected period, when appropriately authorized users can delete snapshots. Cluster removal and backup erasure are therefore separate decisions.

Source: Backup Compliance Policy. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does terminating an Atlas cluster remove snapshots governed by a Backup Compliance Policy?

Buyer evidence still required

  • Terminated cluster and retained snapshot inventory
  • Backup Compliance Policy and protected retention periods
  • Extra retention, copy settings and authorized deletion evidence

Review inference: An exit record should account for retained backups after the primary cluster disappears.

Suggested review condition: Refuse a full-erasure finding while retained snapshots or their retention conditions remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Snapshot contents, retention enforcement and actual deletion are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Make residual backup custody visible in enterprise offboarding decisions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified deletion or compliance certification from a product policy name
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MongoDB change streams: Resume tokens and retained history

Question: Does storing a change-stream resume token guarantee recovery after any outage?

No. MongoDB requires enough oplog history to locate the relevant operation. Invalidation also affects how a stream can restart. A saved token is a position reference, not a guarantee that the required history still exists or every downstream event was processed.

Source: MongoDB change stream resume history requirements. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A resume token guarantees complete replay after an arbitrary interruption.

Buyer evidence still required

  • Retained history covering the saved position
  • Invalidation or topology events relevant to the stream
  • Evidence of downstream processing and reconciliation after reconnect

Suggested review condition: Require retained-history and outcome evidence before a complete-replay claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck retention, stream configuration and recovery procedures.

Optional saved evidence: Preserve the continuity conditions behind an event-feed procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MongoDB MCP: Read-only tools and database authority

Question: Can an agent inspect MongoDB without receiving permission to change data or clusters?

MongoDB documents a read-only MCP mode and recommends a separate read-only database identity. Write operations are otherwise enabled by default. Review both layers and any Atlas tools: selecting a safer tool set does not establish the effective permissions of an existing connection.

Source: MongoDB local MCP security boundaries. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: MongoDB-published local server; not the separately hosted remote service

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

MongoDB publishes the local MCP server; the buyer controls its local configuration.

Documented by publisher. MongoDB local MCP security boundaries; MongoDB MCP tool and telemetry configuration

Purpose

The server exposes database operations and optional Atlas management tools.

Documented by publisher. MongoDB local MCP security boundaries; MongoDB MCP tool and telemetry configuration

Read capability

Read and metadata categories include finding data and inspecting databases or collections.

Documented by publisher. MongoDB local MCP security boundaries; MongoDB MCP tool and telemetry configuration

Write capability

Create, update and delete categories can modify data or Atlas resources unless restricted.

Documented by publisher. MongoDB local MCP security boundaries; MongoDB MCP tool and telemetry configuration

Authentication

Database connection information and Atlas API credentials are separate configuration inputs.

Documented by publisher. MongoDB local MCP security boundaries; MongoDB MCP tool and telemetry configuration

Permission surface

The readOnly setting limits tool operations; disabledTools can restrict individual categories. MongoDB also recommends read-only database credentials.

Documented by publisher. MongoDB local MCP security boundaries; MongoDB MCP tool and telemetry configuration

Data leaving the environment

Query results enter the MCP client. Database hosting, telemetry configuration and model recipients need separate review.

Review inference. MongoDB local MCP security boundaries; MongoDB MCP tool and telemetry configuration

Failure modes to consider

An enabled write category or a broader database identity can defeat the intended analysis-only scope.

Review inference. MongoDB local MCP security boundaries; MongoDB MCP tool and telemetry configuration

Unknowns and applicability

Actual credentials, database grants, Atlas privileges, telemetry settings and installed version have not been inspected.

Not established

Suggested refusal or clarification condition

Resolve the target identity and allowed operations before requesting sensitive data; do not treat tool names as proof of database restrictions.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck the server mode, disabled categories and database or Atlas grants.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the two-layer permission review behind an analysis-only database connection.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MotherDuck local MCP: Read-only queries and host access

Question: Does read-only mode isolate a self-hosted MotherDuck MCP server from its host?

No. The publisher explicitly warns that read-only mode alone still allows filesystem access and DuckDB setting changes. The local server and hosted remote service have different boundaries. A data-write restriction is insufficient evidence of host isolation for third-party access.

Source: MotherDuck local MCP read-only defaults and token requirements. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Publisher local DuckDB/MotherDuck server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

MotherDuck publishes the local server; the buyer operates a self-hosted instance.

Documented by publisher. MotherDuck local MCP read-only defaults and token requirements

Purpose

Query DuckDB or MotherDuck through MCP.

Documented by publisher. MotherDuck local MCP read-only defaults and token requirements

Read capability

Reads selected database data and schema information.

Documented by publisher. MotherDuck local MCP read-only defaults and token requirements

Write capability

Write mode is optional; read-only mode does not itself restrict all host operations.

Documented by publisher. MotherDuck local MCP read-only defaults and token requirements

Authentication

MotherDuck connections use a token; local DuckDB access uses the host environment.

Documented by publisher. MotherDuck local MCP read-only defaults and token requirements

Permission surface

Database mode, database switching and host restrictions are separate settings.

Documented by publisher. MotherDuck local MCP read-only defaults and token requirements

Data leaving the environment

Local data may be returned to the assistant; remote databases add their own connection path.

Review inference. MotherDuck local MCP read-only defaults and token requirements

Failure modes to consider

A read-only label can conceal unresolved filesystem exposure.

Review inference. MotherDuck local MCP read-only defaults and token requirements

Unknowns and applicability

Host isolation, token scope and third-party deployment controls have not been tested.

Not established

Suggested refusal or clarification condition

Require host-access evidence before treating self-hosted read-only access as isolated.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck local server version, exposed transport and host restrictions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the distinction between database write protection and host isolation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Mounted container-file lifetime versus separately managed uploaded skill assets

Question: Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset?

The guide binds mounted skills and container files to the hosted container lifecycle, while separately describing uploaded skill versions and their deletion rules.

Source: OpenAI primary documentation: openai skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset?

Buyer evidence still required

  • container ID/lifecycle
  • uploaded skill/version IDs
  • copied files
  • asset deletion receipts
  • output inventory

Review inference: Does expiry of a hosted OpenAI skill container prove deletion of the separately uploaded skill asset? Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence. Mounted container-file lifetime versus separately managed uploaded skill assets. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Validate data residency and retention requirements

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not extend the container-file statement to uploaded assets, local copies or prior outputs without separate retention evidence.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

MPP challenges and intended payment recipient

Question: Does an HTTP 402 MPP challenge establish that its stated merchant and payment terms are authorised?

MPP clients are instructed to check the requested amount, recipient, currency or asset and validity window before authorising payment. The description is display text and must not be used for payment verification. A 402 challenge supplies payment requirements; its presence does not independently establish that the endpoint or recipient matches the buyer intent.

Source: Protocol overview | MPP. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an HTTP 402 MPP challenge establish that its stated merchant and payment terms are authorised?

Buyer evidence still required

  • Expected endpoint and merchant or recipient identity
  • Decoded challenge amount, currency, recipient and expiry
  • Buyer spending authority and intended resource

Review inference: Bind the requested payment to a previously established service identity and spending decision, using the structured terms rather than the description.

Suggested review condition: Do not authorise a payment when the structured recipient or terms differ from the approved request.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The endpoint owner, merchant relationship and actual buyer authority require independent evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent payment to a substituted recipient or different terms.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • HTTP 402 or human-readable text as merchant verification
  • The endpoint owner, merchant relationship and actual buyer authority require independent evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MPP expiry and payment-proof verification

Question: Can an MPP server accept a caller payment assertion after the challenge expired merely because it was signed earlier?

MPP credential processing checks that the challenge identifier is outstanding, that the challenge has not expired, that the method-specific payment or proof verifies, and that the credential is not replayed. A client-supplied signature or transaction identifier does not replace those checks. For a submitted Tempo transaction hash, the server verifies the confirmed transfer against challenge parameters.

Source: Credentials | MPP. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an MPP server accept a caller payment assertion after the challenge expired merely because it was signed earlier?

Buyer evidence still required

  • Outstanding challenge and verification-time expiry
  • Method-specific verified proof and expected terms
  • Replay state and prior processing result

Review inference: Treat the current challenge validity and verified method outcome as release conditions, independent of the caller assertion.

Suggested review condition: Refuse delivery from an expired challenge or unverified caller assertion; reconcile any actual payment separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether a payment occurred despite rejected access and what recovery applies depend on the payment method and service.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep delivery fail-closed while preserving a path to reconcile uncertain payment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A signature timestamp or caller receipt overriding challenge validity
  • Whether a payment occurred despite rejected access and what recovery applies depend on the payment method and service.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MPP method selection and settlement assumptions

Question: Does switching MPP payment methods preserve the same verification and settlement behavior?

MPP standardises the challenge and credential framework while payment-method specifications define request and proof schemas, verification and settlement procedures. Session methods additionally define how setup, incremental authorisation and accepted usage settle. Sharing the protocol envelope does not make a card payment, transaction proof or metered channel operationally interchangeable.

Source: Protocol overview | MPP. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does switching MPP payment methods preserve the same verification and settlement behavior?

Buyer evidence still required

  • Negotiated payment method, intent and specification version
  • Method-specific verification and settlement evidence
  • Applicable recovery, refund and aggregate budget policy

Review inference: Review the selected method and intent before applying previous settlement, recovery or spending assumptions.

Suggested review condition: Do not carry settlement, refund or global spending-limit assumptions across methods without supporting evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual method implementation and any cross-session budget enforcement are not established by the common envelope.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid unsupported financial assumptions when an agent changes payment rails.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal settlement finality, refund rights or cross-session spending caps
  • The actual method implementation and any cross-session budget enforcement are not established by the common envelope.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MPP payment proof and request-body binding

Question: Does an MPP payment credential automatically authorise a different request body or resource?

MPP supports a digest parameter binding a challenge to the request body. When present, the submitted body must match that digest. The security guidance also requires verification of amount, currency, recipient and route-level context. Challenge integrity therefore needs to be connected to the actual paid request; a receipt or payment proof is not a general-purpose resource authorisation.

Source: Protocol overview | MPP. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an MPP payment credential automatically authorise a different request body or resource?

Buyer evidence still required

  • Original challenge and expected route context
  • Original and submitted request-body digests
  • Verified payment proof and authorised resource scope

Review inference: Check the challenge-to-request binding before reusing payment evidence for an amended API call.

Suggested review condition: Refuse a different body or resource when the required challenge binding cannot be established.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The server may omit body binding or route checks; this review does not test its enforcement.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep delegated spending attached to the exact operation it was intended to fund.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A payment receipt as unrestricted access to other resources
  • The server may omit body binding or route checks; this review does not test its enforcement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MPP payment proof versus private-data authority

Question: Does a valid MPP payment credential by itself authorise access to a customer private resource?

MPP distinguishes payment failure from application authentication and policy denial. It documents a 403 response when payment verifies but policy denies access. When an endpoint also uses application Authorization, it can advertise Payment-Authorization for the payment credential, keeping the two credentials separate. Valid payment is therefore not a substitute for application-level access authority.

Source: Credentials | MPP. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a valid MPP payment credential by itself authorise access to a customer private resource?

Buyer evidence still required

  • Application principal and resource access policy
  • Advertised payment header and verified payment credential
  • Access decision and any denied-payment recovery record

Review inference: Verify the principal and resource permission separately from the proof that money was paid.

Suggested review condition: Do not disclose private data solely because payment verification succeeded.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The merchant access policy and whether credentials are bound to the same authorised buyer require deployment evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep paid retrieval from bypassing existing identity and entitlement boundaries.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Payment purchasing another customer identity or data permissions
  • The merchant access policy and whether credentials are bound to the same authorised buyer require deployment evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MPP receipts and service-delivery evidence

Question: Does an MPP receipt alone prove the intended API result was delivered for the agreed amount and currency?

The common MPP receipt records a payment method, method-specific reference, success status and processing timestamp; methods may add fields. It is a server acknowledgement of payment, not a complete copy of the challenge or the delivered result. Reconciliation must retain the challenge terms and application outcome alongside the payment reference.

Source: Payment Receipts and verification | MPP. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an MPP receipt alone prove the intended API result was delivered for the agreed amount and currency?

Buyer evidence still required

  • Receipt and method-specific provider reference
  • Original challenge amount, currency and resource binding
  • Application result, response completion and delivery record

Review inference: Keep payment verification, requested terms and actual response or delivery evidence as linked but separate observations.

Suggested review condition: Do not infer complete service delivery or all purchase terms from the minimal receipt fields.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual client receipt, response completeness and provider settlement require separate evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Recover paid-but-undelivered API purchases without inventing completion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Receipt success as guaranteed delivery or irreversible settlement
  • Actual client receipt, response completeness and provider settlement require separate evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

MPP replay prevention and operation recovery

Question: Does cryptographically binding an MPP challenge guarantee safe retries across multiple server instances?

MPP distinguishes challenge integrity from replay prevention. Payment methods must enforce single-use proof semantics separately; deployment guidance calls for shared atomic replay state across instances and warns against process-local memory. Non-idempotent operations also need idempotency handling. Preventing proof reuse is therefore not the same as proving an external operation executed exactly once.

Source: Credentials | MPP. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does cryptographically binding an MPP challenge guarantee safe retries across multiple server instances?

Buyer evidence still required

  • Method-specific replay storage and concurrency scope
  • Payment consumption and original operation identity
  • Idempotency key, execution outcome and recovery policy

Review inference: Reconcile payment consumption and operation outcome before retrying an uncertain paid request.

Suggested review condition: Do not claim distributed exactly-once execution from a signed challenge or a single-instance replay cache.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The installed replay store, downstream operation and failure point were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent duplicate charges or actions during distributed recovery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Protocol adoption as proof of exactly-once delivery
  • The installed replay store, downstream operation and failure point were not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Must a repeated A2A cancellation return the same task object to be idempotent

Question: Must a repeated A2A cancellation return the same task object to be idempotent?

The captured specification makes Cancel Task idempotent but permits TaskNotFoundError on a duplicate cancellation after the task was canceled and purged. Cancellation itself can fail for a noncancelable state. Preserve earlier responses and reconcile outcome rather than treating every later not-found as evidence of failed cancellation.

Source: A2A Project primary documentation: a2a spec. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Must a repeated A2A cancellation return the same task object to be idempotent?

Buyer evidence still required

  • cancellation requests
  • earlier responses
  • terminal state
  • purge policy
  • external outcome

Review inference: Must a repeated A2A cancellation return the same task object to be idempotent? Do not infer rollback, original task outcome or a missing first cancellation solely from a later not-found response. A2A's explicit duplicate-cancel purge exception is a distinct reconciliation decision from MCP cooperative cancellation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer rollback, original task outcome or a missing first cancellation solely from a later not-found response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. 3.3.1. Idempotency; 3.1.5. Cancel Task

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer rollback, original task outcome or a missing first cancellation solely from a later not-found response.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Must an MCP scope challenge be a subset of advertised scopes

Question: Must an MCP scope challenge be a subset of advertised scopes?

No. MCP 2026-07-28 prohibits assuming a set relationship between challenged scopes and scopes_supported, and requires treating the challenge as authoritative for the current operation. For initial authorization it recommends using the challenge scope first; otherwise it recommends advertised scopes, omitting scope when scopes_supported is undefined. This does not itself grant consent.

Source: Model Context Protocol primary documentation: mcp authorization. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Must an MCP scope challenge be a subset of advertised scopes?

Buyer evidence still required

  • challenge
  • resource metadata
  • operation
  • current grant

Review inference: Must an MCP scope challenge be a subset of advertised scopes? Use the actual challenge and consent policy, not an assumed discovery-list subset. Scope negotiation differs from tool-list filtering under an existing token. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Use the actual challenge and consent policy, not an assumed discovery-list subset.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Scope Selection Strategy

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Use the actual challenge and consent policy, not an assumed discovery-list subset.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

n8n MCP: Workflow visibility, authoring and execution

Question: Does connecting to n8n MCP only let an agent run a fixed workflow?

The reviewed n8n documentation includes workflow search, execution and authoring. Search previews and full workflow access have different boundaries; OAuth grants and workflow exposure also matter. Check the installed version and execution mode before granting access, because a workflow can call connected services using its configured credentials.

Source: n8n instance MCP authentication and workflow capabilities. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Built-in instance service; version-dependent permissions

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

n8n publishes the instance MCP service for Cloud and self-hosted instances.

Documented by publisher. n8n instance MCP authentication and workflow capabilities

Purpose

Discover, build, edit and execute workflows where permitted.

Documented by publisher. n8n instance MCP authentication and workflow capabilities

Read capability

Workflow previews and exposed workflow data within user access.

Documented by publisher. n8n instance MCP authentication and workflow capabilities

Write capability

Create or edit workflows and data tables, and trigger workflow execution.

Documented by publisher. n8n instance MCP authentication and workflow capabilities

Authentication

OAuth or a personal access token tied to the user.

Documented by publisher. n8n instance MCP authentication and workflow capabilities

Permission surface

User access, client grants and workflow exposure apply; discovery previews have a broader scope.

Documented by publisher. n8n instance MCP authentication and workflow capabilities

Data leaving the environment

Workflow inputs and outputs may reach connected services and the MCP client.

Review inference. n8n instance MCP authentication and workflow capabilities

Failure modes to consider

Choosing the wrong execution mode or workflow can trigger unintended downstream actions.

Review inference. n8n instance MCP authentication and workflow capabilities

Unknowns and applicability

Installed features, effective grants and downstream credential scope are unverified.

Not established

Suggested refusal or clarification condition

Confirm workflow, execution mode and downstream action authorization before running it.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck instance version, OAuth grants, exposure settings and published workflow revisions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the version, exposure and downstream-action assumptions behind workflow access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Namespace/profile/session tuple versus authenticated tenant boundary

Question: Can a Cloudflare Agent Memory session identifier alone define a tenant boundary?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented hierarchy separates namespaces and profiles, with sessions scoped to a profile and the same session ID permitted in different profiles. Recall is described as confined to the selected profile.

Source: Cloudflare primary documentation: cloudflare memory profiles. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Cloudflare Agent Memory session identifier alone define a tenant boundary?

Buyer evidence still required

  • account/namespace/profile tuple
  • session ID
  • identity mapping
  • API token permissions
  • isolation tests

Review inference: Can a Cloudflare Agent Memory session identifier alone define a tenant boundary? Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation. Namespace/profile/session tuple versus authenticated tenant boundary. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Sessions are scoped to a profile

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the application's authenticated-identity-to-profile mapping; a session string alone does not establish tenant authorisation. Private beta access and current feature applicability require separate confirmation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

namespaceKeys update replaces full set and preserves dependent keys

Question: Does UpdateMemory append namespace keys while retaining the previous set?

The documented namespaceKeys update replaces the entire set. The guide requires preserving existing keys and rejects removing a key still used by a strategy template.

Source: Amazon Web Services primary documentation: aws memory namespaces. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does UpdateMemory append namespace keys while retaining the previous set?

Buyer evidence still required

  • before/after key sets
  • dependent namespace templates
  • update request/response
  • approval

Review inference: Does UpdateMemory append namespace keys while retaining the previous set? Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving. namespaceKeys update replaces full set and preserves dependent keys. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Update namespace keys

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Treat a namespace change as full-configuration replacement; compare old/new keys and all dependent strategies before approving.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Derived claim boundary

NASA IMS E4.1: Performance boundary

Question: Does the safe NASA IMS E4.1 result establish performance qualification?

The public NASA IMS E4.1 source records a safe but not performance-qualified result. The safe status does not support a performance qualification claim.

Derived from BDAS NASA IMS E4.1 — Safe But Not Performance Qualified. No new experiment or validation is claimed.

Claim boundaries
  • performance qualification
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Neon MCP: Project grants, SQL roles and write access

Question: Does selecting a Neon tool category make a database agent read-only?

No. The README distinguishes category selection from read-only enforcement and a pinned SQL role. It documents OAuth grants and API-key requests differently, and warns against production use. Review the project, role and write setting together before approving database access.

Source: Neon MCP project scoping, read-only controls and tool categories. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted management server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Neon publishes and hosts the management server.

Documented by publisher. Neon MCP project scoping, read-only controls and tool categories

Purpose

Inspect and manage database projects and related resources.

Documented by publisher. Neon MCP project scoping, read-only controls and tool categories

Read capability

Reads schemas, query results and diagnostics.

Documented by publisher. Neon MCP project scoping, read-only controls and tool categories

Write capability

Can change databases and platform resources when writes are allowed.

Documented by publisher. Neon MCP project scoping, read-only controls and tool categories

Authentication

OAuth or a Neon API key.

Documented by publisher. Neon MCP project scoping, read-only controls and tool categories

Permission surface

Categories select tool families; read-only mode and project/role grants apply separately.

Documented by publisher. Neon MCP project scoping, read-only controls and tool categories

Data leaving the environment

Database results enter the assistant; account analytics are separately described by the publisher.

Review inference. Neon MCP project scoping, read-only controls and tool categories

Failure modes to consider

A category name can be mistaken for a read-only control.

Review inference. Neon MCP project scoping, read-only controls and tool categories

Unknowns and applicability

The buyer grant, role privileges and runtime have not been checked.

Not established

Suggested refusal or clarification condition

Clarify production use and effective grants; do not infer read-only access from category selection.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck category contents, OAuth grants and SQL-role privileges.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the documented grant distinctions behind a database-agent onboarding decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Neon restore: History windows and eligible branches

Question: Does Neon instant restore apply to every branch and any past time?

No. Current documentation limits instant point-in-time restore to eligible root branches within retained history and excludes branches created by snapshot restore. It restores all databases on the chosen branch. Review eligibility, history and blast radius before accepting a universal recovery claim.

Source: Neon branch restore history and recovery limits. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Any Neon branch can be restored to any prior point without affecting other databases.

Buyer evidence still required

  • Branch type and snapshot-restore origin
  • Available history covering the required time
  • All databases affected and evidence of the intended recovery outcome

Suggested review condition: Require branch eligibility and recovery scope before promising a restore.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck restore support, history settings and branch lineage.

Optional saved evidence: Save the branch/history conditions behind a database recovery review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Nested workflows: Secret forwarding boundaries

Question: Does passing secrets to one reusable GitHub workflow automatically pass them to every nested workflow?

Secrets are passed only to the directly called workflow. In a caller-to-intermediate-to-nested chain, the intermediate workflow must also forward the relevant secrets. Explicit mappings and secrets: inherit have different breadth. Review each call boundary without exposing the values when assessing credential disclosure.

Source: GitHub: Reuse workflows. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Secrets automatically propagate through the entire workflow chain.

Buyer evidence still required

  • Caller/callee chain and exact workflow revisions.
  • Named secret mappings or inherit settings per hop.
  • Authorized recipients and required credential purpose.

Suggested review condition: Require a per-hop disclosure map before approving secret inheritance across workflow owners.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workflow ownership, references, secret names and per-hop forwarding; never include values.

Optional saved evidence: Preserve credential-routing evidence without retaining sensitive credentials.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Netlify MCP: Deployment and resource authority

Question: Does adding Netlify MCP only give my agent deployment guidance?

Netlify describes MCP capabilities for creating and deploying projects, managing resources and changing configuration. The local package can use the API and CLI; current docs also distinguish a remote server. Review the chosen variant, credentials and permitted resources before treating the connection as guidance-only.

Source: Netlify local MCP API, CLI and resource management. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Local Netlify MCP package; remote connector distinguished

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Netlify publishes the local MCP package; the buyer runs this variant.

Documented by publisher. Netlify local MCP API, CLI and resource management; Netlify remote and local MCP deployment distinction

Purpose

Connect code agents to Netlify API and CLI capabilities.

Documented by publisher. Netlify local MCP API, CLI and resource management; Netlify remote and local MCP deployment distinction

Read capability

Retrieves user, team and resource information.

Documented by publisher. Netlify local MCP API, CLI and resource management; Netlify remote and local MCP deployment distinction

Write capability

Can deploy projects and manage access controls, extensions, forms and environment configuration.

Documented by publisher. Netlify local MCP API, CLI and resource management; Netlify remote and local MCP deployment distinction

Authentication

The local setup documents a personal-access-token authentication option.

Documented by publisher. Netlify local MCP API, CLI and resource management; Netlify remote and local MCP deployment distinction

Permission surface

The effective credential grants and per-operation restrictions require buyer verification.

Not established. Netlify local MCP API, CLI and resource management; Netlify remote and local MCP deployment distinction

Data leaving the environment

Local hosting still calls Netlify services; results and configuration can enter the assistant context.

Review inference. Netlify local MCP API, CLI and resource management; Netlify remote and local MCP deployment distinction

Failure modes to consider

Wrong project selection or broad deployment authority can change live resources.

Review inference. Netlify local MCP API, CLI and resource management; Netlify remote and local MCP deployment distinction

Unknowns and applicability

The buyer token, local execution permissions and target deployment state are unknown.

Not established

Suggested refusal or clarification condition

Require explicit deployment and configuration authority; do not infer it from a request for hosting advice.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck when switching server variant, identity or target team/project.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the deployment, credential and configuration questions used before enabling hosting actions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

NetworkPolicy: Declared rules and effective enforcement

Question: Does a Kubernetes NetworkPolicy object prove an agent pod cannot reach the internet?

NetworkPolicy needs a supporting network implementation. Pods are not isolated for egress by default, and applicable policy allowances combine rather than overriding each other by order. A saved policy object is therefore insufficient: selection, direction, implementation support and the combined allowed traffic must be checked.

Source: Kubernetes NetworkPolicy enforcement. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A NetworkPolicy object alone establishes enforced outbound isolation.

Buyer evidence still required

  • Network implementation and supported policy features.
  • Pod labels, namespace and all applicable egress policies.
  • Observed permitted and denied paths in the intended environment.

Suggested review condition: Require effective enforcement evidence before claiming the agent is network-isolated.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Cluster network implementation, pod selection, direction, policies and tested traffic paths.

Optional saved evidence: Save the source-backed evidence requirements for an agent isolation procurement check.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

New Relic MCP: Identity, feature switches and tool availability

Question: Does a working New Relic API key provide all MCP analysis tools?

No. The overview distinguishes OAuth-only tools from API-key access and requires organisation-level permission plus relevant feature switches. Preview and API-key access have separate controls. A successful connection therefore does not establish access to every analysis capability or every account dataset.

Source: New Relic MCP capabilities and access. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted Ground Truth MCP access

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

New Relic operates the MCP service.

Documented by publisher. New Relic MCP capabilities and access

Purpose

Query and investigate observability information.

Documented by publisher. New Relic MCP capabilities and access

Read capability

Permitted operational data and analysis results.

Documented by publisher. New Relic MCP capabilities and access

Write capability

The overview does not establish an exhaustive mutation boundary.

Not established. New Relic MCP capabilities and access

Authentication

OAuth or user API key, with different tool availability.

Documented by publisher. New Relic MCP capabilities and access

Permission surface

Organisation permission, feature controls and tool/usage entitlement.

Documented by publisher. New Relic MCP capabilities and access

Data leaving the environment

Telemetry results can enter the chosen AI client.

Review inference. New Relic MCP capabilities and access

Failure modes to consider

A missing tool can reflect authentication or feature eligibility.

Review inference. New Relic MCP capabilities and access

Unknowns and applicability

Actual data access and the complete deployed tool set are unverified.

Not established

Suggested refusal or clarification condition

Request tool and account evidence before claiming complete analysis access.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. OAuth-only tools, feature defaults and usage entitlement.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save why a successful login did not establish the required analysis or data entitlement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

Next.js: Locate authorization checks and hosting protection

Question: Can an agent assess middleware authorization bypass from a Next.js version alone?

For CVE-2025-29927, the Next.js maintainer identifies authorization checks performed in middleware as the relevant condition and states that Vercel-hosted deployments are protected against this issue. The frozen records retain branch-specific fixes: 12.3.5, 13.5.9, 14.2.25 and 15.2.3. The maintainer also discusses 11.x, which the frozen 12.x range does not cover. Check where authorization is enforced and how requests reach the deployment. Neither a package match nor this hosting statement establishes overall application security; these are historical issue-specific fixes.

Source: Next.js maintainer advisory: CVE-2025-29927. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (4)
  • npm / next — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-f82v-jwr5-mffw, captured 2026-10-08
  • npm / next — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-f82v-jwr5-mffw, captured 2026-10-08
  • npm / next — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-f82v-jwr5-mffw, captured 2026-10-08
  • npm / next — Historical source binding; projection withheld from current lookup after whole-group ambiguity review — GHSA-f82v-jwr5-mffw, captured 2026-10-08

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • overall application security inferred from hosting protection
  • frozen branch coverage assumed complete for 11.x
  • a buyer's authorization checks or deployment verified

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

NIST AI 600-1: Generative AI profile scope

Question: What does NIST AI 600-1 add to AI risk management?

NIST AI 600-1 is a cross-sector generative AI profile accompanying AI RMF 1.0. It frames risks and suggested management actions for generative AI; citing the profile is not evidence that an organisation has implemented or tested those actions.

Source: NIST AI 600-1 publication. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • implemented organisational controls
  • validated model behaviour
  • certification from a citation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

NIST AI 600-1: Suggested actions and evidence

Question: Do NIST's suggested generative AI risk actions demonstrate that controls were completed?

NIST AI 600-1 suggests actions across the Govern, Map, Measure and Manage functions. A suggested action is guidance, not a completed check: an implementation claim needs an accountable owner, defined scope and supporting evidence for the action actually taken.

Source: NIST AI 600-1: Generative Artificial Intelligence Profile. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • completed risk assessment
  • effective deployed mitigation
  • evidence that every suggested action applies

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

NIST AI RMF adjudicated feedback

Question: Does collecting AI user feedback establish that it influences the system?

AI RMF 1.0 GOVERN 5.2 describes mechanisms for regularly incorporating adjudicated feedback into design and implementation. A feedback inbox or survey count does not establish review, disposition or incorporation. Trace relevant feedback to a reasoned decision and the resulting change or documented decision not to change.

Source: NIST: AI RMF 1.0 Core. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does collecting AI user feedback establish that it influences the system?

Buyer evidence still required

  • feedback mechanism
  • review and adjudication records
  • resulting design decisions
  • implementation evidence
  • review cadence

Review inference: A supplier counts submitted feedback as evidence of responsive oversight. Consequential concerns may remain unreviewed despite a high response count. Adds the feedback-to-decision chain rather than general completion of governance actions. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: The framework does not require every suggestion to be accepted or prove that feedback represents all affected users.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Govern 5.2

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The framework does not require every suggestion to be accepted or prove that feedback represents all affected users.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

NIST AI RMF assessor independence

Question: Does a developer-only assessment establish the AI RMF independent-assessment outcome?

AI RMF 1.0 MEASURE 1.3 includes regular assessment involving internal experts who were not front-line developers and/or independent assessors, with relevant consultation as needed. It does not require every review to be external. Retain assessor roles, involvement in development, review scope and findings before making an independence claim.

Source: NIST: AI RMF 1.0 Core. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a developer-only assessment establish the AI RMF independent-assessment outcome?

Buyer evidence still required

  • assessor identities by role
  • development involvement
  • review scope and date
  • consultation rationale
  • findings

Review inference: A team labels its own implementation check an independent assurance review. The stated assurance level can exceed the review actually performed. Adds the assessor separation criterion and internal-versus-external distinction. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: An independent review is not certification, complete objectivity or proof that all risks were detected.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Measure 1.3

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • An independent review is not certification, complete objectivity or proof that all risks were detected.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

NIST AI RMF intervention responsibility

Question: Does an emergency stop button establish the AI RMF intervention outcome?

AI RMF 1.0 MANAGE 2.4 pairs mechanisms for superseding, disengaging or deactivating unsuitable systems with assigned and understood responsibilities. A control shown in a user interface is not evidence that an authorized operator can apply it in the relevant scenario. Review mechanism scope, responsible roles and evidence of its application separately.

Source: NIST: AI RMF 1.0 Core. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an emergency stop button establish the AI RMF intervention outcome?

Buyer evidence still required

  • intended-use limits
  • intervention mechanism
  • assigned responsible roles
  • escalation conditions
  • observed exercise evidence

Review inference: A procurement review accepts a stop control without checking who can use it. The needed intervention may be unavailable or unowned during an incident. Adds responsibility and applied intervention mechanisms rather than a general human-oversight statement. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: The source does not establish runtime enforcement, automatic shutdown or effectiveness in a specific deployment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Manage 2.4

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The source does not establish runtime enforcement, automatic shutdown or effectiveness in a specific deployment.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

NIST AI RMF residual risk downstream

Question: Can a risk review close without recording remaining risks to downstream users?

AI RMF 1.0 MANAGE 1.4 describes documenting negative residual risks for downstream acquirers and end users. A list of mitigations does not by itself record what remains unmitigated or who may be affected. Review the residual-risk statement, affected uses and decision owner without treating risk documentation as acceptance by every downstream party.

Source: NIST: AI RMF 1.0 Core. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a risk review close without recording remaining risks to downstream users?

Buyer evidence still required

  • mitigations
  • unresolved risk statements
  • downstream use and users
  • accountable review decision

Review inference: A supplier provides only a list of controls to justify release. Buyers can miss material limitations remaining after mitigation. Adds downstream residual-risk disclosure content, distinct from framework adoption or completed controls. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Documented residual risk is not proof of safety, informed consent, legal compliance or transfer of responsibility.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Manage 1.4

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Documented residual risk is not proof of safety, informed consent, legal compliance or transfer of responsibility.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

NIST AI RMF safe decommissioning

Question: Does removing an AI service from inventory establish a safely managed retirement?

AI RMF 1.0 GOVERN 1.7 describes processes for safely phasing out AI systems without increasing risk or reducing organizational trustworthiness. Inventory removal alone does not establish that transition. Identify dependencies, outstanding work, retained evidence and accountable transition decisions as buyer-specific review inputs; the source does not prescribe a universal deletion checklist.

Source: NIST: AI RMF 1.0 Core. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does removing an AI service from inventory establish a safely managed retirement?

Buyer evidence still required

  • retirement scope
  • dependencies
  • outstanding actions
  • retention obligations
  • transition owner and evidence

Review inference: An organization disables an agent while dependent workflows still rely on its outputs. Retirement can leave unfinished work or unavailable evidence. Adds retirement and downstream dependency risk rather than general evidence that suggested actions occurred. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: The framework does not prove deletion, prescribe every retirement step or certify a completed exit.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Govern 1.7

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The framework does not prove deletion, prescribe every retirement step or certify a completed exit.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

NIST AI RMF third party contingency

Question: Does recording a third-party AI dependency satisfy the AI RMF contingency outcome?

AI RMF 1.0 GOVERN 6.2 describes contingency processes for failures or incidents involving high-risk third-party AI systems or data. A dependency inventory alone does not show such a process exists. For a buyer review, identify the affected dependency, failure conditions, responsible operator and documented fallback or escalation evidence.

Source: NIST: AI RMF 1.0 Core. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does recording a third-party AI dependency satisfy the AI RMF contingency outcome?

Buyer evidence still required

  • dependency inventory
  • risk classification
  • contingency process
  • responsible owner
  • exercise or incident evidence

Review inference: A buyer accepts a supplier list as the complete AI outage plan. No usable fallback may exist when the dependency fails. Adds the distinct operational decision about third-party failure contingency rather than merely naming the framework. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: The framework is voluntary guidance, not certification or proof that a supplier will recover successfully.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Govern 6.2

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The framework is voluntary guidance, not certification or proof that a supplier will recover successfully.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

NIST AI RMF: Voluntary framework boundary

Question: Does using NIST AI RMF amount to a certified safety result?

NIST describes AI RMF as a voluntary framework for managing AI risks. Its use can structure an assessment, but naming the framework does not establish certification, completion of controls or a safe outcome for a specific system.

Source: NIST AI Risk Management Framework. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • NIST certification
  • complete control implementation
  • guaranteed safe outcome

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

NIST critical-infrastructure AI profile: Concept-stage evidence

Question: Does citing the NIST critical-infrastructure AI profile establish that a supplier completed a readiness assessment?

The reviewed NIST project page describes an ongoing effort to develop a critical-infrastructure AI RMF profile and links a concept note. It describes intended guidance, not a completed supplier assessment. Preserve the document stage and date alongside evidence of the controls actually implemented. A reference to this project does not establish certification, a finished checklist or deployment approval.

Source: NIST: Concept Note, AI RMF Profile on Trustworthy AI in Critical Infrastructure. Documentation checked 2026-10-12; no deployment validation is claimed.

Claim boundaries
  • project participation proving supplier readiness
  • a concept note establishing a finished checklist
  • certification or deployment approval

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Normalised namespace string controls whether IAM conditions match

Question: Can an AgentCore namespace IAM condition omit its leading or trailing slash?

AgentCore normalises namespaces with leading and trailing slashes. The guide says an IAM condition lacking these does not match the namespace on which the service acts.

Source: Amazon Web Services primary documentation: aws memory namespaces. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can an AgentCore namespace IAM condition omit its leading or trailing slash?

Buyer evidence still required

  • normalised namespace
  • request value
  • IAM condition
  • strategy template
  • denied/allowed test evidence

Review inference: Can an AgentCore namespace IAM condition omit its leading or trailing slash? Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string. Normalised namespace string controls whether IAM conditions match. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Namespace format

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Compare the normalised runtime value with the actual IAM condition; do not diagnose effective access from a visually similar string.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Notion AI evidence: No-training claims and retention scope

Question: Does Notion AI not training on customer data mean no provider retains any of it?

Notion states that customer data is not used for model training by default. Retention is a separate, plan- and feature-dependent claim, with explicit exceptions for some AI features and External Agents. Treat training, provider retention and deletion of other stored representations as distinct questions; the reviewed documentation does not verify a particular workspace.

Source: Notion AI training and retention scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: No training means no retention anywhere in our Notion AI workflow.

Buyer evidence still required

  • The current workspace plan and feature inventory
  • Administrative settings for data-retaining models
  • A provider- and data-layer-specific retention explanation for the intended workflow

Suggested review condition: Do not infer universal zero retention from the no-training statement; obtain clarification for feature exceptions or ambiguous deletion timelines.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck feature exceptions, subprocessors, workspace settings and plan.

Optional saved evidence: Retain the distinction between training policy and retention for a specific procurement question.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion audit: Agent configuration events are not a run trace

Question: Does the Notion audit log show everything a Custom Agent did during a run?

The audit documentation lists Custom Agent configuration and access events but explicitly excludes recording what an agent did during a specific run. Exports also follow active filters and a bounded historical window with a recent-data gap. Audit availability is not proof of a complete agent execution trace.

Source: Notion audit log scope and exports. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Notion audit export supplies complete per-run agent evidence.

Buyer evidence still required

  • Workspace plan and applicable event catalogue.
  • Export filters, time window and recent-data gap.
  • Separate run-level evidence for the specific agent action.

Suggested review condition: Do not claim full agent traceability from configuration events alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Plan, event catalogue, export filters and separate run evidence

Optional saved evidence: Retain the distinction between agent configuration history and evidence of a particular run.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion blocks: First-level children are not the full page tree

Question: Does one Notion block-children response capture all nested page content?

Notion returns only the first level of children for the requested block, and the list itself is paginated. Nested content needs separate child retrieval. A short response is not sufficient evidence that the full page tree has been collected.

Source: Notion: Retrieve block children. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does one Notion block-children response capture all nested page content?

Buyer evidence still required

  • Root identity and child relationships.
  • Completed cursors for each traversed block.
  • Missing or inaccessible child references.

Suggested review condition: Record both traversal depth and pagination coverage before claiming a complete page capture.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Root block, nested-child traversal, cursor completion and access failures.

Optional saved evidence: Does one Notion block-children response capture all nested page content?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion export: Accessible content is not an instant restore

Question: Does a Notion workspace export prove that the whole workspace can be restored?

Exports omit pages the exporter cannot access and can be limited by teamspace settings. The guide also states that uploading exported content does not instantly recreate the workspace. Export coverage and a demonstrated restoration workflow are separate evidence requirements.

Source: Notion workspace settings and export. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A workspace export is a complete restorable backup.

Buyer evidence still required

  • Exporter access and teamspace restrictions.
  • Export contents and excluded pages.
  • Documented restoration procedure and trial evidence.

Suggested review condition: Do not claim complete recovery from an export file alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Exporter permissions, teamspace settings, formats and recovery procedure

Optional saved evidence: Keep export coverage and outstanding recovery evidence attached to an exit or continuity decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion MCP: Content access and external sharing

Question: Can an agent assume Notion content stays inside Notion when using its MCP connector?

Notion documents a hosted OAuth connector that can read and update accessible content. Its security guidance explicitly warns that connected clients may send returned content outside Notion. Check the client and model data policy as well as workspace access. The connector's publisher and valid login do not establish a no-egress or no-training guarantee.

Source: Notion MCP overview. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Notion-hosted remote MCP; excludes locally hosted alternatives. Workspace, client and account entitlements must be checked separately.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Notion hosts the remote MCP service.

Documented by publisher. Notion MCP overview; Notion MCP security guidance

Purpose

Search, read and update workspace content.

Documented by publisher. Notion MCP overview; Notion MCP security guidance

Read capability

Content accessible to the authorizing user, including supported search across connected sources.

Documented by publisher. Notion MCP overview; Notion MCP security guidance

Write capability

Documented operations include creating pages or databases and updating content.

Documented by publisher. Notion MCP overview; Notion MCP security guidance

Authentication

User authorization through OAuth; workspace and organization owners have documented connection management controls.

Documented by publisher. Notion MCP overview; Notion MCP security guidance

Permission surface

The user's content access and workspace connection controls define relevant boundaries; buyer settings were not inspected.

Documented by publisher. Notion MCP overview; Notion MCP security guidance

Data leaving the environment

Notion explicitly states that an MCP client may send returned content to systems outside Notion.

Review inference. Notion MCP overview; Notion MCP security guidance

Failure modes to consider

Treating workspace authorization as a data-residency promise; following instructions embedded in a page; unintended content changes.

Review inference. Notion MCP overview; Notion MCP security guidance

Unknowns and applicability

Client/model training and retention policy, effective connected-source access and the buyer's workspace restrictions.

Not established

Suggested refusal or clarification condition

When a task requires no external disclosure, resolve the client's data flow before reading private pages; do not apply page instructions as user authority.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the documented content-sharing limitation with a dated connector approval discussion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion page lock and API updates

Question: Does locking a Notion page prevent edits through its API by an otherwise authorized connection?

Notion’s update-page reference states that is_locked controls editing in the Notion interface and does not affect API updates. API capability and page-access requirements remain separate. A visible page lock therefore is not evidence that a connected integration has lost update authority.

Source: Update page - Notion Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does locking a Notion page prevent edits through its API by an otherwise authorized connection?

Buyer evidence still required

  • Page ID and is_locked state
  • Connection access and update-content capability
  • Approved API action and observed permission result

Review inference: Use connection access and update capability as the API boundary, and treat the lock as an interface control.

Suggested review condition: Reject an API-write prohibition based only on the page’s visible lock state.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual connection permissions and update result are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid relying on an interface lock to prevent automated edits.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • API authorization revocation from a Notion page lock
  • The actual connection permissions and update result are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion properties: Finish pagination before relying on a rollup

Question: Can an agent rely on the first Notion property response as the complete relation or rollup result?

Notion returns some property types as paginated lists and directs callers to continue until has_more is false. Rollups include calculation metadata, and every page must be read before using a calculated result. A first response can therefore be incomplete evidence.

Source: Notion: Retrieve a page property item. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an agent rely on the first Notion property response as the complete relation or rollup result?

Buyer evidence still required

  • Property type and exact identifiers.
  • All continuation responses and final has_more state.
  • Final rollup calculation metadata.

Suggested review condition: Separate interim property pages from the completed value used in a decision.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. API version, page/property identity, property type and continuation status.

Optional saved evidence: Can an agent rely on the first Notion property response as the complete relation or rollup result?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion sharing: Broad grants and child-page permissions

Question: Does moving a Notion parent page to Private revoke every child-page grant?

Notion says that moving a shared page to Private removes others from that parent, while subpage grants remain. It also applies the broadest access granted to a user. Review parent, child and workspace grants separately before reporting a complete access revocation.

Source: Notion inherited sharing and public access. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Making a parent private removes every route to its child content.

Buyer evidence still required

  • Current parent and subpage sharing settings
  • Workspace or other broader grants for affected users
  • Outcome checks for the intended audience after the change

Suggested review condition: Do not claim complete revocation from the parent setting alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck page moves, subpage grants and workspace access.

Optional saved evidence: Save the sharing-scope evidence needed for a document handover or offboarding review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion webhooks: Event metadata and retrieved content

Question: Does a Notion webhook contain the full page content as it existed when the event occurred?

The documented flow sends event metadata and then retrieves updated content through the Notion API. That retrieval is a separate operation, not proof of an event-time content snapshot. Signature checking authenticates the received bytes; it does not establish the completeness or historical identity of subsequently fetched page content.

Source: Notion webhook events and current-state retrieval. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A verified webhook is a complete immutable page-content snapshot.

Buyer evidence still required

  • Subscribed event and exact received payload.
  • Signature verification over original bytes.
  • API retrieval time, permissions and saved content version.

Suggested review condition: Date and identify the retrieved content separately from the notification event.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Connection, subscription, event payload, signature verification and follow-up content retrieval.

Optional saved evidence: Preserve the boundary between authenticated notification and a separately captured document version.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion: Reading, inserting and updating are separate

Question: Does permission to insert Notion content imply permission to read full objects or update existing pages?

Notion separates read, insert and update content capabilities. Insert capability permits creating content without granting full-object reading or existing-page updates. Comment and user-information capabilities are separate choices, so a generic write label obscures the actual declared operations.

Source: Notion: Connection capabilities. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does permission to insert Notion content imply permission to read full objects or update existing pages?

Buyer evidence still required

  • Granted content, comment and user capabilities.
  • Requested endpoint and operation.
  • Pages shared with the connection.

Suggested review condition: Match each proposed operation to its capability instead of inferring a broad read/write grant.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Connection capabilities, endpoint and shared content scope.

Optional saved evidence: Does permission to insert Notion content imply permission to read full objects or update existing pages?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Notion: Search is not a complete workspace inventory

Question: Can a Notion search export establish every document an integration can access?

Notion says search is not guaranteed to enumerate everything a connection can access, and indexing is not immediate. Directly shared pages or databases have a documented return guarantee, but general search results are not a complete inventory. A missing match is not proof of deletion or lack of access.

Source: Notion: Search optimizations and limitations. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a Notion search export establish every document an integration can access?

Buyer evidence still required

  • Connection identity and directly shared objects.
  • Search timing, filters and pagination evidence.
  • Independent inventory or specific object checks for the claimed scope.

Suggested review condition: Require additional enumeration evidence before claiming complete coverage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Connection, shared objects, query timing and inventory claim.

Optional saved evidence: Save the limits behind a Notion discovery or export assessment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Npm calling workflow identity check

Question: Which workflow identity must match npm trusted publishing when one workflow calls another?

For the workflow invocation paths described in the captured guide, validation checks the calling workflow name rather than the workflow containing npm publish. The guide also requires id-token: write on parent and child workflows. Match the documented identity to the actual call chain instead of configuring only the reusable publish file.

Source: npm: Trusted publishing with OIDC. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Which workflow identity must match npm trusted publishing when one workflow calls another?

Buyer evidence still required

  • caller and called workflow names
  • invocation path
  • OIDC permissions on both
  • trusted publisher configuration

Review inference: A team moves publishing into a reusable workflow and updates the wrong identity setting. Publication fails or the authorization review binds the wrong workflow. Adds npm's caller-versus-publisher workflow identity distinction. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: This authentication mapping does not verify every action or dependency inside either workflow.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. validation checks the calling workflow

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • This authentication mapping does not verify every action or dependency inside either workflow.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

npm ignore-scripts: Explicit commands still execute

Question: Does ignore-scripts make every npm operation safe from project script execution?

In npm CLI v11, ignore-scripts suppresses package.json scripts during operations such as installation. Commands explicitly intended to run a script, including npm test and npm run, still run the requested script while omitting pre- and post-scripts. This setting is not an execution sandbox for later agent commands.

Source: npm install ignore-scripts. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Once ignore-scripts is set, no npm command can run project code.

Buyer evidence still required

  • npm version and effective configuration.
  • Exact proposed command and requested script.
  • Project trust and execution environment.

Suggested review condition: Require separate execution authority for explicit scripts even when installation scripts are disabled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. npm CLI version, effective setting, exact command and project script authority.

Optional saved evidence: Preserve the execution boundary used when approving a coding-agent workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

npm locked dependency installation

Question: Does a compatible dependency range alone guarantee that npm installs the previously reviewed dependency tree?

npm’s package lock records a resolved dependency tree. npm ci requires a lockfile and fails when its dependencies disagree with package.json instead of updating the lock. Its installation does not rewrite the lock, and tree-shaping flags must match those used to create it. A version range alone is not this frozen-install evidence.

Source: npm-ci | npm Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a compatible dependency range alone guarantee that npm installs the previously reviewed dependency tree?

Buyer evidence still required

  • Reviewed lockfile hash and package manifest
  • npm version and tree-shaping configuration
  • Installation result and resolved dependency inventory

Review inference: Bind the reviewed lockfile, installer version and relevant flags to the installed tree.

Suggested review condition: Refuse reproducibility claims based only on compatible version ranges.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Runtime loading, platform differences and package safety remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Reduce accidental dependency drift in a reviewed agent integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A guarantee that locked dependencies are harmless or identical on every platform
  • Runtime loading, platform differences and package safety remain unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Npm OIDC provenance generation conditions

Question: Does every npm OIDC publication automatically include provenance?

The captured guide limits automatic provenance to supported GitHub Actions or GitLab CI/CD publication from a public repository to a public package. CircleCI provenance is not supported in that capture, and generation can be explicitly disabled. Verify the actual attestation and configuration rather than infer provenance from OIDC authentication alone.

Source: npm: Trusted publishing with OIDC. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does every npm OIDC publication automatically include provenance?

Buyer evidence still required

  • CI provider
  • repository and package visibility
  • provenance setting
  • delivered attestation
  • verification result

Review inference: A consumer assumes an authenticated CircleCI publication has an attestation. The required provenance evidence may be absent. Adds conditions for provenance existence, distinct from the meaning of a present attestation. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Provenance presence still does not certify absence of malicious code or verify buyer deployment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Automatic provenance generation

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Provenance presence still does not certify absence of malicious code or verify buyer deployment.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

npm provenance: Source linkage is not a malware clearance

Question: Does npm provenance guarantee that a package contains no malicious code?

The npm guide explicitly says provenance does not guarantee absence of malicious code. It provides a verifiable link to source and build instructions, with supported publishing environments and separate verification steps. Package identity and provenance verification support a review; they do not replace content evaluation.

Source: npm provenance boundaries. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A provenance badge proves the package is benign.

Buyer evidence still required

  • Exact package version and downloaded artifact identity.
  • Attestation verification with the relevant tooling.
  • Source/build review and the consumer acceptance criteria.

Suggested review condition: Do not infer benign content solely from provenance availability.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Package identity, attestation format, verifier and acceptance policy

Optional saved evidence: Retain the source linkage and unresolved content questions behind package acceptance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Npm trusted publisher action scope

Question: Does npm trusted publishing grant direct publication and dist-tag management together?

The captured guide distinguishes staged publishing, direct npm publish and dist-tag management. Direct publishing and dist-tag permissions are independent choices, and historical configurations have date-dependent defaults. Review the actual connection's allowed actions. Other stage actions, including approval, require interactive authentication and cannot use OIDC tokens.

Source: npm: Trusted publishing with OIDC. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does npm trusted publishing grant direct publication and dist-tag management together?

Buyer evidence still required

  • connection creation date
  • configured allowed actions
  • intended command
  • interactive approval policy

Review inference: An agent has staged-publish access and is assumed able to approve or retag the release. The workflow can fail or be given broader authority than intended. Adds operation-level npm publishing authority and separate human approval rather than only project identity. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Token authentication or npm whoami is not proof of permission for every publishing command.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Allowed actions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Token authentication or npm whoami is not proof of permission for every publishing command.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Npm trusted publisher first use expiry

Question: Can an unused npm trusted-publisher configuration remain ready indefinitely?

A new configuration must complete its first successful publish within two days. That first publish validates it and binds the immutable repository identity. An unused configuration expires after that window and must be deleted and recreated before it can be used. Inspect validation state and date rather than treating the saved connection as operational evidence.

Source: npm: Trusted publishing with OIDC. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can an unused npm trusted-publisher configuration remain ready indefinitely?

Buyer evidence still required

  • configuration creation time
  • validation state
  • first successful publication
  • repository identity

Review inference: A release team creates publishing authority well before the first scheduled release. The dormant connection expires and blocks publication. Adds npm's initial validation expiry rather than only short-lived upload credentials. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A configured or validated publisher does not establish package-content safety or future workflow success.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Trusted publisher configuration expiry

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A configured or validated publisher does not establish package-content safety or future workflow success.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Npm trusted publisher token coexistence

Question: Does adding an npm trusted publisher disable traditional publishing tokens?

Trusted publishing adds an OIDC-authenticated publishing route alongside traditional tokens and manual publishing. Disallowing traditional tokens is a separate package setting; OIDC publishers continue to work when that restriction is applied. Review all enabled routes before describing the package as tokenless.

Source: npm: Trusted publishing with OIDC. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does adding an npm trusted publisher disable traditional publishing tokens?

Buyer evidence still required

  • trusted publisher configurations
  • package publishing-access setting
  • token inventory
  • manual-publish policy

Review inference: An operator removes a CI secret but leaves package token access enabled. Other long-lived credentials can still authorize publication. Adds npm's coexistence and separate restriction of old publishing authority. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A trusted publisher entry does not independently establish that legacy credentials were revoked.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. in addition to traditional authentication methods

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A trusted publisher entry does not independently establish that legacy credentials were revoked.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

npm: Ignoring install scripts does not disable explicit scripts

Question: Does npm ignore-scripts prevent an agent from executing npm test or npm run?

The npm v11 documentation says ignore-scripts suppresses package.json scripts during installation. Commands explicitly intended to run a script still execute that script, while their pre- and post-scripts are skipped. The flag is not a general command-execution boundary.

Source: npm-ci | npm Docs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does npm ignore-scripts prevent an agent from executing npm test or npm run?

Buyer evidence still required

  • npm version and effective configuration.
  • Install command and subsequent script commands.
  • Package script definitions and owner authority.

Suggested review condition: Do not describe an agent workflow as non-executing merely because installation used ignore-scripts.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. npm version and effective configuration. Install command and subsequent script commands. Package script definitions and owner authority.

Optional saved evidence: Review the actual agent command sequence rather than an installation setting alone.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Package safety, sandboxing or inspection of customer scripts
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Nylas MCP: Mailbox, calendar and outbound action scope

Question: Does connecting Nylas MCP give an agent only mailbox-reading access?

Nylas exposes mail, calendar, contacts and Notetaker operations, including state-changing actions. It requires an API key and connected account grant, with regional endpoints. The guide recommends narrowly scoped IAM keys for production agents; a working connection alone does not establish a read-only or single-account boundary. Sending requires the documented confirmation step; it does not replace owner approval or IAM restrictions.

Source: Nylas MCP server. Documentation checked 2026-10-17; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer installation and runtime untested

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Nylas operates the documented regional MCP service.

Documented by publisher. Nylas MCP server

Purpose

Use connected communications accounts through typed tools.

Documented by publisher. Nylas MCP server

Read capability

Permitted email, calendar and contact data.

Documented by publisher. Nylas MCP server

Write capability

Mail, calendar and Notetaker actions within effective grants.

Documented by publisher. Nylas MCP server

Authentication

Bearer authentication using a Nylas API key.

Documented by publisher. Nylas MCP server

Permission surface

Connected account grants and effective key permissions.

Documented by publisher. Nylas MCP server

Data leaving the environment

Communications data passes through Nylas and the selected agent client.

Review inference. Nylas MCP server

Failure modes to consider

An overly broad key can exceed the intended account or action scope.

Review inference. Nylas MCP server

Unknowns and applicability

Effective IAM policies, provider grants and client retention were not inspected.

Not established

Suggested refusal or clarification condition

Preserve required send confirmations and obtain exact account, recipient and action authority.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Application region, API-key policy, connected account grants and authorised actions.

Record history: 2026-10-17 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the account and action boundaries reviewed before communications automation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth active introspection and action authority

Question: Can a resource server treat an OAuth introspection active response as approval for the requested action?

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: RFC 7662: OAuth 2.0 Token Introspection. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a resource server treat an OAuth introspection active response as approval for the requested action?

Buyer evidence still required

  • Introspection response, issuer and observation time
  • Required operation, resource and applicable scope
  • Resource-server authorization rules and caching behaviour

Review inference: Evaluate applicable scope, audience and resource policy with sufficiently fresh token-state evidence before admitting an action.

Suggested review condition: Do not allow an action solely because active is true when its required authority has not been established.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The issuer's active semantics, response freshness and actual resource-server decision are buyer-specific.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid admitting an agent action merely because its credential remains live.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • 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

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth authorization response issuer comparison

Question: How should a multi-provider OAuth client verify the issuer of an authorization response?

RFC 9207 defines the iss authorization-response parameter. A supporting client compares it with the expected issuer using simple string comparison and rejects a mismatch. It must remember which configured servers support the parameter and reject a response missing iss from one that does. Expected issuer identity comes from server metadata or deployment-specific configuration.

Source: RFC 9207: OAuth 2.0 Authorization Server Issuer Identification. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: How should a multi-provider OAuth client verify the issuer of an authorization response?

Buyer evidence still required

  • Expected issuer configuration for this authorization flow
  • Response iss value and the server's declared support
  • Recorded issuer comparison and rejection handling

Review inference: Bind the response to the intended authorization server; receiving a code alone is insufficient evidence of issuer continuity.

Suggested review condition: Do not proceed with a mismatched issuer or a missing issuer from a server configured to support RFC 9207.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Correct initial trust in issuer configuration and enforcement in the deployed client were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a connector from accepting an authorization response for the wrong configured provider.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic trust in an arbitrary issuer URL or proof that the caller authorised every downstream action
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth client credentials and human approval

Question: Does an OAuth client-credentials token prove that a human approved this particular agent action?

RFC 6749 limits the client-credentials grant to confidential clients. The client requests access using its own authentication for resources under its control or access previously arranged with the authorization server. That authentication supplies the grant without an additional authorization request. The flow does not itself record a human's approval of each proposed action.

Source: RFC 6749: The OAuth 2.0 Authorization Framework. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an OAuth client-credentials token prove that a human approved this particular agent action?

Buyer evidence still required

  • Grant type, client registration and issued scope
  • Resource-access arrangement and applicable policy
  • Approval evidence bound to the proposed action when required

Review inference: Obtain separate action-specific authority evidence when a workflow requires human approval, even if the service can authenticate successfully.

Suggested review condition: Do not substitute a service token for a required human approval or assume it represents a named user.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual business delegation, resource permissions and any independent human approval remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Distinguish service access from the buyer approval required before a consequential agent action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Human consent to each action or unrestricted authority from possession of a service credential
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth evidence — Cached status and revocation window

Question: Does a cached active introspection result establish that an agent token has not since been revoked?

RFC 7662 permits response caching but warns that it can allow use after revocation until cached state expires. If exp is present, the response must not be cached past it. Cache duration is a resource-specific security and performance choice, not a guarantee of current validity.

Source: IETF RFC 7662: OAuth 2.0 Token Introspection. Documentation checked 2026-11-05; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a cached active introspection result establish that an agent token has not since been revoked?

Buyer evidence still required

  • Non-secret issuer, client and resource identity with applicable protocol/profile version
  • Relevant response fields, observation timestamps and correlation identifiers without credential values
  • Effective authorization or recovery policy and independent outcome evidence

Review inference: Do not treat cached active status as current revocation evidence without observation time, expiry and cache policy. The existing record separates liveness from action authority and mentions freshness. This decision adds the specific cache revocation window and mandatory exp ceiling for determining whether cached status remains usable. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not treat cached active status as current revocation evidence without observation time, expiry and cache policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 4 Security Considerations

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat cached active status as current revocation evidence without observation time, expiry and cache policy.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth evidence — Current actor versus historical actors

Question: May an authorization decision inherit authority from a prior actor nested inside an OAuth act claim?

RFC 8693 identifies the current actor in the outermost act claim. Nested actors are informational delegation history. Access-control decisions must consider only the top-level token claims and current actor, rather than granting authority from prior actors.

Source: IETF RFC 8693: OAuth 2.0 Token Exchange. Documentation checked 2026-11-05; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: May an authorization decision inherit authority from a prior actor nested inside an OAuth act claim?

Buyer evidence still required

  • Non-secret issuer, client and resource identity with applicable protocol/profile version
  • Relevant response fields, observation timestamps and correlation identifiers without credential values
  • Effective authorization or recovery policy and independent outcome evidence

Review inference: Do not promote historical actor identities into current permission; validate the token and applicable policy separately. The adjacent record concerns subject/actor request parameters and issuance policy. This decision governs downstream interpretation of an issued nested actor chain and excludes historical actors from current access control. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not promote historical actor identities into current permission; validate the token and applicable policy separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 4.1 act Actor Claim

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not promote historical actor identities into current permission; validate the token and applicable policy separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth evidence — Inactive result and disclosure limits

Question: Does active false in an introspection response identify revocation as the cause?

For an authorized call, RFC 7662 returns active false when the token is inactive, unknown to that server, or unavailable for that resource to inspect. Further cause information should be withheld. Invalid credentials for the inspection call instead produce an authorization error. The result alone does not identify the cause.

Source: IETF RFC 7662: OAuth 2.0 Token Introspection. Documentation checked 2026-11-05; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does active false in an introspection response identify revocation as the cause?

Buyer evidence still required

  • Non-secret issuer, client and resource identity with applicable protocol/profile version
  • Relevant response fields, observation timestamps and correlation identifiers without credential values
  • Effective authorization or recovery policy and independent outcome evidence

Review inference: Do not infer revocation, nonexistence or a specific offboarding cause from active false alone. The previous decision addresses active true versus action authority. This decision distinguishes inactive, undisclosed and unknown token states from caller-authentication failure, changing incident classification. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not infer revocation, nonexistence or a specific offboarding cause from active false alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 2.2 Introspection Response; 2.3 Error Response

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer revocation, nonexistence or a specific offboarding cause from active false alone.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth evidence — Issued representation and usage type

Question: Can every value in the token-exchange access_token field be sent as an OAuth Bearer credential?

RFC 8693 uses access_token as a response field even when the issued object is not an OAuth access token. issued_token_type describes its representation; token_type describes its use. N_A indicates that an OAuth usage type does not apply. The field name alone does not establish Bearer usability.

Source: IETF RFC 8693: OAuth 2.0 Token Exchange. Documentation checked 2026-11-05; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can every value in the token-exchange access_token field be sent as an OAuth Bearer credential?

Buyer evidence still required

  • Non-secret issuer, client and resource identity with applicable protocol/profile version
  • Relevant response fields, observation timestamps and correlation identifiers without credential values
  • Effective authorization or recovery policy and independent outcome evidence

Review inference: Do not select an authentication scheme from the field name; inspect issued type, usage type and recipient requirements. The adjacent record reviews whether requested delegation is granted. This decision prevents misuse of the resulting object by distinguishing representation from usage type, including outputs that are not access tokens. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not select an authentication scheme from the field name; inspect issued type, usage type and recipient requirements.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 2.2.1 Successful Response

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not select an authentication scheme from the field name; inspect issued type, usage type and recipient requirements.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth evidence — Scope across requested targets

Question: Does one scope list in a multi-target token exchange assign different scopes to different recipients?

RFC 8693 defines the request as asking for every requested scope at every requested target, rather than positional scope-to-recipient pairs. Broad requests may be refused, including with invalid_target. Requested combinations remain distinct from the rights actually issued.

Source: IETF RFC 8693: OAuth 2.0 Token Exchange. Documentation checked 2026-11-05; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does one scope list in a multi-target token exchange assign different scopes to different recipients?

Buyer evidence still required

  • Non-secret issuer, client and resource identity with applicable protocol/profile version
  • Relevant response fields, observation timestamps and correlation identifiers without credential values
  • Effective authorization or recovery policy and independent outcome evidence

Review inference: Do not interpret a shared scope list as per-recipient least privilege or proof of granted access. The RFC 8707 record assesses recipient trust and bearer replay across resources. This RFC 8693 decision instead defines scope-target request semantics and prevents a positional-mapping error before issuance. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not interpret a shared scope list as per-recipient least privilege or proof of granted access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 2.1.1 Relationship between Resource Audience and Scope

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not interpret a shared scope list as per-recipient least privilege or proof of granted access.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth evidence — Service failure and revocation recovery

Question: Can an agent mark credential revocation complete after the provider returns HTTP 503?

RFC 7009 requires a client receiving HTTP 503 to assume the token still exists. It may retry after a reasonable delay; Retry-After can indicate expected unavailability. A failed revocation request is not completion evidence.

Source: IETF RFC 7009: OAuth 2.0 Token Revocation. Documentation checked 2026-11-05; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an agent mark credential revocation complete after the provider returns HTTP 503?

Buyer evidence still required

  • Non-secret issuer, client and resource identity with applicable protocol/profile version
  • Relevant response fields, observation timestamps and correlation identifiers without credential values
  • Effective authorization or recovery policy and independent outcome evidence

Review inference: Keep revocation unresolved after HTTP 503. Later outcome and applicable scope require separate review; retries do not prove all access has ended. The existing record limits conclusions from HTTP 200. This decision concerns the explicit 503 recovery obligation and unresolved-token assumption, not the successful-response ambiguity. Operational review inference; no deployment outcome was observed.

Suggested review condition: Keep revocation unresolved after HTTP 503. Later outcome and applicable scope require separate review; retries do not prove all access has ended.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. 2.2.1 Error Response

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Keep revocation unresolved after HTTP 503. Later outcome and applicable scope require separate review; retries do not prove all access has ended.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth exact redirect URI comparison

Question: Can an OAuth server replace exact redirect URI matching with a trusted parent-domain check?

RFC 9700 requires exact string matching against pre-registered redirect URIs, apart from the localhost port exception for native applications. A parent-domain match or a general wildcard is not that comparison. The guidance also prohibits open redirectors in clients and authorization servers.

Source: RFC 9700: Best Current Practice for OAuth 2.0 Security. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an OAuth server replace exact redirect URI matching with a trusted parent-domain check?

Buyer evidence still required

  • Registered redirect URI and actual authorization request URI
  • Client application type and any localhost port exception
  • Callback redirect behaviour and server comparison configuration

Review inference: Review the exact registered callback and allowed exception rather than assuming every destination under a trusted domain is acceptable.

Suggested review condition: Do not rely on a trusted parent domain as evidence that the exact callback destination was authorised.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer server's matching behaviour, callback integrity and current registration were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid redirecting authorization results to an unapproved callback destination.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Validated deployment security or permission to broaden registered callback destinations
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth multiple-resource token issuance trust

Question: Is a multi-audience OAuth bearer token isolated from replay between its accepted recipients?

RFC 8707 explains that a bearer token usable at multiple resources can be replayed by one recipient at another. It recommends issuing access tokens for one resource at a time where possible, with authorization-server discretion over multi-resource requests. This is an issuance-policy decision; it does not introduce a new rule that every token is safe merely because an audience is present.

Source: IETF RFC 8707. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Is a multi-audience OAuth bearer token isolated from replay between its accepted recipients?

Buyer evidence still required

  • Requested resource set
  • Recipient trust relationships
  • Actual audience and issuance policy

Review inference: Assess mutual trust before issuing one bearer token to multiple recipients. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Retain only with the RFC8707 multi-resource issuance decision and its single-resource recommendation explicit. Do not claim this is a novel replay principle or extend it to sender-constrained tokens.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 3 in IETF RFC 8707 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Retain only with the RFC8707 multi-resource issuance decision and its single-resource recommendation explicit. Do not claim this is a novel replay principle or extend it to sender-constrained tokens.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth omitted resource policy

Question: Does omitting OAuth resource mean a token is valid at every resource server?

RFC 8707 allows an authorization server receiving no resource parameter to process the request without a specific resource, use a default resource, or reject it for lacking a resource. Omission does not establish unrestricted access or one universal default. Inspect the applicable policy and the resulting token restrictions.

Source: IETF RFC 8707. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does omitting OAuth resource mean a token is valid at every resource server?

Buyer evidence still required

  • Authorization-server policy
  • Request with omitted resource
  • Issued token restrictions or error

Review inference: Require the server default or rejection policy before reasoning about omitted audience. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Include all three documented possibilities; the current buyer_decision mentions default or rejection but omits processing with no specific resource. No option alone establishes arbitrary-server acceptance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 2.1 in IETF RFC 8707 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Include all three documented possibilities; the current buyer_decision mentions default or rejection but omits processing with no specific resource. No option alone establishes arbitrary-server acceptance.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth PKCE and confidential client authentication

Question: Can OAuth PKCE replace client authentication for a confidential authorization-code client?

RFC 9700 recommends PKCE for confidential clients as protection against authorization-code misuse. RFC 6749 separately requires client authentication for confidential clients or clients issued credentials when using the token endpoint. PKCE binds a code exchange to a verifier; it does not remove that client-authentication requirement.

Source: RFC 9700: Best Current Practice for OAuth 2.0 Security. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can OAuth PKCE replace client authentication for a confidential authorization-code client?

Buyer evidence still required

  • Client registration and confidential or public classification
  • Token endpoint authentication method and enforcement evidence
  • Transaction-specific PKCE challenge and verifier handling

Review inference: Review the client type, authentication method and PKCE exchange as separate controls rather than treating one successful verifier check as both.

Suggested review condition: Do not accept a confidential-client authentication claim supported only by PKCE use.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The deployed authentication checks, credential storage and correct verifier validation are not established by the specifications.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Check a connector login flow without confusing code interception protection with client identity.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete OAuth security or tested authentication from advertised PKCE support
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth RAR front-channel integrity

Question: Does sending payment authorization_details through a browser protect them from replacement?

RFC 9396 warns that authorization details sent through the front channel can be tampered with or swapped. It recommends integrity protection such as signed request objects or pushed authorization requests. Protecting those request terms does not establish that the server granted them, that the client may execute them, or that a payment settled.

Source: IETF RFC 9396. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does sending payment authorization_details through a browser protect them from replacement?

Buyer evidence still required

  • Request transport and integrity mechanism
  • Original and received authorization details
  • Returned grant and later outcome

Review inference: Bind the approved payment terms to an integrity-protected authorization request. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Preserve the source conditional: when parameter integrity is a concern it MUST be protected. Signing or pushing the request does not prove user approval, transaction execution, payment settlement, or a secure deployment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 12 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Preserve the source conditional: when parameter integrity is a concern it MUST be protected. Signing or pushing the request does not prove user approval, transaction execution, payment settlement, or a secure deployment.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth RAR invalid authorization details

Question: May an OAuth RAR server silently ignore unknown fields in a known authorization-details type?

RFC 9396 requires rejection with invalid_authorization_details for unknown types, invalid fields or values, and missing required fields. A type definition can expressly permit extension fields, so not every unfamiliar field is automatically invalid. Validation must use the supported type definition rather than silently accepting malformed authority terms.

Source: IETF RFC 9396. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: May an OAuth RAR server silently ignore unknown fields in a known authorization-details type?

Buyer evidence still required

  • Supported RAR type versions
  • Required fields and extension policy
  • Actual validation response

Review inference: Fail closed on malformed or unrecognized fine-grained authority descriptions. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. The applicable type definition determines which fields are known. Do not reject legitimate type-defined extensions merely because they are not common RFC fields, or claim deployed enforcement was tested.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 5 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The applicable type definition determines which fields are known. Do not reject legitimate type-defined extensions merely because they are not common RFC fields, or claim deployed enforcement was tested.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth RAR permission combinations

Question: Does one OAuth RAR object pair each action with just one listed resource location?

RFC 9396 applies the common actions, locations and datatypes of one authorization-details object as a cross-product. Arrays do not implicitly pair their positions. Separate authorization-details objects can express distinct combinations. A client must inspect the type-specific semantics and the complete combinations before treating a request as narrowly scoped.

Source: IETF RFC 9396. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does one OAuth RAR object pair each action with just one listed resource location?

Buyer evidence still required

  • Applicable type definition
  • All actions, locations and datatypes
  • Intended permitted combinations

Review inference: Avoid accidental permission multiplication across action, location and data-type arrays. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Limit the rule to the RFC common fields as used by the applicable type; do not invent semantics for arbitrary extension fields. A request is not an issued grant.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 2.2 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Limit the rule to the RFC common fields as used by the applicable type; do not invent semantics for arbitrary extension fields. A request is not an issued grant.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth RAR requested terms and returned grant

Question: Can an OAuth RAR client treat its requested payment amount and recipient as the granted authority?

RFC 9396 requires the authorization details granted to the access token to be returned. They can differ from the request: consent can reduce permissions, a type can permit enrichment, and the server can omit values. Interpret the returned grant using that type before relying on the requested transaction terms. This does not establish payment execution.

Source: IETF RFC 9396. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an OAuth RAR client treat its requested payment amount and recipient as the granted authority?

Buyer evidence still required

  • Requested and returned authorization_details
  • Applicable RAR type semantics
  • Actual token grant and intended transaction

Review inference: Compare the returned authorization details with the requested transaction before using the token. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Compare the actual token grant with the intended transaction using the applicable RAR type. The server may omit values; the fictitious payment example is not a universal payment schema or settlement proof.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Sections 3, 7 and 7.1 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Compare the actual token grant with the intended transaction using the applicable RAR type. The server may omit values; the fictitious payment example is not a universal payment schema or settlement proof.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth RAR semantic downscoping

Question: Does a JSON subset comparison establish that revised OAuth RAR details reduce authority?

RFC 9396 permits authorization_details on a token request to reduce the permissions of the issued token. The server must use type-specific semantics to decide whether the requested permissions are a subset; structural JSON comparison alone is insufficient. Issuing the reduced token does not change the underlying authorization grant.

Source: IETF RFC 9396. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a JSON subset comparison establish that revised OAuth RAR details reduce authority?

Buyer evidence still required

  • Original grant
  • Requested reduced permissions
  • Type-specific subset rules

Review inference: Require type-specific comparison rules before accepting a claimed downscope. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Do not prescribe a universal comparator, assume all permissions are additive, or infer that narrowing one token revokes the original grant.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 6.1 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not prescribe a universal comparator, assume all permissions are additive, or infer that narrowing one token revokes the original grant.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth RAR string comparison

Question: May an OAuth RAR verifier normalize differently spelled identifiers before comparing authority?

RFC 9396 requires strings in authorization_details to be compared as defined by RFC 8259, without additional transformation or normalization. This is a rule for string values, not a requirement that serialized JSON documents be byte-identical. Applying an extra case or Unicode transformation can change the permission comparison.

Source: IETF RFC 9396. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: May an OAuth RAR verifier normalize differently spelled identifiers before comparing authority?

Buyer evidence still required

  • Original parsed string values
  • Type interpretation
  • Comparison and normalization behavior

Review inference: Avoid creating authority equivalence beyond the specification string comparison rule. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Clarify comparison after valid JSON decoding; this is not byte-for-byte equality of serialized JSON, object member order, or whitespace. Do not equate visually similar identifiers.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 12 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Clarify comparison after valid JSON decoding; this is not byte-for-byte equality of serialized JSON, object member order, or whitespace. Do not equate visually similar identifiers.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth refresh grant and requested resource subset

Question: Can a multi-resource OAuth grant produce a token limited to one selected resource?

RFC 8707 allows a token request to select a subset of the resources authorized by the grant. The resulting access token can be restricted to that subset while a refresh token remains associated with the full authorized set. Resource selection must remain within the grant and authorization-server policy; a narrow access token does not prove the underlying grant was reduced.

Source: IETF RFC 8707. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a multi-resource OAuth grant produce a token limited to one selected resource?

Buyer evidence still required

  • Original authorized resource set
  • Token request resource subset
  • Issued access and refresh-token policy

Review inference: Separate the overall grant from the narrower authority of an individual token. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Preserve grant-type and AS-policy qualifications; a client request alone does not force universal issuance or narrow the original refresh grant.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 2.2 in IETF RFC 8707 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Preserve grant-type and AS-policy qualifications; a client request alone does not force universal issuance or narrow the original refresh grant.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth refresh validity and invalid_grant evidence

Question: Can an agent treat a retained refresh token or an invalid_grant response as proof of continuing authority?

RFC 6749 requires the server to validate a refresh token and bind it to the client. Its invalid_grant error can mean an invalid, expired or revoked grant or refresh token, a redirect mismatch, or issuance to another client. Possessing saved credentials does not establish validity, and the error alone does not identify one unique revocation cause.

Source: rfc6749. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an agent treat a retained refresh token or an invalid_grant response as proof of continuing authority?

Buyer evidence still required

  • Client binding and grant-state evidence
  • Sanitized token-endpoint error and timing
  • Provider-approved reauthorization or recovery procedure

Review inference: Stop relying on the credential after rejection and obtain the applicable grant-state and recovery evidence.

Suggested review condition: Do not keep claiming authority from retained bytes or diagnose a unique revocation cause from invalid_grant alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The provider’s actual grant state and rejection cause remain unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent stale credentials and ambiguous errors from becoming an authority assumption.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal instant invalidation of all access tokens when a grant changes
  • The provider’s actual grant state and rejection cause remain unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth resource identifiers and token audience

Question: Must an access token audience equal the exact OAuth resource parameter string?

RFC 8707 permits resource to identify a protected resource with an absolute URI, including an abstract identifier rather than a network locator. The authorization server can map that value to a more general URI or abstract audience. Endpoint location, resource identifier and issued audience therefore need an established mapping; none authorizes an arbitrary destination.

Source: IETF RFC 8707. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Must an access token audience equal the exact OAuth resource parameter string?

Buyer evidence still required

  • Requested resource identifier
  • Authorization-server audience mapping
  • Actual endpoint and audience validation

Review inference: Verify the authorization server mapping rather than rejecting or accepting by raw string alone. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Never authorize arbitrary audience mismatch. Establish the AS mapping and the relying resource validation rule; preserve protocol-specific stricter rules such as MCP.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 2 in IETF RFC 8707 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Never authorize arbitrary audience mismatch. Establish the AS mapping and the relying resource validation rule; preserve protocol-specific stricter rules such as MCP.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth resource parameter does not filter RAR

Question: Does an OAuth resource parameter automatically narrow authorization_details to that server?

RFC 9396 states that the resource parameter does not change how an authorization server processes authorization_details. A resource value is therefore not a filter that silently removes other detailed permissions. The RAR type, its locations and the actual granted details need separate review before relying on a restricted target.

Source: IETF RFC 9396. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an OAuth resource parameter automatically narrow authorization_details to that server?

Buyer evidence still required

  • resource request values
  • RAR locations and type semantics
  • Actual granted details

Review inference: Prevent treating the resource indicator as a filter over rich authorization details. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Do not claim that resource is ignored for scope or that authorization_details can bypass audience validation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 3.2 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim that resource is ignored for scope or that authorization_details can bypass audience validation.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth revocation success and invalid-token ambiguity

Question: Does an OAuth token revocation HTTP 200 prove that the submitted token previously existed?

RFC 7009 returns HTTP 200 both when revocation succeeds and when the submitted token is invalid; clients ignore the response body. An invalid token is not an error because the requested invalidation outcome is already satisfied. The response therefore does not establish that a particular valid credential existed or that every related credential was revoked.

Source: RFC 7009: OAuth 2.0 Token Revocation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an OAuth token revocation HTTP 200 prove that the submitted token previously existed?

Buyer evidence still required

  • Non-secret credential inventory and issuer identity
  • Revocation request identity, time and response status
  • Documented related-token scope and residual-access checks

Review inference: Retain credential inventory and applicable revocation-scope evidence separately from the acknowledgement.

Suggested review condition: Do not claim a complete offboarding inventory or universal credential revocation from a single HTTP 200 response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Prior token validity, related credential state and residual access in the buyer deployment were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep offboarding receipts honest about what the provider acknowledgement proves.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof of historical token existence or revocation of every related credential
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth scope and RAR combined consent

Question: Can an agent ignore OAuth scope when authorization_details is present in the same request?

RFC 9396 allows scope and authorization_details in the same request. Their permissions are combined according to the applicable API semantics, and the authorization server must present the combined authorization requirements to the user. Neither field should be assumed to cancel or supersede the other without the relevant definition.

Source: IETF RFC 9396. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an agent ignore OAuth scope when authorization_details is present in the same request?

Buyer evidence still required

  • Both request fields
  • API combination semantics
  • Consent and returned authorization

Review inference: Reconcile both independently supplied permission descriptions and consent. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. The combination algorithm is API-specific, not a universal union or intersection. Keep AS obligations separate from client policy and actual consent evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Section 3.1 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The combination algorithm is API-specific, not a universal union or intersection. Keep AS obligations separate from client policy and actual consent evidence.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OAuth token exchange delegation evidence

Question: Does supplying a subject token and requested audience automatically grant delegated OAuth authority?

RFC 8693 distinguishes the subject token from an optional actor token representing the party receiving delegated rights. Issuing a composite token depends on authorization-server policy and configuration. Request parameters describe desired delegation; they do not themselves establish an approved grant to the actor for the target resource.

Source: RFC 8693: OAuth 2.0 Token Exchange. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does supplying a subject token and requested audience automatically grant delegated OAuth authority?

Buyer evidence still required

  • Subject and actor identities without exposing token secrets
  • Authorization-server exchange policy and requested audience
  • Issued token scope, audience and delegation representation

Review inference: Review exchange policy, authenticated actor and issued token restrictions together.

Suggested review condition: Reject a delegation claim supported only by the submitted exchange request.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The authorization server’s applicable policy and actual issued token are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Verify a delegated agent’s authority at the exchange boundary.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic cross-audience authority from possession of a token
  • The authorization server’s applicable policy and actual issued token are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth: Public-client PKCE requirement

Question: What does RFC 9700 require for public clients using authorization codes?

RFC 9700 requires PKCE for public clients using the authorization code grant. A claim of PKCE support still needs evidence that the deployed flow enforces it.

Source: RFC 9700: Authorization Code Grant. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • correct PKCE enforcement
  • complete OAuth security
  • tested protection from a library feature list

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth: Security guidance scope

Question: Does citing RFC 9700 establish that an OAuth deployment is secure?

RFC 9700 documents OAuth 2.0 security best practices and updates earlier guidance. Citation alone does not demonstrate that a deployment implements the relevant requirements.

Source: RFC 9700: OAuth 2.0 Security Best Current Practice. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • deployment conformance
  • complete security assurance
  • authorization for an agent action

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth: Sender-constrained token scope

Question: What can sender-constrained access tokens support in an OAuth security claim?

RFC 9700 recommends sender-constraining access tokens to reduce misuse of stolen tokens. A deployment claim needs evidence that the relevant proof is checked; the mechanism is not a universal compromise guarantee.

Source: RFC 9700: Access Tokens. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • all token theft prevented
  • proof verification in an untested deployment
  • protection after all relevant key material is compromised

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OAuth: Server metadata scope

Question: Does OAuth server metadata prove the deployment is correctly configured?

RFC 9700 recommends publishing authorization server metadata and using it where available. Metadata supports configuration but does not prove that advertised controls are correctly enforced.

Source: RFC 9700: Other Recommendations. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • correct enforcement of advertised features
  • trusted configuration without issuer checks
  • complete deployment validation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OIDC workflows: Caller and reusable-job identity

Question: Does a valid GitHub OIDC token prove an approved reusable deployment workflow ran?

For reusable workflows, ordinary workflow and ref claims describe the caller, while job_workflow_ref identifies the called workflow. Cloud trust policies must use the supported claim or subject conditions for the intended restriction. Token validity alone does not establish that the buyer configured an approved-workflow boundary.

Source: GitHub: OIDC with reusable workflows. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A valid token proves the expected reusable workflow was authorized.

Buyer evidence still required

  • Caller identity and called-workflow reference.
  • Cloud-provider claim support and actual trust policy.
  • Dated token-claim evidence with sensitive token material removed.

Suggested review condition: Check caller and callee restrictions separately before accepting workflow-specific cloud access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Caller, reusable workflow revision, provider-supported claims and effective trust conditions.

Optional saved evidence: Save the identity binding behind a deployment-credential decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Okta API tokens: Owner changes affect ongoing automation

Question: Is an Okta API token's authority fixed when it is created?

Okta API tokens follow the creating user's permissions, including later permission changes, and require that user to remain active. Their inactivity expiry renews with use. Procurement should check the owner lifecycle and effective privileges, rather than assuming a fixed permission grant or fixed maximum lifetime.

Source: Okta: Manage API tokens. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Is an Okta API token's authority fixed when it is created?

Buyer evidence still required

  • Token owner identity and current roles.
  • Owner activation state and intended lifecycle.
  • Last-use and expiry evidence for the token.

Suggested review condition: Do not treat a token created by an administrator as a permanently fixed or narrowly scoped entitlement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token owner, current role, activation and inactivity evidence.

Optional saved evidence: Save the owner-dependency review for identity automation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Okta MCP: Scope filtering and administrative identity

Question: Does the Okta MCP server expose only directory reads?

The server loads tools according to configured scopes. Read scopes and manage scopes expose different operations, and manage scopes also cover reads. Device authorization and private-key JWT are documented alternatives; granted API scopes and assigned admin roles must match the intended task.

Source: Okta self-hosted MCP server. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Publisher self-hosted Management API server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Okta publishes the server; the buyer hosts it.

Documented by publisher. Okta self-hosted MCP server

Purpose

Access Okta management operations from an MCP client.

Documented by publisher. Okta self-hosted MCP server

Read capability

Directory, application, policy and diagnostic information.

Documented by publisher. Okta self-hosted MCP server

Write capability

Manage scopes can expose administrative changes.

Documented by publisher. Okta self-hosted MCP server

Authentication

Device authorization or private-key JWT.

Documented by publisher. Okta self-hosted MCP server

Permission surface

Configured scopes, granted scopes and admin roles matter.

Documented by publisher. Okta self-hosted MCP server

Data leaving the environment

Tenant results pass through the local server to the agent.

Review inference. Okta self-hosted MCP server

Failure modes to consider

Scope mismatch or identity configuration can block or broaden access.

Review inference. Okta self-hosted MCP server

Unknowns and applicability

Effective roles, token storage and hosted environment are untested.

Not established

Suggested refusal or clarification condition

Do not authorise directory mutations for a read-only question.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Scope-to-tool mapping, tenant support and role assignments.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the distinction between tool filtering and the underlying administrative identity.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Okta service apps: OAuth grants and administrative roles

Question: Are OAuth scopes alone sufficient evidence of the authority granted to an Okta service app?

Okta documents both scope grants and administrative role assignments for service apps. Roles constrain permissions and resources; an organization setting can also automatically assign a broad administrative role. Review the app grants, roles and organization settings together before claiming least-privilege access.

Source: Okta OAuth service app scopes and administrative roles. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The service app scope list completely establishes its effective authority.

Buyer evidence still required

  • Granted Okta API scopes
  • Admin role assignments and applicable resource sets
  • Relevant organization setting and dated access review

Suggested review condition: Require role and resource evidence when scope names alone are offered as a least-privilege claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck role assignments, scope grants, resource sets and automatic-role settings.

Optional saved evidence: Preserve the reviewed identity, role and scope combination for a service integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Okta: Session removal and OAuth-token revocation are separate

Question: Does removing an Okta session prove that related API tokens were revoked?

The guide separates session cookies from access and refresh tokens. Removing all user sessions can optionally include token revocation through a specific parameter. A successful revocation response also covers already-invalid tokens. Record the operation and its options, then verify the relevant access outcome.

Source: Okta token revocation and sessions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Successful session removal proves all related API access ended.

Buyer evidence still required

  • Exact session/token revocation operation and options.
  • Relevant token family and application session inventory.
  • Authorised verification of the intended access outcome.

Suggested review condition: Do not equate a successful session API response with complete token invalidation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Session/token inventory, operation options and application behaviour.

Optional saved evidence: Save what the offboarding action actually covered and which access outcomes still need proof.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPA logs: Masked evidence is not the original input

Question: Can an exported OPA decision log be assumed to preserve the exact policy input and result?

OPA can erase or modify decision-log fields through a masking policy before upload or custom-plugin delivery. The log records erased or masked paths. A retained decision record can therefore differ from the original input or decision and needs that transformation context.

Source: Open Policy Agent: Decision logs. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an exported OPA decision log be assumed to preserve the exact policy input and result?

Buyer evidence still required

  • Applicable masking policy and revision.
  • Decision record with erased or masked paths.
  • Authorised independent evidence for any required missing field.

Suggested review condition: Preserve masking provenance without reintroducing protected values into the review.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Decision identity, masking policy revision and retained field markers.

Optional saved evidence: Can an exported OPA decision log be assumed to preserve the exact policy input and result?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPA: Decision versus enforcement

Question: Does an OPA decision by itself enforce an agent's permissions?

OPA separates policy evaluation from enforcement. The calling application must apply the decision at the relevant action boundary; a returned decision alone does not establish that enforcement occurred.

Source: Open Policy Agent. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • automatic enforcement by a decision response
  • absence of bypass paths
  • complete deployment protection

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPA: Decisions over structured input

Question: Can OPA evaluate policy for a proposed agent action?

OPA evaluates policy against structured input. An agent action must be represented by suitable input and policy; this record does not show that a buyer's rules are complete or correct.

Source: Open Policy Agent. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • a buyer's policy correctness
  • automatic discovery of all relevant context
  • deployment approval

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPA: Distributed policy deployment

Question: Can OPA run alongside services that need policy decisions?

OPA documents deployment alongside services and management interfaces for policy distribution and telemetry. Documentation of this architecture does not establish latency or availability for a particular installation.

Source: OPA Management APIs and Architecture. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • measured customer latency
  • high availability of a named deployment
  • automatic consistency of every policy instance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPA: Downloaded policy is not necessarily active policy

Question: Does publishing a newly signed OPA bundle prove that running agents use it?

OPA activates a signed bundle only after successful configured verification. On verification failure it retains the existing bundle and reports activation failure through status and error logging. Publication alone does not establish the active policy revision.

Source: Open Policy Agent: Bundles. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does publishing a newly signed OPA bundle prove that running agents use it?

Buyer evidence still required

  • Published revision and configured verification key.
  • OPA activation status and error evidence.
  • Active revision associated with the relevant decision.

Suggested review condition: Bind a policy-change claim to successful activation on the deciding instance, not only publication.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Bundle revision, signing configuration, activation status and decision time.

Optional saved evidence: Does publishing a newly signed OPA bundle prove that running agents use it?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPA: HTTP success can carry no policy result

Question: Can a successful OPA Data API response be interpreted as an allow decision?

OPA documents HTTP 200 with an omitted result field when a Data API document is undefined. HTTP success and the policy decision are separate. A caller must inspect the expected result rather than treating transport success as permission.

Source: Open Policy Agent: REST API. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a successful OPA Data API response be interpreted as an allow decision?

Buyer evidence still required

  • Exact policy path and input.
  • Response body including result presence and type.
  • Caller handling for false, undefined and request errors.

Suggested review condition: Require an explicit expected decision; do not coerce a missing result into an allow.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Data API path, input, expected decision shape and caller handling of undefined results.

Optional saved evidence: Can a successful OPA Data API response be interpreted as an allow decision?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPA: Management interfaces

Question: What do OPA's management interfaces cover?

OPA documents interfaces for policy bundles, decision logs, status and discovery configuration. Integrators configure or implement the surrounding management service; the interfaces alone are not a completed control plane.

Source: OPA Management APIs and Architecture. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • a deployed management service
  • complete audit retention
  • secure handling of every decision log

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPC UA certificate ApplicationURI binding

Question: Can an OPC UA endpoint be accepted when its ApplicationURI differs from the certificate identity?

OPC UA Part 4 version 1.05.07 requires application URI consistency between the certificate and application description. CreateSession specifies client and server checks, including Bad_CertificateUriInvalid for a client mismatch. Certificate trust alone does not satisfy this application-identity binding.

Source: Determining if a Certificate is trusted – OPC Unified Architecture - Part 4: Services. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an OPC UA endpoint be accepted when its ApplicationURI differs from the certificate identity?

Buyer evidence still required

  • Certificate URI and ApplicationDescription URI
  • Endpoint/session identity evidence
  • Applicable OPC UA version and validation results

Review inference: Verify URI consistency using the applicable protocol version before accepting the session.

Suggested review condition: Refuse identity acceptance when the required application URI binding fails.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual endpoint certificate and session checks are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Detect identity substitution or misconfiguration before industrial access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A guarantee that older protocol versions have identical validation rules
  • The actual endpoint certificate and session checks are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPC UA method calls and physical completion

Question: Does an OPC UA Call result alone prove that the intended physical operation completed?

OPC UA Call returns per-method execution status and outputs under the method’s application-defined semantics. The specification says results can be discarded when a session terminates independently of the actual server task, and execution order for multiple operations is undefined. A generic call outcome does not supply a universal physical-completion criterion.

Source: Call – OPC Unified Architecture - Part 4: Services. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an OPC UA Call result alone prove that the intended physical operation completed?

Buyer evidence still required

  • Method definition and object identity
  • Per-method results and operation correlation
  • Independent process completion or failure evidence

Review inference: Bind the method’s documented semantics to operation identifiers and process-specific completion observations.

Suggested review condition: Do not infer physical acceptance or ordered execution from a batch Call response alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Physical outcomes and application-specific completion semantics remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid repeating or closing an uncertain industrial action on protocol status alone.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed industrial completion, safety or exactly-once operation
  • Physical outcomes and application-specific completion semantics remain unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPC UA monitored-item loss indicators

Question: Does receiving OPC UA subscription updates prove every intermediate value was preserved?

OPC UA monitored items sample values and queue notifications. When a queue larger than one overflows, the specified overflow indication records loss while discard settings decide which queued value is removed. A queue of one behaves differently and does not use that overflow indication. Sampling itself can miss changes between samples.

Source: MonitoredItem model – OPC Unified Architecture - Part 4: Services. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does receiving OPC UA subscription updates prove every intermediate value was preserved?

Buyer evidence still required

  • Sampling and publishing intervals
  • Queue size and discard policy
  • Status bits and expected process change frequency

Review inference: Review sampling, queue size and discard policy before using updates as a complete process history.

Suggested review condition: Decline complete-transition claims from received notifications alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Changes between samples and overwritten values cannot be reconstructed from this stream alone.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify missing transitions before relying on a subscription as audit evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete physical-event capture or lossless industrial telemetry
  • Changes between samples and overwritten values cannot be reconstructed from this stream alone.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPC UA sequence gaps and retransmission limits

Question: Can OPC UA Republish reconstruct every missing notification after a sequence gap?

OPC UA subscriptions sequence NotificationMessages and may retain them in a retransmission queue. Republish requests a particular retained sequence number; Bad_MessageNotAvailable indicates the requested message is unavailable. Detecting a sequence gap therefore does not establish that the missing content can still be recovered.

Source: Subscription model – OPC Unified Architecture - Part 4: Services. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can OPC UA Republish reconstruct every missing notification after a sequence gap?

Buyer evidence still required

  • Subscription and sequence range
  • Available sequence numbers and Republish results
  • Gap handling and application recovery policy

Review inference: Reconcile sequence numbers, available retransmissions and unrecoverable gaps explicitly.

Suggested review condition: Do not mark a notification history complete while required sequence gaps remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Content no longer retained by the server is unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Separate gap detection from successful recovery of industrial evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed reconstruction of every physical event
  • Content no longer retained by the server is unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPC UA trusted applications and node permissions

Question: Does trusting an OPC UA application certificate authorize every node operation for its user?

OPC UA Part 4 separates application certificate trust and user authentication from authorization. Even when an external authorization service is involved, the server remains responsible for enforcing node permissions. Trusting an application does not describe the user’s permitted operations on each node.

Source: Authorization Services – OPC Unified Architecture - Part 4: Services. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does trusting an OPC UA application certificate authorize every node operation for its user?

Buyer evidence still required

  • Validated application certificate and trust configuration
  • Activated session user identity
  • Effective node permissions for each intended operation

Review inference: Check application identity, user identity and node permissions as separate decisions.

Suggested review condition: Reject unrestricted-operation claims based only on a trusted certificate.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual server permission configuration and user session are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a trusted connection from being mistaken for unrestricted industrial control.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Industrial safety approval from certificate trust
  • The actual server permission configuration and user session are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OPC UA value quality and freshness

Question: Does a Good OPC UA DataValue status prove the underlying measurement is fresh?

OPC UA Part 4 distinguishes a value’s status from sourceTimestamp and serverTimestamp. The source timestamp identifies the source’s value or status change, while the server timestamp reflects the server’s knowledge of the value. A Good status is not a freshness threshold or independent sensor calibration result.

Source: DataValue – OPC Unified Architecture - Part 4: Services. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Good OPC UA DataValue status prove the underlying measurement is fresh?

Buyer evidence still required

  • DataValue status and both timestamps
  • Clock assumptions and sampling configuration
  • Buyer-defined freshness threshold and sensor assurance evidence

Review inference: Assess source time, server time and the process-specific maximum acceptable age together.

Suggested review condition: Refuse freshness approval from Good status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual sensor accuracy, clock alignment and acceptable process age are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid automating a consequential decision from stale telemetry.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Certification of sensor accuracy or physical-process safety
  • Actual sensor accuracy, clock alignment and acceptable process age are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Open Payments completion and received amounts

Question: Does marking an Open Payments incoming resource complete prove that a target amount was paid?

The reviewed completion API tells the recipient account servicing entity that no further payments will be sent toward an unexpired incoming resource. The resource model also permits sessions without an incomingAmount. Completion therefore needs to be reconciled with received-amount evidence rather than interpreted as proof of an independently specified purchase total.

Source: Complete an incoming payment. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does marking an Open Payments incoming resource complete prove that a target amount was paid?

Buyer evidence still required

  • Incoming resource and any amount ceiling
  • Completion event and actual received amounts
  • Agreed purchase total and allocation

Review inference: Separate closing a payment session from satisfying a commercial amount due. This is a review decision, not an observed buyer result.

Suggested review condition: Do not infer that a commercial target was fully paid from completion alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual received funds and satisfaction of the buyer invoice are not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual received funds and satisfaction of the buyer invoice are not assessed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Open Payments grants for unspecified future recipients

Question: Does an Open Payments outgoing grant always identify the recipient before consent is obtained?

The reviewed future-payments guide supports obtaining sender-side authority before the recipient is known. Its example authorises a bounded monthly amount for future destinations, as used by Web Monetization. Possession of that grant does not establish that a particular later merchant was individually identified during the initial consent.

Source: Get an outgoing payment grant for future payments. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an Open Payments outgoing grant always identify the recipient before consent is obtained?

Buyer evidence still required

  • Approved grant scope and limits
  • Actual recipient discovered for the later request
  • Buyer policy governing recipient selection

Review inference: Distinguish a flexible future-spend grant from approval of a named supplier. This is a review decision, not an observed buyer result.

Suggested review condition: Do not describe a recipient-unspecified grant as evidence of approval for a named merchant.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer consent details, selected recipient and account configuration remain unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Buyer consent details, selected recipient and account configuration remain unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Open Payments incoming amount and payment allocation

Question: Does Open Payments incomingAmount require exactly one payment of that amount?

The pinned resource model describes incomingAmount as the maximum to pay into the recipient account. One or more payments may use the incoming resource details, but their combined amounts cannot exceed that maximum. The field is an aggregate ceiling, not proof of one exact transfer or complete commercial payment.

Source: Resources. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does Open Payments incomingAmount require exactly one payment of that amount?

Buyer evidence still required

  • Incoming resource and maximum amount
  • All associated received-payment records
  • Commercial order allocation and outstanding amount

Review inference: Reconcile partial payments against a shared incoming resource without inventing a one-to-one transfer. This is a review decision, not an observed buyer result.

Suggested review condition: Do not infer one exact transfer from the incomingAmount field.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual incoming payments and allocation completeness remain unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual incoming payments and allocation completeness remain unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Open Payments interval ceilings and unused amounts

Question: Does unused Open Payments recurring-grant allowance roll into the next interval?

The pinned future-payments guide describes an amount that resets for each configured interval, without carrying forward the unused portion. Its example also bounds the number of repetitions and the start time. A monthly allowance is not a cumulative balance that grows when earlier periods are underspent.

Source: Get an outgoing payment grant for future payments. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does unused Open Payments recurring-grant allowance roll into the next interval?

Buyer evidence still required

  • Approved maximum and asset
  • Interval start, duration and repetition count
  • Usage attributed to the current interval

Review inference: Avoid overstating remaining delegated spending authority across billing periods. This is a review decision, not an observed buyer result.

Suggested review condition: Do not add unused previous-interval allowance to the current spending limit.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual grant, remaining amount and provider enforcement are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • The actual grant, remaining amount and provider enforcement are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Open Payments outgoing instructions and settlement

Question: Does creating an Open Payments outgoing resource prove that inter-provider settlement completed?

The reviewed resource model says an outgoing resource can represent a payment that will be, is being or was sent. It is an instruction to the sender account servicing entity. Open Payments supplies payment instructions; settlement between the account servicing entities uses a separate shared rail.

Source: Resources. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does creating an Open Payments outgoing resource prove that inter-provider settlement completed?

Buyer evidence still required

  • Outgoing resource identity and current state
  • Sender and recipient account servicing entities
  • Applicable rail settlement and receipt evidence

Review inference: Require a supported payment outcome beyond successful creation of an instruction. This is a review decision, not an observed buyer result.

Suggested review condition: Do not release an entitlement solely because an outgoing-payment resource was created.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No inter-provider settlement or actual recipient credit is verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • No inter-provider settlement or actual recipient credit is verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Open Payments quote validity and replacement

Question: Can an Open Payments recurring payment keep using the original quote after it expires?

The reviewed guide states that quote responses include expiresAt and the outgoing payment should be created before that time. If creation fails because the quote expired, a new quote is required. A reusable grant does not extend the lifetime of the separately quoted payment terms.

Source: Set up recurring payments with a fixed incoming amount. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an Open Payments recurring payment keep using the original quote after it expires?

Buyer evidence still required

  • Accepted quote ID, amounts and expiry
  • Outgoing-payment creation outcome
  • Replacement quote and applicable buyer approval

Review inference: Keep authority, accepted cost and a currently valid quote aligned. This is a review decision, not an observed buyer result.

Suggested review condition: Do not reuse expired quoted terms merely because the spending grant remains valid.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The latest quoted price and adequacy of buyer approval remain unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • The latest quoted price and adequacy of buyer approval remain unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Open Payments recurring authority and payment initiation

Question: Does obtaining an Open Payments recurring grant automatically initiate every later payment?

The reviewed recurring-payment guide requires the application to create a new incoming payment, quote and outgoing payment at each later interval. Existing grants may remain usable, but they do not replace those resource requests. Authority to make periodic payments is separate from scheduling and successfully initiating them.

Source: Set up recurring payments with a fixed incoming amount. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does obtaining an Open Payments recurring grant automatically initiate every later payment?

Buyer evidence still required

  • Grant duration and current token
  • Per-interval incoming, quote and outgoing resources
  • Scheduling and payment outcome records

Review inference: Distinguish an authorised recurring budget from evidence that a subscription charge occurred. This is a review decision, not an observed buyer result.

Suggested review condition: Do not report an interval payment merely because recurring consent exists.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual scheduling, resource creation and financial outcomes are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual scheduling, resource creation and financial outcomes are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Open Payments sender cost and recipient amount

Question: Does an Open Payments fixed-send quote guarantee the recipient receives that same amount?

The reviewed resource model distinguishes fixed-send quotes, which specify the amount debited from the sender, from fixed-receive quotes, which specify the amount received. A quote accounts for applicable costs and is time-limited. The debit and receipt objectives are different and should be preserved separately in reconciliation.

Source: Resources. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an Open Payments fixed-send quote guarantee the recipient receives that same amount?

Buyer evidence still required

  • Quote type and validity
  • Debit and receive amounts with asset details
  • Agreed buyer budget and recipient obligation

Review inference: Select the correct cost commitment when supplier receipt and buyer budget differ. This is a review decision, not an observed buyer result.

Suggested review condition: Do not substitute a sender debit commitment for a recipient receipt commitment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual conversion, fees and received value have not been independently reconciled.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual conversion, fees and received value have not been independently reconciled.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Open Payments spend reporting scope

Question: Does Open Payments spent-amount retrieval return the lifetime total for a recurring grant?

The reviewed API guide identifies the current grant through the supplied access token and returns its debit and receive amounts. For a recurring grant, the reported amounts cover the current interval only. A lifetime spend history cannot be inferred from that one response.

Source: Get spent amounts for current outgoing payment grant. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does Open Payments spent-amount retrieval return the lifetime total for a recurring grant?

Buyer evidence still required

  • Access token grant association
  • Current interval and returned debit/receive amounts
  • Separately retained earlier-interval payment records

Review inference: Reconcile interval allowances without mistaking a scoped response for complete historical spend. This is a review decision, not an observed buyer result.

Suggested review condition: Do not label a current-interval response as lifetime grant expenditure.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Historical payments and completeness of retained buyer records remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Historical payments and completeness of retained buyer records remain unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenAI abuse-monitoring retention exceptions

Question: Is OpenAI abuse-monitoring retention an unconditional maximum that applies despite all safety and legal exceptions?

The data guide describes ordinary abuse-log retention of up to 30 days, with longer retention for legal requirements or protection from harm. It also describes retaining suspected CSAM image material for manual review even under approved Zero Data Retention or Modified Abuse Monitoring. These exceptions differ from ordinary application-state retention.

Source: Data controls in the OpenAI platform. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Is OpenAI abuse-monitoring retention an unconditional maximum that applies despite all safety and legal exceptions?

Buyer evidence still required

  • Approved organization and project data controls
  • Input types and applicable exception provisions
  • Required retention assurance and supporting contractual evidence

Review inference: Record approved controls and documented exceptions separately rather than turn the ordinary period into an absolute erasure guarantee.

Suggested review condition: Reject an unconditional maximum-retention claim that omits the documented exceptions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether an exception applies to any particular submitted content is unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Make retention commitments that account for the provider’s stated exception boundaries.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A guaranteed deletion deadline for all safety-review material
  • Whether an exception applies to any particular submitted content is unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI Agents SDK: Application ownership

Question: What remains the application's responsibility when using an agent SDK?

OpenAI describes its Agents SDK as running inside the application: the application owns deployment, tool implementations, state storage and approval decisions, while the SDK runs the agent loop and invokes tools. Treat hosting, persistence and authorisation as explicit application responsibilities. Installing the SDK alone does not establish a deployed service, durable storage or approved tool access.

Source: OpenAI Agents SDK: Build with the SDK. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • managed hosting supplied by an SDK installation
  • durable application storage without configuration
  • tool authorisation or operational readiness established by a package choice

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI Agents SDK: Resuming an approved tool call

Question: How should an application continue an agent run after a tool call waits for approval?

The Agents SDK records an approval interruption before the tool executes and returns resumable state. The application resolves the pending approval or rejection, then resumes that state; delayed review can use a stored serialised state. Starting a new user turn is not the documented continuation path. Approval still needs an authorised decision; this reference does not establish idempotent external side effects.

Source: OpenAI Agents SDK: Approval lifecycle. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • approval authority inferred from a model request
  • automatic storage or reviewer identity verification
  • exactly-once external side effects or automatic rollback

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI Agents SDK: Trace capture and configuration

Question: What should I check before assuming an agent run has a usable trace?

OpenAI documents tracing enabled by default for the normal server-side Agents SDK path, with model calls, tool calls and outputs, handoffs, guardrails and custom spans. SDK and per-run controls can change capture. Check the actual runtime, configuration and received trace before relying on it. This source does not establish browser or test-runtime defaults, complete capture, retention compliance or correct agent decisions.

Source: OpenAI Agents SDK: Integrations and observability. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • identical defaults in every runtime
  • complete trace capture or delivery
  • retention compliance from a default setting
  • correct decisions inferred from a trace

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI Agents SDK: Where guardrails apply

Question: Where should validation run when an agent hands work to another agent or calls a tool?

OpenAI documents input guardrails on the first agent, output guardrails on the final-output agent, and tool guardrails on the function tools to which they are attached. Review validation at each side-effecting tool boundary; entry and exit checks alone do not cover every intermediate action. This documents control placement, not tested enforcement or protection for every tool type.

Source: OpenAI Agents SDK: Guardrails and human review. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • automatic validation of every intermediate action
  • uniform guardrail coverage across all tool types
  • tested enforcement in a buyer deployment

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI Agents token subsets and double counting

Question: Should reasoning and cached tokens be added to OpenAI Agents input and output totals?

OpenAI documents cached tokens as a subset of input_tokens and reasoning tokens as a subset of output_tokens in Agents usage. Adding those detailed categories again to the parent counts double-counts recorded tokens. Preserve the subsets for applicable pricing analysis while keeping the totals and component categories distinct.

Source: OpenAI Agents API: Observability and usage. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Should reasoning and cached tokens be added to OpenAI Agents input and output totals?

Buyer evidence still required

  • Usage object with parent and detail counts
  • Model and accounting scope
  • Applicable pricing and billing evidence

Review inference: Review openai agents token subsets and double counting before accepting the buyer claim. Parent/subset arithmetic, including reasoning output, is distinct from deciding cached versus uncached rates. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Token arithmetic alone does not establish the final charge, complete task cost or applicable model rates.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Understand token usage

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Token arithmetic alone does not establish the final charge, complete task cost or applicable model rates.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenAI Agents usage and provisional accounting

Question: Does null or unchanged OpenAI Agents session usage prove that no cost was incurred?

OpenAI describes Agents API session and turn usage as best-effort: it can be null when unknown and recorded values may change as accounting arrives. These counts are not a final bill. Treat missing usage as unestablished, retain observation times and reconcile later accounting before concluding zero consumption or final cost.

Source: OpenAI Agents API: Observability and usage. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Does null or unchanged OpenAI Agents session usage prove that no cost was incurred?

Buyer evidence still required

  • Session and turn identifiers
  • Timestamped usage observations
  • Later accounting and applicable billing evidence

Review inference: Review openai agents usage and provisional accounting before accepting the buyer claim. Unknown and revisable session accounting is distinct from model-specific token-rate interpretation. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: No zero-cost, finalized-invoice or complete usage conclusion from an absent or provisional usage field.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Understand token usage

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No zero-cost, finalized-invoice or complete usage conclusion from an absent or provisional usage field.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenAI Batch: Reconcile successful and failed request results

Question: Does a completed OpenAI Batch output file establish success for every submitted request?

OpenAI Batch writes successful requests to the output file and failed-request information to a separate error file. Output order need not match input order; custom_id links each result to its request. A completed batch or downloaded success file alone does not account for every submitted item.

Source: Batch API. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a completed OpenAI Batch output file establish success for every submitted request?

Buyer evidence still required

  • Original request inventory and unique custom_id values
  • Batch status, output_file_id and error_file_id
  • Per-request results reconciled to intended downstream work

Review inference: Completion evidence is a request-level reconciliation, not a file-level success flag.

Suggested review condition: Refuse all-items-success findings while error output or unmatched request identifiers remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual request success and downstream effects are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid repeating successful work or losing failed items in bulk agent processing.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Success of every item or execution of external actions from batch completion
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI cached-token cost interpretation

Question: Can an agent estimate OpenAI prompt cost by charging every input token at one uncached rate?

OpenAI’s current prompt-caching guide distinguishes uncached input, cached input and cache-write rates, with model-specific pricing. Cache-write pricing is not an additive fee in that guide. Cached-token usage and the applicable model’s rate categories therefore matter when reconciling a request.

Source: Prompt caching | OpenAI API . Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent estimate OpenAI prompt cost by charging every input token at one uncached rate?

Buyer evidence still required

  • Actual model and request date
  • Input, cached and cache-write usage where applicable
  • Applicable pricing schedule and billing adjustments

Review inference: Apply the captured model/version pricing categories to actual usage rather than infer cost from total input tokens alone.

Suggested review condition: Decline exact cost claims without usage-category and rate evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s model-specific rates, discounts and billed result are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid incorrect cost attribution for repeated agent context.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A fixed price, guaranteed cache hit or final invoice calculation
  • The buyer’s model-specific rates, discounts and billed result are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI Conversations: Deleting a conversation does not delete its items

Question: Does deleting an OpenAI Conversations API conversation also delete its items?

The Conversations API delete reference states that deleting a conversation does not delete the items in it. The returned conversation.deleted object identifies the conversation-level deletion. That response alone cannot establish item removal or an application's complete data-exit outcome.

Source: Delete a conversation. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting an OpenAI Conversations API conversation also delete its items?

Buyer evidence still required

  • API family, conversation identifier and deletion response
  • Inventory and lifecycle evidence for associated items
  • Other retained objects and the buyer's declared exit boundary

Review inference: An exit assessment needs item-level evidence in addition to the conversation response.

Suggested review condition: Refuse an items-deleted claim supported only by conversation.deleted.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer item lifecycle, retained copies and eventual erasure outcomes are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a conversation-level deletion receipt from being mistaken for complete content removal.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Physical erasure, retention duration, recoverability or deletion of other Responses, files and backups
  • Equivalence with ChatGPT UI deletion or the Realtime API
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI file expiry and completed batch residue

Question: Does completing an OpenAI batch establish that its uploaded files and application state have been deleted?

The upload reference makes file lifetime depend on purpose and expiration settings: batch-purpose uploads expire after 30 days by default, while other uploaded files persist until manually deleted unless an expiration policy applies. The data guide separately lists batch application state as retained until deletion. A completed job is not a file-deletion receipt.

Source: Create upload | OpenAI API Reference. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does completing an OpenAI batch establish that its uploaded files and application state have been deleted?

Buyer evidence still required

  • Batch ID and associated input, output and error file IDs
  • Each file purpose, expires_at value and deletion response
  • Required retention boundary and post-operation inventory

Review inference: Inventory batch input, output and error file identities separately from job completion, and inspect each actual expiry or deletion outcome.

Suggested review condition: Do not accept job completion as complete cleanup when any associated file or application-state outcome is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual file retention settings and residual customer copies have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Reconcile retained batch artifacts before declaring an AI processing task closed.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic erasure of every batch artifact on completion
  • Actual file retention settings and residual customer copies have not been inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI function calling: A requested action needs an execution result

Question: Does a model-generated OpenAI function call prove that the external action happened?

OpenAI's function-calling workflow returns a tool call to the application, which executes its code and supplies the tool output in a subsequent request. The model can then produce a final response or further calls. The documented application-executed function flow separates the model's requested operation from the application-supplied result.

Source: Function calling | OpenAI API . Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a model-generated OpenAI function call prove that the external action happened?

Buyer evidence still required

  • Function name, validated arguments and tool-call identifier.
  • Application execution record and authoritative external-system result.
  • Linked tool output, failures and any subsequent model response.

Review inference: Neither generated arguments nor a narrative reply establish external state without execution evidence.

Suggested review condition: Refuse a completed-action claim when only model output or an unbound tool result is supplied.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Application implementation, result authenticity and external side effects are unobserved.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck API flow and tool type; hosted built-in tools are outside this custom-function review.

Optional saved evidence: Bind an action request to the outcome evidence needed for a business decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Observed execution, authentic external results or coverage of hosted built-in tool execution
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI regional storage versus processing scope

Question: Does an OpenAI regional-storage configuration establish that all processing stays in that region?

OpenAI distinguishes regional storage from regional processing. If a selected region does not support regional processing, customer content may be processed and temporarily stored elsewhere. Residency also excludes system data and third-party services. Applicable endpoints, models, snapshots and regional capabilities must be checked together.

Source: Data controls in the OpenAI platform. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an OpenAI regional-storage configuration establish that all processing stays in that region?

Buyer evidence still required

  • Project geography and request endpoint
  • Supported model, snapshot and regional-processing configuration
  • Required customer-content, system-data and third-party scope

Review inference: Treat storage location and inference-processing location as separate acceptance criteria.

Suggested review condition: Decline a region-contained processing claim when only at-rest storage geography is evidenced.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual request routing and downstream processor locations are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid approving a deployment whose processing geography exceeds its agreed custody scope.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal regional containment from a regional hostname
  • Actual request routing and downstream processor locations are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI remote-tool data retention boundary

Question: Do OpenAI organization retention controls automatically govern data sent to a remote MCP service?

OpenAI identifies remote MCP servers as third-party services whose own retention policies apply to data sent to them. Network transfers to other third-party services likewise follow those services’ retention policies. OpenAI account controls therefore do not describe the complete downstream retention boundary.

Source: Data controls in the OpenAI platform. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Do OpenAI organization retention controls automatically govern data sent to a remote MCP service?

Buyer evidence still required

  • Remote server identity and retention terms
  • Tool arguments and returned data categories shared downstream
  • Deletion and offboarding evidence from each destination

Review inference: Review the destination service and the data disclosed to it as a separate custody relationship.

Suggested review condition: Do not approve end-to-end zero retention based only on the OpenAI project configuration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The remote service’s actual storage and deletion behavior is not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify retained copies beyond the model provider before completing agent offboarding.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Inheritance of OpenAI controls by third-party tools
  • The remote service’s actual storage and deletion behavior is not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI Responses MCP: Imported tools and sharing approval

Question: Does allowing a remote MCP tool in OpenAI Responses also approve sending it data?

OpenAI Responses uses allowed_tools to limit imported MCP tools and a separate require_approval setting for tool-call approval. By default it requests approval before sharing data with a connector or remote MCP server. An approval request exposes the tool and arguments for review; disabling approvals changes that sharing gate, not the remote service permissions.

Source: MCP servers. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does allowing a remote MCP tool in OpenAI Responses also approve sending it data?

Buyer evidence still required

  • Responses MCP configuration and server identity
  • Requested tool arguments and approval response
  • Remote credential scope and permitted data recipients

Review inference: Tool selection, data-sharing consent and upstream authority require separate evidence.

Suggested review condition: Refuse an approved-sharing finding without the applicable approval policy and call-specific authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Remote server behavior, actual data handling and effective permissions are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Review agent data egress before permitting a remote tool call.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Remote permission enforcement, safe arguments or server trust from an allowlist
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI Responses: Storage settings and feature-specific retention

Question: What OpenAI response state can persist after a call when storage or retention settings change?

OpenAI's data guide describes Responses application-state retention by default or with store=true, stating that response data is retained for at least 30 days in those cases. Zero Data Retention treats store as false, but endpoint and feature exceptions remain. Background mode uses temporary storage for polling, and Modified Abuse Monitoring has additional rules for omitted versus explicit store settings.

Source: Data controls in the OpenAI platform . Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: What OpenAI response state can persist after a call when storage or retention settings change?

Buyer evidence still required

  • Endpoint, model, foreground/background mode and exact store parameter.
  • Organization/project retention entitlement and applicable feature exceptions.
  • Separate logs, conversation/file resources and external recipient inventories.

Review inference: A storage flag is not a blanket erasure statement for every feature, log or separately stored resource.

Suggested review condition: Refuse universal zero-retention or exact-deletion-date claims from store=false alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer's retention agreement and deletion outcomes are unknown; the source does not promise exact deletion at day 30.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck data-controls matrix and background-mode rules after endpoint, feature or entitlement changes.

Optional saved evidence: Identify residual resources before closing a data-retention or exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified deletion, exact day-30 erasure or coverage of unrelated stateful resources
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI service accounts: Roles, key scopes and propagation

Question: What establishes an OpenAI project service-account key's effective authority after a role or scope change?

OpenAI documents project-owned service accounts, group-assigned project roles and separately issued scoped API keys. Key scopes can narrow the account's assigned project permissions but cannot grant permissions outside that role. The Terraform creation flow can create an identity with no default role or key. The RBAC guide allows up to 30 minutes for role changes and group sync to propagate.

Source: Manage service accounts with Terraform | OpenAI API . Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: What establishes an OpenAI project service-account key's effective authority after a role or scope change?

Buyer evidence still required

  • Project and service-account IDs, key scopes and assigned direct or group roles.
  • Change timestamps and authorization outcomes after propagation.
  • Actual key expiry or revocation state and all replacement credentials.

Review inference: An intended role change or local expiry schedule is insufficient evidence that a particular key has ceased working.

Suggested review condition: Refuse instantaneous loss-of-access or automatic-expiry claims without evidence for the actual key and current grants.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

These guides do not establish a universal service-account key expiry guarantee; actual key state and effective access are unknown.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck API-key lifecycle documentation, group assignments, scope mappings and propagation guidance.

Optional saved evidence: Establish current credential scope before accepting access removal or delegation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic key-expiry guarantees, immediate revocation or tested buyer permissions
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI vector stores: Removing membership does not delete the file

Question: Does deleting a file from an OpenAI vector store also delete the underlying uploaded file?

The OpenAI vector-store file deletion reference explicitly distinguishes removal from the vector store from deletion of the underlying file. Its DELETE operation removes the vector-store file association; deleting the uploaded file requires the separate file deletion endpoint. The response identifies a vector_store.file.deleted result.

Source: Delete vector store file | OpenAI API Reference. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a file from an OpenAI vector store also delete the underlying uploaded file?

Buyer evidence still required

  • Vector-store ID, uploaded file ID and all known associations.
  • Separate association-removal and uploaded-file deletion responses.
  • Other stores, exported copies and applicable retention conditions.

Review inference: A membership-deletion receipt cannot close a wider file-erasure claim without other resource evidence.

Suggested review condition: Refuse complete-file-deletion conclusions based only on vector_store.file.deleted.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual file deletion, other associations and downstream copies were not inspected.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck exact vector-store and Files API behavior after API or resource changes.

Optional saved evidence: Identify residual resources before closing a data-retention or exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Physical erasure attestation or deletion from every copy and recipient
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenAI: Alerts, hard spend limits and request rates

Question: Do OpenAI spending alerts and rate limits prevent an agent from incurring further API costs?

OpenAI distinguishes spend alerts, which leave traffic running, from configured organization or project hard spend limits, which reject affected requests with a 429 error. Enforcement can lag and recorded spend can exceed the amount slightly. Rate limits constrain request or token throughput; they are separate from monthly spend controls and approved usage limits.

Source: Spend limits | OpenAI API . Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Do OpenAI spending alerts and rate limits prevent an agent from incurring further API costs?

Buyer evidence still required

  • Organization and project IDs, active spend-control type and configured amounts.
  • Actual limit error codes, time-stamped usage and propagation evidence.
  • Agent task approval, permitted models and other credentials or billing paths.

Review inference: A budget control does not establish approval for each charge or prevent spending through an unrelated account.

Suggested review condition: Refuse an exact no-further-spend claim based only on an alert, a rate limit or a newly changed cap.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer's enabled limits, propagation timing and outstanding billable usage are unobserved.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck control type, project scope, error semantics and enforcement-delay guidance after a limit or billing change.

Optional saved evidence: Reconcile spending authority or transaction state before approving financial reliance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exact zero overshoot, transaction authorization or cessation through every credential
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenFGA authorization cache freshness

Question: Can a successful OpenFGA tuple update be followed by a stale Check response?

The pinned consistency guide says MINIMIZE_LATENCY can use cached results, so an immediate check may omit a recent tuple change when caching is enabled. HIGHER_CONSISTENCY bypasses the cache and queries the database. Caching is documented as disabled by default. The actual configuration and request mode matter; a write receipt alone does not establish a fresh authorization decision.

Source: Query Consistency Modes. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a successful OpenFGA tuple update be followed by a stale Check response?

Buyer evidence still required

  • Tuple write time and check consistency mode
  • Cache configuration and application decision time
  • Application enforcement point and downstream access observations

Review inference: Decide whether a grant or revocation has been reflected in the check used for an action. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not infer immediate effective revocation from a write receipt and a potentially cached check.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Cache deployment and downstream enforcement are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Cache deployment and downstream enforcement are unobserved.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA authorization model selection

Question: Can an OpenFGA authorization check change when the request omits authorization_model_id?

OpenFGA models are immutable, but a write creates a new model version. The pinned documentation says requests without authorization_model_id use the store’s latest model. Passing the ID binds evaluation and validation to that version. Immutability therefore does not guarantee stable authorization when applications implicitly select whichever model was created last.

Source: Immutable Authorization Models. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an OpenFGA authorization check change when the request omits authorization_model_id?

Buyer evidence still required

  • Store and authorization model IDs
  • Request parameters and rollout configuration
  • Model rollout and decision-log correlation

Review inference: Identify the policy version that governed a permission decision. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not describe an unpinned latest-model check as a reproducible evaluation of a fixed policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The active store, model and request history have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The active store, model and request history have not been inspected.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA change log and decision reconstruction

Question: Can OpenFGA Read Changes alone reconstruct decisions that used contextual tuples?

OpenFGA contextual tuples exist only for a request and are not stored. Read Changes reports stored tuple writes and deletes, and the token-claims guide warns that permission-aware indexes built from it may not account for contextual tuples. A complete reconstruction needs the request-local inputs as well as the stored changes; the change stream is not an execution trace.

Source: Contextual Tuples. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can OpenFGA Read Changes alone reconstruct decisions that used contextual tuples?

Buyer evidence still required

  • Read Changes export and cursor coverage
  • Decision requests containing contextual tuples
  • Authorization model version and input-retention policy

Review inference: Recognize missing request-local authority in an exported relationship history. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not claim complete decision reconstruction from stored relationship changes alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Request logs, omitted context and actual tool execution are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Request logs, omitted context and actual tool execution are unknown.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA change-stream resumption

Question: Does reaching the current end of OpenFGA Read Changes make its continuation token disposable?

The pinned Read Changes guide says to persist continuation tokens across errors and restarts. At the current end, the API returns the same token, which should be saved for later polling. A token produced by an object-type filter must be reused with that type. Losing the cursor or its filter context can undermine a claimed continuous audit export.

Source: How to get tuple changes. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does reaching the current end of OpenFGA Read Changes make its continuation token disposable?

Buyer evidence still required

  • Saved cursor, filter and page sequence
  • Export timestamps and restart evidence
  • Export pagination limits and any recorded retrieval errors

Review inference: Preserve a resumable, correctly scoped relationship-change history. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not label a filtered or restarted export complete without cursor and scope continuity.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer export coverage and retention are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer export coverage and retention are not observed.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA condition context merge

Question: Can request context replace a condition parameter already stored in an OpenFGA relationship tuple?

The pinned conditions guide specifies a merge of persisted tuple context and request context for condition evaluation. Persisted values take precedence when both provide the same parameter. A request that sends a different grant duration does not, by that act alone, replace the stored duration. Reconstruction requires both inputs and their documented precedence.

Source: Conditions. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can request context replace a condition parameter already stored in an OpenFGA relationship tuple?

Buyer evidence still required

  • Persisted tuple condition context
  • Conflicting request context and model condition
  • Actual evaluated condition result and request correlation

Review inference: Determine which condition values actually governed an authorization check. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not report the request value as effective without checking persisted context precedence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual stored and request values have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual stored and request values have not been inspected.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA contextual Expand documentation conflict

Question: Do the pinned OpenFGA guides agree that Expand accepts contextual tuples?

At the pinned documentation revision, the contextual-tuples guide lists Expand among supported query methods, while the token-claims guide says contextual tuples are not supported on Expand. These statements conflict. The reviewed documentation alone cannot settle support for a buyer version; inspect that version’s API contract and validate the intended request before relying on an Expand result.

Source: Contextual Tuples. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Do the pinned OpenFGA guides agree that Expand accepts contextual tuples?

Buyer evidence still required

  • Exact server and API versions
  • Version-specific schema and controlled request result
  • Captured contradictory documentation and implementation conformance evidence

Review inference: Avoid assuming contextual authority is reflected in an Expand result when the guides disagree. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not select the favourable documentation statement and claim version-specific Expand support.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Which statement matches the buyer deployment is unresolved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Which statement matches the buyer deployment is unresolved.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA model and tuple migration

Question: Does publishing a renamed relation in OpenFGA migrate existing relationship tuples automatically?

The pinned immutable-model guide describes relation renaming as a coordinated migration: create the new model, update application relation names, copy existing tuples to the new relation and deploy against the new model ID. Creating an immutable model version alone is not the tuple or application migration. Rollout evidence must connect all three states.

Source: Immutable Authorization Models. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does publishing a renamed relation in OpenFGA migrate existing relationship tuples automatically?

Buyer evidence still required

  • Old and new models with relation names
  • Tuple migration result and deployed application model ID
  • Post-migration checks comparing expected and effective access

Review inference: Avoid losing or unintentionally changing access during a relation rename. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not mark a relation migration complete solely because a new model was written.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Tuple completeness and application rollout are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Tuple completeness and application rollout are not observed.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA request-local relationship overrides

Question: Can a contextual tuple override the same stored relationship in an OpenFGA request?

The pinned contextual-tuples guide says request-local tuples participate in evaluation as stored tuples would, but are not persisted and affect only that request. When user, relation and object match a stored tuple, the contextual tuple takes precedence. Reviewing the database alone therefore does not reconstruct the relationships used by that specific decision.

Source: Contextual Tuples. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a contextual tuple override the same stored relationship in an OpenFGA request?

Buyer evidence still required

  • Stored relationship and matching contextual tuple
  • Exact authorization request and model ID
  • Authority and validation of the caller supplying contextual tuples

Review inference: Capture request-local authority inputs before explaining a permission result. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not reconstruct a decision from stored tuples while omitting request-local overrides.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual contextual inputs and caller authority to supply them are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The actual contextual inputs and caller authority to supply them are unknown.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA temporal condition inputs

Question: Does an OpenFGA temporal grant independently establish the current time used for authorization?

The pinned conditions guide models access using current_time, grant_time and grant_duration, and its query examples supply current_time in request context. The documented expression evaluates those inputs; it is not evidence of how the caller obtained or protected the clock value. A buyer must establish the provenance and freshness of time supplied for the decision.

Source: Conditions. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does an OpenFGA temporal grant independently establish the current time used for authorization?

Buyer evidence still required

  • Condition expression and persisted grant context
  • Request time value and its trusted source
  • Clock tolerance and source authentication policy

Review inference: Check the trustworthiness of time inputs before relying on a temporary permission. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not treat a caller-supplied time value as independent clock attestation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The caller clock, input validation and real decision time are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The caller clock, input validation and real decision time are unobserved.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenFGA token-derived residual membership

Question: Does removing a directory group immediately remove OpenFGA access based on an unexpired token claim?

The pinned OpenFGA token-claims guide warns that relationships supplied from token claims can continue granting access until the token expires even if the underlying directory relationship changes. Contextual tuples avoid persistent synchronization but do not make the token’s claim live directory evidence. Offboarding must account for that residual acceptance window and the deployed token-handling policy.

Source: Use Token Claims As Contextual Tuples. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does removing a directory group immediately remove OpenFGA access based on an unexpired token claim?

Buyer evidence still required

  • Membership-change time and token expiry
  • Token validation and contextual-tuple construction
  • Offboarding policy for active sessions and outstanding tokens

Review inference: Identify residual authority when directory membership and token-derived relationships diverge. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not treat directory removal as proof all token-derived FGA relationships have ceased.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual token invalidation, sessions and downstream access are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual token invalidation, sessions and downstream access are unobserved.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

OpenID CAEP: Access response boundary

Question: Does receiving a CAEP event prove that access changed?

OpenID describes CAEP event types that let receivers adjust access in response to changing conditions. Receiving an event and applying an access decision are separate steps; evidence of the receiver's policy and resulting action is needed to claim enforcement.

Source: OpenID Shared Signals specifications. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • automatic access revocation in every receiver
  • correct policy configuration
  • observed enforcement from a specification alone

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenID CAEP: Declared event coverage

Question: Does the CAEP interoperability profile mean every event use case is implemented?

The reviewed draft CAEP profile describes use cases involving session, credential and device-compliance changes. Implementations can support selected use cases; a profile reference alone does not show which events a sender emits, a receiver accepts or an application acts on.

Source: CAEP Interoperability Profile 1.0 - draft 01. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • support for every event type
  • confirmed signal delivery
  • correct receiver action

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenID CAEP: Draft interoperability profile

Question: Is the reviewed CAEP interoperability profile a final deployment assurance?

The reviewed CAEP Interoperability Profile 1.0 is labelled draft 01. It profiles Shared Signals, CAEP and OAuth requirements for interoperable implementations; draft guidance does not establish final standard status or a conforming, securely configured deployment.

Source: CAEP Interoperability Profile 1.0 - draft 01. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • final status of this profile
  • tested deployment conformance
  • effective access enforcement

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenID RISC: Risk signal boundary

Question: Does a RISC risk event establish that remediation occurred?

OpenID lists RISC as a specification for exchanging risk-related events using Shared Signals. A risk notification supplies information to another system; it does not by itself establish an accurate local risk decision, account recovery or completed remediation.

Source: OpenID Shared Signals specifications. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • completed remediation
  • correct local risk decision
  • automatic account recovery

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenID Shared Signals: Framework scope

Question: What does the OpenID Shared Signals Framework establish?

OpenID's Shared Signals specifications describe a framework for exchanging security events between systems. The framework enables communication; a specification reference does not prove an integration is configured, signals arrive or a receiver enforces the intended policy.

Source: OpenID Shared Signals specifications. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • configured integration
  • reliable event delivery
  • enforced recipient policy

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenSearch: Manual snapshots have separate custody

Question: Can an OpenSearch exit inventory omit manual snapshots because automated recovery has a retention window?

OpenSearch distinguishes automated snapshots in a service-managed bucket from manual snapshots in the customer S3 bucket. Manual snapshots have a separate deletion operation and storage charges. Automated retention does not define the lifetime of every customer-held snapshot.

Source: Creating index snapshots in Amazon OpenSearch Service - Amazon OpenSearch Service. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can an OpenSearch exit inventory omit manual snapshots because automated recovery has a retention window?

Buyer evidence still required

  • Automated and manual repository inventory.
  • Snapshot identifiers and customer S3 ownership.
  • Retention rules and deletion outcome references.

Suggested review condition: Do not close residual-data review from automated retention alone while manual snapshots remain unaccounted for.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Automated and manual repository inventory. Snapshot identifiers and customer S3 ownership. Retention rules and deletion outcome references.

Optional saved evidence: Include customer snapshot repositories in an AI search-service exit review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual snapshot deletion, discovery of unknown copies or successful offboarding
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenSSF Scorecard: Project practice evidence

Question: Does an OpenSSF Scorecard result guarantee that a dependency is safe?

OpenSSF Scorecard uses automated checks to assess project security practices. A result is evidence about those checks, not a guarantee that an artifact is safe or suitable for a buyer.

Source: OpenSSF Scorecard. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • absence of vulnerabilities
  • safe dependency certification
  • all security properties tested

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry baggage and untrusted authority claims

Question: Can OpenTelemetry baggage be trusted as authenticated user identity or agent spending authority?

OpenTelemetry baggage carries contextual key-value data that can propagate to downstream services and unintended third parties. Its documentation states that there are no built-in integrity checks proving that baggage items originated with the reader's system. Baggage is also separate from span, metric and log attributes unless explicitly copied into them.

Source: Baggage | OpenTelemetry. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can OpenTelemetry baggage be trusted as authenticated user identity or agent spending authority?

Buyer evidence still required

  • Baggage origin and propagation path
  • Independent identity and action-authorisation evidence
  • Rules for copying baggage into retained telemetry and filtering outbound fields

Review inference: Treat identity or spending fields in baggage as untrusted context until independently authenticated and authorised.

Suggested review condition: Do not approve a tool call or payment solely from an identity, role or budget value supplied in baggage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The caller, tampering resistance of the surrounding system and actual propagation boundaries were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent propagated observability context from being mistaken for verified tool or payment authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authenticated identity, tamper-proof provenance or permission to spend
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry Collector: Retries do not guarantee delivery

Question: Does an enabled Collector sending queue guarantee that telemetry eventually reaches the backend?

OpenTelemetry documents loss when a sending queue fills or its retry window expires. Persistent storage helps across restarts but has its own failure conditions. Queueing and retries improve resilience without establishing loss-free delivery.

Source: OpenTelemetry: Collector resiliency. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does an enabled Collector sending queue guarantee that telemetry eventually reaches the backend?

Buyer evidence still required

  • Queue capacity, retry policy and persistent-storage settings.
  • Queue and failure observations during the outage.
  • Backend receipts reconciled against source counts.

Suggested review condition: Preserve an explicit delivery gap unless source, queue and destination evidence account for it.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Exporter queue, retry duration, storage configuration and outage window.

Optional saved evidence: Does an enabled Collector sending queue guarantee that telemetry eventually reaches the backend?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry ForceFlush timeout and outcome

Question: Does calling OpenTelemetry ForceFlush guarantee that pending spans were exported before shutdown?

The OpenTelemetry Trace SDK specifies ForceFlush across registered SpanProcessors. It should indicate success, failure or timeout and complete or abort within a timeout. Calling it without checking the result therefore does not establish successful export. OTLP acknowledgement also remains a single-hop acceptance boundary rather than proof of final backend retention.

Source: Tracing SDK | OpenTelemetry. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does calling OpenTelemetry ForceFlush guarantee that pending spans were exported before shutdown?

Buyer evidence still required

  • SDK and processor configuration with flush timeout
  • Observed ForceFlush outcome and process shutdown sequence
  • Destination evidence for the expected spans

Review inference: Record flush outcome and shutdown timing, then reconcile the required spans at the destination before relying on complete evidence.

Suggested review condition: Do not mark the evidence chain complete when flushing timed out or its result was not observed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Processor completion, spans discarded during termination and downstream retention remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Check shutdown evidence rather than silently treating a flush request as successful delivery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed flush on process termination or complete downstream retention
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry logs: Event time and observation time differ

Question: Can an OpenTelemetry log observation timestamp be treated as the time the agent action occurred?

OpenTelemetry distinguishes Timestamp, measured at the event source, from ObservedTimestamp, measured when the collection system observes it. The source timestamp can be absent. Collection delay and clock provenance therefore matter when reconstructing an action sequence from logs.

Source: OpenTelemetry: Logs data model. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an OpenTelemetry log observation timestamp be treated as the time the agent action occurred?

Buyer evidence still required

  • Original timestamp fields and units.
  • Source and collector clock context.
  • Correlation evidence for the action sequence.

Suggested review condition: Label the timestamp basis explicitly and avoid treating collection order as proven causality.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Available timestamp fields, source clock and collection path.

Optional saved evidence: Can an OpenTelemetry log observation timestamp be treated as the time the agent action occurred?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry OK status and evidence precedence

Question: Does an OpenTelemetry span with status OK independently prove an external action succeeded?

The OpenTelemetry Trace API defines OK as application developer or operator validation that the operation completed successfully. Its status ordering is OK above Error above Unset: setting OK can override a prior Error, and subsequent Error or Unset updates are ignored. The span status is an application assertion with precedence rules, not independent verification of an external outcome.

Source: Tracing API | OpenTelemetry. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an OpenTelemetry span with status OK independently prove an external action succeeded?

Buyer evidence still required

  • Instrumentation and operator rules that set span status
  • Relevant error events and status changes where available
  • Provider-side outcome evidence linked to the span

Review inference: An audit should retain action-specific evidence and relevant errors rather than relying on the final status field alone.

Suggested review condition: Do not certify success or infer absence of earlier errors from a final OK status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The reason OK was set, the correctness of instrumentation and the external outcome are not established by the standard.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid overstating successful agent actions when telemetry status can suppress error signals.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Independent success verification or recovery of overwritten status history
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry redaction: Exceptions and attribute scope

Question: Does configuring the OpenTelemetry redaction processor prove every sensitive attribute is masked?

The processor supports key and value policies with explicit exceptions. Ignored keys pass without redaction; allowed values are not masked. Enabling allow_all_keys disables the key allowlist but still applies blocked-value rules. Review the effective exceptions and processed attributes before treating the processor name as evidence of complete removal.

Source: OpenTelemetry: Redaction processor. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Installing a redaction processor establishes complete sensitive-data removal.

Buyer evidence still required

  • Collector revision and active processor configuration.
  • Allowed, ignored and blocked keys or values.
  • Representative output and all downstream paths.

Suggested review condition: Require evidence for exception paths and output scope before approving sensitive telemetry export.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Collector version, processor configuration, attribute scope, exceptions and downstream destinations.

Optional saved evidence: Save the specific policy exceptions behind a telemetry-disclosure decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry service name and instance identity

Question: Does OpenTelemetry service.name uniquely identify the production instance that performed an action?

OpenTelemetry defines service.name as the logical service name. service.instance.id distinguishes instances of the same service, and the combination of service.namespace, service.name and service.instance.id must be globally unique. A shared service.name alone cannot distinguish replicas or environments, and these declared attributes do not authenticate the emitting workload.

Source: Service | OpenTelemetry. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does OpenTelemetry service.name uniquely identify the production instance that performed an action?

Buyer evidence still required

  • Resource attributes including service name, namespace and instance ID
  • Deployment and environment mapping for those attributes
  • Evidence linking the emitting workload to the action

Review inference: Use a suitable instance and environment binding when joining action evidence, then verify its provenance separately.

Suggested review condition: Do not attribute an action to a unique production instance using only service.name.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Attribute correctness, uniqueness in the buyer environment and the actual originating workload remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid joining audit events to the wrong replica or environment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authenticated workload identity or unique production attribution from a logical service name
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry: Naming conventions

Question: What do OpenTelemetry semantic conventions contribute to agent observability?

OpenTelemetry semantic conventions standardise names for operations and telemetry data. Consistent naming does not establish that a deployment captures complete or accurate evidence.

Source: OpenTelemetry Semantic Conventions. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • complete observability from naming alone
  • correctness of captured telemetry
  • proof that an agent action was authorised

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry: Sampling limits action reconstruction

Question: Does a missing OpenTelemetry trace prove that an agent action never happened?

OpenTelemetry distinguishes sampled spans exported for observation from data not selected for export. Head sampling cannot ensure that every later error is retained; downstream tail sampling only evaluates data available to it. Trace absence therefore requires review of the sampling pipeline before an action-absence conclusion.

Source: OpenTelemetry sampling. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a missing OpenTelemetry trace prove that an agent action never happened?

Buyer evidence still required

  • The SDK and collector sampling configuration.
  • The relevant time interval and routing path.
  • Independent action records and known export gaps.

Suggested review condition: Do not infer no action from missing traces when sampling or export coverage is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The SDK and collector sampling configuration. The relevant time interval and routing path. Independent action records and known export gaps.

Optional saved evidence: An investigation owner must establish observability coverage before using missing traces to deny an action occurred.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof that a particular missing trace was sampled out or that every exported trace is complete
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry: Sampling limits trace coverage

Question: Can sampled traces establish a complete history of agent actions?

OpenTelemetry sampling selects traces or spans for processing and export. Head and tail sampling make decisions at different points, and can be combined. A retained sample is not an exhaustive record of all actions or requests.

Source: OpenTelemetry: Sampling. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can sampled traces establish a complete history of agent actions?

Buyer evidence still required

  • Head and tail sampling configuration.
  • Service coverage and propagation settings.
  • Independent action counts or unsampled evidence where required.

Suggested review condition: Label sampled evidence and avoid treating a missing trace as proof an action did not happen.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. SDK and Collector sampling policies, affected services and observation window.

Optional saved evidence: Can sampled traces establish a complete history of agent actions?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OpenTelemetry: Telemetry shape across upgrades

Question: Can I assume telemetry names and attributes stay unchanged after an instrumentation upgrade?

The OpenTelemetry Telemetry Stability page, currently marked Development, distinguishes unstable from stable instrumentation. Unstable producers offer no telemetry-shape guarantees; additive telemetry is allowed for both classes. The page also retains a moratorium on relying on schema transformations for stability. Check the producer label, version and emitted fields before updating dashboards or alert rules; a Schema URL alone does not demonstrate compatibility.

Source: OpenTelemetry: Telemetry Stability. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • unchanged telemetry across arbitrary upgrades
  • automatic schema conversion support
  • working dashboards or alert rules without validation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Oracle SQLcl MCP: Command restrictions are separate from database grants

Question: Does SQLcl MCP restrict level 4 prove that an Oracle connection is read-only?

SQLcl 26.3 documents level 4 as the MCP default, restricting host commands and scripts. Its database tools still execute SQL and PL/SQL under the connected identity. A command restriction is not evidence that database privileges exclude changes; saved connection selection and grants need separate review.

Source: Oracle SQLcl 26.3 MCP tools. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Version 26.3 documented tools and restrict levels

Oracle SQLcl 26.3 documentation; installed version not inspected. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Oracle publishes SQLcl; the buyer runs the local process.

Documented by publisher. Oracle SQLcl 26.3 MCP tools; Oracle SQLcl 26.3 MCP restrict levels

Purpose

Connect to Oracle and execute supported database tools.

Documented by publisher. Oracle SQLcl 26.3 MCP tools; Oracle SQLcl 26.3 MCP restrict levels

Read capability

Saved connection names, schema details and query results.

Documented by publisher. Oracle SQLcl 26.3 MCP tools; Oracle SQLcl 26.3 MCP restrict levels

Write capability

SQL/PLSQL and enabled commands may change database state.

Documented by publisher. Oracle SQLcl 26.3 MCP tools; Oracle SQLcl 26.3 MCP restrict levels

Authentication

Saved named database connections.

Documented by publisher. Oracle SQLcl 26.3 MCP tools; Oracle SQLcl 26.3 MCP restrict levels

Permission surface

Database grants and SQLcl command restrict level are distinct.

Documented by publisher. Oracle SQLcl 26.3 MCP tools; Oracle SQLcl 26.3 MCP restrict levels

Data leaving the environment

Database results pass through SQLcl to the agent.

Review inference. Oracle SQLcl 26.3 MCP tools; Oracle SQLcl 26.3 MCP restrict levels

Failure modes to consider

Broad saved credentials or relaxed command restrictions increase reach.

Review inference. Oracle SQLcl 26.3 MCP tools; Oracle SQLcl 26.3 MCP restrict levels

Unknowns and applicability

Installed version, saved identities and effective grants are unverified.

Not established

Suggested refusal or clarification condition

Require database-level read constraints before claiming read-only use.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. SQLcl version, command restrictions and connection grants.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve separate local-command and database-authority checks.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Organization policy: Existing-resource exceptions

Question: Does a new Google organization policy automatically correct existing violations?

Organization policies are usually not retroactive unless the specific constraint says otherwise. A service already in a newly prohibited state can continue its earlier behaviour and require separate correction. Constraint-specific applicability and dry-run evidence matter; assignment alone does not establish that old resources were remediated.

Source: Google Cloud organization policy constraints. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: New organization policy immediately makes every existing resource conform.

Buyer evidence still required

  • Exact constraint and retroactivity documentation.
  • Existing-resource inventory and effective policy.
  • Remediation outcomes and dry-run results.

Suggested review condition: Require evidence for existing resources rather than inferring correction from assignment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Constraint, inherited policy, existing resource state and remediation evidence.

Optional saved evidence: Save the source-bound applicability review for organization-wide control claims.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV queries: Choose one package and version representation

Question: How should an agent identify a package version in an OSV query?

OSV's query documentation separates commit queries from package-version queries. Do not combine a commit with a top-level version. Identify a package through its name and ecosystem, or through a package URL. Supply the version either separately or within that URL; supplying both returns a bad-request response. Preserve the actual package identity and case. A valid query does not establish that the identified package is deployed or safe.

Source: OSV: POST /v1/query. Documentation checked 2026-10-11; no deployment validation is claimed.

Claim boundaries
  • a valid query proving deployment or safety
  • conflicting version fields silently resolved
  • identical names across ecosystems treated as one package

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV-Scanner: Input coverage

Question: Does scanning a lockfile or SBOM establish complete deployment coverage?

OSV-Scanner documents SBOM, lockfile and directory inputs. The result depends on what the supplied input represents; supported input formats do not establish a complete inventory of the running system.

Source: OSV.dev. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • complete running-system inventory
  • zero vulnerabilities
  • all code paths assessed

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV: Advisory provenance

Question: What does OSV aggregation establish about a vulnerability advisory?

OSV aggregates advisories in a shared vulnerability format. The originating advisory and affected-version mapping remain relevant; aggregation does not establish that a particular deployment is affected.

Source: OSV data sources and advisory format. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • verified exploitation in a customer system
  • complete database coverage
  • independent confirmation of every advisory

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV: Affected versions and range boundaries

Question: Is a version unaffected if it is missing from an advisory versions list?

OSV allows affected versions to be expressed by enumeration or ranges. Check both using the appropriate ecosystem or commit ordering. fixed, last_affected and limit have different meanings; a missing enumerated version or a range boundary alone must not be turned into a general safety conclusion.

Source: OSV: Affected versions and range boundaries. Documentation checked 2026-10-08; no deployment validation is claimed.

Claim boundaries
  • safety from absent enumeration alone
  • interchangeable range-event meanings
  • correct evaluation by an unsupported version comparator
  • runtime exploitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV: Alias IDs and corroboration

Question: Do multiple advisory IDs provide independent confirmation of a vulnerability?

OSV aliases identify the same vulnerability across databases. Counting those IDs as separate confirmations overstates the evidence. Distinguish alias, upstream and related links, and inspect the originating evidence before claiming independent corroboration.

Source: OSV: Alias IDs and corroboration. Documentation checked 2026-10-08; no deployment validation is claimed.

Claim boundaries
  • independent confirmation from identifier count
  • distinct vulnerabilities from aliases alone
  • verified applicability to a deployment

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV: API rate and response-size boundaries

Question: Does an API with no published rate limit guarantee unlimited retrieval?

OSV currently documents no API rate limit, but limits HTTP/1.1 responses to 32 MiB and recommends HTTP/2 for large responses. This is a dated description of the upstream service, not an availability guarantee or a limit inherited by other providers. Check the actual endpoint and transport before planning retrieval.

Source: OSV API 1.0: Rate and response-size limits. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • guaranteed throughput or availability
  • unchanged future service policy
  • the limits of a downstream service

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV: Import quality findings

Question: Are OSV import findings accepted vulnerability results?

OSV documents an experimental endpoint for records that fail import-time quality checks. Such findings describe ingestion issues and must not be treated as accepted vulnerability results or a stable interface guarantee.

Source: OSV API 1.0. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • accepted advisory status
  • stable experimental API contract
  • vulnerability proven by an import failure

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV: Known vulnerability queries

Question: Does an empty OSV query prove a package has no vulnerabilities?

OSV provides queries for known vulnerabilities by package version or commit, including batches. No returned match does not prove absence of unknown issues or correct identification of the deployed artifact.

Source: OSV API 1.0. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • absence of all vulnerabilities
  • complete deployed dependency identification
  • runtime exploitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OSV: Withdrawn advisory interpretation

Question: Does a withdrawn advisory mean the package is safe?

In OSV, withdrawn dates the retirement of that advisory entry; its summary can explain why. Withdrawal alone is not a package-safety verdict. Check the publisher explanation and other applicable records before deciding what remains relevant.

Source: OSV: Withdrawn advisory interpretation. Documentation checked 2026-10-08; no deployment validation is claimed.

Claim boundaries
  • package-wide safety
  • resolution of other advisories
  • a verified fix in the buyer deployment

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

OT3: Workload reduction boundary

Question: Does the OT3 development record establish workload reduction?

The OT3 public source records development learning without reduction promotion. Workload reduction is explicitly not demonstrated.

Derived from BDAS OT3 — Frequency-Localized Development Record. No new experiment or validation is claimed.

Claim boundaries
  • workload reduction
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OTLP acknowledgement and multi-hop delivery

Question: Does an OTLP exporter acknowledgement prove durable retention in the final telemetry backend?

OTLP 1.11.1 defines acknowledgements between a single client and server. A full-success response means that receiver accepted the telemetry. End-to-end delivery guarantees across intermediaries are outside the protocol's scope. Acceptance by an agent or collector therefore does not establish durable retention in a downstream backend.

Source: OTLP Specification 1.11.1 | OpenTelemetry. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an OTLP exporter acknowledgement prove durable retention in the final telemetry backend?

Buyer evidence still required

  • Exporter destination and complete collector-to-backend path
  • Acknowledgements and rejection evidence at relevant hops
  • Backend ingestion and retention evidence for the required batch

Review inference: Identify the acknowledging hop and obtain downstream evidence before claiming that an audit batch is retained end to end.

Suggested review condition: Do not claim durable end-to-end evidence retention using only the first exporter acknowledgement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Downstream forwarding, storage durability and record retention were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Locate the proof needed between successful telemetry export and retained audit evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • End-to-end delivery, lossless collection or durable storage guarantees
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OTLP partial success and rejected telemetry

Question: Should an OTLP client retry an export when the response contains partial_success?

OTLP 1.11.1 uses a populated partial_success response to report rejected telemetry counts or warnings. The client must not retry that request. A warning can carry zero rejected items, so a populated field is not itself evidence of data loss; the rejection counts and diagnostic message must be interpreted. An HTTP success response can still report rejected spans.

Source: OTLP Specification 1.11.1 | OpenTelemetry. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Should an OTLP client retry an export when the response contains partial_success?

Buyer evidence still required

  • Complete export response including rejected counts and message
  • Batch identity and affected signal type
  • Receiver records and a separately justified remediation plan

Review inference: Record partial acceptance and reconcile missing evidence instead of blindly resending the whole accepted-and-rejected batch.

Suggested review condition: Do not report full ingestion from HTTP status alone or automatically replay the entire batch after partial_success.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Which specific business actions lack retained evidence and whether later remediation restored them remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Distinguish accepted telemetry, rejected evidence and warnings during audit recovery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Full ingestion from HTTP success or permission to disregard OTLP retry rules
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Output V3: Persistence versus truth

Question: Does preserving an Output V3 result establish claim truth?

Output V3 supports an output-persistence check and auditability posture. Its public source excludes claim truth.

Derived from BDAS Persistent Output V3 — Output Persistence Check. No new experiment or validation is claimed.

Claim boundaries
  • claim truth
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Outsourcing does not erase the first processor obligation

Question: Does a supplier shift its Article 28 responsibilities to the buyer simply by using a subprocessor?

UK Article 28(4) requires the same data-protection obligations to bind the further processor through a contract or other legal act. The initial processor remains fully liable to the controller for performance of those obligations if the further processor fails. Review implication: A list of subcontractors does not establish the obligation chain. Case-specific liability, damages and transfer legality need separate competent assessment.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a supplier shift its Article 28 responsibilities to the buyer simply by using a subprocessor?

Buyer evidence still required

  • Processing-chain identities and activities
  • Relevant upstream and downstream contractual obligations
  • Evidence of sufficient guarantees and responsibility allocation

Review inference: A list of subcontractors does not establish the obligation chain. Case-specific liability, damages and transfer legality need separate competent assessment.

Suggested review condition: Do not decide case-specific legal liability, damages or third-country transfer legality.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • Do not decide case-specific legal liability, damages or third-country transfer legality.
  • A properly bound downstream arrangement can provide the obligation chain; this record does not decide whether a particular loss attracts damages.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

OWASP Agent Control Standard: Foundation scope

Question: Does citing the OWASP Agent Control Standard establish certified agent safety?

OWASP presents the Agent Control Standard as an open foundation for inspectable, traceable and instrumentable agent behaviour. This describes a control framework’s purpose. Citing or adopting it does not establish certification, complete implementation or tested safety of a particular agent.

Source: Agent Control Standard (ACS) — OWASP GenAI Security Project. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • agent certification
  • complete control implementation
  • tested deployment safety

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OWASP Agent Control Standard: Middleware enforcement boundary

Question: Does portable agent-control configuration prove middleware enforces it?

OWASP describes the Agent Control Standard in relation to middleware hooks and portable declarative controls. A declared control still needs an integration that applies it at the relevant execution point. Portability of configuration does not prove universal platform support or enforcement in a specific runtime.

Source: Agent Control Standard (ACS) — OWASP GenAI Security Project. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • universal platform compatibility
  • enforcement without an integration
  • coverage of every execution path

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OWASP Agentic Top 10: Guidance adoption evidence

Question: Does adopting OWASP agentic guidance establish tested security controls?

OWASP's agentic resource provides security guidance. A statement that a team follows it does not demonstrate implementation or test results; each claimed mitigation needs evidence tied to the relevant agent behaviour and deployment.

Source: OWASP Top 10 for Agentic Applications for 2026. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • implemented mitigations from a policy statement
  • passing security tests
  • OWASP certification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OWASP Agentic Top 10: Risk catalogue scope

Question: What does OWASP's 2026 Agentic Top 10 provide?

OWASP's 2026 Agentic Top 10 presents security risks for agentic applications. It can inform threat review, but a catalogue is not an exhaustive assessment of a particular agent, its integrations or the actions it can perform.

Source: OWASP Top 10 for Agentic Applications for 2026. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • exhaustive threat coverage
  • assessment of a specific deployment
  • absence of unlisted risks

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OWASP MCP guide: Delegated permission boundary

Question: Does connecting an assistant to an MCP server authorise every chained tool action?

OWASP's MCP guide describes risks from delegated permissions, dynamic tools and chained calls. Connecting an assistant to a server does not establish user intent or permission for each downstream action; the actual authorisation scope and enforcement need review.

Source: A Practical Guide for Secure MCP Server Development. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • permission for every chained action
  • verified user intent
  • safe downstream effects

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OWASP MCP guide: Server security scope

Question: What does OWASP's MCP server development guide help assess?

OWASP's MCP server guide discusses security across the server boundary, including authentication, authorisation, input handling, isolation and deployment. This is development guidance; it does not validate a specific server or its connected tools.

Source: A Practical Guide for Secure MCP Server Development. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • tested server security
  • correctly configured authentication
  • safe connected tools

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OWASP: Agent skill and tool-interface review scope

Question: Does reviewing an MCP connection cover the security of the agent skills that use it?

OWASP Agentic Skills Top 10 treats skills as the behaviour and execution layer that coordinates workflows, distinct from the MCP tool-communication layer. An integration review should therefore identify both the exposed tool interface and the instructions and actions the skill orchestrates. This incubator guidance supplies a review perspective; citing it does not certify a skill or demonstrate that its permissions and behaviour are safe.

Source: OWASP Agentic Skills Top 10. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • certification of a skill or connector
  • tested resistance to malicious instructions
  • verified runtime permission enforcement

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

OWASP: Mapping LLM risks to other frameworks

Question: Where can I connect LLM security risks to an existing control review?

OWASP's 2026 LLM Top 10 describes risk mappings to NIST, MITRE ATLAS, CWE and the Agentic Applications Top 10. Use these references to locate related risks and review questions. A mapping does not show that a control was implemented or effective. Preserve the editions, selected mapping and application evidence separately; this entry does not assess compliance.

Source: OWASP GenAI LLM Top 10 2026. Documentation checked 2026-10-11; no deployment validation is claimed.

Claim boundaries
  • equivalence of mapped frameworks
  • implemented or effective controls
  • certification or legal compliance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PagerDuty MCP: Regional identity and incident changes

Question: Can I connect PagerDuty MCP for incident review without granting authority to change operations?

PagerDuty documents read and management tools on its hosted MCP service. Authentication scopes constrain successful calls, while hosted tool filtering is not available. Check the regional endpoint, key type and granted scopes before connecting; incident visibility does not authorize changing schedules, services or incident state.

Source: PagerDuty hosted MCP scopes and regional endpoints. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official hosted regional MCP service

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

PagerDuty operates the hosted MCP service; the self-hosted predecessor is deprecated.

Documented by publisher. PagerDuty hosted MCP scopes and regional endpoints

Purpose

Query incident operations and manage supported operational resources.

Documented by publisher. PagerDuty hosted MCP scopes and regional endpoints

Read capability

Incidents, services, schedules and related operational records.

Documented by publisher. PagerDuty hosted MCP scopes and regional endpoints

Write capability

Management tools can create, update or delete supported resources.

Documented by publisher. PagerDuty hosted MCP scopes and regional endpoints

Authentication

API key or OAuth; key types and scopes affect tool behavior.

Documented by publisher. PagerDuty hosted MCP scopes and regional endpoints

Permission surface

Scopes constrain calls; hosted tool filtering is not currently documented as available.

Documented by publisher. PagerDuty hosted MCP scopes and regional endpoints

Data leaving the environment

Operational records and action inputs pass through PagerDuty and the connected client.

Review inference. PagerDuty hosted MCP scopes and regional endpoints

Failure modes to consider

Wrong-region credentials or excessive scopes can cause errors or unauthorized task expansion.

Review inference. PagerDuty hosted MCP scopes and regional endpoints

Unknowns and applicability

Buyer region, effective scopes and approved incident actions are unverified.

Not established

Suggested refusal or clarification condition

Confirm affected resources and task authority before operational changes.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck hosted tool inventory, scope mapping, region and client authentication support.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the regional, identity and read-versus-action boundary for an incident assistant.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Parameter history: Another path to current values

Question: Does denying GetParameter prevent an agent from reading the current parameter value?

Parameter Store authorizes retrieval operations separately. GetParameterHistory can expose the current version as well as earlier values, including SecureString values when decryption is permitted. A denial of other retrieval actions is not evidence that the history path is closed. Parameter and KMS permissions require joint review.

Source: Systems Manager Parameter Store access. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Denying the ordinary read API closes every route to a current parameter value.

Buyer evidence still required

  • Effective permissions for each retrieval operation.
  • Version-history access.
  • Applicable KMS decryption grants.

Suggested review condition: Inspect history and decryption authority before approving metadata-only access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Parameter identities, retrieval actions, history permissions and KMS grants.

Optional saved evidence: Preserve the access-path distinction behind a least-privilege review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Partial approval batch execution boundary

Question: Do unresolved OpenAI Agents SDK approvals prevent every call in the same interruption batch from continuing?

The pinned Python SDK documentation permits resolving only some pending approvals. On resume, resolved calls can continue while unresolved calls remain in interruptions and pause the run again. A remaining approval interruption is not evidence that no call from the batch has progressed.

Source: OpenAI Agents Python human-in-the-loop guide, v0.24.0. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do unresolved OpenAI Agents SDK approvals prevent every call in the same interruption batch from continuing?

Buyer evidence still required

  • Exact installed version, provider variant and effective non-secret configuration
  • Relevant pending-call identifiers, declared arguments and decision provenance without secrets
  • Application-owned review policy and independently observed outcomes where needed

Review inference: Track each pending decision and resulting call separately; an interruption list is not an atomic all-or-nothing execution gate or proof of zero side effects. The existing SDK resumption record explains continuing saved state but not mixed resolved/unresolved batches. This changes how an auditor interprets a new interruption after partial resume. Operational review inference; no deployment outcome was observed.

Suggested review condition: Track each pending decision and resulting call separately; an interruption list is not an atomic all-or-nothing execution gate or proof of zero side effects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Approval decisions / resolving a subset of interruptions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Track each pending decision and resulting call separately; an interruption list is not an atomic all-or-nothing execution gate or proof of zero side effects.
  • An application can require all decisions before calling Runner; that extra policy is not inferred from the SDK interruption mechanism.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Payload suppression still leaves defined metadata paths

Question: Does a Cloudflare AI Gateway payload-log opt-out eliminate the full request log?

The payload header controls request and response bodies while metadata can still be logged. The collect-log header controls the wider stored entry and overrides gateway defaults. For Unified Billing, billing details are recorded even when collection headers are false. These controls apply to gateway-stored logs, not provider retention.

Source: Logging. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Cloudflare AI Gateway payload-log opt-out eliminate the full request log?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require gateway defaults, actual headers and billing mode; do not infer no retained data from absent prompt bodies.

Suggested review condition: Require gateway defaults, actual headers and billing mode; do not infer no retained data from absent prompt bodies.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ### Collect log payload; If `cf-aig-collect-log` is set

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require gateway defaults, actual headers and billing mode; do not infer no retained data from absent prompt bodies.
  • For an ordinary request with collection disabled, the normal stored log entry can be skipped; the documented billing exception must not be applied indiscriminately.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

PayPal MCP: Merchant identity and sandbox separation

Question: Does a successful PayPal MCP sandbox call establish a live merchant outcome?

No. PayPal documents separate sandbox and production settings and endpoints. Local access tokens and remote client-credential setup also need the intended account context. A sandbox result is testing evidence; it does not establish that a real payment, invoice or other production action completed.

Source: PayPal local/remote MCP and sandbox/production distinction. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Local and remote merchant connectors

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

PayPal publishes the local connector and operates remote endpoints.

Documented by publisher. PayPal local/remote MCP and sandbox/production distinction

Purpose

Connect merchant workflows to MCP-compatible assistants.

Documented by publisher. PayPal local/remote MCP and sandbox/production distinction

Read capability

The quickstart demonstrates retrieval of invoice information.

Documented by publisher. PayPal local/remote MCP and sandbox/production distinction

Write capability

The quickstart alone does not establish the complete enabled write-tool set for the buyer.

Not established. PayPal local/remote MCP and sandbox/production distinction

Authentication

Local access token or documented remote client-credential authorisation.

Documented by publisher. PayPal local/remote MCP and sandbox/production distinction

Permission surface

Buyer merchant entitlements and enabled tool permissions require separate inspection.

Not established. PayPal local/remote MCP and sandbox/production distinction

Data leaving the environment

Merchant information returned by tools enters the assistant.

Review inference. PayPal local/remote MCP and sandbox/production distinction

Failure modes to consider

A sandbox result can be misreported as a real merchant action.

Review inference. PayPal local/remote MCP and sandbox/production distinction

Unknowns and applicability

Live permissions, payment status and tool-level effects have not been verified.

Not established

Suggested refusal or clarification condition

Require environment and verified operation evidence before reporting a live financial outcome.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck environment, merchant credentials and supported tool definitions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the environment and evidence distinction used in a merchant-connector review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PayPal: Approved order terms can still change

Question: Does payer approval of a PayPal order prove the final captured amount and shipping terms are unchanged?

PayPal documents updating order amounts and shipping details before capture, including changes after payer approval. Its checkout guidance uses Continue with commit=false when final amounts may change. An agent must compare the approved intent with the final order rather than assuming approval freezes every term.

Source: Update order details | PayPal Developer. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does payer approval of a PayPal order prove the final captured amount and shipping terms are unchanged?

Buyer evidence still required

  • Approved intent and original order.
  • PATCH changes and final order details.
  • Owner-authorized amount, recipient and conditions.

Suggested review condition: Do not rely on the original approval when changed final terms have not been reconciled with delegated authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Approved intent and original order. PATCH changes and final order details. Owner-authorized amount, recipient and conditions.

Optional saved evidence: Detect a mismatch between delegated purchase terms and the final capture request.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Owner approval of amendments, payment execution or final settlement verification
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PayPal: Authorisation and capture are distinct outcomes

Question: Does a PayPal payment authorisation guarantee that a later agent capture will succeed?

PayPal separates authorisation from capture. The documented authorisation window is 29 days, with a three-day honor period; later capture depends on risk assessment and available funds. Reauthorisation produces a new authorisation ID that must be used for subsequent capture. An authorisation is not a completed settlement.

Source: PayPal authorization and capture. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a PayPal payment authorisation guarantee that a later agent capture will succeed?

Buyer evidence still required

  • The approved transaction and authorisation time.
  • Any reauthorisation and current authorisation ID.
  • The provider capture status, amount and reference.

Suggested review condition: Do not report payment completion or guaranteed capture solely from an earlier authorisation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The approved transaction and authorisation time. Any reauthorisation and current authorisation ID. The provider capture status, amount and reference.

Optional saved evidence: A delegated purchasing owner needs current authority and capture evidence before treating an order as paid.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Procurement permission, live funds availability or guaranteed capture success
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PayPal: Retry identity returns the latest request status

Question: Can an agent safely retry an uncertain PayPal capture as a new request?

PayPal documents PayPal-Request-Id for supported APIs, with endpoint-specific retention. Reusing the original identifier returns the latest status of that request; omitting it can duplicate the request. A timeout does not establish that the first capture failed.

Source: PayPal REST API idempotency. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent safely retry an uncertain PayPal capture as a new request?

Buyer evidence still required

  • The API support and identifier-retention window.
  • The original request ID and approved transaction details.
  • Provider-side capture state and recovery response.

Suggested review condition: Do not create a fresh capture merely because the first response was lost or its outcome remains unknown.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The API support and identifier-retention window. The original request ID and approved transaction details. Provider-side capture state and recovery response.

Optional saved evidence: A payment operator must reconcile uncertain capture state before issuing another money-moving request.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authorisation to charge, live payment verification or a universal PayPal retention period
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Peppol amended order completeness

Question: Can a Peppol amended Order Response omit unchanged or already delivered lines?

For an amended Ordering 3.3 response, the seller supplies all lines, including unchanged and already delivered lines. Individual line decisions may differ. A changes-only extract is insufficient to reconstruct the complete response; reconcile the supplied lines against the original order rather than interpreting omissions as agreement.

Source: BIS Ordering 3.3 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Peppol amended Order Response omit unchanged or already delivered lines?

Buyer evidence still required

  • Original order lines
  • Complete amended response
  • Each line decision and references

Review inference: Reconstruct the full commercial position after an amended order response. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse completeness when unchanged or previously delivered lines are missing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual order-line completeness was not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual order-line completeness was not tested.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol billing profile and response capability

Question: Does basic Peppol Billing Profile 01 guarantee a structured invoice response?

Billing 3.0.21 distinguishes basic Profile 01 from Billing with Response Profile 02. The release notes require separate SMP registration for the response profile. An invoice under the basic profile does not itself establish structured response support; check the recipient capability and the actual process agreement.

Source: BIS Billing 3.0.21 — May 2026 release. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does basic Peppol Billing Profile 01 guarantee a structured invoice response?

Buyer evidence still required

  • Invoice ProfileID
  • Recipient SMP capability registration
  • Agreed response process

Review inference: Confirm response capability before depending on automated invoice feedback. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse guaranteed structured feedback inferred from basic Billing Profile 01.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Live recipient registration and response delivery were not checked.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Live recipient registration and response delivery were not checked.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol buyer routing reference versus approved order

Question: Does a Peppol invoice BuyerReference establish an approved purchase order?

BIS Billing requires a buyer reference or purchase-order reference. A BuyerReference can route an invoice to a person or department; it is not itself evidence of an approved purchase order. Check the referenced commercial authority separately before an agent treats the invoice as authorised spend.

Source: BIS Billing 3.0.21 — May 2026 release. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a Peppol invoice BuyerReference establish an approved purchase order?

Buyer evidence still required

  • BuyerReference or order reference
  • Referenced procurement approval
  • Buyer authority policy

Review inference: Separate invoice routing from permission to pay. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse approved-spend conclusions from an internal routing reference alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer approval record was not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer approval record was not inspected.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol card identification without full card data

Question: Should a Peppol card-payment invoice contain the full payment card number?

BIS Billing limits the card account identifier to the last four to six digits and includes a card-network identifier. These fields support identifying the declared payment method; they are not full card credentials or independent evidence that the card payment was authorised or completed.

Source: BIS Billing 3.0.21 — May 2026 release. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Should a Peppol card-payment invoice contain the full payment card number?

Buyer evidence still required

  • Truncated card identifier
  • Card network identifier
  • Separate payment verification evidence

Review inference: Avoid unnecessary sensitive card data and unsupported payment conclusions. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse full-card-data collection or completed-payment claims justified only by invoice card fields.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Card authorisation and settlement were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Card authorisation and settlement were not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol cart validity and seller time zone

Question: Can a procurement agent rely on a Peppol Punch Out cart after its seller-defined validity expires?

Punch Out 3.1 permits validity periods for the cart and its lines. A date-only expiry ends at the close of that day in the seller time zone, and applicable contract terms take precedence over cart information. Recheck validity before relying on the selected price or availability.

Source: BIS Punch Out 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a procurement agent rely on a Peppol Punch Out cart after its seller-defined validity expires?

Buyer evidence still required

  • Cart and line validity periods
  • Seller time zone
  • Applicable contract terms

Review inference: Avoid buying against an expired or superseded cart. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse current-price reliance when the applicable validity or overriding terms are unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Current seller pricing and contract applicability were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Current seller pricing and contract applicability were not verified.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol catalogue acceptance versus purchasing

Question: Does accepting a Peppol Catalogue place an order for the listed items?

Catalogue With Response 3.1 supports accepting catalogue information into the buyer system. Ordering is a separate process outside that catalogue exchange. Catalogue acceptance therefore does not establish a purchase commitment for the listed items or permission for an agent to place an order.

Source: BIS Catalogue With Response 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does accepting a Peppol Catalogue place an order for the listed items?

Buyer evidence still required

  • Catalogue acceptance response
  • Buyer procurement policy
  • Separate approved purchase order

Review inference: Avoid converting catalogue approval into purchase authority. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse purchase-commitment claims from catalogue acceptance alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Any actual purchase approval or order was not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Any actual purchase approval or order was not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol catalogue item update identity

Question: Should a Peppol catalogue item update be matched by CatalogueLine ID?

Catalogue With Response 3.1 identifies an item for update through its seller or standard item identifier, rather than the CatalogueLine ID. An updated line is replaced as a whole, and line update or deletion is used under a header Update. Retain the correct item key to avoid modifying an unrelated entry.

Source: BIS Catalogue With Response 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Should a Peppol catalogue item update be matched by CatalogueLine ID?

Buyer evidence still required

  • Header and line action codes
  • Seller or standard item identifier
  • Complete replacement line

Review inference: Apply catalogue changes to the intended commercial item. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse an item update matched only by CatalogueLine numbering.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer item mapping and update results were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Buyer item mapping and update results were not inspected.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol catalogue replacement versus patch

Question: Is an omitted Peppol Catalogue action equivalent to a partial catalogue update?

Catalogue With Response 3.1 defaults an omitted header action to Replace. Update has different, partial-update semantics, and action codes are case-sensitive. Treating an unlabelled incoming catalogue as a patch can therefore leave obsolete items in the buyer system. Resolve the header action before applying the message.

Source: BIS Catalogue With Response 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Is an omitted Peppol Catalogue action equivalent to a partial catalogue update?

Buyer evidence still required

  • Incoming catalogue header action
  • Previously accepted catalogue
  • Buyer import mode

Review inference: Prevent obsolete catalogue entries surviving an intended replacement. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse to interpret an omitted action as an incremental update.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual catalogue import behaviour was not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual catalogue import behaviour was not tested.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol complete-cart purchase restrictions

Question: Can an agent select only some items from a Peppol Punch Out cart marked complete?

Punch Out 3.1 marks a complete cart through ActionCode set to true. Such a cart is intended to be ordered together without changing its quantities; when that indication is absent, the documented default is false and partial selection is allowed. Preserve the flag before letting an agent remove items or change quantities.

Source: BIS Punch Out 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can an agent select only some items from a Peppol Punch Out cart marked complete?

Buyer evidence still required

  • Cart ActionCode
  • All line quantities
  • Buyer proposed order

Review inference: Respect the declared cart composition when preparing a purchase. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse partial selection from a cart explicitly marked complete.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The seller cart and resulting order were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The seller cart and resulting order were not inspected.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol credit note correction identity

Question: Is a preceding invoice number sufficient to uniquely bind a Peppol credit note correction?

BIS Billing allows correction references to preceding invoices. If an invoice number does not uniquely identify the earlier document, its issue date is also needed. Bind the correction to the intended invoice instance before reconciling balances; the correction reference does not establish that a cash refund occurred.

Source: BIS Billing 3.0.21 — May 2026 release. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Is a preceding invoice number sufficient to uniquely bind a Peppol credit note correction?

Buyer evidence still required

  • Preceding invoice identifier
  • Issue date where needed for uniqueness
  • Credit note and separate refund evidence

Review inference: Avoid applying a credit correction to the wrong invoice. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse a unique correction match where reused invoice numbers remain ambiguous.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Balance adjustment and any refund were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Balance adjustment and any refund were not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol currency conversion validation boundary

Question: Does Peppol invoice validation verify the exchange rate used for VAT accounting currency?

BIS Billing permits a VAT accounting currency different from the invoice currency. The exchange rate is not supplied in the invoice instance, and that conversion is not validated there. Obtain the applicable rate and calculation evidence separately; successful invoice validation cannot establish the correctness of the conversion.

Source: BIS Billing 3.0.21 — May 2026 release. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does Peppol invoice validation verify the exchange rate used for VAT accounting currency?

Buyer evidence still required

  • Invoice and VAT accounting currencies
  • Applicable exchange-rate evidence
  • Conversion calculation and accounting context

Review inference: Expose a financial calculation outside document validation. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse verified currency-conversion claims from invoice validation alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Exchange-rate correctness and tax treatment were not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Exchange-rate correctness and tax treatment were not assessed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol despatch across purchase orders

Question: Can one Peppol Despatch Advice be assumed to belong to a single purchase order?

A Despatch Advice 3.1 message may cover more than one order, while an order may have several despatch notices. For a multi-order notice, references belong on individual lines rather than a single header order reference. Reconcile these relationships before counting received quantities against a purchase order.

Source: BIS Despatch Advice 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can one Peppol Despatch Advice be assumed to belong to a single purchase order?

Buyer evidence still required

  • Despatch identifier and lines
  • Line-level purchase-order references
  • Other notices for the same order

Review inference: Avoid attributing a combined shipment to one order. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse a one-message-one-order assumption without checking references.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual shipment consolidation and receipt quantities were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual shipment consolidation and receipt quantities were not verified.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol despatch notice versus goods receipt

Question: Does a Peppol Despatch Advice prove that the buyer received the goods?

Despatch Advice 3.1 describes goods being sent and information supporting their receipt. It is a supplier notice, not an independent observation that the buyer received or accepted those goods. Match it to receiving records before treating physical delivery as complete.

Source: BIS Despatch Advice 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Peppol Despatch Advice prove that the buyer received the goods?

Buyer evidence still required

  • Despatch advice
  • Purchase-order references
  • Independent receiving or acceptance record

Review inference: Prevent a shipping notice being counted as completed receipt. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse completed goods receipt from despatch advice alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Physical delivery and condition were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Physical delivery and condition were not inspected.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol expected later supply versus total shortfall

Question: Does Peppol OutstandingQuantity represent every ordered item that has not arrived?

Despatch Advice 3.1 uses OutstandingQuantity for the quantity expected to follow later. It does not necessarily represent every unit that has not been delivered: some remaining ordered quantity may never follow. Reconcile ordered, despatched and expected-later quantities separately before calculating an unresolved shortfall.

Source: BIS Despatch Advice 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Peppol OutstandingQuantity represent every ordered item that has not arrived?

Buyer evidence still required

  • Ordered quantity
  • Despatched quantity
  • OutstandingQuantity and seller explanation

Review inference: Identify shortfalls not covered by promised later shipments. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse to equate expected later supply with the complete undelivered balance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Later deliveries and cancellation of any balance were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Later deliveries and cancellation of any balance were not verified.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol invoice rejection versus obligation

Question: Does a Peppol invoice rejection cancel the invoice content or underlying payment obligation?

Invoice Response 3.2 communicates processing status without changing the invoice content or the parties commercial responsibilities. A rejection response therefore is not, by itself, evidence that the underlying invoice was cancelled or the transaction reversed. Preserve any separate correction, cancellation or dispute resolution.

Source: BIS Invoice Response 3.2 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Peppol invoice rejection cancel the invoice content or underlying payment obligation?

Buyer evidence still required

  • Rejected invoice and response
  • Reason or requested action
  • Separate correction or cancellation evidence

Review inference: Avoid treating a processing rejection as a completed commercial reversal. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse automatic cancellation or extinguished-obligation conclusions from RE alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Contractual obligations and legal effects were not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Contractual obligations and legal effects were not assessed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol invoice seller versus payee

Question: Does a Peppol invoice always direct payment to its seller?

BIS Billing distinguishes the seller from an optional payee. When a payee is omitted, the seller is the assumed recipient; a separate payee can represent a factoring arrangement. A declared name and payment account do not independently verify account ownership or authorise a changed destination.

Source: BIS Billing 3.0.21 — May 2026 release. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Peppol invoice always direct payment to its seller?

Buyer evidence still required

  • Seller and optional payee identities
  • Payment account details
  • Independent destination-change approval

Review inference: Resolve the intended recipient before acting on invoice payment details. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse account ownership or change authority inferred solely from invoice fields.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Recipient identity and bank account ownership were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Recipient identity and bank account ownership were not verified.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol invoice status finality and corrections

Question: Can a Peppol buyer report an approved invoice as under query by sending a later Invoice Response?

Invoice Response 3.2 constrains transitions: following AP, the next protocol status is PD; final RE or fully paid PD ends the response sequence. A later changed decision must be communicated by other means. The documented PD with partial-payment clarification is an exception to final payment, so inspect that clarification before closing reconciliation.

Source: BIS Invoice Response 3.2 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Peppol buyer report an approved invoice as under query by sending a later Invoice Response?

Buyer evidence still required

  • Previous response status
  • Payment clarification where present
  • Separate communication of a changed decision

Review inference: Identify corrections that cannot be reconstructed from later protocol responses alone. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse a complete decision history from protocol responses when an out-of-band correction is needed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Any changed decision outside the response exchange was not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Any changed decision outside the response exchange was not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol invoice status sequence gaps

Question: Must every Peppol Invoice Response status appear before an invoice is reported paid?

Invoice Response 3.2 does not require every intermediate status to be reported. A response carries the current status and the first response may begin later in the documented sequence. Missing intermediate messages alone do not prove that approval steps were skipped; assess the reporting agreement and available workflow evidence.

Source: BIS Invoice Response 3.2 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Must every Peppol Invoice Response status appear before an invoice is reported paid?

Buyer evidence still required

  • Received response sequence
  • Agreed reporting requirements
  • Independent workflow or approval evidence

Review inference: Distinguish omitted status reporting from missing approval work. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse an omitted-control finding based solely on absent intermediate status messages.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual internal processing steps were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual internal processing steps were not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol maximum backorder quantity

Question: Does a Peppol MaximumBackorderQuantity promise delivery of the entire unfulfilled order line?

Ordering 3.3 uses MaximumBackorderQuantity for the maximum quantity that may be delivered later when its delivery date is unknown. A zero value indicates that the remaining quantity will not be delivered. Neither a positive maximum nor a missing delivery date establishes that the whole outstanding order will arrive.

Source: BIS Ordering 3.3 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Peppol MaximumBackorderQuantity promise delivery of the entire unfulfilled order line?

Buyer evidence still required

  • Ordered and delivered quantities
  • MaximumBackorderQuantity
  • Seller timing and remaining commitment

Review inference: Identify unfulfilled quantities requiring replacement sourcing or clarification. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse a full-delivery promise inferred from a maximum backorder value.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Future supply and delivery dates were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Future supply and delivery dates were not verified.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol missing original order-line identity

Question: Does the Peppol despatch order-line reference NA identify a matched purchase-order line?

Despatch Advice 3.1 allows NA as a placeholder where the required order-line reference is unavailable. The presence of that field therefore does not always identify a real purchase-order line. Obtain a defensible mapping before allocating received quantities, closing a line or approving a matching invoice.

Source: BIS Despatch Advice 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the Peppol despatch order-line reference NA identify a matched purchase-order line?

Buyer evidence still required

  • Despatch order-line reference
  • Original purchase-order lines
  • Evidence resolving an NA placeholder

Review inference: Expose unresolved line matching despite valid document syntax. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse a resolved line match based on NA.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No missing-reference resolution was observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No missing-reference resolution was observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol order and line references

Question: How should a Peppol order response be matched to the original order and individual lines?

Ordering 3.3 requires an order reference at header level. If response lines are supplied, each needs the related original order-line reference. Reconciliation should use those identifiers and the correct document context; matching by item description or response position alone can attach a decision to the wrong line.

Source: BIS Ordering 3.3 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: How should a Peppol order response be matched to the original order and individual lines?

Buyer evidence still required

  • Original order identifier and lines
  • Response header order reference
  • Response line references

Review inference: Bind seller decisions to the intended original purchase lines. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse line-level acceptance attribution where original references cannot be resolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer order and response were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer order and response were not inspected.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol order cancellation decision

Question: Does sending a Peppol Order Cancellation establish that the seller accepted cancellation?

Advanced Ordering 3.0 distinguishes a buyer cancellation request from the seller decision. Cancellation may depend on agreed deadlines and whether delivery has already been prepared; the seller can accept or reject it. Keep the resulting decision before treating the order as cancelled or releasing its reserved budget.

Source: BIS Advanced Ordering 3.0 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does sending a Peppol Order Cancellation establish that the seller accepted cancellation?

Buyer evidence still required

  • Cancellation request and order reference
  • Relevant deadline and fulfilment stage
  • Seller cancellation decision

Review inference: Avoid premature cancellation and budget release. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse completed-cancellation claims from a sent request alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Seller acceptance and actual fulfilment state were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Seller acceptance and actual fulfilment state were not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol order receipt versus acceptance

Question: Does Peppol Order Response AB mean that the seller accepted the order?

Ordering 3.3 uses AB for an order that has been received but not yet processed. This response contains no order lines and anticipates a later decision. A procurement agent should retain it as receipt evidence while awaiting the seller decision required for the next commercial step.

Source: BIS Ordering 3.3 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Peppol Order Response AB mean that the seller accepted the order?

Buyer evidence still required

  • Order identifier
  • Header response code
  • Subsequent seller decision

Review inference: Avoid treating an unprocessed order as an accepted commitment. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse to mark the order accepted from AB.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No seller commitment or fulfilment was observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No seller commitment or fulfilment was observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol payment status versus settled funds

Question: Does Peppol Invoice Response PD prove the supplier received settled funds?

Invoice Response 3.2 uses PD when the buyer has initiated payment; it is not independent bank-settlement evidence. The documented partial-payment case combines PD with the PPD clarification and remains non-final. Read both status and clarification before counting an invoice as fully paid or the supplier as having received funds.

Source: BIS Invoice Response 3.2 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does Peppol Invoice Response PD prove the supplier received settled funds?

Buyer evidence still required

  • Invoice response status
  • Clarification code and amount context
  • Independent payment-provider outcome

Review inference: Prevent initiated or partial payments being counted as settled revenue. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse full settlement from PD alone, particularly when PPD is present.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual bank settlement and supplier receipt were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual bank settlement and supplier receipt were not verified.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol price basis and invoice quantity

Question: Can Peppol PriceAmount be multiplied by invoice quantity without considering BaseQuantity?

BIS Billing calculates the priced quantity using the item net price divided by its price base quantity before multiplying by invoiced quantity. Line charges, allowances and specified rounding also matter. Multiplying PriceAmount directly by quantity can therefore overstate a line when the price covers more than one unit.

Source: BIS Billing 3.0.21 — May 2026 release. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can Peppol PriceAmount be multiplied by invoice quantity without considering BaseQuantity?

Buyer evidence still required

  • Item net price and base quantity
  • Invoiced quantity and units
  • Line allowances charges and rounding

Review inference: Reconcile the amount against the declared unit-price basis. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse a line-total conclusion that ignores the declared price base.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual invoice arithmetic and unit compatibility were not executed or verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual invoice arithmetic and unit compatibility were not executed or verified.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol receipt without validation

Question: Does an AB Message Level Response establish that Peppol conformance validation ran?

In Message Level Response 3.0, AB denotes acknowledgement without validation, while AP denotes acceptance after conformance checks. RE is rejection and requires an explanatory description. An AB response should not be counted as evidence that syntax and semantic checks passed; the validation outcome must be established separately.

Source: BIS Message Level Response 3.0 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an AB Message Level Response establish that Peppol conformance validation ran?

Buyer evidence still required

  • Response code
  • Referenced envelope
  • Validation outcome and rejection description

Review inference: Separate successful receipt from completed document validation. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse a passed-validation conclusion from AB alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the recipient ran a validator is unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Whether the recipient ran a validator is unobserved.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol schema versus business-rule validation

Question: Does successful UBL schema validation establish all Peppol invoice business rules passed?

BIS Billing separates UBL schema validation from semantic business rules and the applicable Peppol restrictions, including conditionally applicable country rules. Passing XML structure checks alone does not establish that those other layers passed, nor that the invoice facts are correct. Retain the validation layer, version and results.

Source: BIS Billing 3.0.21 — May 2026 release. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does successful UBL schema validation establish all Peppol invoice business rules passed?

Buyer evidence still required

  • Schema validation result
  • Applicable rule versions and business-rule results
  • Invoice facts and country context

Review inference: Identify which validation evidence is still missing before invoice reliance. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse full conformance or factual correctness from schema validation alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No invoice instance or production validator was tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No invoice instance or production validator was tested.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol seller amendment boundaries

Question: Can a Peppol Advanced Ordering seller impose arbitrary changes to an accepted order?

Advanced Ordering 3.0 permits a seller to accept with changes within a scope previously agreed by the parties. Later order changes have their own acceptance or rejection process. Receiving a syntactically valid amendment does not establish that every proposed change falls within the buyer authorised scope.

Source: BIS Advanced Ordering 3.0 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a Peppol Advanced Ordering seller impose arbitrary changes to an accepted order?

Buyer evidence still required

  • Previously agreed change scope
  • Original and amended terms
  • Buyer or seller acceptance decision

Review inference: Check the authority for a changed purchase commitment. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse unrestricted amendment authority inferred from a valid protocol message.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Applicable agreements and actual authority were not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Applicable agreements and actual authority were not assessed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol seller delivery status versus receipt

Question: Does Peppol order-line code 42 establish independently confirmed receipt by the buyer?

Ordering 3.3 defines line response code 42 for items reported as already delivered. That code is part of the seller response. It is not an independent goods-receipt observation, so a buyer deciding whether to release an invoice should reconcile it with receiving evidence.

Source: BIS Ordering 3.3 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Peppol order-line code 42 establish independently confirmed receipt by the buyer?

Buyer evidence still required

  • Order response line and code
  • Original order-line reference
  • Buyer goods-receipt evidence

Review inference: Separate seller delivery assertions from buyer receiving records. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse independently confirmed receipt based on seller code 42 alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Physical delivery and buyer acceptance were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Physical delivery and buyer acceptance were not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol shopping cart versus placed order

Question: Does receiving a Peppol Punch Out shopping cart place an order with the supplier?

Punch Out 3.1 returns a shopping cart or item list to the buyer procurement system. The buyer prepares and sends the order separately. A returned cart therefore supports selection and pricing review but does not establish that an order was placed, approved or accepted by the supplier.

Source: BIS Punch Out 3.1 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does receiving a Peppol Punch Out shopping cart place an order with the supplier?

Buyer evidence still required

  • Returned Punch Out cart
  • Buyer approval and prepared order
  • Evidence that the order was sent and accepted

Review inference: Keep shopping activity separate from purchase commitment. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse order-completion claims from a returned cart alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer approval and actual order submission were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Buyer approval and actual order submission were not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol successive order-change reconciliation

Question: How are successive Peppol Order Change messages distinguished during reconciliation?

Advanced Ordering 3.0 requires a buyer-assigned OrderChangeSequenceNumber to distinguish successive changes. A response referring to an order change uses a header-level change document reference. Preserve both sequence and document identity: their presence identifies the proposal but does not prove that the proposed terms were accepted.

Source: BIS Advanced Ordering 3.0 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: How are successive Peppol Order Change messages distinguished during reconciliation?

Buyer evidence still required

  • Order Change document and sequence
  • Original order identity
  • Response change-document reference

Review inference: Reconstruct which amendment received which decision. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse accepted-amendment conclusions from sequence numbering alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual change ordering and recipient decisions were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual change ordering and recipient decisions were not inspected.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol technical response envelope binding

Question: Which identifier binds a Peppol Message Level Response to the business message it assessed?

The published MLR profile assesses one business document and binds its response through the original envelope instance identifier. A buyer reconciling technical responses needs the envelope-to-document association. A displayed invoice number alone does not establish which transmitted instance received the response.

Source: BIS Message Level Response 3.0 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Which identifier binds a Peppol Message Level Response to the business message it assessed?

Buyer evidence still required

  • Original envelope instance identifier
  • MLR DocumentReference
  • Envelope-to-business-document association

Review inference: Prevent a technical response being attributed to the wrong message instance. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse instance-level attribution without the referenced envelope mapping.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The transport envelope and document association were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The transport envelope and document association were not inspected.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Peppol technical response versus commercial acceptance

Question: Does a Peppol Message Level Response accepting a document also accept its commercial terms?

The published Message Level Response profile separates transport receipt, document conformance and the business decision. An accepted technical response therefore does not establish that a supplier accepted a purchase, that an invoice was approved or that a payment was authorised. Retain the appropriate business response as a separate item of evidence.

Source: BIS Message Level Response 3.0 — published November 2025 archive. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a Peppol Message Level Response accepting a document also accept its commercial terms?

Buyer evidence still required

  • Message Level Response and code
  • Referenced business message
  • Separate business decision

Review inference: Avoid releasing a purchase on technical acceptance alone. This is a review judgment, not an observed buyer outcome.

Suggested review condition: Refuse commercial-acceptance claims based solely on a technical response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The recipient business decision was not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the applicable BIS release, recipient capability, ERP mapping and independent business outcome before relying on a current transaction.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The recipient business decision was not observed.
  • No independent proof of contractual authority, goods receipt, bank settlement or legal compliance.
  • Applies to the cited published profile; current deployment and release applicability require separate verification.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External advisory review

Pillow: Trace ImageMath input control before inferring exposure

Question: Does accepting image uploads establish the input conditions of Pillow CVE-2023-50447?

Pillow's 10.2.0 release notes identify attacker control over environment argument keys passed to ImageMath.eval as the relevant condition for CVE-2023-50447. They describe restrictions added to those keys, and the frozen advisory records 10.2.0 as the fix. Merely accepting image uploads does not show that the application calls this evaluator or lets users choose those keys. Review the called API and input mapping. This historical change is not a general guarantee for untrusted expressions, image parsing or a buyer's processing pipeline.

Source: Pillow 10.2.0 release notes: CVE-2023-50447. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • image upload acceptance treated as evaluator exposure
  • one input restriction treated as general expression safety
  • image-parser or buyer-pipeline security validated

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pinecone backups after source index deletion

Question: Does deleting a Pinecone index establish that all of its independently created backups are gone?

The Pinecone Python SDK documentation states that backups outlive their source index. Project-wide backup listings include deleted-index backups, while an index-scoped lookup can return 404 after the active index is removed. It documents include_deleted for looking up backups across historical uses of the index name. Index absence is not backup absence.

Source: Backups and restore - Python SDK documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a Pinecone index establish that all of its independently created backups are gone?

Buyer evidence still required

  • Project, source index identities and deletion timestamps
  • Backup IDs, source-deletion metadata and paginated backup inventory
  • Required namespace/data scope and separate backup-deletion results

Review inference: Use backup IDs and project-wide or explicitly historical listings to reconcile residual copies.

Suggested review condition: Refuse complete erasure while backups or restored indexes remain outside the inventory.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual backup contents, names reused by indexes and retained copies are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Find retained recovery copies that a live-index inventory can miss.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Removal of backups or restored data from deleting the source index
  • Actual backup contents, names reused by indexes and retained copies are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pinecone deletion and query visibility delay

Question: Does a successful Pinecone delete response establish that an immediate query cannot return the deleted records?

Pinecone documents eventual consistency and a possible delay before changed records are visible to queries. Its delete guide directs users to check data freshness after changes. A successful deletion request and the subsequent read view are separate observations; the response alone does not establish immediate disappearance from every query.

Source: Delete data - Pinecone Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a successful Pinecone delete response establish that an immediate query cannot return the deleted records?

Buyer evidence still required

  • Delete request, record IDs and target namespace
  • Subsequent fetch/query observations and collection statistics
  • Allowed freshness interval and retry/reconciliation policy

Review inference: Reconcile the requested IDs and namespace with later fetch/query evidence and the required consistency boundary.

Suggested review condition: Do not attest immediate query absence from a delete acknowledgement alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual propagation delay and remaining returned records are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Distinguish accepted cleanup from the read state used by downstream retrieval agents.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Instantaneous query-wide removal of vectors
  • Actual propagation delay and remaining returned records are unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pinecone Developer MCP: Documentation access versus index changes

Question: Can I give an agent Pinecone documentation access without exposing project data or index writes?

Pinecone Developer MCP can search documentation without a project API key. A configured key enables project interactions including supported index creation, upserts and searches. The reviewed server supports integrated-inference indexes; it should not be represented as universal access to every Pinecone product.

Source: Pinecone Developer MCP project scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Pinecone Developer MCP; separate from Pinecone Assistant MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Pinecone publishes the Developer MCP server.

Documented by publisher. Pinecone Developer MCP project scope

Purpose

It connects coding assistants to Pinecone documentation and supported project indexes.

Documented by publisher. Pinecone Developer MCP project scope

Read capability

Tools can inspect indexes and search records; documentation search does not require a project key.

Documented by publisher. Pinecone Developer MCP project scope

Write capability

Tools include index creation and record upserts.

Documented by publisher. Pinecone Developer MCP project scope

Authentication

Project access requires a Pinecone API key.

Documented by publisher. Pinecone Developer MCP project scope

Permission surface

The reviewed capability scope is integrated-inference indexes, not every Pinecone data or Assistant interface.

Documented by publisher. Pinecone Developer MCP project scope

Data leaving the environment

Data queries and upserts cross the Pinecone service boundary and return results to the coding assistant.

Review inference. Pinecone Developer MCP project scope

Failure modes to consider

A documentation-only expectation can become data access once a key is supplied; an unsupported index type may fail.

Review inference. Pinecone Developer MCP project scope

Unknowns and applicability

Actual project grants, namespace selection, client retention and input-data rights are unverified.

Not established

Suggested refusal or clarification condition

Keep documentation-only tasks without project authority; verify target and approved data use before index operations.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck server variant, supported index types, key scope and namespace.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the reason a project credential was or was not needed for a developer workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pinecone ID inventory versus content export

Question: Does a Pinecone record count or paginated list of IDs establish a complete export of stored vector values and metadata?

Pinecone’s list operation returns IDs within a namespace, optionally filtered by prefix, without the data behind them. Fetching the records is a separate operation that returns stored values and metadata. Matching a count or enumerating IDs therefore does not establish that the exported content contains every required record and field.

Source: List IDs - Pinecone Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Pinecone record count or paginated list of IDs establish a complete export of stored vector values and metadata?

Buyer evidence still required

  • Namespace, prefix filter and all list pagination tokens
  • Requested IDs and returned vector/metadata content
  • Expected inventory, export hashes and concurrent-write boundary

Review inference: Reconcile paginated IDs, fetched content and namespace/prefix scope, with a defined treatment of concurrent changes.

Suggested review condition: Reject complete content-export claims based only on counts or IDs.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual source/export equality and stability during capture are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid accepting an inventory-only file as a usable data-exit deliverable.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Atomic or content-complete export from a count or ID list
  • The actual source/export equality and stability during capture are unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pinecone import completion and tolerated errors

Question: Does a completed Pinecone import prove every source record was successfully imported when error_mode is continue?

Pinecone documents abort and continue import error modes. Continue permits the operation to proceed after record errors without notifying which records failed; the describe operation reports how many were imported. The guide also describes silently skipped namespace directories containing no supported import files. Completion is not a record-by-record reconciliation of the source.

Source: Import records - Pinecone Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a completed Pinecone import prove every source record was successfully imported when error_mode is continue?

Buyer evidence still required

  • Import ID, source dataset and selected error mode
  • Imported-record count and resulting namespace inventory
  • Required record IDs, supported file layout and reconciliation results

Review inference: Compare source inventory, error mode and imported content instead of relying only on the terminal status.

Suggested review condition: Do not accept complete migration from Completed when tolerated errors or missing namespaces remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Which source records failed and whether exported/imported contents agree are not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Detect incomplete data migration before relying on the new retrieval index.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Completeness or exact equivalence of all source records from import status
  • Which source records failed and whether exported/imported contents agree are not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pinecone namespaces: Data separation and tenant routing

Question: Does one namespace per tenant prove an application always selects the authorised tenant?

Pinecone documents separate namespaces and requires data operations to target a namespace. That describes storage and query scope. The buyer still needs evidence that its application maps the authenticated tenant to the correct namespace; the documentation does not inspect that mapping.

Source: Pinecone namespaces and tenant routing. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Creating tenant namespaces proves application-level authorisation is correct.

Buyer evidence still required

  • Namespace assignment for each intended tenant
  • How authenticated tenant identity selects the request namespace
  • Authorised tests of cross-tenant rejection in the buyer application

Suggested review condition: Do not substitute storage separation for evidence of correct application routing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck namespace mapping, application identity handling and index changes.

Optional saved evidence: Save the separation-versus-routing distinction for a retrieval-system procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pinecone project deletion: Dependencies and accepted-state evidence

Question: Does a project deletion request prove every Pinecone resource was already removed?

The versioned API requires associated indexes, assistants, backups and collections to be deleted before deleting a project. Its documented response is acceptance of the deletion request. Record dependency removal and subsequent state separately; an accepted response alone is not a complete erasure attestation.

Source: Pinecone Delete project API 2025-04. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An accepted project deletion proves all underlying data and resources were erased.

Buyer evidence still required

  • Exact project identity and API version.
  • Dependency inventory and authorised removal evidence.
  • Subsequent project state and applicable retention terms.

Suggested review condition: Do not treat request acceptance as a comprehensive erasure certificate.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Project identity, API version, dependencies and post-request state

Optional saved evidence: Save the dependency and completion evidence needed before asserting project removal.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

pip: Hash-checking needs a complete pinned dependency set

Question: Does hashing only the top-level Python requirement establish a fully hash-checked installation?

With require-hashes, pip requires pinned requirements and local hashes for every dependency as well as top-level packages. A remotely supplied index hash does not satisfy that local-trust requirement. The captured pip documentation also distinguishes disabling global hash enforcement from strict mode.

Source: Secure installs - pip documentation v26.2.1. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does hashing only the top-level Python requirement establish a fully hash-checked installation?

Buyer evidence still required

  • pip version and require-hashes invocation.
  • Complete pinned dependency file.
  • Trusted local hashes for permitted distribution files.

Suggested review condition: Do not claim full dependency integrity coverage when any dependency or distribution lacks a trusted required hash.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. pip version and require-hashes invocation. Complete pinned dependency file. Trusted local hashes for permitted distribution files.

Optional saved evidence: Check whether an agent dependency install is actually bound to reviewed artifacts.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Malware clearance, publisher trust or security of the approved package contents
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PlanetScale MCP: Branch permissions and query safeguards

Question: Do PlanetScale query safeguards make full-access agent queries harmless?

No. PlanetScale documents branch-specific read-only or full-access permissions and particular query safeguards. These are bounded checks, not proof that every permitted query is appropriate. Review the branch, action and intended effect; a prompt to seek confirmation is not evidence that a person approved.

Source: PlanetScale MCP OAuth and database operations. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted OAuth server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

PlanetScale hosts the MCP service.

Documented by publisher. PlanetScale MCP OAuth and database operations

Purpose

Inspect database structure and performance and execute permitted queries.

Documented by publisher. PlanetScale MCP OAuth and database operations

Read capability

Reads schemas, Insights and optional billing information.

Documented by publisher. PlanetScale MCP OAuth and database operations

Write capability

Write queries are available if granted; certain destructive patterns are blocked.

Documented by publisher. PlanetScale MCP OAuth and database operations

Authentication

OAuth with configurable permissions.

Documented by publisher. PlanetScale MCP OAuth and database operations

Permission surface

Production and development branch access can be read-only or full-access.

Documented by publisher. PlanetScale MCP OAuth and database operations

Data leaving the environment

Query results and performance context reach the assistant.

Review inference. PlanetScale MCP OAuth and database operations

Failure modes to consider

A guarded query can still target the wrong branch or records.

Review inference. PlanetScale MCP OAuth and database operations

Unknowns and applicability

The actual grant and any human confirmation are unverified.

Not established

Suggested refusal or clarification condition

Require the intended branch and authorised effect; do not label full access harmless.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck branch grants, query protections and tool additions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the specific branch and safeguard distinctions used in a query-access review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Playwright clicks and server acceptance

Question: Does a successful Playwright click establish that a server accepted the intended business action?

Playwright auto-waits for actionability checks such as visibility, stability, event reception and enabled state. Its navigation guide describes a hydration case where an enabled button is clicked before listeners attach and the click has no effect. Passing the click operation therefore does not itself establish a server-side business result.

Source: Auto-waiting | Playwright. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a successful Playwright click establish that a server accepted the intended business action?

Buyer evidence still required

  • Target control and intended action identity
  • Relevant response or operation identifier
  • Observed server-side completion or rejection state

Review inference: Reconcile the click with a task-specific response and resulting state.

Suggested review condition: Do not close the task solely because locator.click completed without error.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual server result and any downstream side effects are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid reporting an approved or completed action that never reached the application.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed business completion from browser actionability
  • The actual server result and any downstream side effects are unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Playwright MCP: Browser identity and session boundaries

Question: Does an isolated Playwright MCP browser session prevent privileged web actions or data disclosure?

Playwright MCP documents persistent, isolated and existing-browser session modes. Isolation concerns session state; it does not make authenticated web actions read-only. Its origin filters explicitly exclude redirects from their protection, and the project states that MCP itself is not a security boundary. Review browser identity, destinations and task authorization separately.

Source: Playwright MCP profiles and security boundary. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Microsoft's Playwright MCP in a local/operator-run browser setup; installed package version, launch settings and browser state were not inspected.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Microsoft publishes Playwright MCP; the organization running the process operates the browser connection.

Documented by publisher. Playwright MCP profiles and security boundary; Playwright authentication state

Purpose

Inspect and interact with web pages through browser automation.

Documented by publisher. Playwright MCP profiles and security boundary; Playwright authentication state

Read capability

Page content and browser-visible information under the active session.

Documented by publisher. Playwright MCP profiles and security boundary; Playwright authentication state

Write capability

Browser interactions can submit forms and change remote state using the session's authority.

Documented by publisher. Playwright MCP profiles and security boundary; Playwright authentication state

Authentication

Websites use the browser's authentication state; isolated mode can load saved state. No hosted vendor OAuth login is assumed for local stdio.

Documented by publisher. Playwright MCP profiles and security boundary; Playwright authentication state

Permission surface

Origin filters are documented as incomplete boundaries. Browser identity and surrounding runtime/network controls require separate review.

Documented by publisher. Playwright MCP profiles and security boundary; Playwright authentication state

Data leaving the environment

The browser contacts websites and returns content to the MCP client; a local browser process does not establish local-only model processing.

Review inference. Playwright MCP profiles and security boundary; Playwright authentication state

Failure modes to consider

Reusing a privileged browser session; treating isolation as read-only authority; sharing a saved state file that enables impersonation.

Review inference. Playwright MCP profiles and security boundary; Playwright authentication state

Unknowns and applicability

Installed release, loaded cookies, browser permissions, network enforcement and client data handling.

Not established

Suggested refusal or clarification condition

Use an authorized session and destination set; stop before form submissions outside the task and keep saved auth state out of evidence exports.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save browser-state and destination limitations considered when choosing an automation tool.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Playwright saved authentication coverage

Question: Does Playwright saved storage state automatically preserve every authentication mechanism?

The current authentication guide covers cookies, local storage, IndexedDB and passkey-based authentication, but separately states that Playwright has no API to persist session storage. It supplies a custom save/load example for that case. Supported mechanisms and relevant storage-state options must be checked for the installed version.

Source: Authentication | Playwright. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Playwright saved storage state automatically preserve every authentication mechanism?

Buyer evidence still required

  • Installed Playwright version and storage-state options
  • Application authentication storage mechanisms
  • Restored-session checks for the intended account

Review inference: Treat a saved state file as a scoped authentication snapshot rather than a complete browser identity backup.

Suggested review condition: Decline a complete-authentication-restoration claim without mechanism-specific verification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The application’s actual authentication storage and restoration result are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify missing session material before relying on a restored automation login.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal browser-session persistence from a storage-state file
  • The application’s actual authentication storage and restoration result are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Playwright: Request routes have a Service Worker boundary

Question: Does browserContext.route establish that every browser request passes through an agent's declared filter?

Playwright documents that browserContext.route does not intercept requests already intercepted by a Service Worker. It recommends blocking Service Workers when using request interception. A route handler declaration alone cannot establish complete network mediation for the browser context.

Source: Playwright: BrowserContext API. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does browserContext.route establish that every browser request passes through an agent's declared filter?

Buyer evidence still required

  • Context Service Worker setting.
  • Installed routing rules and their scope.
  • Separately observed network behaviour.

Suggested review condition: Record this interception boundary before relying on a route handler as an enforced egress control.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Browser context options, route handlers and Service Worker configuration.

Optional saved evidence: Does browserContext.route establish that every browser request passes through an agent's declared filter?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Playwright: Saved browser state carries account access

Question: Can a saved Playwright authentication-state file be treated as harmless test configuration?

Playwright warns that saved browser state can contain cookies and headers usable to impersonate the account. Loading that state starts a context already authenticated. Its custody and account scope therefore belong in the authority review, not merely the browser settings inventory.

Source: Playwright: Authentication. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a saved Playwright authentication-state file be treated as harmless test configuration?

Buyer evidence still required

  • Account and origins represented without exposing secrets.
  • Storage and access controls for saved state.
  • Authorised actions for the reused account.

Suggested review condition: Treat reusable authentication state as credential material and keep its contents out of public evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. State-file custody, account identity, target origins and intended actions.

Optional saved evidence: Can a saved Playwright authentication-state file be treated as harmless test configuration?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

provenance non claim record

PLS Provenance Seal — Existence, Authorship and Integrity Only

Question: What does a VAREXIS provenance seal assert?

Public-safe record clarifying the provenance seal boundary.

Claim boundaries
  • truth
  • correctness
  • valuation
  • certification
  • legal enforceability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

External documentation review

Plugin component inventory includes hooks/modules/servers beyond visible skill

Question: Does approving a plugin's visible skill cover its hooks and MCP servers?

Claude Code documents plugins containing skills, agents, lifecycle hooks, JavaScript hook modules and MCP servers. These components can expose capabilities beyond the visible slash command.

Source: Anthropic primary documentation: claude code plugins. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does approving a plugin's visible skill cover its hooks and MCP servers?

Buyer evidence still required

  • plugin manifest
  • component inventory
  • hook commands/modules
  • MCP definitions
  • enablement scope

Review inference: Does approving a plugin's visible skill cover its hooks and MCP servers? Review the entire plugin component inventory and enabled configuration; a skill-level checklist cannot attest to unreviewed hooks or servers. Plugin component inventory includes hooks/modules/servers beyond visible skill. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Review the entire plugin component inventory and enabled configuration; a skill-level checklist cannot attest to unreviewed hooks or servers.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. MCP servers

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Review the entire plugin component inventory and enabled configuration; a skill-level checklist cannot attest to unreviewed hooks or servers.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Port MCP: Read-only selection and connected-tool scope

Question: Is Port MCP automatically read-only when added from an IDE?

The documented read-only header defaults to off, allowing tools according to the user's permissions. Turning it on hides write tools. Enabled external connectors introduce their own identities and operations, so a Port login alone does not establish the scope of every upstream action.

Source: Port MCP installation and read-only mode. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted platform server with optional external connectors

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Port operates the platform server; upstream connectors have separate operators.

Documented by publisher. Port MCP installation and read-only mode; Port external MCP connectors

Purpose

Query platform context and run permitted platform/connector actions.

Documented by publisher. Port MCP installation and read-only mode; Port external MCP connectors

Read capability

Catalog context and enabled upstream data.

Documented by publisher. Port MCP installation and read-only mode; Port external MCP connectors

Write capability

Permitted actions and connected write tools can change state.

Documented by publisher. Port MCP installation and read-only mode; Port external MCP connectors

Authentication

User OAuth in the reviewed installation flow.

Documented by publisher. Port MCP installation and read-only mode; Port external MCP connectors

Permission surface

Port identity, read-only header and upstream grants.

Documented by publisher. Port MCP installation and read-only mode; Port external MCP connectors

Data leaving the environment

Requests can reach Port and the selected upstream provider.

Review inference. Port MCP installation and read-only mode; Port external MCP connectors

Failure modes to consider

A default full tool set or unexpected connector changes the boundary.

Review inference. Port MCP installation and read-only mode; Port external MCP connectors

Unknowns and applicability

Buyer connectors, credentials and approval controls are unknown.

Not established

Suggested refusal or clarification condition

Review the exact upstream action before extending catalog discovery.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Read-only mode, connector authentication and exposed action set.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the platform and upstream authority checks behind an integration decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PostgreSQL RLS: Effective roles and policy exceptions

Question: Does enabling row-level security constrain every database identity?

No. PostgreSQL documents exceptions for superusers, BYPASSRLS roles and normally table owners; owners can opt into forced row security. Whole-table operations also have distinct treatment. Review the actual role and operation before using RLS enablement as evidence of tenant isolation.

Source: PostgreSQL row security and privileged role exceptions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An RLS-enabled table restricts every caller to tenant rows.

Buyer evidence still required

  • Effective connecting role and relevant role attributes
  • Table ownership, force setting and policy definitions
  • Authorised tests using the application identity and operation type

Suggested review condition: Do not accept universal isolation from RLS enablement alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck role grants, ownership, policies and database upgrades.

Optional saved evidence: Preserve the role and policy distinctions for a database-access review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PostgreSQL: Acknowledged commit before durable storage

Question: Can PostgreSQL report a successful asynchronous commit that is lost in a subsequent crash?

PostgreSQL 18 asynchronous commit returns success after logical completion but before the transaction WAL is flushed to durable storage. A crash in that interval can lose the recent transaction while preserving database consistency. The documentation warns against relying on such an acknowledgement for external actions that require the transaction to be remembered.

Source: PostgreSQL: Asynchronous commit. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can PostgreSQL report a successful asynchronous commit that is lost in a subsequent crash?

Buyer evidence still required

  • Effective commit and durability settings for the transaction.
  • Commit response, crash timeline and available WAL or recovery evidence.
  • Post-recovery database state reconciled with dependent external effects.

Suggested review condition: Decline crash-durable completion claims without the applicable commit settings and recovered-state evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Effective commit and durability settings for the transaction. Commit response, crash timeline and available WAL or recovery evidence. Post-recovery database state reconciled with dependent external effects.

Optional saved evidence: An agent may produce an irreversible external effect based on a database success that does not survive recovery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof of durable storage, replica durability or validation of buyer database settings
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PostgreSQL: Crash recovery can replay logical changes

Question: Does a crash-safe logical replication slot guarantee each change reaches a consumer only once?

PostgreSQL persists a logical slot position at checkpoints. After a crash it can return to an earlier position and resend recent changes. Clients are responsible for handling repeated messages; a slot does not know the receiver's processing state.

Source: PostgreSQL 18: Logical decoding concepts. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a crash-safe logical replication slot guarantee each change reaches a consumer only once?

Buyer evidence still required

  • Slot and last acknowledged log sequence position.
  • Consumer durable processing checkpoint.
  • Crash-recovery replay and duplicate-handling evidence.

Suggested review condition: Reconcile database replay position with consumer effects before asserting unique processing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. PostgreSQL version, logical slot position, crash window and consumer progress.

Optional saved evidence: Does a crash-safe logical replication slot guarantee each change reaches a consumer only once?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PostgreSQL: Prepared transactions awaiting a decision

Question: Does PostgreSQL PREPARE TRANSACTION mean a multi-system action has committed?

PostgreSQL 18 PREPARE TRANSACTION stores transaction state for two-phase commit; a later COMMIT PREPARED or ROLLBACK PREPARED resolves it. Prepared transactions retain their locks and should be closed promptly by an external transaction manager. A prepared state is an unresolved participant decision, not proof of a globally completed action.

Source: PostgreSQL: PREPARE TRANSACTION. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does PostgreSQL PREPARE TRANSACTION mean a multi-system action has committed?

Buyer evidence still required

  • Prepared transaction identifier, participant list and pg_prepared_xacts observations.
  • Transaction-manager decision record and participant commit or rollback results.
  • Retained locks, unresolved participants and authorized recovery ownership.

Suggested review condition: Decline global-completion claims or guessed resolution while the authoritative transaction-manager decision is missing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Prepared transaction identifier, participant list and pg_prepared_xacts observations. Transaction-manager decision record and participant commit or rollback results. Retained locks, unresolved participants and authorized recovery ownership.

Optional saved evidence: An abandoned coordinator can leave blocked resources and an unresolved commit decision requiring deliberate recovery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic distributed recovery or authority to force commit or rollback
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PostgreSQL: Serialization failures and transaction retries

Question: After a PostgreSQL serialization failure, is retrying only the last SQL statement sufficient?

PostgreSQL 18 directs applications to retry the complete transaction after a serialization failure, including the logic that chose statements and values. SQLSTATE 40001 identifies that failure. Other errors, such as unique violations, can be persistent, and a retry does not guarantee eventual completion.

Source: PostgreSQL 18: Serialization Failure Handling. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: After a PostgreSQL serialization failure, is retrying only the last SQL statement sufficient?

Buyer evidence still required

  • Isolation level, SQLSTATE and complete failed transaction boundary.
  • Application decision logic and new attempt identity for the whole retry.
  • Final commit result and separate reconciliation of any external effects.

Suggested review condition: Decline recovery-complete claims from a statement-only replay; require the appropriate full transaction retry and final outcome evidence, without blindly retrying persistent errors.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Isolation level, SQLSTATE and complete failed transaction boundary. Application decision logic and new attempt identity for the whole retry. Final commit result and separate reconciliation of any external effects.

Optional saved evidence: Agent recovery must preserve the transaction decision boundary and avoid treating every database error as an interchangeable transient failure.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic retry correctness, guaranteed progress or rollback and deduplication of effects outside the database transaction
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PostHog MCP: Analytics actions and AI usage costs

Question: Does free PostHog MCP access mean every operation has no additional usage cost?

No. PostHog says MCP access and calls are free, while some tools invoke LLMs internally and may incur PostHog AI spend. The connector supports reads and writes across products. Review AI processing settings, the selected project and the intended action separately from the connection price.

Source: PostHog MCP regional routing, broad actions and AI spend. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted regional server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

PostHog provides the hosted MCP service.

Documented by publisher. PostHog MCP regional routing, broad actions and AI spend

Purpose

Query analytics and act on supported PostHog products.

Documented by publisher. PostHog MCP regional routing, broad actions and AI spend

Read capability

Reads analytics, errors and related project context.

Documented by publisher. PostHog MCP regional routing, broad actions and AI spend

Write capability

Supports product changes including feature-flag and destination operations.

Documented by publisher. PostHog MCP regional routing, broad actions and AI spend

Authentication

The buyer authentication grant is not established by the reviewed overview.

Not established. PostHog MCP regional routing, broad actions and AI spend

Permission surface

Effective buyer action permissions and spend controls remain unverified.

Not established. PostHog MCP regional routing, broad actions and AI spend

Data leaving the environment

Project results reach the client; some tools also use internal AI processing.

Review inference. PostHog MCP regional routing, broad actions and AI spend

Failure modes to consider

A free-connection claim can be mistaken for zero-cost AI execution.

Review inference. PostHog MCP regional routing, broad actions and AI spend

Unknowns and applicability

Buyer usage limits, AI processing approval and identity rights are unknown.

Not established

Suggested refusal or clarification condition

Clarify action and spending authority before AI-powered or mutating work.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck AI billing, processing settings and enabled product tools.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the documented cost and action distinctions for analytics-agent approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Postman MCP: Region, credentials and tool-set scope

Question: Which Postman MCP configuration fits API discovery without granting unnecessary workspace changes?

Postman documents separate tool configurations and local or remote servers. Minimal is a smaller tool set, not a stated read-only guarantee. US remote authentication supports OAuth; the EU remote and local variants use an API key. Match the region, identity and specific tools to the task before connecting.

Source: Postman MCP variants and tool sets. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Publisher remote and local variants; US and EU authentication differ

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Postman publishes remote and local MCP variants.

Documented by publisher. Postman MCP variants and tool sets

Purpose

The integration manages API workspaces, collections, specifications and related resources.

Documented by publisher. Postman MCP variants and tool sets

Read capability

Documentation search and API-definition or workspace context depend on the selected configuration.

Documented by publisher. Postman MCP variants and tool sets

Write capability

Management tools can create or change collections, workspaces and environments.

Documented by publisher. Postman MCP variants and tool sets

Authentication

OAuth is supported on the US remote service; EU remote and local servers require a Postman API key.

Documented by publisher. Postman MCP variants and tool sets

Permission surface

Minimal, Code, Full, Learn and Context Graph expose different tool sets; Context Graph requires team enablement.

Documented by publisher. Postman MCP variants and tool sets

Data leaving the environment

Internal API definitions may be passed to the client and its model. A local MCP process still interacts with Postman services.

Review inference. Postman MCP variants and tool sets

Failure modes to consider

Confusing Minimal with read-only, or selecting the wrong region and authentication flow, can invalidate a connection review.

Review inference. Postman MCP variants and tool sets

Unknowns and applicability

Account rights, chosen tools, connected API secrets and downstream client retention are unverified.

Not established

Suggested refusal or clarification condition

Confirm region and specific operations before accessing internal definitions or allowing workspace mutations.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck tool configuration, account region, credentials and workspace membership.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the region and tool-set assumptions behind an API discovery connection.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Prefect MCP: Read-only tools and wider agent authority

Question: Does read-only Prefect MCP make the whole agent read-only?

The documented MCP tools inspect runs, logs and infrastructure without mutations. A local server can inherit the active Prefect profile, while the hosted connection uses selected Cloud workspaces. An agent with separate terminal or SDK access can still change Prefect resources; the MCP tool boundary does not restrict those other capabilities.

Source: Prefect MCP setup and tools. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; deployed buyer configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Prefect publishes the server and offers a hosted Cloud connection.

Documented by publisher. Prefect MCP setup and tools; Prefect MCP server repository

Purpose

Inspect workflow state and diagnose failures.

Documented by publisher. Prefect MCP setup and tools; Prefect MCP server repository

Read capability

Runs, logs, deployment metadata and documentation.

Documented by publisher. Prefect MCP setup and tools; Prefect MCP server repository

Write capability

No mutations through the documented MCP tools.

Documented by publisher. Prefect MCP setup and tools; Prefect MCP server repository

Authentication

Hosted OAuth or local Prefect profile credentials.

Documented by publisher. Prefect MCP setup and tools; Prefect MCP server repository

Permission surface

Authorized workspaces and the selected underlying identity determine access.

Documented by publisher. Prefect MCP setup and tools; Prefect MCP server repository

Data leaving the environment

Execution logs and metadata reach the agent client.

Review inference. Prefect MCP setup and tools; Prefect MCP server repository

Failure modes to consider

Local profile confusion or separate CLI authority can undermine a read-only workflow.

Review inference. Prefect MCP setup and tools; Prefect MCP server repository

Unknowns and applicability

Actual workspace selection, log content and other agent capabilities are unverified.

Not established

Suggested refusal or clarification condition

Confirm the target and separate write capabilities before authorizing diagnostics.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Beta tool surface, profile selection and independent CLI or SDK grants.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve a diagnostic-access review without confusing a read-only connector with a restricted agent.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Presidio: Detection coverage and residual information

Question: Does a clean Presidio result prove a document contains no sensitive information?

Presidio combines configurable recognizers and can use external detection models. Its maintainers explicitly warn that automated detection does not find all sensitive information. The selected recognizers, languages and input types need buyer validation; a clean result cannot alone establish complete anonymization or permission to disclose the document.

Source: Presidio: Detection scope and limitations. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: No detected entities means a document is safe to disclose.

Buyer evidence still required

  • Recognizer and model configuration.
  • Representative language and input-type coverage.
  • Residual-data review and authorized disclosure scope.

Suggested review condition: Require additional protections and relevant coverage evidence before relying on complete removal.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Presidio revision, recognizers, models, languages, input types and disclosure purpose.

Optional saved evidence: Retain the detection limits used when reviewing a privacy-processing workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Prisma MCP: Workspace actions and CLI guardrail limits

Question: Do Prisma CLI destructive-command safeguards also protect MCP operations?

Prisma explicitly limits those safeguards to CLI commands. Its MCP server exposes workspace operations, and the documentation directs users to review approvals in the AI client. A CLI safety claim therefore does not establish the approval behaviour of an MCP call.

Source: Prisma MCP workspace access and resource management. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted workspace server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Prisma provides the hosted MCP integration.

Documented by publisher. Prisma MCP workspace access and resource management

Purpose

Manage Prisma workspace resources from an assistant.

Documented by publisher. Prisma MCP workspace access and resource management

Read capability

Reads database and deployment information.

Documented by publisher. Prisma MCP workspace access and resource management

Write capability

Documents database, Compute and storage management operations.

Documented by publisher. Prisma MCP workspace access and resource management

Authentication

Prisma account authorisation with workspace selection.

Documented by publisher. Prisma MCP workspace access and resource management

Permission surface

The selected workspace and client approval policy need review; CLI safeguards do not apply to MCP.

Documented by publisher. Prisma MCP workspace access and resource management

Data leaving the environment

Requested resource data returns to the connected AI client.

Review inference. Prisma MCP workspace access and resource management

Failure modes to consider

Assuming CLI safeguards cover MCP can leave a change unreviewed.

Review inference. Prisma MCP workspace access and resource management

Unknowns and applicability

Effective workspace rights and client approval rules are unknown.

Not established

Suggested refusal or clarification condition

Require task authority and the actual MCP approval policy before a destructive operation.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck MCP capabilities and client approval settings.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the CLI-versus-MCP control distinction for an onboarding review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Private-beta ingestion retains raw transcript as well as extracted facts

Question: Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The reviewed beta documentation says raw messages are stored verbatim alongside extracted memories and are also searched during recall.

Source: Cloudflare primary documentation: cloudflare memory how. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation?

Buyer evidence still required

  • namespace/profile/session IDs
  • ingestion payload scope
  • transcript and extracted-memory inventory
  • retention policy

Review inference: Does Cloudflare Agent Memory retain only extracted facts after ingesting a conversation? Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation. Private-beta ingestion retains raw transcript as well as extracted facts. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Raw conversation messages are always stored verbatim

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not approve a facts-only retention claim from an extraction result; inventory raw messages as a separate retained representation. Private beta access and current feature applicability require separate confirmation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Profile and destination permissions have different evaluation context

Question: Can a Bedrock inference-profile exception bypass a denied originating Region?

For Geographic cross-Region inference, AWS evaluates the profile and foundation-model resources in the source and candidate destination Regions. The InferenceProfileArn condition is present for foundation-model evaluations, but absent for the profile-resource evaluation. A destination-region exception using that condition cannot bypass the originating-call Region restriction.

Source: Geographic cross-Region inference - Amazon Bedrock. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a Bedrock inference-profile exception bypass a denied originating Region?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Review source and destination authorization separately; do not treat a profile-condition exception as universal authorization or assume denied destinations are silently removed.

Suggested review condition: Review source and destination authorization separately; do not treat a profile-condition exception as universal authorization or assume denied destinations are silently removed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. Service Control Policy requirements for Geographic cross-Region inference

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Review source and destination authorization separately; do not treat a profile-condition exception as universal authorization or assume denied destinations are silently removed.
  • A scoped profile exception can permit destination model evaluations while ordinary Region restrictions remain for other services and the originating call.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Provider preference is not a provider restriction

Question: Does Vercel AI Gateway provider order restrict every fallback to that list?

Vercel documents order as a preference: other eligible providers can still be tried. The only list removes providers outside it; if none of its providers can serve the model, the request fails. Review the effective restriction as well as the order.

Source: AI Gateway Provider Routing and Fallbacks. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Vercel AI Gateway provider order restrict every fallback to that list?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Refuse to infer a provider allowlist from order alone; bind the actual request and effective team policy.

Suggested review condition: Refuse to infer a provider allowlist from order alone; bind the actual request and effective team policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ## Provider filtering, ordering, and sorting

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to infer a provider allowlist from order alone; bind the actual request and effective team policy.
  • A request with both order and an applicable only list can restrict the pool; an order setting is not inherently unrestricted when another control applies.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Pseudonymization: Reversible tokens and key authority

Question: Does tokenizing data with Sensitive Data Protection permanently erase the original meaning?

AES-SIV and format-preserving encryption support re-identification with the required key and context. HMAC-SHA-256 is a separate one-way option. Deterministic transformations can preserve links between records. Review the selected method and who can re-identify or correlate values; tokenization alone is not proof of erasure.

Source: Google Sensitive Data Protection: Pseudonymization. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: All pseudonymization is irreversible deletion.

Buyer evidence still required

  • Exact transformation and context configuration.
  • Key custody and re-identification permissions.
  • Cross-record linkage and retained original copies.

Suggested review condition: Do not describe reversible tokenization as erasure or assume transformed records cannot be linked.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Transformation, structured or unstructured input, key custody, context and recipient authority.

Optional saved evidence: Preserve the reversibility and linkage facts used in a data-sharing review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pub/Sub exactly-once: Acknowledgement and regional scope

Question: Does Pub/Sub exactly-once delivery cover every subscription and external action?

The documented feature applies to pull subscriptions within a cloud region. Successful acknowledgement prevents redelivery of that message, while expired acknowledgement deadlines can lead to a new valid delivery. It does not establish an atomic transaction with an external business system or deduplicate separate publisher messages.

Source: Pub/Sub exactly-once delivery. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Exactly-once delivery guarantees every business effect happens once globally.

Buyer evidence still required

  • Subscription type and feature enablement.
  • Subscriber region and acknowledgement results.
  • Publisher identity and downstream commit handling.

Suggested review condition: Require the regional, subscription and business-transaction scope before accepting an exactly-once claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Subscription mode, region, acknowledgement handling, publisher IDs and downstream transaction.

Optional saved evidence: Preserve the precise delivery guarantee and excluded business effects for supplier evaluation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pub/Sub: Ordering is scoped and can include redelivery

Question: Does Pub/Sub message ordering provide one global, duplicate-free agent action sequence?

Pub/Sub orders messages within an ordering key under its documented regional and subscription conditions, not across keys. Redelivery can also replay later messages for the same key, including acknowledged ones; dead-letter handling adds further qualifications.

Source: Google Cloud Pub/Sub: Order messages. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does Pub/Sub message ordering provide one global, duplicate-free agent action sequence?

Buyer evidence still required

  • Key assignment and regional publishing scope.
  • Subscription ordering and dead-letter settings.
  • Acknowledgement, redelivery and downstream processing evidence.

Suggested review condition: Preserve per-key order and replay uncertainty; do not infer global chronology or unique execution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Ordering keys, publish region, subscription ordering and dead-letter configuration.

Optional saved evidence: Does Pub/Sub message ordering provide one global, duplicate-free agent action sequence?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Public row-scale reduction: Applicability boundary

Question: Does the public row-scale reduction record establish broad workload applicability?

The public row-scale source supports bounded scale interest. Its source excludes broad workload applicability.

Derived from BDAS 163M-Row Public Reduction — Public-Scale Summary. No new experiment or validation is claimed.

Claim boundaries
  • broad workload applicability
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pulumi MCP: Organisation selection and Neo actions

Question: Can a Pulumi inventory question start paid infrastructure work?

Most tools retrieve information or instructions, but the Neo bridge can start billed tasks and pass approvals that let Neo change infrastructure. The documentation also describes fallback organisation selection. Verify the organisation and enabled tools before treating the connection as inventory-only.

Source: Pulumi MCP authentication and organisation selection. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted Pulumi MCP with optional Neo bridge

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Pulumi operates the hosted server.

Documented by publisher. Pulumi MCP authentication and organisation selection

Purpose

Infrastructure discovery, documentation and Neo coordination.

Documented by publisher. Pulumi MCP authentication and organisation selection

Read capability

Stack, resource, policy and organisation information.

Documented by publisher. Pulumi MCP authentication and organisation selection

Write capability

Neo tasks and approvals can lead to infrastructure changes or pull requests.

Documented by publisher. Pulumi MCP authentication and organisation selection

Authentication

Pulumi access token through browser or header authentication.

Documented by publisher. Pulumi MCP authentication and organisation selection

Permission surface

Token role and client tool permissions; organisation selection requires checking.

Documented by publisher. Pulumi MCP authentication and organisation selection

Data leaving the environment

Cloud resource information can reach the connected model.

Review inference. Pulumi MCP authentication and organisation selection

Failure modes to consider

An unexpected organisation or Neo task may change the intended scope.

Review inference. Pulumi MCP authentication and organisation selection

Unknowns and applicability

The buyer token, selected organisation and Neo limits were not inspected.

Not established

Suggested refusal or clarification condition

Clarify the target and authority before starting or approving Neo work.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Organisation fallback, Neo capability and billing changes.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve why an inventory-only approval excluded Neo work and which organisation needed checking.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Pulumi secrets: Encrypted state does not prevent runtime disclosure

Question: Does Pulumi secret encryption prove a value cannot appear in application logs?

Pulumi encrypts marked secret values in state and tracks their propagation, but runtime callbacks receive plaintext and can expose it elsewhere. The documentation also excludes resource IDs from secret encryption. Review runtime handling and value placement before accepting a blanket no-disclosure claim.

Source: Pulumi secret encryption and runtime disclosure. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: State encryption prevents every disclosure of a secret value.

Buyer evidence still required

  • Evidence that the value is marked secret in state.
  • Review of callbacks, logs and downstream output destinations.
  • Whether sensitive material appears in a resource identifier.

Suggested review condition: Do not extend a state-encryption claim to unevidenced runtime channels.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Output marking, callback changes and identifier handling.

Optional saved evidence: Save which runtime and identifier checks remain necessary beyond encrypted state.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

PUMP-E1: Promotion boundary

Question: Can challenged PUMP-E1 evidence be promoted as a safe result?

PUMP-E1 remains a challenged negative record in the public index. Its source lists safe promotion as not demonstrated.

Derived from BDAS PUMP-E1 — Challenged Negative Evidence. No new experiment or validation is claimed.

Claim boundaries
  • safe promotion
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

PUMP-E2C: Customer savings boundary

Question: Can a buyer infer customer savings from PUMP-E2C?

The public PUMP-E2C record supports a narrow selective-execution claim on consumed evidence. It lists customer savings as not demonstrated.

Derived from BDAS PUMP-E2C — Consumed Engineering Selective Execution Evidence. No new experiment or validation is claimed.

Claim boundaries
  • customer savings
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

PUMP-E2C: Fresh holdout boundary

Question: Can PUMP-E2C be cited as a fresh holdout result?

PUMP-E2C is published as historically consumed engineering evidence. Its public source explicitly excludes fresh holdout validation.

Derived from BDAS PUMP-E2C — Consumed Engineering Selective Execution Evidence. No new experiment or validation is claimed.

Claim boundaries
  • fresh holdout validation
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

PUMP-E2C: Hardware contract boundary

Question: Can PUMP-E2C support a hardware-mismatched consumer contract?

The PUMP-E2C public source excludes a hardware-mismatched consumer contract. Its narrow supported claim must retain the stated evidence scope.

Derived from BDAS PUMP-E2C — Consumed Engineering Selective Execution Evidence. No new experiment or validation is claimed.

Claim boundaries
  • hardware-mismatched consumer contract
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

PUMP-E2C: Score reconstruction boundary

Question: Does the PUMP-E2C public record support full score reconstruction?

The PUMP-E2C public source excludes full score reconstruction. Public and paid handling preserve the protected implementation boundary.

Derived from BDAS PUMP-E2C — Consumed Engineering Selective Execution Evidence. No new experiment or validation is claimed.

Claim boundaries
  • full score reconstruction
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview disposition approval and deletion timing

Question: Does approving a Purview disposition review prove immediate deletion of every copy of the item?

Purview separates disposition approval from permanent deletion: its documented timeline allows up to 15 days after final approval for eligible content. Disposed-item information relies on searchable audit events. Approval and the recorded deletion event are different evidence, and the documented workflow does not attest to every independently exported copy.

Source: Disposition of content | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does approving a Purview disposition review prove immediate deletion of every copy of the item?

Buyer evidence still required

  • Final disposition stage, approval time and item identity
  • Enabled audit collection and corresponding deletion evidence
  • Inventory of exports, backups and other independently held copies

Review inference: Keep approval, item-deletion evidence and the wider copy inventory as distinct checkpoints.

Suggested review condition: Do not accept an approval event alone as an immediate or universal erasure attestation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual deletion events and independently held replicas are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Separate authorisation to dispose from evidence that the declared deletion boundary was completed.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified erasure of all replicas from a disposition decision
  • Actual deletion events and independently held replicas are unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview DLP: Simulated matches and enforced controls

Question: Does a Purview DLP simulation alert prove the attempted transfer was blocked?

Simulation runs policies without actual enforcement and reports matched items and alerts separately. It helps evaluate policy impact but does not prove that a transfer was prevented. Procurement should distinguish simulation evidence from the active policy state and observed enforcement in the intended workload.

Source: Microsoft Purview: DLP simulation mode. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A simulated DLP match establishes successful prevention.

Buyer evidence still required

  • Policy mode and relevant workload scope.
  • Separate simulation and enforced-policy results.
  • Dated evidence of actual blocking when claimed.

Suggested review condition: Keep simulated matches labelled as simulation; request enforcement evidence for a blocking claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Policy version, mode, workload, dates and observed enforcement events.

Optional saved evidence: Save the distinction between policy evaluation and operational prevention.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview eDiscovery count reconciliation

Question: Does a Purview eDiscovery estimate or successful process status prove that the exported evidence is complete?

Purview process reports distinguish estimates from exported or collected items. Summary information explains count changes, and item reports identify retrieval exceptions. Differences can arise from attachments, versions, conversations and duplicates as well as errors; equality of headline counts is not a substitute for reconciliation.

Source: Process reports in eDiscovery | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Purview eDiscovery estimate or successful process status prove that the exported evidence is complete?

Buyer evidence still required

  • Search configuration and expected scope
  • Summary and item reports
  • Exported item inventory and unresolved exceptions

Review inference: Reconcile item identities, count adjustments and errors against the intended evidence population.

Suggested review condition: Do not accept completeness from an estimate or process status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual missing items and completeness of the buyer’s evidence population are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify unexplained evidence gaps before handing off a legal-records export.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Legal evidential sufficiency or independently verified chain of custody
  • The actual missing items and completeness of the buyer’s evidence population are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview event retention before its trigger

Question: Does applying an event-based Purview record label start its retention countdown before the event is matched?

Purview event-based retention links labels and event types to a triggering event, with asset IDs identifying relevant documents. A declared record whose triggering event has not happened is retained indefinitely. The configured duration therefore does not by itself establish a calendar deletion deadline from the date the label was applied.

Source: Start retention when an event occurs | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does applying an event-based Purview record label start its retention countdown before the event is matched?

Buyer evidence still required

  • Record label, event type and asset ID
  • Created event and matched-document evidence
  • Trigger date, configured duration and disposition requirements

Review inference: Verify the event association and actual trigger date before calculating the retention end.

Suggested review condition: Refuse a calculated expiry date when the required event-to-record association is missing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s event matches and actual trigger dates are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Find records whose exit date is undefined because the required business event was never associated.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A retention countdown based solely on label application
  • The buyer’s event matches and actual trigger dates are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview hold scope and location outcomes

Question: Does naming a custodian in a Purview eDiscovery hold establish that every intended location is successfully held?

Purview process reports use Locations.csv to expose included locations, processing status and errors. Hold failures can include ineligible objects; the guide distinguishes eligible mailbox and site locations from objects such as distribution groups. A hold action must therefore be reconciled with actual location outcomes.

Source: Process reports in eDiscovery | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does naming a custodian in a Purview eDiscovery hold establish that every intended location is successfully held?

Buyer evidence still required

  • Expected mailbox and site inventory
  • Hold process Locations.csv and error details
  • Remediation evidence for omitted or failed locations

Review inference: Match the intended custody locations to successful hold records and resolve failures.

Suggested review condition: Do not claim complete hold coverage from the custodian label or submitted request alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Unlisted locations and the actual hold state of buyer data are not independently observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Find location-level preservation gaps before relying on a hold.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Legal advice about the adequacy of a hold
  • Unlisted locations and the actual hold state of buyer data are not independently observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview partially indexed evidence coverage

Question: Does a Purview eDiscovery search automatically include content that was not fully indexed?

Purview’s process-report guidance states that search results exclude partially indexed content by default, including unsupported formats and processing failures. Settings.csv records whether partially indexed items were included. A zero-hit result therefore does not establish absence of relevant content in those unsearched items.

Source: Process reports in eDiscovery | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Purview eDiscovery search automatically include content that was not fully indexed?

Buyer evidence still required

  • Search settings and partially indexed option
  • Processing failures and unsupported item inventory
  • Follow-up review of excluded material

Review inference: Inspect indexing coverage and inclusion settings before relying on a negative search result.

Suggested review condition: Reject an absence conclusion while relevant partially indexed content remains unassessed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The contents and relevance of excluded items are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent an incomplete search from becoming a false absence conclusion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed detection of every relevant legal record
  • The contents and relevance of excluded items are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview policy release versus site exclusion

Question: Does excluding a SharePoint site from a Purview retention policy receive the same grace period as releasing the policy?

The retention guide describes a 30-day preservation grace period when a SharePoint or OneDrive retention policy is released. It explicitly excludes updates that remove particular sites or accounts through policy exclusions: their Preservation Hold library cleanup proceeds without that 30-day delay. Other applicable retention controls still need evaluation.

Source: Learn about retention policies & labels to retain or delete | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does excluding a SharePoint site from a Purview retention policy receive the same grace period as releasing the policy?

Buyer evidence still required

  • Exact policy change: release, disable or explicit exclusion
  • Affected site/account and all other retention settings
  • Preservation-copy inventory and required recovery window

Review inference: Treat exclusion and policy release as different offboarding changes with different recovery expectations.

Suggested review condition: Do not rely on the policy-release grace period when the change is an explicit location exclusion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual cleanup timing and other applicable policies are not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid losing a presumed recovery window during a planned retention-scope change.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A guaranteed 30-day recovery window after every retention change
  • Actual cleanup timing and other applicable policies are not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview Preservation Lock and future policy changes

Question: Can a global administrator later shorten or disable a Purview policy after applying Preservation Lock?

Purview Preservation Lock prevents disabling, deleting or making the policy less restrictive, including by global administrators. A locked retention policy can gain locations or a longer period, but cannot lose locations or have its period shortened. A locked retention-label policy can add labels but cannot remove them.

Source: Use Preservation Lock to restrict changes to retention policies | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a global administrator later shorten or disable a Purview policy after applying Preservation Lock?

Buyer evidence still required

  • Policy type and current Preservation Lock state
  • Existing locations, labels and retention duration
  • Approved future exit and data-minimisation requirements

Review inference: Review exit and correction requirements before applying an irreversible restriction to retention administration.

Suggested review condition: Do not promise a later administrative rollback of a preservation-locked policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the buyer has already locked the policy or requires it is not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Expose irreversible retention commitments before approving an enterprise exit plan.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Regulatory certification or guaranteed ability to reverse a lock
  • Whether the buyer has already locked the policy or requires it is not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Purview retention: Conflicts and permanent deletion

Question: Does a short deletion policy prove Microsoft 365 content will be permanently removed on that date?

Ordinary retention conflict rules favour retention over deletion and the longest retention period. Deletion labels and policies have further precedence rules. Priority cleanup is a documented exceptional path. A short deletion setting alone does not determine the effective outcome for an item subject to other retention or hold conditions.

Source: Microsoft Purview retention principles. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The shortest configured deletion period establishes the effective removal date.

Buyer evidence still required

  • All applicable policies, labels and holds.
  • Item-level scope and effective precedence.
  • Any exceptional cleanup action and observed disposition.

Suggested review condition: Reconcile all applicable retention conditions before claiming a permanent-deletion date.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workload, item, retention policies, labels, holds and exceptional cleanup.

Optional saved evidence: Save the source-based precedence analysis without making a legal erasure conclusion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

PyJWT: Bind accepted algorithms to the intended key type

Question: Is enabling every supported JWT algorithm safe for an agent's token-verification helper?

PyJWT's CVE-2022-29217 advisory describes confusion between asymmetric public keys and symmetric verification when incompatible algorithms are accepted. It recommends explicitly selecting the expected algorithms. The frozen source covers versions from 1.5.0 before 2.4.0; the maintainer lists 2.4.0 as patched. For a verification helper, review the accepted algorithm set and intended key type together, including defaults introduced by wrappers. A token decoding successfully is not evidence of correct signature policy or application authorization. The historical patch does not validate a buyer's configuration.

Source: PyJWT maintainer advisory: CVE-2022-29217. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • successful decoding treated as verified authorization
  • a wrapper's algorithm policy inferred from package version
  • historical patch treated as buyer-configuration validation

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

PyPI GitHub owner identity resurrection

Question: Can a new GitHub account reusing a former owner's name inherit its PyPI trusted publishing authority?

PyPI stores the configured GitHub owner's immutable ID and checks repository_owner_id during token minting. A matching reused username with a different owner ID fails that check. Review the stable identity binding; a textual owner or repository name alone is not the documented authority test.

Source: Python Packaging Authority / PyPI: Trusted Publishing internals. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can a new GitHub account reusing a former owner's name inherit its PyPI trusted publishing authority?

Buyer evidence still required

  • stored trusted-publisher identity
  • current owner ID
  • OIDC claims
  • repository and workflow configuration

Review inference: A GitHub username is released and later registered by another account. Name-only review can falsely attribute publishing authority to the replacement. Adds immutable owner-ID checking against name resurrection, beyond general OIDC identity matching. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: This protection does not establish the original owner's account security or package-content safety.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. repository_owner_id

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • This protection does not establish the original owner's account security or package-content safety.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

PyPI pending publisher name reservation

Question: Does a pending PyPI trusted publisher reserve the proposed project name?

A pending publisher neither creates the project nor reserves its name until publication. If another user registers the name first, the pending publisher is invalidated. Confirm actual project ownership and publication outcome before treating the configuration as evidence that the intended distribution identity is secured.

Source: Python Packaging Authority / PyPI: Create a project with a trusted publisher. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a pending PyPI trusted publisher reserve the proposed project name?

Buyer evidence still required

  • pending publisher
  • intended project name
  • actual project registration
  • first publication result

Review inference: A company announces a package name after configuring only a pending publisher. The name can be registered elsewhere before its first release. Adds the pre-project reservation boundary, distinct from authenticated upload to an existing project. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Pending configuration is not namespace ownership, a package review or a completed release.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. does not create a project or reserve

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Pending configuration is not namespace ownership, a package review or a completed release.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

PyPI Trusted Publishing: Short-lived publishing identity is not package approval

Question: Does PyPI Trusted Publishing mean PyPI has reviewed and approved the package code?

Trusted Publishing matches OIDC identities to configured project publishers and exchanges them for short-lived project-scoped upload tokens. It reduces reliance on stored long-lived tokens. That is a publishing-authentication mechanism; the reviewed description does not establish an independent assessment of package contents.

Source: PyPI trusted publisher identity. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Trusted publisher status is an independent code-quality or safety approval.

Buyer evidence still required

  • Project publisher configuration and expected CI identity.
  • Release identity and resulting package version.
  • Separate code and artifact acceptance evidence.

Suggested review condition: Do not convert publishing authentication into a package-safety claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Publisher configuration, CI identity, release version and consumer checks

Optional saved evidence: Save the distinction between an authorised release identity and an accepted artifact.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Python skill tool read-only auto-approval versus script execution approval

Question: Does approving read-only Microsoft Agent Framework skill tools also approve script execution?

For the documented Python SkillsProvider with ToolApprovalMiddleware, the read_only_tools_auto_approval_rule covers load_skill and read_skill_resource while run_skill_script still requires approval. The all_tools_auto_approval_rule includes script execution.

Source: Microsoft primary documentation: ms skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does approving read-only Microsoft Agent Framework skill tools also approve script execution?

Buyer evidence still required

  • provider version
  • middleware configuration
  • auto-approval rules
  • proposed script call

Review inference: Does approving read-only Microsoft Agent Framework skill tools also approve script execution? Do not treat a read-only approval rule as script authorisation, or assume middleware is installed from the skill manifest alone. Python skill tool read-only auto-approval versus script execution approval. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat a read-only approval rule as script authorisation, or assume middleware is installed from the skill manifest alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Tool approval

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat a read-only approval rule as script authorisation, or assume middleware is installed from the skill manifest alone.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Qdrant alias switching and retained collections

Question: Does atomically moving a Qdrant alias to a replacement collection remove the old collection and its data?

Qdrant aliases are names that refer to collections. Its documented migration pattern creates a replacement collection and atomically switches alias operations so callers can use the new collection. Alias changes and collection deletion are different operations. A successful alias switch establishes routing, not removal of the old collection or its snapshots.

Source: Collections - Qdrant. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does atomically moving a Qdrant alias to a replacement collection remove the old collection and its data?

Buyer evidence still required

  • Alias actions and source/destination collection names
  • Collection inventory before and after the switch
  • Old collection and snapshot retention or deletion requirements

Review inference: Inventory collections by their own identities rather than only through the active alias after a cutover.

Suggested review condition: Do not close an exit task from an alias switch while old collection state remains unaccounted for.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Old collection contents, direct-name access and retained snapshots are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Find data left behind after a successful retrieval cutover.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Erasure or access revocation for the previous collection from an alias update
  • Old collection contents, direct-name access and retained snapshots are unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Qdrant completed writes and replica acknowledgement

Question: Does a Qdrant write completed with wait=true establish that every configured replica has applied the change?

Qdrant distinguishes a queued acknowledgement from a completed operation through wait. Replica acknowledgement is separately governed by write_consistency_factor, whose default is one. Offline replicas may receive updates after recovery. An error caused by insufficient acknowledgements can still leave a change partially applied. Completion must be interpreted with the configured replication and consistency requirements.

Source: Points - Qdrant. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Qdrant write completed with wait=true establish that every configured replica has applied the change?

Buyer evidence still required

  • Operation ID, wait setting and response status
  • Replication factor, write_consistency_factor and replica health
  • Read consistency requirements and subsequent observations

Review inference: Reconcile operation status, required acknowledgements and replica state before treating a deletion as cluster-wide.

Suggested review condition: Refuse all-replica completion claims based only on wait=true or a write error.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual state of each replica and subsequent read results are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid mistaking an accepted cleanup or partial write for confirmed cluster-wide state.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal replica convergence or rollback from a single response
  • The actual state of each replica and subsequent read results are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Qdrant MCP: Retrieval scope and persistent memory writes

Question: Can a retrieval agent search Qdrant without adding persistent memories?

The official Qdrant MCP server separates finding stored information from storing new information. Its read-only option disables the store tool. Review the collection, database credential and deployment transport separately; a retrieval setting does not establish who can reach a remotely exposed server.

Source: Qdrant official MCP read and memory-write capabilities. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official qdrant/mcp-server-qdrant deployment selected by the operator

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Qdrant publishes the server; the operator chooses its deployment and database.

Documented by publisher. Qdrant official MCP read and memory-write capabilities

Purpose

The server stores and retrieves semantic memories in Qdrant.

Documented by publisher. Qdrant official MCP read and memory-write capabilities

Read capability

The find tool retrieves matching stored information from the selected collection.

Documented by publisher. Qdrant official MCP read and memory-write capabilities

Write capability

The store tool persists information and optional metadata; QDRANT_READ_ONLY disables that tool.

Documented by publisher. Qdrant official MCP read and memory-write capabilities

Authentication

A Qdrant API key can authenticate the database connection; the selected MCP transport needs its own access review.

Documented by publisher. Qdrant official MCP read and memory-write capabilities

Permission surface

Collection configuration and database authorization remain distinct from disabling the store tool.

Documented by publisher. Qdrant official MCP read and memory-write capabilities

Data leaving the environment

Search output reaches the agent client; stored information persists in the configured Qdrant database.

Review inference. Qdrant official MCP read and memory-write capabilities

Failure modes to consider

An unintended collection or a reachable remote listener can widen the intended retrieval boundary.

Review inference. Qdrant official MCP read and memory-write capabilities

Unknowns and applicability

Database-key scope, remote client authentication, retention and embedding deployment have not been verified.

Not established

Suggested refusal or clarification condition

Resolve collection and caller scope before retrieving private memory; obtain task authority before storing new material.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck collection routing, transport exposure, database credentials and store-tool availability.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve which memory collection and read-only assumptions supported a retrieval decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Qdrant payload index removal and stored fields

Question: Does deleting a Qdrant payload index remove the indexed values from stored point payloads?

Qdrant exposes a field-index deletion operation separately from payload mutation. Its payload guide documents deleting selected keys and clearing all payload fields as distinct operations on points. Removing an index therefore does not establish that the underlying field values were removed; payload cleanup requires its own scoped request and resulting-state evidence.

Source: Delete payload index | Qdrant | API Reference. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a Qdrant payload index remove the indexed values from stored point payloads?

Buyer evidence still required

  • Collection and indexed field identities
  • Point selection and payload-key deletion or clear operation
  • Result status and subsequent payload inspection

Review inference: Separate search-index configuration from the inventory and deletion of the sensitive payload values.

Suggested review condition: Refuse payload-erasure claims supported only by deletion of a field index.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual remaining values, snapshots and external copies are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid declaring sensitive data removed when only a filtering structure has changed.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Deletion of stored field values or backups by removing a payload index
  • Actual remaining values, snapshots and external copies are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Qdrant read-only access and snapshot downloads

Question: Does Qdrant read-only collection access prevent a permitted user from downloading a collection snapshot?

Qdrant’s access matrix permits listing and downloading collection and shard snapshots for collection read access as well as broader roles. Collection snapshots include points, payload and collection configuration. Read-only is therefore not an export prohibition within the authorised collection scope. Full-storage snapshots have different permissions and must not be inferred from collection access.

Source: Security - Qdrant. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Qdrant read-only collection access prevent a permitted user from downloading a collection snapshot?

Buyer evidence still required

  • Credential type and authorised collection scope
  • Available collection/shard snapshots and download permissions
  • Required export restrictions and observed access revocation

Review inference: Include snapshot download capability in the data-access and offboarding assessment of read-only credentials.

Suggested review condition: Reject a no-export conclusion based solely on the read-only label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether snapshots exist or were downloaded, and the buyer’s deployed authorisation configuration, are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Assess whether a supposedly limited credential can retrieve a portable copy of permitted data.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Prevention of data extraction or access to every collection from a read-only credential
  • Whether snapshots exist or were downloaded, and the buyer’s deployed authorisation configuration, are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Qdrant snapshot recovery priority

Question: Does recovering a Qdrant snapshot always replace existing collection data with the snapshot contents?

Qdrant snapshot recovery supports replica, snapshot and no_sync priorities. The default replica priority favours existing replicas during conflict resolution; snapshot priority favours the snapshot. The guide warns that restoring into a new collection requires snapshot priority because empty existing state can otherwise win. Recovery is not a universal replace-or-merge operation independent of these settings.

Source: Snapshots - Qdrant. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does recovering a Qdrant snapshot always replace existing collection data with the snapshot contents?

Buyer evidence still required

  • Snapshot identity, hash and source collection
  • Destination collection state, replicas and selected recovery priority
  • Required point/payload inventory and post-recovery comparison

Review inference: Record the chosen priority and destination state, then reconcile the resulting points against the required recovery inventory.

Suggested review condition: Reject exact-restore claims that omit recovery priority or destination state.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual conflicts, restored contents and compatibility of the buyer’s versions remain unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a recovery operation from silently selecting a different source of truth than intended.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Deterministic replacement of all collection contents with any default restore request
  • Actual conflicts, restored contents and compatibility of the buyer’s versions remain unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Qdrant tiered tenancy: Shared placement has a capacity boundary

Question: Does tiered multitenancy give every small Qdrant tenant independent physical capacity?

The guide places small tenants in a shared fallback shard and describes promotion to dedicated shards. It also documents single-shard transfer constraints and the shared fallback capacity limit. Logical tenant organisation therefore does not establish independent resources, automatic authorisation isolation or unlimited scaling for each tenant.

Source: Qdrant multitenancy design. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A tenant identifier proves independent capacity and complete isolation.

Buyer evidence still required

  • Collection, fallback and dedicated shard configuration.
  • Tenant placement and capacity evidence.
  • Separate authorisation and workload-isolation controls.

Suggested review condition: Do not infer independent capacity or access enforcement from a tenant label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Shard configuration, tenant placement, transfer state and authorisation controls

Optional saved evidence: Retain the distinction between placement, capacity and independently evidenced access controls.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Qdrant: A distributed export needs node coverage

Question: Does one Qdrant node snapshot establish a complete distributed collection export?

Qdrant documents creating and downloading collection snapshots from each node in its distributed-cluster example. Background snapshot creation with wait=false does not return a snapshot name; the resulting snapshots must be listed and downloaded. One accepted request is not evidence of complete node coverage.

Source: Snapshots - Qdrant. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does one Qdrant node snapshot establish a complete distributed collection export?

Buyer evidence still required

  • Cluster node and shard layout.
  • Per-node snapshot completion and names.
  • Downloaded artifacts, hashes and restore plan.

Suggested review condition: Do not mark the distributed export complete while node snapshots or background results remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Cluster node and shard layout. Per-node snapshot completion and names. Downloaded artifacts, hashes and restore plan.

Optional saved evidence: Reconcile vector-store exit artifacts against the distributed collection layout.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual customer export, point-in-time consistency across nodes or successful restoration
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

QV1 PCB1: Net economics boundary

Question: Can QV1 PCB1 correctness evidence support net end-to-end economic gain?

The public QV1 PCB1 source retains strong correctness evidence alongside economic non-qualification. It does not establish net end-to-end economic gain.

Derived from BDAS QV1 PCB1 Vision — Correctness Strong, Economics Not Qualified. No new experiment or validation is claimed.

Claim boundaries
  • net end-to-end economic gain
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

RabbitMQ: Confirmed publish with no destination queue

Question: Does a RabbitMQ publisher confirm prove that the message reached a destination queue?

RabbitMQ 4.3 can confirm an unroutable publish after the exchange determines that no queue matches. With the mandatory flag, basic.return precedes the confirm for an unroutable message. Publisher confirms and consumer acknowledgements cover separate exchanges of responsibility; the publish confirm alone does not establish queue routing or application processing.

Source: RabbitMQ: Consumer acknowledgements and publisher confirms. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a RabbitMQ publisher confirm prove that the message reached a destination queue?

Buyer evidence still required

  • Exchange, routing key, bindings and mandatory flag for the publish.
  • Correlated publisher confirm and any basic.return response.
  • Intended queue observation and consumer processing result.

Suggested review condition: Decline a routed-or-processed conclusion from a publisher confirm without the routing and consumer evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Exchange, routing key, bindings and mandatory flag for the publish. Correlated publisher confirm and any basic.return response. Intended queue observation and consumer processing result.

Optional saved evidence: A recovery decision based only on a positive publish acknowledgement can overlook work that reached no queue.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof of consumer completion or automatic retention of unroutable messages
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

RabbitMQ: Dead-letter transfer can itself fail

Question: Does configuring a RabbitMQ dead-letter exchange guarantee that failed work is retained for recovery?

RabbitMQ 4.3 documents dead-lettering as republishing. By default it uses no internal publisher confirms and removes the message from its source queue after publishing; the message can be lost if the destination cannot accept it. Quorum queues offer an at-least-once dead-lettering alternative. A configured exchange alone does not establish a reliable recovery handoff.

Source: RabbitMQ: Dead-letter exchanges. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does configuring a RabbitMQ dead-letter exchange guarantee that failed work is retained for recovery?

Buyer evidence still required

  • Source queue type, effective dead-letter strategy, exchange and routing configuration.
  • Destination availability and broker handoff errors or confirmations.
  • Retained destination message and recovery result correlated to the original action.

Suggested review condition: Decline retained-for-recovery claims without checking the effective handoff mode and destination evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Source queue type, effective dead-letter strategy, exchange and routing configuration. Destination availability and broker handoff errors or confirmations. Retained destination message and recovery result correlated to the original action.

Optional saved evidence: A failed action can lose its recovery message at the handoff that operators expected to preserve it.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal lossless dead-lettering, exactly-once recovery or verified queue health
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Railway MCP: User identity and confirmation hints

Question: Can a Railway project token restrict an MCP agent to one project?

The current documentation says project tokens are not accepted: MCP requires a user identity. OAuth can select workspaces and projects, while the default CLI bridge reuses the login session. Destructive-action hints depend on client support, so verify both the grant and confirmation behaviour.

Source: Railway hosted and local MCP identity and deployment tools. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted server, CLI bridge and local alternative

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Railway operates the hosted server and publishes its CLI integration.

Documented by publisher. Railway hosted and local MCP identity and deployment tools

Purpose

Manage projects, deployments and supported operational actions.

Documented by publisher. Railway hosted and local MCP identity and deployment tools

Read capability

Reads project, service and feature-flag information.

Documented by publisher. Railway hosted and local MCP identity and deployment tools

Write capability

Can create projects, redeploy, change flags and delegate multistep operations.

Documented by publisher. Railway hosted and local MCP identity and deployment tools

Authentication

User OAuth or CLI login; project tokens are not accepted.

Documented by publisher. Railway hosted and local MCP identity and deployment tools

Permission surface

OAuth resource selections and the acting user determine access; local tools differ.

Documented by publisher. Railway hosted and local MCP identity and deployment tools

Data leaving the environment

Operational context is returned to the assistant and may be handled by Railway delegated tools.

Review inference. Railway hosted and local MCP identity and deployment tools

Failure modes to consider

A client may not enforce protocol confirmation hints as expected.

Review inference. Railway hosted and local MCP identity and deployment tools

Unknowns and applicability

Buyer grant and actual client confirmation behaviour are unknown.

Not established

Suggested refusal or clarification condition

Require scoped identity evidence and authorised deployment intent.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck OAuth selections, CLI variant and confirmation support.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the identity and confirmation assumptions behind a hosting-agent approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

RDS deletion: Retained backup and snapshot copies

Question: Does deleting an RDS instance also remove every recoverable database copy?

Deletion offers separate choices for a final snapshot and retained automated backups. Earlier manual snapshots and a created final snapshot remain. Retained automated backups follow the retention period effective at deletion. Instance absence alone therefore does not establish removal of all recovery copies.

Source: Deleting an Amazon RDS DB instance. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Deleting the database instance proves all recoverable copies were erased.

Buyer evidence still required

  • Deletion options and effective backup retention.
  • Manual and final snapshot inventory.
  • Cross-region or separately copied backup scope.

Suggested review condition: Reconcile retained copies before claiming complete deletion or guaranteed recovery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Instance, deletion options, snapshot inventory and retained backup period.

Optional saved evidence: Preserve the source-linked copy-retention boundary for a supplier exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Record 7026446: Economic gain boundary

Question: Does correctness qualification in record 7026446 establish economic gain?

Record 7026446 separates correctness qualification from economic non-qualification. Its public source does not demonstrate economic gain.

Derived from BDAS 7026446 — Correctness Qualified, Economics Not Qualified. No new experiment or validation is claimed.

Claim boundaries
  • economic gain
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Record 7026446: Outer holdout boundary

Question: Does correctness qualification in 7026446 establish outer holdout promotion?

The public 7026446 source separates correctness from economics and excludes outer holdout promotion.

Derived from BDAS 7026446 — Correctness Qualified, Economics Not Qualified. No new experiment or validation is claimed.

Claim boundaries
  • outer holdout promotion
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Redis MCP: Database ACLs and state-changing memory tools

Question: What prevents a Redis agent from changing session memory while performing a read task?

The Redis MCP server exposes both retrieval and state-changing tools. Its documentation points to Redis ACLs for database restrictions. Identify the database user, command scope and permitted keys; having a memory interface does not make the session read-only or establish a retention policy.

Source: Redis MCP tools and ACL configuration. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official redis/mcp-redis server; operator-selected Redis instance and identity

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Redis publishes the server; the operator chooses its Redis deployment.

Documented by publisher. Redis MCP tools and ACL configuration

Purpose

It lets agent clients manage and search Redis data.

Documented by publisher. Redis MCP tools and ACL configuration

Read capability

Tools retrieve strings, hashes, collection members and other supported Redis data.

Documented by publisher. Redis MCP tools and ACL configuration

Write capability

Tools can set or remove data, publish messages and change stream state.

Documented by publisher. Redis MCP tools and ACL configuration

Authentication

Database username and password or supported deployment-specific identity options configure authentication.

Documented by publisher. Redis MCP tools and ACL configuration

Permission surface

Redis ACLs can restrict database access; the documentation includes a read-only identity example.

Documented by publisher. Redis MCP tools and ACL configuration

Data leaving the environment

Data retrieved from Redis reaches the client; new memory writes persist according to database settings.

Review inference. Redis MCP tools and ACL configuration

Failure modes to consider

Broad key scope, mutable queue operations or missing expiry can exceed an intended read-only memory task.

Review inference. Redis MCP tools and ACL configuration

Unknowns and applicability

Actual ACLs, instance selection, expiration rules, transport security and client retention are unverified.

Not established

Suggested refusal or clarification condition

Confirm command and key permissions before accessing private session state; do not infer read-only access from a search-oriented prompt.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck ACLs, database selection, expiry and supported tools.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the database identity and state-change assumptions behind a memory connector review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Redis queued transaction and execution boundary

Question: Does QUEUED establish that a Redis transaction executed before a connection interruption?

Redis queues commands after MULTI and executes them when EXEC is called. QUEUED is therefore scheduling evidence, not execution. Disconnecting before EXEC performs none of the queued operations. If EXEC was sent and its response was lost, that earlier guarantee does not establish non-execution or make repetition safe; inspect the actual command outcomes separately.

Source: Redis official transactions documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does QUEUED establish that a Redis transaction executed before a connection interruption?

Buyer evidence still required

  • MULTI and queued commands
  • Whether EXEC reached the server
  • Replies or resulting state and retry identity

Review inference: Distinguish QUEUED commands from EXEC-triggered transaction execution after a connection interruption. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Disconnect before EXEC means no queued operations executed; a lost response after sending EXEC is not proof of no execution or safe replay.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Usage; Transaction guarantees in Redis official transactions documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Disconnect before EXEC means no queued operations executed; a lost response after sending EXEC is not proof of no execution or safe replay.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Redis stream acknowledgement evidence

Question: Does Redis XACK prove completed business processing or erasure of the message payload?

Redis XACK removes entries from a consumer group's Pending Entries List and returns the number successfully acknowledged. Already absent IDs are not counted. Consumers should acknowledge after processing, but the command does not independently inspect that business outcome. Clearing the PEL entry is not itself evidence that the stream payload or every other retained copy was erased.

Source: Redis official xack documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Redis XACK prove completed business processing or erasure of the message payload?

Buyer evidence still required

  • Stream, group and message IDs
  • XACK result and PEL state
  • Independent processing and retention evidence

Review inference: Distinguish stream consumer acknowledgement from independently observed business processing and payload retention. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. XACK clears the group PEL entry and counts acknowledgements; it does not inspect external processing or certify erasure of stream content.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Command semantics; Return information in Redis official xack documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • XACK clears the group PEL entry and counts acknowledgements; it does not inspect external processing or certify erasure of stream content.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Redis transaction errors and no rollback

Question: Does an error during Redis EXEC mean that every operation was rolled back?

Redis distinguishes errors while queueing from errors during EXEC. Since 2.6.5, detected queue-time errors cause EXEC to discard the transaction. Runtime errors do not stop the other queued commands, and Redis does not roll back successful operations. An error in the reply array is therefore not proof that the transaction made no changes.

Source: Redis official transactions documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an error during Redis EXEC mean that every operation was rolled back?

Buyer evidence still required

  • Redis version
  • Queue responses and full EXEC reply array
  • Individual command outcomes

Review inference: Distinguish queue-time rejection from partial command errors inside an executed Redis transaction. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Runtime errors do not stop other commands or roll back successful commands; Redis 2.6.5 queue-error behavior is version scoped.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Errors inside a transaction; What about rollbacks? in Redis official transactions documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Runtime errors do not stop other commands or roll back successful commands; Redis 2.6.5 queue-error behavior is version scoped.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Redis WAIT connection and threshold evidence

Question: Does a successful Redis WAIT response establish the requested replication level for every prior application write?

Redis WAIT reports how many replicas acknowledged earlier writes on the current connection. It returns a count on timeout as well as success, so that count must be compared with the requested level. In MULTI and other nonblocking contexts it returns immediately rather than waiting. A WAIT call on another pooled connection does not establish the original writes' barrier.

Source: Redis official wait documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a successful Redis WAIT response establish the requested replication level for every prior application write?

Buyer evidence still required

  • Connection carrying the writes and WAIT
  • Requested and returned replica counts
  • Timeout and blocking context

Review inference: Bind a WAIT replication count to prior writes on the same connection and the requested threshold. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Timeout also returns a count; pooled connections and nonblocking MULTI/script contexts cannot be assumed to provide a global barrier.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Command semantics; Remarks in Redis official wait documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Timeout also returns a count; pooled connections and nonblocking MULTI/script contexts cannot be assumed to provide a global barrier.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Redis WAIT failover retention boundary

Question: Does Redis WAIT guarantee that an acknowledged write survives failover?

Redis documents that WAIT does not make the store strongly consistent. Sentinel and Cluster attempt to promote a suitable replica, but this selection is best effort; even a write acknowledged by multiple replicas can be lost after failover. A replication acknowledgement is useful evidence, not a guarantee of survival under every failure sequence.

Source: Redis official wait documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Redis WAIT guarantee that an acknowledged write survives failover?

Buyer evidence still required

  • Acknowledged write identity
  • Replica and failover topology
  • Observed promoted-node state

Review inference: Distinguish acknowledged Redis replication from guaranteed retention through failover. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Sentinel and Cluster select replicas best effort; acknowledged writes can still be lost.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Consistency and WAIT in Redis official wait documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Sentinel and Cluster select replicas best effort; acknowledged writes can still be lost.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Redis WAITAOF persistence counts

Question: Does a WAITAOF return establish that the requested local and replica persistence levels were met?

Redis WAITAOF, available since 7.2, reports local and replica AOF fsync acknowledgements for prior writes on the same connection. Timeout can return counts below the requested levels; MULTI or script contexts do not block. AOF configuration and documented propagation limitations apply. Inspect both counts; the command does not create global strong consistency or guarantee every failover outcome.

Source: Redis official waitaof documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a WAITAOF return establish that the requested local and replica persistence levels were met?

Buyer evidence still required

  • Redis version and AOF settings
  • Connection writes and requested local/replica counts
  • Actual fsync counts and propagation behavior

Review inference: Interpret local and replica WAITAOF counts as AOF persistence evidence for prior connection writes. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Redis 7.2+, AOF configuration, timeout, nonblocking context and replication/AOF propagation limitations apply; not global strong consistency.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Command semantics; Limitations; Consistency and WAITAOF in Redis official waitaof documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Redis 7.2+, AOF configuration, timeout, nonblocking context and replication/AOF propagation limitations apply; not global strong consistency.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Redis WATCH expiration and eviction conflicts

Question: Can a Redis WATCH transaction abort even when no other client wrote the watched key?

Redis WATCH makes EXEC conditional on watched keys remaining unchanged. Changes include client writes and Redis expiration or eviction; versions before 6.0.9 did not abort for expiration. A conflict returns a Null EXEC reply and aborts conditional execution. Merely seeing no competing client write does not establish that WATCH must succeed.

Source: Redis official transactions documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Redis WATCH transaction abort even when no other client wrote the watched key?

Buyer evidence still required

  • Redis version and watched keys
  • Expiration, eviction and write events
  • EXEC reply and retry policy

Review inference: Interpret WATCH aborts caused by expiration, eviction or client writes before EXEC. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. Expiration behavior differs before Redis 6.0.9; a Null EXEC reply is failed conditional execution, not a committed result.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck WATCH explained in Redis official transactions documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Expiration behavior differs before Redis 6.0.9; a Null EXEC reply is failed conditional execution, not a committed result.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Redis XAUTOCLAIM recovery completeness

Question: Does a completed XAUTOCLAIM scan establish that every pending Redis message was recovered and processed?

Redis XAUTOCLAIM scans pending entries and claims those meeting its idle-time condition. A returned 0-0 ends that scan, but later calls can find entries that have since become eligible. Since Redis 7.0, missing or trimmed stream entries are removed from the PEL and reported separately, not recovered. Cursor completion therefore does not prove all work was processed or all payloads were restored.

Source: Redis official xautoclaim documentation. Documentation checked 2026-10-25; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a completed XAUTOCLAIM scan establish that every pending Redis message was recovered and processed?

Buyer evidence still required

  • Redis version, group and cursor
  • Idle threshold and returned claimed entries
  • Reported deleted IDs and processing outcomes

Review inference: Interpret XAUTOCLAIM cursor completion and missing stream entries during pending-work recovery. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse buyer-specific assurance from documentation alone. 0-0 completes the scan, not all future idle eligibility; since 7.0 deleted entries are removed from the PEL and reported, not recovered.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck Command semantics; History in Redis official xautoclaim documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • 0-0 completes the scan, not all future idle eligibility; since 7.0 deleted entries are removed from the PEL and reported, not recovered.
  • Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Redshift RLS: Cross-database and sharing exceptions

Question: Can an agent assume a Redshift RLS policy follows every cross-database or shared-data access path?

The reviewed limitations distinguish ordinary RLS access from cross-database queries and datasharing. Cross-database reads of protected relations are blocked for users without IGNORE RLS; sharing also has explicit restrictions and configuration. Inspect the caller privilege and access path instead of assuming one filter covers all consumers.

Source: Redshift RLS considerations and limitations. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: One RLS policy proves identical filtering on every data access path.

Buyer evidence still required

  • Relation RLS and sharing configuration.
  • Caller privileges including IGNORE RLS.
  • Cross-database or consumer query path.

Suggested review condition: Require path-specific evidence before claiming row isolation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Relation settings, RLS exception privileges and sharing path

Optional saved evidence: Retain the access-path exceptions that procurement must resolve for row-level isolation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Regional inference does not pin the complete request path

Question: Does Vercel inferenceRegion establish that the gateway and every downstream copy stayed in that region?

The documented pin controls provider inference and configured provider storage; a request-level region must remain within a team pin. Gateway processing may occur in any Vercel region. Gateway-run tools and provider abuse or safety handling have separate location boundaries. Check the serving attempt region, not just the requested value.

Source: AI Gateway Regional Inference. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Vercel inferenceRegion establish that the gateway and every downstream copy stayed in that region?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Refuse an end-to-end regional or sovereign-processing claim from inferenceRegion alone; review tool transfers, safety exceptions and provider terms separately.

Suggested review condition: Refuse an end-to-end regional or sovereign-processing claim from inferenceRegion alone; review tool transfers, safety exceptions and provider terms separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ## Where your data goes; ## How team-wide and per-request pinning interact; ## Confirming where a request ran

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse an end-to-end regional or sovereign-processing claim from inferenceRegion alone; review tool transfers, safety exceptions and provider terms separately.
  • A region-pinned inference attempt can satisfy the narrower documented provider-location question while gateway or tool processing remains outside that scope.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Remote MCP archive resource discovery versus executable script capability

Question: Can a downloaded Microsoft Agent Framework MCP skill archive execute its bundled scripts?

The documented archive-type MCP skill path exposes extracted resources but does not execute bundled scripts. File-based scripts and remote archive resources have different execution treatment.

Source: Microsoft primary documentation: ms skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a downloaded Microsoft Agent Framework MCP skill archive execute its bundled scripts?

Buyer evidence still required

  • MCP source
  • index entry type
  • archive bytes
  • provider/runtime version

Review inference: Can a downloaded Microsoft Agent Framework MCP skill archive execute its bundled scripts? Do not infer local script execution from successful archive discovery; another installation path needs a separate review. Remote MCP archive resource discovery versus executable script capability. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer local script execution from successful archive discovery; another installation path needs a separate review.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Archive-type skills

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer local script execution from successful archive discovery; another installation path needs a separate review.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Render MCP: Workspace selection and deployment effects

Question: Does read-only SQL support mean Render MCP cannot change my application?

No. Render lists read-only SQL alongside service creation, environment-variable updates and redeployment. Actions use the selected workspace. A database inspection task therefore needs a narrower authorised scope than the complete connector capability set.

Source: Render MCP workspace selection and deployment authority. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted server with local alternative

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Render operates the hosted MCP and publishes a local alternative.

Documented by publisher. Render MCP workspace selection and deployment authority

Purpose

Inspect and manage application hosting resources.

Documented by publisher. Render MCP workspace selection and deployment authority

Read capability

Reads logs, metrics, deployment information and read-only SQL results.

Documented by publisher. Render MCP workspace selection and deployment authority

Write capability

Creates services, updates environment variables and triggers deployments.

Documented by publisher. Render MCP workspace selection and deployment authority

Authentication

OAuth or API-key authentication.

Documented by publisher. Render MCP workspace selection and deployment authority

Permission surface

Actions are scoped to the selected workspace and available account access.

Documented by publisher. Render MCP workspace selection and deployment authority

Data leaving the environment

Logs and database query results can enter the assistant.

Review inference. Render MCP workspace selection and deployment authority

Failure modes to consider

Workspace confusion can direct a valid operation at the wrong service.

Review inference. Render MCP workspace selection and deployment authority

Unknowns and applicability

Buyer workspace rights and intended deployment state are unverified.

Not established

Suggested refusal or clarification condition

Require the target service and change authority before redeployment or configuration updates.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck selected workspace, account access and hosted tool additions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the distinction between database inspection and application-changing capability.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

Requests: Check proxy credential exposure conditions

Question: Does an affected Requests version prove that proxy credentials leaked?

The Requests maintainer advisory for CVE-2023-32681 describes a proxy-credential leak during redirects to HTTPS when credentials are supplied in the proxy URL. It lists versions from 2.3.0 before 2.31.0, with 2.31.0 fixing this issue. A package-version match alone does not establish that those conditions occurred. For an exposure review, check proxy authentication, redirect destinations and actual requests. This historical fix does not establish that a version is free of other vulnerabilities.

Source: Requests maintainer advisory: CVE-2023-32681. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • confirmed credential exposure in a buyer's deployment
  • a historical fix establishing a currently safe package
  • earlier leakage disproved by an upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Resend MCP: Drafts, sends and account permissions

Question: Does connecting Resend for support drafting authorise the agent to send email?

No. Resend documents both drafting workflows and transactional sending, plus contact and webhook operations. OAuth grants or API-key access establish technical capability, not the requested business action. Identify whether the task ends at a draft or an authorised send and verify the recipient scope.

Source: Resend hosted MCP OAuth, email and contact operations. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted email platform server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Resend hosts the remote MCP service.

Documented by publisher. Resend hosted MCP OAuth, email and contact operations

Purpose

Use email, contacts, logs and related platform functions.

Documented by publisher. Resend hosted MCP OAuth, email and contact operations

Read capability

Reads request logs and webhook delivery information.

Documented by publisher. Resend hosted MCP OAuth, email and contact operations

Write capability

Can send transactional email and manage contact workflows.

Documented by publisher. Resend hosted MCP OAuth, email and contact operations

Authentication

OAuth or API-key bearer access for headless clients.

Documented by publisher. Resend hosted MCP OAuth, email and contact operations

Permission surface

OAuth permissions are granted to the chosen account and can be revoked in team settings.

Documented by publisher. Resend hosted MCP OAuth, email and contact operations

Data leaving the environment

Email and recipient context can enter the assistant and delivery systems.

Review inference. Resend hosted MCP OAuth, email and contact operations

Failure modes to consider

Drafting intent can be confused with authority to send or change contact segments.

Review inference. Resend hosted MCP OAuth, email and contact operations

Unknowns and applicability

Buyer grant, recipient authorisation and client retention are unknown.

Not established

Suggested refusal or clarification condition

Require explicit send authority and recipient scope before external delivery.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck account permissions, enabled tools and recipient policy.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the draft/send distinction used when approving an email agent.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Responses default_version versus latest_version selection

Question: Which OpenAI Responses skill version is selected when no explicit version is supplied?

The documented Responses Skills API uses default_version for an omitted version and separately tracks latest_version. An explicit version or latest reference has a different update boundary.

Source: OpenAI primary documentation: openai skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Which OpenAI Responses skill version is selected when no explicit version is supplied?

Buyer evidence still required

  • skill ID
  • reference version
  • default/latest pointers
  • reviewed bundle hash

Review inference: Which OpenAI Responses skill version is selected when no explicit version is supplied? Do not transfer Anthropic's omitted-version rule to OpenAI; bind the reviewed version and bytes before approval. Responses default_version versus latest_version selection. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not transfer Anthropic's omitted-version rule to OpenAI; bind the reviewed version and bytes before approval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Version pointers

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not transfer Anthropic's omitted-version rule to OpenAI; bind the reviewed version and bytes before approval.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Responses storage encryption does not cover application-held copies

Question: Does Foundry Agent Service storage configuration describe direct Responses API state and all client-held reasoning items?

Microsoft describes direct Responses API history as service-managed storage without bring-your-own-data storage, distinct from Agent Service arrangements. Resource CMK protection applies only where configured and applicable. That description does not cover application-retained material, including encrypted reasoning items returned for stateless requests.

Source: Data, privacy, and security for Foundry Models sold by Azure in Microsoft Foundry - Microsoft Foundry | Microsoft Learn. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Foundry Agent Service storage configuration describe direct Responses API state and all client-held reasoning items?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require the exact API and storage owner for each copy plus applicable key coverage; refuse to infer client-copy protection or deletion from service encryption settings.

Suggested review condition: Require the exact API and storage owner for each copy plus applicable key coverage; refuse to infer client-copy protection or deletion from service encryption settings.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. ### Encryption of content stored by the Responses API

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the exact API and storage owner for each copy plus applicable key coverage; refuse to infer client-copy protection or deletion from service encryption settings.
  • Applicable CMK configuration can protect covered service-managed content; it is not evidence that all content lacks encryption.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic append-only retention decisions

Question: Does an append-only restic repository prevent a compromised writer from influencing later retention?

The v0.19.1 guide warns that an append-only writer can add misleading snapshots whose timestamps displace legitimate snapshots under some count or calendar retention policies when an administrator later runs forget. It recommends separate secured maintenance access and a keep-within policy, while documenting that protection still depends on the retention window and correct time. Append-only access alone does not validate the snapshots chosen for retention.

Source: restic v0.19.1 — 060_forget. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an append-only restic repository prevent a compromised writer from influencing later retention?

Buyer evidence still required

  • Writer and maintenance access separation
  • Snapshot origins, timestamps and retention selection
  • Policy window and last known-good recovery evidence

Review inference: Review snapshot provenance before privileged maintenance removes recoverable history. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse a retention-integrity guarantee from append-only permissions alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No compromise, attack or buyer repository integrity was independently assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No compromise, attack or buyer repository integrity was independently assessed.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic forgotten snapshots and retained data

Question: Does restic forget immediately remove the backed-up file data from its repository?

In restic v0.19.1, forget removes snapshot references. Repository data no longer needed by retained snapshots is reclaimed by prune, which checks remaining references and may repack partly used files. Data still referenced by another snapshot remains needed. Removing a snapshot reference is therefore distinct from repository reclamation and from physical erasure by the underlying storage service.

Source: restic v0.19.1 — 060_forget. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does restic forget immediately remove the backed-up file data from its repository?

Buyer evidence still required

  • Snapshot IDs removed and snapshots retained
  • Successful prune evidence and remaining data references
  • Storage-provider residual-copy and erasure policy

Review inference: Separate logical retention decisions from actual backup-space reclamation. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse physical-deletion evidence based solely on a successful forget operation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Underlying media erasure, provider replicas and other repositories are not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Underlying media erasure, provider replicas and other repositories are not established.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic recovery deletion scope

Question: Does restic restore --delete remove every extra file from the entire target tree?

The v0.19.1 guide defines --delete as removal of target files absent from the snapshot within the selected restore scope. Include/exclude options restrict which files or directories are subject to deletion. Using --target with --delete requires an include or exclude option, and the guide recommends a verbose dry run. Completion cannot establish removal of extras outside that selected scope.

Source: restic v0.19.1 — 050_restore. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does restic restore --delete remove every extra file from the entire target tree?

Buyer evidence still required

  • Snapshot and restore target
  • Include/exclude scope and verbose dry-run listing
  • Actual deletion results and residual inventory

Review inference: Bound destructive recovery cleanup to the authorised target subset. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse whole-tree cleanup from a filtered restore-delete operation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No cleanup operation or residual file inventory was examined.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No cleanup operation or residual file inventory was examined.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic restore content shortcuts

Question: Does restic restore --overwrite if-changed compare all existing file bytes before deciding they match?

The v0.19.1 guide says if-changed assumes files with matching size and modification time are current, checking full content when those attributes differ. The default always mode verifies existing content and restores mismatching parts. Interrupted in-place restoration can leave partial results. Matching metadata under if-changed therefore does not establish byte equality or completed recovery.

Source: restic v0.19.1 — 050_restore. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does restic restore --overwrite if-changed compare all existing file bytes before deciding they match?

Buyer evidence still required

  • Overwrite mode and target file metadata
  • Content-verification and restore completion results
  • Pre-restore recovery point and interruption history

Review inference: Choose recovery evidence appropriate to metadata shortcuts and interruption risk. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse byte-equality assurance based solely on unchanged size and modification time.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Target contents and restoration completeness remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Target contents and restoration completeness remain unverified.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic retention grouping

Question: Does restic keep-last apply one retention count across every backed-up host and path?

restic v0.19.1 groups snapshots by host name and paths before applying a retention policy independently to each group. group-by can change those keys or disable grouping, while host and tag filters further restrict selection. A keep count without its grouping and filtering context cannot establish which backup sets were retained or removed.

Source: restic v0.19.1 — 060_forget. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does restic keep-last apply one retention count across every backed-up host and path?

Buyer evidence still required

  • Snapshot host, path and tag metadata
  • Effective group-by, host and tag selection
  • Dry-run selection and actual forget results

Review inference: Review the actual backup sets affected by an automated retention run. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse a repository-wide retention count without the applied grouping and filters.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer retention selection or legal retention requirement was evaluated.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No buyer retention selection or legal retention requirement was evaluated.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic retention window anchor

Question: Is restic keep-within measured back from the time the retention job runs?

The v0.19.1 retention guide measures keep-within against the latest snapshot, rather than simply the current wall clock. Calendar keep options count periods containing snapshots and use natural boundaries; future-dated snapshots are ignored by duration-related options and are not removed by them. An apparently old snapshot set therefore needs its timestamps and policy basis reconciled before declaring a retention breach or deletion completion.

Source: restic v0.19.1 — 060_forget. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Is restic keep-within measured back from the time the retention job runs?

Buyer evidence still required

  • Snapshot timestamps and clock context
  • Exact calendar or duration retention options
  • Selection output for the retention run

Review inference: Interpret a retention window against the documented snapshot-time basis. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse a wall-clock expiry conclusion based only on a keep-within duration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The accuracy of snapshot timestamps and buyer policy applicability are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The accuracy of snapshot timestamps and buyer policy applicability are unknown.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic sampled integrity coverage

Question: Do repeated random restic data-subset checks guarantee that every pack has been inspected?

The v0.19.1 guide allows a fixed n/t subset partition or a random percentage/size subset for pack-data checking. Repeating random subsets does not guarantee complete repository coverage, even across many runs. A partitioned plan can cover the specified partitions, but its receipts and repository scope must be retained rather than inferred from the number of successful random checks.

Source: restic v0.19.1 — 045_working_with_repos. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Do repeated random restic data-subset checks guarantee that every pack has been inspected?

Buyer evidence still required

  • Subset mode and parameters for each run
  • Repository pack inventory and changes over the interval
  • Retained results for required partitions or full-data check

Review inference: Avoid converting successful random samples into an unsupported full-coverage claim. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse complete inspection coverage from repeated random-sample success alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual coverage of a changing buyer repository is not known.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual coverage of a changing buyer repository is not known.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic snapshot selection versus restored scope

Question: Does restic restore --path restrict restoration to only that path inside the snapshot?

The restic v0.19.1 restore guide says --path selects a snapshot and does not restrict which files inside it are restored. A snapshot selected by one path can contain other paths that are also restored. File-scope selection instead uses include/exclude options or snapshot:subfolder syntax, with filter paths interpreted relative to that selected subfolder.

Source: restic v0.19.1 — 050_restore. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does restic restore --path restrict restoration to only that path inside the snapshot?

Buyer evidence still required

  • Selected snapshot and its full path inventory
  • Restore target and include/exclude or subfolder scope
  • Dry-run listing and authorised recovery scope

Review inference: Prevent unintended data disclosure or overwrite when selecting a recovery subset. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse a path-restricted restore claim based on --path selection alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual restored content and authorisation were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual restored content and authorisation were not inspected.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic structural checks and payload reads

Question: Does a successful default restic check verify every stored backup payload byte?

restic v0.19.1 distinguishes the default repository-structure check from reading actual pack data. check --read-data reads all packs, while data-subset options limit that work. A successful default check therefore supports structural consistency within its checks, not a claim that every stored data payload was read or that an application restore succeeded.

Source: restic v0.19.1 — 045_working_with_repos. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a successful default restic check verify every stored backup payload byte?

Buyer evidence still required

  • Exact check command and version
  • Check result with payload-read scope
  • Independent restore and application validation evidence

Review inference: Match a backup assurance statement to the checks actually executed. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse all-payload or application-recovery assurance from default check success alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Application recoverability and all payload contents were not verified here.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Application recoverability and all payload contents were not verified here.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

restic Windows security descriptor restoration

Question: Does restoring files with restic on Windows always restore their complete security descriptors?

The v0.19.1 restore guide requires SeRestorePrivilege, SeSecurityPrivilege and SeTakeOwnershipPrivilege, or administrator operation, for full Windows security-descriptor restoration. Without all required privileges only the DACL is restored. Symlink restoration has a separate privilege requirement. File-content recovery alone therefore does not establish equivalent security metadata on the destination.

Source: restic v0.19.1 — 050_restore. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does restoring files with restic on Windows always restore their complete security descriptors?

Buyer evidence still required

  • Restoring identity and effective privileges
  • Source and destination security descriptors
  • Restore warnings and content/security acceptance results

Review inference: Review security metadata separately when accepting a Windows recovery. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse full access-metadata equivalence from file restoration alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Effective destination permissions and audit configuration were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Effective destination permissions and audit configuration were not tested.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Restore testing: Completion and workload validation

Question: Does a completed AWS Backup restore test prove the application works?

Restore-test completion can trigger a separate, optional validation workflow. The buyer defines checks such as a health endpoint and reports their result. A COMPLETED restore job and a successful workload validation are distinct evidence; the sample validation code is not itself proof that useful checks were implemented.

Source: AWS Backup restore testing. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Restore completion automatically establishes usable application recovery.

Buyer evidence still required

  • Restore-job identity and completion event.
  • Actual validation logic and execution logs.
  • Reported validation status and workload scope.

Suggested review condition: Require executed validation of the needed behaviour before asserting application recovery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Restore job, validation workflow, resource identity and tested workload behaviour.

Optional saved evidence: Save the evidence requirements behind a supplier recovery claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Retool MCP: Building, query and administration scope

Question: Does connecting Retool MCP only expose app previews?

Retool's inbound MCP can inspect apps, build or change them, execute resource queries and perform selected administrative tasks according to authorized scopes. It differs from a Retool resource that connects outward to another MCP server. App-building uses both the external development agent and Retool's building service; credit usage remains a separate commercial prerequisite.

Source: Retool MCP scopes and operations. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; deployed buyer configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Retool provides the server on the selected instance.

Documented by publisher. Retool MCP scopes and operations; Retool inbound and outbound MCP distinctions

Purpose

Build apps and manage selected Retool resources.

Documented by publisher. Retool MCP scopes and operations; Retool inbound and outbound MCP distinctions

Read capability

App, resource and authorized organization information.

Documented by publisher. Retool MCP scopes and operations; Retool inbound and outbound MCP distinctions

Write capability

Build or change apps, execute queries and perform scoped administration.

Documented by publisher. Retool MCP scopes and operations; Retool inbound and outbound MCP distinctions

Authentication

OAuth on the selected Retool instance.

Documented by publisher. Retool MCP scopes and operations; Retool inbound and outbound MCP distinctions

Permission surface

Read, write and admin scope selection must match user authority.

Documented by publisher. Retool MCP scopes and operations; Retool inbound and outbound MCP distinctions

Data leaving the environment

Prompts and selected resource data can pass between client and Retool services.

Review inference. Retool MCP scopes and operations; Retool inbound and outbound MCP distinctions

Failure modes to consider

Broad building or admin scope can exceed an inspection-only task.

Review inference. Retool MCP scopes and operations; Retool inbound and outbound MCP distinctions

Unknowns and applicability

Effective resource access, self-hosted version and credit entitlement are unverified.

Not established

Suggested refusal or clarification condition

Require authority for query effects and app changes rather than inferring it from a preview request.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Scope definitions, supported self-hosted versions, query tools and credit terms.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve a scoped app-building and data-access decision without purchasing additional assurance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Reusable workflows: Token permission ceilings

Question: Can a reusable GitHub workflow grant itself broader GITHUB_TOKEN permissions than its caller?

Nested reusable workflows can retain or reduce the caller token permissions, not elevate them. The actual permission chain therefore matters when diagnosing an operation or reviewing claimed isolation. This constraint concerns GITHUB_TOKEN; it does not establish the scope of other credentials supplied to the job.

Source: GitHub: Reusing workflow configurations. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A called workflow can independently elevate its inherited job token.

Buyer evidence still required

  • Caller and nested workflow references.
  • Effective GITHUB_TOKEN permissions at each call.
  • Inventory of other credentials available to the job.

Suggested review condition: Review the complete credential set before treating the token ceiling as total privilege isolation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Caller/callee revisions, token permissions and separately supplied credentials.

Optional saved evidence: Save the authority chain used to review a reusable deployment workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Rovo: GitHub index cleanup has an additional dependency

Question: Does disconnecting GitHub from Rovo alone remove its indexed GitHub content?

Atlassian documents a GitHub-specific exception to connector cleanup: removing indexed GitHub data requires disconnecting GitHub from Rovo and uninstalling GitHub for Jira. A Rovo disconnect alone does not satisfy that documented prerequisite.

Source: Rovo data privacy and usage guidelines. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does disconnecting GitHub from Rovo alone remove its indexed GitHub content?

Buyer evidence still required

  • The Rovo connector state.
  • The GitHub for Jira installation state.
  • Subsequent scoped index checks.

Suggested review condition: Do not close GitHub cleanup while the shared Jira integration remains installed or removal evidence is missing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The Rovo connector state. The GitHub for Jira installation state. Subsequent scoped index checks.

Optional saved evidence: A connector owner must reconcile the shared Jira integration before declaring GitHub offboarding complete.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Deletion from GitHub itself or every downstream copy
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Rovo: Hosted-model selection changes the processor boundary

Question: Does a Rovo no-training commitment restrict processing to our single approved external LLM provider?

Atlassian describes normal Rovo routing across hosted and third-party models and says that routing cannot be limited to one preferred external provider. Its Cloud Enterprise hosted-LLM option instead keeps LLM processing within the Atlassian Cloud boundary, at organization scope. No-training terms do not specify a single processing supplier.

Source: Atlassian-hosted LLMs. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Rovo no-training commitment restrict processing to our single approved external LLM provider?

Buyer evidence still required

  • The organisation plan and hosted-LLM setting.
  • Approved processing suppliers and scope.
  • Current feature availability and configuration evidence.

Suggested review condition: Do not equate a no-training commitment with exclusive use of the buyer-approved external model provider.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The organisation plan and hosted-LLM setting. Approved processing suppliers and scope. Current feature availability and configuration evidence.

Optional saved evidence: A supplier-review owner must identify whether the actual model-routing configuration matches approved subprocessors.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Absence of cloud hosting subprocessors or independent verification of processing paths
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Rovo: Provider retention and hosted chat retention differ

Question: Does Rovo provider zero retention mean Atlassian keeps no chat inputs or outputs?

The Rovo privacy guide says its LLM providers do not retain inputs and outputs, while Atlassian retains Chat and agent inputs and outputs for 30 days for safety and security. Provider and application storage are separate boundaries.

Source: Rovo data privacy and usage guidelines. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Rovo provider zero retention mean Atlassian keeps no chat inputs or outputs?

Buyer evidence still required

  • The specific Rovo feature.
  • The current application privacy terms.
  • Separate provider and Atlassian storage scope.

Suggested review condition: Do not present provider retention terms as erasure of Atlassian application records.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The specific Rovo feature. The current application privacy terms. Separate provider and Atlassian storage scope.

Optional saved evidence: A procurement reviewer must separate subprocessor retention from the hosted application data lifecycle.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Customer-specific erasure or coverage of third-party Marketplace agents
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

RunState integrity before approval recovery

Question: Do schema validation and context_override authenticate an OpenAI RunState snapshot submitted by a reviewer?

The pinned Python SDK guidance says RunState.from_json and from_string restore execution state without authenticating the snapshot or its submitter. Schema checks, tool-call fingerprints, strict_context, context_override or removing approval records do not make untrusted state safe. The application must verify complete integrity, ownership and replay protection before deserializing a client-carried snapshot.

Source: OpenAI Agents Python human-in-the-loop guide, v0.24.0. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do schema validation and context_override authenticate an OpenAI RunState snapshot submitted by a reviewer?

Buyer evidence still required

  • Exact installed version, provider variant and effective non-secret configuration
  • Relevant pending-call identifiers, declared arguments and decision provenance without secrets
  • Application-owned review policy and independently observed outcomes where needed

Review inference: Use server-owned pending state or application-verified complete snapshots; refuse to infer reviewer authority from IDs, context replacement or a valid schema. The Agent Framework record concerns pickle reconstruction and allowed types. This JSON-state decision concerns client-controlled pending calls and arguments surviving context replacement, and complete-snapshot authentication before resume. Operational review inference; no deployment outcome was observed.

Suggested review condition: Use server-owned pending state or application-verified complete snapshots; refuse to infer reviewer authority from IDs, context replacement or a valid schema.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Long-running approvals / Keep approval state on the server

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Use server-owned pending state or application-verified complete snapshots; refuse to infer reviewer authority from IDs, context replacement or a valid schema.
  • A complete integrity-protected snapshot bound to an authorised user/run with replay controls can satisfy application checks; those checks neither encrypt its contents nor prove external success.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Derived claim boundary

S1 reference: Certification boundary

Question: Does S1 reference compatibility establish safety certification?

The S1 spectral alarm reference supports bounded compatibility signalling. Its public source explicitly excludes safety certification.

Derived from BDAS S1 Spectral Alarm — Reference Compatibility Record. No new experiment or validation is claimed.

Claim boundaries
  • safety certification
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

S1 spectral replay: Production alarm boundary

Question: Does S1 exact replay establish a production alarm system?

The S1 replay public source supports bounded exact-replay and diagnostic evidence. It excludes a production alarm system claim.

Derived from BDAS S1 Spectral Replay — Exact Replay Evidence. No new experiment or validation is claimed.

Claim boundaries
  • production alarm system
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 access logs: Missing records do not establish no request

Question: Can S3 server access logs prove that every request was recorded exactly once?

S3 describes server access logging as best effort, with neither completeness nor timeliness guaranteed. Records can arrive late, be duplicated or be absent. These logs support traffic review, but a missing entry alone cannot establish that a request never occurred.

Source: S3 server access log delivery. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Server access logs are a complete, timely, exactly-once request ledger.

Buyer evidence still required

  • Logging configuration and destination history.
  • Observed delivery delays and duplicate handling.
  • Additional evidence for any claim based on a missing request.

Suggested review condition: Do not infer no access solely from an absent server access-log record.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Logging state, destination changes, delivery delay and independent request evidence

Optional saved evidence: Retain the completeness boundary behind a bucket-access investigation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 access-point removal and remaining bucket access

Question: Does deleting one S3 access point revoke access through other access points or the bucket hostname?

AWS states that removing an access point does not disrupt access through other access points or the bucket hostname. Access-point policy restrictions apply to requests using that access point; attaching one does not change other bucket operations. Removing a connector-specific path therefore does not establish complete bucket offboarding.

Source: Amazon S3 FAQs - Cloud Object Storage - AWS. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting one S3 access point revoke access through other access points or the bucket hostname?

Buyer evidence still required

  • Deleted access-point identity and affected principal
  • Other access points, bucket policy and identity grants
  • Required revocation scope and independent access checks

Review inference: Inventory direct bucket and other access-point permissions before declaring all access revoked.

Suggested review condition: Refuse complete access revocation when alternate bucket routes remain unevaluated.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual alternate grants and continuing access are not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Find residual access paths left after removing a single storage integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Global bucket-access revocation from deleting one access point
  • Actual alternate grants and continuing access are not tested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 Batch Operations: Complete jobs can contain failed object tasks

Question: Does a Complete S3 Batch Operations job prove every manifest object's operation succeeded?

S3 Batch Operations marks a job Complete after processing the requested manifest operations, which may have succeeded or failed per object. Optional completion reports can include all tasks or failed tasks only and identify object keys, versions and outcomes. Job status alone does not prove every object's success.

Source: Tracking job status and completion reports. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Complete S3 Batch Operations job prove every manifest object's operation succeeded?

Buyer evidence still required

  • Job identity, operation and manifest with object version scope
  • Completion-report configuration and available task-result files
  • Per-object success, failure and any separate recovery outcomes

Review inference: A review should reconcile manifest coverage with the selected report scope and residual failures.

Suggested review condition: Refuse all-objects-succeeded claims based only on Complete status or an unexplained report count.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer manifest completeness, task results and recovery of failed objects are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Close bulk migration or exit work using object outcomes rather than a job-level completion label.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof of full bucket coverage, physical deletion, successful application restore or off-manifest outcomes
  • Equivalence with the synchronous DeleteObjects API or a current S3 Inventory snapshot
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 lifecycle expiration and retained versions

Question: Does an S3 Lifecycle Expiration action permanently remove all versions of an object in a versioned bucket?

In a versioning-enabled bucket, Expiration can make a delete marker current while the former current object becomes noncurrent. The action applies to current versions and does not remove noncurrent versions. Those require separately configured noncurrent-version expiration, subject to documented lock and replication constraints. An ordinary lookup returning no object is not an all-version deletion inventory.

Source: Expiring objects - Amazon Simple Storage Service. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an S3 Lifecycle Expiration action permanently remove all versions of an object in a versioned bucket?

Buyer evidence still required

  • Bucket versioning state and lifecycle rule actions
  • Current, noncurrent and delete-marker version inventory
  • Object Lock and replication state for targeted versions

Review inference: Check version IDs and noncurrent cleanup rules separately from the current object’s visibility.

Suggested review condition: Do not attest all-version erasure from a current-object delete marker or expiration rule alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual remaining versions and lifecycle execution have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Identify hidden retained versions before declaring a storage exit complete.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Deletion of every stored version from current-object expiration
  • Actual remaining versions and lifecycle execution have not been inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 Lifecycle: Billing changes and physical removal

Question: Does storage billing stopping prove an S3 object has already been deleted?

Lifecycle actions can be queued after an object becomes eligible. Billing changes normally follow eligibility even if the action happens later, with documented exceptions for some transitions. Therefore billing status or a scheduled expiration is not an object-level deletion receipt.

Source: S3 lifecycle actions and billing. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Lifecycle billing state proves completed physical deletion.

Buyer evidence still required

  • Lifecycle rule filters and action type.
  • Object version and eligibility date.
  • Object-level action evidence and retained versions.

Suggested review condition: Do not use a billing change as proof that all object versions were removed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Lifecycle filters, action, storage class, versioning and object-level state.

Optional saved evidence: Save a bounded retention review that distinguishes invoices from removal evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 Object Lock: Protected versions and current visibility

Question: Does locking an S3 object version prevent new versions or delete markers?

No. AWS describes Object Lock as protection for specified versions. Retention and legal holds do not prevent a new version or a delete marker above the protected version. Distinguish retained-version protection from the object currently returned by an ordinary lookup.

Source: S3 Object Lock modes, versions and deletion. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A locked object key can never be replaced or disappear from current lookup.

Buyer evidence still required

  • Protected version identifier and applicable lock
  • Current version or delete-marker state
  • Retrieval evidence for the exact retained version

Suggested review condition: Require version-specific evidence before claiming immutability of the current object view.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck lock settings, version changes and retrieval procedures.

Optional saved evidence: Save the version and visibility distinction used in an evidence-retention review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 presigned URLs: Reuse and credential-bound lifetime

Question: Is an S3 presigned download a single-use link valid until its stated expiry?

The documentation allows repeated use before expiry. Temporary signing credentials can expire earlier than the URL setting, and a download begun before expiry can continue afterwards. Review reuse requirements and credential lifetime separately from the displayed expiration; the URL alone does not implement single-use delivery.

Source: S3 presigned URL lifetime and reuse. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The signed URL is single-use and its expiry is the complete access boundary.

Buyer evidence still required

  • Signing identity type and credential expiration.
  • Configured URL expiry, method and object binding.
  • Any separate single-use enforcement and observed download behaviour.

Suggested review condition: Do not claim single-use access without an additional evidenced control.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Credential lifetime, URL policy and any application-level use limit.

Optional saved evidence: Preserve the delivery assumptions that a signed URL does and does not support.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 private paths: Endpoint existence and enforced restriction

Question: Does creating an S3 VPC endpoint prove the bucket can only be reached through it?

The documented restriction uses a bucket policy tied to a VPC or endpoint condition. Endpoint existence is not that policy evidence. An explicit deny can also block console access and cause lockout if the identifier is wrong, so the effective policy and intended alternate access require review.

Source: S3 bucket policies and VPC endpoints. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An S3 endpoint automatically restricts every bucket access path.

Buyer evidence still required

  • Bucket policy and referenced endpoint/VPC.
  • Identity permissions and alternate access paths.
  • Authorized validation and recovery access plan.

Suggested review condition: Require the enforcing policy before claiming private-path-only access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Bucket policy, endpoint identity, callers and alternate access

Optional saved evidence: Save the policy and access-path evidence behind a private-storage claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 public-access blocks: Retained grants and scope

Question: Does enabling S3 Block Public Access remove the old public grants?

The settings can reject new public grants or ignore their effects without rewriting existing ACLs and policies. Their behaviours differ, and the most restrictive applicable combination governs access. A blocking setting is not evidence that underlying grants were cleaned up or that every non-public access path is appropriate.

Source: S3 Block Public Access. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A public-access block deletes the underlying public grants and proves least privilege.

Buyer evidence still required

  • All applicable block settings and policy levels.
  • Retained bucket policies and ACLs.
  • Authorized access paths and change history.

Suggested review condition: Inspect retained grants and effective settings before relying on later removal of a block.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Organization, account, bucket and access-point settings, ACLs and policies.

Optional saved evidence: Save the difference between disabling a grant effect and removing the grant.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3 replication: Copies and deletion propagation are different

Question: Does S3 replication keep every source and destination deletion state identical?

Replication has documented exclusions, including specific object-version deletions and lifecycle-related behaviour. Existing objects and already replicated objects can require separate batch handling. Review the replication rule, delete-marker behaviour and version identity rather than assume a destination is a complete real-time mirror.

Source: S3 replication coverage and exclusions. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Replication guarantees identical deletion state for every object version.

Buyer evidence still required

  • Source/destination rules and delete-marker configuration.
  • Version-specific deletion and lifecycle behaviour.
  • Evidence of existing-object coverage and destination reconciliation.

Suggested review condition: Do not infer a complete mirror or erasure outcome from enabled replication.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Replication rules, version IDs, lifecycle and reconciliation

Optional saved evidence: Preserve the version and rule exceptions relevant to backup and erasure assumptions.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3: Completion errors inside HTTP 200 responses

Question: Does HTTP 200 from S3 CompleteMultipartUpload establish that the final object was created?

S3 can send HTTP 200 headers while CompleteMultipartUpload is still processing and later embed an error in that response body. Direct callers must parse the complete response; AWS SDKs detect embedded errors and apply their configured handling. The status line alone does not establish successful final object assembly.

Source: Amazon S3: CompleteMultipartUpload. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does HTTP 200 from S3 CompleteMultipartUpload establish that the final object was created?

Buyer evidence still required

  • Upload ID, submitted part list and expected final object identity.
  • Complete response body or SDK result, including retries and exceptions.
  • Final object observation tied to the intended upload and contents.

Suggested review condition: Decline object-ready claims based only on HTTP status; inspect completion content and final object evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Upload ID, submitted part list and expected final object identity. Complete response body or SDK result, including retries and exceptions. Final object observation tied to the intended upload and contents.

Optional saved evidence: A transport-level success can cause an agent to declare an artifact ready before finalization has actually succeeded.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof of artifact correctness, automatic retry safety or live object verification
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3: Multipart abort and remaining uploaded parts

Question: Does one S3 multipart abort prove all in-flight parts and their storage charges are gone?

S3 states that part uploads already in progress may or may not succeed after a multipart abort. Repeated aborts can be needed to free all part storage. AWS directs operators to use ListParts and verify an empty list. The abort response alone is not complete cleanup evidence for concurrent uploads.

Source: Amazon S3: AbortMultipartUpload. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does one S3 multipart abort prove all in-flight parts and their storage charges are gone?

Buyer evidence still required

  • Bucket, object and upload ID with in-flight part attempts.
  • Abort results and completion state of concurrent part uploads.
  • ListParts results and any remaining cleanup owner or unresolved storage.

Suggested review condition: Decline complete-cleanup claims until concurrent part outcomes and the resulting parts inventory are reconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Bucket, object and upload ID with in-flight part attempts. Abort results and completion state of concurrent part uploads. ListParts results and any remaining cleanup owner or unresolved storage.

Optional saved evidence: An interrupted agent upload can leave stored parts and cost exposure after apparent cancellation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed one-call cleanup, deletion of a completed object or verified storage charges
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

S3: Repairing objects with failed replication

Question: What evidence closes recovery for an S3 object marked FAILED for replication?

AWS documents HeadObject replication status and S3 Batch Replication as a recovery path for failed objects; re-uploading instead creates new objects that initiate replication. It also warns that Batch Replication might not resolve a FAILED status in the documented destination-ownership case even when the object exists there. Destination existence and source status need reconciliation.

Source: Amazon S3: Troubleshooting replication. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: What evidence closes recovery for an S3 object marked FAILED for replication?

Buyer evidence still required

  • Source object version, replication rule and observed FAILED status.
  • Repair job or new-upload results and any destination-ownership configuration.
  • Destination version observations and unresolved status discrepancies or support findings.

Suggested review condition: Decline recovered-replica claims until source version, repair results and destination observations agree or discrepancies remain explicit.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Source object version, replication rule and observed FAILED status. Repair job or new-upload results and any destination-ownership configuration. Destination version observations and unresolved status discrepancies or support findings.

Optional saved evidence: Restoring configuration or starting a batch job does not by itself establish that the intended object version is recovered at the destination.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Identical source/destination deletion state or guaranteed recovery from any replication failure
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Salesforce Apex versioned execution defaults

Question: Does every Apex version enforce the same default field and object permissions as the Salesforce user interface?

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: Secure Apex Classes | Work with Salesforce Data | Lightning Web Components Developer Guide | Salesforce Developers. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does every Apex version enforce the same default field and object permissions as the Salesforce user interface?

Buyer evidence still required

  • Apex class API version and entry point
  • Explicit user/system mode and sharing declarations
  • Required object, field and record-level authorization checks

Review inference: Inspect the class API version and explicit query, database-operation and sharing modes.

Suggested review condition: Reject a uniform-permission claim that omits API version or explicit execution modes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer Apex code or runtime access result has been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid applying an obsolete execution-default assumption to a privileged integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • 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

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Salesforce client credentials run-as identity

Question: Can the documented Salesforce connected-app client-credentials flow operate without a configured run-as user?

Salesforce’s connected-app guide requires enabling client credentials and selecting an execution or run-as user. API actions use that user’s permissions, with the integration-user licence and permission configuration considered separately. A client identifier and secret do not replace the execution identity. This is the documented 2024 connected-app flow, not a claim about new-app provisioning defaults.

Source: Invoke REST APIs with the Salesforce Integration User and OAuth Client Credentials | Salesforce Developers Blog. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can the documented Salesforce connected-app client-credentials flow operate without a configured run-as user?

Buyer evidence still required

  • Connected-app client-credentials policy and run-as user
  • Integration-user licence and assigned permissions
  • Required API operations and their access checks

Review inference: Review the chosen integration user and least-privilege permissions alongside the OAuth configuration.

Suggested review condition: Do not approve authority from client credentials without the configured execution user.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s app type, policy and integration-user permissions are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Bind unattended API access to an explicit and reviewed integration identity.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Unrestricted API access from client secret possession
  • The buyer’s app type, policy and integration-user permissions are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Salesforce Composite: HTTP success can contain failed operations

Question: Does HTTP 200 from Salesforce Composite prove every requested change committed?

Salesforce Composite returns subrequest results inside a top-level HTTP 200, including error cases. allOrNone controls rollback; with it false, independent subrequests can continue while dependent ones do not. Nested collection settings can also affect outcomes. Each relevant result must be interpreted.

Source: Salesforce: Composite Request Body. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does HTTP 200 from Salesforce Composite prove every requested change committed?

Buyer evidence still required

  • Composite and nested allOrNone settings.
  • Every subrequest status keyed to its reference ID.
  • Committed-object evidence and intended dependency relationships.

Suggested review condition: Do not report complete success or retry the whole operation until partial outcomes are reconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Composite body, rollback flags, dependencies and individual responses.

Optional saved evidence: Retain the evidence distinguishing request acceptance, rollback and partial completion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Salesforce full scope and user permissions

Question: Does Salesforce OAuth full scope grant data access beyond the logged-in user’s assigned authority?

Salesforce defines full as access to data accessible by the logged-in user. It does not independently return a refresh token; refresh_token must be requested explicitly. API scope names describe access paths within the user context, not a replacement for the user’s underlying permissions and sharing boundary.

Source: OAuth Tokens and Scopes | Salesforce Help. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Salesforce OAuth full scope grant data access beyond the logged-in user’s assigned authority?

Buyer evidence still required

  • Authenticated user and assigned permissions
  • Requested and granted OAuth scopes
  • Relevant object, field and record access evidence

Review inference: Review user authority separately from the scope label and token-lifetime configuration.

Suggested review condition: Decline an unrestricted-data claim based only on full or API-enabled access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The user’s effective permissions and actual data access are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep a broad-sounding OAuth scope from becoming an unsupported authorization claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Bypass of user permissions or implicit refresh-token issuance from full
  • The user’s effective permissions and actual data access are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Salesforce Hosted MCP: User identity and tool authority

Question: Can a Salesforce MCP connection grant an agent unrestricted or unattended access?

The reviewed hosted service uses an External Client App and the connecting user's permissions. The documented flow is user authorization code, not a shared machine identity. Object, field and record permissions still matter; tool annotations depend on client support. Flex Credits and enabled servers need checking separately.

Source: Salesforce hosted MCP security model. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Publisher-hosted servers; custom tool configuration unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Salesforce operates the hosted service.

Documented by publisher. Salesforce hosted MCP security model; Salesforce Hosted MCP Servers overview

Purpose

Expose selected Salesforce data and automation.

Documented by publisher. Salesforce hosted MCP security model; Salesforce Hosted MCP Servers overview

Read capability

Data available to the authenticated user and selected tools.

Documented by publisher. Salesforce hosted MCP security model; Salesforce Hosted MCP Servers overview

Write capability

Enabled tools can invoke platform logic and change records.

Documented by publisher. Salesforce hosted MCP security model; Salesforce Hosted MCP Servers overview

Authentication

User OAuth through an External Client App.

Documented by publisher. Salesforce hosted MCP security model; Salesforce Hosted MCP Servers overview

Permission surface

User permissions and activated tools limit authority.

Documented by publisher. Salesforce hosted MCP security model; Salesforce Hosted MCP Servers overview

Data leaving the environment

Selected business data reaches the connected agent.

Review inference. Salesforce hosted MCP security model; Salesforce Hosted MCP Servers overview

Failure modes to consider

Optional annotations do not establish enforced confirmation.

Review inference. Salesforce hosted MCP security model; Salesforce Hosted MCP Servers overview

Unknowns and applicability

Buyer tool configuration, credits and effective grants are unverified.

Not established

Suggested refusal or clarification condition

Require user and task authority before invoking a changing tool.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Hosted authentication, credit requirements, activated servers and custom tool permissions.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the identity and tool-scope evidence used to approve a Salesforce integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Salesforce permission-group recalculation

Question: Does editing a Salesforce permission-set group immediately change its assigned users’ effective permissions?

Salesforce distinguishes Updated, Outdated, Updating and Failed permission-set-group states. Users do not receive the revised combined permissions until recalculation succeeds; failure leaves changes unpropagated. The guide also documents different recalculation timing for standard Salesforce-owned permission sets. Saving an edit is not proof that the effective combined permission set changed.

Source: Permission Set Group Status and Recalculation | Salesforce Help. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does editing a Salesforce permission-set group immediately change its assigned users’ effective permissions?

Buyer evidence still required

  • Permission-set group and modified component
  • Recalculation status and completion time
  • Assigned user and effective permission evidence

Review inference: Check recalculation status and effective assignments before accepting a grant or restriction as complete.

Suggested review condition: Do not confirm a permission change while recalculation is outstanding or failed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual group status and user authority are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent premature access approvals and offboarding sign-off.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Immediate permission propagation from an edited group
  • Actual group status and user authority are unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Sanity MCP: Drafts, publication and release metadata

Question: Does creating a Sanity release through MCP schedule its publication?

Sanity documents that creating a release records metadata but does not schedule it. Document patching saves drafts or release versions, while separate tools can publish documents. Agents should distinguish a saved draft, a release record and actual publication evidence.

Source: Sanity MCP authentication, document drafts and publication tools. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Sanity hosted workspace MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Sanity hosts the workspace MCP service.

Documented by publisher. Sanity MCP authentication, document drafts and publication tools

Purpose

Expose content queries, document changes and project-management tools.

Documented by publisher. Sanity MCP authentication, document drafts and publication tools

Read capability

Queries documents, schemas, datasets and release state.

Documented by publisher. Sanity MCP authentication, document drafts and publication tools

Write capability

Can create or patch drafts, publish documents and manage supported project resources.

Documented by publisher. Sanity MCP authentication, document drafts and publication tools

Authentication

OAuth is the default; an explicit API token uses its own role and permissions.

Documented by publisher. Sanity MCP authentication, document drafts and publication tools

Permission surface

API-token calls follow token scope; personal tokens inherit user permissions.

Documented by publisher. Sanity MCP authentication, document drafts and publication tools

Data leaving the environment

Content and schema results enter the AI client; some tools invoke additional AI processing.

Review inference. Sanity MCP authentication, document drafts and publication tools

Failure modes to consider

A release record may be mistaken for a schedule; retries can repeat uncertain operations.

Review inference. Sanity MCP authentication, document drafts and publication tools

Unknowns and applicability

The buyer project grants, document state and downstream publishing configuration are unknown.

Not established

Suggested refusal or clarification condition

Do not report scheduled or published content from draft or release creation alone; require the intended state and evidence.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck tool semantics, token scope and target dataset before relying on an older review.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the distinction between content preparation and completed publication.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Secret Manager schedules: Notification is not completed rotation

Question: Does configuring a Secret Manager rotation schedule replace the credential and update every application?

The schedule sends a Pub/Sub rotation notification. A subscriber must perform the required work, such as creating a new secret version and deploying it to consumers. Notification retries and skipped in-flight schedules also matter; the configured timer alone is not proof of completed rotation.

Source: Secret Manager rotation schedules. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A rotation schedule automatically replaces and deploys the credential.

Buyer evidence still required

  • Schedule and Pub/Sub delivery evidence.
  • Subscriber action and new-version evidence.
  • Consumer rollout and old-credential retirement.

Suggested review condition: Require completion evidence beyond the scheduled notification.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Schedule, topic delivery, subscriber action, rollout and retirement

Optional saved evidence: Preserve the notification-to-rollout chain behind a credential-rotation claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Secret Manager: Scheduled destruction and recoverability

Question: Does a destroy request always mean secret material is already irrecoverable?

Secret-version destruction is immediate by default, but a configured destruction delay preserves a recovery interval. During that delay the version is scheduled for destruction and authorized administrators can cancel it. A request acknowledgement must therefore be interpreted with the secret's delay configuration and actual version state.

Source: Secret Manager delayed destruction. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A destroy request proves irreversible destruction in every configuration.

Buyer evidence still required

  • Secret destruction-delay setting.
  • Version state and scheduled destruction time.
  • Authorized recovery actions and final-state evidence.

Suggested review condition: Do not claim irreversible destruction while a configured recovery interval remains.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Secret and version identity, destruction delay, administrator grants and state timestamps.

Optional saved evidence: Preserve the evidence distinguishing access disablement, pending destruction and final destruction.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Secret rotation: Stored value and external service

Question: Does enabling rotation for a non-database secret prove the external credential changed?

Lambda-based rotation must update credentials in both Secrets Manager and the target service. The generic function needs service-specific code, permissions and network access. A configured schedule or newly stored value alone does not establish a successful external change or that applications use the replacement.

Source: Secrets Manager rotation for other secrets. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A rotation schedule proves the external credential and all consumers are current.

Buyer evidence still required

  • Service-specific rotation implementation and execution outcome.
  • Target-service credential evidence.
  • Consumer retrieval and authentication evidence.

Suggested review condition: Require evidence of the target update and consumer use before treating rotation as completed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Secret type, Lambda code, permissions, connectivity, target state and consumers.

Optional saved evidence: Save the evidence checklist for a supplier credential-rotation assurance claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Semantic Kernel: Experimental orchestration scope

Question: Does a documented multi-agent orchestration pattern mean its SDK implementation is stable?

The Semantic Kernel orchestration page labels its implementation experimental and warns that it may change before preview or release-candidate status. It lists concurrent, sequential, handoff, group-chat and Magentic patterns, while stating that orchestration is unavailable in its Java SDK. Retain the package, language and review date when assessing suitability; a pattern description is not a compatibility or production-readiness guarantee.

Source: Semantic Kernel Agent Orchestration. Documentation checked 2026-10-09; no deployment validation is claimed.

Claim boundaries
  • stable API or upgrade compatibility
  • availability in every language SDK
  • validated reliability of a buyer workflow

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Semgrep Guardian: Available scan tools and enforced checks

Question: Does installing Semgrep MCP prove every agent code change was scanned?

Semgrep distinguishes callable MCP scanning tools from event-triggered hooks. Tool availability alone does not prove invocation or coverage of a particular revision. Its former standalone MCP repository is archived and points to the main Semgrep distribution, so verify the installed integration and retain actual scan evidence.

Source: Semgrep Guardian MCP, hooks and scanning scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Current Guardian integration; archived standalone server distinguished

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Semgrep publishes Guardian and the current Semgrep distribution.

Documented by publisher. Semgrep Guardian MCP, hooks and scanning scope; Semgrep MCP tool availability and hook enforcement; Semgrep archived MCP repository migration notice

Purpose

Expose scanning capabilities to coding agents and support workflow checks.

Documented by publisher. Semgrep Guardian MCP, hooks and scanning scope; Semgrep MCP tool availability and hook enforcement; Semgrep archived MCP repository migration notice

Read capability

Code or findings within the selected scan and integration scope.

Documented by publisher. Semgrep Guardian MCP, hooks and scanning scope; Semgrep MCP tool availability and hook enforcement; Semgrep archived MCP repository migration notice

Write capability

Remediation or local file changes depend on the agent and configured workflow; not independently established.

Not established. Semgrep Guardian MCP, hooks and scanning scope; Semgrep MCP tool availability and hook enforcement; Semgrep archived MCP repository migration notice

Authentication

The exact buyer authentication and account setup are not established by this review.

Not established. Semgrep Guardian MCP, hooks and scanning scope; Semgrep MCP tool availability and hook enforcement; Semgrep archived MCP repository migration notice

Permission surface

Effective local file access and organizational policy require configuration evidence.

Not established. Semgrep Guardian MCP, hooks and scanning scope; Semgrep MCP tool availability and hook enforcement; Semgrep archived MCP repository migration notice

Data leaving the environment

Determine code, findings and telemetry recipients for the selected integration before use.

Not established. Semgrep Guardian MCP, hooks and scanning scope; Semgrep MCP tool availability and hook enforcement; Semgrep archived MCP repository migration notice

Failure modes to consider

A tool can be installed but never invoked, or scan a different revision.

Review inference. Semgrep Guardian MCP, hooks and scanning scope; Semgrep MCP tool availability and hook enforcement; Semgrep archived MCP repository migration notice

Unknowns and applicability

Actual hooks, permissions, data flow and completed scan coverage remain unverified.

Not established

Suggested refusal or clarification condition

Do not claim a revision was checked without a matching scan record and demonstrated trigger coverage.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck distribution migration, hook configuration, scan policy and retained results.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve why scanner installation was insufficient evidence of a checked code revision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Semgrep: Excluded files and ignored findings

Question: Does an empty Semgrep findings list prove every relevant file was scanned?

File or folder exclusions prevent findings from being generated for that scope. Ignoring through triage is different: a finding exists but has an Ignored state. Default and configured ignore patterns affect coverage. A buyer needs scan scope and triage evidence, not just the visible findings count.

Source: Semgrep: Ignore files, folders and code. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: No displayed findings establishes complete clean coverage.

Buyer evidence still required

  • Included and excluded paths for the exact revision.
  • Applied ignore patterns and rule selection.
  • Finding states and scan completion evidence.

Suggested review condition: Separate unscanned scope from ignored findings before accepting a clean-result claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Revision, scan scope, ignore configuration, rules and finding states.

Optional saved evidence: Save the scan-coverage and exception basis used in procurement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SensorThings API conformance and access controls

Question: Does SensorThings Sensing conformance establish authenticated access and permission enforcement?

SensorThings Sensing 1.1 states that it does not define specific security capabilities and describes use of existing security mechanisms across the architecture. Its data and operation model therefore does not independently demonstrate authentication or authorization in a deployment. Buyers need the actual service access policy and enforcement evidence for the intended read, create or delete operation.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does SensorThings Sensing conformance establish authenticated access and permission enforcement?

Buyer evidence still required

  • Service authentication mechanism
  • Principal and operation access policy
  • Deployment authorization evidence

Review inference: Verify operation authority separately from data-model conformance. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse access-control approval based only on SensorThings conformance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual service identity and permission enforcement were not reviewed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual service identity and permission enforcement were not reviewed.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings batch envelopes and failed operations

Question: Does HTTP 200 for a SensorThings batch establish success of every enclosed request?

SensorThings Sensing 1.1 defines multipart batch responses and includes an example where the outer response is 200 while an enclosed query fails. The outer status must therefore be distinguished from individual operation results. This observation does not establish atomicity for every batch or changeset; the buyer must inspect the applicable operation and transaction rules.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does HTTP 200 for a SensorThings batch establish success of every enclosed request?

Buyer evidence still required

  • Original batch operation order
  • Full multipart response statuses
  • Applicable changeset and retry policy

Review inference: Reconcile each operation before accepting a multi-request outcome. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse every-operation-succeeded claims from the batch envelope status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual operation persistence and changeset atomicity were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual operation persistence and changeset atomicity were not tested.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings bulk creation and per-observation errors

Question: Does SensorThings CreateObservations returning 201 mean that every submitted observation was created?

SensorThings Sensing 1.1 dataArray creation returns 201 with an ordered response array. Each element is the created observation URL or the string error when that individual creation failed. A successful outer status therefore does not establish complete import; buyers need to reconcile each response position with the corresponding submitted observation.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does SensorThings CreateObservations returning 201 mean that every submitted observation was created?

Buyer evidence still required

  • Ordered submitted observations
  • Full ordered response array
  • Created observation URLs and failed positions

Review inference: Identify failed rows before marking a bulk import complete or retrying it. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse all-observations-created claims from HTTP 201 alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual persisted observations and retry safety were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual persisted observations and retry safety were not tested.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings deletion and related observation loss

Question: Can deleting a SensorThings Datastream leave all its linked observations intact?

SensorThings Sensing 1.1 deletion rules remove entity relations and specify integrity cascades, including deleting observations linked to a deleted Datastream. Deleting a Sensor or ObservedProperty also deletes linked Datastreams. Buyers should assess these dependencies before removal; API entity deletion does not independently prove erasure of backups or other stored copies.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can deleting a SensorThings Datastream leave all its linked observations intact?

Buyer evidence still required

  • Entity and relationship inventory
  • Requested deletion target
  • Retention and backup evidence outside the API

Review inference: Assess the observation impact before deleting metadata entities. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse preservation claims that ignore deletion dependencies or physical-erasure claims based only on API deletion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual cascade execution and residual copies were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual cascade execution and residual copies were not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings device locations and observed targets

Question: Can a SensorThings Thing location be substituted for the location of what was actually observed?

SensorThings Sensing 1.1 distinguishes a Thing location from an observation FeatureOfInterest. In remote sensing, the observed feature may be somewhere other than the sensing Thing. An observation is associated with its FeatureOfInterest, so geographic attribution needs that relation rather than assuming the device location identifies the target.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a SensorThings Thing location be substituted for the location of what was actually observed?

Buyer evidence still required

  • Thing location history
  • Observation FeatureOfInterest relation
  • Remote-sensing or target-selection context

Review inference: Preserve the observed target when joining measurements to locations. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse target-location attribution based only on the sensing Thing location.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual target geometry and device position were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual target geometry and device position were not verified.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings MQTT creation and notification endpoints

Question: Does finding a SensorThings MQTT notification endpoint mean the same endpoint accepts new observations?

SensorThings Sensing 1.1 treats MQTT as an optional extension and advertises supported capabilities through serverSettings. Observation creation and update notifications have separate capability identifiers, and a service supporting both may use different endpoints. A buyer must discover the required capability and endpoint instead of inferring write support from a notification connection.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does finding a SensorThings MQTT notification endpoint mean the same endpoint accepts new observations?

Buyer evidence still required

  • Landing-page serverSettings
  • Creation and notification capability identifiers
  • Endpoint schemes and service configuration

Review inference: Select the advertised operation endpoint before integrating a sensor client. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse observation-write support claims inferred only from a notification endpoint.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual endpoint availability and write permissions were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual endpoint availability and write permissions were not tested.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings MQTT topics and observation ownership

Question: Can the SensorThings MQTT topic determine which Datastream a new observation belongs to?

SensorThings Sensing 1.1 says that when the MQTT topic is a Datastream or FeatureOfInterest navigation link, the new observation is automatically associated with that entity. HTTP creation integrity constraints and specified defaults also apply. Reconciliation must therefore retain the publication topic as well as the payload before attributing the observation to a stream or target.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can the SensorThings MQTT topic determine which Datastream a new observation belongs to?

Buyer evidence still required

  • Exact MQTT publication topic
  • Observation payload
  • Resolved Datastream or FeatureOfInterest identifiers

Review inference: Preserve topic context when attributing newly ingested data. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse ownership attribution from the payload alone when navigation-topic association applies.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual ingestion and entity association were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual ingestion and entity association were not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings multi-value alignment

Question: Can a SensorThings MultiDatastream result array be reordered without changing its meaning?

SensorThings Sensing 1.1 requires matching size and order across MultiDatastream unitOfMeasurements, ObservedProperties, observation result elements and multiObservationDataTypes. Each position carries corresponding meaning. Reordering one array without the others can associate a value with the wrong property, datatype or unit even if the payload remains syntactically valid.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a SensorThings MultiDatastream result array be reordered without changing its meaning?

Buyer evidence still required

  • Ordered properties and unit definitions
  • Result array and datatype array
  • Transformation mapping preserving positions

Review inference: Check positional semantics before transforming multi-value measurements. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse semantic-equivalence claims for a transformation without positional alignment evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual transformations and sensor values were not validated.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual transformations and sensor values were not validated.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings pagination and complete exports

Question: Does a very large SensorThings $top request guarantee that all observations arrive in one response?

SensorThings Sensing 1.1 specifies that when $top exceeds the service pagination limit, the service discards that option and applies its own page limit. The API also defines next-page links. Buyers must inspect pagination and reconcile the intended result set; a large requested limit or stable ordering alone is not proof of a complete, immutable export.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a very large SensorThings $top request guarantee that all observations arrive in one response?

Buyer evidence still required

  • Requested filter and ordering
  • Page responses and next links
  • Expected coverage and concurrent-update policy

Review inference: Follow actual paging behaviour when accounting for exported observations. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse complete-export claims from one oversized top request.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Live page coverage and snapshot consistency were not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Live page coverage and snapshot consistency were not established.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings pre-provisioned control capabilities

Question: Can a SensorThings Tasking Core client create new actuators or control capabilities as part of submitting a Task?

SensorThings Tasking Core 1.0 limits client creation to Tasks. Other entities, including TaskingCapabilities, Actuators and Things, are pre-provisioned to the server. A client therefore cannot infer capability-provisioning authority from its ability to submit a valid Task under this core specification.

Source: OGC SensorThings Part2 Tasking Core1.0, published 2019-01-08 — 17-079r1.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a SensorThings Tasking Core client create new actuators or control capabilities as part of submitting a Task?

Buyer evidence still required

  • Server pre-provisioned capability inventory
  • Client operation authorization
  • Any separately documented provisioning extension

Review inference: Separate task submission from control-surface provisioning. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse capability-creation authority inferred from core Task submission support.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Deployment extensions and actual provisioning permissions were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Deployment extensions and actual provisioning permissions were not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings server-assigned observation times

Question: Does SensorThings phenomenonTime always come from the sensing device clock?

SensorThings Sensing 1.1 permits a client to omit phenomenonTime when creating an observation. The service must then assign its current server time. A populated phenomenonTime can therefore be a server fallback rather than a device timestamp. A freshness decision needs the submitted observation and timestamp-origin policy, not just the stored field.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does SensorThings phenomenonTime always come from the sensing device clock?

Buyer evidence still required

  • Original observation submission
  • Timestamp assignment policy
  • Device clock and collection evidence

Review inference: Identify server fallback before assessing sample age. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse device-time attribution without evidence that the client supplied it.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual observation time and clock accuracy were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual observation time and clock accuracy were not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings task creation and physical completion

Question: Does creating a SensorThings Task prove the actuator completed the requested physical action?

SensorThings Tasking Core 1.0 describes checking submitted taskingParameters against the corresponding TaskingCapability and creating the Task when they are correct. A Task contains the control-action parameters that should run. This validates the declared task request; it does not independently demonstrate actuator execution or a verified physical result.

Source: OGC SensorThings Part2 Tasking Core1.0, published 2019-01-08 — 17-079r1.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does creating a SensorThings Task prove the actuator completed the requested physical action?

Buyer evidence still required

  • Created Task and parameter values
  • Applicable TaskingCapability
  • Independent actuator result evidence

Review inference: Require separate execution evidence before closing a physical-action task. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse physical-completion claims based only on Task creation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actuator execution and physical state were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actuator execution and physical state were not observed.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings task parameter constraints

Question: Can an agent submit arbitrary named fields as SensorThings taskingParameters?

SensorThings Tasking Core 1.0 defines TaskingCapability parameter descriptions and Task values using the SWE Common JSON representation. The capability defines the optional and mandatory parameters, and the server checks submitted parameters against it. Buyers should retain that definition when preparing a task; a plausible field name alone does not establish an accepted control input.

Source: OGC SensorThings Part2 Tasking Core1.0, published 2019-01-08 — 17-079r1.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an agent submit arbitrary named fields as SensorThings taskingParameters?

Buyer evidence still required

  • Capability parameter schema and constraints
  • Submitted parameter names and values
  • Validation outcome for the applicable capability

Review inference: Bind control inputs to the declared capability definition. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse valid-input claims without the corresponding parameter definition.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Runtime validation and physical safety of accepted values were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Runtime validation and physical safety of accepted values were not tested.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings task targets and capability identifiers

Question: What evidence binds a SensorThings Task to the intended TaskingCapability rather than a similarly named control?

SensorThings Tasking Core 1.0 requires each Task to link to one TaskingCapability. Creation can identify it by @iot.id in the request body or through the TaskingCapabilities identifier in the POST URL. Target reconciliation needs the effective identifier and its Actuator and Thing relations; a descriptive capability name is not a substitute for this binding.

Source: OGC SensorThings Part2 Tasking Core1.0, published 2019-01-08 — 17-079r1.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: What evidence binds a SensorThings Task to the intended TaskingCapability rather than a similarly named control?

Buyer evidence still required

  • Effective capability identifier in body or URL
  • Capability-to-Actuator and Thing relations
  • Intended target recorded by the requester

Review inference: Confirm the actual control target before accepting task attribution. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse intended-actuator attribution from a display name alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual target identity and execution were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual target identity and execution were not verified.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings units and comparable measurements

Question: Can two SensorThings result numbers be compared without their Datastream unit definitions?

SensorThings Sensing 1.1 groups a Datastream by a shared ObservedProperty and Sensor and defines unitOfMeasurement using name, symbol and definition. Unit properties are null for observations without a measurement unit. A number alone does not carry this context; comparison needs the stream definitions and observation types as well as the values.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can two SensorThings result numbers be compared without their Datastream unit definitions?

Buyer evidence still required

  • Datastream unit definitions
  • ObservedProperty and Sensor relations
  • Observation types and result values

Review inference: Prevent unit or property mismatches in measurement comparisons. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse numerical comparability claims without unit and observed-property alignment.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Unit conversion and instrument equivalence were not validated.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Unit conversion and instrument equivalence were not validated.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SensorThings unknown result-generation time

Question: Does a null SensorThings resultTime mean the measurement failed?

SensorThings Sensing 1.1 says that when an observation submission omits resultTime, the service assigns null. That field describes result-generation time, separately from the result value and phenomenonTime. Null therefore does not itself diagnose a failed measurement or supply a generation timestamp; the buyer must seek the missing timing evidence separately.

Source: OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a null SensorThings resultTime mean the measurement failed?

Buyer evidence still required

  • Original resultTime and submission
  • Result value and quality information
  • Source timing evidence

Review inference: Avoid inferring measurement failure or timing from a missing generation time. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse failure or exact-generation-time conclusions from null resultTime alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual generation time and measurement validity remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The actual generation time and measurement validity remain unverified.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sentry MCP: Project debugging and data recipients

Question: What should an agent check before sending project error data through Sentry MCP?

Sentry documents organization- or project-scoped connections for its remote MCP, with project scope recommended where possible. Its toolkit describes debugging workflows and notes that AI-powered search in self-hosted setup requires a configured model provider. Identify the deployment, enabled tools and model route before transferring sensitive event context. The public connection page and repository differ in their description of authentication options.

Source: Sentry MCP connection and scope. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Sentry remote MCP, with separately attributed toolkit notes for local/self-hosted setups; these deployments are not treated as interchangeable.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Sentry publishes the remote service and toolkit; a self-hosted deployment has its own operator.

Documented by publisher. Sentry MCP connection and scope; Sentry Toolkit: remote and local MCP

Purpose

Retrieve errors and performance context for development investigations.

Documented by publisher. Sentry MCP connection and scope; Sentry Toolkit: remote and local MCP

Read capability

Errors, issue context and performance information through enabled debugging tools.

Documented by publisher. Sentry MCP connection and scope; Sentry Toolkit: remote and local MCP

Write capability

The service describes issue triage and project management; inspect the effective tools before assuming read-only access.

Documented by publisher. Sentry MCP connection and scope; Sentry Toolkit: remote and local MCP

Authentication

The connection page says OAuth for all connections; the toolkit additionally documents an explicit upstream-token remote path. That path was not tested.

Documented by publisher. Sentry MCP connection and scope; Sentry Toolkit: remote and local MCP

Permission surface

Organization/project URL scoping is documented. The buyer must also inspect identity rights and enabled skills.

Documented by publisher. Sentry MCP connection and scope; Sentry Toolkit: remote and local MCP

Data leaving the environment

Event context reaches the client. The toolkit's self-hosted AI search requires a model provider; actual provider, payload and retention remain unverified.

Review inference. Sentry MCP connection and scope; Sentry Toolkit: remote and local MCP

Failure modes to consider

Using organization-wide context unnecessarily; treating sensitive events as harmless diagnostics; assuming self-hosted search has no model recipient.

Review inference. Sentry MCP connection and scope; Sentry Toolkit: remote and local MCP

Unknowns and applicability

Deployment, event redaction, active skills, model provider, token route availability and retention.

Not established

Suggested refusal or clarification condition

Resolve event sensitivity and recipients before retrieval; stop before project changes outside a debugging-only task.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve project-scope, data-flow and authentication ambiguity in a debugging-tool review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Sentry outcomes: Missing events need ingestion context

Question: Does an empty Sentry event search prove that no error occurred?

The reviewed experimental endpoint reports received-but-dropped events alongside accepted volume. It distinguishes filtering, rate limits and other drop reasons. These counts describe ingestion outcomes, not every event generated by an application; missing events require telemetry and filtering context before a conclusion.

Source: Sentry accepted and dropped event outcomes. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: No matching stored events proves no application error occurred.

Buyer evidence still required

  • SDK/ingestion coverage.
  • Accepted and dropped outcomes for the interval.
  • Filters, quotas and query scope.

Suggested review condition: Require collection and outcome evidence before making an absence claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Experimental API version, collection scope, outcomes and query interval

Optional saved evidence: Preserve the ingestion limitations behind a monitoring or incident-evidence conclusion.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Sentry scrubbing: Incoming events and attachment handling

Question: Does enabling Sentry server-side scrubbing prove sensitive data never left the application or was removed historically?

Sentry describes server-side scrubbing and states that new advanced rules apply to incoming events. Its JavaScript attachment guidance provides a pre-send handling point. These controls do not by themselves prove that sensitive data never left the application or that older stored material was removed.

Source: Sentry organization scrubbing controls and new-event scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Enabling scrubbing proves zero sensitive-data transmission and historical cleanup.

Buyer evidence still required

  • Client pre-send handling and attachment configuration
  • Server scrubbing rules with activation dates
  • Separate evidence for historical data removal and downstream copies

Suggested review condition: Require transmission and historical-retention evidence before accepting a zero-disclosure claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck SDK hooks, safe-field exemptions, rule activation and attachment handling.

Optional saved evidence: Retain the difference between future-event filtering and retrospective cleanup.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Service Bus: Accepted sends and duplicate suppression

Question: Does a successful Service Bus send prove a new message was enqueued?

With duplicate detection enabled, a repeated message identity within the configured window can receive a successful send response while the duplicate is discarded. The feature is tier-dependent and identity construction matters. It does not prove that a downstream consumer completed a unique business action.

Source: Azure Service Bus duplicate detection. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every successful send acknowledgement represents a new queued operation.

Buyer evidence still required

  • Service tier and duplicate-detection window.
  • Message identity and partition settings.
  • Consumer completion and replay records.

Suggested review condition: Reconcile stable message identity before counting accepted retries as new work.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Tier, entity, detection window, message ID, partitioning and consumer effects.

Optional saved evidence: Save the evidence needed to interpret ambiguous sends and prevent inflated completion counts.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Service Bus: Deferred work outside normal retrieval

Question: Can a deferred Service Bus message be treated as completed or expired because normal receives no longer return it?

Deferred Service Bus messages remain in the main queue but require their sequence number for retrieval; peeking can discover them. Expiration is checked when a client tries to retrieve a deferred message by sequence number, rather than automatically removing it as normal time passes. Absence from ordinary receives does not establish completion or cleanup.

Source: Azure Service Bus: Message deferral. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a deferred Service Bus message be treated as completed or expired because normal receives no longer return it?

Buyer evidence still required

  • Deferred message identity, sequence number and intended recovery condition.
  • Peek or explicit deferred-receive observations with expiry information.
  • Processing, settlement or dead-letter outcome and any unresolved deferred inventory.

Suggested review condition: Decline empty-backlog or completed-work claims based only on normal receives without checking deferred work.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Deferred message identity, sequence number and intended recovery condition. Peek or explicit deferred-receive observations with expiry information. Processing, settlement or dead-letter outcome and any unresolved deferred inventory.

Optional saved evidence: Deferred agent work can become invisible to a normal worker while remaining unresolved in the queue.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic deferred-message recovery or proof that expired work has been removed
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Service Bus: Failed settlement after completed work

Question: If Service Bus Complete fails after processing, does that mean the agent action failed too?

Service Bus Complete can fail because of a network problem, expired lock or service condition after the handler has already done its work. The message may be redelivered, so the application must decide how to preserve and recognize an existing result. Broker settlement failure is not proof that the business effect did not occur.

Source: Azure Service Bus: Transfers, locks and settlement. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: If Service Bus Complete fails after processing, does that mean the agent action failed too?

Buyer evidence still required

  • Message ID, lock history and exact Complete failure.
  • Business-result record and external effect observed before settlement.
  • Redelivery handling and reconciliation keyed to the original action.

Suggested review condition: Decline a safe-repeat conclusion until prior business completion and settlement uncertainty are separated.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Message ID, lock history and exact Complete failure. Business-result record and external effect observed before settlement. Redelivery handling and reconciliation keyed to the original action.

Optional saved evidence: Repeating a completed effect to repair a failed acknowledgement can duplicate an external action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Atomicity between message settlement and external writes or verified broker state
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

ServiceNow REST endpoint and data ACLs

Question: Does access to a ServiceNow REST endpoint establish permission to every table and field it exposes?

The Brazil REST guide separates endpoint role and ACL requirements from table and field access. Fields denied by ACLs are omitted from REST query responses. Direct table web-service access also has a dedicated enablement setting; application CRUD flags such as Can read or Can create do not apply to web-service requests.

Source: REST APIs — Brazil. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does access to a ServiceNow REST endpoint establish permission to every table and field it exposes?

Buyer evidence still required

  • Endpoint and applicable REST access policy
  • Calling user’s table and field ACL evidence
  • Table web-service setting and required result fields

Review inference: Evaluate endpoint admission and actual data ACLs separately instead of treating a role or OAuth scope as the complete table boundary.

Suggested review condition: Refuse an all-fields or all-tables claim from endpoint access alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer instance’s ACLs, policies and returned-field completeness are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid treating an admitted API request as unrestricted or complete data access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal table restriction or bypass from a single role or scope
  • The buyer instance’s ACLs, policies and returned-field completeness are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

ServiceNow UI policies and API data validation

Question: Does hiding or restricting a field with a ServiceNow UI policy establish the same restriction for REST writes?

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: Data policy — Brazil. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does hiding or restricting a field with a ServiceNow UI policy establish the same restriction for REST writes?

Buyer evidence still 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 inference: Review data-policy applicability and ACLs for the actual write path rather than infer API behavior from the form.

Suggested review condition: Reject an API-write restriction claim based only on the field’s form appearance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Effective policies and the buyer’s write outcome are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep automated data changes within the documented validation path.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • 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

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Shared HTTP browser context boundary

Question: Does Playwright MCP shared-browser-context isolate browser state between connected HTTP clients?

The pinned Playwright MCP README defines --shared-browser-context as reusing the same browser context across all connected HTTP clients. A separate MCP client connection therefore does not establish a separate browser context when this setting is enabled.

Source: Playwright MCP README, v0.0.84. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Playwright MCP shared-browser-context isolate browser state between connected HTTP clients?

Buyer evidence still required

  • Exact installed version, provider variant and effective non-secret configuration
  • Relevant pending-call identifiers, declared arguments and decision provenance without secrets
  • Application-owned review policy and independently observed outcomes where needed

Review inference: Inspect effective launch configuration and browser identity before treating client connections as isolated users; connection count does not establish tenant isolation or live access. Existing isolation evidence distinguishes session state from read-only authority. This decision identifies an explicit HTTP setting sharing one browser context across distinct clients. Operational review inference; no deployment outcome was observed.

Suggested review condition: Inspect effective launch configuration and browser identity before treating client connections as isolated users; connection count does not establish tenant isolation or live access.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Configuration / --shared-browser-context

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Inspect effective launch configuration and browser identity before treating client connections as isolated users; connection count does not establish tenant isolation or live access.
  • The flag does not describe distinct independently operated server processes or separately verified context allocation; not all Playwright clients necessarily share state.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SharePoint agents: Blocking in Copilot Chat has limited host coverage

Question: Does blocking a SharePoint agent in the Microsoft 365 agent inventory disable it in every host?

The captured SharePoint guidance states that blocking an agent in the administration experience affects Copilot Chat availability, but does not yet apply to OneDrive, SharePoint or Teams. An organization-wide shutdown therefore requires a host-specific access review. The documented administrative block alone does not demonstrate universal removal of the agent.

Source: Manage access to agents in SharePoint. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does blocking a SharePoint agent in the Microsoft 365 agent inventory disable it in every host?

Buyer evidence still required

  • Agent identity and administrative blocking record
  • Inventory of hosts where the agent is available
  • Current host-specific access and licensing settings

Review inference: Host coverage is a separate acceptance criterion for agent offboarding.

Suggested review condition: Refuse a global-disablement finding until every relevant host is covered and checked.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Tenant rollout, current host behavior and remaining access are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid leaving an agent usable through an overlooked host during offboarding.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal agent disablement from a Copilot Chat administrative block
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SharePoint Application Restrictions: Effective policy and excluded callers

Question: Does a SharePoint application allowlist block every unlisted agent from the site?

SharePoint Application Restrictions require the tenant switch to be enabled; tenant denials outrank site allowances. Only positively classified third-party applications are governed: first-party and unclassified callers are excluded. The control does not apply to personal sites or trim search enumeration. Existing authorization still applies to requests that pass this additional gate.

Source: Restrict application and agent access to SharePoint sites. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a SharePoint application allowlist block every unlisted agent from the site?

Buyer evidence still required

  • Tenant enablement, denial list and effective site mode
  • Application identity, classification and site type
  • Existing grants and an authorized deployment access test

Review inference: A stored site allowlist is not a universal agent-access boundary.

Suggested review condition: Refuse a universal-blocking claim without caller coverage, active policy state and effective authorization evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Caller classification, policy parsing and runtime application are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Detect gaps in a proposed enterprise application restriction before relying on it.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal agent blocking, search trimming or replacement of existing permissions
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SharePoint restricted discovery: Search visibility and access remain distinct

Question: Does Restricted Content Discovery revoke access to a SharePoint site or remove its search index data?

SharePoint Restricted Content Discovery limits organization-wide discovery and Copilot exposure while governance work proceeds. It does not change existing access permissions or remove content from the Microsoft 365 search index. Users with permission can still access content directly, and propagation takes time. Discovery suppression is not an offboarding or erasure result.

Source: Restricted content discovery. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Restricted Content Discovery revoke access to a SharePoint site or remove its search index data?

Buyer evidence still required

  • Applied discovery policy and propagation observation
  • Direct-link access and underlying permission inventory
  • Required offboarding or retention outcome

Review inference: A visibility control cannot substitute for permission revocation or deletion evidence.

Suggested review condition: Do not mark offboarding or erasure complete solely because organization-wide discovery is restricted.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Effective user access, propagation completion and retained content are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Separate temporary Copilot discovery controls from completed access removal.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Permission revocation, erasure or immediate universal discovery suppression
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SharePoint retention and version preservation

Question: Does applying Purview retention to a SharePoint site alone guarantee preservation of every file version?

SharePoint retention can copy changed or deleted content into a Preservation Hold library. Microsoft says retaining all file versions requires site versioning; new content is not copied on its first edit. The behavior also differs between retention policies, record labels and ordinary retention labels. Retention configuration alone is not an all-version archive.

Source: Learn about retention for SharePoint and OneDrive | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does applying Purview retention to a SharePoint site alone guarantee preservation of every file version?

Buyer evidence still required

  • Site versioning settings and relevant document version history
  • Retention policy or label type and activation date
  • Preservation Hold library and export coverage for required versions

Review inference: Inspect versioning and label behavior as well as the retention duration when specifying an evidence archive.

Suggested review condition: Reject an all-version preservation claim without versioning and version-level evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s historical versions and preservation copies are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a retained document from being mistaken for a complete revision history.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic reconstruction of every earlier document revision
  • The buyer’s historical versions and preservation copies are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Shopify bulk queries: Finished operations and partial exports

Question: Does a Shopify bulk_operations/finish webhook prove that a complete export is ready?

Shopify sends bulk_operations/finish for completed, failed or canceled operations. A failed query may expose a partialDataUrl containing incomplete results. Result download URLs expire after one week. A finish notification or downloadable file therefore needs status and coverage reconciliation before being treated as a complete export.

Source: Perform bulk operations with the GraphQL Admin API. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Shopify bulk_operations/finish webhook prove that a complete export is ready?

Buyer evidence still required

  • Bulk-operation identity, status and error code
  • Requested scope and result or partial-result inventory
  • Download time, retained artifact and completeness check

Review inference: Export acceptance needs both a terminal outcome and reconciled requested coverage.

Suggested review condition: Refuse complete-export findings from a finish webhook or partial result alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual export completeness and retained artifact contents are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent incomplete commerce data from becoming an accepted migration or audit archive.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete export from a finish event or continued download availability
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Shopify Cart MCP: Cart changes and purchase authority

Question: Can a shopping agent prepare a Shopify cart without committing the buyer to payment?

Shopify separates Cart MCP from Checkout MCP. Cart tools can create, read, replace and cancel a pre-checkout cart using unauthenticated requests with agent-profile metadata. Checkout has a separate authentication boundary. Older Storefront cart tools were removed; a cart or estimated total is not proof of payment.

Source: Shopify UCP Cart MCP pre-purchase capabilities. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Merchant Cart MCP over UCP; separate from checkout and deprecated Storefront cart tools

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Shopify documents the service; calls target the selected merchant storefront.

Documented by publisher. Shopify UCP Cart MCP pre-purchase capabilities; Shopify Storefront MCP migration

Purpose

Cart MCP supports pre-purchase cart preparation before conversion to checkout.

Documented by publisher. Shopify UCP Cart MCP pre-purchase capabilities; Shopify Storefront MCP migration

Read capability

The get-cart operation returns the current cart and estimated totals.

Documented by publisher. Shopify UCP Cart MCP pre-purchase capabilities; Shopify Storefront MCP migration

Write capability

Create, update and cancel operations change cart state; update replaces the cart contents.

Documented by publisher. Shopify UCP Cart MCP pre-purchase capabilities; Shopify Storefront MCP migration

Authentication

Cart calls accept unauthenticated requests with required agent-profile metadata; Checkout MCP requires separate authentication or signing.

Documented by publisher. Shopify UCP Cart MCP pre-purchase capabilities; Shopify Storefront MCP migration

Permission surface

Cart and checkout are separate capabilities with distinct access and rate limits.

Documented by publisher. Shopify UCP Cart MCP pre-purchase capabilities; Shopify Storefront MCP migration

Data leaving the environment

Line items and any supplied buyer context are sent to the merchant service and returned through the client.

Review inference. Shopify UCP Cart MCP pre-purchase capabilities; Shopify Storefront MCP migration

Failure modes to consider

A partial replacement can remove intended items; an old Storefront endpoint or stale cart total can mislead a buying workflow.

Review inference. Shopify UCP Cart MCP pre-purchase capabilities; Shopify Storefront MCP migration

Unknowns and applicability

Merchant support, negotiated version, final pricing and buyer payment authority are unverified.

Not established

Suggested refusal or clarification condition

Keep cart preparation separate from purchase approval and verify the current cart before requesting checkout.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck merchant capabilities, cart replacement behavior and checkout authentication.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the protocol and buyer-authority boundary behind pre-purchase cart preparation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Shopify: Paid orders, fulfillment and delivery are distinct

Question: Does a Shopify order marked paid demonstrate that its goods were fulfilled or delivered?

Shopify's Admin GraphQL Order exposes financial and fulfillment statuses separately. OrderDisplayFinancialStatus includes PAID, while OrderDisplayFulfillmentStatus distinguishes states such as UNFULFILLED, PARTIALLY_FULFILLED and FULFILLED. The separate fields describe different aspects of an order; the reviewed latest API reference does not equate financial status with fulfillment state.

Source: Order - GraphQL Admin. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Shopify order marked paid demonstrate that its goods were fulfilled or delivered?

Buyer evidence still required

  • Order ID, API version and current financial and fulfillment fields.
  • Line-item and fulfillment records including partial quantities.
  • Carrier or recipient evidence for the specific shipment and delivery claim.

Review inference: Even a fulfilled order needs shipment or recipient evidence before asserting physical delivery.

Suggested review condition: Refuse delivery claims derived only from PAID or an aggregate fulfillment label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No order, carrier event or recipient receipt was verified; the latest source alias is not a pinned client API version.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck pinned Admin API version, order statuses and fulfillment quantities.

Optional saved evidence: Bind an action request to the outcome evidence needed for a business decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified shipment, recipient delivery or complete fulfillment of every item
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Should a new user turn be appended immediately after an OpenAI after_turn cancellation

Question: Should a new user turn be appended immediately after an OpenAI after_turn cancellation?

The captured Python SDK guide says after_turn cancellation lets the current turn finish. When manually continuing normalized input after a tool turn, rerun last_agent for the unfinished existing user turn. If new input arrives before that run resumes, convert the drained result to state, stage input and resume. Tool-approval interruptions also require draining and inspecting interruptions before resuming state; a stopped tool turn is not automatically a fresh completed user turn.

Source: OpenAI primary documentation: openai streaming. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Should a new user turn be appended immediately after an OpenAI after_turn cancellation?

Buyer evidence still required

  • SDK version
  • cancel mode
  • drained result
  • last agent
  • interruptions
  • continuation state

Review inference: Should a new user turn be appended immediately after an OpenAI after_turn cancellation? Refuse to treat a partially finished tool or approval turn as a fresh completed conversation turn. Specifies after-turn interruption and staged new-input ordering beyond the generic approval-resume boundary. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse to treat a partially finished tool or approval turn as a fresh completed conversation turn.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Cancel streaming after the current turn

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse to treat a partially finished tool or approval turn as a fresh completed conversation turn.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Should an Issuing dispute always claim the original full transaction amount

Question: Should an Issuing dispute always claim the original full transaction amount?

The creation guide defaults the Dispute Amount to the full transaction but directs users to account for refunds and cases where only a partial amount should be disputed. The amount to challenge must be reconciled against the actual unresolved portion.

Source: Stripe primary documentation: stripe issuing how to submit. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Should an Issuing dispute always claim the original full transaction amount?

Buyer evidence still required

  • original transaction
  • refunds
  • unresolved goods or service value
  • proposed disputed amount

Review inference: Should an Issuing dispute always claim the original full transaction amount? Require refund and partial-fulfilment reconciliation before accepting the default amount. Determining the dispute claim amount is separate from finding uncertain refund-to-authorization links. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require refund and partial-fulfilment reconciliation before accepting the default amount.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Dispute Amount

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require refund and partial-fulfilment reconciliation before accepting the default amount.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sigstore bundle DSSE single-signature profile

Question: Does a Sigstore bundle’s DSSE envelope establish a multi-signer quorum?

The documented Sigstore bundle profile restricts its DSSE envelope to a single signature and an in-toto Statement payload type. Generic DSSE support for multiple signatures does not make a Sigstore bundle a threshold-approval proof.

Source: Sigstore: Bundle specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Sigstore bundle’s DSSE envelope establish a multi-signer quorum?

Buyer evidence still required

  • Bundle media type/version
  • Envelope payload type
  • Signature count
  • Required approval policy

Review inference: Review sigstore bundle dsse single-signature profile before accepting the buyer claim. This decision separates the restrictive Sigstore serialization profile from generic DSSE signature-set handling; a collected bundle cannot silently inherit a quorum claim. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Apply the specific bundle profile rather than generic DSSE possibilities. Obtain separate threshold-policy evidence before claiming multi-party approval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. DSSE

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Apply the specific bundle profile rather than generic DSSE possibilities. Obtain separate threshold-policy evidence before claiming multi-party approval.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sigstore bundle informational digest input

Question: Can a verifier use the message digest inside a Sigstore bundle as proof of the artifact’s own digest?

The Sigstore bundle specification marks message_digest as informational. A verifier must obtain or compute the digest for the artifact being verified rather than trusting that field to identify the supplied artifact.

Source: Sigstore: Bundle specification. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a verifier use the message digest inside a Sigstore bundle as proof of the artifact’s own digest?

Buyer evidence still required

  • Actual artifact bytes or independently obtained digest
  • Bundle
  • Digest algorithm
  • Verification result

Review inference: Review sigstore bundle informational digest input before accepting the buyer claim. The existing bundle record distinguishes collection from verification, but does not specify the informational digest field’s role in selecting verifier input. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not substitute a self-reported bundle digest for a digest of the intended artifact. Refuse artifact identity where independently bound input is missing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Message Signature

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not substitute a self-reported bundle digest for a digest of the intended artifact. Refuse artifact identity where independently bound input is missing.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sigstore Rekor timestamp trust and version

Question: Can Rekor’s signed integrated time be treated as an immutable independently trusted signing timestamp?

Sigstore documents that Rekor v1 integratedTime uses Rekor’s internal clock and is not included in the append-only log node, despite being signed. Rekor v2 uses a separate timestamp authority. Timestamp trust must therefore be evaluated by version and evidence type.

Source: Sigstore: Timestamps. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can Rekor’s signed integrated time be treated as an immutable independently trusted signing timestamp?

Buyer evidence still required

  • Rekor version
  • Timestamp evidence and trusted authority
  • Log inclusion evidence
  • Certificate validity window

Review inference: Review sigstore rekor timestamp trust and version before accepting the buyer claim. The prior record distinguishes certificate expiry from signing-time verification. This question qualifies the timestamp source itself and the material v1/v2 evidence difference. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not treat a signed v1 integratedTime as an independently trusted immutable timestamp. Establish the applicable time source and validation policy; no timestamp proves business completion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Rekor v1;Rekor v2

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat a signed v1 integratedTime as an independently trusted immutable timestamp. Establish the applicable time source and validation policy; no timestamp proves business completion.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sigstore: Bundled verification material

Question: Does possession of a Sigstore bundle mean an artifact has already been verified?

A Sigstore bundle packages signature content and supporting verification material. A verifier still needs to evaluate that material against the expected artifact and trust policy.

Source: Sigstore Bundle Format. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • verification from bundle possession
  • acceptance of an arbitrary signer
  • artifact safety from packaging

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Sigstore: Identity-based signing

Question: What does Sigstore's keyless signing model bind together?

Sigstore's documented keyless flow binds a signing key to an authenticated identity using a short-lived certificate. The identity binding does not establish software quality or permission to deploy.

Source: Sigstore documentation. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • software quality from signer identity
  • deployment permission
  • all signing modes use identical trust assumptions

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Sigstore: Signing transparency

Question: What does a Rekor transparency entry establish?

Sigstore describes Rekor as a public, append-only record of signing information. Log evidence supports auditability; it does not by itself approve the artifact's contents.

Source: Sigstore documentation. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • artifact safety from log presence
  • endorsement by the log operator
  • correctness of a signed claim

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Sigstore: Signing-time evidence after certificate expiry

Question: Can a Sigstore signature remain verifiable after its short-lived certificate expires?

Sigstore’s bundle documentation explains how trusted signing-time evidence can support verification after a short-lived signing certificate expires. The verifier must establish signing within the certificate’s validity and apply its trust policy. A timestamp does not by itself establish artifact safety or the truth of signed content.

Source: Sigstore bundle format. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • artifact safety
  • truth of signed statements
  • verification without trust-policy checks

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Sigstore: Verification expectations

Question: Is verifying an artifact signature sufficient for a Sigstore reliance decision?

The documented Sigstore verification flow checks the signature, expected identity, certificate trust and log inclusion evidence. Reliance also needs the buyer's expected artifact and use context.

Source: Sigstore documentation. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • all trust checks satisfied by signature mathematics alone
  • verification of an actual customer artifact
  • permission to execute after verification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack app approval and installation state

Question: Does Slack administrator preapproval establish that an app is already installed and active in the workspace?

Slack describes preapproval as allowing members to install and use an app. Approval and installation are separate operations. The same guide warns that restricting an app already installed does not stop its use unless it is uninstalled. Policy status alone is therefore not an inventory of active installations.

Source: Manage app approval for your workspace | Slack. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Slack administrator preapproval establish that an app is already installed and active in the workspace?

Buyer evidence still required

  • Workspace app approval or restriction setting
  • Installation inventory and removal evidence
  • Required access cutoff or activation outcome

Review inference: Reconcile app policy with actual installation and removal state.

Suggested review condition: Do not treat approval as completed installation or restriction as completed removal.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual installed apps and effective tokens are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep onboarding and offboarding decisions aligned with active workspace integrations.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic installation everywhere or instant revocation from policy restriction
  • Actual installed apps and effective tokens are unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack app-level token API scope

Question: Can a Slack app-level token replace a bot token for arbitrary Web API operations?

Slack describes app-level tokens as supporting specific app-wide APIs, including operations spanning installations. Bot and user tokens represent different identities and scopes. App-level status does not supply the token type or authority required by every Web API method. The method’s accepted token types remain decisive.

Source: Tokens | Slack Developer Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a Slack app-level token replace a bot token for arbitrary Web API operations?

Buyer evidence still required

  • Target API method and supported token types
  • Token category and granted scopes
  • Workspace or app-wide installation context

Review inference: Check token type, method and installation context together before choosing credentials.

Suggested review condition: Reject credential substitution where the method does not accept that token type.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual token, grants and requested method are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent an integration from confusing app-wide plumbing with workspace action authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal Web API authority from an app-level token
  • The actual token, grants and requested method are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack audit: Administrative events are not message contents

Question: Can Slack Audit Logs API records substitute for a transcript of what an agent read or posted?

Slack describes its Audit Logs API as a read-only view of supported organisational audit actions, not message-content monitoring. It covers a subset of possible audit events and does not determine whether an action was appropriate. A message transcript requires a separate evidence basis.

Source: Slack: Audit Logs API. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can Slack Audit Logs API records substitute for a transcript of what an agent read or posted?

Buyer evidence still required

  • Organisation-level audit access and event coverage.
  • Relevant returned audit records.
  • Separate authorised content evidence where needed.

Suggested review condition: Do not substitute administrative audit events for message contents or an appropriateness verdict.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Enterprise organisation, audit event types and required message evidence.

Optional saved evidence: Can Slack Audit Logs API records substitute for a transcript of what an agent read or posted?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack Connect: Content ownership limits retention and exports

Question: Can one organization's Slack Connect retention and exports cover all externally contributed content?

Slack explains that organizations generally control retention of content sent by their own members; external contributions follow the contributing organization's settings, with documented invitation and plan exceptions. Slack Connect exports can include externally sent messages and display names, but file-link and member-information coverage is limited. Retention by another organization can affect what remains available to export.

Source: How data management features apply to Slack Connect | Slack. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can one organization's Slack Connect retention and exports cover all externally contributed content?

Buyer evidence still required

  • Participating organizations, plans, invitation type and retention policies.
  • Export type, date range, disconnection history and message/file inventory.
  • Other organizations' retention evidence and separately downloaded copies.

Review inference: One party's settings or export cannot establish deletion or custody across all participants.

Suggested review condition: Refuse all-party deletion or complete-export claims from one organization's configuration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Counterparty settings, export completeness and retained copies were not verified.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck invitation type, plan, retention and export rules after connection changes.

Optional saved evidence: Identify residual resources before closing a data-retention or exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • All-party deletion, complete external file export or legal-hold compliance
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack customized messages and user permission

Question: Does approval of chat:write.customize alone justify posting a Slack message as a user?

Slack permits customized message appearance with the additional chat:write.customize scope, but says the feature should respond to an inciting user action and be clearly signposted in advance. Scope approval alone is not the user-specific permission described for posting on their behalf. The method also documents deletion limitations for impersonated messages.

Source: chat.postMessage method | Slack Developer Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does approval of chat:write.customize alone justify posting a Slack message as a user?

Buyer evidence still required

  • Granted scope and chosen message identity
  • User action authorising the message and advance notice
  • Destination and approved content

Review inference: Retain the user request and intended message identity separately from installed scopes.

Suggested review condition: Do not infer approval to impersonate every member from app-level scope consent.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No particular user’s permission or sent-message outcome is established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep automated communication within the user’s actual authorisation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Unrequested messaging on behalf of any workspace member
  • No particular user’s permission or sent-message outcome is established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack Events: Retry delivery is not a new event

Question: Should each Slack Events API delivery trigger a fresh agent action?

Slack assigns a globally unique event_id and retries failed delivery acknowledgements. Optional delayed events settings extend retry handling. Receipt attempts and logical events are different, so an integration should preserve event identity when deciding whether to act again.

Source: Slack: Events API. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Should each Slack Events API delivery trigger a fresh agent action?

Buyer evidence still required

  • event_id and received retry metadata.
  • Acknowledgement and delayed-event configuration.
  • Durable processing outcome for the logical event.

Suggested review condition: Review acknowledgement and action completion separately; do not equate each delivery attempt with a new instruction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Event identity, acknowledgement timing, retry settings and processing state.

Optional saved evidence: Should each Slack Events API delivery trigger a fresh agent action?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack export evidence: Plan and conversation coverage

Question: Does a Slack workspace export contain private channels, direct messages and the files themselves?

Slack distinguishes public-channel exports from broader conversation exports, which depend on plan and additional approval. The documentation describes messages and file links rather than a universal archive of every file. Check the approved export type and retention before using it as evidence of a complete workspace history.

Source: Slack workspace export eligibility and coverage. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: This Slack export is a complete copy of all workspace conversations and attachments.

Buyer evidence still required

  • Export eligibility and any required approval
  • A dated export manifest identifying conversation scope
  • Evidence that needed file contents were retained separately from links

Suggested review condition: Qualify completeness if private conversations, retention periods or linked file contents are not accounted for.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck plan, export approval, conversation scope and link availability.

Optional saved evidence: Retain the export-scope limitations behind a workspace review or migration decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack history access by token type and membership

Question: Can a Slack bot read private-channel history merely because its token has a history scope?

Slack conversations.history combines the relevant history scope with token-specific access. Bot tokens can read conversations the bot belongs to; app-level tokens cover conversations the app belongs to; user tokens cover private conversations the user belongs to and public conversations. A scope name alone does not establish membership or make bot and user access interchangeable.

Source: conversations.history method | Slack Developer Docs. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can a Slack bot read private-channel history merely because its token has a history scope?

Buyer evidence still required

  • Token type and granted history scope without exposing the token
  • Workspace, conversation identity and relevant membership
  • Purpose and authority for retrieving and disclosing the requested history

Review inference: Bind the token identity and conversation membership to the proposed read, separately from any permission to post.

Suggested review condition: Do not claim private-channel read authority from the presence of a history scope alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual membership, effective access, history completeness and downstream disclosure authority were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Check the specific identity and conversation boundary before an agent retrieves messages.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete workspace export or permission to post or redistribute messages
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack history: Cursors and time boundaries define coverage

Question: Does receiving fewer Slack history messages than requested prove the conversation has no more evidence?

Slack warns that history responses may contain fewer items than the requested limit before history is exhausted. Cursor continuation and time bounds must be considered together. The inclusive option controls whether messages exactly at the supplied boundary timestamps are included.

Source: Slack: conversations.history method. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does receiving fewer Slack history messages than requested prove the conversation has no more evidence?

Buyer evidence still required

  • Conversation identity and access scope.
  • Cursor continuations and response metadata.
  • Time bounds, inclusive setting and collection failures.

Suggested review condition: Do not infer completion from a short page; preserve cursor and boundary handling.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Conversation, token access, cursor history and oldest/latest bounds.

Optional saved evidence: Does receiving fewer Slack history messages than requested prove the conversation has no more evidence?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack MCP: Search scope and posting authority

Question: What should an agent check before searching private Slack content without posting messages?

Slack documents separate user-token scopes for searches, conversation history and posting. Review the authorized workspace, requested content and client data handling before retrieval. A search permission does not authorize sending a message, and connecting Slack to another tool creates a separate disclosure decision. This record reviews the official server, not Slackbot's connections to third-party servers.

Source: Slack MCP tools, scopes and client access. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Slack's official hosted MCP server for external clients; not the Slackbot MCP client or a community Slack connector.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Slack operates the official hosted server.

Documented by publisher. Slack MCP tools, scopes and client access

Purpose

Retrieve workspace context and perform supported Slack actions.

Documented by publisher. Slack MCP server and client distinction

Read capability

Searches, files and conversation history require their respective user-token scopes.

Documented by publisher. Slack MCP tools, scopes and client access

Write capability

Posting, reactions, canvases and channel creation have separate write scopes.

Documented by publisher. Slack MCP tools, scopes and client access

Authentication

Confidential OAuth is documented for Marketplace or internal apps; unlisted apps are excluded.

Documented by publisher. Slack MCP tools, scopes and client access

Permission surface

Scope grants and configured app IP allowlists apply to MCP requests.

Documented by publisher. Slack MCP tools, scopes and client access

Data leaving the environment

Slack content reaches the connected client; onward sharing depends on the client and other tools.

Review inference. Slack MCP tools, scopes and client access

Failure modes to consider

Overbroad private-channel access, unintended posting, or following instructions inside retrieved messages.

Review inference. Slack MCP tools, scopes and client access

Unknowns and applicability

Actual workspace grants, channel visibility, client recipients and retention.

Not established

Suggested refusal or clarification condition

For a search task, withhold posting and cross-tool sharing unless separately authorized.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck user-token scopes, app distribution status and IP allowlists when the connection changes.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the scope and disclosure questions used when approving a chat-search connector.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack offboarding: Revocation events need not arrive in order

Question: Does a Slack token-revocation event prove the whole app was uninstalled?

Slack says an app is not uninstalled until its final user and bot tokens are revoked. app_uninstalled and tokens_revoked events have no guaranteed sequential order. Correlate the app and workspace and distinguish an individual revoked token from complete uninstall.

Source: Slack: app_uninstalled event. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a Slack token-revocation event prove the whole app was uninstalled?

Buyer evidence still required

  • App and workspace identities.
  • Relevant uninstall and token-revocation events.
  • State of remaining user and bot grants.

Suggested review condition: Do not equate one revoked token or event arrival order with completed app removal.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Slack app, workspace, grants and event correlation.

Optional saved evidence: Retain the evidence that distinguishes partial revocation from app removal.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack rotation: Expiring access and refresh continuity

Question: Does enabling Slack token rotation provide uninterrupted access without further state handling?

Rotation introduces expiring access tokens and replacement refresh tokens. The new refresh token must be retained after exchange; repeatedly using the original token breaks subsequent refreshes. Slack also limits simultaneously active refreshed tokens. Rotation requires a tested credential-lifecycle implementation, not merely an enabled setting.

Source: Slack token rotation. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Token rotation can be enabled without changing refresh-state handling.

Buyer evidence still required

  • Supported token type and rotation configuration.
  • Secure atomic storage of replacement credentials.
  • Refresh, expiry and recovery test evidence.

Suggested review condition: Require working replacement-token handling before treating rotation as operationally complete.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. App installation, token type, refresh storage, concurrent consumers and recovery behaviour.

Optional saved evidence: Retain the evidence required to assess an integration's credential continuity.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack SCIM: Deactivation is not permanent deletion

Question: Does a successful Slack SCIM offboarding action prove user data was erased?

Slack states that SCIM can deactivate users but cannot permanently delete them. Its token authority also depends on the generating account role. A deactivation result supports an identity-lifecycle claim, not a general data-erasure claim.

Source: Slack SCIM user deactivation and identity lifecycle. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: SCIM offboarding permanently erases the user and their data.

Buyer evidence still required

  • Identity and organisation scope of the offboarding result
  • SCIM actor role and authority over the target user
  • Separate evidence for any claimed content or personal-data deletion

Suggested review condition: Require separate erasure evidence when the requested outcome exceeds deactivation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck SCIM actor roles and the supplier deletion process.

Optional saved evidence: Save the distinction between identity deactivation and data-erasure evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack search: User context and file access

Question: Can a Slack bot token search private conversations from an external assistant?

Slack's Real-time Search API requires a user token for private conversation data or use outside the Slack client. Bot-token calls require an action token. File search permission alone does not grant file-content download; that additionally needs files:read.

Source: Slack: Using the Real-time Search API. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a Slack bot token search private conversations from an external assistant?

Buyer evidence still required

  • In-client or external execution context.
  • Actual token type, scopes and any required action token.
  • File-search versus file-download requirement.

Suggested review condition: Do not widen scopes merely because a private or file-content request fails; confirm the authorised task first.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token type, client context, scopes and file-content need.

Optional saved evidence: Retain the specific identity and disclosure conditions behind Slack search.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack webhooks: The installed destination controls posting

Question: Can an agent redirect a Slack incoming webhook by changing channel or username in its payload?

Slack documents that incoming webhooks use the configured channel, username and icon; payload overrides do not change them. The webhook URL is tied to its installed destination. Review that destination before sending rather than relying on a payload label.

Source: Slack: Sending messages using incoming webhooks. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an agent redirect a Slack incoming webhook by changing channel or username in its payload?

Buyer evidence still required

  • Non-secret webhook installation metadata.
  • Configured channel and app identity.
  • Authorised message and recipient scope.

Suggested review condition: Resolve the installed destination without exposing the webhook secret before approving a send.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Installed webhook destination, app identity and intended recipient.

Optional saved evidence: Can an agent redirect a Slack incoming webhook by changing channel or username in its payload?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack: Posting beyond joined public channels

Question: Does a Slack bot being absent from a public channel prove it cannot post there?

Slack provides chat:write.public for posting to public channels without joining them, alongside chat:write. Channel membership alone is therefore insufficient evidence of the bot's posting boundary. This posting capability does not itself establish permission to read conversation history.

Source: Slack: chat:write.public scope. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a Slack bot being absent from a public channel prove it cannot post there?

Buyer evidence still required

  • Granted chat scopes.
  • Destination channel identity and visibility.
  • Owner authority for the proposed message.

Suggested review condition: Review posting scope and recipient authority even when the bot is not a channel member.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Bot scopes, public-channel destination and intended posting operation.

Optional saved evidence: Does a Slack bot being absent from a public channel prove it cannot post there?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Slack: Sending authority does not guarantee deletion

Question: Can an agent assume it can undo every Slack message it sends by calling chat.delete?

Slack limits bot-token deletion to that bot's messages and user-token deletion to messages the user may delete. The method does not accommodate impersonation: a message sent impersonating another user cannot be deleted through that mechanism. Deletion authority needs its own review.

Source: Slack: chat.delete method. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an agent assume it can undo every Slack message it sends by calling chat.delete?

Buyer evidence still required

  • Message channel, timestamp and authorship.
  • Deletion token type and relevant rights.
  • Recorded deletion response and follow-up observation.

Suggested review condition: Do not promise an undo path solely because a send operation is available.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Posting identity, deletion token type and original message authorship.

Optional saved evidence: Can an agent assume it can undo every Slack message it sends by calling chat.delete?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SLSA provenance: Trusted builder and expected inputs

Question: Does possessing SLSA provenance prove the package came from the expected build?

The reviewed SLSA v1.2 guidance requires verification against expectations: trusted builder identity, provenance signature, build type and external parameters. Unrecognized external parameters should fail verification. Merely retaining a provenance document does not perform those checks or establish the buyer-specific expected build.

Source: SLSA verifying artifacts. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A provenance attachment alone proves the expected supplier build was used.

Buyer evidence still required

  • Trusted builder mapping and expected source/build criteria.
  • Signed provenance and artifact identity.
  • Parameter comparison and verifier outcome.

Suggested review condition: Form and check expectations before relying on provenance as acceptance evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. SLSA v1.2 guidance, artifact, builder trust, build type and external parameters.

Optional saved evidence: Preserve explicit build-acceptance questions alongside the reviewed provenance guidance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SLSA: Artifact provenance

Question: What does SLSA mean by software provenance?

SLSA describes provenance as verifiable information about an artifact's origin and production. Provenance does not by itself establish that the software is harmless or suitable for a customer's use.

Source: SLSA Provenance. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • malware freedom
  • fitness for a buyer's intended use
  • truth of arbitrary claims inside an artifact

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SLSA: Attestation format scope

Question: Does using a recommended SLSA attestation format demonstrate SLSA assurance?

SLSA v1.2 recommends Provenance and Verification Summary Attestation formats without requiring those particular formats. Format choice alone does not show that underlying requirements were met.

Source: SLSA specification v1.2. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • format compliance as full assurance
  • mandatory use of a particular recommended format
  • verification inferred from JSON shape

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SLSA: Build and Source tracks

Question: Can a SLSA claim be assessed without naming its track and requirements?

SLSA v1.2 separates Build and Source tracks, each with its own requirements. A specific assurance claim needs the relevant track, level and supporting evidence.

Source: SLSA 1.2 Tracks. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • a SLSA level inferred from a product name
  • equivalence of Build and Source assurance
  • certification by this index

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SLSA: Provenance dependency lists are not exhaustive inventories

Question: Does SLSA Build L3 provenance guarantee that resolvedDependencies lists every build dependency?

The SLSA v1.2 provenance specification describes resolvedDependencies completeness as best effort through Build L3. This differs from the completeness requirement for externalParameters. A provenance dependency list therefore cannot alone establish an exhaustive inventory for exposure or reconstruction review.

Source: SLSA v1.2 provenance. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does SLSA Build L3 provenance guarantee that resolvedDependencies lists every build dependency?

Buyer evidence still required

  • The provenance version, builder and subject.
  • The resolvedDependencies and builder documentation.
  • Independent inventory or build evidence for required coverage.

Suggested review condition: Do not assert exhaustive dependency coverage solely from a Build L3 label or provenance field presence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The provenance version, builder and subject. The resolvedDependencies and builder documentation. Independent inventory or build evidence for required coverage.

Optional saved evidence: A software buyer must separate build-origin assurance from a complete dependency inventory.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Certification of a build level, complete SBOM generation or actual vulnerability exposure
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SMART launch context and clinical access

Question: Does SMART launch/patient context grant an agent permission to read that patient’s clinical records?

SMART App Launch 2.2 distinguishes launch context from clinical resource scopes. launch/patient requests patient context; patient, user and system scopes describe different access contexts. Granted scopes remain constrained by the underlying system permissions. A patient identifier in a launch response is not itself a clinical read grant.

Source: App Launch: Scopes and Launch Context - SMART App Launch v2.2.0. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does SMART launch/patient context grant an agent permission to read that patient’s clinical records?

Buyer evidence still required

  • Granted SMART scopes and launch patient identifier
  • User or client permission policy
  • Resource types and operations required by the task

Review inference: Verify the returned clinical scopes, patient context and underlying user or client permissions together.

Suggested review condition: Refuse patient-access approval based only on launch context.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual grant and patient-specific access policy are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a clinical workflow from treating context selection as access approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Permission to access every patient from a launch token
  • The actual grant and patient-specific access policy are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SMART successful responses and omitted records

Question: Does HTTP 200 from a SMART-authorized FHIR search prove that every matching clinical record was returned?

SMART 2.2 states that scopes cannot exceed underlying system permissions. Its permission examples allow a successful 200 response while records are omitted because access is unavailable, or a forbidden response. A successful request is therefore not a completeness certificate for the clinical dataset.

Source: App Launch: Scopes and Launch Context - SMART App Launch v2.2.0. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does HTTP 200 from a SMART-authorized FHIR search prove that every matching clinical record was returned?

Buyer evidence still required

  • Granted scope and underlying permission policy
  • Expected patient and resource population
  • Returned results, pagination and documented exclusions

Review inference: Reconcile the authorized resource population, server policy and returned records before accepting completeness.

Suggested review condition: Do not treat HTTP success alone as complete clinical evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The records filtered by the actual server and the full expected population are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid accepting an incomplete clinical administrative export.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Independent verification of a patient record’s completeness
  • The records filtered by the actual server and the full expected population are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake clones and shared partition retention

Question: Can a transient clone retain shared Snowflake micro-partitions after its permanent source table is dropped?

Snowflake zero-copy clones initially share micro-partitions with their source. The documentation explains that a transient clone can keep shared bytes in use after the permanent source table is dropped, delaying their entry into Fail-safe until the clone no longer needs them. Dropping the source does not establish that every copy or shared partition is gone.

Source: Working with Temporary and Transient Tables | Snowflake Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a transient clone retain shared Snowflake micro-partitions after its permanent source table is dropped?

Buyer evidence still required

  • Source and clone identities, table types and lineage
  • Drop events and surviving clone inventory
  • Retention requirements and storage lifecycle observations

Review inference: Include surviving clones and shared-storage dependencies when reconciling deletion and retained recovery data.

Suggested review condition: Reject complete data-removal claims that ignore a surviving clone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual partition sharing, surviving clones and byte-level removal are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Find retained data dependencies that a source-table deletion receipt misses.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Independent archive creation or complete erasure from source-table deletion
  • Actual partition sharing, surviving clones and byte-level removal are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake Cortex: Processing and storage geography differ

Question: Does Snowflake account storage residency prove Cortex inference stays in the same region?

Snowflake describes cross-region inference as transient processing outside the account region without persisting that payload there. The account parameter CORTEX_ENABLED_CROSS_REGION controls permitted routing. A storage-location statement alone does not establish the actual permitted processing geography.

Source: Snowflake Cortex cross-region inference. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Snowflake account storage residency prove Cortex inference stays in the same region?

Buyer evidence still required

  • The account region and effective routing parameter.
  • The model and permitted clouds or geographies.
  • Applicable processing restrictions and request evidence.

Suggested review condition: Do not approve region-local processing without checking the effective account routing configuration.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The account region and effective routing parameter. The model and permitted clouds or geographies. Applicable processing restrictions and request evidence.

Optional saved evidence: A data owner must approve inference locations independently of the warehouse storage location.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof of the region used by a particular request or a legal residency determination
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake daily cloud services adjustment

Question: Can Snowflake's cloud-services adjustment be calculated from one monthly percentage?

Snowflake calculates the cloud-services adjustment daily in UTC using ten percent of virtual-warehouse usage. The daily adjustment is capped at actual cloud-services consumption, and serverless compute does not contribute to that threshold. The monthly adjustment sums daily calculations, so applying one percentage to monthly totals can produce a different result.

Source: Snowflake: Understanding compute cost. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: AI Cost, Usage & Invoice Assurance

Evidence to request before relying on this claim

Claim to check: Can Snowflake's cloud-services adjustment be calculated from one monthly percentage?

Buyer evidence still required

  • daily UTC warehouse and cloud-services credits
  • serverless separation
  • applicable daily price
  • billing period

Review inference: A finance script estimates the monthly adjustment from total compute credits. The script can overstate the adjustment and understate billed cost. Adds the billing adjustment calculation rather than resource-monitor enforcement coverage. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Credits and adjustment arithmetic are not proof of invoice payment or an enforced spending cap.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Understanding billing for cloud services usage

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Credits and adjustment arithmetic are not proof of invoice payment or an enforced spending cap.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Snowflake external access: Destinations and credential grants

Question: Does a Snowflake function with external access have unrestricted internet access?

External access integrations select allowed network destinations and authentication secrets. Creating a handler that uses them also requires relevant integration and secret privileges. The integration is an outbound capability; its existence alone does not demonstrate the buyer's effective destination list or the data the handler sends.

Source: Snowflake external access integrations. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: External access grants unrestricted outbound access.

Buyer evidence still required

  • Enabled integration and network-rule inventory.
  • Secret references and role grants.
  • Handler purpose and permitted data recipients.

Suggested review condition: Require the destination and data-disclosure scope before approving external calls.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Enabled integration, network rules, secret grants and handler data flow

Optional saved evidence: Preserve the destination, credential and disclosure questions used for a data-platform decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake external table deletion and remaining files

Question: Does DROP EXTERNAL TABLE in Snowflake delete the underlying files from external storage?

Snowflake documents that DROP EXTERNAL TABLE removes only table metadata; none of the underlying data files are dropped. External tables also cannot be restored with UNDROP. Removing the Snowflake object and deleting externally held files are separate operations, with different recovery and evidence requirements.

Source: DROP EXTERNAL TABLE | Snowflake Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does DROP EXTERNAL TABLE in Snowflake delete the underlying files from external storage?

Buyer evidence still required

  • External table definition, location and storage ownership
  • DROP result and remaining file/object inventory
  • Authorised storage cleanup and independent recovery requirements

Review inference: Reconcile the external storage inventory separately from the catalogue operation.

Suggested review condition: Refuse physical file-deletion claims based only on DROP EXTERNAL TABLE.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The remaining files, permissions and external storage lifecycle are unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Separate database catalogue cleanup from the removal of externally retained data.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Underlying file erasure or UNDROP recovery from an external-table drop
  • The remaining files, permissions and external storage lifecycle are unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake Fail-safe: Support recovery is separate from Time Travel

Question: Can an agent use Snowflake Fail-safe as routine extended historical-query access?

Fail-safe follows Time Travel and is described as best-effort recovery by Snowflake when other recovery options have been exhausted. It is not ordinary customer historical access and can take substantial time. The documented service also has exclusions and billing implications; a retention label is not a guaranteed self-service restore.

Source: Snowflake Fail-safe recovery. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Fail-safe provides routine immediate access to older queryable history.

Buyer evidence still required

  • Object type, ingestion architecture and applicable recovery coverage.
  • Time Travel expiry and remaining Fail-safe interval.
  • Support recovery scope, expected process and completion evidence.

Suggested review condition: Do not promise self-service historical access or guaranteed recovery from Fail-safe.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Object coverage, ingestion architecture, retention interval and support recovery

Optional saved evidence: Save the recovery-service limitations behind a supplier continuity claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake long-running queries and history transition

Question: Does expiry of a Snowflake Time Travel retention period prove the historical data has already moved into Fail-safe?

Snowflake documents that a long-running Time Travel query delays moving the data and objects it uses into Fail-safe until the query completes. The configured retention period is therefore not, by itself, proof of the observed storage transition. This does not grant a general right to start new historical queries after their retention window has expired.

Source: Understanding & using Time Travel | Snowflake Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does expiry of a Snowflake Time Travel retention period prove the historical data has already moved into Fail-safe?

Buyer evidence still required

  • Effective retention settings and relevant historical timestamps
  • Active Time Travel query status and completion evidence
  • Required deletion or recovery boundary and observed storage state

Review inference: Separate retention eligibility, active historical queries and actual recovery state in a custody review.

Suggested review condition: Refuse a completed-transition claim derived only from elapsed retention time.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual query activity and internal storage transition timing are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid using a calendar calculation as proof of a completed data lifecycle transition.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Instantaneous purge or unrestricted historical query access after retention expiry
  • Actual query activity and internal storage transition timing are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake masking: Query context and retained data

Question: Does Snowflake Dynamic Data Masking replace the underlying sensitive values?

Dynamic Data Masking applies policy at query time. Depending on conditions, execution context and role hierarchy, a query can receive raw, partial or fully masked values. The feature requires Enterprise Edition or higher. Its presence does not establish erasure of source values or the effective output for every identity.

Source: Snowflake Dynamic Data Masking. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A masking policy removes raw values and masks every user identically.

Buyer evidence still required

  • Edition and column-policy attachment.
  • Policy logic and effective role hierarchy.
  • Representative query results for intended identities.

Suggested review condition: Inspect the actual query identity and policy before accepting a universal masking claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Edition, columns, masking logic, execution context and role hierarchy.

Optional saved evidence: Retain the documented masking basis for an analytical-access decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake MCP: Discovery permission and downstream role grants

Question: Does permission to connect to Snowflake MCP also authorize every configured data tool?

Snowflake distinguishes access to the MCP server from privileges on its underlying tools and data. OAuth configuration and the effective role matter. Search, analyst, agent and custom-function tools can require different grants; successful tool discovery is not evidence that every invocation is authorized or read-only.

Source: Snowflake managed MCP roles and tools. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Snowflake-managed MCP server object; not the Snowflake Labs local server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Snowflake provides the managed MCP server within the customer account.

Documented by publisher. Snowflake managed MCP roles and tools

Purpose

A configured server exposes Snowflake search, analyst, agent and custom tools.

Documented by publisher. Snowflake managed MCP roles and tools

Read capability

Data retrieval depends on the configured tools and their underlying resource privileges.

Documented by publisher. Snowflake managed MCP roles and tools

Write capability

Custom functions and procedures can be exposed; their effects require review of the configured implementation.

Documented by publisher. Snowflake managed MCP roles and tools

Authentication

The managed server supports OAuth; dynamic client registration is not supported in the reviewed documentation.

Documented by publisher. Snowflake managed MCP roles and tools

Permission surface

MCP server USAGE permits connection and discovery; underlying tools require their own applicable privileges.

Documented by publisher. Snowflake managed MCP roles and tools

Data leaving the environment

Tool outputs reach the external MCP client; access through a private account does not establish the model recipient policy.

Review inference. Snowflake managed MCP roles and tools

Failure modes to consider

A broad role, unexpected custom procedure or incorrect default warehouse can change access or prevent execution.

Review inference. Snowflake managed MCP roles and tools

Unknowns and applicability

Effective role grants, procedure behavior, data policies and client storage are not verified.

Not established

Suggested refusal or clarification condition

Inspect the named role and configured tools before treating the endpoint as an approved data-only interface.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck roles, OAuth binding, warehouses and custom tool definitions.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the distinction between connector discovery and actual data or procedure authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake monitors: Warehouse suspension is not a universal credit cap

Question: Does an account-level Snowflake resource monitor stop all serverless and cloud-services charges?

Resource monitors control the documented user-managed virtual warehouses, not every Snowflake-provided serverless feature. Warehouse-level monitors cannot suspend cloud-services usage, and further cloud-services cost can arise after warehouse suspension. An account-level label therefore does not prove every credit-consuming path is capped.

Source: Snowflake resource monitor scope. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An account monitor enforces a complete credit ceiling across all features.

Buyer evidence still required

  • Monitor assignment, thresholds and suspension actions.
  • Inventory of user-managed and serverless consumption.
  • Cloud-services and excluded-feature controls with observed outcomes.

Suggested review condition: Do not treat warehouse suspension as proof that all credit usage ended.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Warehouse assignments, monitor actions, serverless features and cloud-services usage

Optional saved evidence: Preserve which consumption paths remain outside the monitor used in a purchasing decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake network rules: Definition is separate from activation

Question: Does creating a Snowflake network rule make it an enforced account restriction?

The network guidance requires activation at the relevant account, user or integration scope. It also distinguishes inbound access from external-access egress, and integration-level policies have storage-stage limitations. A defined rule is not proof of the applicable active policy.

Source: Snowflake network policies. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A stored network rule is an active universal restriction.

Buyer evidence still required

  • Rule-to-policy membership.
  • Active policy association and scope.
  • Covered service/stage and separate outbound configuration.

Suggested review condition: Require the active association before relying on the rule.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Rule membership, active policy association and covered endpoint

Optional saved evidence: Save the active-scope evidence behind a vendor network-control claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake query history: Delay, coverage and transfer status

Question: Does an empty Snowflake query-history result prove no query ran?

No. Account Usage query history can be delayed, and some short hybrid-table queries are represented elsewhere. The documentation also says a successful PUT or GET history status indicates authorisation to proceed, not completed file transfer. Review the view, workload and outcome evidence separately.

Source: Snowflake query history retention, latency and exclusions. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Query history is immediate and sufficient proof of every completed operation.

Buyer evidence still required

  • Chosen view, time range and visibility after documented delay
  • Workload coverage and any aggregate history needed
  • Independent outcome evidence for file transfer or other claimed effects

Suggested review condition: Do not infer inactivity or completed transfer from a single history result.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck history coverage, workload types and status definitions.

Optional saved evidence: Save the activity-evidence limitations used in a data-platform review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake secure sharing and independent custody

Question: Does access to a Snowflake secure data share give the consumer an independently stored exit copy?

Snowflake Secure Data Sharing provides access through the services layer without copying or transferring the shared data between accounts. Consumers receive permitted read access to shared objects. Access to a share therefore does not establish possession of a separate export that remains usable independently of the provider’s sharing and object availability.

Source: About Secure Data Sharing | Snowflake Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does access to a Snowflake secure data share give the consumer an independently stored exit copy?

Buyer evidence still required

  • Provider share and consumer database/object scope
  • Granted access and provider dependency
  • Separately created export, destination custody and completeness evidence

Review inference: Distinguish ongoing shared access from a verified, independently held export in an exit plan.

Suggested review condition: Do not accept a share reference as proof of an independent retained data copy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether a consumer has separately materialised or exported data is unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid treating a revocable access path as a completed data migration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Independent data ownership, durable access or a complete export from a share grant
  • Whether a consumer has separately materialised or exported data is unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake sessions: The primary role is not the whole access picture

Question: Does a restricted primary Snowflake role prove the session cannot use broader privileges?

Active secondary roles contribute privileges for many SQL operations alongside the primary role and inherited grants. Creation authority is evaluated differently, through the primary role. Inspect the active role set and operation rather than infer the complete permission boundary from the primary-role name.

Source: Snowflake active roles and privilege evaluation. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: The primary role name establishes all effective session permissions.

Buyer evidence still required

  • Primary and active secondary role identities.
  • Inherited grants and object ownership.
  • The exact operation and its authorisation evidence.

Suggested review condition: Do not equate a narrow primary role with a narrow session without the secondary-role context.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Active roles, inherited grants, ownership and SQL operation

Optional saved evidence: Retain the actual role-combination questions needed for an access decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake tags: Applicable types and policy precedence

Question: Does assigning a masking tag prove its policy governs every tagged column?

Tag-based masking depends on the column type matching a policy signature; a tag can hold one masking policy per supported type. If a column also has a directly assigned masking policy, that direct policy takes precedence. Review the effective policy per column rather than treating tag presence as sufficient evidence.

Source: Snowflake: Tag-based masking policies. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A masking tag always determines the result for every tagged column.

Buyer evidence still required

  • Tagged columns and actual data types.
  • Tag policies and direct column-policy assignments.
  • Effective query-role output for the intended columns.

Suggested review condition: Confirm type coverage and precedence before asserting consistent tag-based masking.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Column inventory, data types, tag inheritance, direct policies and query-role context.

Optional saved evidence: Preserve the effective-policy questions behind a supplier masking claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake transient table recovery limits

Question: Does a Snowflake transient table retain the same historical recovery window as a permanent table?

Snowflake transient tables support zero or one day of Time Travel and have no Fail-safe period. Permanent tables have a separate seven-day Fail-safe period and edition-dependent Time Travel settings. Selecting a transient table changes the recovery boundary; neither a table name nor a general account retention assumption establishes the applicable history.

Source: Working with Temporary and Transient Tables | Snowflake Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Snowflake transient table retain the same historical recovery window as a permanent table?

Buyer evidence still required

  • Table type, account edition and effective retention settings
  • Required recovery point and relevant object changes
  • Separate export or backup inventory and verification results

Review inference: Record table type, edition and effective retention before deciding whether an exit or recovery plan can depend on historical data.

Suggested review condition: Reject permanent-table recovery assumptions for transient data without a separately verified copy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual retained history and availability of an independent export are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid losing a required recovery option through an unsuitable storage class.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Permanent-table recovery guarantees for transient objects
  • Actual retained history and availability of an independent export are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snowflake unload results and policy context

Question: Does a successful Snowflake COPY INTO location export prove that all unmasked source rows and their governance policies were preserved?

COPY INTO location unloads a table or query result. Snowflake masking policies can transform unloaded values, and row access policies govern rows visible to the query under their evaluated context. A successful unload therefore reflects its query and policy context; it does not establish an unfiltered, unmasked source copy or a portable enforcement implementation in the output files.

Source: COPY INTO *<location>* | Snowflake Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a successful Snowflake COPY INTO location export prove that all unmasked source rows and their governance policies were preserved?

Buyer evidence still required

  • Unload query, execution context and destination file inventory
  • Row access and masking policies relevant to selected objects
  • Required content, file hashes and source-to-export comparison

Review inference: Reconcile required rows and fields against the executed query, role context and applicable policies.

Suggested review condition: Reject complete unmasked-export claims without accounting for filters, policy effects and missing fields.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual exported values, hidden rows and enforcement at the destination are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a technically successful export from concealing missing or transformed business data.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete raw-source export or automatic transfer of Snowflake policy enforcement
  • Actual exported values, hidden rows and enforcement at the destination are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snyk ignores: Scope and expiry are not remediation

Question: Does a Snyk ignore rule establish that a vulnerability was fixed?

The ignore command changes policy treatment of an issue; it does not document a code fix. Paths and expiry determine scope. The .snyk issue-ignore mechanism is not supported for Snyk Code, which has a separate workflow. An invalid expiry can leave an ignore in place indefinitely, so inspect the effective policy.

Source: Snyk CLI: Ignore. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: An ignored issue has been remediated.

Buyer evidence still required

  • Exact issue, scanner and policy file.
  • Applicable paths, reason and parsed expiry.
  • Separate evidence of a fix or accepted exception.

Suggested review condition: Do not treat an ignore as remediation; require the scoped exception or fix evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Scanner, issue ID, policy path, resource scope, expiry and fix evidence.

Optional saved evidence: Save the exception boundary used in a supplier vulnerability review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Snyk MCP: Folder trust and scan-time build execution

Question: Can a Snyk dependency scan execute project tooling, even when the task is only a security review?

Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.

Source: Snyk MCP scanning, folder trust and ecosystem execution. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official Studio MCP and CLI-backed scanning

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Snyk publishes Studio MCP and the supporting CLI.

Documented by publisher. Snyk MCP scanning, folder trust and ecosystem execution; Snyk CLI authentication and account selection

Purpose

Scan code, dependencies, configuration and other supported artifact types.

Documented by publisher. Snyk MCP scanning, folder trust and ecosystem execution; Snyk CLI authentication and account selection

Read capability

Selected project contents, dependency information and scan results.

Documented by publisher. Snyk MCP scanning, folder trust and ecosystem execution; Snyk CLI authentication and account selection

Write capability

Dependency scans may invoke third-party ecosystem tooling locally.

Documented by publisher. Snyk MCP scanning, folder trust and ecosystem execution; Snyk CLI authentication and account selection

Authentication

CLI authentication supports OAuth and other documented token methods.

Documented by publisher. Snyk MCP scanning, folder trust and ecosystem execution; Snyk CLI authentication and account selection

Permission surface

Folder trust, selected scan and authenticated organization affect operation.

Documented by publisher. Snyk MCP scanning, folder trust and ecosystem execution; Snyk CLI authentication and account selection

Data leaving the environment

Assess project information sent to Snyk and local tools for the chosen scan.

Review inference. Snyk MCP scanning, folder trust and ecosystem execution; Snyk CLI authentication and account selection

Failure modes to consider

Untrusted build tooling or the wrong organization can invalidate the intended scan boundary.

Review inference. Snyk MCP scanning, folder trust and ecosystem execution; Snyk CLI authentication and account selection

Unknowns and applicability

Repository behavior, effective trust settings and scan-product data flow are unverified.

Not established

Suggested refusal or clarification condition

Require repository and execution-scope review before scans that invoke project tooling.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck scan type, build-tool behavior, folder trust and Snyk organization.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Keep the folder-trust and execution-context assumptions attached to a scan approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Socket MCP: Package scores and query authority

Question: Does a Socket MCP dependency score establish that my application is safe to deploy?

The documented connector retrieves package security and quality information. Hosted access uses OAuth; the local deployment requires a token with packages:list. A score concerns the supplied dependency identity, not an independently tested application. Client rules can request checks but do not establish that every dependency was checked or a deployment was blocked.

Source: Socket MCP guide. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer deployment unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Socket publishes the MCP integration and operates its hosted endpoint.

Documented by publisher. Socket MCP guide; Local Socket MCP permissions

Purpose

Retrieve dependency scores and package information.

Documented by publisher. Socket MCP guide; Local Socket MCP permissions

Read capability

Package metadata for requested dependency identities.

Documented by publisher. Socket MCP guide; Local Socket MCP permissions

Write capability

The reviewed scoring surface does not document package-management mutations.

Documented by publisher. Socket MCP guide; Local Socket MCP permissions

Authentication

Hosted OAuth or a local Socket API token.

Documented by publisher. Socket MCP guide; Local Socket MCP permissions

Permission surface

The local guide requires packages:list; actual token grants remain unverified.

Documented by publisher. Socket MCP guide; Local Socket MCP permissions

Data leaving the environment

Requested package identities and results cross the service/client boundary.

Review inference. Socket MCP guide; Local Socket MCP permissions

Failure modes to consider

Wrong versions, incomplete dependency input or ignored client rules can leave the decision unsupported.

Review inference. Socket MCP guide; Local Socket MCP permissions

Unknowns and applicability

Installed server revision, dependency completeness and buyer application behaviour are unknown.

Not established

Suggested refusal or clarification condition

Require exact package coordinates and separate application evidence for a deployment decision.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Scoring tools, authentication and package coverage.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save a source-bound interpretation of dependency scores for a purchase or integration review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SonarQube MCP: Read-only filtering and deployment variants

Question: Does connecting SonarQube MCP automatically restrict an agent to reading findings?

The self-hosted server documents a read-only setting that disables write operations, but its default is false. Tool-set filters further narrow availability; per-request headers cannot widen server restrictions. Hosted and local variants differ, so a configuration review must bind the variant, identity and enabled tools rather than assume all connections are read-only.

Source: SonarSource MCP server repository. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Publisher self-hosted server; hosted variants have different tool coverage

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

SonarSource publishes the server; deployment may be local, self-hosted or publisher-hosted.

Documented by publisher. SonarSource MCP server repository; SonarQube MCP configuration; SonarQube MCP overview and data telemetry

Purpose

Retrieve code-quality context and perform supported analysis or finding operations.

Documented by publisher. SonarSource MCP server repository; SonarQube MCP configuration; SonarQube MCP overview and data telemetry

Read capability

Project, issue, metric, quality-gate and related information permitted to the identity.

Documented by publisher. SonarSource MCP server repository; SonarQube MCP configuration; SonarQube MCP overview and data telemetry

Write capability

Issue and security-hotspot status changes are available unless filtered out.

Documented by publisher. SonarSource MCP server repository; SonarQube MCP configuration; SonarQube MCP overview and data telemetry

Authentication

Local configuration uses a SonarQube token; HTTP examples use bearer credentials.

Documented by publisher. SonarSource MCP server repository; SonarQube MCP configuration; SonarQube MCP overview and data telemetry

Permission surface

Read-only and tool-set filters are cumulative; request headers only narrow server scope.

Documented by publisher. SonarSource MCP server repository; SonarQube MCP configuration; SonarQube MCP overview and data telemetry

Data leaving the environment

Relevant source or analysis data can reach SonarQube and the client, depending on the selected tools.

Review inference. SonarSource MCP server repository; SonarQube MCP configuration; SonarQube MCP overview and data telemetry

Failure modes to consider

Variant differences, token scope and filesystem-dependent analysis can change exposure or availability.

Review inference. SonarSource MCP server repository; SonarQube MCP configuration; SonarQube MCP overview and data telemetry

Unknowns and applicability

Buyer configuration, entitlements, source mounts and Results Data usage rights are unverified.

Not established

Suggested refusal or clarification condition

Require explicit authority before changing findings; do not treat internal-use Results Data terms as redistribution clearance.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Default filters, hosted coverage, analysis entitlements and result-use terms.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the exact restrictions needed to keep a review workflow read-only.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SonarQube tokens: Analysis scope and user authority

Question: Does a SonarQube token used by a scanner have only analysis permissions?

User tokens carry the issuing user permissions, including administrative rights where applicable. Project analysis tokens restrict analysis to the associated project and depend on the author retaining Execute Analysis permission. Connected-mode clients require user tokens, so a project-token assumption cannot be applied to every integration.

Source: SonarQube: Managing tokens. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every scanner integration token is restricted to one project.

Buyer evidence still required

  • Token type and issuing identity, without the secret.
  • Effective permissions and associated project.
  • Client authentication requirements and revocation checks.

Suggested review condition: Inspect token type and effective grants before calling an integration least-privileged.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Client purpose, token type, issuing identity, project and effective grants.

Optional saved evidence: Preserve the credential-scope review without storing the credential.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Sparkplug aliases and birth-message context

Question: Can a Sparkplug metric alias be interpreted without the associated birth-message mapping?

Sparkplug 3.0.0 permits aliases but requires each alias to be unique across the Edge Node metrics. Birth messages carry the metric name and alias together; subsequent data and command messages using aliases omit the name. A numeric alias therefore needs the applicable birth mapping, including the node context, before a consumer can identify the intended metric.

Source: Sparkplug 3.0.0 release — Sparkplug_6_Payloads. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Sparkplug metric alias be interpreted without the associated birth-message mapping?

Buyer evidence still required

  • Applicable NBIRTH and DBIRTH mappings
  • Edge Node and device identifiers
  • Alias values in the received messages

Review inference: Prevent an alias from being attributed to the wrong measurement or command. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse metric attribution when the applicable alias mapping is unavailable.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The deployed alias assignments and session continuity were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The deployed alias assignments and session continuity were not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug change-only updates and state reconstruction

Question: Can a Sparkplug consumer treat each DATA message as a complete snapshot of every metric?

Sparkplug 3.0.0 requires the birth sequence to expose the metrics for the session and recommends that subsequent DATA messages contain only changed values. Unchanged values need not recur until a new session. Reconstructing state therefore needs the applicable birth values and subsequent changes; a single DATA message is not necessarily a full snapshot.

Source: Sparkplug 3.0.0 release — Sparkplug_5_Operational_Behavior. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Sparkplug consumer treat each DATA message as a complete snapshot of every metric?

Buyer evidence still required

  • Complete applicable birth sequence
  • Subsequent data updates
  • Gap and session-change detection

Review inference: Retain baseline values when reconstructing current declared state. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse full-state claims from one change-only DATA message.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Completeness of the captured birth and update sequence was not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Completeness of the captured birth and update sequence was not verified.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug conformance and command authority

Question: Does Sparkplug protocol conformance prove that command-topic permissions are correctly secured?

Sparkplug 3.0.0 presents its security chapter as non-normative guidance, discussing MQTT client identity, credentials and topic access control. These considerations do not make protocol conformance an independent permission audit. A buyer must inspect the actual broker and application authorization policies for publishing and subscribing to command topics.

Source: Sparkplug 3.0.0 release — Sparkplug_7_Security. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Sparkplug protocol conformance prove that command-topic permissions are correctly secured?

Buyer evidence still required

  • Broker topic access policy
  • Authenticated principal-to-client mapping
  • Intended NCMD and DCMD publishers

Review inference: Review command authority separately from protocol conformance. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse command-security approval based only on Sparkplug conformance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual broker permissions and command enforcement were not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual broker permissions and command enforcement were not assessed.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug data types and birth definitions

Question: Can an agent infer a Sparkplug metric datatype from the data message alone?

Sparkplug 3.0.0 requires a metric datatype in NBIRTH and DBIRTH and says it should not be included in subsequent data and command messages. Consumers need the birth definition to interpret the metric consistently. The representation of a value in the payload is not a substitute for the declared Sparkplug datatype and its applicable node or device context.

Source: Sparkplug 3.0.0 release — Sparkplug_6_Payloads. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an agent infer a Sparkplug metric datatype from the data message alone?

Buyer evidence still required

  • Birth-message datatype
  • Metric name or resolved alias
  • Payload value and node/device context

Review inference: Retain the schema needed to interpret or prepare metric values. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse datatype-dependent decisions without the applicable birth definition.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual decoder compatibility and device value semantics were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual decoder compatibility and device value semantics were not tested.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug death messages and session correlation

Question: Can a delayed Sparkplug NDEATH be applied to a newer birth session without checking bdSeq?

Sparkplug 3.0.0 uses bdSeq to correlate NBIRTH with the corresponding NDEATH. A delayed Will can arrive after a later birth, so consumers must assess the matching session instead of treating arrival order alone as current state. A rebirth request within the same MQTT session retains bdSeq; a new birth message does not by itself prove a new connection.

Source: Sparkplug 3.0.0 release — Sparkplug_5_Operational_Behavior. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a delayed Sparkplug NDEATH be applied to a newer birth session without checking bdSeq?

Buyer evidence still required

  • NBIRTH bdSeq history
  • NDEATH bdSeq and arrival order
  • Connection and rebirth context

Review inference: Avoid marking a current node offline because of a previous session message. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse current-session death attribution without matching session evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual connection history and delivery order were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual connection history and delivery order were not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug death timestamps and outage timing

Question: Does the timestamp in a Sparkplug NDEATH identify when the node actually failed?

Sparkplug 3.0.0 explains that a Will payload is prepared during MQTT CONNECT, so its original NDEATH timestamp is not a reliable failure instant. Host processing marks the node offline using host time. A Sparkplug-aware broker may replace the timestamp with its attempted delivery time. These times have different meanings and do not independently establish the physical outage instant.

Source: Sparkplug 3.0.0 release — Sparkplug_5_Operational_Behavior. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the timestamp in a Sparkplug NDEATH identify when the node actually failed?

Buyer evidence still required

  • Will preparation and broker policy
  • Host receipt time
  • Independent outage or connectivity observations

Review inference: Avoid reconstructing an outage from the wrong timestamp origin. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse exact outage timing from an unqualified NDEATH timestamp.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual failure instant and broker replacement policy were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The actual failure instant and broker replacement policy were not observed.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug explicit null values

Question: Does a Sparkplug metric with is_null mean that its measured value is zero?

Sparkplug 3.0.0 provides is_null to indicate a null metric value, with the value field permitted to be omitted. This is distinct from an actual numeric zero or false Boolean. A consumer must preserve that distinction when evaluating a reading, rather than silently filling an absent value with a successful measurement.

Source: Sparkplug 3.0.0 release — Sparkplug_6_Payloads. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Sparkplug metric with is_null mean that its measured value is zero?

Buyer evidence still required

  • is_null and value-field presence
  • Birth datatype
  • Consumer null-handling policy

Review inference: Avoid fabricated measurements from null payloads. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse zero-value or false-state assertions obtained by defaulting a null metric.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The reason for the null reading is not independently established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The reason for the null reading is not independently established.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug historical values and live decisions

Question: Can a Sparkplug metric marked is_historical be treated as a current live reading?

Sparkplug 3.0.0 describes is_historical as marking a historical value, including data delivered through store-and-forward or batch collection. The flag separates delayed observations from real-time updates. A consumer must interpret that value with its timestamp and intended use; arrival in the latest message does not make a historical metric current.

Source: Sparkplug 3.0.0 release — Sparkplug_6_Payloads. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Sparkplug metric marked is_historical be treated as a current live reading?

Buyer evidence still required

  • is_historical flag
  • Metric capture timestamp
  • Consumer policy for historical values

Review inference: Keep delayed data out of decisions requiring current readings. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse current-state conclusions from a historical metric without separate current evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual sensor state and elapsed delay were not independently measured.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual sensor state and elapsed delay were not independently measured.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug intentional disconnect evidence

Question: Will a clean MQTT disconnect automatically publish the Sparkplug node death message?

Sparkplug 3.0.0 requires an intentionally disconnecting Edge Node to publish NDEATH before sending MQTT DISCONNECT. A clean disconnect suppresses the broker Will, so relying only on the Will would omit that notification. If no DISCONNECT is sent and a later Will duplicates the death notification, the host must use the matching bdSeq to avoid duplicate processing.

Source: Sparkplug 3.0.0 release — Sparkplug_5_Operational_Behavior. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Will a clean MQTT disconnect automatically publish the Sparkplug node death message?

Buyer evidence still required

  • NDEATH publication record
  • MQTT DISCONNECT handling
  • Host bdSeq duplicate handling

Review inference: Check the explicit shutdown notification path. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse a complete shutdown-notification claim based only on configured Last Will.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual shutdown delivery was not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual shutdown delivery was not observed.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug multiple samples in one payload

Question: Can repeated appearances of one Sparkplug metric in a DATA payload be discarded as duplicates?

Sparkplug 3.0.0 permits multiple changes for the same metric within one DATA message when the samples have distinct timestamps. It also requires non-historical metrics in chronological order. A consumer that deduplicates by metric name alone can discard legitimate intermediate samples; interpretation needs the individual timestamps and the historical flag.

Source: Sparkplug 3.0.0 release — Sparkplug_5_Operational_Behavior. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can repeated appearances of one Sparkplug metric in a DATA payload be discarded as duplicates?

Buyer evidence still required

  • Metric identifiers and each timestamp
  • Historical flags
  • Consumer ordering and deduplication rules

Review inference: Preserve intermediate samples during payload normalization. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse lossless-conversion claims when repeated metric names are collapsed without sample context.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual sample completeness and clock order were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual sample completeness and clock order were not verified.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug node death and child-device state

Question: Does Sparkplug marking every child device offline mean those physical devices have stopped?

Sparkplug 3.0.0 directs the host to mark the Edge Node and its associated devices offline after the applicable NDEATH and to mark their birth metrics STALE. This describes the host view of unavailable data through that node. It is not physical shutdown evidence for each device, which may continue operating while its reporting path is unavailable.

Source: Sparkplug 3.0.0 release — Sparkplug_5_Operational_Behavior. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Sparkplug marking every child device offline mean those physical devices have stopped?

Buyer evidence still required

  • Applicable NDEATH and birth device inventory
  • Host offline and stale state transitions
  • Independent physical-state evidence

Review inference: Separate loss of telemetry from physical equipment state. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse equipment-stopped assertions from the Sparkplug offline state alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Physical equipment behaviour was not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Physical equipment behaviour was not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug omitted Quality properties

Question: Does an omitted Sparkplug Quality property independently prove a sensor reading is good?

Sparkplug 3.0.0 defines an optional Quality property and requires it when quality is not GOOD. Under that convention, omission represents the default GOOD condition. This is a declaration convention, not an independent sensor or calibration check. Buyers need the producer implementation and measurement evidence before relying on an omitted property as proof of quality.

Source: Sparkplug 3.0.0 release — Sparkplug_6_Payloads. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does an omitted Sparkplug Quality property independently prove a sensor reading is good?

Buyer evidence still required

  • Presence and value of Quality
  • Producer conformance and encoding policy
  • Independent measurement or calibration evidence

Review inference: Distinguish default quality encoding from demonstrated measurement quality. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse verified-quality claims based solely on omission of Quality.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Sensor accuracy and producer compliance were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Sensor accuracy and producer compliance were not verified.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug publication and measurement times

Question: Which Sparkplug timestamp should a buyer use to distinguish sample age from publication delay?

Sparkplug 3.0.0 distinguishes the payload timestamp, representing publication time, from metric timestamps associated with captured values. The specification describes metric timestamps as UTC capture times and requires them in birth and data messages. Comparing the two can support a declared delay assessment, but neither field independently establishes clock accuracy or physical measurement time.

Source: Sparkplug 3.0.0 release — Sparkplug_6_Payloads. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Which Sparkplug timestamp should a buyer use to distinguish sample age from publication delay?

Buyer evidence still required

  • Payload publication timestamp
  • Individual metric timestamps
  • Device clock and synchronization evidence

Review inference: Separate declared sample age from transport timing. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse freshness guarantees based only on the payload publication time.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Clock synchronization and actual sampling were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Clock synchronization and actual sampling were not verified.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug reorder recovery and missing data

Question: Does a Sparkplug rebirth after a sequence gap recover every missing historical sample?

Sparkplug 3.0.0 recommends a configurable reorder timeout. Where configured, unresolved missing sequence messages at timeout require a rebirth request. Rebirth stops data publication temporarily and sends the complete birth sequence to restore the consumer state. This is not a promise to replay every missing sample or reconstruct the lost interval.

Source: Sparkplug 3.0.0 release — Sparkplug_5_Operational_Behavior. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Sparkplug rebirth after a sequence gap recover every missing historical sample?

Buyer evidence still required

  • Sequence-gap and timeout observations
  • Rebirth request and response sequence
  • Separate retained historical samples

Review inference: Separate state resynchronization from historical gap recovery. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse complete-history claims based only on a successful rebirth.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual loss, retained history and downstream recovery were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual loss, retained history and downstream recovery were not tested.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug sequence wrap and message counts

Question: Does a repeated Sparkplug seq value prove that a message is a duplicate?

Sparkplug 3.0.0 uses an Edge Node message sequence in the range 0 to 255 and wraps after 255. NDEATH is excluded from this sequence. A repeated seq value can therefore be expected after wrap and cannot serve as a globally unique message identifier. Reconstruction needs node, session and ordering context as well as the sequence value.

Source: Sparkplug 3.0.0 release — Sparkplug_6_Payloads. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a repeated Sparkplug seq value prove that a message is a duplicate?

Buyer evidence still required

  • Node and session identification
  • Ordered message capture around wrap
  • Message type and seq value

Review inference: Avoid false duplicate removal at sequence wrap. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse global deduplication using seq alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Complete delivery and actual retransmission behaviour were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Complete delivery and actual retransmission behaviour were not verified.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug transient flags and storage evidence

Question: Does Sparkplug is_transient prove a metric was never retained by a downstream historian?

Sparkplug 3.0.0 describes is_transient as identifying a value that should not be stored by a historian. That expresses intended treatment of the metric; it does not demonstrate what any downstream consumer actually retained. A buyer assessing storage obligations still needs consumer configuration and retention evidence for each relevant copy.

Source: Sparkplug 3.0.0 release — Sparkplug_6_Payloads. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Sparkplug is_transient prove a metric was never retained by a downstream historian?

Buyer evidence still required

  • is_transient flag
  • Historian and intermediary retention configuration
  • Evidence of stored copies and disposition

Review inference: Separate a storage instruction from observed retention. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse non-retention claims from the transient flag alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Downstream storage and deletion were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Downstream storage and deletion were not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Sparkplug-aware stored births and current values

Question: Are retained birth messages from a Sparkplug-aware broker guaranteed to contain current metric values?

Sparkplug 3.0.0 requires a Sparkplug-aware broker to store the latest NBIRTH and DBIRTH and expose them on designated retained $sparkplug topics. These remain the original birth messages: later DATA changes do not make their metric values current. The specification explicitly warns consumers to account for those subsequent updates.

Source: Sparkplug 3.0.0 release — Sparkplug_10_Conformance. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Are retained birth messages from a Sparkplug-aware broker guaranteed to contain current metric values?

Buyer evidence still required

  • Stored birth publication time
  • Subsequent data changes
  • Broker profile and retained-topic source

Review inference: Avoid using cached birth values as a live equipment snapshot. This is a review judgment, not a measured deployment result.

Suggested review condition: Refuse current-value claims from stored birth messages alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The broker cache and intervening data were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The broker cache and intervening data were not inspected.
  • No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPDX: Standard and certification boundary

Question: Does publishing an SPDX document certify the software it describes?

SPDX is an open specification for exchanging supply-chain information. Its standards status does not certify a submitted document's completeness, license conclusions or the safety of its software.

Source: SPDX Specifications. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • software safety certification
  • complete component inventory
  • verified license compliance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SPIFFE federation endpoint binding

Question: Does a downloaded SPIFFE trust bundle identify which trust domain it is authorized to represent?

The pinned federation specification says a bundle does not contain its trust-domain name. Clients must configure the endpoint URL, profile and associated trust domain before retrieval. Bundles from different domains must remain separate; merging them allows one domain to forge identities in another under the combined trust store. HTTPS success alone does not supply the missing domain binding.

Source: SPIFFE Federation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a downloaded SPIFFE trust bundle identify which trust domain it is authorized to represent?

Buyer evidence still required

  • Approved endpoint/profile/domain mapping
  • Separate stored trust bundles
  • Independent approval for the endpoint-to-domain association

Review inference: Validate the configured issuer namespace before accepting a foreign workload. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not infer domain authority from an arbitrary HTTPS bundle or merge trust domains.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer federation mapping and endpoint control are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer federation mapping and endpoint control are unknown.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPIFFE federation key rollout

Question: Can a new SPIFFE signing key be used before foreign verifiers can fetch its bundle?

The pinned federation specification requires new externally used keys to appear at the bundle endpoint before issuing SVIDs with them. It recommends publication three to five refresh-hint intervals in advance and removing deprecated keys after no valid SVIDs remain. These are rollout conditions; a successful local issuance does not prove foreign verifiers have refreshed.

Source: SPIFFE Federation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a new SPIFFE signing key be used before foreign verifiers can fetch its bundle?

Buyer evidence still required

  • Bundle publication and issuance times
  • Refresh policy and outstanding credential lifetimes
  • Foreign verifier refresh observations during the rotation window

Review inference: Plan key rotation without interpreting propagation failures as unauthorized identity. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not claim federation readiness from local issuance without publication and propagation evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Foreign client refresh times and actual outages have not been observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Foreign client refresh times and actual outages have not been observed.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPIFFE filesystem key and certificate consistency

Question: Can separate file reads load a mismatched SPIFFE private key and certificate despite atomic rotation?

The pinned, incubating filesystem delivery specification recommends loading the credential bundle in one open/read/close cycle. Separate cycles for key and certificate can straddle a rotation and produce a mismatched pair, even when the provisioning system writes atomically. Applications must reload updated bundles promptly and must not assume the new key type or chain matches the old one.

Source: The SPIFFE Filesystem Delivery Standard. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can separate file reads load a mismatched SPIFFE private key and certificate despite atomic rotation?

Buyer evidence still required

  • Provisioner replacement method
  • Consumer file-read and reload sequence
  • Deployed filesystem-delivery standard revision and file permissions

Review inference: Verify that credential reloads preserve the key-to-certificate pairing. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not treat atomic file replacement as proof that multiple independent reads are consistent.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer filesystem, file permissions and reload implementation are untested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer filesystem, file permissions and reload implementation are untested.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • The filesystem delivery standard is incubating; stable support in a buyer implementation is not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPIFFE filesystem withdrawal signals

Question: Does an empty SPIFFE credential file mean the client should keep its last cached identity?

The pinned, incubating filesystem delivery specification defines an empty credential or trust-bundle file as deliberate redaction. Consumers should unload the withdrawn material, including individual anchors removed from a remaining bundle. An absent file can instead reflect remounting or repopulation; emptiness is the stronger intentional signal. Keeping cached identity indefinitely would erase that distinction.

Source: The SPIFFE Filesystem Delivery Standard. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does an empty SPIFFE credential file mean the client should keep its last cached identity?

Buyer evidence still required

  • File-content transitions and mount events
  • Consumer cache and trust-anchor removal policy
  • Deployed consumer redaction behaviour and open-session policy

Review inference: Distinguish explicit credential withdrawal from transient filesystem absence. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not silently retain deliberately emptied credentials as a malformed-update fallback.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual withdrawal propagation and existing sessions remain unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual withdrawal propagation and existing sessions remain unobserved.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • The filesystem delivery standard is incubating; stable support in a buyer implementation is not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPIFFE identity ambiguity in certificates

Question: Can an X509-SVID with two URI SAN identities be accepted if its certificate chain verifies?

The pinned X509-SVID specification requires exactly one URI subject alternative name and one SPIFFE ID. Validators must reject more than one URI SAN, even when ordinary certificate-path validation succeeds. Other SAN types may be present. The identity selection rule prevents a verifier from arbitrarily choosing which workload identity to authorize.

Source: The X.509 SPIFFE Verifiable Identity Document. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can an X509-SVID with two URI SAN identities be accepted if its certificate chain verifies?

Buyer evidence still required

  • Presented certificate and SAN types
  • SPIFFE-aware validation result
  • Expected workload identity and deployed validation-library version

Review inference: Reject ambiguous workload identity before mapping a certificate to tool authority. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not choose one URI identity from a certificate that violates the single-URI rule.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer certificate or validator output has been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No buyer certificate or validator output has been inspected.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPIFFE signing authority versus caller identity

Question: Can a SPIFFE CA signing certificate authenticate as the workload it issues credentials for?

The pinned X509-SVID specification reserves caller authentication for leaf certificates and prohibits using signing certificates for authentication. A leaf must have cA false, lack keyCertSign and cRLSign, and carry a SPIFFE ID with a non-root path. Possessing valid signing material is not interchangeable with presenting a valid workload leaf.

Source: The X.509 SPIFFE Verifiable Identity Document. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a SPIFFE CA signing certificate authenticate as the workload it issues credentials for?

Buyer evidence still required

  • Leaf and chain certificate fields
  • Expected workload SPIFFE ID
  • Caller-to-business-principal mapping for the requested action

Review inference: Keep credential-issuing authority separate from the identity requesting a tool action. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not authorize a caller using a CA certificate in place of its workload leaf.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual key custody and the caller are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual key custody and the caller are unobserved.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPIFFE streamed identity withdrawal

Question: Should a workload keep an old SPIFFE bundle when a later API response omits it?

SPIFFE Workload API stream responses are complete replacements, not incremental patches. Default or empty fields must replace previous values; omitted material should be treated as redacted. The X509 profile says clients should cease using redacted SVIDs or bundles, including withdrawal indicated by PermissionDenied. Retaining previously cached authority can contradict that update.

Source: The SPIFFE Workload API. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Should a workload keep an old SPIFFE bundle when a later API response omits it?

Buyer evidence still required

  • Previous and subsequent stream responses
  • Consumer cache-replacement behaviour
  • Time the consumer applied the last complete identity response

Review inference: Check whether credential caches actually apply withdrawal notifications. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not merge an omitted credential back into a complete replacement response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Propagation delay and deployed client compliance are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Propagation delay and deployed client compliance are unknown.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPIFFE token replay and uniqueness

Question: Does a JWT-SVID jti claim make a SPIFFE workload token single-use?

The pinned JWT-SVID specification permits jti but does not require validators to track its uniqueness. JWT-SVIDs remain bearer tokens: audience and expiry constrain exposure without eliminating replay. A token with multiple audiences can be replayed by one recipient to another listed recipient. Single-use acceptance therefore needs separately evidenced controls.

Source: The JWT SPIFFE Verifiable Identity Document. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a JWT-SVID jti claim make a SPIFFE workload token single-use?

Buyer evidence still required

  • Token audiences, expiry and identifier
  • Validator replay-state design and request evidence
  • Approved receiver identity and token validation configuration

Review inference: Decide whether a captured workload token can be reused for another tool call. This is a source-based review decision, not an observed deployment result.

Suggested review condition: Do not infer single-use protection from jti or a valid signature alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer validator and replay state have not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer validator and replay state have not been tested.
  • Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SPIFFE: Identity material retrieval

Question: What can a workload obtain through the SPIFFE Workload API?

The Workload API defines retrieval of workload identity documents and trust material. Availability and entitlement depend on the implementation and its configured caller identification.

Source: SPIFFE Workload API. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • access to identities belonging to other workloads
  • an available endpoint in a buyer's deployment
  • automatic entitlement

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SPIFFE: Short-lived workload credentials

Question: Can SPIFFE tooling support short-lived credentials for workload authentication?

SPIFFE deployment guidance describes workload-bound keys and short-lived X.509 credentials for authentication and TLS. Correct rotation and acceptance still depend on the deployment.

Source: Working with SVIDs. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • working credential rotation in a named system
  • uninterrupted availability during renewal
  • authorisation from certificate possession

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SPIFFE: Trust-domain scope

Question: Can an SVID from any SPIFFE trust domain be accepted automatically?

SPIFFE roots identity trust in the relevant trust domain and signing authority. Acceptance across domains requires an appropriate trust relationship and verification policy.

Source: SPIFFE Identity and SVID. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • automatic cross-domain trust
  • universal acceptance of an SVID
  • validity based only on an identity string

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SPIFFE: Workload API caller checks

Question: Does the Workload API's lack of an explicit client secret mean caller checks are unnecessary?

The Workload API specification places caller identification on the endpoint implementation through out-of-band checks. Lack of an application-level secret does not mean callers may be accepted without identification.

Source: SPIFFE Workload API. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • anonymous access as the intended trust model
  • caller identification verified in a named deployment
  • security from endpoint reachability alone

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SPIFFE: Workload identity

Question: What does a SPIFFE SVID establish about a workload?

An SVID lets a workload present a verifiable SPIFFE identity. Identity evidence does not by itself grant permission for a requested action or demonstrate the workload's behaviour.

Source: SPIFFE Identity and SVID. Documentation checked 2026-10-07; no deployment validation is claimed.

Claim boundaries
  • permission to execute an action
  • trustworthiness of workload behaviour
  • identity as proof of claim truth

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SPIRE: A node alias widens identity eligibility

Question: Does a SPIRE workload registration parent identify only one machine when it names a node alias?

A workload registration has one parent ID, which may identify a specific node or a node alias shared by a set of nodes. Nodes matching the alias selectors can obtain SVIDs for workloads registered under that parent. The parent text alone does not establish single-machine scope.

Source: Registering workloads | SPIFFE. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does a SPIRE workload registration parent identify only one machine when it names a node alias?

Buyer evidence still required

  • Workload entry and parent ID.
  • Node alias registration and selectors.
  • Attested node membership and workload selectors.

Suggested review condition: Do not report single-host identity confinement without resolving a parent alias and its matching nodes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workload entry and parent ID. Node alias registration and selectors. Attested node membership and workload selectors.

Optional saved evidence: Assess how many hosts can receive an agent workload identity.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual attestation results, identity uniqueness or authorization of downstream actions
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Splunk MCP 1.0: Query guardrails and encrypted-token scope

Question: Does a Splunk MCP 1.0 search result establish complete log coverage?

Version 1.0 describes encrypted-token access and constrained SPL query execution. Unsafe commands or excessive execution time can cause rejection. Search and knowledge-object tools remain bounded by identity and query scope. This dated review does not establish newer-version authentication or that a successful query covered every relevant event.

Source: Splunk MCP 1.0 token and tool management. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Explicitly version 1.0 documentation; newer authentication variants not inferred

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Splunk publishes the Platform MCP integration.

Documented by publisher. Splunk MCP 1.0 token and tool management; Splunk MCP 1.0 tools

Purpose

Run supported SPL searches and retrieve knowledge objects.

Documented by publisher. Splunk MCP 1.0 token and tool management; Splunk MCP 1.0 tools

Read capability

Search results, saved searches, alerts and other supported knowledge objects.

Documented by publisher. Splunk MCP 1.0 token and tool management; Splunk MCP 1.0 tools

Write capability

The reviewed query tool applies guardrails against unsafe or destructive commands; this is not independent safety proof.

Documented by publisher. Splunk MCP 1.0 token and tool management; Splunk MCP 1.0 tools

Authentication

Version 1.0 documents encrypted tokens and specific issuance/execution capabilities.

Documented by publisher. Splunk MCP 1.0 token and tool management; Splunk MCP 1.0 tools

Permission surface

Issuance privileges and tool-execution privileges are distinct.

Documented by publisher. Splunk MCP 1.0 token and tool management; Splunk MCP 1.0 tools

Data leaving the environment

Queries and authorised log content pass between Splunk and the agent client.

Review inference. Splunk MCP 1.0 token and tool management; Splunk MCP 1.0 tools

Failure modes to consider

Guardrail rejection, time limits, stale tokens and incomplete query scope can affect results.

Review inference. Splunk MCP 1.0 token and tool management; Splunk MCP 1.0 tools

Unknowns and applicability

Installed version, role capabilities, index coverage and client handling are unknown.

Not established

Suggested refusal or clarification condition

Do not claim complete incident coverage or apply this version-specific login description to every Splunk deployment.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. MCP version, authentication modes, role capabilities and guardrails.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the dated query and identity limitations used in a log-access decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SQL/vector/entity representations versus single-store exit completeness

Question: Is a Mem0 vector-store export a complete memory custody inventory?

The reviewed architecture separates facts/metadata in SQL, embeddings in a vector database and extracted entities in an entity store; managed and OSS operation differs.

Source: Mem0 primary documentation: mem0 filters. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Is a Mem0 vector-store export a complete memory custody inventory?

Buyer evidence still required

  • managed/OSS mode
  • configured stores
  • fact/vector/entity inventories
  • export manifests
  • residual copies

Review inference: Is a Mem0 vector-store export a complete memory custody inventory? Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions. SQL/vector/entity representations versus single-store exit completeness. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Where memories live

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat one backing-store export as complete; reconcile each configured representation and its owner before exit assertions.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SQS dead letter retention clock

Question: Does moving a message to an SQS dead-letter queue restart its retention clock?

For standard queues the original enqueue timestamp continues to govern expiry, while the dead-letter age metric measures time since the move. FIFO queues reset the enqueue timestamp when a message moves to the dead-letter queue. Queue type and original age therefore determine the remaining recovery window.

Source: Amazon Web Services: Dead-letter queue retention. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does moving a message to an SQS dead-letter queue restart its retention clock?

Buyer evidence still required

  • queue type
  • source and dead-letter retention
  • original enqueue time
  • move time
  • queue metrics

Review inference: An operator delays recovery because the dead-letter queue age appears recent. A standard-queue message can expire earlier than expected. Distinguishes arrival in a dead-letter queue from the previously covered redrive out of it. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer remaining recovery time from the dead-letter age metric alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Setting-up dead-letter queue retention

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer remaining recovery time from the dead-letter age metric alone.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

SQS FIFO: Deduplication scope and business effects

Question: Does FIFO deduplication prevent every duplicate business action?

SQS suppresses repeated sends within its documented deduplication interval. Content-based IDs use the message body rather than message attributes. This queue admission behaviour does not establish a transaction across the consumer and an external service, or protection for retries beyond that interval.

Source: SQS FIFO deduplication. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: FIFO queue deduplication proves end-to-end exactly-once effects.

Buyer evidence still required

  • Deduplication mode and message-ID construction.
  • Retry timing and body-versus-attribute use.
  • Consumer-side commit and replay handling.

Suggested review condition: Do not equate duplicate-send suppression with atomic downstream processing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Deduplication configuration, message identity, retry interval and consumer transaction boundary.

Optional saved evidence: Save the source basis for evaluating exactly-once claims in a queued service.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SQS visibility: Temporary hiding is not completion

Question: Does an SQS visibility timeout prove a task was processed once?

Visibility temporarily hides a received message. Without deletion it becomes available again when the timeout expires, and standard-queue delivery can still duplicate messages. A lease period is not proof that downstream work committed or that repeating the work is harmless.

Source: SQS visibility timeout. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A visibility timeout guarantees one completed business action.

Buyer evidence still required

  • Queue type and visibility settings.
  • Consumer deletion and lease-extension behaviour.
  • Business-operation identity and retry evidence.

Suggested review condition: Require business completion evidence before treating an invisible message as a finished action.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Queue type, visibility lease, consumer acknowledgement and business idempotency.

Optional saved evidence: Preserve the evidence questions separating queue state from a completed customer action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SQS: Redrive identity and recovery lineage

Question: Can an SQS redrive preserve the original message identity and undo messages already moved?

SQS treats redriven messages as new messages with new message IDs and enqueue times, resetting retention. Redriven traffic can interleave with newly produced messages. Canceling a move leaves messages already moved at their destination. Recovery correlation therefore needs application-level action references and destination observations, not only the old message ID or a canceled move status.

Source: Amazon SQS: Dead-letter queue redrive. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an SQS redrive preserve the original message identity and undo messages already moved?

Buyer evidence still required

  • Original message and stable application-action references with the redrive task identifier.
  • Destination queue, new message references and concurrent producer activity.
  • Move cancellation result, already-moved messages and consumer outcomes.

Suggested review condition: Decline restored-lineage or fully-recalled claims without correlating moved messages and destination processing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Original message and stable application-action references with the redrive task identifier. Destination queue, new message references and concurrent producer activity. Move cancellation result, already-moved messages and consumer outcomes.

Optional saved evidence: Operators need to distinguish recovered actions from new work and identify messages still eligible for execution.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Original message-ID preservation, recall of moved messages or once-only execution
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

SQS: Successful delete with a stale receipt handle

Question: Does a successful SQS DeleteMessage response using an old receipt handle prove the message was removed?

SQS requires the receipt handle from the most recent receive. An old handle can produce a successful DeleteMessage response while the message might not be deleted. Standard queues can also rarely return a message after deletion when a stored copy was unavailable during the delete. Application effects therefore still need duplicate handling.

Source: Amazon SQS: DeleteMessage. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a successful SQS DeleteMessage response using an old receipt handle prove the message was removed?

Buyer evidence still required

  • Message ID and non-secret references to successive receives and their receipt handles.
  • Delete attempt correlated with the most recent receive and response.
  • Subsequent delivery observations and duplicate-safe business-effect reconciliation.

Suggested review condition: Decline a removed-or-never-repeated conclusion from a stale-handle success response.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Message ID and non-secret references to successive receives and their receipt handles. Delete attempt correlated with the most recent receive and response. Subsequent delivery observations and duplicate-safe business-effect reconciliation.

Optional saved evidence: Cleanup receipts must identify the current delivery attempt rather than an obsolete receive handle.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed permanent non-redelivery or permission to inspect queue payloads
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Square retry identity and changed payment amounts

Question: Can a Square CreatePayment retry reuse its idempotency key with a changed payment amount?

Square documents that repeating a successful CreatePayment request with the same idempotency key returns the original successful response instead of taking another payment. Reusing that key with a changed request, such as a different amount, returns an error. Square notes that idempotency behavior can vary by API, so this rule must not be generalised to every endpoint.

Source: Idempotency. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a Square CreatePayment retry reuse its idempotency key with a changed payment amount?

Buyer evidence still required

  • Original CreatePayment request and idempotency key
  • Original or recovered provider outcome
  • Proposed changed amount and renewed buyer authority

Review inference: Preserve the original request identity during recovery and treat a changed purchase as a separately authorised operation.

Suggested review condition: Do not rotate keys or change amounts merely to bypass a retry conflict before reconciling the first outcome.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The first request outcome and any separate buyer-approved amendment require transaction evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid duplicate or unintended charges while resolving uncertain payment attempts.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Universal idempotency guarantees across all Square APIs
  • The first request outcome and any separate buyer-approved amendment require transaction evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Square: Delayed authorization can complete automatically

Question: Does leaving a Square delayed-capture payment untouched guarantee it will be cancelled?

The default delay_action is CANCEL, but eligible payments can specify COMPLETE. At delayed_until, Square applies the configured action if the payment is not already terminal. The declared delay and action must therefore be reviewed together; an approved payment is not an indefinite neutral hold.

Source: Delayed Capture of a Card Payment. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does leaving a Square delayed-capture payment untouched guarantee it will be cancelled?

Buyer evidence still required

  • Payment status and delay_action.
  • Server delayed_until value.
  • Cancellation or completion outcome evidence.

Suggested review condition: Do not assume abandonment cancels a payment whose configured deadline action is COMPLETE.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Payment status and delay_action. Server delayed_until value. Cancellation or completion outcome evidence.

Optional saved evidence: Account for an automatic charge path when an agent abandons or retries an intent.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Actual payment outcome, live cancellation or owner permission to charge
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Square: Payment amendments need version reconciliation

Question: Does a Square payment update protect an agent from overwriting another concurrent amendment?

Payment updates are last-write-wins by default. The optional version_token enables optimistic concurrency. Only eligible APPROVED payments and permitted fields can be updated; the payment capabilities and capture/cancel deadline constrain available changes.

Source: Update Payment and Tip Amounts. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Square payment update protect an agent from overwriting another concurrent amendment?

Buyer evidence still required

  • Approved payment and capability fields.
  • Reviewed version_token and proposed fields.
  • Update result and final payment version.

Suggested review condition: Do not treat an unversioned update as evidence that no concurrent terms were overwritten.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Approved payment and capability fields. Reviewed version_token and proposed fields. Update result and final payment version.

Optional saved evidence: Bind a reviewed amount amendment to the exact payment version.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Spending approval, settlement verification or prevention of every concurrent payment change
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Square: Refund state is separate from payment state

Question: Does a Square refund request or a COMPLETED payment establish that the buyer was refunded?

Square refunds have their own status, including PENDING, COMPLETED, FAILED and REJECTED. The original payment can remain COMPLETED after a partial or full refund. Recovery must inspect the PaymentRefund object; request acceptance or payment status alone does not establish refund completion.

Source: Square payment refunds. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Square refund request or a COMPLETED payment establish that the buyer was refunded?

Buyer evidence still required

  • The payment and refund identifiers.
  • The current PaymentRefund status and amount.
  • Provider evidence resolving any pending or failed refund.

Suggested review condition: Do not report a completed refund from request acceptance or the original payment status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The payment and refund identifiers. The current PaymentRefund status and amount. Provider evidence resolving any pending or failed refund.

Optional saved evidence: A purchasing agent must distinguish an accepted refund operation from its later financial outcome.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Bank posting time, live funds receipt or authority to issue another refund
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Stage B: General acceleration boundary

Question: Does Stage B controlled reduction establish general acceleration?

The Stage B source supports bounded controlled-reduction evidence. It explicitly excludes general acceleration.

Derived from BDAS Stage B — Controlled Reduction Evidence. No new experiment or validation is claimed.

Claim boundaries
  • general acceleration
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

Derived claim boundary

Stage F/G: Selectivity boundary

Question: Does Stage F/G safety establish selective-execution qualification?

The Stage F/G source preserves a safe but non-selective outcome. Selective-execution qualification is explicitly not demonstrated.

Derived from BDAS Stage F/G — Safe But Not Selective. No new experiment or validation is claimed.

Claim boundaries
  • selective execution qualification
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External advisory review

Starlette: Include multipart text fields in resource review

Question: Do file-upload limits alone cover the Starlette multipart denial-of-service advisory?

Starlette's CVE-2024-47874 advisory concerns multipart parts without a filename, which are buffered as text fields. File-upload controls alone therefore do not address the described path. The maintainer also warns that concurrent requests can cause disruption despite reverse-proxy request limits. Review form parsing, text-field limits and concurrency. The maintainer's affected field says below 0.39.2, while the frozen record extends to the shared fix boundary 0.40.0. That discrepancy remains unresolved here; neither record measures a buyer's available capacity or resistance to denial of service.

Source: Starlette maintainer advisory: CVE-2024-47874. Documentation checked 2026-10-11; no deployment validation is claimed.

Frozen advisory sources (1)

Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets.

Claim boundaries
  • upload-file controls assumed to cover text fields
  • proxy limits treated as proven denial-of-service protection
  • source range discrepancy resolved or buyer capacity measured

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Step functions callback principal account

Question: Can a principal in another AWS account directly return a Step Functions task token?

The integration guide requires task tokens to be returned by principals in the same AWS account; tokens sent from principals in a different account do not work. Returning a token is a technical callback mechanism, not proof that a reviewer had business authority or that the referenced action matches an approval.

Source: Amazon Web Services: Step Functions service integration patterns. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a principal in another AWS account directly return a Step Functions task token?

Buyer evidence still required

  • state-machine account
  • callback principal identity and account
  • token lifecycle
  • approval-to-action evidence

Review inference: A cross-account review service is chosen to approve a workflow directly. The callback can fail despite an external approval decision. Adds the callback identity/account constraint and distinguishes it from approval authority. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not interpret token possession as business approval or disclose tokens in audit records.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. principals within the same AWS account

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not interpret token possession as business approval or disclose tokens in audit records.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Step Functions redrive: Original execution identity

Question: Does redriving a failed workflow use the newly deployed fix?

Eligible Standard Workflow redrives retain the original execution identity, input and state-machine definition. Successful steps are generally preserved while failed work resumes according to state-specific rules. Updating an alias does not make a redrive use its new version; redrive and starting a new execution are different decisions.

Source: Step Functions execution redrive. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Redrive automatically picks up the latest workflow deployment.

Buyer evidence still required

  • Original execution version and input.
  • Failure state and state-specific redrive behaviour.
  • External side-effect and reconciliation evidence.

Suggested review condition: Check the original definition and prior side effects before approving recovery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workflow type, original version, execution history, eligibility and external effects.

Optional saved evidence: Save the recovery decision basis without implying that retrying applies a new software fix.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Step functions start idempotency state

Question: When can a Step Functions StartExecution retry return the original execution?

For Standard workflows, the same name and input return the original response only while the execution is running. A closed execution or different input returns ExecutionAlreadyExists; names can be reused 90 days after closure. Express StartExecution is not idempotent. Retrying safely requires the workflow type, identity, input and current execution state.

Source: Amazon Web Services: Step Functions StartExecution API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: When can a Step Functions StartExecution retry return the original execution?

Buyer evidence still required

  • workflow type
  • execution name
  • exact input
  • execution state and closure date

Review inference: A client retries after losing the start response. A new Express execution or changed identity can repeat external work. Adds the concrete start-request identity and running-versus-closed boundary to general workflow execution semantics. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: A successful start response does not establish completion of downstream effects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. StartExecution is idempotent

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • A successful start response does not establish completion of downstream effects.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Step functions start version binding

Question: Does starting an unqualified state machine ARN execute the previously reviewed version?

An unqualified ARN starts the latest revision and is not associated with a version, even if a version contains that same revision. A version ARN selects that version; an alias ARN selects through the alias. Approval evidence must bind the invoked ARN and execution version rather than assume that a previously reviewed definition was used.

Source: Amazon Web Services: Step Functions StartExecution API. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does starting an unqualified state machine ARN execute the previously reviewed version?

Buyer evidence still required

  • approved definition or version
  • invoked ARN
  • alias configuration at execution
  • execution metadata

Review inference: A workflow is edited between review and a new unqualified start. The executed revision can differ from the approved one. Covers a new execution's version binding, whereas the existing record covers redrive preserving the original definition. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Documentation does not independently establish the buyer's approval or actual deployed definition.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. stateMachineArn

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Documentation does not independently establish the buyer's approval or actual deployed definition.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Step functions sync cancellation best effort

Question: Does stopping a Step Functions workflow guarantee its synchronous service job stopped?

Cancellation of an aborted .sync integration is best effort. Missing execution-role permissions or a temporary service outage can prevent cancellation, including after the workflow stops or another parallel branch fails. The integrated job may continue and incur charges; reconcile its own status before treating the action as stopped.

Source: Amazon Web Services: Step Functions service integration patterns. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does stopping a Step Functions workflow guarantee its synchronous service job stopped?

Buyer evidence still required

  • execution status
  • integration type
  • service job identifier
  • cancellation permission
  • downstream job status

Review inference: An operator stops a purchase-processing workflow and assumes all jobs stopped. Downstream work or cost can continue after the parent stops. Adds AWS .sync cancellation failure modes and service-job reconciliation rather than Temporal cooperative heartbeats. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Workflow termination does not prove downstream termination or undo completed effects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. best-effort attempt to cancel

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Workflow termination does not prove downstream termination or undo completed effects.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Step functions sync early callback boundary

Question: Can a Step Functions .sync task finish before its service job completes?

A job can return a task token through SendTaskSuccess or SendTaskFailure before it fully completes. Step Functions uses that response to finish the task, stops monitoring the job and continues the workflow. A task-completion event on this path is therefore not evidence that the service job itself reached completion.

Source: Amazon Web Services: Step Functions service integration patterns. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Step Functions .sync task finish before its service job completes?

Buyer evidence still required

  • task integration and token use
  • callback response
  • service job ID
  • downstream completion evidence

Review inference: An audit treats a successful task event as the end of a long-running export. Unfinished work can be incorrectly reported as completed. Adds a specific early-completion mechanism absent from general execution guarantees. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not equate callback success with independently verified job completion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. before the job is fully complete

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not equate callback success with independently verified job completion.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Step Functions: Execution guarantees depend on workflow type

Question: Can every Step Functions workflow be described as exactly-once execution?

AWS distinguishes exactly-once Standard workflow execution, at-least-once asynchronous Express execution and at-most-once synchronous Express execution. Express idempotency is not automatically managed. The selected workflow type is essential context for interpreting repeated or missing runs.

Source: AWS Step Functions: Choosing workflow type. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can every Step Functions workflow be described as exactly-once execution?

Buyer evidence still required

  • State-machine workflow type and invocation mode.
  • Execution names, identifiers and start responses.
  • Task retry and downstream idempotency evidence.

Suggested review condition: Apply the documented guarantee only to its workflow scope; review downstream side effects separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Workflow type, invocation mode, execution identity and task retry design.

Optional saved evidence: Can every Step Functions workflow be described as exactly-once execution?

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Strapi MCP: Admin-token scope and audit coverage

Question: Does Strapi MCP audit logging prove every content read was recorded?

The documentation describes permission checks for tools, fields, locales and individual documents. It separately states that MCP entry actions require the documented version and Enterprise audit entitlement, and content-only reads are not logged. Permission enforcement and activity-record completeness therefore need separate evidence.

Source: Strapi MCP admin permissions and tools. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Built-in Strapi CMS MCP endpoint

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Strapi provides the endpoint; the buyer operates its CMS deployment.

Documented by publisher. Strapi MCP admin permissions and tools

Purpose

Content and supported plugin operations.

Documented by publisher. Strapi MCP admin permissions and tools

Read capability

Permitted content fields and locales.

Documented by publisher. Strapi MCP admin permissions and tools

Write capability

Permitted content changes and publication; plugins can add tools.

Documented by publisher. Strapi MCP admin permissions and tools

Authentication

Admin token, independently checked on requests.

Documented by publisher. Strapi MCP admin permissions and tools

Permission surface

Tool/schema filtering plus runtime document checks.

Documented by publisher. Strapi MCP admin permissions and tools

Data leaving the environment

Allowed CMS content can enter the client context.

Review inference. Strapi MCP admin permissions and tools

Failure modes to consider

Missing tools may reflect schema compatibility rather than absent permissions.

Review inference. Strapi MCP admin permissions and tools

Unknowns and applicability

Buyer entitlement, plugin inventory and actual audit records are unverified.

Not established

Suggested refusal or clarification condition

Do not assert complete read auditing from MCP support.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Audit version/plan conditions, plugin capabilities and schema compatibility.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the separate permission and audit-coverage questions for a CMS procurement review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe API v1: Retry keys, cached failures and expiry

Question: Does reusing a Stripe API v1 idempotency key guarantee that a payment retry is safe indefinitely?

Stripe API v1 retains the first executed response for a key, including a 500 response. Keys may be pruned after at least 24 hours; reuse after pruning starts a new request. Parameter mismatches fail, while validation or concurrent-execution conflicts may leave no cached result. These rules do not establish the payment outcome.

Source: Idempotent requests. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does reusing a Stripe API v1 idempotency key guarantee that a payment retry is safe indefinitely?

Buyer evidence still required

  • API version, operation and original request identity
  • Key age, parameter equality and retained response
  • Provider object state and application retry history

Review inference: A retry decision needs both operation identity and provider-state reconciliation.

Suggested review condition: Do not infer non-payment from a 500 or replay an expired key without reconciling the original operation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual key retention, payment state and application duplicate protection are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid a second charge when recovering an ambiguous API request.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Indefinite deduplication, API v2 equivalence or proof of payment settlement
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe billing-credit applicability

Question: Does a Stripe billing-credit balance pay every type of subscription charge?

Stripe billing credits apply to eligible subscription items linked to meter prices. They are applied after discounts and before taxes and invoice credit balance. Legacy usage-record prices and non-metered charges are outside the documented supported scope. Match credit applicability and eligible invoice lines rather than treating a balance as universal payment coverage.

Source: Stripe: Billing credits. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Stripe billing-credit balance pay every type of subscription charge?

Buyer evidence still required

  • Credit grant applicability and availability
  • Meter-price and subscription-item bindings
  • Invoice lines, discounts, tax and other credit balances

Review inference: Review stripe billing-credit applicability before accepting the buyer claim. Billing-credit eligibility differs from credit-note refund allocation and ordinary invoice credit balances. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: An available credit grant does not establish coverage of every line, tax or outstanding balance.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Apply credit grants; Credit grant eligibility

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • An available credit grant does not establish coverage of every line, tax or outstanding balance.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe charge capability versus payout capability

Question: Does charges_enabled on a Stripe connected account establish that it can also receive payouts?

Stripe exposes separate charges_enabled and payouts_enabled fields. The first states whether the account can process charges; the second states whether funds in the account can be paid out. One flag does not replace the other, nor does either flag identify a completed payout to a particular bank account.

Source: The Account object. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does charges_enabled on a Stripe connected account establish that it can also receive payouts?

Buyer evidence still required

  • Current connected-account identity and capability fields
  • Applicable requirements and account restrictions
  • Transfer or payout outcome for the intended transaction

Review inference: Check both relevant capabilities and the actual transfer or payout outcome before accepting a supplier payment path.

Suggested review condition: Do not infer payout eligibility or bank receipt from charges_enabled alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Current onboarding restrictions, later capability changes and actual payout completion are account-specific.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid promising supplier funds based on the wrong account capability.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A capability flag as payment execution or settlement evidence
  • Current onboarding restrictions, later capability changes and actual payout completion are account-specific.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe Checkout line-item completeness

Question: Does expanding line_items on a Stripe Checkout Session necessarily return every purchased item?

Stripe describes the includable session line_items property as containing the first handful of items. The dedicated session line-items endpoint returns the full list through pagination. A session expansion alone is therefore not evidence that every purchased product and quantity has been enumerated.

Source: Retrieve a Checkout Session's line items. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does expanding line_items on a Stripe Checkout Session necessarily return every purchased item?

Buyer evidence still required

  • Verified Checkout Session ID
  • All line-item pages and terminal pagination state
  • Price-to-product mapping and per-item quantities

Review inference: Complete pagination before binding the verified purchase to all required entitlements.

Suggested review condition: Do not declare complete delivery while additional line-item pages remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual item count, requested expansion and pagination completeness require the buyer response sequence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid omitting paid items from multi-product delivery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A partial expanded list as proof of complete purchase coverage
  • The actual item count, requested expansion and pagination completeness require the buyer response sequence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe Checkout recovery creates a new session

Question: Does recovering an expired Stripe Checkout Session resume the same provider session identity?

An expired Checkout Session cannot be completed. With recovery enabled, opening its recovery URL creates a new copied Checkout Session. The recovered_from field identifies the original expired session. Recovery therefore creates a new attempt that can be correlated with the abandoned one; it does not turn the expired session itself into a completed payment.

Source: Expire a Checkout Session. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does recovering an expired Stripe Checkout Session resume the same provider session identity?

Buyer evidence still required

  • Original and recovered session IDs with recovered_from
  • Recovery expiry and verified current payment status
  • Order-level deduplication and fulfillment history

Review inference: Preserve both session identities and reconcile the later payment and delivery against the recovered attempt.

Suggested review condition: Do not fulfil or retry solely from an expired session or recovery link without the new session outcome.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the buyer completed another session or already received delivery requires merchant-side evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Recover abandoned purchases without losing attempt identity or duplicating delivery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A recovery URL as proof of payment or unique fulfillment
  • Whether the buyer completed another session or already received delivery requires merchant-side evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe Checkout: Session completion and delayed payment outcomes

Question: Does a completed Stripe Checkout session prove successful payment for an asynchronous payment method?

Stripe's fulfillment guide directs integrations to retrieve the Checkout Session and inspect payment_status. Delayed payment methods can remain processing after checkout; checkout.session.async_payment_succeeded and checkout.session.async_payment_failed report later outcomes. The guide also requires the application to record fulfillment separately and handle repeated fulfillment calls safely.

Source: Fulfill orders | Stripe Documentation. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a completed Stripe Checkout session prove successful payment for an asynchronous payment method?

Buyer evidence still required

  • Server-retrieved session ID, payment status and underlying payment reference.
  • Authenticated later success or failure events for the same session.
  • Idempotent fulfillment record and current entitlement or delivery state.

Review inference: Session completion is insufficient to infer paid entitlement; payment success still does not establish delivery or irreversible settlement.

Suggested review condition: Refuse paid-and-delivered conclusions from checkout.session.completed alone for delayed methods.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer checkout, payment, dispute or fulfillment was inspected.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck accepted payment methods, status/event semantics and fulfillment policy.

Optional saved evidence: Reconcile spending authority or transaction state before approving financial reliance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Irreversible settlement, chargeback immunity or observed delivery
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe collection pause and retained draft invoices

Question: Does resuming Stripe payment collection automatically settle invoices created during the pause?

Pausing collection leaves subscription status unchanged and can retain invoices as drafts, mark them uncollectible or void them. When invoices were kept as drafts, resuming subscription collection does not itself settle those invoices: Stripe instructs merchants to enable auto_advance on each retained draft to collect later. A resumed collection setting is not a payment receipt.

Source: Pause payment collection. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does resuming Stripe payment collection automatically settle invoices created during the pause?

Buyer evidence still required

  • Pause behavior and resume timestamp
  • Retained invoice IDs, states and auto_advance settings
  • Payment attempts and merchant entitlement policy

Review inference: Inventory invoices created during the pause and reconcile each chosen disposition and subsequent payment outcome.

Suggested review condition: Do not mark retained drafts paid or confuse collection pause with the paused subscription status.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Which invoices exist and whether collection later succeeds require account-specific evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Recover missed billing without inventing payment completion or duplicate invoices.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Resumption as automatic payment or restoration of a particular entitlement
  • Which invoices exist and whether collection later succeeds require account-specific evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe Connect charge model and dispute liability

Question: Does Stripe on_behalf_of move dispute debits to a connected account for every charge model?

Stripe separates direct charges from charges created on a platform. Direct-charge disputes debit the connected account for the disputed amount, while destination charges and separate charges and transfers debit the platform balance, with or without on_behalf_of. The parameter can make the connected account the business of record, but it does not erase charge-model-specific debit rules.

Source: Understand how charges work in a Connect integration. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does Stripe on_behalf_of move dispute debits to a connected account for every charge model?

Buyer evidence still required

  • Charge account, charge model and on_behalf_of setting
  • Connected-account fee and liability configuration
  • Dispute and balance-transaction records

Review inference: Identify the actual charge model, account context and fee configuration before assigning financial responsibility.

Suggested review condition: Do not assign all dispute liability from a merchant label or on_behalf_of alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Contractual responsibility and account-specific arrangements require separate evidence; this review describes documented provider debits.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a procurement agent from attributing dispute risk to the wrong account.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A legal merchant-of-record or liability determination
  • Contractual responsibility and account-specific arrangements require separate evidence; this review describes documented provider debits.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe Connect: Refunds and separate transfer recovery

Question: Does refunding a Stripe separate charge automatically recover money transferred to connected accounts?

With Stripe separate charges and transfers, refunding the charge does not reverse its associated transfers. The platform must reconcile recovery separately, for example through transfer reversals or adjusted later transfers. Reversals have balance or reserve requirements and may fail. A customer refund and recovery from recipients are different outcomes.

Source: Create separate charges and transfers. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does refunding a Stripe separate charge automatically recover money transferred to connected accounts?

Buyer evidence still required

  • Charge, refund and linked transfer identities
  • Reversal outcomes and recipient available balances or reserves
  • Amounts already recovered through later transfer adjustments

Review inference: Recovery accounting needs independent evidence for both the refund and each recipient leg.

Suggested review condition: Do not mark platform recovery complete solely from the refund or a reversal request.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Recipient balances, reversals and actual recovery are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent unreconciled platform losses after marketplace refunds.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic transfer recovery or applicability to every Connect charge model
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe credit notes and billing-credit restoration

Question: Does issuing a Stripe credit note restore billing-credit grants previously consumed by an invoice?

Stripe documents different outcomes for voiding an invoice and issuing a credit note. Voiding reinstates applied grant balance, but already expired credits expire again immediately. A credit note does not refund the applied grant; restoring those billing credits requires a new grant. Reconcile the actual grant ledger and correction type.

Source: Stripe: Billing credits. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does issuing a Stripe credit note restore billing-credit grants previously consumed by an invoice?

Buyer evidence still required

  • Invoice correction type and identifier
  • Applied credit-grant ledger
  • Grant expiry and restored or replacement balance

Review inference: Review stripe credit notes and billing-credit restoration before accepting the buyer claim. Restoration of metered billing-credit grants is distinct from allocating an invoice credit note to cash or customer balance. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not equate an invoice correction or credit note with restored spendable billing credits or a cash refund.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Void invoices and issue credit notes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not equate an invoice correction or credit note with restored spendable billing credits or a cash refund.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe credit notes and refund destination

Question: Does issuing a Stripe credit note guarantee a refund to the original payment method?

A credit note reduces an open or paid invoice. For a paid invoice, Stripe supports allocation to a payment-method refund, customer credit balance or an out-of-band refund. Invoices funded partly by customer balance can return excess credit to that balance. The credit-note total therefore does not identify one refund destination or prove bank receipt.

Source: Issue credit notes. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does issuing a Stripe credit note guarantee a refund to the original payment method?

Buyer evidence still required

  • Credit note and original invoice funding breakdown
  • Refund, credit-balance and out-of-band allocations
  • Current refund outcome or external repayment evidence

Review inference: Reconcile the credit note allocation with each linked refund, credit ledger or external repayment record.

Suggested review condition: Do not tell a buyer their original payment method was refunded from a credit-note amount alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Provider refund completion and external reimbursement are separate observations.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Explain and reconcile reimbursement without confusing credit issuance with completed repayment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Credit-note issuance as proof of bank receipt
  • Provider refund completion and external reimbursement are separate observations.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe delivery evidence: Verified events and duplicate handling

Question: Does receiving a Stripe webhook prove that payment was verified and fulfilled exactly once?

Stripe documents signature verification, possible duplicate deliveries and no guaranteed event ordering. Receiving a webhook or returning a successful response does not by itself prove a matching payment entitlement or completed fulfilment. Review authenticity, object state and the application processing record separately.

Source: Stripe event delivery and verification boundaries. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: One successful webhook delivery proves a valid payment and exactly-once fulfilment.

Buyer evidence still required

  • Evidence that the handler verifies authentic events in the intended mode
  • The matching payment or subscription state from the provider
  • An idempotent processing and fulfilment record covering retries and duplicates

Suggested review condition: Refuse payment reliance on caller-supplied status or an unverified event; seek provider-bound payment evidence before delivery.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck endpoint secrets, event versions, retry behavior and fulfilment idempotency.

Optional saved evidence: Retain the delivery-versus-entitlement distinction behind a payment-integration review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe destination refunds and application fees

Question: Does refunding a Stripe destination charge automatically refund the platform application fee?

For a destination charge, Stripe says the platform keeps the application fee by default when refunding the charge. refund_application_fee can return it, and that path also requires reversing the transfer. A full refund returns the full fee on that path; a partial refund returns a proportional fee. Customer refund, transfer reversal and application-fee refund are distinct records.

Source: Create destination charges. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does refunding a Stripe destination charge automatically refund the platform application fee?

Buyer evidence still required

  • Charge refund amount and refund_application_fee setting
  • Transfer reversal outcome
  • Application fee and fee-refund records

Review inference: Reconcile all three allocations before declaring that the platform and recipient balances were restored.

Suggested review condition: Do not infer that the platform fee was returned from the customer refund alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The chosen flags, separate fee refunds and completed money movements require account evidence.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid refund reconciliation gaps between buyer, platform and supplier.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Refunding a charge automatically restoring every participant balance
  • The chosen flags, separate fee refunds and completed money movements require account evidence.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe disputes after licensed delivery

Question: Does successful software delivery make a Stripe card payment immune to a later dispute debit?

Stripe documents that a formal card dispute causes the card network to debit Stripe and Stripe to debit the merchant balance for the disputed amount and a dispute fee. The dispute process can subsequently return funds or uphold the cardholder outcome. An application delivery record does not disable that provider process or prove irreversible funds.

Source: How disputes work. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does successful software delivery make a Stripe card payment immune to a later dispute debit?

Buyer evidence still required

  • Original payment and immutable delivery records
  • Dispute state and related balance transactions
  • Applicable existing licence and dispute-handling policy

Review inference: Keep purchase, delivery and later dispute outcomes linked while applying the existing licence and dispute policies separately.

Suggested review condition: Do not describe an entitlement delivery as proof of irreversible payment or automatically change licence rights from this review.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The dispute merits, issuer decision and contractual rights are not determined here.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Preserve auditable payment-to-delivery history when later financial reversals occur.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Predicting dispute outcomes or providing legal entitlement advice
  • The dispute merits, issuer decision and contractual rights are not determined here.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe entitlement recovery after webhook loss

Question: Can a provisioning service recover a Stripe customer feature inventory without replaying every missed webhook?

Stripe documents listing current active entitlements by customer for startup and reconciliation after webhook delivery failure. The response is paginated and uses feature lookup keys. This supports reconstructing the current declared feature inventory; it does not prove that the application applied it or that earlier access was correct.

Source: Stripe Billing Entitlements (API). Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a provisioning service recover a Stripe customer feature inventory without replaying every missed webhook?

Buyer evidence still required

  • Exact customer-to-user binding
  • All pages of current active entitlements
  • Local provisioning and removal outcomes

Review inference: Review stripe entitlement recovery after webhook loss before accepting the buyer claim. Recovers a provider feature inventory after missed events; existing webhook evidence only distinguishes delivery from fulfilment. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse historical-access or successful-provisioning claims from a current entitlement list alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Retrieve the list of all active entitlements for a customer

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse historical-access or successful-provisioning claims from a current entitlement list alone.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe entitlement-summary completeness

Question: Can a Stripe entitlement webhook establish that a customer has only the features listed in its data array?

Stripe limits the active-entitlement summary data array to ten entitlements. For larger inventories, its documented URL leads to the complete paginated list. Absence from the inline array alone is insufficient evidence for removing access; reconcile the full inventory for the exact customer.

Source: Stripe Billing Entitlements (API). Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a Stripe entitlement webhook establish that a customer has only the features listed in its data array?

Buyer evidence still required

  • Customer identifier
  • Summary event and entitlement URL
  • Complete paginated active-entitlement responses

Review inference: Review stripe entitlement-summary completeness before accepting the buyer claim. The specific ten-feature truncation and complete-inventory decision are not established by generic webhook delivery evidence. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse complete-inventory or revocation conclusions from a truncated summary.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Listen for webhooks to grant or revoke access

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse complete-inventory or revocation conclusions from a truncated summary.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe event account-context reconciliation

Question: Can a Stripe event be reconciled against an arbitrary account when it originated from a connected account or organisation context?

The Event account field identifies the originating connected account, while context supplies authentication context for relevant event/object retrieval. Stripe’s organisation guidance requires the corresponding Stripe-Context when fetching manually; documented SDK fetch helpers apply that context automatically. Event identity does not remove account scoping.

Source: The Event object. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a Stripe event be reconciled against an arbitrary account when it originated from a connected account or organisation context?

Buyer evidence still required

  • Verified Event and account/context fields
  • Retrieval account and API context
  • Expected merchant and product mapping

Review inference: Bind retrieval and business effects to the verified event’s account context and intended merchant.

Suggested review condition: Refuse cross-account reconciliation when the originating context cannot be verified.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s account mappings and authorisation are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid applying payment evidence to the wrong account or merchant.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Permission to access another account from possession of an event identifier
  • The buyer’s account mappings and authorisation are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe event and retry timestamps

Question: Does a new Stripe webhook signature timestamp mean the business event was created again?

Stripe’s Event created field records object creation time. A retry delivery receives a new signature and signature timestamp. These observations refer to different stages: the Event’s creation and a particular delivery attempt. Neither timestamp alone establishes causal order across concurrent business actions.

Source: The Event object. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a new Stripe webhook signature timestamp mean the business event was created again?

Buyer evidence still required

  • Event ID and created value
  • Verified delivery timestamp and attempt history
  • Business-object state and outcome evidence

Review inference: Preserve both event identity/time and delivery-attempt evidence during replay reconciliation.

Suggested review condition: Do not interpret a fresh delivery signature as a newly created business event.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Exact business execution time and cross-system clock alignment remain unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep delayed and replayed payment evidence in the correct chronology.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed event ordering from delivery time
  • Exact business execution time and cross-system clock alignment remain unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe event identity and duplicate processing

Question: Can different Stripe Event IDs still represent duplicate processing of the same underlying effect?

Stripe distinguishes repeated delivery of one Event from cases where two separate Event objects are generated. Its webhook guidance recommends using the underlying object ID together with event type to identify the latter. Application idempotency must still respect legitimate later transitions; different Event IDs alone do not prove distinct business effects.

Source: Manage webhook endpoints. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can different Stripe Event IDs still represent duplicate processing of the same underlying effect?

Buyer evidence still required

  • Event IDs, object IDs and types
  • Transition state and business idempotency policy
  • Existing fulfilment or reconciliation record

Review inference: Reconcile event identity with object, type and the intended state transition before issuing an effect twice.

Suggested review condition: Do not issue duplicate effects merely because Event IDs differ.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether two buyer events are duplicate effects or legitimate updates is unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent duplicate commercial actions without suppressing valid later updates.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A universal deduplication key for every object update
  • Whether two buyer events are duplicate effects or legitimate updates is unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe Event retrieval retention boundary

Question: Can the Stripe v1 Event retrieval API reconstruct events older than its documented retrieval window?

The reviewed v1 Retrieve Event reference makes events available for retrieval only for thirty days. That endpoint is not a permanent audit archive. Failure to retrieve an older Event cannot by itself establish that the underlying payment never occurred.

Source: Retrieve an event. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can the Stripe v1 Event retrieval API reconstruct events older than its documented retrieval window?

Buyer evidence still required

  • Event creation date and API retrieval result
  • Retained event archive and integrity evidence
  • Relevant business-object and accounting records

Review inference: Preserve required evidence within the retrieval window and reconcile older activity from separately retained records.

Suggested review condition: Decline complete historical reconstruction from an endpoint outside its documented window.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s retained records and older payment history are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent irrecoverable gaps in retrospective payment investigations.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Deletion of all Stripe business records after thirty days
  • The buyer’s retained records and older payment history are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe feature changes and existing subscriptions

Question: Does attaching a Stripe feature to a product immediately entitle existing subscribers?

Stripe documents that product feature changes create active entitlements for existing subscriptions at the next billing-period start. A changed product definition therefore does not establish that every existing customer already has the feature. Compare the subscription period, feature mapping and current customer entitlement inventory before provisioning.

Source: Stripe Billing Entitlements (API). Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does attaching a Stripe feature to a product immediately entitle existing subscribers?

Buyer evidence still required

  • Subscription and billing-period identifiers
  • Product-feature mapping and change time
  • Customer active-entitlement inventory

Review inference: Review stripe feature changes and existing subscriptions before accepting the buyer claim. Feature propagation timing is distinct from subscription payment status. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not infer immediate access for existing subscribers from a product-feature attachment alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Add your features to products

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer immediate access for existing subscribers from a product-feature attachment alone.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe gross, fee and net payment evidence

Question: Is a Stripe balance transaction amount the net proceeds of the underlying payment?

Stripe defines amount as the gross transaction amount, fee as assessed fees and net as the net impact on the balance. The balance transaction has its own currency and can include an exchange rate when conversion occurs. available_on describes when net funds become available. Gross payment, balance impact and bank payout are therefore different observations.

Source: The Balance Transaction object. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Is a Stripe balance transaction amount the net proceeds of the underlying payment?

Buyer evidence still required

  • Balance transaction amount, fee, net and currency
  • Underlying payment and any exchange rate
  • Availability date and separately linked payout evidence

Review inference: Reconcile gross, fees, currency conversion and availability before comparing sales totals with supplier proceeds.

Suggested review condition: Do not report gross amount as net proceeds or available balance as bank receipt.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Other account movements and the bank-side receipt are not established by this transaction definition.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Make transaction reconciliation useful without overstating revenue or settlement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Net balance amount as recognised revenue, profit or settled bank funds
  • Other account movements and the bank-side receipt are not established by this transaction definition.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe historical Event schema binding

Question: Does retrieving an old Stripe Event with a newer API version upgrade its stored data schema?

Stripe documents that an Event’s data is rendered using its api_version when created and remains unchanged. Updating the account version or retrieving an older Event through a newer API version does not retroactively rewrite that stored Event. The parser must respect the recorded version.

Source: The Event object. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does retrieving an old Stripe Event with a newer API version upgrade its stored data schema?

Buyer evidence still required

  • Event api_version and original payload
  • Parser version and supported historical schemas
  • Object state retrieved separately if needed

Review inference: Bind historical interpretation to the Event’s own schema and preserve version-specific decoding.

Suggested review condition: Reject reconstruction that assumes old Event data was upgraded by retrieval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s parser compatibility and historical storage are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid misreading historical payment events after API upgrades.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A guarantee that all event types share one schema
  • The buyer’s parser compatibility and historical storage are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe incremental authorization: Failed increases and original expiry

Question: Does increasing a Stripe authorization renew its deadline or replace the original amount when declined?

For eligible Stripe incremental authorizations, success updates the authorized amount. If an increment is declined, the earlier authorized amount remains capturable and proposed field updates are not saved. Incrementing does not extend the original authorization validity period. Eligibility, the increment result and subsequent capture must be checked separately.

Source: Increment an authorization. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does increasing a Stripe authorization renew its deadline or replace the original amount when declined?

Buyer evidence still required

  • Original authorization and capture deadline
  • Increment response and current capturable amount
  • Eligibility and buyer-approved spending ceiling

Review inference: An attempted increase cannot establish either a higher spending allowance or fresh capture time.

Suggested review condition: Do not release a higher-value order without a successful eligible increment and current capture evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer approval, issuer acceptance and final captured amount are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Control increased-order exposure without mistaking an attempted increment for approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic renewal of a hold or authorization of additional buyer spending
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe invoice credits and new-money evidence

Question: Does a Stripe invoice marked paid after balance adjustments prove new money was received?

Stripe customer invoice balances are a ledger of credit and debit adjustments that can apply to later invoices. Credit reduces the amount due; very small amounts can be moved to the invoice balance while the invoice is marked paid. These documented balance movements do not themselves establish a new cash payment for that invoice.

Source: Customer invoice balance. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Stripe invoice marked paid after balance adjustments prove new money was received?

Buyer evidence still required

  • Invoice amounts and final status
  • Linked customer-balance transactions and adjustment types
  • New payment or external collection evidence

Review inference: Separate invoice balance application and carried debt from independently verified payment collection.

Suggested review condition: Do not count a paid or zero-due invoice as new revenue without reconciling the funding source.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The historical source of a credit and whether money was collected elsewhere are not proven by an invoice flag.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent credits or carried balances from being counted as new licence sales.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Every credit balance representing deposited customer cash
  • The historical source of a credit and whether money was collected elsewhere are not proven by an invoice flag.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe invoices: Out-of-band payment is not a Stripe charge

Question: Does a Stripe invoice marked paid prove that Stripe collected the money?

The Stripe invoice payment API accepts paid_out_of_band to record payment outside Stripe; this option makes no charge. Consequently, a paid invoice alone cannot identify the collection channel or establish a provider-processed payment. Reconcile the invoice with the relevant Stripe payment or separately supported external receipt.

Source: Pay an invoice. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Stripe invoice marked paid prove that Stripe collected the money?

Buyer evidence still required

  • Invoice identity and payment operation parameters
  • Linked provider payment or external collection record
  • Reconciled amount, currency and beneficiary

Review inference: A bookkeeping status needs a collection record before it supports a paid-delivery decision.

Suggested review condition: Refuse a Stripe-collected finding when only a paid invoice or an unverified external receipt is available.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

External receipt authenticity and actual receipt of funds are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid supplying a licensed deliverable against unsupported collection evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proof that Stripe charged a payment method or verified an external receipt
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe Issuing budget aggregation and overshoot

Question: Is an Issuing spending limit a strict instantaneous maximum for an agent budget?

Stripe documents best-effort spend aggregation with a possible delay, and later tips or fees that can exceed a limit.

Source: Stripe: Issuing spending controls. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Is an Issuing spending limit a strict instantaneous maximum for an agent budget?

Buyer evidence still required

  • Applicable card and cardholder limits
  • Concurrent authorizations
  • Captures and later adjustments

Review inference: Review stripe issuing budget aggregation and overshoot before accepting the buyer claim. The generic budget boundary does not identify Issuing aggregation delay and later adjustments; this review supplies the provider-specific exception evidence. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not claim a hard real-time cap from these controls. Reconcile delayed and adjusted amounts against the separate spending mandate.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Spending limits

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim a hard real-time cap from these controls. Reconcile delayed and adjusted amounts against the separate spending mandate.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing capture after card restrictions change

Question: Does deactivating an Issuing card block capture of an already approved authorization?

The captured documentation excludes capture from current card-status, spending-control and real-time authorization checks.

Source: Stripe: Issuing transactions. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does deactivating an Issuing card block capture of an already approved authorization?

Buyer evidence still required

  • Original authorization
  • Card-control change time
  • Capture transactions

Review inference: Review stripe issuing capture after card restrictions change before accepting the buyer claim. Merchant-side capture expiry does not establish issuer-card control behavior; this review checks the effect of later issuer restrictions on prior authority. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not infer cancellation of earlier authorized exposure from a later card restriction. Obtain capture and recovery evidence separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Issuing transactions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer cancellation of earlier authorized exposure from a later card restriction. Obtain capture and recovery evidence separately.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing category limits and permitted merchants

Question: Does an Issuing spending limit for one merchant category block every other category?

A category-scoped limit applies only to its categories. Category restrictions use the separate allowed or blocked category controls.

Source: Stripe: Issuing spending controls. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an Issuing spending limit for one merchant category block every other category?

Buyer evidence still required

  • Category-specific limits
  • Allowed and blocked category configuration
  • Proposed merchant category

Review inference: Review stripe issuing category limits and permitted merchants before accepting the buyer claim. This is a scope-composition decision: spending amount rules and merchant restrictions have different documented meanings. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not treat a scoped amount rule as an exclusive merchant allowlist. Compare both rule types with the purchasing mandate.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Spending limits

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat a scoped amount rule as an exclusive merchant allowlist. Compare both rule types with the purchasing mandate.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing declines before the agent callback

Question: Does no Issuing authorization-request callback mean no purchase was attempted?

Spending controls run before the synchronous callback and can decline a request before it is sent, producing a declined authorization-created event.

Source: Stripe: Issuing spending controls. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does no Issuing authorization-request callback mean no purchase was attempted?

Buyer evidence still required

  • Authorization-created outcomes
  • Configured controls
  • Callback event coverage

Review inference: Review stripe issuing declines before the agent callback before accepting the buyer claim. This is an event-population boundary before the callback, distinct from loss or retry of a webhook that was already emitted. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not infer no attempted purchase from the callback stream alone. Review pre-callback outcomes and collection completeness.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Issuing spending controls

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer no attempted purchase from the callback stream alone. Review pre-callback outcomes and collection completeness.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing fallback decisions and callback health

Question: Does approved=true prove the agent authorization callback successfully decided the purchase?

On a missing or invalid response, configured fallback can decide the authorization. Stripe directs users to request-history error reasons when assessing callback health.

Source: Stripe: Real-time authorizations. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does approved=true prove the agent authorization callback successfully decided the purchase?

Buyer evidence still required

  • Authorization request history
  • Callback result and timing
  • Applicable timeout or Autopilot configuration

Review inference: Review stripe issuing fallback decisions and callback health before accepting the buyer claim. The prior asynchronous webhook receipt boundary does not describe synchronous Issuing fallback decisions or their attribution to an agent. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not attribute a fallback decision to the agent policy. Confirm feature availability: Autopilot behavior is documented as public preview.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Monitor your webhook responses;Autopilot

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not attribute a fallback decision to the agent policy. Confirm feature availability: Autopilot behavior is documented as public preview.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing force capture and missing authorization

Question: Does absence of an approved Issuing authorization prove no capture can occur?

Stripe documents captures following a decline or without an authorization; a transaction can therefore lack an authorization link.

Source: Stripe: Issuing transactions. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does absence of an approved Issuing authorization prove no capture can occur?

Buyer evidence still required

  • Capture transaction
  • Available authorization history
  • Independent purchase mandate and dispute evidence

Review inference: Review stripe issuing force capture and missing authorization before accepting the buyer claim. This covers issuer-side forced capture without approved authorization, not the merchant PaymentIntent capture window. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not infer either spending authority or absence of debit from the authorization population alone. Investigate unmatched captures.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Force capture

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer either spending authority or absence of debit from the authorization population alone. Investigate unmatched captures.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing partial and multiple capture accounting

Question: Can one Issuing authorization be reconciled using only one capture transaction?

Merchants can partially or repeatedly capture an authorization. The held amount depends on the authorization and all linked captures.

Source: Stripe: Issuing transactions. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can one Issuing authorization be reconciled using only one capture transaction?

Buyer evidence still required

  • Authorization amount and status
  • Complete linked capture set
  • Currency and hold evidence

Review inference: Review stripe issuing partial and multiple capture accounting before accepting the buyer claim. The existing expiry review does not define reconciliation across multiple issuer captures and the remaining authorized hold. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Reconcile all captures before declaring the purchase complete or the remaining hold zero. Repeated capture records are not inherently duplicate execution.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Partial capture;Multi capture

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Reconcile all captures before declaring the purchase complete or the remaining hold zero. Repeated capture records are not inherently duplicate execution.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing pending amount and decision-time evidence

Question: Should an Issuing decision use the initial top-level amount instead of pending_request.amount?

The request stores the requested amount in pending_request while initial top-level amount is zero. The top-level fields change after the response.

Source: Stripe: Real-time authorizations. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Should an Issuing decision use the initial top-level amount instead of pending_request.amount?

Buyer evidence still required

  • Decision-time event
  • Pending request amount and currency
  • Later authorization state

Review inference: Review stripe issuing pending amount and decision-time evidence before accepting the buyer claim. This identifies which lifecycle-specific amount is available at the spending decision, rather than a general budget policy requirement. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not approve a supposedly zero-cost request from the initial top-level amount, or reconstruct the original request solely from later state.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Authorization requests

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not approve a supposedly zero-cost request from the initial top-level amount, or reconstruct the original request solely from later state.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing refund reversals and amount direction

Question: Does every Issuing transaction with type refund add a credit?

A refund reversal retains type refund but has a negative amount, unlike a standard positive refund.

Source: Stripe: Issuing transactions. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does every Issuing transaction with type refund add a credit?

Buyer evidence still required

  • Transaction type and signed amount
  • Currency
  • Original refund and reversal records

Review inference: Review stripe issuing refund reversals and amount direction before accepting the buyer claim. This adds the Issuing reversal encoding needed to avoid double-counting credits; invoice credit-note categories do not define that sign convention. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Preserve amount direction when reconciling credits. Type alone must not cause a reversal to be counted as another refund.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Refund reversals

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Preserve amount direction when reconciling credits. Type alone must not cause a reversal to be counted as another refund.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe Issuing replacement cards and shared limits

Question: Does replacing an Issuing card reset its spending-limit history?

The documented card limits extend across the replacement chain, while cardholder limits apply across that cardholder's cards.

Source: Stripe: Issuing spending controls. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does replacing an Issuing card reset its spending-limit history?

Buyer evidence still required

  • Replacement-card lineage
  • Card and cardholder limits
  • Spending history across the relevant cards

Review inference: Review stripe issuing replacement cards and shared limits before accepting the buyer claim. This decision concerns identity continuity across replacement cards, not simply whether a configured budget is enforced. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not budget a replacement as an independent fresh allowance without reconciling the documented shared scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Spending limits

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not budget a replacement as an independent fresh allowance without reconciling the documented shared scope.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe late usage and invoice finalization

Question: Will an accepted late Stripe meter event necessarily update a finalized invoice or appear on the next one?

Stripe distinguishes meter-event acceptance from invoice inclusion. Its timestamp window can permit an event after the related invoice finalized, while the event appears in summaries without updating that invoice or entering the next one. Threshold invoices have an earlier receipt cutoff. Match event receipt, service period and invoice lifecycle.

Source: Stripe: Record usage for billing with the API. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Will an accepted late Stripe meter event necessarily update a finalized invoice or appear on the next one?

Buyer evidence still required

  • Event timestamp and receipt time
  • Subscription service period
  • Invoice creation and finalization times
  • Meter summary and invoice lines

Review inference: Review stripe late usage and invoice finalization before accepting the buyer claim. Provider acceptance versus finalization cutoff is distinct from usage-month and invoice-month allocation. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Do not claim a finalized or future invoice includes usage solely because Stripe accepted its timestamp.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Event timestamps

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim a finalized or future invoice includes usage solely because Stripe accepted its timestamp.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe manual capture: Expiry and remaining authorization

Question: Can an agent treat a Stripe card authorization as available funds for any later capture?

Stripe exposes a card authorization deadline through capture_before. An uncaptured authorization that expires releases its funds and becomes canceled. For most payments a partial capture releases the remainder and permits no second capture; eligible multicapture payments are an exception. Authorization is therefore not evidence that the intended amount was captured.

Source: Place a hold on a payment method. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent treat a Stripe card authorization as available funds for any later capture?

Buyer evidence still required

  • PaymentIntent and latest charge identity
  • capture_before, amount_capturable and captured amount
  • Payment-method and multicapture eligibility

Review inference: Fulfillment decisions should bind the intended amount to a completed capture.

Suggested review condition: Refuse a completed-payment finding while capture is pending, expired or not reconciled to the required amount.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Live authorization validity, issuer behavior and capture outcome are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid shipping against an expired or incompletely captured card hold.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed capture availability or settlement from an authorization
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe MCP: Account actions and payment authority

Question: Does connecting Stripe MCP authorize an agent to refund or change a live account?

Stripe documents broad API read and write tools, with OAuth for interactive use and permission-scoped Agent Keys for autonomous access. A connection is not approval for a particular financial action. Check the account, live or sandbox environment, permissions and approval rules. The documentation announces an MCP key-acceptance change on 31 October 2026; this dated review does not test that future behaviour.

Source: Stripe MCP authentication and tools. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Stripe MCP authentication and account operations as documented on the review date; separate from an application's server-side Stripe integration.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Stripe operates the documented MCP service.

Documented by publisher. Stripe MCP authentication and tools; Stripe API key types and restrictions

Purpose

Retrieve Stripe information and perform permitted account/API operations.

Documented by publisher. Stripe MCP authentication and tools; Stripe API key types and restrictions

Read capability

Stripe API GET methods and documentation search, within the authorized account and permissions.

Documented by publisher. Stripe MCP authentication and tools; Stripe API key types and restrictions

Write capability

API mutation tools include refund and subscription operations; their availability is not buyer authorization to execute them.

Documented by publisher. Stripe MCP authentication and tools; Stripe API key types and restrictions

Authentication

OAuth or Agent Keys are documented. The MCP page announces rejection of full-access keys and untagged restricted keys from 31 October 2026.

Documented by publisher. Stripe MCP authentication and tools; Stripe API key types and restrictions

Permission surface

Agent-tagged restricted keys retain scoped permissions and are subject to documented approval rules.

Documented by publisher. Stripe MCP authentication and tools; Stripe API key types and restrictions

Data leaving the environment

Account results return to the AI client. The record does not establish what customer fields that client stores or sends onward.

Review inference. Stripe MCP authentication and tools; Stripe API key types and restrictions

Failure modes to consider

Confusing sandbox and live account; refunding without task approval; relying on a key type after a documented acceptance change.

Review inference. Stripe MCP authentication and tools; Stripe API key types and restrictions

Unknowns and applicability

Actual key grants, selected account/environment, active approval rules and client retention.

Not established

Suggested refusal or clarification condition

Withhold live mutations until exact action, account and environment are authorized; never treat this profile as permission to spend or refund.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the documented 31 October 2026 MCP authentication change before use across that date.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the documented account-action boundaries and dated authentication notice used in a finance-tool review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe meter acceptance and later validation

Question: Does accepting a Stripe meter event prove that its usage was successfully aggregated for billing?

Stripe processes meter events asynchronously. Aggregated summaries and upcoming invoices can lag received events, and processing errors can produce meter error-report or no-meter events. Retain event identity and reconcile processing outcomes before treating an accepted request as a complete billable usage record.

Source: Stripe: Record usage for billing with the API. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does accepting a Stripe meter event prove that its usage was successfully aggregated for billing?

Buyer evidence still required

  • Meter event identifier and payload mapping
  • Meter summaries for the relevant period
  • Processing-error events and invoice state

Review inference: Review stripe meter acceptance and later validation before accepting the buyer claim. Usage-meter ingestion and asynchronous validation are separate from payment webhook delivery. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Neither immediate absence from a summary nor request acceptance proves final aggregation or invoice inclusion.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Record usage for billing with the API; Handle meter event errors; Error codes

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Neither immediate absence from a summary nor request acceptance proves final aggregation or invoice inclusion.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe no-payment-required sessions and cash evidence

Question: Does a Stripe Checkout Session with no_payment_required prove a new cash payment?

Checkout payment_status distinguishes paid, unpaid and no_payment_required. Stripe documents no_payment_required for setup mode or a billing-cycle anchor without proration where collection happens at the anchor date. That state can be relevant to a merchant workflow, but it does not by itself establish a new charge or money received.

Source: The Checkout Session object. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Stripe Checkout Session with no_payment_required prove a new cash payment?

Buyer evidence still required

  • Session mode, payment_status and billing-cycle settings
  • Linked payment or setup object and collection evidence
  • Merchant access policy for setup and deferred payment

Review inference: Separate any permitted setup or deferred-billing access from a claim that the buyer has paid now.

Suggested review condition: Do not record a paid purchase or grant a payment-required entitlement solely from no_payment_required.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The merchant may separately authorise access without a current charge; that policy is not supplied by this review.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent setup or deferred-billing events being misreported as paid licence sales.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic entitlement or settled revenue from a no-payment-required session
  • The merchant may separately authorise access without a current charge; that policy is not supplied by this review.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe payouts: A paid label can precede a later failure

Question: Does a Stripe payout initially marked paid establish irreversible receipt by the destination bank?

Stripe documents payout states including paid, failed and canceled. Some payouts that initially appear paid can later change to failed. Failure information and the associated reversal balance transaction help reconcile the returned funds. A single status observation is insufficient to establish irreversible bank receipt.

Source: The Payout object. Documentation checked 2026-10-22; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Stripe payout initially marked paid establish irreversible receipt by the destination bank?

Buyer evidence still required

  • Payout identity and destination reference
  • Current status, failure code and reversal balance transaction
  • Bank confirmation and observation time

Review inference: A payout assessment needs a timestamp and subsequent failure reconciliation.

Suggested review condition: Do not assert irreversible bank receipt from a paid label without independently supported destination evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Bank receipt and any later status transition are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep supplier-payment and treasury reconciliation from closing prematurely.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Irreversible settlement or proof of recipient bank credit
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe pending updates and payment-dependent plan changes

Question: Do Stripe pending subscription updates always prevent a plan change before successful payment?

Pending updates normally apply changes only after the resulting invoice payment succeeds. Stripe documents an exception when resumption moves a paused subscription to active or past_due: a matching pending update can apply even without successful payment. A populated pending_update can also mean payment is still processing. Applied-update and invoice-payment outcomes require separate checks.

Source: Pending updates. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Do Stripe pending subscription updates always prevent a plan change before successful payment?

Buyer evidence still required

  • Pending update, expiry and resumption context
  • Applied or expired update events and current subscription
  • Resulting invoice and payment outcome

Review inference: Use the actual applied-update event and invoice outcome, including resumption context, before treating a changed plan as paid.

Suggested review condition: Do not infer successful collection solely from an applied update or failure solely from a pending_update field.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer integration, payment-record processing and resumption path are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid enabling a paid plan from an incomplete interpretation of pending-update state.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • An unconditional guarantee that pending updates enforce paid access
  • The buyer integration, payment-record processing and resumption path are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe prorations and unpaid subscription changes

Question: Does a Stripe subscription proration establish that the old or changed plan was actually paid?

Stripe calculates prorations assuming previous invoices will eventually be paid. An unpaid period can consequently produce a credit for unused time. Negative prorations are not automatically refunded and positive prorations are not necessarily immediately billed. A proration amount records a billing adjustment, not proof of collection or refund completion.

Source: Prorations. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Stripe subscription proration establish that the old or changed plan was actually paid?

Buyer evidence still required

  • Old and new subscription terms with proration behavior
  • Underlying unpaid and newly created invoice states
  • Actual collection, credit and refund records

Review inference: Reconcile the underlying invoice and payment outcomes before crediting paid service or accepting a changed plan as funded.

Suggested review condition: Do not treat a proration credit or invoice item as money collected or returned.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual invoice payment and the merchant policy for unpaid plan changes require deployment records.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent credits and access changes from outrunning verified collection.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Proration calculation as payment, refund or entitlement evidence
  • Actual invoice payment and the merchant policy for unpaid plan changes require deployment records.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe raw-body signature verification

Question: Can a parsed and reserialized Stripe webhook body be substituted for the original bytes during signature verification?

Stripe requires the unmodified raw request body for webhook signature verification. Framework parsing or other changes can cause verification to fail. Verification also depends on the correct endpoint signing secret; a CLI listener secret is distinct from the Dashboard endpoint’s secret.

Source: Manage webhook endpoints. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a parsed and reserialized Stripe webhook body be substituted for the original bytes during signature verification?

Buyer evidence still required

  • Raw request bytes and Stripe-Signature header
  • Correct endpoint secret configuration
  • Verification outcome before processing

Review inference: Preserve the original body through verification and bind the secret to the actual endpoint.

Suggested review condition: Refuse processing when authenticity cannot be established over the original body.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s middleware and secret selection are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent middleware changes from invalidating payment-event verification.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Payment completion or fulfilment merely from a valid signature
  • The buyer’s middleware and secret selection are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe refunds: Creation and final outcomes differ

Question: Does creating a Stripe refund establish that the customer received it and the original effects were reversed?

Stripe documents refunds that remain pending when a card refund lacks sufficient available balance, and refunds that later fail when the bank or card issuer cannot process them. Failed refunds return funds to the Stripe balance and expose failure information. Some early refunds appear as reversals of the original charge rather than a separate credit.

Source: Refund and cancel payments | Stripe Documentation. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does creating a Stripe refund establish that the customer received it and the original effects were reversed?

Buyer evidence still required

  • Refund and original payment IDs, amount, currency and current refund status.
  • Later failure or return events and available refund reference information.
  • Separate tax, entitlement, inventory and delivery compensation records.

Review inference: A refund record does not by itself reverse business effects such as delivered goods or granted access.

Suggested review condition: Refuse completed-refund or all-effects-reversed claims based solely on refund creation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Customer receipt and the buyer's compensation state were not observed.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck payment-method-specific pending, failed and reversal behavior and later state changes.

Optional saved evidence: Reconcile spending authority or transaction state before approving financial reliance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed customer receipt, automatic tax correction or reversal of non-payment effects
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe scheduled cancellation and access timing

Question: Does setting Stripe cancel_at_period_end mean the subscription has already ended?

Setting cancel_at_period_end schedules cancellation for the end of the billing period; it can be unset before that point. Stripe distinguishes subscription.updated when the flag changes from subscription.deleted when cancellation occurs. Pending prorations can remain collectible at period end. The scheduling event alone is not the terminal cancellation event.

Source: Cancel subscriptions. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does setting Stripe cancel_at_period_end mean the subscription has already ended?

Buyer evidence still required

  • Subscription cancellation flag and effective period end
  • Updated and deleted event sequence with current state
  • Existing access-expiry and outstanding-invoice policy

Review inference: Apply the existing access policy using the effective cancellation time and final state rather than treating scheduling as immediate termination.

Suggested review condition: Do not report immediate cancellation or debt removal solely because cancellation was scheduled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the merchant continues service until the period ends is a separate contract and application decision.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid ending prepaid access early or treating scheduled cancellation as cleared liabilities.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Changing VAREXIS subscription terms or prescribing customer access policy
  • Whether the merchant continues service until the period ends is a separate contract and application decision.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe shared credit grants and invoice order

Question: Can invoice creation order predict which Stripe subscription consumes a shared billing-credit grant first?

Stripe applies a grant eligible for multiple invoices to the invoice that finalizes first. Subscription invoices finalize independently, so their finalization order is not guaranteed. Within one invoice, eligible lines consume credit in their listed order. Reconcile actual allocation rather than assuming creation order or equal sharing.

Source: Stripe: Billing credits. Documentation checked 2026-10-28; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can invoice creation order predict which Stripe subscription consumes a shared billing-credit grant first?

Buyer evidence still required

  • Shared grant and eligible subscriptions
  • Invoice finalization timestamps
  • Invoice line order and actual credit applications

Review inference: Review stripe shared credit grants and invoice order before accepting the buyer claim. The competition for a shared grant is a separate operational allocation decision from refund accounting. This is a documentation-review judgment, not an observed deployment outcome.

Suggested review condition: Refuse predicted per-subscription credit allocation without finalized invoice and credit application evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.

Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.

Recheck: Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included. Multiple invoices or line items

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse predicted per-subscription credit allocation without finalized invoice and credit application evidence.
  • Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Stripe shared payment tokens: Seller scope and lifecycle limit delegated spending

Question: What spending authority does an agent grant with a Stripe shared payment token?

Stripe's agent-side SPT guide creates a token for a seller Stripe profile using a customer payment method, with currency, maximum amount and expiry limits. Revocation prevents the seller using that token to create a payment. Token states include active, requires_action and terminal deactivated; deactivation can mean consumption, expiry or revocation. A token state alone is not a settlement or delivery record.

Source: Stripe shared payment tokens for agents. Documentation checked 2026-10-23; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: What spending authority does an agent grant with a Stripe shared payment token?

Buyer evidence still required

  • Seller profile, customer authority, currency, maximum amount, expiry and applicable preview API version
  • Token state, deactivation reason and authenticated lifecycle event evidence
  • Correlated payment status, external fulfilment and any reversal evidence

Review inference: Review the bounded spending grant and resulting payment separately; revocation and token deactivation cannot substitute for payment-outcome evidence.

Suggested review condition: Refuse a completed, settled, delivered or reversed purchase claim supported only by token creation, active status, consumption or revocation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Customer consent, seller eligibility, buyer token configuration and actual payment, reversal or fulfilment outcomes are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Separate a delegated spending grant from the evidence required to reconcile the resulting purchase and delivery.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Independent customer consent, completed settlement, delivery or reversal of an existing payment
  • Universal country or payment-method availability, or automatic SPT support in an INDEX executable
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe signing-secret rotation overlap

Question: Can more than one Stripe webhook signing secret remain valid during a planned rotation?

Stripe allows immediate secret expiration or a delayed expiration of up to twenty-four hours. During the overlap, multiple secrets can be active and Stripe generates a signature for each active secret. Rotation completion therefore requires checking the old secret’s expiry rather than assuming it stopped working when the new one appeared.

Source: Manage webhook endpoints. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can more than one Stripe webhook signing secret remain valid during a planned rotation?

Buyer evidence still required

  • Endpoint and active secret versions
  • Scheduled expiry and receiver rollout state
  • Verification checks across the rotation boundary

Review inference: Reconcile receiver configuration with the intended overlap and expiry schedule.

Suggested review condition: Do not claim the old signing secret is invalid before its documented expiry.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual endpoint rotation state and secret exposure are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Plan event-verification continuity without overstating revocation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic revocation of other credentials or sessions
  • The actual endpoint rotation state and secret exposure are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe subscription status and outstanding invoices

Question: Does an active Stripe subscription establish that every outstanding invoice is paid?

Stripe explicitly states that active does not necessarily mean every outstanding subscription invoice has been paid. Status resolution can depend on the most recent invoice or all applicable invoices; settling can also include marking an invoice uncollectible. Failed-payment settings can leave a subscription past_due. Subscription status and invoice-level collection evidence are therefore separate.

Source: How subscriptions work. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an active Stripe subscription establish that every outstanding invoice is paid?

Buyer evidence still required

  • Subscription status-resolution and failed-payment settings
  • Applicable invoice statuses and payment evidence
  • Merchant access policy and current entitlement state

Review inference: Reconcile the invoices and merchant access policy instead of equating active with all debt collected or past_due with automatic service removal.

Suggested review condition: Refuse a claim of fully paid subscription access from the aggregate subscription status alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The merchant policy, applicable invoices and actual access enforcement are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid incorrect access and revenue decisions based on a single subscription flag.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Subscription status as complete cash-collection or access-control proof
  • The merchant policy, applicable invoices and actual access enforcement are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe Tax: Calculated amounts need a transaction binding

Question: What binds a Stripe tax calculation and approved purchase terms to the payment actually submitted?

Stripe's custom tax integration uses a calculation's amount_total as the amount to charge. Recording the sale requires a Tax Transaction created from that calculation, with a unique reference for reconciliation. The calculation can be used until expires_at, documented as 90 days; recorded Tax Transaction amounts are not recalculated for later tax-rate changes.

Source: Custom Stripe Tax API | Stripe Documentation. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: What binds a Stripe tax calculation and approved purchase terms to the payment actually submitted?

Buyer evidence still required

  • Calculation ID, expiry, line items, currency and tax-inclusive total.
  • Versioned buyer-approved terms and actual submitted payment fields.
  • Payment outcome, order reference and Tax Transaction ID or reversal records.

Review inference: Calculation/reference linkage does not establish buyer approval; approved terms must be reconciled separately with what was submitted.

Suggested review condition: Refuse an approved-transaction claim if the approved amount, currency, items or terms cannot be bound to the submitted transaction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No approval, tax treatment or actual settlement was validated.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck calculation expiry, amended terms and final payment/tax records after material changes.

Optional saved evidence: Reconcile spending authority or transaction state before approving financial reliance.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Tax advice, legal compliance, approved spending authority or verified settlement
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe thin events and reconstructed object state

Question: Does fetching the related object for a Stripe thin event reconstruct its exact historical state?

Stripe thin notifications contain limited event information. The event and its related object can be retrieved separately; retrieving the related object returns its latest state, not necessarily the state when the notification was generated. A current object must not be silently presented as the historical event snapshot.

Source: How events work. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does fetching the related object for a Stripe thin event reconstruct its exact historical state?

Buyer evidence still required

  • Thin event identity and creation context
  • Retrieved event data and retrieval time
  • Current related object and historical decision records

Review inference: Separate event-time evidence from current-state retrieval when reconstructing fulfilment decisions.

Suggested review condition: Refuse historical-state claims based only on a later related-object fetch.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Intervening updates and the buyer’s original decision state are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid rewriting payment history with later object state.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Purchase fulfilment from notification receipt alone
  • Intervening updates and the buyer’s original decision state are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe transfer acceptance and available funds

Question: Does a successful Stripe transfer request prove that the associated charge funds were already available?

For separate charges and transfers, a transfer using source_transaction can be accepted before the charge funds become available; Stripe waits for those funds before executing it. Without that linkage, available platform balance constrains transfers, and failed transfers are not automatically retried. Acceptance, funding availability and completed movement must therefore be distinguished.

Source: Create separate charges and transfers. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a successful Stripe transfer request prove that the associated charge funds were already available?

Buyer evidence still required

  • Transfer ID, source_transaction and linked charge
  • Balance availability and transfer outcome
  • Existing retry and supplier-delivery reconciliation records

Review inference: Reconcile the transfer funding source and resulting balance state before representing the supplier as paid.

Suggested review condition: Do not treat request acceptance or unrelated platform balance as proof that the intended charge funded the supplier.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual payment-method timing, balance availability and recipient payout were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid releasing a supplier obligation based on a queued funds movement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Transfer acceptance proving bank receipt or immutable settlement
  • The actual payment-method timing, balance availability and recipient payout were not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Stripe transfer groups and funding provenance

Question: Does a shared Stripe transfer_group prove a one-to-one funding relationship between a charge and transfer?

Stripe describes transfer_group as an association string that does not change standard transfer behavior. Charge and transfer amounts need not match: one charge can support several transfers, and several charges can be included in a transfer. A shared group alone therefore does not establish a unique funding allocation or completed delivery for a particular purchase.

Source: Create separate charges and transfers. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a shared Stripe transfer_group prove a one-to-one funding relationship between a charge and transfer?

Buyer evidence still required

  • Charge and transfer IDs sharing the group
  • Amounts, currencies and source_transaction bindings
  • Order-level allocation and entitlement evidence

Review inference: Retain explicit charge, transfer, amount and order allocations instead of relying on a group label as payment provenance.

Suggested review condition: Refuse a claim of uniquely funded licensed delivery when only a transfer_group match is available.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The merchant allocation logic and actual delivered purchase remain outside the group field.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Reconstruct procurement funding without confusing a label with a verified allocation.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • An association label as cryptographic or one-to-one funding proof
  • The merchant allocation logic and actual delivered purchase remain outside the group field.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Successful CreateEvent can persist short-term event while strategy extraction is skipped

Question: Does accepting an AgentCore event prove all intended tenant-scoped extraction ran?

AWS states that when CreateEvent omits a custom namespace variable referenced by a strategy template, extraction is not initiated for that strategy even though the event succeeds and persists in short-term memory. NamespaceResolutionFailure metrics identify the skipped strategy.

Source: Amazon Web Services primary documentation: aws memory namespaces. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does accepting an AgentCore event prove all intended tenant-scoped extraction ran?

Buyer evidence still required

  • namespace-key schema
  • runtime values
  • strategy templates
  • extraction/skip metrics
  • event ID

Review inference: Does accepting an AgentCore event prove all intended tenant-scoped extraction ran? Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction. Successful CreateEvent can persist short-term event while strategy extraction is skipped. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. NamespaceResolutionFailure

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Bind extraction evidence to the intended namespace and strategy; event acceptance alone is insufficient evidence of complete tenant-scoped extraction.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Supabase backup evidence: Database recovery and stored files

Question: Does a Supabase database backup also recover the uploaded files used by my application?

Supabase documents that database backups contain Storage metadata, not the stored object contents. Restoring a database backup does not recover objects deleted afterwards. A whole-application recovery claim needs separate evidence for files and other dependencies, together with the actual backup configuration and a suitable restore check.

Source: Supabase database backup coverage. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A database backup alone establishes complete recovery of our Supabase application.

Buyer evidence still required

  • The backup configuration and a dated available recovery point
  • Separate retention and recovery evidence for stored objects
  • A restore review covering the dependencies the application needs

Suggested review condition: Do not approve a whole-application recovery claim when only database backup evidence is available.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck backup mode, Storage handling, role credentials and application dependencies.

Optional saved evidence: Retain the distinction between database restoration and attachment recovery during supplier review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Supabase MCP: Database access and developer authority

Question: What should an agent check before connecting a database project to Supabase MCP?

Supabase documents project scoping, read-only mode and feature-group restrictions. Its guidance identifies developer permissions and warns about untrusted database content. Review those controls and the actual data requested before connecting a sensitive project. A confirmation prompt or read-only query does not establish that returned data is suitable for the client or model receiving it.

Source: Supabase MCP scope and security. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Supabase-hosted MCP for developer use; project, enabled features and authentication method must be specified.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Supabase publishes the MCP and hosted connection guidance.

Documented by publisher. Supabase MCP scope and security; Supabase MCP repository

Purpose

Inspect database projects and perform permitted development operations.

Documented by publisher. Supabase MCP scope and security; Supabase MCP repository

Read capability

Schema, query results and project logs through enabled features.

Documented by publisher. Supabase MCP scope and security; Supabase MCP repository

Write capability

SQL, migrations and deployment tools exist outside applicable restrictions.

Documented by publisher. Supabase MCP scope and security; Supabase MCP repository

Authentication

Hosted OAuth registration is documented; scoped PATs support unattended use. Manual OAuth setup has separately documented scope requirements.

Documented by publisher. Supabase MCP scope and security; Supabase MCP repository

Permission surface

Project scope disables account management tools; read-only queries and selected feature groups reduce the exposed surface.

Documented by publisher. Supabase MCP scope and security; Supabase MCP repository

Data leaving the environment

Query results and logs reach the connected client. A read-only connection can still disclose sensitive rows.

Review inference. Supabase MCP scope and security; Supabase MCP repository

Failure modes to consider

Developer authority mistaken for end-user row permissions; instructions in stored content; assuming every SQL operation requires a human confirmation.

Review inference. Supabase MCP scope and security; Supabase MCP repository

Unknowns and applicability

Resolved grants, data sensitivity, effective feature restrictions, client retention and buyer-specific isolation.

Not established

Suggested refusal or clarification condition

For a diagnostic-only task, withhold writes and minimize returned data; do not give an end user the developer connector.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Review the effective tool inventory and client data policy before a new integration decision.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve project scoping, read-only and data-disclosure questions behind a database-tool review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Supersession preserves old history despite latest-first recall

Question: Does a newer Cloudflare memory fact replace and erase the previous fact?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The beta documentation describes facts and instructions being superseded by topic key while retaining old versions; recall preferentially surfaces the latest version.

Source: Cloudflare primary documentation: cloudflare memory how. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a newer Cloudflare memory fact replace and erase the previous fact?

Buyer evidence still required

  • topic key
  • old/new memory IDs
  • supersession state
  • history inventory
  • deletion scope

Review inference: Does a newer Cloudflare memory fact replace and erase the previous fact? Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation. Supersession preserves old history despite latest-first recall. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. full history is preserved

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not equate supersession or absence from recall with deletion; record historical versions and their disposal evidence. Private beta access and current feature applicability require separate confirmation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Supplier criticality depends on the intended use

Question: Can supplier brand or spend alone determine the assurance tier for an enterprise MCP service?

NIST SP 1305 recommends supplier-criticality criteria based on business importance, data sensitivity and system access, followed by prioritised supplier records. Review implication: Brand or spend alone does not describe this intended-use consequence. The buyer must supply its criticality criteria; this record supplies no risk score or mandatory tier.

Source: NIST SP 1305 C-SCRM quick-start. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can supplier brand or spend alone determine the assurance tier for an enterprise MCP service?

Buyer evidence still required

  • Business process dependency and failure impact
  • Data sensitivity and system access
  • Documented criticality criteria and assigned tier

Review inference: Brand or spend alone does not describe this intended-use consequence. The buyer must supply its criticality criteria; this record supplies no risk score or mandatory tier.

Suggested review condition: No quantitative risk score, supplier certification or mandatory NIST threshold is supplied.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • Voluntary NIST CSF 2.0/SP 1305 guidance, final October 2024. No automatic UK/EU legal obligation or supplier certification.
  • No quantitative risk score, supplier certification or mandatory NIST threshold is supplied.
  • A small supplier may be critical for a sensitive workflow, while a large supplier may be low criticality for a limited use.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Synced skill preprocessing differs by execution surface and client version

Question: Can the same synced Claude skill have identical execution behaviour in cloud and local sessions?

The captured guide distinguishes cloud, Cowork and other local sessions for shell preprocessing, file references and substitutions, with relevant restrictions requiring Claude Code v2.1.228 or later.

Source: Anthropic primary documentation: claude code skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Can the same synced Claude skill have identical execution behaviour in cloud and local sessions?

Buyer evidence still required

  • source of synced skill
  • client version
  • session surface
  • command/file/substitution usage

Review inference: Can the same synced Claude skill have identical execution behaviour in cloud and local sessions? Do not transfer an approval between surfaces without recording client version and the effective preprocessing rules. Synced skill preprocessing differs by execution surface and client version. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not transfer an approval between surfaces without recording client version and the effective preprocessing rules.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. How Claude Code handles the body of a synced skill

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not transfer an approval between surfaces without recording client version and the effective preprocessing rules.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Derived claim boundary

Synthetic IIoT: Customer validation boundary

Question: Does the synthetic IIoT record establish real customer environment validation?

The public IIoT source describes synthetic workload reduction and scale. It excludes real customer environment validation.

Derived from BDAS IIoT Synthetic 60M Logs — Public-Safe Reduction Summary. No new experiment or validation is claimed.

Claim boundaries
  • real customer environment validation
  • new experimental result
  • independent validation
  • evidence maturity upgrade

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Systems Manager: Aggregate success and target evidence

Question: Does Run Command Success prove the intended change completed on every targeted machine?

Systems Manager reports plugin, invocation and aggregate command statuses separately. AWS documents Success cases with no matching tagged instances, tolerated invocation failures or a zero exit code despite prevented execution. The overall status therefore does not establish the intended change on every target.

Source: AWS Systems Manager: Understanding command statuses. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does Run Command Success prove the intended change completed on every targeted machine?

Buyer evidence still required

  • Intended and resolved target population, command document revision and error settings.
  • Per-node invocation and plugin statuses with meaningful exit results.
  • Dated checks of the intended change on each required target and unresolved exceptions.

Suggested review condition: Decline fleet-wide completion claims until required targets and per-node outcomes are reconciled; treat missing or unverified effects as open evidence gaps.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Intended and resolved target population, command document revision and error settings. Per-node invocation and plugin statuses with meaningful exit results. Dated checks of the intended change on each required target and unresolved exceptions.

Optional saved evidence: A fleet-wide agent change needs proof of target population and per-node effect, not only a green aggregate result.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Successful execution on every node, correctness of the intended configuration change or complete fleet coverage
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Task deprioritisation after session end versus deletion

Question: Does ending a Cloudflare Agent Memory session delete its task memories?

Cloudflare Agent Memory PRIVATE BETA, documentation reviewed 30 October 2026: The documented task class is session-scoped and deprioritised after the session ends. Deprioritisation describes retrieval treatment rather than an asserted deletion operation.

Source: Cloudflare primary documentation: cloudflare memory how. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does ending a Cloudflare Agent Memory session delete its task memories?

Buyer evidence still required

  • task memory IDs
  • session lifecycle
  • recall behaviour
  • applicable deletion/retention evidence

Review inference: Does ending a Cloudflare Agent Memory session delete its task memories? Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation. Task deprioritisation after session end versus deletion. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Tasks are deprioritized

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not use lower ranking as expiry evidence; identify a deletion or retention process and its results. Private beta access and current feature applicability require separate confirmation.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Tavily MCP: Account selection and query attribution

Question: Does signing in to Tavily MCP prove that queries use the intended team API key?

Tavily documents a key-selection order for remote OAuth connections, including a named default and personal-versus-team precedence. Login alone therefore does not demonstrate the intended billing identity. Check the selected key and account before sending work queries; session attribution is separate from user authorization.

Source: Tavily MCP authentication and session attribution. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Official remote OAuth/API-key and local wrapper

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Tavily publishes the MCP integration and operates the search API.

Documented by publisher. Tavily MCP authentication and session attribution

Purpose

Provide search and content extraction to MCP clients.

Documented by publisher. Tavily MCP authentication and session attribution

Read capability

Search results and extracted web content.

Documented by publisher. Tavily MCP authentication and session attribution

Write capability

The reviewed scope concerns retrieval and account usage; business-application mutation is not established.

Not established. Tavily MCP authentication and session attribution

Authentication

Remote OAuth or API key; local wrapper uses API authentication.

Documented by publisher. Tavily MCP authentication and session attribution

Permission surface

OAuth key-selection rules can select personal rather than team credentials.

Documented by publisher. Tavily MCP authentication and session attribution

Data leaving the environment

Queries and retrieval targets reach the service; review any client-supplied identifiers.

Review inference. Tavily MCP authentication and session attribution

Failure modes to consider

An unintended key may attribute work to the wrong account or usage budget.

Review inference. Tavily MCP authentication and session attribution

Unknowns and applicability

Selected credentials, retention obligations and effective client settings are unverified.

Not established

Suggested refusal or clarification condition

Resolve billing identity and query-data permission before sensitive or chargeable work.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck OAuth key-selection rules, account membership and client attribution settings.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the reviewed account-selection assumptions behind an agent research connection.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Teams deletion and retained mailbox evidence

Question: Does a Teams message disappearing from chat prove that its retained compliance copy is gone?

Microsoft describes separate Teams service data and message copies in hidden Exchange mailbox locations used by compliance tools. Chat and channel types use different mailbox types. Retention and eDiscovery operate on these compliance copies, so the visible Teams conversation is not a complete inventory of retained message evidence.

Source: Learn about retention for Teams | Microsoft Learn. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Teams message disappearing from chat prove that its retained compliance copy is gone?

Buyer evidence still required

  • Chat or channel type and message identity
  • Relevant mailbox type, retention policy and hold scope
  • eDiscovery results and documented content exclusions

Review inference: Reconcile the relevant mailbox location and policy with the chat view before claiming deletion.

Suggested review condition: Refuse a complete-deletion conclusion based only on the Teams user interface.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual mailbox copies, tenant policies and export results have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Locate the correct retained evidence when investigating or offboarding a Teams-based agent.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete Teams content coverage from a visible chat view
  • Actual mailbox copies, tenant policies and export results have not been inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Teleport MCP: Proxy identity and upstream OAuth

Question: Does a Teleport login also authorize the upstream MCP service?

Some upstream servers need a separate OAuth token. Teleport still applies its own roles and tool permissions, while the upstream token satisfies that service. The documented login stores credentials locally and contacts the authorization server from the workstation. Changing the upstream URI requires a new login.

Source: Teleport upstream MCP OAuth. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: One proxy login establishes all upstream permissions and contains every authentication flow.

Buyer evidence still required

  • Teleport roles and allowed tools.
  • Upstream OAuth issuer, scopes and server URI.
  • Client version and local credential handling.

Suggested review condition: Confirm both authority layers and authorization-server access before connecting.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Teleport version, roles, upstream URI, OAuth issuer, scopes and client credentials.

Optional saved evidence: Retain the two-layer identity boundary for a managed connector review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Temporal business refusal and retry policy

Question: Will Temporal automatically recognise a business refusal as a non-retryable Activity failure?

Temporal Retry Policies support non-retryable error types matched against the Application Failure type, and SDKs can report an explicitly non-retryable failure. The default non-retryable error list is empty. Activity retry defaults do not classify an application-specific business refusal on the buyer's behalf.

Source: What is a Temporal Retry Policy? | Temporal Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Will Temporal automatically recognise a business refusal as a non-retryable Activity failure?

Buyer evidence still required

  • Application failure type and SDK error construction
  • Effective Activity retry policy and execution timeout
  • Business refusal semantics and evidence of any later renewed authority

Review inference: Map a permanent refusal, such as denied authority, to the appropriate application failure handling before allowing retries.

Suggested review condition: Do not treat retry backoff as renewed permission or keep retrying a permanent refusal without an explicit business decision.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the worker correctly classifies failures and whether a later attempt is authorised are not established by the policy documentation.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent recovery policy from being mistaken for authority to repeat a refused action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic classification of arbitrary business errors or renewal of payment or tool authority
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Temporal closed history retention and archive evidence

Question: Can Temporal retention expiry remove the history needed to reconstruct a closed Workflow?

Temporal retention applies to closed Workflow execution data in a namespace's persistence store; cleanup is scheduled at the end of that period. Self-hosted Archival can copy closed histories and visibility records to blob storage beyond retention, but the reviewed documentation describes it as experimental and disabled by default for manual and Helm installations. Retention configuration alone is not evidence that an archive exists.

Source: Temporal Server | Temporal Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can Temporal retention expiry remove the history needed to reconstruct a closed Workflow?

Buyer evidence still required

  • Service version, namespace retention and Workflow close time
  • Applicable archival configuration and destination ownership
  • Retrieved history and visibility records with run coverage and integrity checks

Review inference: Preserve and verify the required history before cleanup; review archive availability, access and completeness separately.

Suggested review condition: Do not claim reconstructable history after retention expiry without an accessible, checked copy covering the required runs.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual archival success, storage retention, completeness and applicability to a managed Temporal service have not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Decide whether an agent workflow has enough retained evidence for later reconstruction or exit review.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed archival, complete business-event capture or a deletion or compliance certificate
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Temporal Continue-As-New run and history chain

Question: Does Temporal Continue-As-New preserve one run ID and one continuous event history?

Temporal Continue-As-New closes the current execution and starts a new execution in the same Workflow chain with the same Workflow ID, a new Run ID and a fresh event history. State needed by the next execution must be supplied in its input arguments. A single run history therefore does not cover the entire chain.

Source: Continue-As-New | Temporal Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Temporal Continue-As-New preserve one run ID and one continuous event history?

Buyer evidence still required

  • Workflow ID and linked run identifiers
  • Histories covering each relevant run
  • Continue-As-New inputs and applicable approval context

Review inference: Reconstruction should join the relevant runs and examine the state explicitly carried forward; unchanged Workflow ID does not prove unchanged approval context.

Suggested review condition: Do not treat one run export or an unchanged Workflow ID as complete evidence for the whole execution chain.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether required state and buyer authorisation were carried forward correctly is application-specific and unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Reconstruct long-running agent work across execution boundaries without losing evidence linkage.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic preservation of every prior event or independent approval of a continued action
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Temporal parent closure and child workflow policy

Question: Can a Temporal child Workflow continue after its parent closes?

Temporal Parent Close Policy determines what happens to a child Workflow when its parent closes. Abandon leaves it unaffected; RequestCancel requests cancellation; Terminate terminates the child Workflow and is the documented default. The policy is set per child. Parent closure therefore cannot by itself establish that every child stopped.

Source: Parent Close Policy | Temporal Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can a Temporal child Workflow continue after its parent closes?

Buyer evidence still required

  • Parent close event and child execution identities
  • Parent Close Policy configured for each child
  • Child terminal history and separate external outcome evidence

Review inference: Inspect each child policy and terminal history before closing an incident; Workflow termination is not proof that an external side effect was undone.

Suggested review condition: Do not report all delegated work stopped merely from the parent's terminal status.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Configured policies, child acceptance of cancellation and downstream residual effects remain buyer-specific.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Close delegated work with evidence for each child instead of relying on the parent status.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed external process termination, automatic rollback or reversal of completed effects
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Temporal replay versus Activity reexecution

Question: Does Temporal Workflow replay itself repeat a completed Activity external side effect?

Temporal replays deterministic Workflow code against recorded history and compares generated commands with the existing events. External interactions belong in Activities, which execute outside the replay path. Activity retries are a separate mechanism. A Workflow replay should therefore not be equated with a new execution of every recorded Activity.

Source: Temporal Workflow Definition | Temporal Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Temporal Workflow replay itself repeat a completed Activity external side effect?

Buyer evidence still required

  • Workflow and run identifiers with relevant history
  • Worker code version and replay or reset operation performed
  • Activity attempt identifiers and downstream operation receipts

Review inference: Distinguish history replay from a fresh Activity attempt or a newly started Workflow before assessing duplicate external effects.

Suggested review condition: Do not promise exactly-once external effects from deterministic replay alone, especially when Activity retries or new runs are involved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer code may violate deterministic constraints or place external interactions outside Activities; the actual replay and provider outcomes were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Review recovery without confusing reconstructed Workflow state with new external execution.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A guarantee that arbitrary Workflow code is deterministic or that retries cannot duplicate external actions
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Temporal timeout and uncertain external effects

Question: Does a Temporal Activity timeout prove that its external action did not complete?

Temporal can time out an Activity Task when its worker does not report completion, including when the worker called an external function and then failed. Activity retry policies can schedule another attempt. The timeout reports the execution boundary observed by Temporal; it does not establish that an external system made no change.

Source: Activity Execution | Temporal Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a Temporal Activity timeout prove that its external action did not complete?

Buyer evidence still required

  • Activity attempt history and configured timeouts
  • External operation identifier and provider outcome evidence
  • Retry policy, deduplication scope and current authority for another attempt

Review inference: Before repeating a consequential external operation, reconcile its provider-side outcome and idempotency boundary instead of treating timeout as proof of non-execution.

Suggested review condition: Do not conclude that retrying is harmless while the first external outcome or retry authority is unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether the external action committed, whether the first worker is still active and whether the provider will deduplicate a repeated request remain buyer-specific.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Decide whether a timed-out agent action may safely be retried under its existing authority.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exactly-once effects, automatic compensation or proof that a timeout prevented a purchase
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Temporal workflow ID reuse and idempotency scope

Question: Does Temporal Workflow ID reuse policy deduplicate every external API call made by an agent?

Temporal distinguishes conflict handling for an already running Workflow ID from reuse policy for a closed execution with that ID. Closed-execution reuse checks depend on retained history, and the default reuse policy permits another execution. These policies govern starting Workflow executions in a namespace, not provider-side deduplication of each external API call.

Source: Workflow Id and Run Id | Temporal Documentation. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does Temporal Workflow ID reuse policy deduplicate every external API call made by an agent?

Buyer evidence still required

  • Namespace, Workflow ID and run IDs
  • Conflict and reuse policies with applicable history retention
  • External request identifiers and provider deduplication rules

Review inference: Record both Workflow identity policy and external idempotency keys; neither can substitute for the other.

Suggested review condition: Do not infer that an external purchase cannot be repeated solely because a Workflow ID is reused or a reject-duplicate policy is configured.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Retained executions, selected start options and provider duplicate handling remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Choose a recovery identity policy without overstating its protection against repeated purchases.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Permanent Workflow ID uniqueness or exactly-once external transactions
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Temporal: Cooperative activity cancellation

Question: Does requesting Temporal activity cancellation forcibly stop the worker or its external action?

Temporal documents activity cancellation as a cooperative notification that allows cleanup. Activities must heartbeat to receive cancellation from the service, and activity code can accept or ignore it. A workflow can proceed without waiting for acceptance. A cancellation request therefore does not establish that the worker or an external effect has stopped.

Source: Temporal: Activity execution. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does requesting Temporal activity cancellation forcibly stop the worker or its external action?

Buyer evidence still required

  • Activity identity, SDK cancellation behavior and heartbeat history.
  • Cancellation request, worker handling and workflow wait behavior.
  • Cleanup result and external-effect observations after the request.

Suggested review condition: Decline stopped-or-cleaned claims until worker cooperation and external-effect closure are evidenced.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Activity identity, SDK cancellation behavior and heartbeat history. Cancellation request, worker handling and workflow wait behavior. Cleanup result and external-effect observations after the request.

Optional saved evidence: Recovery must distinguish the cancellation request, worker acknowledgement and actual effect closure.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Forced process termination, automatic undo or an INDEX cancellation service
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Tenable Hexa AI: Scan authority and external clients

Question: Does Tenable Hexa AI MCP only read vulnerability findings?

Tenable documents both retrieval and state-changing operations, including tagging assets, creating dashboards and launching scans. The hosted connector uses Tenable API keys and requires an eligible Tenable One licence and enabled access. The buyer supplies the AI client; its handling of returned exposure data needs a separate review.

Source: Tenable: Hexa AI MCP. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Dated publisher documentation; buyer deployment unverified

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Tenable operates the hosted Hexa AI MCP endpoint.

Documented by publisher. Tenable: Hexa AI MCP

Purpose

Connect an AI client to exposure data and supported security workflows.

Documented by publisher. Tenable: Hexa AI MCP

Read capability

Authorized asset and vulnerability information.

Documented by publisher. Tenable: Hexa AI MCP

Write capability

Documented tools can tag assets, create dashboards and launch scans.

Documented by publisher. Tenable: Hexa AI MCP

Authentication

Tenable Vulnerability Management access key and secret key.

Documented by publisher. Tenable: Hexa AI MCP

Permission surface

Eligible licence, enabled Hexa AI access and appropriate user-role privileges.

Documented by publisher. Tenable: Hexa AI MCP

Data leaving the environment

Security results reach the buyer-selected AI client; client retention is not established here.

Review inference. Tenable: Hexa AI MCP

Failure modes to consider

A request framed as investigation may select a state-changing tool.

Review inference. Tenable: Hexa AI MCP

Unknowns and applicability

Effective tenant grants, selected client and tool execution have not been inspected.

Not established

Suggested refusal or clarification condition

Confirm target assets, scan authority and client data handling before allowing actions.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Licence eligibility, account access controls and tool mutations.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the permission and disclosure basis used before admitting a security connector.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Tender access does not establish permission to train

Question: Does sharing confidential tender material with a bidder establish permission to use it for model training?

PPN 017 describes proportionate controls to prevent confidential authority information or other non-public information being used as AI training data by suppliers. Review implication: Access to tender material alone does not establish training permission or actual compliance with the agreed handling restriction.

Source: Cabinet Office PPN 017. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does sharing confidential tender material with a bidder establish permission to use it for model training?

Buyer evidence still required

  • Document classification and disclosure scope
  • Applicable tender handling restrictions
  • Supplier process for AI input and training use

Review inference: Access to tender material alone does not establish training permission or actual compliance with the agreed handling restriction.

Suggested review condition: Do not claim that every AI input trains a model or that a supplier actually complied with a restriction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK central government departments, executive agencies and non-departmental public bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • Do not claim that every AI input trains a model or that a supplier actually complied with a restriction.
  • An applicable express training permission and handling agreement could support that narrower authority; receipt of a document alone cannot.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Terraform MCP: Tool selection is separate from destructive-operation gating

Question: Does disabling destructive Terraform operations make MCP read-only?

The operation switch gates specified destructive actions, not every write. The reference also lists project, team and access-grant creation. Omitting toolset selection enables all toolsets, with authenticated management tools depending on the token. Review the actual tool list and token permissions.

Source: Terraform MCP toolsets and operation controls. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: HashiCorp Terraform MCP registry and management toolsets

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

HashiCorp publishes the Terraform MCP server.

Documented by publisher. Terraform MCP toolsets and operation controls

Purpose

Registry lookup and Terraform service management.

Documented by publisher. Terraform MCP toolsets and operation controls

Read capability

Registry documentation, workspaces, plans and access information.

Documented by publisher. Terraform MCP toolsets and operation controls

Write capability

Project, team, workspace and run operations include writes.

Documented by publisher. Terraform MCP toolsets and operation controls

Authentication

Authenticated management uses a Terraform service token.

Documented by publisher. Terraform MCP toolsets and operation controls

Permission surface

Tool selection, token permissions and the destructive-operation switch are separate controls.

Documented by publisher. Terraform MCP toolsets and operation controls

Data leaving the environment

Plans and configuration returned to an agent may reveal infrastructure details.

Review inference. Terraform MCP toolsets and operation controls

Failure modes to consider

A destructive-operation label can be mistaken for a universal write block.

Review inference. Terraform MCP toolsets and operation controls

Unknowns and applicability

Effective token access and server configuration are unverified.

Not established

Suggested refusal or clarification condition

Do not call the connection read-only without checking each exposed operation.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. New tools, default toolsets and operation-gate coverage.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the distinction between a destructive-operation gate and an approved management-tool set.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Terraform: Saved plan execution has no new prompt

Question: Will Terraform ask an agent for approval again when it applies a saved plan file?

Passing a saved plan to terraform apply executes its planned operations without another confirmation prompt. Terraform treats submission of that plan as approval. Planning options cannot be changed in this mode; the saved plan can be inspected with terraform show before execution.

Source: terraform apply command reference | Terraform | HashiCorp Developer. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Will Terraform ask an agent for approval again when it applies a saved plan file?

Buyer evidence still required

  • Saved plan artifact identity.
  • Review of its displayed operations.
  • Caller authority and apply invocation.

Suggested review condition: Do not assume an interactive confirmation remains after a saved plan is passed to apply.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Saved plan artifact identity. Review of its displayed operations. Caller authority and apply invocation.

Optional saved evidence: Place owner review before handing an approved plan to automated execution.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Fresh infrastructure validation, safety of planned changes or authorization to execute them
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Terraform: Sensitive display masking is separate from persistence

Question: Does marking a Terraform value sensitive keep it out of state and plan files?

The sensitive setting masks ordinary display, but does not by itself omit values from state or plans. The documentation provides separate ephemeral and write-only mechanisms with version and provider constraints. Review the actual data path and backend rather than accepting a masked screenshot as non-persistence evidence.

Source: Terraform sensitive and ephemeral values. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A sensitive variable cannot persist in infrastructure artifacts.

Buyer evidence still required

  • Value flow and relevant variable/resource declarations.
  • Terraform and provider support for omission mechanisms.
  • State/plan storage, access and export handling.

Suggested review condition: Do not infer non-persistence from display redaction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Provider support, language versions and state/export handling.

Optional saved evidence: Save the concrete distinction between hidden output, omitted values and protected artifact storage.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

The controller choice and storage exception must be explicit

Question: Which controller exit choice and claimed domestic-law storage exception must be evidenced under UK Article 28(3)(g)?

UK Article 28(3)(g) sets out the controller choice of return or deletion at the end of processing services, together with deletion of existing copies unless domestic law requires storage. Review implication: Identify the controller exit choice and evidence supporting any asserted legal storage exception. This duty is separate from evidence that return or deletion actually occurred.

Source: UK GDPR Article 28. Documentation checked 2026-11-13; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Which controller exit choice and claimed domestic-law storage exception must be evidenced under UK Article 28(3)(g)?

Buyer evidence still required

  • Controller exit choice and data scope
  • Applicable retention exception and legal basis
  • Return/deletion and residual-copy evidence

Review inference: Identify the controller exit choice and evidence supporting any asserted legal storage exception. This duty is separate from evidence that return or deletion actually occurred.

Suggested review condition: No verified deletion, legal exception determination or memory-custody enforcement is supplied.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.

Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.

Recheck: Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included. Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Claim boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No verified deletion, legal exception determination or memory-custody enforcement is supplied.
  • A supported domestic-law storage requirement can affect the exit handling; this does not prove all copies must or may be retained indefinitely.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

The recording Region is not always the inference Region

Question: Which Bedrock event field identifies where a cross-Region invocation was processed?

AWS records cross-Region requests in the source Region and documents additionalEventData.inferenceRegion for processing location. Its streaming-completion example uses serviceEventDetails.AdditionalEventData.additionalEntries.inferenceRegion and parentRequestId. The event type and correlation matter; awsRegion identifies where the event was recorded.

Source: Monitor Amazon Bedrock API calls using CloudTrail - Amazon Bedrock. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Which Bedrock event field identifies where a cross-Region invocation was processed?

Buyer evidence still required

  • Dated effective request, team and provider configuration with non-secret identifiers
  • Exact service, API mode, model and relevant policy or contract at request time
  • Correlated request and provider outcome evidence; missing observations remain unknown

Review inference: Require the matching endpoint, event type, selector coverage and correlated request; refuse to substitute a logging Region or missing region field for execution evidence.

Suggested review condition: Require the matching endpoint, event type, selector coverage and correlated request; refuse to substitute a logging Region or missing region field for execution evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual account configuration, governing agreements, request execution, logging completeness, all retained copies and deletion outcomes are unobserved. Source capture is not deployment attestation.

Free documentary evidence only; no live verification, sovereignty, legal compliance, verified deletion, supported gateway executable or new licence is established.

Recheck: Rolling source or configuration change; recheck relevant primary documents and agreements before reliance. No ongoing monitoring included. Stream-completion events for streaming invocations; The AdditionalEventData key

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the matching endpoint, event type, selector coverage and correlated request; refuse to substitute a logging Region or missing region field for execution evidence.
  • A request can be processed in its source Region, so the two values can agree; disagreement is not required for every cross-Region profile request.
  • No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
  • No new product compatibility, positive fit rule or licence right.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Todoist MCP: Task access and planning changes

Question: Does connecting Todoist for a daily review also expose task-changing tools?

Yes. Todoist documents a hosted OAuth MCP service with task and project reads, creation and updates. A planning or review request should specify whether the agent may change the plan. The overview does not establish a buyer-specific read-only grant.

Source: Todoist hosted MCP OAuth and task operations. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted task and project server

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Doist provides the Todoist MCP service.

Documented by publisher. Todoist hosted MCP OAuth and task operations

Purpose

Let assistants review and manage tasks and projects.

Documented by publisher. Todoist hosted MCP OAuth and task operations

Read capability

Reads task and project information.

Documented by publisher. Todoist hosted MCP OAuth and task operations

Write capability

Creates and updates tasks and projects.

Documented by publisher. Todoist hosted MCP OAuth and task operations

Authentication

OAuth for the hosted connection.

Documented by publisher. Todoist hosted MCP OAuth and task operations

Permission surface

The reviewed overview does not establish the buyer-specific action grant.

Not established. Todoist hosted MCP OAuth and task operations

Data leaving the environment

Task descriptions and project context enter the connected assistant.

Review inference. Todoist hosted MCP OAuth and task operations

Failure modes to consider

An ambiguous planning request may lead to unwanted task changes.

Review inference. Todoist hosted MCP OAuth and task operations

Unknowns and applicability

Buyer sharing arrangements and precise granted scopes are unverified.

Not established

Suggested refusal or clarification condition

Clarify whether the request is advice or an authorised task update.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck tool scopes and project-sharing changes.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the capability boundary used when approving a personal or team planning assistant.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Trace parent identifiers and missing history

Question: Does the W3C parent-id field contain the complete upstream request history?

The W3C parent-id identifies the caller’s current request or span, while trace-id identifies the overall distributed trace. Neither field contains the full upstream sequence. Reconstructing earlier operations requires the corresponding recorded spans and their parent relationships.

Source: Trace Context. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does the W3C parent-id field contain the complete upstream request history?

Buyer evidence still required

  • Trace and parent identifiers
  • Recorded upstream spans and parent links
  • Coverage and missing-span assessment

Review inference: Join separately collected span records; do not treat one propagated header as a complete chain.

Suggested review condition: Refuse complete lineage when required upstream span records are absent.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Earlier operations and their timestamps are not contained in the header.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Define the evidence required for cross-system audit reconstruction.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authenticated causality or complete history from a header
  • Earlier operations and their timestamps are not contained in the header.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Trace sampled flags and recording coverage

Question: Does a W3C sampled trace flag require every downstream component to record the operation?

W3C Trace Context treats trace flags as recommendations rather than strict downstream instructions. Trust decisions, implementation defects and downsampling can affect recording. The sampled bit conveys a caller recording decision; it is not confirmation that every downstream span was stored.

Source: Trace Context. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a W3C sampled trace flag require every downstream component to record the operation?

Buyer evidence still required

  • Received trace flags
  • Component sampling and recording policies
  • Expected spans and collected evidence

Review inference: Reconcile recording policy and actual collected spans separately from propagated flags.

Suggested review condition: Reject complete-trace claims based solely on sampled=1.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Downstream storage and missing spans remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a propagated sampling flag from masking evidence gaps.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Guaranteed end-to-end recording
  • Downstream storage and missing spans remain unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Trace-context privacy boundary

Question: Can customer identifiers or sensitive business data be embedded in W3C trace context?

The pinned W3C Recommendation prohibits personally identifiable and other sensitive information in traceparent and tracestate. It also cautions against identifiable random-number generation seeds. Correlation identifiers travel across components and must not become a covert customer-data channel.

Source: Trace Context. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can customer identifiers or sensitive business data be embedded in W3C trace context?

Buyer evidence still required

  • Trace identifier generation method
  • Tracestate fields and propagation destinations
  • Privacy classification of embedded values

Review inference: Review context generation and vendor state for sensitive information before cross-system propagation.

Suggested review condition: Refuse propagation designs that encode personal or sensitive data in these fields.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer’s generated identifiers and downstream retention are not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid disclosing customer data through telemetry correlation fields.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A general privacy or compliance certification
  • The buyer’s generated identifiers and downstream retention are not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Traceparent version and identifier validation

Question: Can an unfamiliar traceparent version or all-zero identifier be accepted without validation?

The pinned W3C Recommendation makes all-zero trace and parent identifiers invalid. Its higher-version parsing rules require checks of length, separators and known fields rather than blindly applying a current-format parser. Valid parsing establishes a usable context format, not an authenticated event history.

Source: Trace Context. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Can an unfamiliar traceparent version or all-zero identifier be accepted without validation?

Buyer evidence still required

  • Raw traceparent value and parser version
  • Validation outcome for version and identifier fields
  • Handling of rejected or restarted contexts

Review inference: Apply the specification’s version-specific validation before using incoming context for correlation.

Suggested review condition: Do not accept invalid identifiers or assume unknown versions have identical syntax.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The caller identity and causal truth of syntactically valid context are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid merging evidence through invalid or incorrectly parsed context.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Authentication or certified trace integrity
  • The caller identity and causal truth of syntactically valid context are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Transactional outbox: Commit and event publication

Question: Can a database change commit while its agent completion event is never published?

AWS describes the dual-write gap between a database update and a message notification: one can succeed while the other fails. A transactional outbox records the change and pending event within one database transaction, then publishes separately. The relay can publish duplicates, so consumers still need duplicate handling. This is architecture guidance, not evidence that a buyer implemented the pattern.

Source: AWS Prescriptive Guidance: Transactional outbox pattern. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can a database change commit while its agent completion event is never published?

Buyer evidence still required

  • Database transaction outcome and corresponding outbox entry or equivalent commit evidence.
  • Relay attempts, publication acknowledgements and stable event-to-action identifiers.
  • Consumer results and treatment of repeated or missing events.

Suggested review condition: Decline an event-complete or safe-retry conclusion while committed changes and publication outcomes remain unreconciled.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Database transaction outcome and corresponding outbox entry or equivalent commit evidence. Relay attempts, publication acknowledgements and stable event-to-action identifiers. Consumer results and treatment of repeated or missing events.

Optional saved evidence: Missing completion events can conceal committed actions and make a blind retry duplicate their effects.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Atomicity across arbitrary services or proof that the buyer uses an outbox
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Triggering/coexistence qualification versus isolated demonstration

Question: Does a skill's successful isolated demonstration establish safe selection alongside existing skills?

The enterprise guide calls for isolated and coexistence evaluations covering triggering accuracy, output quality and regressions across the active skill set, separately from security review.

Source: Anthropic primary documentation: claude skills enterprise. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a skill's successful isolated demonstration establish safe selection alongside existing skills?

Buyer evidence still required

  • active skill set
  • model/version
  • positive/negative/ambiguous cases
  • coexistence results

Review inference: Does a skill's successful isolated demonstration establish safe selection alongside existing skills? Do not promote solely from one successful demonstration or a scanner result; include incorrect-trigger and coexistence cases. Triggering/coexistence qualification versus isolated demonstration. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not promote solely from one successful demonstration or a scanner result; include incorrect-trigger and coexistence cases.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. coexistence testing

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not promote solely from one successful demonstration or a scanner result; include incorrect-trigger and coexistence cases.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Trivy offline mode: Network and database boundaries

Question: Does Trivy --offline-scan guarantee no network access and current vulnerability data?

The air-gap guide treats remote Java identification, database availability, version checks and telemetry separately. The offline-scan flag prevents remote dependency-identification requests; it is not an all-network switch. Database acquisition and freshness need their own evidence. Version checks and telemetry have independent disabling controls.

Source: Trivy: Air-gapped environment. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: One offline flag proves both isolation and up-to-date scan coverage.

Buyer evidence still required

  • Trivy version and all network-related settings.
  • Imported database version and capture date.
  • Network observation and dependency identification limits.

Suggested review condition: Require separate isolation and database-age evidence before accepting an offline coverage claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Trivy revision, command options, database identity, capture date and observed connectivity.

Optional saved evidence: Preserve the network and freshness boundary behind an offline scan.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Trivy: Package origin affects advisory interpretation

Question: Can an upstream fixed-version comparison replace Trivy OS-vendor advisory assessment?

The captured Trivy v0.67 guide uses distribution advisories for OS-managed packages because vendors can backport fixes without adopting the upstream version. It also describes precision versus comprehensive detection tradeoffs. Package origin and advisory selection matter; an upstream version comparison alone can misstate exposure.

Source: Trivy vulnerability scanning. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can an upstream fixed-version comparison replace Trivy OS-vendor advisory assessment?

Buyer evidence still required

  • The installed package origin and distribution version.
  • The selected advisory source and scanner mode.
  • Vendor fix evidence and the exact package build.

Suggested review condition: Do not declare a package affected or fixed solely from an upstream version when distribution backports are relevant.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The installed package origin and distribution version. The selected advisory source and scanner mode. Vendor fix evidence and the exact package build.

Optional saved evidence: A software reviewer must reconcile package provenance and vendor backports before accepting or disputing a vulnerability finding.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Exhaustive detection, malware assessment or confirmed exploitability
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Trivy: Unfixed filtering hides findings without fixing them

Question: Does a clean Trivy report using --ignore-unfixed show that no known affected packages remain?

The captured Trivy v0.67 documentation describes --ignore-unfixed as excluding affected, will_not_fix, fix_deferred and end_of_life statuses. Filtering those findings changes the report; it does not remediate the packages or establish that no known exposure remains.

Source: Trivy result filtering. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a clean Trivy report using --ignore-unfixed show that no known affected packages remain?

Buyer evidence still required

  • The installed scanner version and full invocation.
  • The status filters and unfiltered findings.
  • Package applicability and separate remediation evidence.

Suggested review condition: Do not treat findings hidden by --ignore-unfixed as repaired or absent vulnerabilities.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The installed scanner version and full invocation. The status filters and unfiltered findings. Package applicability and separate remediation evidence.

Optional saved evidence: A dependency owner must inspect scanner filters before using a clean report for an admission decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Current behavior of unreviewed Trivy versions or buyer-specific vulnerability applicability
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Trusted credential broker versus secrets injected into generated-code environment

Question: Does putting a credential in a secrets manager prevent a skill from reading it at runtime?

OpenAI distinguishes credentials kept outside execution and supplied by a trusted proxy from secrets injected into the environment, which remain exposed to generated code. Its executor environment key is also readable inside that environment.

Source: OpenAI primary documentation: openai sandbox security. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does putting a credential in a secrets manager prevent a skill from reading it at runtime?

Buyer evidence still required

  • credential flow diagram without secret values
  • proxy policy
  • injected variable names
  • executor key permissions

Review inference: Does putting a credential in a secrets manager prevent a skill from reading it at runtime? Do not claim secret isolation from storage alone; identify actual injection, proxy destinations and environment-key scope. Trusted credential broker versus secrets injected into generated-code environment. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not claim secret isolation from storage alone; identify actual injection, proxy destinations and environment-key scope.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Broker third-party access

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not claim secret isolation from storage alone; identify actual injection, proxy destinations and environment-key scope.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

TUF cross-file metadata consistency

Question: Can separately valid TUF signatures establish that timestamp, snapshot and targets metadata belong together?

The pinned client workflow also binds metadata versions and any listed hashes across roles: snapshot must match the trusted timestamp, and targets must match the trusted snapshot. These checks address mixed metadata sets. Valid signatures on independently selected files are not a substitute for verifying the required cross-file relationships.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can separately valid TUF signatures establish that timestamp, snapshot and targets metadata belong together?

Buyer evidence still required

  • Timestamp, snapshot and targets metadata
  • Referenced versions, hashes and signature results
  • Complete ordered verification outcome for the fetched metadata set

Review inference: Determine whether a signed tool release uses a coherent metadata set. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not accept a mixture of signed metadata files without their required cross-file bindings.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No repository release set or client validation trace has been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No repository release set or client validation trace has been inspected.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF delegated target authority

Question: Can a delegated TUF signer authorize a tool path allowed by its own metadata but excluded by an ancestor?

The pinned TUF delegation rules require the target path to satisfy trusted paths at every role in the delegation chain. Matching only the leaf role’s path is insufficient. A descendant cannot enlarge authority beyond an ancestor’s delegated path scope merely by signing metadata that names additional targets.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can a delegated TUF signer authorize a tool path allowed by its own metadata but excluded by an ancestor?

Buyer evidence still required

  • Target path and full delegation chain
  • Path or path-hash restrictions at each role
  • Approved publishing policy and target namespace

Review inference: Verify that a tool artifact lies within the complete delegated publishing scope. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not accept leaf-signer scope without checking every ancestor restriction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer delegation graph and artifact path have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer delegation graph and artifact path have not been inspected.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF delegation without relinquishment

Question: Does delegating a TUF target role remove the parent publisher’s authority over those targets?

The pinned TUF roles description says a delegating role remains trusted after it delegates full or partial target scope. Delegation is therefore not evidence that the parent has surrendered publishing authority. A buyer seeking exclusive control by a subsidiary signer must inspect the entire trust arrangement rather than infer exclusivity from a delegation entry.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does delegating a TUF target role remove the parent publisher’s authority over those targets?

Buyer evidence still required

  • Parent and delegated target metadata
  • Required exclusivity policy and configured trust roots
  • Buyer policy identifying every acceptable release authority

Review inference: Distinguish delegated publishing from exclusive release ownership. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not claim a delegated signer is the only publishing authority merely because delegation exists.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer exclusivity requirements and trust configuration are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer exclusivity requirements and trust configuration are unobserved.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF initial trust bootstrap

Question: Can an agent trust a new tool repository by downloading its own TUF root metadata from that repository?

The pinned TUF client workflow begins with a trusted root copy supplied through an out-of-band process. Repository-supplied metadata cannot independently establish that initial trust. Later root updates must continue from the accepted root. A buyer must identify who approved the starting root and how its bytes and keys reached the updater.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can an agent trust a new tool repository by downloading its own TUF root metadata from that repository?

Buyer evidence still required

  • Approved initial root bytes and source
  • Updater repository identity and stored root
  • Approval of the repository identity and distribution channel

Review inference: Separate initial repository approval from subsequent signed update validation. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not bootstrap authority from a root file whose only endorsement is the untrusted repository itself.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer root distribution process and initial trust decision are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer root distribution process and initial trust decision are unknown.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF root expiry during recovery

Question: Does an expired intermediate TUF root necessarily prevent reaching a valid current root?

The pinned TUF workflow allows trusted starting and intermediate root expiry to remain unchecked while following verified root updates. It checks expiry after reaching the final trusted root, against the fixed update start time. This recovery rule does not allow an expired final root or relax the intervening version and signature checks.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does an expired intermediate TUF root necessarily prevent reaching a valid current root?

Buyer evidence still required

  • Verified sequence of root versions
  • Final root expiry and fixed update start time
  • Client clock source and recorded update start time

Review inference: Distinguish permitted root-chain recovery from accepting stale final authority. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not use the intermediate-root exception to accept an expired final root.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer clock and complete verified root chain are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer clock and complete verified root chain are unobserved.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF root-rotation continuity

Question: Is a new TUF root trusted when only the new root keys signed it?

The pinned TUF root-update procedure requires the next root to satisfy signature thresholds from both the previously trusted root and the new root itself. A self-signed replacement alone does not establish continuity. Failed verification must abort that update cycle and retain the previous starting point for the next attempt.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Is a new TUF root trusted when only the new root keys signed it?

Buyer evidence still required

  • Previous and proposed root metadata
  • Distinct verified signatures against both key sets
  • Persisted accepted root state after the rotation attempt

Review inference: Verify that a publisher key change continues the approved update authority. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not accept a root replacement solely under its newly declared keys.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual signature verification and key compromise status are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual signature verification and key compromise status are unobserved.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF signature threshold identity

Question: Can repeated signatures from one TUF key satisfy a multi-key approval threshold?

The pinned TUF verification rules count each key only once toward a role’s signature threshold. Repeating a KEYID in the signatures list does not add another verified signer. A threshold review must therefore count distinct authorized key identifiers after signature verification, rather than count signature entries or signature blobs.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can repeated signatures from one TUF key satisfy a multi-key approval threshold?

Buyer evidence still required

  • Role key IDs and required threshold
  • Verified signature-to-key mapping
  • Key ownership and role membership at verification time

Review inference: Check whether claimed multi-key release approval actually uses distinct trusted keys. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not equate several signature entries with several independent authorized keys.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Key ownership independence and compromise have not been independently established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Key ownership independence and compromise have not been independently established.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF signed metadata freshness

Question: Does a valid TUF timestamp signature prove that the update metadata is fresh enough to use?

TUF timestamp verification includes distinct signature, version and expiry checks. The pinned workflow rejects rollback and an expiry no later than the fixed update start time, even if the signature is valid. Signing authenticity therefore does not replace freshness evidence; the buyer also needs a defensible client clock and retained version state.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a valid TUF timestamp signature prove that the update metadata is fresh enough to use?

Buyer evidence still required

  • Timestamp signatures, version and expiry
  • Previously trusted version and update-start clock
  • Client clock provenance and the complete metadata verification outcome

Review inference: Reject a stale signed update view before installing an agent tool. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not treat authentic signed metadata as necessarily current.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The client clock and persisted anti-rollback state have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The client clock and persisted anti-rollback state have not been inspected.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF skipped root versions

Question: Can a TUF client skip unavailable intermediate root versions and trust the latest signed root?

The pinned root-update workflow fetches the next numbered root and requires its version to be exactly one greater than the trusted version. Intermediate roots establish the chain across key changes. A higher version number or a latest-root URL alone does not establish that chain; missing continuity requires investigation rather than bypassing the required verification.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can a TUF client skip unavailable intermediate root versions and trust the latest signed root?

Buyer evidence still required

  • Stored root version and subsequent numbered roots
  • Signature continuity and download results
  • Updater retry limits and recovery policy for unavailable roots

Review inference: Determine whether an offline updater can safely reconnect after several publisher key rotations. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not jump over unverified intermediate roots to make a stale client update.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Availability of the buyer repository’s intermediate roots is unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Availability of the buyer repository’s intermediate roots is unknown.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF terminating delegation boundary

Question: Can a TUF updater fall back to another signer after a terminating delegation has no matching tool target?

TUF terminating delegations stop consideration of later matching trust statements after that role and its descendants have been processed. The pinned workflow does not treat a missing target as permission to seek a more permissive later signer. This restriction preserves the authority boundary deliberately assigned to the terminating delegation.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Can a TUF updater fall back to another signer after a terminating delegation has no matching tool target?

Buyer evidence still required

  • Ordered delegation list and terminating flags
  • Target lookup path and validation results
  • Configured lookup limits and target-not-found outcome

Review inference: Prevent fallback search from bypassing the designated release authority. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not bypass a terminating delegation to find a signer that permits the target.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer lookup implementation has not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer lookup implementation has not been tested.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

TUF unchanged timestamp handling

Question: Does a repeated TUF timestamp version mean a tool update failed or an attack was proven?

The pinned timestamp workflow distinguishes lower versions from equal versions. A lower version is a rollback failure; an equal version is discarded and the update cycle ends normally without an error, because metadata should not have changed under that version. A no-change stop is not evidence of installation or independently proven malicious activity.

Source: The Update Framework Specification (2026-10-08, pinned revision). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Dependency/Advisory Reliance Boundaries

Evidence to request before relying on this claim

Claim to check: Does a repeated TUF timestamp version mean a tool update failed or an attack was proven?

Buyer evidence still required

  • Previous and fetched timestamp versions
  • Updater result and installation state
  • Installation receipt or explicit evidence that no install was attempted

Review inference: Classify an updater’s no-change outcome accurately in an audit. This review does not inspect an updater or authorize software execution.

Suggested review condition: Do not classify an equal-version normal stop as a new installation or a confirmed attack.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer updater outcome and repository behaviour are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The buyer updater outcome and repository behaviour are unobserved.
  • TUF metadata trust does not establish software safety, required permissions, business approval or licence entitlement.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

Required source attribution and distribution notice

External documentation review

Turso MCP: OAuth consent and database operations

Question: Does Turso MCP OAuth mean an agent can only query a database?

The publisher describes organization, database and group management as well as SQL. Dashboard consent selects organization, group and scopes; the scoped token is forwarded to the Turso API for enforcement. OAuth removes manual token copying, but does not by itself make the operation read-only.

Source: Turso MCP server. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Publisher hosted server and client plugin configuration

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Turso operates the hosted server.

Documented by publisher. Turso MCP server

Purpose

Manage selected Cloud resources and run SQL.

Documented by publisher. Turso MCP server

Read capability

Permitted resource metadata and query results.

Documented by publisher. Turso MCP server

Write capability

Database/group management and authorized SQL changes.

Documented by publisher. Turso MCP server

Authentication

OAuth with PKCE and dashboard consent.

Documented by publisher. Turso MCP server

Permission surface

Organization binding, role and scopes enforced by the API.

Documented by publisher. Turso MCP server

Data leaving the environment

Requests and returned database content reach the service and client.

Review inference. Turso MCP server

Failure modes to consider

Wrong consent scope or assumed read-only access can broaden effects.

Review inference. Turso MCP server

Unknowns and applicability

Actual consent, grants, SQL rights and usage costs are unverified.

Not established

Suggested refusal or clarification condition

Require action and spending authority before changing cloud data.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Consent model, API enforcement and exposed operations.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the scoped-identity evidence used for cloud database approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Twilio Docs MCP: API discovery without account execution

Question: Can the Twilio documentation MCP send a message or read my account?

This documented variant searches public specifications and retrieves documentation. It requires no account authentication and does not execute Twilio API calls. It also defaults to the latest available API version. Confirm the intended version; do not treat documentation retrieval as proof of an account action.

Source: Twilio documentation MCP scope. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted public documentation MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Twilio operates the documentation endpoint.

Documented by publisher. Twilio documentation MCP scope

Purpose

Search public API information and retrieve schemas.

Documented by publisher. Twilio documentation MCP scope

Read capability

Public documentation and specifications.

Documented by publisher. Twilio documentation MCP scope

Write capability

No account API execution in the reviewed variant.

Documented by publisher. Twilio documentation MCP scope

Authentication

No Twilio account authentication required.

Documented by publisher. Twilio documentation MCP scope

Permission surface

Public documentation access; no account credential grant.

Documented by publisher. Twilio documentation MCP scope

Data leaving the environment

Search terms go to the hosted documentation service.

Review inference. Twilio documentation MCP scope

Failure modes to consider

A latest-version result may not fit an older integration.

Review inference. Twilio documentation MCP scope

Unknowns and applicability

Search completeness and buyer integration compatibility are untested.

Not established

Suggested refusal or clarification condition

Do not report a message sent or account inspected from a documentation result.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Beta status, version defaults and introduction of authenticated execution variants.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save which API version and documentation supported an integration decision without implying execution.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Twilio: Queue, delivery and read outcomes differ

Question: Does a queued or delivered Twilio message prove that a customer read it?

Twilio distinguishes creation, sending, delivery and channel-dependent read receipts. Status callbacks can report delivery failures and error codes. Read events depend on channel support; a queued message or a delivery status alone is not a universal read confirmation.

Source: Twilio: Track outbound message status. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a queued or delivered Twilio message prove that a customer read it?

Buyer evidence still required

  • Message identity, channel and initial status.
  • Correlated status callbacks and error information.
  • Whether that channel provides a read event and whether one was observed.

Suggested review condition: Report only the observed delivery stage; do not infer reading or repeat a send solely because its outcome is uncertain.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Message identity, channel, callbacks and required proof of communication.

Optional saved evidence: Save the exact communication status supporting an operational claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Twilio: Restricted keys still need an action review

Question: Does a restricted Twilio API key make an agent communication task read-only?

Twilio Restricted API keys select permissions that map to endpoint actions. A restricted key can still permit creating calls or other state-changing operations. The feature also has SDK-token limitations. Review the actual permission mapping and task authority instead of treating the word restricted as a read-only guarantee.

Source: Twilio restricted API key endpoint permissions and SDK limits. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Any restricted API key is safe to use for read-only communication analysis.

Buyer evidence still required

  • Non-secret key type and permission inventory
  • Mapping from approved task to granted endpoint actions
  • Evidence of task approval and the intended server or client-SDK integration

Suggested review condition: Require approved state-changing actions; do not infer a spending limit or read-only access from the key label.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck permission changes, endpoint requirements and integration type.

Optional saved evidence: Save the endpoint-action review behind granting a communication agent credentials.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

UCP advertised versus active capabilities

Question: Does a capability advertised in a UCP profile become active for every checkout operation?

UCP v2026-08-25 selects response capabilities from the negotiated session intersection and those relevant to the operation type. An extension must relate to a relevant root capability. Profile advertisement therefore does not establish that every capability or merchant extension is active in the current checkout, or that the buyer authorised its use.

Source: Overview - Universal Commerce Protocol (UCP). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a capability advertised in a UCP profile become active for every checkout operation?

Buyer evidence still required

  • Both profiles and negotiated versions
  • Current response capabilities and operation type
  • Buyer authority for the proposed extension-dependent action

Review inference: Check the negotiated response and buyer scope before relying on an advertised extension.

Suggested review condition: Do not use an unnegotiated or irrelevant capability as evidence of an authorised operation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual merchant implementation, session negotiation and buyer consent have not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid invoking commerce features that were never mutually selected.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Capability discovery as permission to spend or execute
  • The actual merchant implementation, session negotiation and buyer consent have not been tested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

UCP authentication and profile identity

Question: Does UCP require one universal authentication scheme for every merchant endpoint?

UCP v2026-08-25 supports API keys, OAuth, mutual TLS and HTTP Message Signatures. Regardless of mechanism, the authenticated identity must be consistent with the advertised UCP-Agent profile; business-to-platform webhooks must be signed. A discoverable profile therefore does not remove identity-binding requirements or prove a particular deployment uses the expected authentication method.

Source: Overview - Universal Commerce Protocol (UCP). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does UCP require one universal authentication scheme for every merchant endpoint?

Buyer evidence still required

  • Endpoint authentication mechanism and validated principal
  • UCP-Agent profile and authorised representation binding
  • Required message signatures and verification evidence

Review inference: Check the mechanism and principal-to-profile binding for the actual endpoint before relying on its capability declaration.

Suggested review condition: Do not accept a profile advertisement as authenticated identity without the applicable binding checks.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The merchant configuration and successful verification of a real request are not established here.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid trusting capability metadata from a mismatched or impersonated principal.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Profile discovery as permissionless access to private merchant operations
  • The merchant configuration and successful verification of a real request are not established here.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

UCP cached profiles and version revalidation

Question: Can an agent rely indefinitely on a cached UCP profile because its dated version is unchanged?

UCP v2026-08-25 allows approved amendments to a supported release. Runtime consumers should follow HTTP caching semantics and revalidate after max-age expires. UCP-defined capabilities must match their profile release version, with mismatched entries rejected. A dated version string alone therefore does not prove that a cached artifact remains current or internally consistent.

Source: Overview - Universal Commerce Protocol (UCP). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent rely indefinitely on a cached UCP profile because its dated version is unchanged?

Buyer evidence still required

  • Cached profile body, version and capture time
  • Cache-Control metadata and revalidation result
  • Capability versions and any publisher change notices

Review inference: Retain the captured profile version and content identity, then revalidate according to its cache policy before relying on current capabilities.

Suggested review condition: Do not activate mismatched entries or assume indefinite freshness from an unchanged release date.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether an amendment affects the buyer integration requires current content comparison and compatibility review.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent stale discovery from authorising incompatible commerce operations.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A date label as an immutable content hash or deployment assurance
  • Whether an amendment affects the buyer integration requires current content comparison and compatibility review.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

UCP checkout updates and final purchase terms

Question: Does the initial UCP checkout response freeze the terms an agent will later commit to purchase?

UCP v2026-08-25 permits Update Checkout to replace checkout state with updated inputs before accepted completion. Complete Checkout is the final placement operation when the user has committed to the chosen items. Once completion is accepted and in progress, updates are not permitted. An earlier cart response is therefore not a substitute for the current checkout terms.

Source: Overview - Universal Commerce Protocol (UCP). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does the initial UCP checkout response freeze the terms an agent will later commit to purchase?

Buyer evidence still required

  • Initial and current checkout revisions, items and totals
  • Active discount and request constraints
  • Buyer approval bound to the final purchase terms

Review inference: Compare current items, totals and any discount changes with the buyer approval before the final placement operation.

Suggested review condition: Do not complete a purchase when material changes cannot be reconciled with current approval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Whether a particular change requires renewed consent depends on the buyer authority and active protocol extensions.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent an agent committing changed commercial terms without a defensible approval link.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A universal legal consent rule or a guarantee that prices never change
  • Whether a particular change requires renewed consent depends on the buyer authority and active protocol extensions.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

UCP order confirmation and fulfilment evidence

Question: Does a confirmed UCP order prove that the purchased entitlement or goods were delivered?

UCP orders represent confirmed transactions following checkout. The order model separately tracks line-item quantities, fulfilment expectations and fulfilment events as the order progresses. Placing the order creates its initial representation; subsequent events update its state. An order identifier or expected delivery grouping therefore does not by itself establish completed fulfilment.

Source: Overview - Universal Commerce Protocol (UCP). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a confirmed UCP order prove that the purchased entitlement or goods were delivered?

Buyer evidence still required

  • Order and checkout identities with purchased items
  • Fulfilled quantities and relevant outcome events
  • Application-specific entitlement or delivery receipt

Review inference: Link the ordered item and quantity to actual fulfilment evidence before marking the buyer task complete.

Suggested review condition: Do not report delivery from order confirmation or a fulfilment expectation alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual physical delivery or secure software retrieval needs evidence outside the initial confirmation.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Keep procurement completion separate from the receipt of the purchased deliverable.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Provider order data independently proving receipt by the buyer
  • Actual physical delivery or secure software retrieval needs evidence outside the initial confirmation.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

UCP payment handlers and credential recipients

Question: Can an agent assume every UCP payment handler sends credentials to the same parties?

The UCP payment-handler guide requires each handler specification to identify participants, prerequisites, configuration, acquisition and processing flows. Business, platform and response declarations serve different purposes. The common architecture expects the platform to pass a token or mandate to the business while using the credential provider interface. The handler identity alone does not establish an unchanged credential destination.

Source: Guide - Universal Commerce Protocol (UCP). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an agent assume every UCP payment handler sends credentials to the same parties?

Buyer evidence still required

  • Negotiated handler ID, version and specification
  • Business and credential-provider configuration and endpoints
  • Credential type, acquisition flow and intended recipient

Review inference: Review the selected handler configuration and participants before switching the payment-credential path.

Suggested review condition: Do not send credentials through a changed handler until its actual recipient and scope are established.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The deployed handler and pre-existing provider relationship were not inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent credential disclosure or payment routing to an unintended participant.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • UCP compatibility as certification of credential handling or PCI compliance
  • The deployed handler and pre-existing provider relationship were not inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

UCP readiness versus completed order

Question: Does UCP ready_for_complete establish a completed or paid order?

In UCP v2026-08-25, ready_for_complete means the required information is present and the platform can invoke Complete Checkout. incomplete requires resolution, while complete_in_progress means processing was accepted and must not include an order. completed includes the placed order. Readiness, accepted processing and completed placement are distinct states, not interchangeable payment evidence.

Source: Overview - Universal Commerce Protocol (UCP). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does UCP ready_for_complete establish a completed or paid order?

Buyer evidence still required

  • Current checkout status, messages and outstanding actions
  • Completion request identity and resulting order
  • Separate payment and delivery evidence

Review inference: Inspect the final state and linked payment evidence before treating readiness as a completed purchase.

Suggested review condition: Do not release a payment-required entitlement from readiness or accepted processing alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The merchant payment method and actual order or delivery outcome are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid premature delivery while a commerce workflow is still incomplete.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Readiness as proof of payment authorisation, settlement or delivery
  • The merchant payment method and actual order or delivery outcome are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Unrestricted file access and workspace roots

Question: Does Playwright MCP keep its default workspace and file-URL restrictions after allow-unrestricted-file-access is enabled?

The pinned README says --allow-unrestricted-file-access permits files outside workspace roots and unrestricted file:// navigation. By default the documented file access is restricted to workspace roots, or the working directory when no roots are configured, and file:// navigation is blocked.

Source: Playwright MCP README, v0.0.84. Documentation checked 2026-11-08; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does Playwright MCP keep its default workspace and file-URL restrictions after allow-unrestricted-file-access is enabled?

Buyer evidence still required

  • Exact installed version, provider variant and effective non-secret configuration
  • Relevant pending-call identifiers, declared arguments and decision provenance without secrets
  • Application-owned review policy and independently observed outcomes where needed

Review inference: Do not infer default workspace/file-URL restrictions after this flag is enabled. OS permissions, browser sandboxing and other tools require separate evidence. The existing record concerns browser session identity and origin-filter limits. This distinct flag changes workspace/file-URL handling without establishing broader OS authority. Operational review inference; no deployment outcome was observed.

Suggested review condition: Do not infer default workspace/file-URL restrictions after this flag is enabled. OS permissions, browser sandboxing and other tools require separate evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included. Configuration / --allow-unrestricted-file-access

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer default workspace/file-URL restrictions after this flag is enabled. OS permissions, browser sandboxing and other tools require separate evidence.
  • The flag neither grants OS privileges nor proves every path readable. Default roots do not prove an OS sandbox or constrain unrelated tools.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Upload acknowledgement versus version retrieval readiness

Question: Does an OpenAI skill upload response prove that the new version can already be attached?

The guide says a newly uploaded version can briefly return 404. It instructs callers to retrieve the version with bounded backoff before attachment and use the returned version string.

Source: OpenAI primary documentation: openai skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does an OpenAI skill upload response prove that the new version can already be attached?

Buyer evidence still required

  • upload response
  • version retrieval response
  • bounded retry policy
  • attachment request

Review inference: Does an OpenAI skill upload response prove that the new version can already be attached? Treat upload acceptance and retrieval readiness as separate evidence; do not silently fall back to another version. Upload acknowledgement versus version retrieval readiness. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Treat upload acceptance and retrieval readiness as separate evidence; do not silently fall back to another version.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Wait for an uploaded version

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Treat upload acceptance and retrieval readiness as separate evidence; do not silently fall back to another version.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Usability versus clean scan, warnings and authorised overrides

Question: Does a usable Claude skill prove that it passed scanning without an exception?

The guide says pending or failed scans block use, warning results can remain usable behind a caution notice, and authorised owners or library-managing roles can allow some failed skills.

Source: Anthropic primary documentation: claude skills enterprise. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does a usable Claude skill prove that it passed scanning without an exception?

Buyer evidence still required

  • scan status
  • warning details
  • override actor/role
  • exception rationale and expiry

Review inference: Does a usable Claude skill prove that it passed scanning without an exception? Usability alone does not establish a clean scan; record outcome, warning and any authorised exception separately. Usability versus clean scan, warnings and authorised overrides. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Usability alone does not establish a clean scan; record outcome, warning and any authorised exception separately.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. passes with a warning

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Usability alone does not establish a clean scan; record outcome, warning and any authorised exception separately.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

User command visibility versus autonomous invocation authority

Question: Does user-invocable false prevent Claude from invoking a sensitive skill?

The guide distinguishes disable-model-invocation true, which prevents autonomous invocation, from user-invocable false, which removes user invocation while allowing Claude to invoke the skill.

Source: Anthropic primary documentation: claude code skills. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Does user-invocable false prevent Claude from invoking a sensitive skill?

Buyer evidence still required

  • frontmatter
  • command visibility
  • desired invocation actor
  • separate tool permissions

Review inference: Does user-invocable false prevent Claude from invoking a sensitive skill? Do not confuse command visibility with prohibition of model invocation or downstream tool authority. User command visibility versus autonomous invocation authority. The decision turns on the documented operation and required evidence, not on a different vendor name. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not confuse command visibility with prohibition of model invocation or downstream tool authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Control who invokes a skill

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not confuse command visibility with prohibition of model invocation or downstream tool authority.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

output structure record

VAREXIS Analytical Review Artefact — Scope and Value

Question: What does the Analytical Review artefact give a client?

Public-safe record for the VAREXIS Analytical Review artefact as a governed assessment output.

Claim boundaries
  • legal advice
  • financial advice
  • regulatory advice
  • guaranteed outcome
  • external action approval

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

reliance boundary record

VAREXIS Authority Boundary — Qualify, Bound or Halt

Question: What is VAREXIS authorised to do for a claim or decision?

Public-safe record defining the VAREXIS authority boundary: qualify, bound or halt; do not advise, certify or authorise.

Claim boundaries
  • legal advice
  • regulatory approval
  • certification
  • guaranteed correctness
  • authority to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

admissibility chain record

VAREXIS DCFN / EDR / SVKL Admissibility Chain

Question: How does VAREXIS handle pass, reject, escalate and admissibility states?

Public-safe record for DCFN, EDR and SVKL admissibility logic.

Claim boundaries
  • automated client advice
  • single-node sufficiency
  • unprovenanced reliance
  • unresolved evidence basis
  • certification

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

claim register record

VAREXIS Evidence Posture and Claim Discipline Register

Question: How does VAREXIS classify claims in a review artefact?

Public-safe record for claim posture, disqualifiers and halt discipline in VAREXIS artefacts.

Claim boundaries
  • unconditional correctness
  • claim certification
  • complete evidence sufficiency
  • advice
  • external approval

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

evidence bound output record

VAREXIS Evidence-Bound Output Doctrine

Question: How should VAREXIS outputs state what evidence supports?

Public-safe doctrine record for evidence-bound VAREXIS outputs and constrained determination language.

Claim boundaries
  • proof of truth
  • guaranteed accuracy
  • certified correctness
  • legal enforceability
  • external reliance without recipient responsibility

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

fragmentation normalisation record

VAREXIS Fragmentation and N1 Normalisation Rules

Question: How does VAREXIS preserve meaning while conditioning material?

Public-safe record for fragmentation and normalisation controls in the VAREXIS delivery system.

Claim boundaries
  • semantic inference
  • advice generation
  • truth finding
  • unlogged transformation
  • unbounded extraction

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

disqualifier language record

VAREXIS Overclaim Disqualifier Language

Question: Which words or claims should trigger overclaim caution?

Public-safe record of overclaim/disqualifier language for agentic and human review of VAREXIS outputs.

Claim boundaries
  • unconditional truth
  • risk-free outcome
  • investment-grade claim
  • legal correctness
  • financial accuracy guarantee

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

public assurance record

VAREXIS Public Assurance — AI Usage and Human Oversight

Question: How should VAREXIS explain AI usage and human oversight?

Public-safe record for AI usage and human oversight assurance posture.

Claim boundaries
  • guaranteed correctness
  • certified AI output
  • fully autonomous authority
  • regulatory approval
  • client-specific assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

public assurance record

VAREXIS Public Assurance — Information Handling

Question: What public assurance material should VAREXIS expose about information handling?

Public-safe record for information handling and public assurance posture.

Claim boundaries
  • external certification
  • complete security assurance
  • legal compliance guarantee
  • regulated advice
  • client-specific approval

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

reliance control record

VAREXIS Reliance Control Sheet

Question: What does a Reliance Control Sheet provide?

Public-safe record for Reliance Control Sheet purpose and reliance restrictions.

Claim boundaries
  • external permission
  • legal advice
  • certification
  • guaranteed result
  • unconditional reliance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

delivery spine record

VAREXIS Review Delivery Spine

Question: What is the VAREXIS delivery spine for governed review work?

Public-safe record for the VAREXIS review delivery spine and client-facing reliance posture.

Claim boundaries
  • live automation of every layer
  • system certification
  • client advice
  • external action authority
  • unbounded evidence acceptance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

External documentation review

Vault account searches and shared-drive coverage

Question: Does selecting custodian accounts in a Vault Drive search automatically include all relevant shared-drive files?

Vault distinguishes account searches from searches of selected shared drives. Account search coverage depends on sharing and shared-drive inclusion settings. The API documents sharedDrivesOption with explicit exclusion, conditional inclusion and inclusion modes; it supersedes the older includeSharedDrives and includeTeamDrives fields. Selecting an account alone does not describe complete shared-drive scope.

Source: Use Vault to search Google Drive, Meet & Sites | Google Vault | Google Workspace Help. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does selecting custodian accounts in a Vault Drive search automatically include all relevant shared-drive files?

Buyer evidence still required

  • Custodian accounts, shared drives and membership evidence
  • Query sharedDrivesOption and supported API version
  • Expected file scope and search/export reconciliation

Review inference: Record the actual search inclusion options and drive memberships with the export evidence.

Suggested review condition: Refuse complete shared-drive coverage when only an account list is evidenced.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual membership, sharing state and file results are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Close shared-drive scope gaps before accepting a custodian export as complete.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • All shared-drive coverage from custodian selection alone
  • Actual membership, sharing state and file results are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault export download window

Question: Can a Google Vault export remain a downloadable evidence archive indefinitely after it is created?

The Vault exports guide makes exports available for 15 days after creation, after which they are deleted and no longer accessible. Listing an export or recording its identifier does not preserve the downloadable files beyond that window. Creating, downloading and independently retaining the export are separate steps.

Source: Manage exports | Google Vault | Google for Developers. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Google Vault export remain a downloadable evidence archive indefinitely after it is created?

Buyer evidence still required

  • Export ID, creation time and current status
  • Complete downloaded file inventory and hashes
  • Approved archive location and retention requirements

Review inference: Track the creation-based deadline and preserve a verified copy within the buyer’s authorised archive.

Suggested review condition: Do not accept an export identifier as durable evidence when the files were not preserved before expiry.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Download completeness and the buyer’s archive retention are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Prevent a time-limited export from being mistaken for a durable exit archive.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Indefinite provider-hosted storage of Vault exports
  • Download completeness and the buyer’s archive retention are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault historical content and current metadata

Question: Does a Vault version-date search reproduce every historical Drive revision and its metadata exactly as they existed then?

Vault searches a file’s current version even when a version date is supplied. For supported Google file types, preview and export use the last version saved before midnight on that date, but properties such as title, sharing and modification metadata remain current. Comment inclusion has separate rules. This is not an exact replay of every historical property.

Source: Use Vault to search Google Drive, Meet & Sites | Google Vault | Google Workspace Help. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Vault version-date search reproduce every historical Drive revision and its metadata exactly as they existed then?

Buyer evidence still required

  • Supported file type, version date and query time zone
  • Required content revisions and metadata fields
  • Exported content, metadata and comment inclusion rules

Review inference: Define which content and metadata fields must be historical, then reconcile them instead of treating a version date as a complete forensic snapshot.

Suggested review condition: Reject an exact historical-state claim where current metadata or unsupported revision coverage is unaccounted for.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The existence of every required revision and external edits is not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid relying on mixed-time export evidence when reconstructing a document’s historical state.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Complete point-in-time metadata and comment reconstruction
  • The existence of every required revision and external edits is not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault leases: Static KV values are not dynamic credentials

Question: Does a Vault lease policy prove that a copied static password expires?

Vault documents leases for dynamic secrets and service tokens, while the key/value backend does not issue secret leases even when a duration is returned. A static value stored in Vault therefore needs its own credential-lifecycle evidence. Storage in a lease-capable product is not evidence of automatic downstream expiry.

Source: Vault leases and static KV exception. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Every value stored in Vault automatically expires or is revoked through a lease.

Buyer evidence still required

  • Secrets engine and whether the value is dynamic or static KV.
  • Actual lease identifier and revocation mechanism where applicable.
  • Downstream rotation or invalidation evidence for static credentials.

Suggested review condition: Do not promise expiry of a static credential solely from Vault storage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Engine changes, credential type and downstream revocation process.

Optional saved evidence: Preserve the engine and lifecycle distinction behind a credential-expiry assessment.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault matter closure and export loss

Question: Can a Google Vault matter be closed while preserving its active holds and existing downloadable exports?

Vault requires all holds to be deleted before a matter can be closed. Closing retains saved queries and audit data but immediately deletes export files. Reopening preserves the queries and audit data; holds and exports must be recreated. Matter closure is therefore a different operation from merely pausing an investigation.

Source: Create & manage matters | Google Vault | Google Workspace Help. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Google Vault matter be closed while preserving its active holds and existing downloadable exports?

Buyer evidence still required

  • Matter identity and all active holds
  • Authority and prerequisites for releasing each hold
  • Required exports, downloads and audit preservation

Review inference: Confirm authorised hold release and preserve required export deliverables before closing the matter.

Suggested review condition: Do not close an investigation on the assumption that reopening automatically restores its holds or export files.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The continuing legal need for a hold and the completeness of downloaded exports are not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Avoid losing export deliverables or preservation controls during an investigation handover.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Restoration of previous holds and export files through reopening
  • The continuing legal need for a hold and the completeness of downloaded exports are not established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault MCP: Secret disclosure and beta-use boundaries

Question: Does keeping secrets in Vault keep them out of an AI client?

Not when an authorised MCP query returns them. The Vault MCP page explicitly warns that secret data can reach clients and models, and describes both read and write operations. It labels the feature beta and discourages production deployment. This review does not establish a buyer-specific access policy.

Source: Vault MCP tools and authentication. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Vault MCP beta for KV and PKI operations

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

HashiCorp documents the Vault MCP server.

Documented by publisher. Vault MCP tools and authentication

Purpose

KV secret and PKI management through an AI client.

Documented by publisher. Vault MCP tools and authentication

Read capability

Secret values, mounts and PKI information.

Documented by publisher. Vault MCP tools and authentication

Write capability

Secret and mount changes, certificate issuance and PKI-role operations.

Documented by publisher. Vault MCP tools and authentication

Authentication

The overview does not specify the complete credential setup.

Not established. Vault MCP tools and authentication

Permission surface

The overview is insufficient to establish effective path-level permissions.

Not established. Vault MCP tools and authentication

Data leaving the environment

Returned secret values may enter client or model context.

Review inference. Vault MCP tools and authentication

Failure modes to consider

A storage-security claim can obscure disclosure through authorised reads.

Review inference. Vault MCP tools and authentication

Unknowns and applicability

Credential policy, mounted engines and client handling are unverified.

Not established

Suggested refusal or clarification condition

Require credential and client-handling evidence before relying on secret isolation.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Beta status, supported engines and authentication documentation.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the documented disclosure and beta limitations when assessing a secrets connector.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault retention expiry and service-specific removal

Question: Does expiry of a Google Vault retention rule prove immediate removal from every supported service and from Vault?

Vault documents different post-expiry behavior by service. Drive items can take up to 15 days to leave Drive and become unavailable to Vault once removed without a protecting rule or hold. Gmail and Gemini messages can remain searchable in Vault for roughly 30 more days. A single policy timestamp is not a uniform purge receipt.

Source: How retention works | Google Vault | Google Workspace Help. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does expiry of a Google Vault retention rule prove immediate removal from every supported service and from Vault?

Buyer evidence still required

  • Service, item identity and applicable retention/hold settings
  • Retention expiry and actual removal observations
  • Separate administrator recovery and archive requirements

Review inference: Use the service-specific removal state, outstanding holds and retrieval evidence to assess a declared exit boundary.

Suggested review condition: Do not report immediate universal purge from the policy expiry timestamp alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual service cleanup progress and recoverable copies have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Set realistic exit checks around each service’s documented removal process.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Identical or instantaneous purge timing across Workspace services
  • Actual service cleanup progress and recoverable copies have not been inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault wrapping: Delivery-token expiry is not secret expiry

Question: Does a short-lived Vault wrapping token make the underlying secret expire at the same time?

Response wrapping delivers a single-use token with its own lifetime instead of the original response. That lifetime is separate from the wrapped secret. Creation-path inspection and unwrap status help review delivery, but failed unwrapping alone does not prove interception; expiry is another possible cause.

Source: Vault response wrapping. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A wrapping token's lifetime is the lifetime of the wrapped credential.

Buyer evidence still required

  • Wrapping creation path and expiry metadata.
  • Underlying secret or lease lifecycle.
  • Authorized unwrap outcome.

Suggested review condition: Keep delivery-token and underlying-credential lifetime claims separate.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Wrapping metadata, origin, unwrap state and secret lifecycle

Optional saved evidence: Retain separate delivery and credential-lifetime evidence for a secret handoff.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault: Audit availability, coverage and hashed values

Question: Does a working Vault server prove its secret-access audit trail is complete?

Vault distinguishes operational logs from audit devices, which must be enabled on a new cluster. With auditing enabled, a request requires a successful write to at least one enabled device; one device need not contain the whole history. Documented endpoint exceptions and hashed values also limit interpretation.

Source: Vault audit device enablement, availability and hashing boundaries. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Operational server logs alone prove complete secret-access auditing.

Buyer evidence still required

  • Enabled audit-device configuration and dates
  • Combined device records and evidence of collection/retention
  • Relevant endpoint exceptions and hashed-field interpretation

Suggested review condition: Do not certify a complete access history from process logs, a single device or uninterpreted hashes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck device changes, availability, exceptions and version-specific logging behaviour.

Optional saved evidence: Preserve the evidence questions behind a secrets-service audit claim.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault: Forced lease removal and residual access

Question: Does a successful Vault force-revoke establish that the backend credential can no longer be used?

Vault force revocation ignores errors from the secrets backend. Removing the lease entry therefore does not establish that the issued credential was disabled in the target system. The ordinary revoke API also distinguishes queued processing from synchronous completion.

Source: Vault: /sys/leases. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Does a successful Vault force-revoke establish that the backend credential can no longer be used?

Buyer evidence still required

  • Lease identity, backend and revocation operation, including force and sync options.
  • Backend cleanup result and any unresolved revocation errors.
  • Dated target-system evidence for the issued credential and remaining sessions.

Suggested review condition: Decline a completed-offboarding claim based only on forced lease removal; obtain backend revocation evidence and resolve residual-access uncertainty.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Lease identity, backend and revocation operation, including force and sync options. Backend cleanup result and any unresolved revocation errors. Dated target-system evidence for the issued credential and remaining sessions.

Optional saved evidence: Offboarding an agent or closing a credential incident requires evidence from the credential issuer, especially after a failed backend cleanup.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Successful removal of the underlying credential or termination of existing backend sessions
  • Verified buyer configuration, effective access or actual event completeness
  • Runtime enforcement, certification or approval to act

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vault: Orphan tokens survive a former parent

Question: Does revoking a Vault parent token revoke orphan credentials created from that workflow?

Ordinary child tokens and their leases are revoked with their parent. Orphan tokens have no parent and form their own trees. The revoke-orphan operation removes a token while orphaning its immediate children instead of revoking those children.

Source: Tokens | Vault | HashiCorp Developer. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Does revoking a Vault parent token revoke orphan credentials created from that workflow?

Buyer evidence still required

  • Token accessors and creation methods.
  • Parent/orphan relationships.
  • Revocation operation and remaining token evidence.

Suggested review condition: Do not close revocation from one parent result when orphan tokens or revoke-orphan use remain unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Token accessors and creation methods. Parent/orphan relationships. Revocation operation and remaining token evidence.

Optional saved evidence: Reconstruct credential lineage before declaring an agent access tree closed.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Reading or revoking customer secrets, actual backend access or discovery of unknown tokens
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vector remap: Failed redaction and original events

Question: Can a Vector remap error send the original sensitive event downstream?

By default, a processing error forwards the original unmodified event because drop_on_error is false. Explicit aborts have a separate drop_on_abort setting. Rerouted dropped events can also carry original data. Review normal, error and dropped outputs separately before relying on a remap transformation as a disclosure barrier.

Source: Vector: Remap transform. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A remap redaction program prevents raw data from leaving on every path.

Buyer evidence still required

  • Effective drop_on_error and drop_on_abort settings.
  • Rerouted-output destinations and access controls.
  • Failure-case output for representative inputs.

Suggested review condition: Do not approve a no-raw-data claim without reviewing error and reroute paths.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Vector revision, remap configuration, failure inputs and every output destination.

Optional saved evidence: Preserve the failure-path questions behind a log-processing purchase.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Velero backup API-version compatibility

Question: Can Velero restore a resource when the target cluster lacks the API version used in the backup?

The v1.18.4 guide backs up resources using the source Kubernetes API server preferred version for each group/resource. That same API group/version must exist on the target for restoration; it need not be the target preferred version. A target cluster exposing a different version of the resource does not by itself establish compatibility.

Source: Velero v1.18.4 — how-velero-works. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can Velero restore a resource when the target cluster lacks the API version used in the backup?

Buyer evidence still required

  • Source preferred API versions at backup
  • Resource versions present in the archive
  • Target discovery and restore results

Review inference: Check migration feasibility against actual source and target API versions. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse version-compatible restoration when the backed-up API endpoint is unavailable.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Conversion behaviour or a buyer migration was not independently tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Conversion behaviour or a buyer migration was not independently tested.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero backup hooks and consistency evidence

Question: Does a Velero backup completing establish that its pre-backup consistency hook succeeded?

The v1.18.4 hook guide allows Fail or Continue handling for non-zero hook exit codes, with Fail as the default, and treats a hook exceeding its timeout as an error. The documented default timeout is 30 seconds. A backup configured to continue after a hook error needs the hook result reconciled separately before it can support an application-consistency claim.

Source: Velero v1.18.4 — backup-hooks. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a Velero backup completing establish that its pre-backup consistency hook succeeded?

Buyer evidence still required

  • Hook command, target container and error policy
  • Hook exit status, duration and backup log
  • Application-specific consistency acceptance evidence

Review inference: Check that the intended quiescence or preparation step actually completed. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse consistency assurance from backup completion without successful required-hook evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The hook command effect and application state were not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The hook command effect and application state were not observed.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero backup records and object storage

Question: Does deleting a Kubernetes Velero Backup object establish removal of its object-storage archive?

The v1.18.4 guide treats object storage as the source of truth and synchronises properly formatted stored backups back into missing Kubernetes Backup resources. A Completed resource missing its archive is removed from Kubernetes; Failed and PartiallyFailed resources are not removed by that sync rule. Resource presence or absence alone therefore does not establish the corresponding archive disposition.

Source: Velero v1.18.4 — how-velero-works. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a Kubernetes Velero Backup object establish removal of its object-storage archive?

Buyer evidence still required

  • Kubernetes backup resource state and identifiers
  • Object-storage archive inventory
  • Controller sync and authorised deletion records

Review inference: Require storage evidence when reconciling backup inventories or offboarding. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse archive deletion based solely on removal of its Kubernetes resource.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Underlying archive retention and physical erasure remain unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Underlying archive retention and physical erasure remain unobserved.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero backup repository password changes

Question: Can changing the Velero repository credential secret after the first backup preserve access to earlier backups automatically?

The v1.18.4 FSB guide says the backup repository is created on the first backup targeting it and the custom repository password should be set before that operation. Changing the secret password after repository creation prevents Velero from connecting to older backups. Editing the Kubernetes secret is therefore not documented as an automatic re-encryption or password migration of existing archives.

Source: Velero v1.18.4 — file-system-backup. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can changing the Velero repository credential secret after the first backup preserve access to earlier backups automatically?

Buyer evidence still required

  • Repository creation and backup history
  • Credential-change sequence and protected recovery material
  • Connectivity and restore validation for retained archives

Review inference: Plan credential changes without silently losing recovery access to retained backups. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse transparent rotation or erasure claims based only on changing the credential secret.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No password, key material or buyer restore was accessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No password, key material or buyer restore was accessed.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero backup TTL and deletion failures

Question: Does reaching a Velero backup TTL prove that its backup files and snapshots were deleted?

The v1.18.4 guide applies expiry through the garbage-collection controller, whose documented default reconciliation interval is one hour. Expiry targets the backup resource, object-storage backup file, PV snapshots and associated restores. Failed deletion can be labelled with reasons including an unavailable or read-only backup storage location. A passed TTL alone does not establish successful removal of those objects.

Source: Velero v1.18.4 — how-velero-works. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does reaching a Velero backup TTL prove that its backup files and snapshots were deleted?

Buyer evidence still required

  • Backup expiry and controller reconciliation schedule
  • Deletion results and gc-failure labels
  • Object-store, snapshot and restore inventories

Review inference: Reconcile retention deadlines with actual garbage-collection outcomes. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse completed retention deletion solely because the TTL has elapsed.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Provider residual copies and successful deletion of a buyer backup were not verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Provider residual copies and successful deletion of a buyer backup were not verified.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero existing resources and volume data

Question: Does Velero existing-resource-policy update restore the data in an existing persistent volume?

The v1.18.4 restore guide limits existing-resource update to Kubernetes resource data such as its spec. It explicitly says PVC update does not restore or overwrite the PV data. Updates are best effort; a failed patch can produce a warning and fall back to non-destructive handling without failing the restore. Restore labels or a completed workflow therefore do not establish that volume contents were recovered.

Source: Velero v1.18.4 — restore-reference. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Velero existing-resource-policy update restore the data in an existing persistent volume?

Buyer evidence still required

  • Restore policy and existing PVC/PV inventory
  • Patch warnings and per-resource outcomes
  • Volume restore mechanism and content validation

Review inference: Separate resource-definition reconciliation from volume-content recovery. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse volume-recovery approval from resource update or restore labels alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual volume recovery and application consistency are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual volume recovery and application consistency are unknown.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero live-filesystem consistency

Question: Does Velero File System Backup capture all files at a single atomic point in time?

The v1.18.4 File System Backup guide describes beta-quality support that reads the live filesystem rather than taking a single storage snapshot. Files are consequently not captured at the same point in time. Suitability for a stateful application depends on its consistency controls and recovery validation, not only a successful transfer of files.

Source: Velero v1.18.4 — file-system-backup. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Velero File System Backup capture all files at a single atomic point in time?

Buyer evidence still required

  • Application write and quiescence conditions
  • Volume backup method and per-volume results
  • Application-level recovery validation

Review inference: Determine whether a backup is coherent enough for the intended application recovery. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse an atomic or application-consistent snapshot claim from File System Backup success alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Application consistency and recoverability were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Application consistency and recoverability were not tested.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero restored status fields

Question: Does Velero restore the status of every Kubernetes object along with its spec?

The v1.18.4 guide says status is removed by default before object restoration because controllers typically reconcile it. Selected resource types or object annotations can request status restoration, which requires a separate update after creation. A restored spec therefore cannot stand in for retained status history, and restored historical status alone does not establish current runtime health.

Source: Velero v1.18.4 — restore-reference. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Velero restore the status of every Kubernetes object along with its spec?

Buyer evidence still required

  • Restore status inclusion/exclusion settings and annotations
  • Source object status and post-creation update result
  • Current controller reconciliation and health evidence

Review inference: Distinguish reconstructed configuration, preserved status and newly observed health. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse historical-status completeness or current health from spec restoration alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Buyer controller behaviour and actual health remain unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Buyer controller behaviour and actual health remain unknown.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero ServiceAccount merge exceptions

Question: Does Velero default non-destructive restore leave every existing ServiceAccount unchanged?

The v1.18.4 guide documents ServiceAccounts as an exception to default existing-resource skipping. Velero attempts to merge backed-up fields into an existing ServiceAccount, appending Secrets and ImagePullSecrets and adding absent labels and annotations while retaining existing ones. Default non-destructive restore is therefore not a promise that every existing identity configuration is untouched.

Source: Velero v1.18.4 — restore-reference. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does Velero default non-destructive restore leave every existing ServiceAccount unchanged?

Buyer evidence still required

  • Source and destination ServiceAccount definitions
  • Secret references and pre/post restore comparison
  • Effective access review and restore outcomes

Review inference: Review restored identity references before approving access equivalence. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse an unchanged-identity assertion solely from the default restore policy.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Referenced secret contents and effective authorisation were not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Referenced secret contents and effective authorisation were not assessed.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Velero volume backup mechanism coverage

Question: Does enabling Velero File System Backup also produce a native snapshot of the same volume?

The v1.18.4 guide states that File System Backup and native/CSI snapshots are mutually exclusive for the same volume. When FSB runs, the snapshot is skipped; opting out of FSB allows a snapshot attempt if configured. Neither a global feature setting nor an opt-out establishes that both mechanisms completed, so recovery coverage must be mapped per volume to its actual backup result.

Source: Velero v1.18.4 — file-system-backup. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does enabling Velero File System Backup also produce a native snapshot of the same volume?

Buyer evidence still required

  • Per-volume FSB opt-in or opt-out settings
  • Snapshot configuration and attempt outcomes
  • Actual backup artifact map for each volume

Review inference: Avoid counting an expected snapshot as a second recovery copy when FSB replaced it. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse dual-copy coverage without separate evidence of the actual artifacts.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer volume inventory or backup artifact was inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No buyer volume inventory or backup artifact was inspected.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Vercel audit evidence: Entitlement, exporter role and event scope

Question: Does having Vercel deployment logs mean our plan provides administrative audit evidence?

Vercel documents Audit Logs as an Enterprise feature accessible to team owners. Its event catalogue and export or streaming path need their own review. Deployment output is not equivalent to an administrative activity trail, and the availability of an audit feature does not demonstrate successful capture in the buyer account.

Source: Vercel Enterprise audit-log access. Documentation checked 2026-10-14; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Our existing deployment logs are a complete administrative audit trail.

Buyer evidence still required

  • Applicable Enterprise entitlement and owner access
  • The event types required for the review
  • A dated export or verified delivery to the intended archive

Suggested review condition: Request audit-specific evidence where the supplied material is only build or runtime logging.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck audit entitlements, event coverage and migration of streaming integrations.

Optional saved evidence: Preserve the evidence gap between operational logs and an administrative audit requirement.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vercel MCP: Team access and deployment authority

Question: What should an agent verify before using a deployment connector to inspect or change a team's project?

Vercel documents a separate sign-in and team-authorization step after adding its MCP server. Existing Vercel permissions still apply. Tools cover project and deployment inspection as well as operational changes, so a diagnosis request should not silently become a deployment or account change. Review the target team, project and environment, and the handling of returned logs.

Source: Vercel MCP authorization and security. Documentation checked 2026-10-11; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Vercel's hosted account-management MCP, not an arbitrary MCP application deployed on Vercel.

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, feature entitlement and effective configuration are not verified.

Publisher and operator

Vercel operates its hosted MCP service.

Documented by publisher. Vercel MCP authorization and security

Purpose

Inspect and manage Vercel projects, deployments and other account resources.

Documented by publisher. Vercel MCP team access and tool categories

Read capability

Team/project information, deployment status and runtime logs are documented tool areas.

Documented by publisher. Vercel MCP team access and tool categories

Write capability

The tool catalog includes deployment, project and account-management operations.

Documented by publisher. Vercel MCP team access and tool categories

Authentication

Clients use a sign-in/OAuth flow and team authorization.

Documented by publisher. Vercel MCP authorization and security; Vercel MCP team access and tool categories

Permission surface

Adding the server does not complete authorization; the owning team must be granted and existing rights apply.

Documented by publisher. Vercel MCP team access and tool categories

Data leaving the environment

Operational context is returned to the AI client and may be shared onward by other tools.

Review inference. Vercel MCP authorization and security

Failure modes to consider

Wrong team or environment, sensitive log disclosure, or treating a missing team grant as an absent project.

Review inference. Vercel MCP authorization and security; Vercel MCP team access and tool categories

Unknowns and applicability

Authorized teams, effective role, target environment and client retention/approval settings.

Not established

Suggested refusal or clarification condition

During diagnosis, stop before deployment or account changes until the exact target and action are authorized.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck granted teams, project role and deployment target whenever the connection or task changes.

Record history: 2026-10-11 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve team, environment and log-disclosure checks used to approve a deployment assistant.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent tool execution or security testing
  • Vendor certification, guaranteed safety or no-training assurance

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vercel spend pauses: Production scope and excluded usage

Question: Does Vercel Spend Management stop every charge as soon as the spend amount is reached?

A spend amount alone does not stop usage; production pausing must be enabled. Checks occur periodically, so usage can continue after the amount is crossed. The guide also excludes AI Gateway API-key and v0 usage from production pausing. Inspect scope and timing before treating it as a universal spending ceiling.

Source: Vercel spend management and pause behaviour. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Production pausing creates an instant ceiling for all team usage.

Buyer evidence still required

  • Spend amount and enabled pause action.
  • Inventory of production, AI Gateway and other billed usage.
  • Observed pause timing and the separate controls for excluded usage.

Suggested review condition: Do not use production pausing as proof that all billable activity stops.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Pause setting, team usage categories, check timing and resumption

Optional saved evidence: Preserve which usage the configured pause affects and what remains outside it.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Vertex AI: Retention depends on enabled features

Question: Does a zero-retention objective apply automatically to every Vertex AI grounding and session feature?

The captured Google documentation describes feature-specific storage: Search grounding logs can persist for up to three days, Maps grounding data for 30 days, and optional Live API session resumption for up to 24 hours. These settings and service terms must be reviewed separately from a general model retention claim.

Source: Vertex AI zero data retention. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a zero-retention objective apply automatically to every Vertex AI grounding and session feature?

Buyer evidence still required

  • The exact model API and enabled grounding features.
  • Session resumption and request-response logging settings.
  • The applicable current service terms and documented exceptions.

Suggested review condition: Do not approve zero retention while an enabled feature requires storage or its retention terms are unresolved.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. The exact model API and enabled grounding features. Session resumption and request-response logging settings. The applicable current service terms and documented exceptions.

Optional saved evidence: An AI buyer needs to decide whether selected grounding and session features fit the approved data-custody boundary.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • All Google AI features, buyer-specific erasure or equivalence to a contractual guarantee
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

VPC Service Controls: A perimeter is separate from IAM

Question: Does a Google Cloud service perimeter replace resource permissions?

VPC Service Controls supplies context-based perimeter checks in addition to IAM. Ingress/egress rules and supported-service scope determine which paths it covers. A perimeter configuration does not establish least-privilege identities or coverage for every service operation.

Source: Google Cloud VPC Service Controls overview. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A service perimeter replaces identity authorization for all services.

Buyer evidence still required

  • Restricted services and resource inventory.
  • Ingress, egress and access-level rules.
  • Effective IAM permissions.

Suggested review condition: Require both identity and perimeter evidence before approving data isolation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Perimeter resources, supported services, access rules and IAM

Optional saved evidence: Preserve two separate control layers in a cloud data-sharing decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

vss method boundary record

VSS Observation → Enabled Behaviour → Consequence

Question: How should VSS describe a security surface finding?

Public-safe record for VSS-style passive surface findings and bounded consequence language.

Claim boundaries
  • exploitability proof
  • penetration-test result
  • security certification
  • complete vulnerability coverage
  • permission to attack

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Human record · Request an answer or receipt

External documentation review

W3C tracing: Correlation identifiers are not authenticated lineage

Question: Does a matching traceparent identifier prove that two records belong to an authentic agent action chain?

Trace Context standardizes cross-service correlation. Its security discussion warns that callers can forge trace-ID collisions and manipulate recording behavior. VAREXIS therefore treats correlation headers as supplied context that needs independent identity and event evidence, not authenticated action lineage.

Source: Trace Context. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Does a matching traceparent identifier prove that two records belong to an authentic agent action chain?

Buyer evidence still required

  • Header origin and trust boundary.
  • Authenticated actor and operation evidence.
  • Receiver parsing and collision-handling policy.

Suggested review condition: Do not establish actor identity or genuine causal lineage from matching trace identifiers alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Header origin and trust boundary. Authenticated actor and operation evidence. Receiver parsing and collision-handling policy.

Optional saved evidence: Keep trace correlation separate from proof of who performed a sensitive action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Cryptographic authentication, complete recording or an actual security assessment
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Weaviate absent-object delete acknowledgements

Question: Does a successful Weaviate delete prove that the target object existed before deletion?

The pinned guide distinguishes deletion responses by replication topology. A missing ID on an unreplicated single shard with replication factor one returns 404, while replicated configurations can return success for a missing object. Client handling of 404 also differs. The acknowledgement must be interpreted with topology and client semantics; it does not reconstruct prior existence or establish deletion of every replica or backup.

Source: Weaviate pinned documentation — delete. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a successful Weaviate delete prove that the target object existed before deletion?

Buyer evidence still required

  • Object ID and tenant
  • Replication factor, shard topology and client version
  • Pre-deletion inventory and raw operation result

Review inference: Prevent an idempotent deletion acknowledgement from being used as prior-existence evidence. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Do not infer prior existence from delete success alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual replica convergence and backup erasure are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Actual replica convergence and backup erasure are unknown.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate backups: Tenant coverage and whole-collection restore

Question: Can a Weaviate backup restore tenant content beyond a declared deletion boundary?

Weaviate backups include active and inactive tenants from v1.37.0, with backports to v1.35.17 and v1.36.10; earlier releases include active tenants only. Offloaded tenant data is excluded. Backups operate at instance or collection granularity, and tenant-level restore is unavailable: restoring brings back a whole collection. Backup coverage therefore depends on version and tenant state.

Source: Backups | Weaviate Documentation. Documentation checked 2026-10-18; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Weaviate backup restore tenant content beyond a declared deletion boundary?

Buyer evidence still required

  • Weaviate version, tenant state and collection/include/exclude manifest.
  • Backup creation time, destination inventory and retention or immutability controls.
  • Post-deletion backup disposition and restore outcomes reconciled to tenants.

Review inference: Earlier backups containing tenant data need separate accounting before asserting deletion or approving restoration.

Suggested review condition: Refuse tenant-complete deletion or isolated tenant-restore claims without version, backup and scope evidence.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Existence and contents of buyer backups, erasure and restored data were not inspected.

Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck tenant inclusion, backports, offloading and restore granularity after upgrades.

Optional saved evidence: Identify residual resources before closing a data-retention or exit decision.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Automatic backup deletion, verified tenant erasure or successful selective tenant restoration
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Weaviate bounded bulk deletion

Question: Can one successful Weaviate filter deletion remove every matching object?

The pinned Weaviate deletion guide limits a multi-object deletion to QUERY_MAXIMUM_RESULTS, whose documented default is 10,000. It instructs callers to repeat deletion until no matching objects remain; deletion order is by UUID. Dry-run counts and verbose per-object outcomes are available. A successful bounded batch alone does not establish exhaustion of the intended tenant and filter scope.

Source: Weaviate pinned documentation — delete. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can one successful Weaviate filter deletion remove every matching object?

Buyer evidence still required

  • Tenant and filter used for deletion
  • Effective result limit and each batch outcome
  • Post-operation matching-object reconciliation

Review inference: Avoid signing off an offboarding job after only its first bounded delete batch. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse all-matches-deleted when only one capped batch is evidenced.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Concurrent writes and other copies were not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Concurrent writes and other copies were not assessed.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate deleted collections and dangling aliases

Question: Does deleting a Weaviate collection automatically remove every alias that points to it?

The pinned collection-alias guide defines an alias as a routing pointer for object operations and queries. Removing it removes the pointer, not its target collection. Conversely, deleting a collection does not automatically remove its aliases. An alias change or disappearance is therefore routing evidence, not proof of collection deletion or a complete migration.

Source: Weaviate pinned documentation — collection-aliases. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does deleting a Weaviate collection automatically remove every alias that points to it?

Buyer evidence still required

  • Alias-to-collection mapping before and after the change
  • Underlying collection inventory
  • Authorised deletion or migration acceptance records

Review inference: Reconcile dangling routing pointers separately from deleted collection data. This is a review judgment, not an observed buyer cleanup.

Suggested review condition: Refuse a fully cleaned routing inventory from collection deletion alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Residual collections, backups and destination contents are not established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Residual collections, backups and destination contents are not established.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate expiry visibility versus deletion

Question: Does hiding expired Weaviate objects from queries establish that TTL deletion ran?

The pinned Weaviate TTL documentation separates expiry from scheduled deletion. The OBJECTS_TTL_DELETE_SCHEDULE setting enables the background deletion schedule; without it expired objects are not deleted. Query exclusion can hide expired objects before that deletion. A query with no expired results therefore does not establish that the deletion job ran or that residual copies were removed.

Source: Weaviate pinned documentation — time-to-live. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does hiding expired Weaviate objects from queries establish that TTL deletion ran?

Buyer evidence still required

  • Collection TTL configuration and installed version
  • Deletion schedule and job execution evidence
  • Object identifiers and residual-copy inventory

Review inference: Distinguish search invisibility from a completed retention action. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse a completed-deletion conclusion based only on expiry or empty query results.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Deletion execution and backup disposition remain unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Deletion execution and backup disposition remain unobserved.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate incremental restore dependencies

Question: Can an older Weaviate full backup be deleted while dependent incremental backups are retained?

The pinned backup guide states that incremental backups can reference unchanged files in earlier backups, including through a chain of incremental bases. Restore follows the chain to obtain those files. Every base and intermediate backup on which a retained backup depends must therefore remain available. Keeping only the newest incremental archive is not evidence of an independently restorable copy.

Source: Weaviate pinned documentation — backups. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can an older Weaviate full backup be deleted while dependent incremental backups are retained?

Buyer evidence still required

  • Retained backup IDs and base dependencies
  • Backend inventory for every dependency
  • Restore verification and retention approval

Review inference: Make backup deletion decisions against the dependency graph rather than archive age alone. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse deletion of a base still required by a retained incremental backup.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No actual dependency graph or restore was tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No actual dependency graph or restore was tested.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate per-object import failures

Question: Can a completed Weaviate batch import conceal failed objects or references?

The pinned import guide permits individual objects to fail while other objects continue. It exposes per-object failures and client-specific error reporting, including failed objects and references after Python batching. Completion of the surrounding batch is not an all-records receipt. Migration acceptance needs submitted identifiers reconciled against per-object results and the intended reference graph.

Source: Weaviate pinned documentation — import. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a completed Weaviate batch import conceal failed objects or references?

Buyer evidence still required

  • Submitted object IDs and reference inventory
  • Client version and batch error outputs
  • Destination counts and identifier reconciliation

Review inference: Detect partial ingestion before accepting a replacement store. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse complete import when failed-object or failed-reference results are missing.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Semantic equivalence of embeddings and references has not been verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Semantic equivalence of embeddings and references has not been verified.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate preview export scope

Question: Does a successful Weaviate Parquet export include later writes and all tenants?

The pinned export guide describes a preview feature introduced in v1.37, disabled by default and unavailable in Weaviate Cloud. Its snapshot fixes the data and tenant list when export starts. Later writes and newly created tenants are outside that snapshot; HOT and COLD tenants are included while OFFLOADED tenants are skipped with shard status. A completion status needs reconciliation against that declared scope before an exit export is accepted.

Source: Weaviate pinned documentation — export. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does a successful Weaviate Parquet export include later writes and all tenants?

Buyer evidence still required

  • Deployment version and export feature availability
  • Start-time tenant inventory and snapshot cutoff
  • Export manifest, shard states and source counts

Review inference: Define an export cutoff and account for skipped tenants before migration acceptance. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse an all-tenant current-state export claim without skipped-tenant and cutoff reconciliation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Destination portability and buyer export completeness were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Destination portability and buyer export completeness were not tested.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate redacted backup dependency metadata

Question: Does an empty Weaviate backup base ID prove that a backup is full?

The pinned guide says the list-side incremental_base_backup_id field, introduced in v1.37.6, is only populated for a confirmed root user. Other callers receive an empty value even when a backup is incremental and they otherwise have backup permissions. An empty list value is therefore ambiguous without caller identity and independent chain evidence; it cannot classify the backup as self-contained.

Source: Weaviate pinned documentation — backups. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does an empty Weaviate backup base ID prove that a backup is full?

Buyer evidence still required

  • Server version and listing caller identity
  • Backup-list output with effective permissions
  • Independently retained creation and base-chain records

Review inference: Detect a permission-induced evidence gap in backup dependency audits. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse a full-backup classification from an empty base field without resolving redaction.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The actual caller role and backup dependency are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • The actual caller role and backup dependency are unknown.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate restore cancellation boundary

Question: Can a Weaviate restore still be cancelled once it reaches FINALIZING?

The pinned backup guide permits cancellation in STARTED, TRANSFERRING and TRANSFERRED, but not FINALIZING, when schema changes are being committed through Raft. CANCELLING and CANCELED are separate states. A cancellation request must therefore be reconciled with the operation phase and terminal result; it cannot be represented as a guaranteed rollback after finalisation begins.

Source: Weaviate pinned documentation — backups. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Can a Weaviate restore still be cancelled once it reaches FINALIZING?

Buyer evidence still required

  • Installed restore capability and operation ID
  • Phase at cancellation request and response
  • Terminal restore state and resulting schema inventory

Review inference: Define an operational stop point before restore schema changes are committed. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse a cancelled-or-rolled-back conclusion from the request alone, especially after FINALIZING.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer cancellation, rollback or residual staged-data cleanup was observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • No buyer cancellation, rollback or residual staged-data cleanup was observed.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate restored data and omitted access configuration

Question: Does restoring a Weaviate collection automatically restore its RBAC users and roles?

The pinned backup guide states that RBAC roles and users are not restored by default. The restore options rolesOptions and usersOptions default to noRestore; selecting all enables restoration, with those options documented from v1.32.0. A data restore must therefore be reconciled separately with the intended access configuration rather than treated as proof that previous authority boundaries were recreated.

Source: Weaviate pinned documentation — backups. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does restoring a Weaviate collection automatically restore its RBAC users and roles?

Buyer evidence still required

  • Installed version and backup RBAC contents
  • Restore options for users and roles
  • Post-restore access-policy comparison

Review inference: Check access configuration explicitly when accepting a restored collection. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse access-equivalence approval from a successful data restore alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Effective access after restore and source configuration completeness were not tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Effective access after restore and source configuration completeness were not tested.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Weaviate tenant offload initiation

Question: Does the Weaviate offload timeout bound completion of tenant data transfer?

The pinned tenant-offloading documentation describes OFFLOAD_TIMEOUT as a limit for starting the offload operation, with a documented default of 120 seconds. Transfer proceeds asynchronously after initiation. That setting is not a maximum transfer duration, nor does successful initiation establish that the tenant data reached the offload destination.

Source: Weaviate pinned documentation — tenant-offloading. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: AI Data Custody, Retention & Exit Assurance

Evidence to request before relying on this claim

Claim to check: Does the Weaviate offload timeout bound completion of tenant data transfer?

Buyer evidence still required

  • Tenant operation and effective timeout configuration
  • Observed state transitions and terminal outcome
  • Destination object and transfer evidence

Review inference: Avoid treating a start deadline as a completed custody transfer. The required reconciliation is a review judgment; no buyer deployment was inspected.

Suggested review condition: Refuse completed offload based only on initiation success or expiry of the start timeout.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Transfer duration, destination completeness and source residuals remain unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned source, deployed version, selection policy and retained operation results before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Transfer duration, destination completeness and source residuals remain unobserved.
  • No independently verified physical deletion, complete recovery, legal compliance or security assurance.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Webflow MCP: Site changes and Designer dependencies

Question: Does keeping the Webflow Designer closed stop an agent from changing my site?

Webflow documents that most MCP operations use its Data API without an open Designer. Only some live-session capabilities need the Bridge App. The server can change site content and design within existing permissions, so closing the Designer is not evidence of a read-only connection.

Source: Webflow MCP operations and unsupported capabilities. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Main hosted MCP; beta and documentation-only servers excluded

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Webflow hosts the main MCP service.

Documented by publisher. Webflow MCP operations and unsupported capabilities; Webflow MCP OAuth, roles and Designer Bridge

Purpose

Connect assistants to site design, CMS and related management operations.

Documented by publisher. Webflow MCP operations and unsupported capabilities; Webflow MCP OAuth, roles and Designer Bridge

Read capability

Reads site data and supported analytics; live visual capture needs the Bridge App.

Documented by publisher. Webflow MCP operations and unsupported capabilities; Webflow MCP OAuth, roles and Designer Bridge

Write capability

Can modify content, design and custom code; some page-branch operations require Enterprise.

Documented by publisher. Webflow MCP operations and unsupported capabilities; Webflow MCP OAuth, roles and Designer Bridge

Authentication

OAuth authorises site access within one workspace per connection.

Documented by publisher. Webflow MCP operations and unsupported capabilities; Webflow MCP OAuth, roles and Designer Bridge

Permission surface

Existing roles govern operations; MCP cannot change user access settings.

Documented by publisher. Webflow MCP operations and unsupported capabilities; Webflow MCP OAuth, roles and Designer Bridge

Data leaving the environment

Site data and responses pass between Webflow and the connected assistant.

Review inference. Webflow MCP operations and unsupported capabilities; Webflow MCP OAuth, roles and Designer Bridge

Failure modes to consider

A closed Designer does not prevent ordinary API changes; unsupported features can appear absent.

Review inference. Webflow MCP operations and unsupported capabilities; Webflow MCP OAuth, roles and Designer Bridge

Unknowns and applicability

The buyer role, publishing workflow and site state have not been checked.

Not established

Suggested refusal or clarification condition

Require approval for the intended site change; do not treat closing the Designer as an access control.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck role grants, workspace connection and Bridge-dependent capabilities.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the distinction between API changes, live Designer requirements and role evidence.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Where does Service Bus retain a message that cannot be forwarded

Question: Where does Service Bus retain a message that cannot be forwarded?

For failed auto-forward or send-via transfer, the message is placed in the transfer dead-letter queue of the source entity that forwarded it, not the intended destination.

Source: Service Bus Dead-Letter Queues - Azure Service Bus | Microsoft Learn. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Where does Service Bus retain a message that cannot be forwarded?

Buyer evidence still required

  • source and destination entities
  • forwarding configuration
  • transfer DLQ inventory
  • operation identity

Review inference: Locate stranded workflow transfers before replay. Require the missing evidence before accepting, retrying or closing the operation. Transfer failure storage location differs from deferred-message retrieval. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not declare the transfer lost or recovered from the destination inventory alone. Inspect the source transfer DLQ and reconcile actual effects.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Path to the transfer dead-letter queue

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not declare the transfer lost or recovered from the destination inventory alone. Inspect the source transfer DLQ and reconcile actual effects.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Where must an Entra agent identity obtain its authentication credentials

Question: Where must an Entra agent identity obtain its authentication credentials?

The agent identity has no credentials of its own. Its blueprint holds credentials and acquires tokens on its behalf, subject to relevant consent. Review both objects and their credential relationship.

Source: Microsoft primary documentation: entra agent identities. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Where must an Entra agent identity obtain its authentication credentials?

Buyer evidence still required

  • tenant
  • agent ID
  • blueprint ID
  • credential reference
  • consent

Review inference: Where must an Entra agent identity obtain its authentication credentials? Do not accept an agent identifier alone as proof of a usable, authorized credential path. Entra blueprint credential custody is a different mechanism from an AgentCore workload token. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not accept an agent identifier alone as proof of a usable, authorized credential path.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Credentials

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not accept an agent identifier alone as proof of a usable, authorized credential path.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Where should a Graph sharing review locate the source of an inherited grant

Question: Where should a Graph sharing review locate the source of an inherited grant?

Graph sharing permissions can be direct or inherited. The inheritedFrom property identifies the ancestor supplying an inherited permission, so the child list alone is not a statement that the grant originated on that child.

Source: List who has access to a file - Microsoft Graph v1.0 | Microsoft Learn. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Where should a Graph sharing review locate the source of an inherited grant?

Buyer evidence still required

  • child item identifier
  • inheritedFrom references
  • ancestor sharing inventory
  • intended change scope

Review inference: Where should a Graph sharing review locate the source of an inherited grant? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Finding the grant origin differs from satisfying consent and token prerequisites. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Resolve the granting ancestor before recommending a scoped permission change; no change or revocation is performed here.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Effective sharing permissions

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Resolve the granting ancestor before recommending a scoped permission change; no change or revocation is performed here.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Which audience and resource identify an MCP enterprise grant

Question: Which audience and resource identify an MCP enterprise grant?

In the optional pinned 2026-07-28 profile, the token-exchange audience is the resource authorization server's issuer identifier. The optional resource parameter, when supplied, identifies the MCP server. The profile requires the final access token to be restricted to the MCP server identified by the ID-JAG resource claim. Omission does not establish unrestricted access; this source does not resolve every omitted-resource deployment behavior.

Source: Model Context Protocol primary documentation: ext enterprise managed authorization. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Which audience and resource identify an MCP enterprise grant?

Buyer evidence still required

  • exchange request
  • issuer
  • MCP resource ID
  • final audience summary

Review inference: Which audience and resource identify an MCP enterprise grant? Do not substitute the MCP URL for the authorization-server issuer. Grant audience differs from final resource-token audience. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not substitute the MCP URL for the authorization-server issuer.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. audience

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not substitute the MCP URL for the authorization-server issuer.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Which identifier receives an autonomous Entra agent app-role assignment

Question: Can a blueprint client ID receive a child agent's resource app-role assignment?

For an application-permission grant to the child agent, the documented assignment uses the agent identity service principal object ID as principalId, the resource service principal object ID as resourceId, and the selected appRoleId. Do not substitute the blueprint client ID. A separate grant to a blueprint for agent-user creation is a different operation.

Source: Microsoft primary documentation: entra autonomous agent authentication authorization flow. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Can a blueprint client ID receive a child agent's resource app-role assignment?

Buyer evidence still required

  • agent object ID
  • resource principal ID
  • role ID
  • grant response

Review inference: Can a blueprint client ID receive a child agent's resource app-role assignment? Require the exact principal/resource/role tuple. Identifies the actual grant recipient, not an administrator consent role. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require the exact principal/resource/role tuple.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Create an app role assignment via APIs

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require the exact principal/resource/role tuple.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Which Mcp-Name value should an HTTP client send for later MCP task operations

Question: Which Mcp-Name value should an HTTP client send for later MCP task operations?

For tasks/get, tasks/update and tasks/cancel over Streamable HTTP, the optional 2026-07-28 extension requires Mcp-Name equal to params.taskId. Mcp-Method remains the JSON-RPC method. This enables intermediaries to route to the instance holding task state; it does not replace authorization.

Source: Model Context Protocol primary documentation: mcp tasks current. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Which Mcp-Name value should an HTTP client send for later MCP task operations?

Buyer evidence still required

  • transport
  • task ID
  • Mcp-Name
  • Mcp-Method
  • response
  • caller permission

Review inference: Which Mcp-Name value should an HTTP client send for later MCP task operations? Require task-ID routing and separate access checks before diagnosing a missing task as absent work. Task operations route by task ID rather than the original tool name or generic method alone. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Require task-ID routing and separate access checks before diagnosing a missing task as absent work.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Routing Headers

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Require task-ID routing and separate access checks before diagnosing a missing task as absent work.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Whose identity appears when an Entra blueprint provisions an agent

Question: Whose identity appears when an Entra blueprint provisions an agent?

The tenant blueprint principal is referenced by the blueprint token oid and audit records for blueprint operations. That provisioning actor differs from the child performing later resource work.

Source: Microsoft primary documentation: entra agent blueprint. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Agent Identity, Credentials & Delegation

Evidence to request before relying on this claim

Claim to check: Whose identity appears when an Entra blueprint provisions an agent?

Buyer evidence still required

  • blueprint principal
  • child ID
  • provisioning/runtime events
  • tenant

Review inference: Whose identity appears when an Entra blueprint provisions an agent? Preserve both actors; provisioning is not evidence of a child's later action. Separates provisioning and runtime actors, not permission tuples. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Preserve both actors; provisioning is not evidence of a child's later action.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Audit Logging

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Preserve both actors; provisioning is not evidence of a child's later action.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Will LangSmith automatically score runs skipped while an evaluator was budget-paused

Question: Will LangSmith automatically score runs skipped while an evaluator was budget-paused?

After a reset or increased limit, evaluation resumes on new runs. The documentation states that skipped runs are not backfilled, leaving a distinct assessment coverage gap.

Source: Track and limit evaluator spend. Documentation checked 2026-10-30; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Will LangSmith automatically score runs skipped while an evaluator was budget-paused?

Buyer evidence still required

  • pause interval
  • skipped run identities
  • resumed evaluations
  • explicit reassessment evidence

Review inference: Will LangSmith automatically score runs skipped while an evaluator was budget-paused? Use the stated boundary to identify missing scope, source or outcome evidence before closing the review. Missing evaluations differ from missing source traces or capture configuration. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not treat budget recovery as completion of the previously skipped evaluation interval.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. When a limit is reached

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not treat budget recovery as completion of the previously skipped evaluation interval.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Will TTL clear messages already in a Service Bus dead-letter queue

Question: Will TTL clear messages already in a Service Bus dead-letter queue?

Time-to-live is not observed inside the dead-letter queue. There is no automatic cleanup; dead letters remain until explicitly retrieved and completed.

Source: Service Bus Dead-Letter Queues - Azure Service Bus | Microsoft Learn. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Audit, Provenance & Evidence Accountability

Evidence to request before relying on this claim

Claim to check: Will TTL clear messages already in a Service Bus dead-letter queue?

Buyer evidence still required

  • entity and subqueue
  • dead-letter inventory
  • cleanup policy
  • completion evidence

Review inference: Check retention of messages after failed processing. Require the missing evidence before accepting, retrying or closing the operation. Dead-letter retention differs from deferred-message expiry and retrieval. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not use original TTL as disposal evidence. Verify the relevant inventory and completion records.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. dead-letter queue

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not use original TTL as disposal evidence. Verify the relevant inventory and completion records.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Wise cancelled refunded state distinction

Question: Does Wise cancelled identify the same financial outcome as funds_refunded?

Wise distinguishes funds_refunded from cancelled. The status table describes cancelled as final for an unfunded transfer, but the same documentation also shows a funded returned-payment flow passing through processing and cancelled before funds_refunded, and permits rollback transitions. A cancelled label alone therefore establishes neither absence of funding nor completion of a refund. Reconcile the state timeline, funding and provider refund evidence.

Source: Wise: Transfer statuses. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does Wise cancelled identify the same financial outcome as funds_refunded?

Buyer evidence still required

  • transfer API state
  • funding history
  • cancellation outcome
  • refund reference where applicable

Review inference: A recovery system normalises all abandoned transfers to cancelled. Its ledger can omit a funding-and-refund cycle. Adds Wise's distinct cancellation/refund states, not retry identity. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer that cancelled means never funded or already refunded. Reconcile transfer history and refund evidence; a provider status is not independent proof of receipt at the sender bank.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. funds_refunded

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer that cancelled means never funded or already refunded. Reconcile transfer history and refund evidence; a provider status is not independent proof of receipt at the sender bank.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Wise funding initiation versus receipt

Question: Does a Wise transfer in incoming_payment_initiated establish received funding?

Wise describes incoming_payment_initiated as funding started but not yet received. The processing state indicates Wise has received funds and is performing its processing activities; it does not itself establish payout. Transfer submission, funding receipt and recipient outcome require distinct evidence.

Source: Wise: Transfer statuses. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Wise transfer in incoming_payment_initiated establish received funding?

Buyer evidence still required

  • transfer ID
  • funding method and reference
  • state transitions
  • received-funds and payout evidence

Review inference: An agent reports a purchase funded immediately after initiating its transfer. Fulfilment may proceed before the required funding has arrived. Separates Wise pay-in receipt from transfer creation, unlike card authorisation/capture. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse funded or recipient-paid claims based on a submitted or initiated transfer; do not interpret processing as completed payout.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. incoming_payment_initiated

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse funded or recipient-paid claims based on a submitted or initiated transfer; do not interpret processing as completed payout.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Wise inbound return originator receipt

Question: Does a Wise inbound-payment return marked REFUNDED prove the originator received it?

For the documented inbound return flow, CANCELLED means the balance was debited and return processing starts; REFUNDED means the return was processed and is en route to the originator. Wise also describes reconciliation using the original inbound transfer ID in the balance statement. A processed return is not independent evidence of originator-bank receipt.

Source: Wise: Initiate an inbound-payment return. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a Wise inbound-payment return marked REFUNDED prove the originator received it?

Buyer evidence still required

  • original inbound payment or transfer ID
  • return-state events
  • balance-statement debit
  • originator receipt if required

Review inference: An operator closes a mistaken incoming payment after initiating its return. Return processing can be mistaken for completed receipt by the sender. Adds a specifically documented inbound-return state and original-ID reconciliation contract. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not confuse this inbound-return contract with ordinary outgoing-transfer states or assert originator receipt from REFUNDED alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Monitor the return status

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not confuse this inbound-return contract with ordinary outgoing-transfer states or assert originator receipt from REFUNDED alone.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Wise logical transfer retry identity

Question: Should an uncertain Wise transfer creation be retried with a new customerTransactionId?

Wise's error guide identifies customerTransactionId as the logical transfer identifier and says to reuse it when retrying the same uncertain creation. A new identifier can create another transfer. The quote.duplicate error requires reconciliation of the existing transfer rather than reusing that quote for another one.

Source: Wise: Transfer error handling. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Should an uncertain Wise transfer creation be retried with a new customerTransactionId?

Buyer evidence still required

  • logical payment intent
  • original customerTransactionId
  • quote ID
  • prior creation response or timeout
  • retrieved transfer state

Review inference: A network timeout occurs after creating an authorised supplier transfer. A recovery attempt can become a second payment. Adds Wise's transfer/quote identity pairing and duplicate-quote recovery, not PayPal's request-header contract. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not create a new logical identifier merely to recover an uncertain response; reconcile the existing transfer first.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. customerTransactionId

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not create a new logical identifier merely to recover an uncertain response; reconcile the existing transfer first.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Wise originator reference restriction

Question: Can changing an originator reference safely resolve Wise's originator-not-allowed error?

For validation.failure.originator.externalId.not.allowed, Wise instructs integrations to investigate the restriction or a confirmed data defect and retain the same reference for the same originator. Altering the identifier is not documented as a legitimate way to clear the restriction.

Source: Wise: Transfer error handling. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can changing an originator reference safely resolve Wise's originator-not-allowed error?

Buyer evidence still required

  • originator identity and external reference
  • exact error
  • confirmed correction or restriction resolution
  • approved retry intent

Review inference: An automated recovery routine substitutes identifiers after a payment refusal. It can misbind the payment originator or bypass a required investigation. Addresses preserving originator identity through a refusal, distinct from deduplicating an otherwise permitted payment. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse a retry that changes identity merely to evade the restriction; this evidence grants no authority to transact.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. validation.failure.originator.externalId.not.allowed

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse a retry that changes identity merely to evade the restriction; this evidence grants no authority to transact.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Wise quote rate expiry distinction

Question: Does an unexpired Wise quote guarantee the originally approved rate remains locked?

Wise exposes rateType, rateExpirationTime and expirationTime as separate fields: rate expiry concerns the locked rate, while expirationTime concerns the whole quote. The guide also binds the rate promise after transfer creation to funding before its deadline. Quote validity alone is not evidence that approved conversion terms still apply.

Source: Wise: Authenticated quotes. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an unexpired Wise quote guarantee the originally approved rate remains locked?

Buyer evidence still required

  • quote ID and status
  • fixed or floating rate type
  • both expiry times
  • funding time
  • approved source and target amounts

Review inference: An agent resumes an approved currency transfer after a delay. The transfer may use terms different from the original approval. Adds FX quote-versus-rate validity and funding deadlines, distinct from editable order amounts. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Refuse unchanged-rate claims without the applicable lock and funding evidence; a replacement quote requires comparison with approved terms.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. rateExpirationTime

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Refuse unchanged-rate claims without the applicable lock and funding evidence; a replacement quote requires comparison with approved terms.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Wise quote recipient context binding

Question: Does a valid Wise quote alone authorise a transfer to a changed recipient?

Wise documents quote.targetaccount.mismatching when quote and target recipient do not match, and requires the quote and recipient to belong to the same profile and transfer context. A missing target account must also be resolved before accepting the quote. These API checks do not verify the buyer's approval of a bank-detail change.

Source: Wise: Transfer error handling. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a valid Wise quote alone authorise a transfer to a changed recipient?

Buyer evidence still required

  • quote and recipient IDs
  • owning profile
  • final target account
  • approved payee details
  • transfer requirements

Review inference: Supplier bank details change between quote preparation and transfer creation. A technically accepted transfer may still target an unapproved payee. Adds provider quote/recipient-context consistency while explicitly leaving business approval unproved. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer payee-change approval or bank-account ownership from API acceptance; bind final recipient details to the original authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. quote.targetaccount.mismatching

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer payee-change approval or bank-account ownership from API acceptance; bind final recipient details to the original authority.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Wise sent nonfinal beneficiary outcome

Question: Does Wise's Completed label prove final receipt at the beneficiary bank?

Wise maps its consumer Completed label to outgoing_payment_sent, meaning it sent the payout rather than confirming beneficiary credit. Transfers support rollback transitions, and returned funds can lead to bounced_back, processing or refund outcomes. Reconciliation cannot assume that reaching the sent state makes later state changes impossible.

Source: Wise: Transfer statuses. Documentation checked 2026-10-29; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does Wise's Completed label prove final receipt at the beneficiary bank?

Buyer evidence still required

  • transfer ID
  • API state timeline
  • recipient-bank evidence
  • bounce and refund events

Review inference: An invoice system closes a supplier obligation when Wise displays Completed. A delayed or bounced payout can remain unreconciled. Adds Wise's consumer/API label mapping and non-monotonic transfer lifecycle, rather than card capture submission. This is an operational review inference, not an observed deployment outcome.

Suggested review condition: Do not infer beneficiary credit or irreversible finality from Completed or outgoing_payment_sent alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.

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.

Recheck: Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included. Transfer status flow

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Do not infer beneficiary credit or irreversible finality from Completed or outgoing_payment_sent alone.
  • Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
  • No expanded capabilities or licences for existing INDEX executables.

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Workload federation: Trusted issuer and accepted identities

Question: Does trusting an external identity provider let every identity from it access Google Cloud?

Workload Identity Federation uses attribute mapping and can apply conditions to accept only selected external identities. Resource access then depends on direct IAM grants or service-account impersonation. Removing a stored service-account key does not establish a narrowly scoped trust relationship by itself.

Source: Google Cloud Workload Identity Federation. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Keyless federation automatically establishes least privilege.

Buyer evidence still required

  • Issuer and attribute mapping.
  • Provider condition and accepted identity set.
  • Direct grants or impersonated account permissions.

Suggested review condition: Require accepted-identity and resource scope before approving federation.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Issuer, mappings, provider conditions and resource authorization

Optional saved evidence: Preserve the identity-selection and resource-permission evidence for keyless access.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

WorkOS MCP: Role inheritance, environment and write controls

Question: Does the WorkOS sandbox default prevent production changes?

The default target is sandbox, but production access and writes are separately controlled and initially enabled in the documented team settings. The agent inherits the dashboard user role. Check those settings and the requested environment; the sandbox default alone is not a production-access restriction.

Source: WorkOS management MCP workspace controls. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Hosted WorkOS management MCP

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

WorkOS operates the management endpoint.

Documented by publisher. WorkOS management MCP workspace controls

Purpose

Manage workspace authentication resources and configuration.

Documented by publisher. WorkOS management MCP workspace controls

Read capability

Permitted organisation, user and configuration data; returned secret values are stripped.

Documented by publisher. WorkOS management MCP workspace controls

Write capability

Supported configuration and resource changes within the inherited role.

Documented by publisher. WorkOS management MCP workspace controls

Authentication

OAuth as the dashboard account.

Documented by publisher. WorkOS management MCP workspace controls

Permission surface

Role inheritance plus independent team controls for access, production and writes.

Documented by publisher. WorkOS management MCP workspace controls

Data leaving the environment

Permitted workspace data enters the connected client.

Review inference. WorkOS management MCP workspace controls

Failure modes to consider

A default sandbox target may be mistaken for enforced production isolation.

Review inference. WorkOS management MCP workspace controls

Unknowns and applicability

Team settings and the buyer role were not inspected.

Not established

Suggested refusal or clarification condition

Confirm production authority before changing the target environment.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Team-control defaults, role inheritance and excluded operations.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Save the difference between a default target and an enforced production/write restriction.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Workspace app controls: Trusted access is not a narrow scope grant

Question: Does marking a third-party app Trusted prove it has only the scopes needed for my task?

Trusted apps can access restricted and unrestricted Google services, subject to the relevant authorisation. The guide separately offers Specific Google data scope selection and organisational-unit settings. A Trusted label alone therefore does not establish a narrowly scoped integration.

Source: Google Workspace third-party app access controls. Documentation checked 2026-10-16; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: A Trusted app designation proves least-privilege access.

Buyer evidence still required

  • OAuth client identity and requested scopes.
  • Configured app access level and organisational-unit scope.
  • Evidence of actual granted access for the intended workflow.

Suggested review condition: Require scope and organisational-unit evidence before accepting a least-privilege claim.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. App client IDs, scopes, access levels and organisational-unit assignments

Optional saved evidence: Preserve the concrete grant questions behind an app approval.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Workspace delegation user-selection limits

Question: Do OAuth scopes restrict which users a Google Workspace domain-wide delegated account can impersonate?

Google’s domain-wide delegation guidance states that OAuth scopes limit types of data but do not restrict which users the service account can impersonate. Choosing narrower scopes is therefore not a per-user impersonation allowlist. The guide recommends limiting use of domain-wide delegation and protecting the delegated service account.

Source: Domain-wide delegation best practices | Apps & integrations | Google Workspace Help. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Governance & Policy Boundaries

Evidence to request before relying on this claim

Claim to check: Do OAuth scopes restrict which users a Google Workspace domain-wide delegated account can impersonate?

Buyer evidence still required

  • Authorized OAuth scopes and delegated service account
  • Intended impersonated-user population
  • Independent controls and evidence limiting use of the account

Review inference: Treat user-selection restrictions as a separate requirement needing its own demonstrated control.

Suggested review condition: Reject a per-user restriction claim supported only by the OAuth scope list.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual impersonation controls and account use are unknown.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the documented behavior, product version and buyer evidence before relying on a current outcome.

Optional saved evidence: Expose broad impersonation reach before approving a delegated enterprise agent.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • A built-in per-user allowlist inferred from scope narrowing
  • Actual impersonation controls and account use are unknown.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

x402 A2A task and payment-state evidence

Question: Does x402 A2A payment-submitted or payment-verified establish completed payment?

The pinned A2A transport distinguishes submitted, verified and completed payment statuses. Payment payloads carry task correlation, and settlement results appear as receipts in task-status metadata. The submitted or verified labels are earlier states; they must not be treated as the completed settlement result.

Source: Transport: A2A (Agent-to-Agent Protocol). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does x402 A2A payment-submitted or payment-verified establish completed payment?

Buyer evidence still required

  • Task ID and submitted payment payload reference
  • Payment-status transition history
  • Settlement receipt metadata and matching resource

Review inference: Join the correct task to its payment result without collapsing intermediate states. This is a review decision, not an observed buyer result.

Suggested review condition: Do not classify submitted or verified task payment status as completed settlement.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual task execution, payment and delivered artifact are unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual task execution, payment and delivered artifact are unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 batch backing and collection risk

Question: Are all x402 batch-settlement commitments backed by the client on-chain funds?

The reviewed scheme permits capital-backed and credit-backed commitments. In the latter model, a trusted intermediary associates identity with a billing account and settles later. Each network binding must specify its trust model, redemption process and seller guarantee; the shared scheme name does not make those protections identical.

Source: Scheme: `batch-settlement`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Are all x402 batch-settlement commitments backed by the client on-chain funds?

Buyer evidence still required

  • Chosen network binding and backing model
  • Responsible intermediary or committed-capital evidence
  • Redemption rules and stated seller guarantee

Review inference: Identify who bears collection risk before serving high-volume machine requests. This is a review decision, not an observed buyer result.

Suggested review condition: Do not infer prefunded collateral from batch-settlement compatibility.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Intermediary creditworthiness, enforceability and recoverability have not been assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Intermediary creditworthiness, enforceability and recoverability have not been assessed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 batched commitment and later payment

Question: Does a successful x402 batch-settlement response prove that value has already transferred?

The pinned batch-settlement scheme accepts and stores a cryptographic commitment during the request; its network binding redeems value later. A successful response must include a non-empty commitment identifier. That identifier is not necessarily a chain transaction hash and does not itself establish completed redemption.

Source: Scheme: `batch-settlement`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a successful x402 batch-settlement response prove that value has already transferred?

Buyer evidence still required

  • Network binding and commitment identifier
  • Stored commitment and resource-delivery records
  • Redemption schedule and actual transfer evidence

Review inference: Reconcile delivered API work with stored commitments and subsequent value transfer. This is a review decision, not an observed buyer result.

Suggested review condition: Do not report a stored batch commitment as settled cash.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Commitment storage, redeemability and actual receipt of funds remain unobserved.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Commitment storage, redeemability and actual receipt of funds remain unobserved.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 delegation changes after simulation

Question: Can a successful x402 ERC-7710 simulation guarantee that the later transfer will execute?

The pinned EVM binding verifies ERC-7710 authority through simulation. Its security discussion identifies a race in which the client invalidates delegation before execution, leaving the facilitator paying gas for a failed transaction. The permission context depends on the particular delegation-manager implementation.

Source: Scheme: `exact` on `EVM`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a successful x402 ERC-7710 simulation guarantee that the later transfer will execute?

Buyer evidence still required

  • Delegation manager and permission context
  • Simulation time and resulting authority evidence
  • Execution receipt, transfer result and gas cost

Review inference: Separate a simulated authority check from executed payment and facilitator cost. This is a review decision, not an observed buyer result.

Suggested review condition: Do not treat simulation success as a guaranteed later transfer.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No delegation manager, live authority or network transaction has been validated.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • No delegation manager, live authority or network transaction has been validated.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 MCP settlement failure and prior execution

Question: Does an x402 MCP payment error prove that the tool did not execute?

The reviewed MCP transport uses isError tool results for payment requirements and failures. It specifically covers settlement failing after tool execution and says the tool content should then be withheld. An error result therefore does not establish absence of a prior tool effect; the failure phase matters.

Source: Transport: MCP (Model Context Protocol). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an x402 MCP payment error prove that the tool did not execute?

Buyer evidence still required

  • Tool request and stable operation identity
  • Verification, execution and settlement phase records
  • Tool effect evidence and retry policy

Review inference: Avoid repeating a side-effecting paid tool call based only on its error result. This is a review decision, not an observed buyer result.

Suggested review condition: Do not infer no execution from an x402 MCP payment error alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No actual tool effects or server retry protections have been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • No actual tool effects or server retry protections have been inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 metered authorization reuse

Question: Can an x402 upto authorization be charged again for its unused allowance?

The reviewed upto specification requires at most one settlement per authorization. Settlement consumes it regardless of the amount charged. Repeated settlements, recurring charges and open-ended allowances are outside this scheme; a lower first charge does not preserve the remainder as reusable authority.

Source: Scheme: `upto`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an x402 upto authorization be charged again for its unused allowance?

Buyer evidence still required

  • Original authorization and nonce
  • First settlement status and amount
  • Separate authority for the proposed later charge

Review inference: Prevent a one-request spending ceiling from being mistaken for a recurring budget. This is a review decision, not an observed buyer result.

Suggested review condition: Do not reuse a consumed upto authorization for later usage.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual nonce enforcement and any separately negotiated subscription remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual nonce enforcement and any separately negotiated subscription remain unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 metered ceilings and final charges

Question: Does the x402 upto amount mean the same thing during verification and settlement?

For the reviewed upto scheme, verification-time amount is the authorised maximum and settlement-time amount is the actual charge. The actual amount cannot exceed the signed maximum and may be zero. The facilitator must verify the signature against the original authorised maximum rather than the later charge.

Source: Scheme: `upto`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does the x402 upto amount mean the same thing during verification and settlement?

Buyer evidence still required

  • Signed maximum amount and asset units
  • Measured usage and agreed price calculation
  • Actual settlement amount and original authorization

Review inference: Reconcile metered usage to a bounded authorisation without confusing the ceiling with the invoice amount. This is a review decision, not an observed buyer result.

Suggested review condition: Do not report the authorised ceiling as the amount actually paid.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Usage measurement accuracy and the buyer actual charge are not independently established.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Usage measurement accuracy and the buyer actual charge are not independently established.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 payment flow and execution order

Question: Must every x402 v2 payment settle after the protected resource executes?

The reviewed v2 specification defines authorization, upfront and escrow flows with different ordering around resource execution. A non-authorization flow must be declared in the offered requirements. Clients must not construct payments for an unrecognised flow, and servers must reject unsupported method-and-flow combinations.

Source: X402 Protocol Specification. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Must every x402 v2 payment settle after the protected resource executes?

Buyer evidence still required

  • Offered transfer method and paymentFlow
  • Client and facilitator supported combinations
  • Execution, deposit and final-charge evidence

Review inference: Understand whether funds are committed before an operation can fail. This is a review decision, not an observed buyer result.

Suggested review condition: Do not assume one settlement order across all x402 schemes.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Implementation conformance and the effect of a failed buyer request remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Implementation conformance and the effect of a failed buyer request remain unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 pending settlement and retry decisions

Question: Does x402 settlement_pending mean that no payment transaction was broadcast?

The reviewed EVM exact binding permits settlement_pending when a transaction was broadcast but confirmation could not be established. The response carries its transaction hash so the caller can reconcile the chain outcome before retrying. This state is different from proof that no transfer occurred.

Source: Scheme: `exact` on `EVM`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does x402 settlement_pending mean that no payment transaction was broadcast?

Buyer evidence still required

  • Original signed payment identity
  • Broadcast transaction hash and target network
  • Subsequent confirmation or terminal failure evidence

Review inference: Avoid requesting a replacement payment while the original transfer may still confirm. This is a review decision, not an observed buyer result.

Suggested review condition: Do not treat a confirmation timeout as evidence that a fresh payment is safe.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No chain transaction or buyer retry implementation was inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • No chain transaction or buyer retry implementation was inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 Permit2 spender and payee checks

Question: Is the facilitator the signed spender in x402 exact Permit2 authorization?

The reviewed EVM exact binding identifies the x402ExactPermit2Proxy as the signed spender, rather than the facilitator. Its witness binds the destination address. The setup separately requires token approval to Permit2, with ordinary or supported sponsored approval paths; these roles should not be collapsed into one recipient identity.

Source: Scheme: `exact` on `EVM`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Is the facilitator the signed spender in x402 exact Permit2 authorization?

Buyer evidence still required

  • Token approval target and allowance
  • Signed proxy spender and witness destination
  • Network-specific contract and payment requirement

Review inference: Check the actual approval, spender and beneficiary before signing a machine-payment request. This is a review decision, not an observed buyer result.

Suggested review condition: Do not substitute the facilitator address for the specified signed spender or payee.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Contract deployments, approval state and buyer wallet behaviour are not independently tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Contract deployments, approval state and buyer wallet behaviour are not independently tested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 receipt content and independent reconciliation

Question: Does every x402 signed receipt contain a transaction reference and payment amount?

The pinned receipt format deliberately permits omission of the transaction reference for privacy. Its canonical fields identify the resource, payer, network and issuance time, without requiring a payment amount. A signature authenticates the server statement; independent financial reconciliation may require additional transaction evidence.

Source: Offer and Receipt Extension. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does every x402 signed receipt contain a transaction reference and payment amount?

Buyer evidence still required

  • Signed receipt and service-authorised key
  • Payment requirements and agreed amount
  • Independent transaction evidence where available

Review inference: Know which information must be retained separately to reconcile a machine-purchased service. This is a review decision, not an observed buyer result.

Suggested review condition: Do not infer amount, transfer finality or independently proven delivery from omitted receipt fields.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual payment and delivery are not independently observed by this documentation review.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual payment and delivery are not independently observed by this documentation review.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 receipt keys and historical authority

Question: Does a valid x402 receipt signature prove that its key was authorised for the service when issued?

The reviewed extension distinguishes signature validity from authority to sign for the resource URL. Historical verification should evaluate authority at receipt issuance. Removing a key from a current authorization source does not by itself establish that it was unauthorised earlier; dated authority evidence is therefore relevant.

Source: Offer and Receipt Extension. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does a valid x402 receipt signature prove that its key was authorised for the service when issued?

Buyer evidence still required

  • Receipt payload and signature
  • Resource URL and issuance time
  • Dated signer-authority evidence

Review inference: Retain evidence needed to assess commercial receipts after signing-key rotation. This is a review decision, not an observed buyer result.

Suggested review condition: Do not equate a valid signature or current key list with historical service authority.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual key ownership, authority and receipt truth have not been independently checked.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual key ownership, authority and receipt truth have not been independently checked.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 retry identifiers and operation binding

Question: Can an x402 payment identifier safely identify different paid operations across tenants?

The reviewed payment-identifier extension calls for binding an identifier to a normalized request fingerprint. Reuse with changed operation details should produce a conflict. It also recommends scoping keys by tenant, merchant, route or facilitator account where those boundaries exist, rather than using the identifier alone for authorization.

Source: Extension: `payment-identifier`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an x402 payment identifier safely identify different paid operations across tenants?

Buyer evidence still required

  • Identifier and original request fingerprint
  • Tenant, merchant and resource scope
  • Cached response and conflict-handling evidence

Review inference: Keep payment retries from returning another operation or tenant cached result. This is a review decision, not an observed buyer result.

Suggested review condition: Do not reuse cached authorization merely because the payment identifier matches.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Cache persistence, key scope and deployed conflict handling have not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Cache persistence, key scope and deployed conflict handling have not been tested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 signed offers and unsigned selection indices

Question: Can an x402 signed offer be bound to checkout terms using acceptIndex alone?

The reviewed offer extension describes acceptIndex as an unsigned convenience field. Clients should check its range and compare the selected payment requirements with the signed fields. The signature-covered terms, including network, asset, payee and amount, are the binding evidence; the index itself is not authoritative.

Source: Offer and Receipt Extension. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an x402 signed offer be bound to checkout terms using acceptIndex alone?

Buyer evidence still required

  • Exact signed offer payload
  • Selected accepts entry and index
  • Field-by-field comparison and authorised signing key

Review inference: Detect changed offer selection without treating an unsigned pointer as approved terms. This is a review decision, not an observed buyer result.

Suggested review condition: Do not rely on acceptIndex alone to bind the approved payment terms.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual server keys, offers and client matching behaviour have not been tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual server keys, offers and client matching behaviour have not been tested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 smart-wallet execution evidence

Question: Can a successful smart-wallet simulation alone establish x402 Solana settlement success?

The pinned Solana binding requires post-confirmation transfer verification for its smart-wallet path. The primary check inspects confirmed inner instructions; a documented fallback checks destination balance change when those instructions are unavailable. Simulation establishes expected behaviour, while settlement success must reflect actual chain effects.

Source: Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can a successful smart-wallet simulation alone establish x402 Solana settlement success?

Buyer evidence still required

  • Verification path and simulation result
  • Confirmed transaction and inner instructions
  • Any fallback balance observations and their timing

Review inference: Require execution evidence after a smart-wallet payment simulation. This is a review decision, not an observed buyer result.

Suggested review condition: Do not classify a simulated transfer as an observed settled transfer.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No buyer transaction, RPC data or attribution of a balance change has been independently verified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • No buyer transaction, RPC data or attribution of a balance change has been independently verified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 Solana hidden-account verification

Question: Can an x402 Solana sponsor sign before resolving the transaction address lookup tables?

The reviewed binding requires address lookup tables to be resolved before fee-payer isolation checks, making the reachable accounts visible. If the sponsor cannot resolve them, including a transient resolution failure, it must reject rather than verify an incomplete account set. The rule applies before signing.

Source: Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Can an x402 Solana sponsor sign before resolving the transaction address lookup tables?

Buyer evidence still required

  • Full resolved transaction accounts
  • Lookup-table resolution result
  • Fee-payer isolation checks before signing

Review inference: Prevent fee sponsorship from authorising an incompletely inspected account set. This is a review decision, not an observed buyer result.

Suggested review condition: Do not treat unresolved accounts as safe or absent.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual table contents and signing controls have not been inspected.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual table contents and signing controls have not been inspected.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 Solana payment validity and fee sponsorship

Question: Must a sponsor accept every transaction valid under x402 Solana exact?

The pinned binding separates the required payment outcome from sponsor acceptance policy. A sponsor may reject an otherwise valid payment on local policy grounds. Recommended controls include compute and priority-fee limits and program restrictions; successful payment validation does not entitle the client to sponsorship.

Source: Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Must a sponsor accept every transaction valid under x402 Solana exact?

Buyer evidence still required

  • Payment outcome validation
  • Sponsor program and fee policies
  • Requested compute and priority-fee parameters

Review inference: Budget the facilitator exposure separately from the buyer transfer amount. This is a review decision, not an observed buyer result.

Suggested review condition: Do not infer sponsorship approval from payment validity alone.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Configured sponsor limits and implementation behaviour remain unverified.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Configured sponsor limits and implementation behaviour remain unverified.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 Solana transfer identity and amount

Question: Does x402 Solana exact require the matching transfer amount to equal the quoted amount exactly?

The pinned Solana exact binding permits a matching transfer greater than or equal to the required amount, including rounding-related overpayment. It nevertheless requires exactly one matching transfer across top-level and inner instructions, with the correct mint, destination and token program. Zero or multiple matching transfers must be rejected.

Source: Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does x402 Solana exact require the matching transfer amount to equal the quoted amount exactly?

Buyer evidence still required

  • Pinned Solana binding revision
  • Required mint, recipient and amount
  • Full executed transfer instruction evidence

Review inference: Avoid inferring exact financial equality from a scheme name or aggregating ambiguous transfers. This is a review decision, not an observed buyer result.

Suggested review condition: Do not assume the name exact establishes amount equality or permits summing multiple matches.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The wallet transaction and any actual overpayment are not observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • The wallet transaction and any actual overpayment are not observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 Solana transfer replay and duplicate access

Question: Does Solana transaction deduplication alone prevent repeated x402 resource access?

The reviewed binding describes a settlement race in which repeated submissions can receive successful responses although the chain executes the transfer once. It recommends tracking in-flight payloads to reject duplicate settlements. Chain-level transfer deduplication and application-level resource access are separate controls.

Source: Exact Payment Scheme for Solana Virtual Machine (SVM) (`exact`). Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does Solana transaction deduplication alone prevent repeated x402 resource access?

Buyer evidence still required

  • Submitted transaction payload identity
  • Concurrent settlement and response records
  • Resource admission and deduplication state

Review inference: Avoid granting several paid operations against a single transfer. This is a review decision, not an observed buyer result.

Suggested review condition: Do not infer one resource delivery from one on-chain transfer.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

No multi-instance deployment or deduplication storage was tested.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • No multi-instance deployment or deduplication storage was tested.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 upfront charges and failed resource delivery

Question: Does x402 exact upfront define an automatic refund when the resource handler fails?

The pinned exact scheme allows upfront settlement before resource execution. It explicitly notes that a handler failure can leave the client charged without delivery and that this scheme defines no refund for that situation. Any remedy is an arrangement made by the resource server.

Source: Scheme: `exact`. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does x402 exact upfront define an automatic refund when the resource handler fails?

Buyer evidence still required

  • Selected exact payment flow
  • Merchant delivery and remedy terms
  • Payment and failed-execution evidence

Review inference: Check recovery terms before accepting a prepaid machine-service call. This is a review decision, not an observed buyer result.

Suggested review condition: Do not promise an automatic protocol refund for an upfront handler failure.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

Actual merchant recovery arrangements and transferred funds are not assessed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • Actual merchant recovery arrangements and transferred funds are not assessed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

x402 verification and payment state

Question: Does an x402 v2 successful verify response establish that funds have moved?

The pinned x402 v2 specification defines verify as read-only. It checks an authorization without committing payment state. Settle is a separate operation whose effect depends on the selected scheme and payment flow. An isValid response therefore cannot substitute for the applicable settlement evidence.

Source: X402 Protocol Specification. Documentation checked 2026-10-24; no deployment validation is claimed.

Evidence area: Agent Payments, Authority & Transaction Evidence

Evidence to request before relying on this claim

Claim to check: Does an x402 v2 successful verify response establish that funds have moved?

Buyer evidence still required

  • Selected scheme, network and payment flow
  • Verification response and matching settlement record
  • Resource request and entitlement correlation

Review inference: Release a paid API result only against the payment state required by its agreed flow. This is a review decision, not an observed buyer result.

Suggested review condition: Do not classify read-only verification as a completed transfer.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer network, actual transfer and delivered resource have not been observed.

Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.

Recheck: A saved purchase does not recheck the source or buyer configuration. Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome.

Free exact HTTP publication only. Original record metadata retains proposed saved-evidence context; paid saving and MCP access are not activated for this record.

Claim boundaries
  • Independent verification of payment, delivery or deployed controls
  • The buyer network, actual transfer and delivered resource have not been observed.
  • Buyer deployment testing, live runtime enforcement, certification or permission to act
  • Expanded capabilities or licences for existing INDEX executables

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

Free exact HTTP publication only; outside MCP/search and paid saved retrieval.

Machine-readable record · Free publication and exact preview

External documentation review

Zapier MCP: Dynamic tool discovery and cross-app actions

Question: What should I check before a Zapier agent can discover tools and take actions across connected apps?

Zapier MCP uses connected-app actions and can discover and enable tools during a conversation. A fixed tool list is an alternative. Review the discovery mode, app identities and authorization for each destination; successful calls also consume the existing Zapier task allowance.

Source: Zapier MCP tool selection and client connection. Documentation checked 2026-10-14; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Zapier hosted MCP with app connections; dynamic or manually fixed tool discovery

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Zapier operates the hosted MCP service.

Documented by publisher. Zapier MCP tool selection and client connection; Zapier MCP task consumption

Purpose

It connects agent requests to actions in configured applications.

Documented by publisher. Zapier MCP tool selection and client connection; Zapier MCP task consumption

Read capability

Available actions can search or find application records.

Documented by publisher. Zapier MCP tool selection and client connection; Zapier MCP task consumption

Write capability

Available actions can send messages and create or update records in connected apps.

Documented by publisher. Zapier MCP tool selection and client connection; Zapier MCP task consumption

Authentication

Most clients connect using OAuth; tools run through Zapier app connections.

Documented by publisher. Zapier MCP tool selection and client connection; Zapier MCP task consumption

Permission surface

Dynamic discovery can enable tools during use; manual selection supports a fixed tool set.

Documented by publisher. Zapier MCP tool selection and client connection; Zapier MCP task consumption

Data leaving the environment

A cross-app workflow can move information from one connected service through the client to another.

Review inference. Zapier MCP tool selection and client connection; Zapier MCP task consumption

Failure modes to consider

Discovery can expand a tool list, a wrong app connection can target another account, and retries may consume additional tasks.

Review inference. Zapier MCP tool selection and client connection; Zapier MCP task consumption

Unknowns and applicability

Configured connections, effective workspace controls, budget and human approval behavior are unverified.

Not established

Suggested refusal or clarification condition

Resolve the app identity and permission for each write or external message before execution.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Recheck enabled discovery, app connections, shared-server access and task charging.

Record history: 2026-10-14 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Retain the approved destinations and discovery assumptions for a cross-app workflow.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Zendesk: Protecting a ticket update from stale state

Question: Can an agent overwrite a newer Zendesk ticket update using an old preview?

Zendesk documents safe updates using safe_update with the last known updated_stamp. A newer ticket change can cause the attempted update to be rejected; the client must obtain fresh state and handle the conflict. An earlier preview is not proof that the ticket remains unchanged.

Source: Zendesk: Creating and updating tickets. Documentation checked 2026-10-17; no deployment validation is claimed.

Evidence to request before relying on this claim

Claim to check: Can an agent overwrite a newer Zendesk ticket update using an old preview?

Buyer evidence still required

  • Ticket identity and last observed update timestamp.
  • Safe-update fields in the intended operation.
  • Conflict response and refreshed state before another attempt.

Suggested review condition: Reconcile a conflicting update with the authorised intent before resubmitting.

This condition is a VAREXIS review rule, not a statement of the vendor's policy.

The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.

Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.

Recheck: A saved purchase does not recheck the source or buyer configuration. Ticket revision, safe-update mode, concurrent changes and authorised edit.

Optional saved evidence: Save the concurrency assumptions behind an automated support action.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. The publisher documentation can change; a purchase does not refresh it.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt

External documentation review

Zoom MCP: Meeting reads and content creation use different scopes

Question: Does connecting Zoom MCP give an agent only meeting search?

The publisher lists default meeting, recording and content tools, including file creation. Dedicated product endpoints expose different tool sets and granular scopes. Authentication mode alone does not establish parity across tools or tokens; requested content and write operations must match the granted scope.

Source: Zoom MCP server reference. Documentation checked 2026-10-16; no deployment validation is claimed.

Read the complete tool trust profile

Review scope: Default hosted server; dedicated product servers reviewed as distinct

Dated rolling documentation snapshot; no installed or hosted runtime version independently verified. Buyer plan, entitlement and effective configuration are not verified.

Publisher and operator

Zoom publishes the hosted server family.

Documented by publisher. Zoom MCP server reference; Zoom MCP OAuth setup

Purpose

Retrieve meeting assets and perform selected content operations.

Documented by publisher. Zoom MCP server reference; Zoom MCP OAuth setup

Read capability

Authorized meeting, recording and file information.

Documented by publisher. Zoom MCP server reference; Zoom MCP OAuth setup

Write capability

Default content creation and product-specific mutations.

Documented by publisher. Zoom MCP server reference; Zoom MCP OAuth setup

Authentication

OAuth setup with tool-specific scopes.

Documented by publisher. Zoom MCP server reference; Zoom MCP OAuth setup

Permission surface

Server variant, token type and granular scope.

Documented by publisher. Zoom MCP server reference; Zoom MCP OAuth setup

Data leaving the environment

Meeting and file content can reach the agent client.

Review inference. Zoom MCP server reference; Zoom MCP OAuth setup

Failure modes to consider

Wrong product endpoint or missing scope can produce partial capability.

Review inference. Zoom MCP server reference; Zoom MCP OAuth setup

Unknowns and applicability

Buyer token, consent, retention and actual tool inventory are unverified.

Not established

Suggested refusal or clarification condition

Do not infer content-write or collaborator authority from meeting access.

Suggested VAREXIS review condition

Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.

A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.

Recheck: Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation. Product endpoint tool sets, scope requirements and token support.

Record history: 2026-10-16 - v1: Initial documentation review; no earlier vendor assessment claimed.

Optional saved record: Preserve the exact product and content permissions behind a Zoom integration.

Single purchase: Existing server-saved version-bound route snapshot for later authenticated retrieval.

Evidence Receipt: The same snapshot plus the existing unsigned delivery receipt.

Hashes identify content versions; they do not prove truth or provide a signature.

Source response hashes and review dates are included in the JSON. Original publisher pages may change; full copies of those pages are not sold or republished here.

Claim boundaries
  • Verified buyer configuration or effective access rights
  • Independent execution, completeness or security testing
  • Vendor certification, legal compliance or guaranteed suitability

VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.

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.

Machine-readable record · Request an answer or receipt