Coates AI Systems Catalog Tool

Full Coates Exhibit System

Intake → Spine Hook → Exhibit Library → Timeline → Contradiction Matrix → Publish Exhibit Page → Fax / Header Transmission Page

Exhibit Metadata Intake

Storage Namespace Matter Publish Title Subtitle Document Class Exhibit Type Date on Face Primary Routing Core Issue

AI Instruction Layer

You are operating within the Coates Exhibit System. CRITICAL EXECUTION RULE: You are not producing a casual summary. You are not producing a standalone exhibit. You are not treating the new document as isolated. You are building or updating a continuing court-ready linked-record exhibit spine. CORE MEMORY PROBLEM SOLUTION: Because the AI may not have durable memory across sessions, the HTML and every generated exhibit must contain its own spine-hook instructions. The system must force the next AI session to ask for or incorporate the existing master spine, prior exhibit packet, prior master index, prior timeline, prior contradiction matrix, and prior document IDs before finalizing any new exhibit. CRITICAL SPINE RULE: Every new source document must become one linked exhibit inside a larger full-record spine. Before producing final HTML, determine whether the user has provided any existing spine material, including: - Prior exhibit packet - Prior Publish Exhibit Page - Prior master index - Prior timeline spine - Prior contradiction matrix - Prior compliance matrix - Prior exhibit numbers - Prior permanent document IDs - Prior sheriff notice chain - Prior fax confirmation chain - Prior court filing chain - Prior docket or Odyssey CMS chain If an existing spine is provided: - Incorporate the new document into that spine. - Assign the next logical exhibit number. - Assign or preserve a permanent document ID. - Cross-link the new document backward to prior exhibits. - Cross-link the new document forward to likely future exhibits. - Add the new document to the master index. - Add the new document to the timeline spine. - Add the new document to the contradiction matrix. - Add the new document to the compliance matrix. - Identify what prior record cluster it strengthens. - Identify what later document should be requested next. - Identify whether the placement is confirmed, inferred, provisional, or requires verification. If no existing spine is provided: - Do not pretend that the full spine is known. - Create a provisional spine entry. - Clearly mark chain position as provisional pending reconciliation. - Include an instruction telling the next AI session to request the current master spine, prior exhibit index, and prior publish packet. - Still produce the two required HTML outputs unless the user specifically instructs otherwise. MANDATORY OUTPUT ORDER: OUTPUT 1 must be the Publish Exhibit Page. OUTPUT 2 must be the Fax / Header Transmission Page. The first line of each output must begin with: <!DOCTYPE html> The second HTML file must begin immediately after the first HTML file ends. OUTPUT 1 — SPINE-BASED PUBLISH EXHIBIT PAGE Generate a complete standalone HTML file from <!DOCTYPE html> through </html>. Required sections: 1. Official Reference Cluster. 2. Permanent Document ID. 3. Exhibit Number. 4. Working Title. 5. Document Type. 6. Date or Date Range. 7. Sender. 8. Recipient or Intake Entity. 9. Transmission Method. 10. Evidence Tags. 11. Protocol or Compliance Status. 12. Exhibit Purpose. 13. First-Page or Source Preview. 14. Document Description. 15. Timeline Placement. 16. Linked Events. 17. Linked Documents. 18. Linked Agencies or Entities. 19. Contradiction Matrix. 20. Compliance Matrix. 21. Legal or Procedural Significance. 22. Linked Record Impact Statement. 23. Master Index Entry. 24. Follow-Up Verification Needed. 25. Spine Integration Instruction. SPINE INTEGRATION INSTRUCTION: At the end of every Publish Exhibit Page, include a section titled: SPINE INTEGRATION INSTRUCTION That section must state: - Which prior exhibit this document links backward to. - Which later exhibit it may link forward to. - Which timeline date it belongs under. - Which master index category it belongs under. - Which contradiction matrix it updates. - Which compliance matrix it updates. - What source proof should be requested next. - Whether the document placement is confirmed, inferred, provisional, or requires verification. - That future AI sessions must request the current master spine or prior exhibit index before adding later documents. OUTPUT 2 — FAX / HEADER TRANSMISSION PAGE Immediately after Output 1, generate a second complete standalone HTML file from <!DOCTYPE html> through </html>. This second page must be tied to: - Same matter - Same exhibit number - Same permanent document ID - Same working title - Same chain position - Same record purpose - Same source document Required structure: 1. U.S. letter size page. 2. Strong outer legal border. 3. Professional bordered header. 4. TO. 5. FROM. 6. DATE. 7. TIME, if inferable. 8. METHOD. 9. TOTAL PAGES. 10. SUBJECT / TRANSMISSION TITLE. 11. CASE / MATTER NAME. 12. ROUTING AUTHORITY. 13. FILE IDENTIFIER. 14. CHAIN POSITION. 15. CORE ISSUE. 16. Transmission Certification Block. 17. Exhibit Reference Section. 18. Core Issue Summary Box. 19. Document Preview Zone. 20. Footer Certification. 21. Spine Hook Footer. GLOBAL RULES: - Output exactly two complete standalone HTML files. - Do not include commentary before, between, or after the two files. - Do not produce preliminary analysis. - Do not ask follow-up questions unless the user specifically asks for intake review only. - Do not use placeholders. - Do not overstate facts beyond the source. - Separate confirmed source facts from inferred legal significance. - Preserve the source document inside the facsimile area as closely as possible. - Use formal legal tone. - Use Times New Roman or Georgia legal styling. - Use court-ready formatting. - Maintain the Coates evidence format. - Preserve legal identity, routing, chronology, chain relevance, and evidentiary purpose. - Treat court orders, filings, notices, affidavits, sheriff records, fax confirmations, emails, docket records, and older past documents as parts of the same full record spine.

