LiquiLens Evidence Carrier

LiquiLens Evidence Carrier

LiquiLens Evidence Carrier is a transport-neutral contract for moving financial evidence through files, warehouses, event buses, observability systems, data catalogs, FDC3 desktops, notebooks, citations, and AI agents without dropping provenance, rights, freshness, or authority boundaries.

The carrier is infrastructure for inspection and reproducibility. It is not an order, recommendation, credit rating, market-data entitlement, or endorsement by Bloomberg, LSEG, FactSet, FINOS, or any other platform.

The current signed and published core release is v0.19.0. Annotated tag object c3239bfc7c4d3c4b7fc5ce26e0f602962e7d4337 targets the allowlisted SSH-signed release commit 8f5738c9e77cc95b9a68543d478b9521f5595d61, tree acca6fa7aab75ebc91bf044e153c6468cd6f9c0c; remote main resolved to the same commit when the receipt was verified. The exact commit passed preflight run 33630656569, and release run 33630790150 published 23 assets at 2026-09-02T12:36:19Z. All 22 entries in the downloaded SHA256SUMS passed; its SHA-256 is c6d52cbf8794db6e478e3b2ea9e1ed8eee7757137650892a6a96fcbb839bb6bc. Attestation 44695012 binds the 22 non-manifest artifacts to the tagged source. The official MCP Registry record is active/latest at 0.19.0 and pins MCPB SHA-256 11db11aefafcc6c4ba558877d1f9892fc708150b3afbaa28a741e74435b9a91a.

Release v0.19.0 preserves every Trade Safety v1 schema byte and adds the deterministic adversarial corpus, dependency-free TypeScript-compatible Node raw-UTF8 verifier and authenticated paper-only order guard, OpenBB 0.2.0 hash-only verification, and MCP corpus discovery. Gateway 0.1.2 pins core 0.19.0 and remains a read-only, hash-only sandbox with no broker route. Container run 33630789998 published and smoke-tested the core multi-platform index at sha256:bdbfed2afa87f25e8ef88dffeb4ba7ab198854705528c0de5abe31552a170b9a; attestation 44695462 binds that digest to the tagged source. Separately, gateway run 33630790011 published and smoke-tested gateway index sha256:b5c43013da1fdddd9e6e56cab0e4f0f562e39ab25cc640869c5008e3457218e3; attestation 44695195 binds it to the same commit. These are package and registry artifacts, not a hosted gateway, live-order activation, or financial authority.

A later independent gateway-only publication used signed annotated tag trade-safety-gateway-v0.1.3, tag object 757c18928c8036910ab50c80ec073679d7434abf, targeting signed commit fa8e25ae8e0e992611706b8d66e951342d594243 and tree 7680694bf3397a0844f2388fb29067ff402f066d. Gateway run 33651560380 published and smoke-tested the amd64/arm64 index sha256:9b8f704547ecf6c43039b34149d6cca842de5d66cba13c040199cf5f3f216d61; attestation 44751184 binds that digest to the tagged source. The run recorded semantic, source-commit, and signed-tag-object aliases without moving latest or a core-* alias. There is no corresponding GitHub Release object and no hosted deployment or paid-route activation is claimed. See the exact gateway 0.1.3 publication receipt.

See docs/RELEASE-0.19.0.md for the complete release, Registry, artifact, and OCI receipt. GitHub reports the Release record itself as immutable: false; version-tag ruleset 21288366 blocks v* tag update and deletion with no bypass, and the current assets are checksum- and transparency-attested, but they are not described as platform-enforced immutable assets. The complete historical v0.18.0 receipt remains docs/RELEASE-0.18.0.md.

The immutable annotated v0.17.0 tag object cb85e527c2b74abf476fd9a01b73b2235ce976b7 targets protected-main merge edde9b92ad9851d2974b91326a8c3877f4386d3a, but its release run 33585764285 failed at the commit-signature gate before any artifact was built, attested, or published. There is no v0.17.0 GitHub release or official MCP Registry record. See docs/RELEASE-0.17.1.md for the unchanged recovery receipt and docs/RELEASE-0.17.0.md for the unchanged failed-attempt record.

