Built Word Documents (.docx):
Spensara Overview (.docx)
Capability Assessment (.docx)
Brink POS Ingestion Analysis (.docx)
The Borg Ingestion Architecture (.docx)
Categories
Architecture (19)
System design documents, C4 architecture diagrams and models, and platform integration structures.
- c4/docs/C4/actors.c4
- c4/docs/C4/AGENTS.md
- c4/docs/C4/customer_model.c4
- c4/docs/C4/etl/ingestion.c4
- c4/docs/C4/etl/integrations.c4
- c4/docs/C4/integrations_model.c4
- c4/docs/C4/kdsai_model.c4
- c4/docs/C4/specifications.c4
- c4/docs/C4/usecases/anomaly_detection.c4
- c4/docs/C4/views.c4
- docs/auth-and-data-ownership.md
- docs/ETL.md
- docs/flows/etl-ingestion.md
- docs/flows/kb-generation.md
- docs/flows/monitor-authoring.md
- docs/flows/runtime-execution.md
- docs/README.md
- docs/REDSHIFT.md
- docs/technologies.md
Auth And Data Ownership
The web Front is a backend-for-frontend, not a system of record.
Ownership Boundaries
- Keycloak owns identities, roles, login, logout, and token issuance.
- Backend owns customers, users, customer API keys, documents, activity logs, tenant resolution, and authorization decisions.
- Front owns Blade/UI routes, OIDC session hydration, and calls to backend APIs using the current user's bearer token.
Front Constraints
- No Eloquent user/customer/document/activity models.
- No migrations, seeders, local database sessions, local database cache, local database queues, or password reset tables.
- No local login credentials or
Auth::attemptflow. - No tenant or customer headers derived by Front; backend resolves tenant context from authenticated claims and membership.
Runtime Defaults
- Local Front defaults to cookie sessions, file cache, and sync queues.
- Aspire overrides Front to Redis sessions/cache and sync queues for distributed local validation.
- Backend APIs enforce admin/user policies and tenant scoping for document/admin flows.