Register 09 · Compliance controls

FRE 707 (proposed).

Proposed Federal Rule of Evidence 707 would subject machine-generated evidence offered without a sponsoring expert to the same reliability factors as FRE 702(b)–(d) — a Daubert-shaped bar of a reliable method, reliably applied. The evidence record proves: Distinctness, drift, and coherence run against the fleet under test, sealed in a Merkle-rooted, SHA-256-pinned record

register 09 · Compliance controls· Evidence / professional-responsibility rule

Reviewed 2026-07-08

01 ·

What this is.

Seventy-two regulatory cite-anchors, organized for evidence lookup and review

Use. machine-generated evidence · Rule-702-grade reliability for AI output (PROPOSED).

Register. 09 · Compliance controls — one of the 17 registers of the PLANiSPHERE corpus library.

02 ·

See it work.

Evidence record you can check — not code you have to trust.

Planisphere measures your tool deployment against FRE 707 (proposed) and seals the result into a signed, Merkle-rooted evidence record. The grade recomputes on your own hardware; the model state never crosses the boundary.

03 ·

Promise. compliance

The contract this mark binds — derived, not asserted.

FRE 707 (proposed) sets the bar an AI output must clear before a tribunal or a client relies on it — reliability, candor, competence. Planisphere supplies the reliability record: a reproducible measurement of the system that produced the output, the thing the rule says you must be able to show.

Answers: How does FRE 707 (proposed) treat AI-generated work, and what record supports review?

04 ·

What it requires.

The obligation this regime imposes — and the honest ceiling. Evidence / professional-responsibility rule

Proposed Federal Rule of Evidence 707 would subject machine-generated evidence offered without a sponsoring expert to the same reliability factors as FRE 702(b)–(d) — a Daubert-shaped bar of a reliable method, reliably applied. The rule is PROPOSED and not yet effective: advanced by the Advisory Committee on Evidence Rules 2025-05-02, public comment closed 2026-02-16, a final report is expected June 2026, and the earliest possible effective date is 2027-12-01. Until then it binds no one, but it signals the reliability foundation courts will expect of standalone AI evidence.

What the evidence record proves.

  • Distinctness, drift, and coherence run against the fleet under test, sealed in a Merkle-rooted, SHA-256-pinned record
  • Any party can recompute the record byte-for-byte
  • Documents method reliability and application stability — the empirical record a 702/707-shaped reliability inquiry runs on
  • Includes the 5-axis battery alongside the audit triad
  • Produces the reliability record before the evidence is offered, not after a challenge

What this does not prove. Planisphere does not opine that any specific output is admissible — admissibility is the court's gatekeeping call — and does not certify a tool '707-compliant,' since Rule 707 is proposed and not yet in effect. It measures model behaviour and emits a reproducible reliability record; counsel and the court decide what it proves. Not legal advice.

Cite-anchor: Proposed Federal Rule of Evidence 707 — machine-generated evidence (PROPOSED, not yet effective) · Imports FRE 702(b)–(d) reliability factors; comment closed 2026-02-16, earliest effective 2027-12-01

06 ·

The record this pin expects.

Related marks, and the surface this one funnels to.
07 ·

Routes here from.

Where this mark is referenced in the Planisphere surface.

Any internal link in the Planisphere site that names "FRE 707 (proposed)" canonicalises here.

See the record FRE 707 (proposed) asks for.

The console shows the evidence; the docs show the endpoints; the briefing shows what the product does and does not claim.

API ·

When FRE 707 (proposed) asks for proof, hand over records — not assurances.

record the duty · seal the receipt · verify offline

Planisphere records each duty event — an output marked, a disclosure shown, a review made — and seals it into a receipt that verifies offline against our published keys. You send hashes, never content. A record is evidence a third party can check; it is not a certification and not a legal determination.

See how a record is checked · See the law Toolkit →