Skip to content

Commit dbb221b

Browse files
author
Denis Yermakou
committed
standard: establish chronological AOS 0000-0011 artifacts
1 parent 841f91e commit dbb221b

31 files changed

Lines changed: 969 additions & 1256 deletions

‎.github/workflows/ci.yml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ jobs:
2222
- name: Verify AxonOS Standard contract
2323
run: python3 tools/verify_standard_contract.py
2424

25-
canonical-artifacts:
26-
name: canonical artifacts
25+
standard-artifacts:
26+
name: standard artifacts
2727
runs-on: ubuntu-latest
2828
timeout-minutes: 5
2929
steps:
@@ -33,7 +33,7 @@ jobs:
3333
with:
3434
python-version: "3.x"
3535

36-
- name: Verify canonical draft artifacts
36+
- name: Verify chronological AOS artifacts
3737
run: python3 tools/verify_standard_artifacts.py
3838

3939
normative-chapters:

‎CHANGELOG.md‎

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,13 @@
44

55
### Added
66

7-
- Draft status marker.
8-
- Root documentation license.
9-
- Conformance profile draft.
10-
- Standard remediation plan.
11-
- Research preprints directory.
12-
- AxonOS analytical microkernel preprint as non-normative artifact.
13-
- Expanded claims register structure.
7+
- Chronological AOS artifact sequence AOS-0000 through AOS-0011.
8+
- `tools/verify_standard_artifacts.py`.
9+
- `tools/verify_standard_contract.py`.
10+
- `tools/verify_normative_chapters.py`.
11+
- CI jobs for standard contract, standard artifacts, and normative chapters.
1412

15-
### Changed
13+
### Fixed
1614

17-
- Repository positioned as pre-normative Draft 0.1 rather than final standard.
15+
- Missing verifier referenced by CI.
16+
- Non-chronological or incomplete AOS artifact layout.

‎CONFORMANCE.md‎

Lines changed: 6 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -1,66 +1,10 @@
1-
# Conformance Profiles
1+
# Conformance
22

33
Status: Draft.
44

5-
This file defines preliminary AxonOS conformance profiles. These profiles are
6-
not final certification classes. They exist to make implementation claims
7-
specific, testable, and reviewable.
5+
AxonOS conformance is profile-based. Draft profiles are defined in
6+
`standard/AOS-0006-conformance-profiles.md`.
87

9-
## Profile S0 — Documentation alignment
10-
11-
An implementation may claim S0 alignment if it:
12-
13-
- uses AxonOS terminology consistently;
14-
- links to the AxonOS Standard;
15-
- states its implementation status;
16-
- does not claim clinical, regulatory, or final conformance status.
17-
18-
## Profile S1 — SDK boundary compatibility
19-
20-
An implementation may claim S1 compatibility if it:
21-
22-
- emits or consumes typed AxonOS intent events;
23-
- uses explicit capability manifests;
24-
- does not expose raw neural data to applications by default;
25-
- documents ABI and serialization assumptions.
26-
27-
## Profile K1 — Kernel substrate compatibility
28-
29-
A kernel implementation may claim K1 compatibility if it:
30-
31-
- provides bounded task scheduling;
32-
- exposes monotonic time;
33-
- provides bounded IPC or equivalent transport;
34-
- documents unsafe-code surface;
35-
- provides evidence for timing claims.
36-
37-
## Profile C1 — Consent semantics compatibility
38-
39-
A consent implementation may claim C1 compatibility if it:
40-
41-
- represents consent as an explicit state machine;
42-
- supports grant, withdrawal, suspension, and expiry;
43-
- treats withdrawal as terminal for the current session;
44-
- denies application override of safety suspension;
45-
- provides transition tests.
46-
47-
## Profile V1 — Evidence-tagged validation
48-
49-
An implementation may claim V1 validation discipline if every public technical
50-
claim includes:
51-
52-
- value;
53-
- evidence level;
54-
- artifact;
55-
- limitations;
56-
- falsification threshold where applicable.
57-
58-
## Non-conformance
59-
60-
An implementation is not AxonOS-conformant if it:
61-
62-
- grants raw neural data access by default;
63-
- treats consent as a UI-only preference;
64-
- claims real-time behavior without deadlines and bounds;
65-
- claims safety or certification without evidence;
66-
- claims AxonOS affiliation without authorization.
8+
The initial profiles are S0 documentation alignment, S1 SDK boundary compatibility,
9+
K1 kernel substrate compatibility, C1 consent semantics compatibility, and V1
10+
evidence-tagged validation. These profiles are not certification classes.

