AES (Authority Evolution Simulator) is a research simulator for studying how authority evolves over time in capability-based systems.
  • C++ 77.7%
  • Python 19.7%
  • CMake 1.3%
  • Lean 0.9%
  • Shell 0.3%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Erik Inkinen 623f8d8727
All checks were successful
clang-format / check-format (pull_request) Successful in 1m12s
markdownlint / markdown-lint (pull_request) Successful in 42s
formal / definitions (pull_request) Successful in 2m22s
ci / smoke (pull_request) Successful in 35m8s
ci / sanitizers (pull_request) Successful in 1h21m38s
markdownlint / markdown-lint (push) Successful in 17s
clang-format / check-format (push) Successful in 29s
formal / definitions (push) Successful in 1m7s
ci / smoke (push) Successful in 31m48s
ci / sanitizers (push) Successful in 2h10m57s
CI: integrate issue 670 budget qualification into paired controls
2026-10-30 05:28:06 +02:00
.forgejo CI: allow bounded full expanded sanitizer suite execution 2026-10-30 05:27:31 +02:00
analysis Phase 2: integrate survival statistics into the research suite (#119) 2026-10-21 06:10:41 +03:00
artifacts CI: integrate issue 670 budget qualification into paired controls 2026-10-30 05:28:06 +02:00
cli Phase 2: parse closed protocols and dispatch explicit research stages (#107) 2026-10-21 04:46:57 +03:00
cmake Phase 2: Propagate sanitizer instrumentation to consumers (#614) 2026-10-20 17:21:39 +03:00
core Phase 2: add independent clone execution and research cut controls (#105) 2026-10-21 07:49:34 +03:00
docs CI: integrate issue 670 budget qualification into paired controls 2026-10-30 05:28:06 +02:00
formal Phase 2: pin Lean and define bounded research types (#132) 2026-10-21 05:32:25 +03:00
io Reject non-JSON number and whitespace syntax (fixes #632) 2026-10-20 20:43:47 +03:00
metrics Phase 1: Strategy-Differentiating Revocation Artifacts and Figure Pipeline (#81) 2026-03-06 13:49:08 +01:00
protocols/protocol-2.2 Phase 2: Freeze scope and source traceability (#84) 2026-10-20 16:33:22 +03:00
research Phase 2: integrate paired controls with selected research infrastructure (#105) 2026-10-27 01:37:43 +02:00
schemas Phase 2: reject trailing newline aliases in protocol schema (#107) 2026-10-21 04:52:16 +03:00
sim Reject exhausted engine clocks and event IDs before mutation 2026-10-20 19:56:43 +03:00
tests Phase 2: integrate paired controls with selected research infrastructure (#105) 2026-10-27 01:37:43 +02:00
tools Phase 2: integrate paired controls with selected research infrastructure (#105) 2026-10-27 01:37:43 +02:00
validation/sel4/environment Phase 2: pin and validate the standard seL4 environment (#148) 2026-10-21 06:40:05 +03:00
workload Phase 1: Strategy-Differentiating Revocation Artifacts and Figure Pipeline (#81) 2026-03-06 13:49:08 +01:00
.clang-format Fix: Code and documentation formatting (#44) 2026-02-04 11:21:19 +01:00
.clang-tidy Phase 0: repository scaffold and conventions (#41) 2026-01-31 19:46:26 +02:00
.editorconfig Phase 0: repository scaffold and conventions (#41) 2026-01-31 19:46:26 +02:00
.gitattributes Phase 2: Preserve legacy semantics and baseline artifacts (#85) 2026-10-20 17:11:13 +03:00
.gitignore Phase 2: pin Lean and define bounded research types (#132) 2026-10-21 05:32:25 +03:00
.markdownlint.json Fix: Code and documentation formatting (#44) 2026-02-04 11:21:19 +01:00
.mdl_style.rb Add .mdlrc 2026-02-04 12:31:54 +02:00
.mdlrc Add .mdlrc 2026-02-04 12:31:54 +02:00
.pre-commit-config.yaml Phase 2: Repair local validation hooks (#605) 2026-10-20 16:28:06 +03:00
CMakeLists.txt Define version-4 research events and transition contracts (P2-07-A) 2026-10-20 20:34:29 +03:00
LICENSE Initial commit 2026-01-31 19:05:44 +02:00
README.md Phase 2: Define independent grant and withdrawal scope (#86) 2026-10-20 18:03:09 +03:00

AES — Authority Evolution Simulator

AES (Authority Evolution Simulator) is a research simulator for studying how authority evolves over time in capability-based systems.

Rather than modeling a concrete operating system or kernel, AES treats authority as a temporal graph and focuses on long-term dynamics such as revocation, provenance, epistemic limits, persistence, and collapse. The simulator is designed to support controlled, reproducible experiments that expose structural limits of authority management in long-lived systems.


What AES is (and is not)

AES is:

  • a research simulator
  • a temporal model of authority and delegation
  • a tool for empirical studies accompanying academic publications

AES is not:

  • an operating system or microkernel
  • a kernel emulator
  • a security product
  • a performance benchmark

The goal is explanatory power, not deployment.


Core design invariants

AES is built around a small number of non-negotiable invariants:

  • All authority changes occur via explicit events
  • Authority state is fully reconstructible from history
  • Simulation runs are deterministic given a seed
  • Metrics are pure functions over history or snapshots
  • There is a strict separation between ground truth and observation

These invariants are established in Phase 0 and preserved throughout all later phases.


Research structure

Development is organized into Phases 0–6. Phases are cumulative: each phase weakens an assumption made by earlier ones.

Phase Focus
Phase 0 Core simulator infrastructure and invariants
Phase 1 Revocation semantics under full knowledge
Phase 2 Summary adequacy and metadata reclamation
Phase 3 Epistemic limits of authority reasoning
Phase 4 Revocation horizons and historical limits
Phase 5 Memory, persistence, and authority residue
Phase 6 Predicting authority collapse

Phases are tracked as milestones in the issue tracker.
Tasks within a phase are tracked as issues, with checklist items corresponding to verifiable work and acceptance outcomes. The Phase 2 protocol fixes its scope, requirements and evidence. The legacy ledger records preserved behavior. The policy scope documentation describes the independent grant and withdrawal components.


Repository structure

The repository is organized by responsibility, not by phase:


cli/        Command-line tools
core/       Core data structures and invariants
docs/       Specifications and phase documentation
io/         Event logs, replay, and serialization
metrics/    Measurement and analysis code
sim/        Simulation engine and execution logic
tests/      Determinism, invariants, and correctness tests
tools/      Auxiliary scripts and helpers
workload/   Workload and stress-test generators


Workflow overview

  • Milestones represent Phases (0–6)
  • Issues represent reviewable outcomes or parents of linked tasks
  • Issue checklists represent verified work and acceptance steps
  • Branches and PRs correspond to individual issues, including closure records
  • Labels describe semantics (e.g. revocation, metrics, epistemic)
  • A single Kanban board is used for daily execution only

Reproducibility

AES is designed so that:

  • identical seeds produce identical event traces,
  • all results can be regenerated from raw logs,
  • figures and tables are derived from scripts, not manual steps.

Reproducibility is treated as a research requirement, not an afterthought.

Workload-Family Experiments

AES sweep mode now emits one row per run in experiment_runs.csv in addition to existing sweep artifacts. This enables workload-family reporting over (strategy, depth, fan_out, seed) instead of single-graph snapshots.

Default Phase 1 workload-family matrix and analysis scripts:

  • config: tools/figures/phase1/sweep_workload_family_default.json
  • run + validate + aggregate + plots: tools/regen-workload-family.sh
  • summary table output: results/summary/by_strategy_depth_fanout.csv

License

AES is released under the MIT License.

See LICENSE for details.


Status

This repository is under active research-driven development.
Interfaces may evolve between phases, but core invariants are preserved deliberately.

If you are reading this as part of an academic artifact evaluation:
the recommended entry point is Phase 0 documentation in docs/.


Citation

A formal citation will be added once the first associated publication is available.