Norms and AI execution control: an infrastructural perspective.

Different layers, same problem.

The AI Act, NIS2 and the ISO and NIST standards operate on different layers: legal, organisational, risk-management. Although heterogeneous, they converge on a restricted set of key requirements.

Read by principles rather than by articles, these requirements reduce to four recurring properties: preventive control of AI invocation, documented and verifiable traceability of decisions, technical auditability and accountability attributable to identifiable subjects.

The legal layer defines obligations; the organisational layer defines processes; the risk-management layer defines methods. Missing from this stratification is an explicit definition of the technical mechanisms through which such requirements can be made observable in the systems that actually execute AI.

The missing common denominator.

The requirements listed in the reference frameworks are expressed in terms of what must be guaranteed. Their operational translation is today entrusted to heterogeneous instruments — textual rules, documentation, application controls, after-the-fact records — rarely brought back to the same architectural layer.

In particular, a technical control point is missing that jointly presents the following four properties.

• Non-bypassable Authorisation of AI use cannot be ignored, rewritten or omitted by the code that requests it.
• Independent The control point is decoupled from applications: it does not depend on their cooperation or on their correct configuration.
• Sub-applicational It resides below the application layer, in a position the applications cannot modify.
• Technical evidence It produces, as an effect of its own operation, verifiable records of the decisions taken.

The absence of such a control point is not a gap in the norms: it is a gap in the architecture of the systems. It is, in other words, an architectural problem.

Where AIKNOCK sits.

AIKNOCK explores a possible ex-ante technical control point, at the system layer, consistent with the execution-control, auditability and risk-management requirements referenced by norms and standards, without replacing or interpreting them.

Norms and standards define obligations. AIKNOCK operates on the layer of technical mechanisms. The system operates independently of external regulatory or standard frameworks and maintains a consistent technical behaviour at execution level. The two layers are complementary: what the law and the standards prescribe as system properties, a mechanism such as the one described can contribute to making observable and verifiable.

What AIKNOCK does not do with respect to the norms.

To avoid confusion between distinct layers, it is appropriate to state explicitly the scope that AIKNOCK does not occupy.

• DOES NOT it does not interpret the law,
• DOES NOT it does not guarantee compliance,
• DOES NOT it does not replace organisational or legal processes,
• DOES NOT it does not eliminate the responsibilities of deployers,
• DOES NOT it does not govern datasets or training processes.

Observance of the norms remains a responsibility of operators, implementers and competent authorities. AIKNOCK does not shift such responsibility: it describes a distinct technical layer.

Conclusion.