PlatformMemory
The senior who never retires.
Capture once, applied every time.
How this inspector reads the code. Which amendment tripped the last project. Memory makes it institutional instead of personal.
Five layers
Memory has a shape.
Personal
How you write, sign emails, structure plan check comments — applied automatically to your responses.
Company
Firm-wide standards and internal guidance, so twenty people answer like one firm.
Project
Notes, files and decisions that apply while the project is active — and nowhere else.
Client & jurisdiction
How each reviewer, agency or client actually works. The layer that prevents re-learning it every project.
Topic collections
ADU law, zoning overlays — custom knowledge applied selectively across projects.
How it resolves
Code first. Context second. Always in that order.
Answering with memory active
Check official code sources
Apply active memories
Ignore inactive memories
Compose the answer
Ichi acts as an external brain — distilling a vast amount of institutional knowledge into something that's immediately usable, clear, and grounded in real-world practice.
Questions
Predictable by design.
The rest of the platform.
Memory is 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.
Artifacts
The finished document: versioned, discussed, shared and exported without leaving Ichi.
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.
Give your team a memory.
Bring your own documents if you'd like — or we'll use a sample set. Either way, it's the same platform for both sides of the counter.