[ implementation · reference architectures ]
Reference architectures are testable patterns, not product promises.
Each pattern shows a narrow workload, a proposed data-flow boundary, explicit assumptions, measurements, failure paths, and primary sources. Adapt it only after reviewing the actual system, authority, devices, and applicable obligations.
Field operations teams working with intermittent connectivity and reviewable records.
Offline field capture with authorized cloud escalation
A bounded field workflow where capture, validation, and a compact draft step remain on a supported device; only approved, necessary material is escalated when connectivity and policy allow.
Inspect pattern →Schools and districts testing a narrowly scoped accessibility or instructional-support workflow.
School accessibility assistant with teacher-controlled review
A limited classroom support pattern for transforming teacher-approved material into an accessibility aid—such as a reading-level draft, caption draft, vocabulary support, or alternative format—without making the assistant an assessment authority.
Inspect pattern →Small organizations and teams that need faster retrieval from a defined, permissioned internal knowledge base.
Internal search over approved documents with source-linked answers
A bounded internal search pattern that indexes an approved corpus, retrieves source passages, and asks a model to draft an answer with links back to those passages—while keeping access and corpus governance explicit.
Inspect pattern →