Local-first

AEGIS should operate primarily against local vaults, local tools, and user-controlled data.

Optional

SentinelOS should remain useful without forcing an assistant layer or online account.

Bounded actions

Actions should be explicit, auditable, and constrained by tool contracts and user authority.

Public framing

Assistant layer, not cloud dependency.

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 control
v0.9.5 ecosystem map

AEGIS Core known baselines

A.V.I.C · AEGIS Vault Intake Console

v1.0 locked

Vault intake, quarantine, sanitation and import workflow.

S.C.A.N · Sentinel Checksum & Audit Node

v1.0 locked

Certification, checksums, dashboard and repair-plan generation.

V.A.U.L.T · Vault Access Utility & Lookup Terminal

v1.0 locked

Vault lookup, access, manual workflow and archive/delete handling.

R.E.P.O · Repository Organizer & Package Operator

v1.0 locked / private internal

Private/internal repository organization and package operation tooling.

B.A.S.T.I.O.N · Backup Archive & Snapshot Integrity Operations Node

v1.0 locked

Snapshot, backup integrity and checksum generation workflow.

A.R.C · AEGIS Runtime Console

v1.2 latest recorded

Runtime control console. Preferred command label: arc-control.

Sentinel Command · AEGIS Edition

v1.0 locked

Dashboard, repair plans, package flows and local command layer.

Vault Setup · AEGIS Vault Setup

v1.0 locked

Vault create, verify, repair, wipe and first-run setup workflow.

Publication boundary: AEGIS tool records describe known project baselines. Exact public package names, checksums and signatures still need final publication mapping.