Applied AI

Buyer-hosted, zero-egress assurance

Run Acceptance-10 in your environment. Get a one-page summary + CT-class, Merkle-anchored receipts. Deeper operational kits are sent only after access approval.

Request a buyer-hosted access window →

Route internally: forward to Preparedness/Safety or Platform/Infra owner.

  • Zero-egress (NIST SP 800-207) • short-TTL creds • heartbeat → suspend/kill
  • CT-class Merkle proofs (RFC 9162-compatible) — transparency without exposing payloads
  • Procurement docs on request (NDA/SOW/1-pager)
Buyer-hosted Zero-egress

See what you’ll get

Independent, buyer-hosted acceptance. Posture public, payload private.

Understand the problem

  • External testing hits privacy & legal walls.
  • Internal demos don’t satisfy T&E / safety / audit.
  • Reviewers want repeatable evidence—without data leaving.

Run in your environment

  • Acceptance-10 executes inside your network.
  • Telemetry budget: counters • times • flags (governance-only).
  • Receive a one-page summary + CSV receipts.

Verify replay receipts

  • Merkle inclusion proofs (CT-class; RFC 9162-compatible).
  • Fields to support determinism %, p95/pmax, veto/kill, UTC/operator, config hash/ID.

Align to Zero Trust & T&E

Zero-Trust rails

  • Default-deny egress
  • Short-TTL creds & per-run auth
  • Heartbeat → suspend/kill
  • NIST SP 800-207

Governance-only

  • Telemetry is counters, times, flags
  • Never raw content, prompts, or weights

Public-sector friendly

  • Artifacts structured to drop into U.S. public-sector AI/T&E intake
  • Program-specific phrasing (CDAO AI T&E, DoD 3000.09) sent after access approval

Verify replay receipts (audit-ready)

We show that verification is possible on this page, but the full verification kit and real receipts are delivered only to identified buyers.

Show verification snippet 
curl -O https://echoclonelabs.com/acceptance10_sample_pack/SHA256SUMS.txt
# Linux:   sha256sum -c SHA256SUMS.txt
# macOS:   shasum -a 256 -c SHA256SUMS.txt
unzip acceptance10_verification_kit_v3_dirproofs.zip
# Example (offline, CT-class / RFC 9162-compatible):
python3 verify_receipt.py --receipt receipts/sample_receipt.json --tree trees/log_tree.json

Each run includes inclusion & consistency proofs (CT-class; RFC 9162-compatible) so you can replay without egress. Full artifacts and any program-specific clause text are mailed after the access window is approved.

Request → Run → Verify → Decide

Straightforward process

Kickoff
NDA (No-Use/No-Derivation), slot, short-TTL access, egress default-deny.
Run
Acceptance-10 inside your environment; governance-only telemetry.
Evidence
One-page + CSV + Merkle receipts; verify offline.
Decision
Next step: mirror/telemetry or program-specific work.

Cross-walk: Evidence maps to NIST AI RMF 1.0. DoD/CDAO phrasing is provided in the private pack.

FAQ

How is this different from governance/guardrail platforms?
We’re not a runtime or policy platform. We run a buyer-hosted, independent evaluation and deliver decision-ready, governance-friendly evidence you can use in your own processes.
What do you deliver?
A one-page, file-ready evidence sheet (timing, repeatability, stop/kill), plus a short cross-walk note for NIST AI RMF. No code, prompts, UIs, thresholds, or model weights leave your custody.
Is this suitable for autonomy/defense programs?
Yes. We operate buyer-side (simulation-only if required), avoid ITAR/EAR technical data on public intake, and we can include DoD- or CDAO-flavored language (e.g. DoD Directive 3000.09, CDAO AI T&E framing) in the private, NDA’d pack.
Which standards do you align to?
NIST SP 800-207 (Zero Trust Architecture); artifacts support filing into NIST AI RMF 1.0; and we reference RFC 9162 for CT-class transparency proofs.

Contact

EchoClone Labs LLC

We typically respond within one business day.

Request buyer-hosted access

Request access →

Standard terms

References available.

Request a buyer-hosted access window →