Foundation
The parsing target remains an OnlyOneAPI foundation endpoint, not parser-specific UX.
See parsing, ingestion, and dependency reality before it becomes support debt.
La route connectors doit permettre a un client d'identifier ce qui alimente son BrainCaps, ce qui est operationnel, et ce qui reste en mode transition ou fallback.
Explicit
Direct parser backends may exist only as visible, controlled fallbacks.
Legibility
The customer should see whether ingestion is healthy, degraded, or waiting on configuration.
What the customer can reasonably see
Connectors should reveal product-relevant states without turning this page into an ops console.
- Parser chain statusShow whether the foundation path is configured and whether fallback mode is active.
- Ingestion activityHighlight recent ingestion volume and visible staleness or blockage.
- Dependency impactTranslate backend readiness into customer-readable health language.
How to avoid leaking operator detail
The customer route should remain product-facing even when it references technical dependencies.
- HealthyThe ingestion path is available and BrainCaps can continue updating workspace memory.
- DegradedThe workspace remains usable but recent updates may lag or use controlled fallbacks.
- Needs supportThe issue exceeds self-service product handling and requires operator follow-up.
What the route should reinforce
The page should make the future architecture clearer, not muddier.
- Foundation firstThe customer sees one product path, not a list of parser brands.
- Fallback visibleIf fallback is active, its impact should be legible and auditable.
- Admin separationDeep diagnostics and recovery actions stay in braincaps360.