TRUST / CONTRACT BEHAVIOR

Trust is in
the response.

A healthcare agent should not trust an answer because it sounds certain. It should know what evidence supports the result, when that evidence applied, what remains unknown, and where its authority stops.

The response envelope

The answer is only
one part of the answer.

01 / evidence

Provenance travels

Material values point back to authorized documents, records, transactions, or derived rules.

02 / time

Time stays explicit

When something applied and when it was observed are separate, first-class parts of the result.

03 / uncertainty

Unknown stays valid

Missing, stale, unavailable, conflicting, and false are not interchangeable states.

04 / authority

Actions stay bounded

A contract declares what the result supports, what it cannot establish, and where review belongs.

Truth semantics

Unknown is not false.
Conflicting is not resolved.
Failed is not denied.

known

Available evidence supports the determination, including a supported negative value.

unknown

Available evidence cannot establish the determination.

conflicting

Authorized sources disagree, and the disagreement remains visible.

unresolved

The contract executed, but identity or evidence could not support a domain result.

failed

Validation, authorization, or technical execution failed. No domain conclusion should be inferred.

Deployment boundaries

Trust must be
deployment-specific.

Access, tenancy, data location, retention, subprocessors, audit behavior, human review, and contractual commitments depend on the contract, deployment, customer environment, and governing agreement.

ANY does not use this public page to imply certifications, public availability, universal integrations, or controls that have not been verified for a specific deployment.

The public website is informational. It has no user accounts or clinical workflow. Do not send protected health information, medical records, or urgent care requests through this website or to the public email address.

Contract honesty

Status is part
of the interface.

lifecycle

Proposed, preview, active, deprecated, or retired.

availability

None, private, or public.

artifact maturity

Representative, draft, binding, or normative.

Inspect the current registry metadata

A bounded conversation

Trust the evidence.Question the boundary.

Ask how a specific ANY contract handles source evidence, uncertainty, authority, and deployment controls.

Ask about trust