The canonical plane
A relational source of truth owns identity, lifecycle state, and confidence. Promotion follows a controlled draft → approved → retired path. Deletion here is real deletion.
Technology portfolio · CVI
Missing peers are gaps, not facts.
CVI — Callosum Vector Integration is a relational-vector synchronisation and governed coordination fabric. It lets a system use semantic recall without letting similarity overrule what the system authoritatively knows. CVI is implemented and separately licensable; qualification remains incomplete.
Recall is advisory by constructionThe vector plane is derived, disposable, and never authoritative. That is enforced at runtime, not asserted in a design document.
Arbitration is the productEvery recall row is checked against authoritative memory and classified by whether authority backs it.
The client supplies contextMiraTV demonstrates an integration environment; claims still remain bounded to registered evidence.
The organizing idea
Separation of semantic recall and authority.
Most catalog and knowledge systems blur the two, and the blur is what makes AI-assisted work untrustworthy. CVI keeps them in physically separate stores and makes crossing between them a governed act.
The advisory plane
Vector embeddings are advisory, never authoritative. They are a one-way projection from canonical content, disposable by design, and rebuildable after a model upgrade without corrupting state.
Arbitration
The system reports where its own two halves disagree.
Separation is architecture — a competitor can copy the diagram. Arbitration is what the separation buys you, and it is the claim no similarity-first system can make.
Implemented · governed local-model lane
Vector facts are checked against authoritative memory before they are treated as evidence.
Every recall row is joined back to the canonical plane and classified by whether authority stands behind it. A recall hit with no authoritative peer is not demoted quietly or silently dropped — it is labelled a gap, and a gap is a reportable finding rather than a fact in waiting.
Matched peerMissing peer = gapAdvisory-only enforcementGrounded arbitration
Blind spots
Strong semantic recall with no authoritative record behind it. The system says so instead of presenting the recall as knowledge.
Convergence and duplication
Where the canonical plane holds two distinct records that recall keeps treating as one thing — the duplicate a normalizer missed.
Advisory-only, at runtime
The arbitration lane refuses to run unless the recall plane is marked advisory and the arbiter is in grounded mode. The discipline is a precondition, not a convention.
Technology components
What is actually owned.
Provider normalization
Structurally similar provider data can be normalized on entry while provider-native identifiers and provenance are preserved. Compatibility and scale remain subject to the actual adapter and qualification scope.
Canonical identity layer
Stable, platform-owned identifiers separate provider reference from platform authority. Cross-provider reconciliation is non-destructive and identity resolution is late-binding rather than forced at ingest.
Concurrent ID mapping engine
An explicit mapping layer carries live, VOD, and series relationships, supporting overlapping provider IDs and multiple providers holding identical or near-identical content. Updates are non-destructive; retirement is soft, via active flags.
Relational–vector sync
A functional, model-versioned projection from canonical content into the recall plane. Re-embedding does not corrupt state, and the vector layer stays deliberately disposable.
Authority preservation
Explicit confidence scoring, controlled promotion lifecycle, traceable provenance, hydration from canonical records before reasoning, and deterministic authority lookup.
Controlled reasoning surface
Time-based validity windows, status-based filtering, and domain-level filtering — so what a model is permitted to see is a policy decision rather than an accident of schema.
Integration
Every plane is addressed by name, never by connection.
CVI is built to be adopted without demanding that a licensee replace their stack. The seam is a registry: callers ask for a logical plane, and a resolver decides what actually answers.
Logical planes, not connections
Authority, recall, knowledge, and coordination stores are each addressed by a registry key. Nothing in the calling code carries a connection, so repointing a plane is a configuration change rather than a code change.
One audited path
Database access runs through a single governed gateway with token authentication, a permitted-statement boundary, and request logging — so access is observable and constrained rather than ambient.
Bring your own model
Model choice can remain with the licensee. Relational, vector, and embedding-provider compatibility must be verified for the selected environment; broad embedding-provider independence is not presently claimed.
How it is evidenced
Implementation evidence is not universal qualification.
MiraTV provides a demanding reference context for CVI integration. Evidence from that environment can support bounded claims, but it does not establish suitability, scale, or qualification for every licensee environment.
A demanding, unforgiving workload
MiraTV is a live IPTV client and platform carrying real customer traffic across multiple providers on Android and Android TV. Catalog technology that degrades the viewing experience is technology nobody adopts — so the client working is not a demo, it is the argument.
CVI, proven by the client
What Iberion licenses is the architecture: normalization, canonical identity, concurrent mapping, the recall/authority separation, and the arbitration that governs it. It is portable to any catalog or knowledge problem of the same shape, and that portability is where its value sits.
The platform, client included, is available — that conversation can be had. But the client’s job here is to prove the technology does what this page says it does.
Shared reference context
One integration. Separate evidence boundaries.
The same client can carry CVI and Citadel in a latency-sensitive media workload. Each technology remains separately defined, licensed, evidenced, and qualified.
Citadel
Iberion’s protection architecture is integrated and exercised inside the same client, on Android and Android TV, with its evidence state published ring by ring rather than flattened into a single maturity claim.
Explore Citadel →Demonstration is not definition
MiraTV is not Citadel, and it is not CVI either. It is a production application in which both have been integrated and exercised. Neither technology is defined, contained, or bounded by the application that happens to host it, and each is licensed on its own terms.
Technology portfolio →Roadmap
Stated separately, because it is not shipped.
These are specified as optional advanced and premium capabilities. They are named so the roadmap is legible — not presented as current behaviour.
Catalog intelligence
Automated duplicate-resolution suggestions and semantic catalog gap analysis.
Comparative analytics
Provider performance scoring and cross-domain insight extraction.
Evidence boundary
How to read this page.
This page describes designed technology capability. Iberion assigns evidence status per capability rather than per product, and does not present a capability set as uniformly deployed, qualified, or independently certified simply because the architecture defines it.
Per-capability maturity — what is running in production, what is implemented and under qualification, and what remains specified — is available as a controlled record, under NDA and scoped to the specific question being asked.
The same discipline governs Iberion’s other technologies. See the Citadel press kit for a worked example of per-component evidence status stated publicly.