Unified dashboard
A single operational view of ingestion throughput, index freshness, custody state, graph resolution latency and cost per workload — with drill-down to the individual job or query.
The central infrastructure that collects, governs, and prepares information.
Infrastructura centrală care colectează, guvernează și pregătește informația.cida.tech is the operational control surface of the Central Intelligence Data Architecture. Every ingestion job, index rebuild, credential release and cortex query passes through policy here — authenticated, authorised, rate-shaped, metered and observable. Nothing in CIDA executes outside its governance.
Distributed architectures fail at the seams — where responsibility for identity, policy, cost and observability is unclear. CIDA resolves this by centralising governance while keeping storage, processing and reasoning strictly separated. The Control Plane owns the seams.
A single operational view of ingestion throughput, index freshness, custody state, graph resolution latency and cost per workload — with drill-down to the individual job or query.
One authenticated entry point for every CIDA capability. Versioned contracts, schema validation, quota enforcement, deterministic error semantics and per-tenant rate shaping.
Role- and attribute-based authorisation evaluated per request, with jurisdictional constraints, purpose limitation and time-bounded elevation for sensitive operations.
Structured traces, metrics and logs correlated by request identity across all five components — so an anomaly in a cortex answer can be traced back to the ingestion batch that caused it.
Policy is declarative, versioned and testable. Changes are proposed, diffed against live traffic in shadow mode, then promoted — never edited directly in production.
Scheduled and event-driven workflows across ingestion, refinement, indexing and re-scoring, with dependency awareness, back-pressure handling and idempotent retries.
Consumers of CIDA — including the RONOR runtime — never address components directly. They address the gateway, which resolves the correct component, applies policy, meters usage and returns a traceable response.
# Resolve a question through the Cortex, governed end to end POST https://api.cida.tech/v1/resolve Authorization: Bearer <operator-token> X-CIDA-Purpose: "investment-committee" X-CIDA-Jurisdiction: "EU" { "query": "long-duration storage parity window", "min_confidence": 0.75, "include": ["provenance", "timeline"], "components": ["cortex", "archive"] } # 200 OK { "trace_id": "cida_7fd41a9e", "confidence": 0.89, "band": "strongly-supported", "sources": 63, "policy": { "decision": "allow", "residency": "eu-central" }, "metered": { "units": 4, "component": "cortex" } }
Every request carries an identity, a purpose and a jurisdiction. The authorisation engine evaluates these against declarative policy and returns a decision with its reasoning attached. Denials are as auditable as approvals.
Sensitive operations — Vault reads, index rebuilds, policy promotion — require time-bounded elevation with a named approver. Elevation expires automatically; standing privilege does not exist in CIDA.
Correlated telemetry across all five components makes causality recoverable. An unexpected confidence downgrade in the Cortex can be traced to the ingestion batch, the source document and the policy version responsible.
| Surface | Responsibility | Enforcement point | Audit |
|---|---|---|---|
| Dashboard | Operational visibility and drill-down | Read-only, scoped per tenant | View events logged |
| API Gateway | Single authenticated entry point | Per-request policy evaluation | Full request/decision record |
| Access Control | Identity, purpose, jurisdiction | Deny-by-default authorisation | Immutable decision log |
| Monitoring | Traces, metrics, anomaly signals | Correlated by request identity | Retention per policy |
| Orchestration | Workflow scheduling and retries | Idempotent, back-pressure aware | Job lineage preserved |
CIDA separates the handling of data from the understanding of it. Four infrastructure components move, refine, index and protect material; the Cortex constructs meaning. The Control Plane governs all five, and the RONOR runtime consumes them on the user's behalf.
Control Plane access is provisioned to named operators under a defined purpose and jurisdiction, with elevation workflows and audit retention agreed in advance. Tell us what you need to operate and we will scope it.
office@cida.tech · No cookies · No tracking