WYEA / Platform
Platform
A knowledge system that can show you where every answer came from
The system reads the documents your firm already keeps, answers questions against them, and binds each answer to the exact version of the exact file it was found in. Where it cannot find something, it says so.
| Source | Reads | Version identity | Authority |
|---|---|---|---|
| Dropboxfirst adapter | Documents | rev | Yours |
| SharePoint, OneDriveMicrosoft Graph | Documents | driveItemVersion.id | Yours |
| Google Drive | Documents | revisionId | Yours |
| iManage, NetDocuments | Documents | version / subversion | Yours |
| Outlookinbound mail | Mail and attachments | message id | Yours |
| Public court recordshared corpus | Dockets, opinions | corpus revision | Public |
The shape of it
Four parts
Each one exists because of a specific way document systems behave, not because it rounded out a diagram.
Connected sources
Your document store, your mail, and the public record. Your store stays the system of record.
We mirror, we do not own
The platform never becomes a second library your people have to keep in sync. Your store remains the thing that is true.
Providers differ, and it matters
Version durability, digest algorithm, change-feed shape and access control all vary. The connector declares what it can actually promise.
Filenames are not identity
A filename at a firm is often the sensitive part. Path and title never participate in identity or authorization.
Grounding and verification
A quote is located in the source or it does not become an answer.
Exact span, or nothing
The quote is searched for in the source text. Found, it carries its character offsets. Not found, it is flagged.
No confidence score
There is no number between right and wrong for a reviewer to interpret generously at 6pm.
Unreadable is its own answer
If the source could not be opened, the result is not checked. That is different from checked and false.
Evidence and the record
Answers bind to a version identity that comes from your platform, not from us.
There is no WYEA seal
The integrity anchor is your platform's own immutable version identity plus a content hash. We do not ask you to trust a stamp we invented.
Records supersede, never change
A new version, a permission change or a fresh read writes a new record. Nothing is edited in place.
The cache holds only what was claimed
Providers expire old versions. We retain the exact bytes behind claims already made, so an old answer stays checkable.
Isolation
One firm, one cell. There is no shared content plane to leak across.
Own database, network, identity
The per-firm boundary is a real infrastructure boundary, not a tenant column in a shared table.
Nothing pooled
No shared corpus, no cross-firm retrieval, no training on your content. Instances share code and never data.
We publish the limits
WYEA operates the cell. The security page states what that does and does not mean today.
Where it is used
Two lines of work
The system is built around documents, versions and evidence, so the profession sitting on top of it is configuration rather than architecture.
Legal
Matters, served paper, discovery, motions and deadlines, with the public court record and case law connected alongside the firm's own files. This is where the platform started and where most of the domain work sits today.
Insurance
The same reading problem with different paper. Submissions, policies, endorsements and correspondence, where the question is usually what a specific document actually says rather than what someone remembers it saying.
Start a conversation
Tell us what your people spend the day reading.
Thirty minutes, no obligation. If a shared product would serve you better, we will say so on the call.
The Brief
The week in legal, in four minutes.
Free, national to Orange County, every Wednesday.