You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-4Lines changed: 28 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,24 @@ The core problem in AI governance is not a lack of rules, transparency, or overs
7
7
8
8
Regulatory frameworks increasingly classify systems by capability, not configuration. Liability attaches to what a system is able to do, not only to what it happens to be doing. The real leverage point is design time, where continuants, capabilities, roles, and processes can still be made explicit, inspectable, and contestable.
9
9
10
+
### Regulatory classification as a design-time problem
11
+
12
+
Modern AI regulation increasingly classifies systems by *capability*, not by configuration or stated intent. Under the EU Artificial Intelligence Act, this shift is explicit: Article 6 and Annex III define high-risk status in terms of what a system is structurally capable of doing, regardless of whether those capabilities are currently enabled.
13
+
14
+
ARCO operates on top of this regulatory reality.
15
+
16
+
Rather than treating regulatory classification as an interpretive or post-hoc exercise, ARCO formalizes Article 6 and Annex III criteria as explicit, capability-based conditions that can be evaluated at design time. If a system’s structure supports the realization of a regulated capability, that classification follows as a matter of logical consequence. If it does not, the classification does not resolve.
17
+
18
+
This framing establishes the minimum foundation required for ARCO to function: a shared, explicit model of system structure, capabilities, and regulatory triggers that can be inspected, validated, and reasoned over deterministically.
19
+
20
+
### Ontological grounding (why structure matters)
21
+
22
+
For regulatory classification to be derived from system structure, the underlying model must distinguish clearly between what *exists*, what it is *capable of*, and what *processes* may occur as a result.
23
+
24
+
ARCO is grounded in a realist ontological framework aligned with the Basic Formal Ontology (BFO). This grounding enforces explicit separation between material entities, dispositions (capabilities), roles, and processes, preventing regulatory classifications from being inferred from informal descriptions, policy language, or implementation detail alone.
25
+
26
+
This is what allows ARCO to treat capability as something that resolves from structure rather than something asserted by documentation or intent. If the structural prerequisites for a regulated capability are not present, the capability does not exist for regulatory purposes.
27
+
10
28
## Overview
11
29
12
30
ARCO is a framework for producing **clear, defensible regulatory classifications** for high-stakes AI systems.
@@ -28,21 +46,27 @@ ARCO is under active development. Ontological commitments and determination mech
28
46
For readers who want a fast, system-level understanding before diving into the full materials:
29
47
30
48
**0. Executive overview (non-technical)**
31
-
A concise, business-facing overview of ARCO's purpose, economic value, and positioning for decision-makers.
49
+
A concise, business-facing overview of ARCO's purpose, economic value, and positioning for decision-makers.
0 commit comments