The capability layer of the programme. Each layer addresses a distinct part of platform governance, and each can be evaluated on its own — the architecture is designed to hold either way.
Described at an architectural level. Every identity below is read from the published portfolio rather than maintained separately here.
CIVACE™ · Feature-level compliance engine
An architecture for evaluating and governing selected platform features using jurisdictional requirements, safety and trust signals, feature-specific risk, circumvention indicators, and differentiated operational controls.
SPGI · Government-side platform governance
An architecture for translating authorised policy and regulatory requirements into structured platform-governance, compliance-verification and evidence processes.
CIVITERA BX-AI™ · Cognitive memory substrate
An evidence-oriented architecture for structured event reconstruction, contextual analysis, continuity, and auditable decision history across complex digital environments.
Each technology may be evaluated independently. Selected integration configurations may also be explored under an appropriate confidential evaluation process. The evidence layer is optional; use of all three systems is not required.
A technology is listed in a child-safety context only where approved public material supports that relevance. The basis is stated rather than assumed.
The frozen public profile itself addresses child, minor and youth treatment on social-media platforms, and approved public source names it as the platform governance layer of this program.
The frozen public profile addresses platform governance for government and regulatory sectors, and approved public source names it as the government and regulatory layer of this program.
Approved public source names it as the optional evidence layer of this program and states plainly that use of all three systems is not required.
The estate is broader than this programme. Most published technologies address other domains entirely, and none is presented here as a child-safety technology unless its own published profile and the approved programme material support it.
Capabilities are described at an architectural level. Claim scope, filing architecture, and enabling technical detail are not published here, and no capability description should be read as an assertion of patent scope or as a statement that a particular feature of any third-party system is covered. Technologies are patent-pending; patent-pending status does not mean a patent has been granted, examined, or allowed.
The governance model these layers serve, the regulatory context, and the research behind them.
Each technology may be evaluated independently under an appropriate confidential evaluation process.