Why it travels

One verified JSON object can be embedded in:

• FDC3 contexts and app-directory workflows;
• CloudEvents and OpenTelemetry logs;
• OpenLineage custom facets and data catalogs;
• Arrow or Parquet schema metadata;
• dbt warehouse tests, CSV, SQL, and spreadsheets;
• CSL-JSON citations and PROV-O knowledge graphs; and
• MCP or other agent responses.

Every full carrier preserves event_time <= knowledge_time <= as_of, source hashes, explicit redistribution rights, a content-derived identity, and an all-false execution/recommendation/credit-rating boundary. Restricted or unknown rights fail closed; incomplete or expired evidence is redacted to a separately identified reference rather than silently upgraded.

Install and verify

The installation guide covers ordinary conda-forge 0.15.0, the listed Dev Container Feature (Carrier 0.14.0), and SchemaStore editor setup. Those channels have their own versions; use the signed 0.19.0 wheel below for the current core release and Trade Safety verification.

# Source checkout (main may contain post-release documentation)
uv sync --locked
uv run liquilens-evidence --help

# Signed v0.19.0 wheel; checksum verified against the release manifest
python -m pip install 'https://github.com/beepboop2025/liquilens-evidence-carrier/releases/download/v0.19.0/liquilens_evidence-0.19.0-py3-none-any.whl#sha256=1adccb72376f50456fd16a979e372f802ae73ba35b766633bc3d8bd4ab5abcc8'
liquilens-evidence issue examples/descriptor.json > carrier.json
liquilens-evidence verify carrier.json --as-of 2026-08-24T12:00:00Z
liquilens-evidence convert carrier.json --format fdc3

Published release v0.19.0 provides a wheel and checksum manifest. The Python runtime has no third-party dependencies. A Node.js verifier is also included for cross-language liquilens-hash-tree-v1 identity checks:

node protocol/verify_hash_tree_v1.mjs --artifact evidence-carrier carrier.json
node protocol/verify_hash_tree_v1.mjs --artifact fleet-brief fleet-brief.json
node protocol/verify_hash_tree_v1.mjs --artifact trade-safety-receipt receipt.json

Canonical contract identities

Contract	Canonical identity	Availability at this source checkpoint
Full carrier	https://liquilens.in/protocol/liquilens-evidence-carrier-v1.schema.json	Published and hosted
Redacted reference	https://liquilens.in/protocol/liquilens-evidence-carrier-reference-v1.schema.json	Published and hosted
Four-product fleet brief	https://liquilens.in/protocol/liquilens-fleet-brief-v1.schema.json	Published and hosted
Trade Safety request	https://liquilens.in/protocol/liquilens-trade-safety-request-v1.schema.json	Published v0.19.0 release asset and canonically hosted
Trade Safety policy	https://liquilens.in/protocol/liquilens-trade-safety-policy-v1.schema.json	Published v0.19.0 release asset and canonically hosted
Broker preview reference	https://liquilens.in/protocol/liquilens-broker-preview-reference-v1.schema.json	Published v0.19.0 release asset and canonically hosted
Trade Safety receipt	https://liquilens.in/protocol/liquilens-trade-safety-receipt-v1.schema.json	Published v0.19.0 release asset and canonically hosted
FDC3 Trade Safety receipt	https://liquilens.in/protocol/fdc3/com.liquilens.trade-safety-receipt.schema.json	Published v0.19.0 release asset and canonically hosted
FDC3 context	https://liquilens.in/protocol/fdc3/com.liquilens.evidence.schema.json	Published and hosted
OpenLineage facet	https://liquilens.in/protocol/openlineage/liquilens-evidence-facet.schema.json	Published and hosted

The five Trade Safety identities above are stable schema $id values. LiquiLens Pages run 33592149926 succeeded at 2026-09-02T04:49:12Z for site revision 3ec660175c81c5b282715ee400eea2f771dc2610; its post-deploy gate retrieved all five URLs over HTTPS and matched their exact bytes to the hashes in protocol/catalog.json. This is schema-hosting proof, not a hosted Trade Safety gateway or live-order activation receipt.

