Skip to content

Capabilities

Each Davion capability is a layer on top of the ontology, not a standalone product. This page lists the capabilities shipping in AlpOS 1.0 and what each is for.

Retrieval-augmented generation runs inside the perimeter, grounded in the ontology rather than a vendor knowledge graph. Every generation cites the source span; every retrieval respects access policy.

The retrieval layer is hybrid by default — keyword, semantic, and structured-query — with the planner choosing per question. Citations are not bolt-on; they are emitted by the retrieval layer and threaded through the generation step, so the operator can verify the answer against the source span without leaving the console.

Translation runs on the institution’s hardware, fine-tuned to the domain when the engagement scopes for it. Sixty-plus language pairs at general availability; specific pair quality is documented per language. Every translation is auditable: the model version, the source text, the produced output, and the operator who approved (if approval is required for the workflow) are logged.

Where the institution has existing localisation processes, the translation capability integrates with translation memories and termbases rather than replacing them.

Connectors for the systems institutions actually run: core banking, SCADA, MES, EHR, content stores, unstructured archives, public registries. Ingestion is observable, policy-aware, and rebuildable from source — meaning the platform can re-ingest from the system of record if the ontology shape changes, without needing the data to be re-uploaded by hand.

  • Search — faceted search over the ontology, with policy-aware results
  • Analytics — SQL and notebook surfaces against the same governed schema
  • Workflow — propose/approve workflows with signed audit trails
  • Copilot — an in-perimeter assistant that uses RAG, search, and the workflow engine to draft proposals for the operator

Some capabilities that operators commonly ask about are not in 1.0 and are tracked on a published roadmap rather than implied to be available:

  • Geospatial reasoning at scale (PostGIS-class capabilities are present; deep geospatial reasoning is roadmap)
  • Video understanding (audio understanding ships; long-form video is roadmap)
  • Multi-tenant federation across geographically distributed perimeters

Where a deployment depends on a roadmap capability, we say so during pilot scoping rather than at production cutover.