01
Document intelligence starts at intake, where files are parsed once, sealed, and corrected only with an auditable reason.
Part of the evidence and operations foundation behind OBE.
Proof of work
A public ledger of what we build.
Trust requires more than promises. This feed records what was built, why the architecture exists, and how OBE became a source-backed foundation firms can own instead of rent.
Featured architecture story
One year of building a backend for legal
The OBE foundation exists because AI-first legal case management needs more than a chat window: sealed document parsing, sidecar file systems, entity source-of-truth policies, CaseMaps, scoped sandboxes, and a deployment plan a firm can actually own.
02
Case intelligence builds on CaseMaps that tell sandboxed agents which documents, entities, gaps, and facts exist.
Part of the evidence and operations foundation behind OBE.
03
Entity resolution decides which source controls each fact when contracts, interviews, IDs, and financial records disagree.
Part of the evidence and operations foundation behind OBE.
04
Setup guidance covers containerized services, ports, resource planning, external API keys, and clean scoping.
Part of the evidence and operations foundation behind OBE.
Architecture
Firm controlledOne substrate from evidence to workflow
- 04Firm workflowsReview, phases, approvals
- 03Governed agentsScoped tools and audit trail
- 02Canonical case stateFacts, rules, activity
- 01Source evidenceOriginals, sidecars, citations
The feed
Field notes from the build.
One year of building a backend for legal
The OBE foundation exists because AI-first legal case management needs more than a chat window: sealed document parsing, sidecar file systems, entity source-of-truth policies, CaseMaps, scoped sandboxes, and a deployment plan a firm can actually own.
You’ve reached the end of the ledger.