The current contracts are v1. Release v0.17.1 added Trade Safety without changing the previously published Carrier or Fleet Brief semantics. Release v0.19.0 preserves the v1 schema bytes and extends cross-language verification; it does not create a new protocol identity. The signed release workflow is run 33630790150, the wheel SHA-256 is 1adccb72376f50456fd16a979e372f802ae73ba35b766633bc3d8bd4ab5abcc8, and the MCPB SHA-256 is 11db11aefafcc6c4ba558877d1f9892fc708150b3afbaa28a741e74435b9a91a. Production integrations can pin v0.19.0; separately released container, skill, plugin, browser, and package-manager channels retain their own verified versions. The canonical URLs are now available for public schema discovery.

Order-bound Trade Safety Receipts

liquilens.trade-safety-receipt.v1 composes independent Seiche funding/system context, Undertow position-sized exit context, optional LiquiLens institution context, an operator-authored policy, and a broker-preview reference into one short-lived receipt bound to one exact proposed order. Missing, stale, restricted, mismatched, or future-dated inputs fail closed.

liquilens-evidence issue-trade-safety \
  --request examples/trade-safety/request.paper.json \
  --evidence examples/trade-safety/evidence.paper.json \
  --policy examples/trade-safety/policy.paper.json \
  --broker-preview examples/trade-safety/broker-preview.paper.json \
  --issuer examples/trade-safety/issuer.paper.json \
  --as-of 2026-09-02T12:00:00Z > receipt.json

liquilens-evidence verify-trade-safety receipt.json \
  --as-of 2026-09-02T12:00:30Z

A hash-only receipt supports observation and paper conformance. A live pass requires tenant-local authenticated integrity, real-money-eligible required evidence, an executable Undertow quote, and an unexpired broker preview bound to the same request and account. Current public adapters satisfy none of those live gates. A pass is not advice, broker approval, or an execution instruction; the immutable authority object keeps execution, recommendation, allocation, credit-rating, and executable-quote authority false. See docs/TRADE-SAFETY-RECEIPT-V1.md, the adoption plan, and the read-only sandbox gateway.

The gateway 0.2.0 source candidate adds a server-owned policy floor and an optional x402 v2/Bazaar access route for AI agents. Payment purchases access to the exact receipt only; it never relaxes policy, changes an outcome, extends evidence freshness, or becomes execution authority. x402 is disabled without a complete operator configuration, and no hosted 0.2.0 activation or paid-use claim is made here. See the x402 operating contract and traction measurement contract.

Python broker and agent runtimes can place the fail-closed, paper-only before_order guard around their only submit callable. Its agent-facing gateway requires tenant-authenticated HMAC receipts, so a missing, expired, mismatched, cross-account, or non-pass receipt never reaches broker code. A configured claim store blocks receipt replay; use a durable operator-owned store outside local paper/demo runs. Live submission remains held until the broker idempotency and uncertain-outcome reconciliation gates are complete.

TypeScript and Node consumers can use the zero-runtime-dependency @liquilens/trade-safety package. Its authoritative APIs consume raw UTF-8 bytes so 1000 and 1000.0 retain their different protocol identities, and it rejects malformed UTF-8, duplicate keys, tamper, cross-context use, expiry, replay, and every live request before the paper submit callback. The committed corpus and threat model are documented in TRADE-SAFETY-CONFORMANCE.md.

Four-product fleet briefs

liquilens.fleet-brief.v1 bundles already-issued native carriers without flattening LiquiLens, Seiche, Undertow, and Palimpsest into one score. Each brief contains exactly one rights-aware section per product and explicitly preserves full, metadata_only, unavailable, rejected, or missing state.

liquilens-evidence issue-brief \
  --liquilens ./liquilens.carrier.json \
  --seiche ./seiche.carrier.json \
  --undertow ./undertow.carrier.json \
  --palimpsest ./palimpsest.carrier.json \
  --as-of 2026-08-25T00:00:00Z > fleet-brief.json

liquilens-evidence verify-brief fleet-brief.json \
  --as-of 2026-08-25T00:00:00Z

