Corpus · capability status
Corpus capability status
What works in Corpus today, what we set up for your archive, and what is not built yet. One label per capability, in plain words.
Checked 2026-10-03 against product commit 8892c7c, the version the public demo runs. We update this page with each release.
The labels
What each label means
- Current
- Works in the product and the public demo today; not independently certified.
- Set up for you
- Set up for your archive during setup; not shown in the demo; not yet done for any customer.
- Proposed: not built yet
- Not built. We discuss it on the free 30-minute call; scope and price are agreed in writing as paid work.
- Our commitment
- A promise about how we handle your work, written into the pilot or deployment agreement. Not a product feature.
- Not offered
- Not part of Corpus.
Acceptance-tested: None yet. The first pilot is the first acceptance test.
Capability by capability
Where each part of Corpus stands
| Capability and its label | What that means today |
|---|---|
| Current Cited search over the demo archive: keyword and vector search, with page citations | Archive citations open on the cited page with the passage highlighted. Case-law citations have no page image, no original link and no source panel. |
| Current Source panel on an archive citation | File name, real document title, project and category, page, issuing organization, highlighted passage, OCR tag, page image and original link. See the citation anatomy below. |
| Current “Nothing on file” when nothing supports an answer | Designed to say “Nothing on file” instead of guessing. An empty result does not prove that no such record exists. |
| Current OCR of the demo archive’s image-only scans | Pages read by OCR are tagged on the citation and the source panel, so you can compare the text with the page image. |
| Current Two demo roles, Project Engineer and Principal, and one restricted project | Any visitor can switch roles. The restricted project (a litigation hold) is removed before search for the Project Engineer role: in the keyword query, in the vector index and in page images. Fictional demo data. |
| Current Go/no-go research on an RFQ | Nine criteria. Corpus suggests six scores, and a person accepts them or changes any of them; fit, relationship and capacity are scored only by people. A verdict appears only after all nine are scored. Research sections mark what the archive does not hold. |
| Current SOQ draft for RFQ items 1 to 4 | Each sentence is written to carry a page citation; open each citation, because the software does not check that every sentence is supported. GAP and NEEDS INPUT markers show what is missing. Office details, key staff and sub-consultants, and references are filled in by people. No SOQ export, no sign-off step and no DRAFT watermark. |
| Current Fee build | Arithmetic done in code on WSDOT M 27-50 Appendix AA; check it line by line against your own spreadsheet. Arithmetic done in code is only as good as its inputs and formulas, so a qualified person still checks them. |
| Current Rate comparison with GSA CALC+ ceiling-rate benchmarks | Your rates are compared with a snapshot of GSA CALC+ ceiling rates. Ceiling rates are maximums, not averages. |
| Current Fee approval by the Principal role | The server lets only the Principal role approve. Corpus stores who approved (in the demo, the fictional Principal), the total and the time; the time is not shown. Editing the fee clears the approval, and a changed total shows “approval out of date”. Fictional demo data. |
| Current Contract draft from the approved fee | A fixed WSDOT CPFF agreement form stamped DRAFT, generated only from an approved fee; its PDF stays blocked until approval. It is not legal advice: your counsel and technical reviewers decide what may be used. |
| Current Bid-tab unit prices and price trends | Looked up in public bid tabulations in the demo archive, with page citations. |
| Current Demo archive | 57 public documents, about 7,100 searchable pages, filed under a fictional sample firm. Fictional demo data. |
| Current Conversation threads in the demo | A thread expires 24 hours after its last use. |
| Set up for you Corpus is cloud-agnostic: it runs on AWS, Azure, Google Cloud, or your own servers | Installed for you during setup; not yet done for any customer. Where Corpus runs is not, by itself, a compliance claim. |
| Set up for you OCR of your own scanned files | Scans are planned on the call and read during setup. |
| Set up for you Connector to your network drive | No connector is ready-made; each is built for your archive during setup. |
| Set up for you SharePoint connector | No connector is ready-made; each is built for your archive during setup. |
| Set up for you ProjectWise connector | No connector is ready-made; each is built for your archive during setup. |
| Set up for you Microsoft Teams app | No connector is ready-made; each is built for your archive during setup. |
| Set up for you Identity mapping: each role tied to your named people and groups | No connector is ready-made; each is built for your archive during setup. |
| Set up for you Setting up your RFQ: fee tasks, research and SOQ questions, page limit, contract-terms note | Done by us; for the pilot's one pursuit it is inside the $5,000. |
| Set up for you Another owner’s fee method or agreement form | The demo uses WSDOT’s. |
| Set up for you Refresh schedule and do-not-index folders | |
| Proposed: not built yet Record owner, revision, approval status, jurisdiction, effective date, retrieval date and index freshness on each citation | Not shown today, so your reviewer confirms them. The demo has no date field; a year shows only when a file name carries one. |
| Proposed: not built yet Edition check: current and superseded labels, conflict flags | The demo holds the 2014 and 2024 editions of WSDOT M 41-10, but no answer comparing them has been captured. Today your reviewer confirms the edition. |
| Proposed: not built yet Exception register: an owner and a resolution for each gap | Today: your procedure. |
| Proposed: not built yet Sign-off records for SOQs and answers, and version history | Today: your procedure. Fee, SOQ and contract drafts are overwritten when edited. |
| Proposed: not built yet Search audit trail by named person, live permission re-check, delta-sync and revocation tests | |
| Proposed: not built yet Design-evidence packet and calculation-review packet (firms) | |
| Proposed: not built yet Consultant-review packet, permit matrix, submittal comparison, completeness review and fee-support packet (public owners) | |
| Proposed: not built yet Structured table extraction | |
| Proposed: not built yet Redline classification, competitor evaluation, win/loss tracking and a staffing database | |
| Proposed: not built yet Key staff suggested from your staff roster | Today key staff is a field your people fill in. |
| Our commitment Deleting the pilot copy | When the pilot ends, we delete the copy within 7 days and confirm it in writing. |
| Our commitment Training or fine-tuning a model on your files | In the pilot, your files are never used to train or fine-tune a model. In full deployment, fine-tuning on your files happens only if you agree in writing. |
| Not offered Native CAD and BIM model files | Corpus reads PDF files. |
| Not offered Operational-system data such as SCADA exports, plant operation, process control and safety systems | |
| Not offered Checking engineering calculations or code compliance, design certification and seals | Your qualified people do this work. |
| Not offered Legal advice | The contract draft is stamped DRAFT and is not legal advice. |
| Not offered High availability and a service-level agreement (SLA) |
Changes: 2026-10-03: every row checked against product commit 8892c7c.
Who checks what
What the software enforces, and what your procedure covers
The software enforces
- Only the Principal role can approve a fee, and the server enforces it. Corpus stores who approved, the fee total and the time; the time is not shown.
- Editing the fee clears its approval. If the total changes, the fee shows “approval out of date” until it is approved again.
- The contract draft is generated only from an approved fee, and its PDF stays blocked until then.
- A go/no-go verdict appears only after all nine criteria are scored. Corpus suggests six scores, and a person accepts them or changes any of them; fit, relationship and capacity are scored only by people.
- A restricted project is removed before search for any role that may not open it.
- Set up for you In the demo any visitor can switch roles. Tying each role to your named people is identity mapping, set up for you and not yet done for any customer. No connector is ready-made; each is built for your archive during setup.
Your procedure covers
- Reviewing and signing off the SOQ draft. Corpus has no sign-off step and no SOQ export.
- Checking each answer against the pages it cites before anyone relies on it.
- Deciding which standards and editions apply to the project.
- Naming an owner for each gap and deciding how it is resolved.
- Final submission to the client or owner, and any signature or seal your project and jurisdiction require. Corpus applies neither.
Anatomy of a citation
What a citation shows today, and what it does not show yet
Current On a citation today
Fictional demo data: [1] Source: 2020-EV288-STR-Spec · p. 7 (Evergreen Containment Basin) is how the demo files a real TxDOT 2024 special specification.
- File name (in the demo it carries a fictional year)
- Real document title
- Project and category
- Page, with the page image and the passage highlighted
- Issuing organization
- OCR tag on pages read by OCR
- Original link to the public source
- GAP markers, and “Nothing on file” when nothing supports an answer
Not on a citation yet
A field Corpus does not show is a field your reviewer has to confirm.
- Proposed: not built yet Record owner
- Proposed: not built yet Revision
- Proposed: not built yet Approval status
- Proposed: not built yet Jurisdiction
- Proposed: not built yet Effective date
- Proposed: not built yet Retrieval date
- Proposed: not built yet Index freshness
Case-law citations in the demo have no page image, no original link and no source panel.
Check it on your own pursuit
No capability here has been acceptance-tested on a customer archive yet. A $5,000 pilot on one real pursuit is where your team checks it.
→ How your people review Corpus output, step by step→ Each copy of your files and where it lives