Trust & technology
Architecture
Applications for distinct jobs, a shared authorization layer and explicit boundaries around report data and AI processing.
Search the public guides. Your search stays in this browser.
On this page
The system at a glance.
- ApplicationsWindows and Mac editor; native iPhone/iPad fieldwork; browser administration and fieldwork.
- Access layerIdentity verification and workspace, role, license and seat checks.
- Application servicesReports, revisions, notebook sync, administration and requested AI assistance.
- Data & providersPrivate relational storage, managed identity, screened AI processing and selected lookup services.
What it is built with.
Scroll horizontally to read the full table.
| Component | Technology | Responsibility |
|---|---|---|
| Desktop | Electron with a bundled Next.js / React editor | Installed report workspace and operating-system integration. |
| Native fieldwork | SwiftUI; Apple RoomPlan where supported | Adaptive iPhone/iPad collection and device capabilities. |
| Web | Next.js / React | Browser workspace administration and responsive fieldwork. |
| Service | .NET on Google Cloud Run | Authorization, report operations, notebook synchronization and AI orchestration. |
| Identity | Google Identity Platform | Account authentication and connected sign-in methods. |
| Persistent data | PostgreSQL on Google Cloud SQL | Workspace records, reports, notebooks and retained revisions. |
| AI | OpenAI API and Google Cloud Model Armor | Narrative assistance and report checks with text screening. |
Where the boundaries matter.
Device to cloud
The desktop bundles its editor, while report authorization remains online. Prepared fieldwork has bounded local access. A local save, cloud synchronization and report import are separate events.
Workspace to workspace
The application service scopes report operations to the authorized workspace. Being an internal administrator does not substitute for a report user's membership and seat.
Report to AI provider
Only requested AI operations send selected report context to the model provider. The current narrative workflow excludes photo image bytes and uses screening before and after generation.
Draft to retained revision
Working drafts can change. A retained snapshot/PDF revision is designed to preserve the version that was recorded. Later work creates a new version rather than rewriting that record.
How the system is being built.
Shared contracts keep notebook evidence consistent across applications. Domain models, report-format adapters, AI integration and cloud authorization have distinct responsibilities. Automated checks cover those boundaries alongside application and packaged-desktop journeys.
Release work also includes device testing, migration checks, PDF consistency and recovery validation. Passing a component test is not the same as proving an entire firm workflow. The roadmap separates implementation progress from release gates.