Do not trust the thesis. Test the boundary.
This packet gives reviewers the shortest route into AristotleOS: claims to challenge, local verification, research context, limitations, comparison notes, and contribution channels.
Claims to test.
- Commit Gate enforcement happens before consequential execution.
- Warrants are scoped to one canonical action and cannot be repurposed safely.
- Governed adapters refuse before emission rather than merely logging after the fact.
- GEL records and replay artifacts can be independently verified.
- Disconnected operation stays bounded by delegated authority and reconciles without silent permission drift.
- Website and documentation claims remain narrower than the implementation supports.
Reviewer verification
Run the 18-check flow covering Commit Gate, Warrant verification, swarm partition, and replay artifact equality.
Research library
Read the papers behind authority routing, evidence ledgers, G-Plane architecture, insurability, 6G governance, and governance kernels.
Adjacent systems
Compare AristotleOS against policy engines, provenance systems, agent frameworks, and execution-control peers.
Non-claims
Read limitations before treating any claim as certified, audited, or production validated.
What useful feedback looks like.
Technical finding
A reproducible bypass, weak invariant, Warrant-binding problem, replay mismatch, or adapter emission path.
Claims finding
A website, README, paper, or demo claim that is broader than the current implementation proves.
Integration finding
A framework, runtime, protocol, or deployment path where the governed boundary is unclear or incomplete.