‎GLOSSARY.md‎

Lines changed: 5 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,8 @@
11
# Glossary
22

3-
## AxonOS
3+
Canonical terminology is defined in `standard/AOS-0002-terminology.md`.
44

5-
The deterministic operating layer for brain-computer interface software.
6-
7-
## Neural permission
8-
9-
A typed capability that grants access to a specific class of neural-derived event or intent without granting access to raw neural data.
10-
11-
## Intent event
12-
13-
A typed, bounded event derived from neural signal processing and exposed across the application boundary.
14-
15-
## Consent state machine
16-
17-
A deterministic model of consent grant, withdrawal, suspension, expiry, and fault transitions.
18-
19-
## Evidence level
20-
21-
A label describing how strongly a claim is supported.
22-
23-
## Reference implementation
24-
25-
A public implementation of part of the AxonOS standard. Reference implementation does not imply certification.
26-
27-
## Hardware-gated consent
28-
29-
Consent enforcement that can drive a hardware interlock or safety state below the application layer.
5+
Important terms include AxonOS, AxonOS Standard, neural data, raw neural data,
6+
typed intent event, neural permission, capability gate, consent state machine,
7+
hardware-gated consent, WCET, WCRT, evidence level, reference implementation,
8+
and conformance profile.

‎GOVERNANCE.md‎

Lines changed: 5 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,9 @@
11
# Governance
22

3-
AxonOS governance is designed around technical clarity, safety discipline, and evidence-tagged evolution.
3+
AxonOS governance is based on technical clarity, evidence-tagged claims, and
4+
auditable change control.
45

5-
## Governance objectives
6+
The canonical governance artifact is `standard/AOS-0011-governance-and-change-control.md`.
67

7-
- Preserve a stable BCI software standard.
8-
- Prevent claim inflation.
9-
- Maintain clear reference implementation boundaries.
10-
- Keep privacy, consent, and real-time behavior reviewable.
11-
- Separate experimental work from normative architecture.
12-
13-
## Change process
14-
15-
Changes to the standard should be introduced through RFCs.
16-
17-
A standard-impacting change should include:
18-
19-
1. motivation;
20-
2. affected components;
21-
3. safety and privacy impact;
22-
4. validation impact;
23-
5. migration notes;
24-
6. implementation status.
25-
26-
## Repository status categories
27-
28-
| Status | Meaning |
29-
|---|---|
30-
| Normative | Defines part of the AxonOS standard |
31-
| Reference | Implements part of the standard |
32-
| Experimental | Explores a future standard extension |
33-
| Integration | Bridges AxonOS with external hardware/software |
34-
| Historical | Preserved for audit or compatibility context |
35-
36-
## Claims policy
37-
38-
No repository should claim:
39-
40-
- certification without certification;
41-
- hardware validation without trace artifacts;
42-
- clinical readiness without clinical evidence;
43-
- affiliation without explicit agreement;
44-
- full formal verification when only bounded checks exist.
8+
Draft 0.1 uses maintainer-led review. Future versions should define steward roles,
9+
review board composition, voting or consensus thresholds, and appeals.

‎LICENSE‎

Lines changed: 5 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,9 @@
11
Creative Commons Attribution 4.0 International Public License
22

3-
By exercising the Licensed Rights, You accept and agree to be bound by the terms
4-
and conditions of the Creative Commons Attribution 4.0 International Public
5-
License.
3+
Documentation in this repository is intended to be licensed under Creative Commons
4+
Attribution 4.0 International (CC BY 4.0), unless otherwise stated.
65

