PlatformFiles
Hundreds of sheets in.
One exact spot out.
Permit sets are the format general-purpose AI handles worst: hundreds of sheets, dense schedules, drawings that mean more than their captions. Ichi reads the whole set the way a reviewer does, and remembers where everything is.
A0.10 · Code data & occupancy
Occupancy B / S-1 · Type V-B · sprinklered
Reading the whole set. Not a summary of the first few pages — every sheet is opened, split into its parts, and filed with the coordinates of what was found. Ask a question 200 sheets later and the answer still knows it came from A0.10.
Split into blocks
A sheet isn't one blob. Every page breaks into its parts — text, tables, schedules, figures, title blocks — and each becomes findable on its own.
Located, not just extracted
Every block keeps its coordinates on the page. That's what makes a citation honest: it opens the sheet and points at the spot, instead of saying "page 42".
Understood visually
Drawings are indexed as images, not just by the text near them. Search a stair detail and you get the detail — including the ones whose captions say nothing.
Indexed like a set
Sheet indexes are parsed, title blocks read, disciplines recognized. Ask about A2.01 and Ichi knows which sheet that is, what's on it, and what references it.
Files get cited exactly the way code sections do — down to the sheet, and the spot on it. See the whole platform →
Beyond the upload
A file library that compounds.
Reading one set well is table stakes. What matters is what happens when every set, letter, photo and finished document sits in one place that keeps learning.
Your markups stay yours
Redlines, stamps and callouts from Bluebeam or Acrobat are read — and kept apart from the sheet's own content, so a colleague's annotations never pollute what search finds.
Files where they already live
Sync from SharePoint and OneDrive, pull documents from Procore, or upload directly. Folders, versions and archived files are tracked. No second filing system to maintain.
Outputs become inputs
Every artifact Ichi writes is itself a file. Last cycle's comment letter, the approved response matrix, the signed notice — all of it citable on the next job.
Reads improve retroactively
Extraction is versioned. When the reading gets better, existing files are reprocessed in place — the library sharpens without anyone re-uploading a thing.
Questions
What people ask about files.
The rest of the platform.
Files are one part of it. Here's everything else.
Platform overview
How the whole thing fits together: the stack, the workspace, the human sign-off.
Code Compliance
Licensed books, state amendments and local ordinances — the layer every answer stands on.
Artifacts
The finished document: versioned, discussed, shared and exported without leaving Ichi.
Memory
Personal, company, project and jurisdiction knowledge, applied to every answer.
Integrations
Procore, SharePoint, OneDrive, SSO, API and MCP.
Security
Where the data lives, who can reach it, and what we will and won't claim.
Bring the set that breaks other tools.
A real permit set, as issued. We'll upload it on the call and you can ask it anything.