Local-first
AEGIS should operate primarily against local vaults, local tools, and user-controlled data.
AEGIS is designed as a local-first assistant layer that works with local files, local tools, vault-aware workflows, explicit authority, and bounded actions.
AEGIS should operate primarily against local vaults, local tools, and user-controlled data.
SentinelOS should remain useful without forcing an assistant layer or online account.
Actions should be explicit, auditable, and constrained by tool contracts and user authority.
The website should describe AEGIS carefully: local-first, optional, advisory by default, and user-authorised for actions. Avoid language that implies cloud control or uncontrolled autonomy.
AEGIS principle:
local files
local tools
explicit authority
bounded actions
user controlv1.0 locked
Vault intake, quarantine, sanitation and import workflow.
v1.0 locked
Certification, checksums, dashboard and repair-plan generation.
v1.0 locked
Vault lookup, access, manual workflow and archive/delete handling.
v1.0 locked / private internal
Private/internal repository organization and package operation tooling.
v1.0 locked
Snapshot, backup integrity and checksum generation workflow.
v1.2 latest recorded
Runtime control console. Preferred command label: arc-control.
v1.0 locked
Dashboard, repair plans, package flows and local command layer.
v1.0 locked
Vault create, verify, repair, wipe and first-run setup workflow.