Security.
AIEOS treats verification as the security model — nothing reaches Done without evidence, and every decision is on the record.
Last Updated · 24 July 2026
Our Approach
In AIEOS, governance is the security posture. Rather than trusting an AI’s own “it’s done”, work has to earn its way to Done through recorded checks. This is a controlled-pilot build designed to align with governed engineering practice — it is not a certification, and the sections below describe how the system works, not a guarantee against every risk.
Separation Of Powers — The Triple Gate
Distinct roles handle distinct responsibilities, and a claim stays Unverifieduntil it clears them:
- Tests — evidence, not opinion.
- Independent Review — a separate reviewer, not the author.
- Human Decision — your recorded approval is a required gate.
Merging additionally requires a clean dry-run merge. Green is earned, never asserted.
Blind Independent Review
The reviewer challenges the actual diff and never sees the author’s transcript. Self-review is blocked, and an inconclusive result is not approval.
Tamper-Evident Journal
Every step writes to a hash-chained, append-only journal. The record of what was decided, and on what evidence, is designed to be tamper-evident — you can see the history rather than take it on faith. Evidence goes Stale the moment new commits land, so freshness is tracked, never assumed.
Isolated Worktrees
Work is written in isolated git worktrees. Your product repository stays untouched until a change has earned approval and merges cleanly.
Credential & Data Handling
AIEOS is local-first, the official CLIs own sign-in, and API keys are stripped from the execution path. See Data Usage for the full picture of what stays local and what moves when you connect an integration.
Responsible Disclosure
If you believe you have found a security issue, please report it privately by email to john@cybereq.io. Please give us a reasonable window to respond before any public disclosure, and we will acknowledge good-faith reports.
Honest Limitations
AIEOS is a controlled-pilot development build. It is designed to align with governed engineering practice, but it is not a certification of compliance, not a guarantee of security, and not a substitute for your own review, testing and judgement. Use it as the disciplined layer it is intended to be.