How The Intelligence Layer Works
Three coordinated subsystems. Each handles a distinct responsibility. They share context continuously so a change in one place is understood everywhere.
Most systems treat documents as files. This subsystem reads submissions, SOPs, batch records, and datasets as structured scientific content, extracting specifications, numeric limits, referenced values, and calculations, then building a live dependency map of what must remain internally consistent.
- Specification extractionIdentifies regulated values such as limits, ranges, and assay thresholds as distinct entities, not as raw text strings.
- Dependency mappingTraces which values in a draft are directly dependent on SOP sections, source datasets, or earlier batch records.
- Cross-document linkingBuilds a graph connecting related sections across separate documents so a change in one place surfaces downstream risks immediately.
- Calculation verificationFlags derived values that no longer match their source data, including yield computations, assay results, and dose calculations.
As a scientist writes, this subsystem checks each new statement against the approved SOP context the document references. It doesn't wait for QA review or submission. It surfaces conflicts in real time, with exact source citations, before the error moves downstream and compounds into a larger correction loop.
- Live SOP checkingEvery value entered is checked against the active SOP version governing that product, method, or process step.
- Cited flaggingMismatches are surfaced with a reference to the exact SOP section and the authoritative value, not a generic warning.
- Correction suggestionWhen a conflict is found, the copilot proposes the correct value and the revision needed before the author moves to the next section.
- Audit trail generationEvery check and resolution is logged with timestamps against document version and SOP revision, ready for inspection.
Documents, lab software, spreadsheets, and browser-based workflows each operate in isolation today. This subsystem connects them. When one agent sees a value change in software, the others cross-check every place that value appears across documents, datasets, and open workflows, and align before the user proceeds.
- Multi-agent architectureSeparate agents run in document, browser, and software contexts simultaneously. Each specializes in its environment; all share one knowledge state.
- Propagation detectionA changed value in one tool triggers an automated check of all dependent references across the other tools, in the same session, not the next review cycle.
- Conflict arbitrationWhen agents disagree, the system identifies which source is authoritative by tracing the reference chain, then surfaces the resolution to the scientist.
- Isolated deploymentThe shared context runs entirely within your company environment. No data crosses into external systems or public model infrastructure.
Lab software like Empower, LabWare, and instrument consoles assume deep expertise. One wrong setting produces invalid data that no one catches until review. This subsystem reads the live software screen, understands where the user is, and walks them through the exact workflow their company SOP requires. It guides each step, validates every entry against approved parameters, and stops mistakes before they generate bad data. A scientist is guided to the right result instead of being left to discover the wrong one later.
- Screen-aware guidanceReads the live interface of the software in use, identifies the current screen and available actions, and maps them to the governing SOP for that method or instrument.
- Step-by-step directionWalks the user through the procedure in sequence (which field, which value, which button, in what order) so the correct workflow is followed every time, regardless of experience level.
- Guardrail enforcementValidates every parameter and entry against the company's approved SOP and protocol limits in real time. Out-of-range values, skipped steps, and incorrect settings are flagged before they are committed.
- Competency levelingLowers the expertise barrier so a trained-but-junior scientist can operate complex software correctly under SOP control, while every guided session is logged for review and competency records.