PlatformArtifacts
Not a chat answer.
The actual deliverable.
A real document, on your letterhead, in your team's voice — and it lives online. Share it in one click, comment line by line, keep every version. It doesn't get sent and go stale; it stays alive.
What goes in
- 01Your comment-letter templatethe format your department already issues
- 02The review findingsevery issue, with the sheet it came from
- 03Your instructionssaid the way you'd say them out loud
- 04Letters you've signedso the tone matches the last one you sent
You never manage these. The workflow already holds your format, your standards and the documents your team has signed — which is why the draft sounds like you wrote it.
Provide the occupant load calculation for Suite 200 on sheet A0.30, including the function-of-space areas used.CBC 1004.5
Submit the special inspection program for the post-installed anchors shown on S3.01 prior to permit issuance.CBC 1705.3
+ 7 more findings, each cited
Nobody maintains those inputs — they accumulate. See how memory works →
Two ways in
Workflows write them. Conversations rewrite them.
The same document, reachable from either side — which is why a finished artifact is never finished in the unhelpful sense.
A workflow finishes
Plan review, intake, completeness, an RFI — the run ends by writing the document rather than handing you findings to type up. The citations it gathered are already in place.
See the workflows →A conversation turns into one
Ask for something longer than a reply and you get an artifact — then keep talking to it. Restructure the document, renumber every finding, bulk-edit by asking.
How Ichi reads your files →A document with a life
Treated like the record it's about to become.
These documents get served, appealed, audited and archived. So the artifact behaves accordingly — with history, discussion and control that a chat transcript can't offer.
Versioned like code
Every save is a named version with a note on what changed. Roll back, compare, or keep v1 on file for the record while v3 goes out the door.
Discussed like a document
Comments anchor to the exact sentence, carry threads, and resolve. The argument about finding A-1's wording happens on finding A-1, not in a separate email chain.
Edited without fear
Edit in place; unsaved work is held as a draft until you commit it. Ask for a rewrite and only the section you point at regenerates — your edits elsewhere stand.
Polished before it lands
Generation isn't the last step. Every artifact gets a second pass for structure, formatting and consistency — the difference between output and a deliverable.
After it's written
Out the door, and back into the system.
The finished document goes to whoever needs it — and stays useful to whoever writes the next one.
Live, not attached
Every artifact has a stable link your team — or the applicant across the counter — opens in one click. Updates land live, so nobody reviews a stale copy.
A file when you need one
Export to PDF on your letterhead for the record, the packet or the archive. Most teams share the link instead and skip the attachment entirely.
Citations ride along
The code sections and sheet references the document was built from stay in it. Whoever reads it can check any claim against the source — which is what makes it defensible.
Artifacts are files
A finished artifact joins your file library like anything you upload. This cycle's approved letter becomes next cycle's example — the loop that makes every next document better.
What kinds of documents? Comment letters, notices of violation, RFI responses, submittal reviews, intake records, completeness reports — and anything your team produces repeatedly. See the custom workflows →
Questions
What people ask about artifacts.
The rest of the platform.
Artifacts 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.
Files
Plansets read sheet by sheet, every block located, every answer citable to the spot.
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.
Watch a workflow end in a document.
Bring the letter your team dreads writing. We'll run the workflow and you'll leave with the draft.