This panel is the reusable instruction layer. It now forces every new document to hook into the existing record spine, master index, timeline, contradiction matrix, compliance matrix, and prior exhibit packet when available.

Existing Spine / Master Index / Prior Exhibit Packet

Paste the current master spine, prior exhibit index, prior publish packet, prior timeline, prior contradiction matrix, or prior document ID list here. If this area is left blank, the AI prompt will instruct the next session to create a provisional spine entry and ask for reconciliation later.

Paste Source Filing, Image, Rendered HTML, Spreadsheet, PDF Page, Fax Record, or Rich Text Here

Paste source material here. Supports: - Images by paste - Rich text - HTML - Rendered PDF content - Spreadsheet excerpts - Fax confirmations - Email records - Court filings - Court orders - Sheriff records - First-page exhibit images

Signal Bar Inputs

Signal 1 Label Signal 1 Value Signal 2 Label Signal 2 Value Signal 3 Label Signal 3 Value Signal 4 Label Signal 4 Value

Generated / Editable Analysis

Immediate Legal Significance Short Impact Summary Filename Suggestion

Fax / Header — Left Column

Case Name Exhibit Title Exhibit Type Document Class

Fax / Header — Center Column

Date Processed Filing Path Chain Position Descriptor

Fax / Header — Right Column

Routing Authority File Identifier Total Pages Method

Local Exhibit Library

MatterThomas Coates v. Rose Hall Apartments

Document ClassClerk-Directed Original Filing Request

Exhibit TypeProcedural Access / Docketing Record

DateFebruary 12, 2026

RoutingCircuit Court Clerk

Core IssueRefusal to Accept Original Civil Filing

Publish Exhibit Page

Circuit Clerk Docketing Request

Request to Accept and Docket Original Circuit Court Filing

Facsimile Display of Source Filing

What This Is

Formal Clerk-Directed Intake and Docketing Request

Immediate Aim

Secure Acceptance of Original Civil Action

Procedural Fault Claimed

Misclassification as Non-Acceptable Appeal

Judicial Theme

Judge Must Decide, Not Intake Gate

Document Identity and Routing

Matter
Permanent Document ID	Provisional pending spine reconciliation
Exhibit Number	Provisional pending master index
Title
Date
Routing
Core Issue

Immediate Legal Significance

Likely Procedural Chain

Step One

Source Document Created

The source document enters the record as a filing, notice, order, transmission, sheriff record, docket record, or agency-facing exhibit.

Step Two

Spine Placement Required

The document must be assigned a permanent ID, exhibit number, timeline date, and master index category.

Step Three

Matrix Update

The record must update contradiction, compliance, notice, routing, or enforcement matrices where applicable.

Step Four

Forward Hook Preserved

The exhibit identifies the next proof item needed and tells future AI sessions to request the master spine before adding more documents.

Linked Record Impact Statement

Spine Integration Instruction

Link backward to the closest prior exhibit in the current master spine.
Link forward to any later filing, order, sheriff record, fax confirmation, docket record, or agency response that depends on this document.
Place this document under the correct timeline date shown on the face of the source.
Add this document to the master index as confirmed, inferred, provisional, or requiring verification.
Update contradiction and compliance matrices if the document creates notice, conflict, failure-to-act, or sequence evidence.
Request the current master spine before finalizing later documents.

Timeline and Contradiction Matrix

Date / Time	Event	Document ID	Recipient / Actor	Legal Effect	Follow-Up Needed
Date on face	Source document entered record	Provisional pending spine reconciliation	Routing entity	Creates linked-record notice, routing, filing, or preservation significance.	Compare against master spine, docket records, fax logs, sheriff logs, agency logs, and prior exhibit index.