Integration centre
What EDS connects to, what is written and not connected, and what has never been called.
Demonstration project - no figure here describes a real facilityChanges are not saved
Why
Each row states its real condition. An integration whose code exists and whose credential does not is reported as implemented, not as available.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Integrations
8
Working today
2
Implemented, not connected
3
Never called
3
Implemented is not available
Most of this list has never run against the thing it integrates with.
Connected systems
| System | What it is for | Condition | What that means |
|---|---|---|---|
| Supabase PostgreSQL | Every record the project holds | Implemented, not connected | The database adapter, the migrations and row-level security are written and tested without a database. No project has been provisioned, so nothing has been stored. |
| Supabase Storage | Document files | Implemented, not connected | Tenant-scoped storage keys are generated and recorded. No bucket exists, so no file has been uploaded. |
| Clerk | Authentication and organisation membership | Implemented, not connected | The identity boundary and the tenant context it feeds are written. No instance has been configured, so nothing has authenticated. |
| Primavera P6 | Schedule import and export | Working | The XER reader and writer run against the project's own schedule, verified by re-reading the output block by block. |
| Excel registers | Register import and export | Working | The workbook writer produces files Excel opens, verified by unpacking them and reading the cells. |
| Azure AI Document Intelligence | Production OCR | Not built | The approved production candidate. No client has been written and no page has ever been sent: activating it is a Product Owner decision with a cost. |
| Google Cloud Document AI | Independent OCR benchmark | Not built | Intended as the independent comparison. Not built, never called. |
| AI provider | Deliverable generation and the assistant | Not built | No provider selected and no budget approved. The grounding and citation rules are implemented; the generation step is not. |
API access
No external API is exposed. The application’s own server actions are the only write path, and they run inside a tenant session that row-level security reads. An API would need its own authentication boundary and its own rate limiting, and neither has been built.