7-
This repository contains documentation for the AxonOS Standard.
6+
You are free to share and adapt the material for any purpose, even commercially,
7+
provided that attribution is given and changes are indicated.
88

9-
You are free to:
10-
11-
Share — copy and redistribute the material in any medium or format.
12-
Adapt — remix, transform, and build upon the material for any purpose, even commercially.
13-
14-
Under the following terms:
15-
16-
Attribution — You must give appropriate credit, provide a link to the license,
17-
and indicate if changes were made.
18-
19-
No additional restrictions — You may not apply legal terms or technological
20-
measures that legally restrict others from doing anything the license permits.
21-
22-
Full license text:
23-
24-
https://creativecommons.org/licenses/by/4.0/legalcode
9+
Full license text: https://creativecommons.org/licenses/by/4.0/legalcode

‎README.md‎

Lines changed: 32 additions & 66 deletions
Original file line numberDiff line numberDiff line change
@@ -2,36 +2,35 @@
22

33
[![CI](https://github.com/AxonOS-org/axonos-standard/actions/workflows/ci.yml/badge.svg)](https://github.com/AxonOS-org/axonos-standard/actions/workflows/ci.yml)
44

5-
**The canonical technical standard for deterministic brain-computer interface software.**
5+
**Canonical draft technical standard for deterministic brain-computer interface software.**
66

7-
AxonOS defines the missing operating layer between neural hardware and intelligent applications: a deterministic, privacy-preserving, capability-gated software foundation for brain-computer interface systems.
7+
AxonOS defines the missing operating layer between neural hardware and intelligent applications:
8+
a deterministic, privacy-preserving, capability-gated software foundation for BCI systems.
89

9-
This repository is the normative documentation hub for the AxonOS standard: architecture, terminology, governance, validation levels, neural permissions, consent semantics, safety boundaries, and reference implementation scope.
10+
Status: **Draft 0.1 — pre-normative.**
1011

11-
AxonOS is not an AI-agent framework, not a wellness app, and not a token project.
12+
This repository is the canonical entry point for AxonOS architecture, terminology,
13+
conformance profiles, validation discipline, neural permissions, consent semantics,
14+
and governance. It is not yet a finalized conformance standard.
1215

13-
It is an operating standard for brain-computer interfaces.
16+
## Canonical AOS artifacts
1417

15-
---
18+
The Draft 0.1 artifact sequence is maintained in [`standard/`](./standard).
1619

17-
## Mission
18-
19-
To establish the deterministic software foundation for safe, private, real-time brain-computer interfaces.
20-
21-
---
22-
23-
## Mandate
24-
25-
AxonOS Standard exists to:
26-
27-
- define the deterministic BCI software architecture;
28-
- maintain neural permissions and consent semantics;
29-
- publish validation levels and evidence requirements;
30-
- coordinate reference implementations;
31-
- prevent unsafe or misleading claims in BCI software infrastructure;
32-
- provide a stable technical vocabulary for researchers, engineers, hardware teams, and institutional partners.
33-
34-
---
20+
| Artifact | Title |
21+
|---|---|
22+
| [`AOS-0000`](./standard/AOS-0000-charter-and-scope.md) | Charter and Scope |
23+
| [`AOS-0001`](./standard/AOS-0001-system-boundary.md) | System Boundary |
24+
| [`AOS-0002`](./standard/AOS-0002-terminology.md) | Terminology |
25+
| [`AOS-0003`](./standard/AOS-0003-evidence-levels-and-claims.md) | Evidence Levels and Claims |
26+
| [`AOS-0004`](./standard/AOS-0004-neural-permissions.md) | Neural Permissions |
27+
| [`AOS-0005`](./standard/AOS-0005-consent-semantics.md) | Consent Semantics |
28+
| [`AOS-0006`](./standard/AOS-0006-conformance-profiles.md) | Conformance Profiles |
29+
| [`AOS-0007`](./standard/AOS-0007-intent-event-model.md) | Intent Event Model |
30+
| [`AOS-0008`](./standard/AOS-0008-ipc-and-timing-contract.md) | IPC and Timing Contract |
31+
| [`AOS-0009`](./standard/AOS-0009-security-and-privacy-threat-model.md) | Security and Privacy Threat Model |
32+
| [`AOS-0010`](./standard/AOS-0010-reference-implementation-mapping.md) | Reference Implementation Mapping |
33+
| [`AOS-0011`](./standard/AOS-0011-governance-and-change-control.md) | Governance and Change Control |
3534

3635
## Principles
3736

@@ -40,53 +39,20 @@ AxonOS Standard exists to:
4039
3. Real-time claims must be falsifiable.
4140
4. Privacy must be structural, not policy-only.
4241
5. Reference implementations must not claim beyond their evidence level.
43-
6. Safety boundaries must be inspectable.
44-
7. Public infrastructure should outlive any single product cycle.
45-
46-
---
4742

4843
## Reference implementations
4944

5045
| Repository | Role |
5146
|---|---|
52-
| [`axonos-kernel`](https://github.com/AxonOS-org/axonos-kernel) | Deterministic real-time kernel substrate |
53-
| [`axonos-sdk`](https://github.com/AxonOS-org/axonos-sdk) | Application-facing typed intent and capability API |
54-
| [`axonos-rfcs`](https://github.com/AxonOS-org/axonos-rfcs) | Engineering RFC process |
55-
| [`axonos-consent`](https://github.com/AxonOS-org/axonos-consent) | Consent state machine and safety-gating semantics |
56-
| [`axonos-swarm`](https://github.com/AxonOS-org/axonos-swarm) | Experimental distributed timing layer |
57-
| [`axon-bci-gateway`](https://github.com/AxonOS-org/axon-bci-gateway) | OpenBCI hardware-in-the-loop acquisition gateway |
58-
59-
---
60-
61-
## Repository map
62-
63-
| File | Purpose |
64-
|---|---|
65-
| [`STANDARD.md`](./STANDARD.md) | Canonical standard overview |
66-
| [`GOVERNANCE.md`](./GOVERNANCE.md) | Governance model and change process |
67-
| [`VALIDATION.md`](./VALIDATION.md) | Evidence levels and validation policy |
68-
| [`SECURITY.md`](./SECURITY.md) | Security and disclosure policy |
69-
| [`GLOSSARY.md`](./GLOSSARY.md) | Canonical terminology |
70-
| [`ROADMAP.md`](./ROADMAP.md) | Public roadmap |
71-
| [`architecture/`](./architecture) | Architecture chapters |
72-
| [`validation/`](./validation) | Claims, evidence levels, falsifiable predictions |
73-
| [`legal/`](./legal) | Disambiguation and attribution notes |
74-
| [`rfcs/`](./rfcs) | RFC index and linkage |
75-
76-
---
77-
78-
## Institutional posture
79-
80-
AxonOS is maintained as an open technical standard with public reference implementations.
81-
82-
Institutional conversations are considered selectively where the collaboration strengthens the standard, validation program, safety review, or reference implementation.
83-
84-
Capital is not treated as a substitute for technical evidence.
85-
86-
---
47+
| `axonos-kernel` | deterministic real-time kernel substrate |
48+
| `axonos-sdk` | typed intent and capability API |
49+
| `axonos-rfcs` | engineering RFC process |
50+
| `axonos-consent` | consent state machine and safety-gating semantics |
51+
| `axonos-swarm` | experimental distributed timing layer |
52+
| `axon-bci-gateway` | acquisition integration gateway |
8753

8854
## Contact
8955

90-
- General / institutional: [connect@axonos.org](mailto:connect@axonos.org)
91-
- Security: [security@axonos.org](mailto:security@axonos.org)
92-
- Project: [axonos.org](https://axonos.org)
56+
General / institutional: connect@axonos.org
57+
Security: security@axonos.org
58+
Website: https://axonos.org

0 commit comments

Comments
 (0)