Feature. The Evidence Orchestrator
The Article 39.14 (the Texas rule requiring the State to hand over its evidence to the defense) Native-File Metadata Posture. A Product Posture, Not Legal Advice.
On the benchmark run, The Evidence Orchestrator’s metadata-extraction layer detected, on every MP4 body-camera file the State produced in discovery, an FFmpeg libavformat encoder signature reading Lavf55.33.100 and absent embedded GPS atoms. The platform did not infer the condition. It detected the file-level metadata signature. The product capability that follows is technical: metadata-integrity detection, automated demand-template insertion, demand tracking, State-response logging, and, under explicit firm consent, cross-matter aggregation.
AI On This Page
Buddy Preserves Metadata, Provenance, And Review State Through The Production Set.
Buddy is The IMC Machine’s AI assistant. Talk, upload, or speak – Buddy turns what you send into structured records you approve before anything moves.
Talk To Buddy
“Prepare The 39.14 Production For Matter 2026-0419”
Buddy assembles the production with full metadata and review state preserved on every file.
Upload A Photo
Drop The Prosecutor’s Discovery Checklist.
Buddy reads the checklist and cross-checks the production against each listed item.
Voice Note
Voice-Confirm The Production Ready State.
Buddy logs the named attorney’s release with a timestamp and a copy of the voice confirmation.
Buddy autofills are reviewable. Nothing publishes, files, or sends without a named human approval on the record.
The detection layer
What The Platform Actually Reads Off The File.
Every MP4 body-camera file that lands in a matter’s evidence tree passes through a metadata-extraction step before the worksheet opens. The step reads the file container itself. The encoder signature recorded by whatever tool last wrote the file, the presence or absence of embedded GPS atoms (GPMF as written by GoPro-family cameras, ©xyz as written by Apple devices, CLLI as written by certain industrial cameras), the presence or absence of vehicle-telemetry atoms. On the benchmark run, the layer detected the same condition on every MP4 the State produced. Encoder signature Lavf55.33.100, an FFmpeg libavformat tag indicating the file had been rewritten through a re-encode pass, with the embedded GPS and telemetry atoms absent. Axon’s own help documentation confirms that GPS coordinates and vehicle telemetry are not displayed when sharing through the copy flow; the unstripped native file is accessible only through a separate Download Original pathway that is permission-gated to agency users.
The demand-template lane
What The Product Capability Does Next.
Capability 01
Demand-Template Insertion
When the metadata-integrity detection raises a flag, the demand-template lane offers the attorney a draft pre-populated against the specific condition the file presented. The draft names the original native Axon file, the embedded metadata expected on that file, a request for written confirmation of the Download Original pathway, a request for the evidence.com audit logs, and a request for a written explanation if the agency declines native production. The language is templated; the case-specific particulars are filled from the matter record.
Capability 02
Demand Tracking
Each demand the firm sends is tracked on the matter. When it was sent, to whom, in response to which file, what specific request it made, what the demand’s serve date was, and what the response deadline is. The tracking surface is the firm’s, not a public dashboard. It feeds the firm’s docket and the matter’s deadlines lane.
Capability 03
State-Response Logging
When the State responds (with the original native file, with a partial production, with a refusal, or with silence past the deadline), the response is logged on the matter, attached to the originating demand, and available in the chain-of-custody record for the file under review. Refusals are logged with the State’s reason where given. The firm has an audit-ready record of what was asked and what was returned.
Capability 04
Cross-Matter Aggregation, On Consent
Across matters within a firm, the platform can aggregate the metadata-integrity record. How often the encoder signature pattern recurs, how often native production is refused, how response timing varies. Any cross-firm aggregation requires explicit firm consent and confidentiality safeguards. Aggregation is off by default; the firm opts in.
Capability 05
Source-Anchored Citations
Every claim the demand template makes about the file traces back to a per-file metadata record the attorney can inspect: the actual encoder signature, the actual list of atoms read off the container, the actual timestamps the platform extracted. The attorney is not asked to take the platform’s word for what the file contained. The platform shows them the read.
Posture
Product, Not Legal Opinion
This is a technical capability for the firm to use under its own legal judgment. The platform detects, drafts, tracks, and logs. The attorney decides whether the file’s condition warrants a demand, what to argue, and what to do if the State refuses. The legal framing lives in the Texas Compliance Framework for AI-Assisted Criminal Defense Practice (May 14, 2026), not on this page.
How it fits the source-of-truth partition
The Lane Operates Entirely Inside The Firm’s Authentication.
The metadata-detection step runs on the file the platform already pulled into the matter’s Drive tree through the Axon Download Orchestration Lane. The demand-tracking surface lives in The Evidence Orchestrator alongside the file under review. State responses are logged on the matter the same way other casework events are logged. Cross-matter aggregation, where the firm has opted in, draws from the firm’s own matters under firm authentication, not from a multi-firm pool.
- Google Drive remains the canonical home of the file and the demand PDF.
- A practice-management system remains the canonical home of matter identity and deadlines.
- Supabase and the Evidence Review Portal hold the demand-tracking and response-log state under row-level-security policies and allowlisted casework access.
- None of this is SOC 2, CJIS, or HIPAA compliance. No formal audit exists. Implemented guardrails include server-side credential handling, row-level-security policies, allowlisted casework access, and audit-ready records. Any production deployment requires firm-specific security review before launch.
See the metadata lane on a live file
A Thirty-Minute Walkthrough Of The Detection, The Draft, And The Response Log.
Bring an Axon body-camera file from a current Bexar or comparable-metro matter. We will show you what the platform reads off the container, what the draft demand looks like populated against that file, and how the State-response log presents in the matter record.
Why This Matters
Read The File’s Own Signature First.
Texas Code of Criminal Procedure Article 39.14, the Michael Morton Act, places the disclosure duty on the State8. Watkins v. State (2021) and a 2025 remedies clarification widened what ‘material’ means and what courts can do when the duty is breached8. With one police department reporting a 600% increase in audio and video evidence over five years4, the production stack itself becomes the discovery surface. On the benchmark run, the Orchestrator’s metadata-extraction layer detected, on every MP4 body-camera file the State produced, an FFmpeg libavformat encoder signature reading Lavf55.33.100 and absent embedded GPS atoms. The platform did not infer the condition, it read the file container itself. The product capability that follows is technical: metadata-integrity detection, automated demand-template insertion, demand tracking, State-response logging, and, under explicit firm consent, cross-matter aggregation.
Sources
Where The Numbers Came From.
Sources and citations
- RAND / NCSC / ABA, National Public Defense Workload Study (2023). rand.org; ABA Journal coverage.
- Sixth Amendment Center, State of the Nation on Gideon’s 60th; Bureau of Justice Statistics, State Government Indigent Defense Expenditures.
- Texas Tribune, Feb. 27, 2025; SMU Dedman / Deason Center, “Country Justice in Texas.”
- Colorado Public Radio, Jan. 2, 2026; The Journal.
- National Registry of Exonerations, 2024 Annual Report. DPIC coverage; Registry homepage.
- Zealous Advocate, $156M paid to Texas exonerees since 2009.
- Three-Model Consensus aligns with the Attorney Approval Ceremony; reviewable framework. See ABA Standing Committee on Legal Aid and Indigent Defendants.
- Texas Code of Criminal Procedure Article 39.14; Watkins v. State (2021) analysis; 2025 remedies update.
Learn This Product
Want the working order, in a course?
Continue Learning
Learn The Evidence Orchestrator
Five sequential modules on defense-side evidence preparation: the matter record, multi-format intake, the Cockpit, the three-model consensus gate, and the Article 39.14 native-file posture.
Open The Course →Continue Learning
Learn The Issue Spotter
Five sequential modules on defense-side motion practice: the firm-control premise, the dismissal pathway library, evidence-to-motion drafting, the six-state lifecycle, and the attorney approval ceremony.
Open The Course →