Encypher Meter · Early partner program

Turn per-answer evidence into a bounded source-use report.

Name: Encypher Meter
Availability: LimitedAvailability

Meter pilots assemble signed-source references, answer-level retrieval evidence, observed events, partner-supplied records, supplied rights terms, and unresolved gaps into one bounded report for rights and licensing review.

Meter in action

See the bounded report take shape

The real Meter reel introduces the early-partner evidence trail behind an answer. The report keeps Encypher-observed events, partner-supplied records, and unresolved gaps separate.

How it works

From one answer event to one bounded report

Per-answer RAG evidence is the atomic input. A source-use report with explicit evidence bounds is the commercial output.

1
Resolve the signed source
Sign the source library with Mark, Seal, or Trace. A Meter pilot uses those provenance identifiers to connect a retrieved passage to its signed source record; final compatibility and migration terms are confirmed with each partner.
2
Supply the answer-level event
For each answer, the partner supplies agreed retrieval, citation, ingestion, or outcome event data. Meter keeps those records separate from verification and crawler events observed by Encypher.
3
Review the bounded report
Both sides review the methodology, the origin of each event, the supplied rights terms, and every unresolved gap before using the report for rights or licensing review.

Bounded report

Review the source-use report, not an unexplained total

The report is useful because its evidence provenance and limits remain attached to every row.

Illustrative report - early partner program

Bounded source-use report

One illustrative per-answer packet, organized for rights and licensing review.

Report reference: MTR-BSR-024
Atomic input: 1 answer event / 1 source passage
Commercial output: Rights and licensing review

Evidence ledger

Signed source
Source record SRC-042, passage 7. The report resolves this reference to the signed source record.
Observed by Encypher
Answer / retrieval event
Answer event ANS-118 links passage 7 to one completed RAG response and its retrieval record.
Supplied by partner
Verification / crawler event
A provenance verification resolved SRC-042; one crawler request carried the same source identifier.
Observed by Encypher
Retrieval, citation, ingestion, or outcome event
The partner record includes retrieval and citation events. It includes no ingestion or downstream outcome event.
Supplied by partner
Supplied rights terms
A rights snapshot and W3C ODRL policy reference travel with the source. The report shows the terms as supplied, not as legal findings.
Supplied by partner
Unresolved gap
No observed or supplied event establishes training or inference use, or any use outside this answer event.
Not established
Review status
The methodology and report bounds are pending review by both parties.
Joint review pending

From evidence to review

Per-answer evidence in. A bounded report out.

Meter pilots keep the atomic RAG event intact while turning it into a commercial review artifact both sides can inspect.

The answer event stays atomic

Each report starts with one answer-level packet: the signed source and passage reference, the retrieval event, the completed response reference, and the origin of each field.

Evidence origin stays explicit

Every event is labeled "Observed by Encypher," "Supplied by partner," or "Not established." Missing evidence remains a visible gap instead of becoming an inferred use claim.

Rights terms stay in bounds

Supplied rights terms sit beside the event record for review. They do not prove ownership, authorization, infringement, notice, willfulness, damages, or compliance.

Methodology travels with the report

Early partners review which events enter the report, who supplied or observed them, and where the report stops. The resulting source-use report is the commercial output.

Why a bounded report

One commercial artifact, with every evidence boundary intact

Meter pilots turn source-level and answer-level records into a report for rights and licensing review without converting incomplete signals into claims about unobserved use.

Anchored where provenance resolves

When an event resolves to Encypher provenance, the report ties it to the signed source record. Partner-supplied events remain separately labeled.

Silent gaps stay visible

The report names missing ingestion, outcome, training, or inference evidence. It never treats a crawler observation or retrieval record as proof of a different event.

Where this fits

Publishers · Music · Stock media · Data licensors

For engineers

Per-answer RAG evidence is the atomic input; the bounded source-use report is the commercial output
Observed Encypher events, partner-supplied events, supplied rights terms, and unresolved gaps remain separate
Pilot methodology and report bounds are reviewed with each early partner

Platform Implementation guide API playground

Review a bounded Meter report with us.

Meter remains an early-partner program with no self-serve path.Partner exchange: The partner supplies agreed event data. Both sides review the methodology, evidence provenance, unresolved gaps, and report bounds.