Issuance performs no discovery or network fetch. A product mismatch, duplicate, unknown field, or tampered carrier fails closed. Rejected rights never disclose source metadata or payload. See docs/FLEET-BRIEF-V1.md for the complete contract.

Offline MCP server

The package includes a zero-third-party-dependency stdio server for agents that need to inspect local carrier JSON. It implements current stateless MCP 2026-07-28 (including server/discover) and the latest initialization-based revision, 2025-11-25, for existing clients.

{
  "mcpServers": {
    "liquilens-evidence-carrier": {
      "command": "liquilens-evidence-mcp",
      "args": ["--root", "/absolute/path/to/evidence"]
    }
  }
}

The published v0.19.0 release exposes four read-only tools:

• verify_carrier verifies the content identity, clocks, rights, and export disposition of one explicit JSON path below the configured root.
• project_carrier applies an existing rights-aware projection (fdc3, cloudevent, otel, openlineage, jsonld, csl, flat, or arrow).
• verify_fleet_brief verifies one local four-product brief at its exact recorded evaluation clock without returning embedded evidence bodies.
• verify_trade_safety_receipt verifies one local hash-only order-bound receipt. It accepts no secret; HMAC/live receipts fail closed and must be verified inside the tenant boundary.

It never fetches network data, expands restricted rights, recommends, rates credit, or executes a financial action. The published v0.19.0 GitHub release carries the checksum-pinned liquilens-evidence-carrier-mcp-0.19.0.mcpb bundle for compatible desktop clients. Registry identity: io.github.beepboop2025/liquilens-evidence-carrier.

Integration kit

• docs/EVIDENCE-CARRIER-V1.md defines the contract, rights routing, transports, and failure modes.
• docs/FLEET-BRIEF-V1.md defines deterministic, rights-aware four-product briefs and their five explicit section states.
• docs/TRADE-SAFETY-RECEIPT-V1.md defines strict order, policy, evidence, broker-preview, receipt and verification semantics; the companion adoption plan separates discovery from enforcement.
• docs/TRADE-SAFETY-X402.md defines optional paid access, Bazaar discovery, durable replay/reconciliation, and activation gates; docs/TRADE-SAFETY-TRACTION.md keeps reach, activation, settlement, release, protected orders, payers, and revenue as separate evidence layers.
• CHANGELOG.md, the v0.19.0 publication receipt, the preserved v0.18.0 receipt, and the unchanged v0.17.1 recovery receipt separate current release facts from immutable history and independently versioned channels.
• integrations/fdc3 contains the custom financial-desktop context schema.
• integrations/openlineage contains the custom lineage facet schema.
• dbt_project.yml and macros make the repository directly installable as a dbt package. The mirrored integrations/dbt directory remains available for integration-bundle consumers.
• protocol/verify_hash_tree_v1.mjs verifies content identities without trusting Python number formatting.

Inherit verification in existing workflows

Pin the reusable action to an exact release tag:

- uses: beepboop2025/liquilens-evidence-carrier@v0.19.0
  with:
    path: evidence/close.evidence.json

For local commit gates, add this repository to .pre-commit-config.yaml. The published hook verifies files ending in .evidence.json or .carrier.json and passes every matched file through liquilens-evidence verify-files.

Use in another product

1. Issue the carrier at the boundary where the evidence and its rights are known.
2. Verify before every disclosure or conversion.
3. Preserve the raw carrier plus carrier_id and record_hash at materialized boundaries.
4. Treat missing carrier metadata as a failure, not as permission to use a naked number.
5. Add a product-specific adapter and golden vector; do not fork the core temporal or authority semantics.

Provenance and license

Protocol artifact SHA-256 values are recorded in protocol/catalog.json. The original carrier, reference, FDC3, and OpenLineage contracts retain their established identities; the Fleet Brief and Trade Safety v1 schemas are additive. This public repository is the redistribution boundary for the carrier kit; private research code and datasets are not included.

Code, schemas, documentation, and integration assets in this repository are licensed under Apache‑2.0. Provider data carried inside an evidence object retains its own rights and license; this repository's license does not grant rights to third-party data or product trademarks.