CIVITERA intellectual property is organised as an architecture rather than a product. Each layer addresses a problem that stands on its own, and each is designed to be licensed without requiring the others.
Described at the architectural level: what the layer governs, not how any implementation of it is built.
Counter-autonomous and transport protection
Counter-UAS detection and response, and protective architecture for AI-driven transport platforms. The layer at which protective behaviour is structured and authorised rather than implemented.
Cross-sovereign and execution governance
Cross-jurisdiction governance bridges, execution policy, and auditable governance trails — the layer at which an obligation becomes something a system can apply and an authority can examine.
Agent and pipeline control
Coordination across models and agents, decision-chain routing, and observability of how work moves through a population of automated components.
Runtime authority
The runtime foundation for institutional deployments: execution doctrine, orchestration primitives, and policy resolved at the point of action.
Attribution and continuity
Identity, attribution and control across autonomous infrastructure, including how human-originated contribution and authority remain traceable over time.
The layers are separable, but they are not unrelated. These are the public functional relationships between them.
Protective systems operating in regulated environments need an accountability path. A defense-layer deployment is designed to engage the governance layer so that what was detected, concluded and authorised remains examinable.
Coordination produces decisions; the operating layer is what makes those decisions attributable to an authority. Together they turn agent activity into action an institution can account for.
The layers are designed to be licensed separately. A counterparty may take a position in one layer without taking the others, and the architecture is intended to hold either way.
This page describes architecture. It does not describe an implementation, and it is not an enabling disclosure. The layers are how CIVITERA organises its intellectual property and how a counterparty can take a position in part of it; they are not a specification a system could be built from.
Where a layer is described as operating in a regulated environment, that describes the environment a licensee deploys into. It is not a statement that CIVITERA holds a certification or approval. That boundary is set out in full on the standards page.
Layer descriptions are published at a non-enabling level. Implementation detail, claim architecture, and filing architecture are not published, and no layer description should be read as one. Publicly available patent records may be independently verified through USPTO systems where applicable. Information concerning non-public applications is provided through controlled verification procedures to qualified counterparties.
Licensing is structured so a counterparty can engage a single layer. Field of use, territory, and exclusivity are defined in executed agreements.
