SentinelOS
A familiar, local-first desktop
Download
Boundary: AEGIS assists, reports and performs only authorised local actions. The user remains the final authority. Secrets, private repositories and AEGIS Prime are not included in the public conversion.
1. Installation

Install AEGIS only after the non-AEGIS SentinelOS release gate passes.

The final public conversion defaults to no AEGIS runtime. This avoids making the assistant a dependency of the operating system. Install both the suite and its conditional theme from the signed repository:

sudo apt update
sudo apt install aegis-sentinel-suite=1.2.2-1 sentinelos-aegis-theme=1.0.1-1
sudo aegis-public-suite-verify --system
sudo aegis-public-suite-initialize-user USERNAME
sudo sentinelos-aegis-theme --verify
sudo sentinelos-aegis-theme-apply-user USERNAME

Replace USERNAME with the normal desktop account. Log out and back in after the theme is applied.

aegis-sentinel-suite=1.2.2-1

Provides the complete public AEGIS application cohort and coordinated local workflows.

sentinelos-aegis-theme=1.0.1-1

Provides the conditional navy, grey and gold visual identity. It should not be present on a base non-AEGIS machine.

2. First run

Establish a known-good vault and backup before advanced use.

  1. Verify the installed suite.

    Run the system verifier and resolve missing packages or ownership errors before creating data.

  2. Open AEGIS Vault Setup.

    Create or select the local vault root, verify permissions and record where backups will be stored.

  3. Create the initial structure.

    Initialise intake, quarantine, sanitised import, index, reports and backup locations for the signed-in user.

  4. Create a baseline backup.

    Use B.A.S.T.I.O.N before importing important material or changing A.R.C runtime settings.

  5. Open Sentinel Command.

    Review suite health, component availability and any warning before beginning normal workflows.

3. Components

Use each tool for its defined responsibility.

Suite hub

Sentinel Command

Provides the public dashboard, state summary, package and repair-plan coordination, and the user-facing command layer. It is the first place to assess overall suite health.

sentinel-command
First-run setup

AEGIS Vault Setup

Creates, verifies, repairs or deliberately wipes the user vault structure. Destructive actions require explicit user confirmation.

aegis-vault-setup
Intake

A.V.I.C

Moves material through intake, quarantine, sanitation, approval and import. It prevents unreviewed material from being treated as trusted vault content.

avic
Audit

S.C.A.N

Calculates checksums, audits records, certifies known-good state and generates repair plans. It should report uncertainty rather than silently rewriting evidence.

scan-node
Lookup

V.A.U.L.T

Searches and retrieves authorised local records and handles deliberate archive or deletion workflows.

vault-terminal
Recovery

B.A.S.T.I.O.N

Creates snapshots, backup archives, integrity records and restore evidence for the public vault.

bastion
Advanced control

A.R.C

Controls approved AEGIS runtime settings and local model or service state. Change one setting at a time and keep a rollback point.

arc-control

Package builds may expose additional aliases. Use command -v and the installed desktop entries to confirm the executable on the machine.

4. Permissions and secrets

Grant the minimum authority required for one task.

Denied by default

Applications and assistants should not receive vault, credential, document or automation access merely because they are installed.

Granular approval

Authorise the specific tool, data category and action. Separate read, write, execute, export and delete authority.

Credential vault boundary

Stored secrets remain encrypted and outside public build outputs. AEGIS may use a selected secret only after the user grants that specific permission.

Reviewable actions

High-impact operations should show the target, scope and expected result before execution.

No unrestricted model access

A model should receive the minimum necessary context, not a raw dump of the complete vault or credential store.

User revocation

Permissions should be removable without breaking the underlying application or operating system.

5. Vault lifecycle

Move data through explicit trust states.

  1. Intake.

    Place new material in the intake area without treating it as trusted.

  2. Quarantine.

    Keep it isolated while provenance, file type and security checks are reviewed.

  3. Sanitise.

    Create a safe working copy where the workflow supports sanitation. Preserve evidence of the original separately when required.

  4. Authorise import.

    The user approves the item, destination and metadata before it enters trusted storage.

  5. Index and checksum.

    S.C.A.N records a digest and V.A.U.L.T makes the item discoverable under approved permissions.

  6. Back up.

    B.A.S.T.I.O.N creates a verified recovery copy after meaningful changes.

6. Everyday workflows

Combine the tools in predictable sequences.

01

Add a document

Use A.V.I.C for intake and quarantine, review the result, approve import, run S.C.A.N to record the checksum, confirm lookup in V.A.U.L.T and create a B.A.S.T.I.O.N backup.

02

Find trusted information

Search from Sentinel Command or V.A.U.L.T, confirm source and trust state, then open only the authorised result. Missing provenance should remain visible.

03

Respond to a warning

Read the summary in Sentinel Command, open S.C.A.N for evidence, review the repair plan, back up, then apply only the targeted correction.

04

Change runtime settings

Create a snapshot, record the current state, change one A.R.C setting, test suite health and roll back immediately if behaviour becomes unclear.

05

Archive or remove material

Use V.A.U.L.T, verify the selected item and dependencies, create a backup, then authorise archive or deletion explicitly.

06

Use a stored credential

Select the exact credential in Password Vault, grant the approved application a bounded use permission, complete the local action and revoke unnecessary access afterward.

7. Backup and restore

Treat recovery as part of normal operation.

Before change

Create a snapshot before bulk import, cleanup, repair, archive, delete or A.R.C changes.

After backup

Verify the archive and checksum record. Keep at least one copy away from the main vault location.

Before restore

Confirm target, date and digest. Restore into a safe location first when practical, then compare before replacing working data.

Never rely on the only copy. A snapshot stored on the same failing disk is not a complete recovery strategy.
8. Health and repair

Preserve evidence and apply one bounded repair.

  1. Verify package state.

    Confirm the exact AEGIS suite and theme packages are installed.

  2. Run the public suite verifier.

    Use the system verifier to identify missing components or ownership errors.

  3. Inspect Sentinel Command.

    Read component status and the proposed repair plan.

  4. Create a backup.

    Protect the last known working state before repair.

  5. Apply the smallest repair.

    Correct the specific package, permission, index or runtime fault.

  6. Re-verify.

    Run package, suite, theme and vault checks again and preserve the result.

9. Command reference

Use system commands for verification and initialisation.

aegis-public-suite-verify --systemVerify the complete public suite at system scope.
sudo aegis-public-suite-initialize-user USERNAMEInitialise package-owned user integration for the target account.
sentinelos-aegis-theme --verifyVerify the conditional AEGIS theme package.
sudo sentinelos-aegis-theme-apply-user USERNAMEApply the AEGIS visual baseline to the selected user.
dpkg-query -W aegis-sentinel-suite sentinelos-aegis-themeShow installed package versions.
command -v sentinel-repoShould return nothing on the public system because private R.E.P.O is forbidden.
10. Disable or remove

Preserve user data, return to the base theme, then remove packages deliberately.

  1. Export and back up AEGIS data.

    Verify the backup before package removal.

  2. Revoke integrations and secrets.

    Remove application permissions and lock credential access.

  3. Return the user to SentinelOS Light.

    Apply the base GTK, Marco, icon and cursor themes before removing the AEGIS theme package.

  4. Remove only the public suite packages.

    Review the apt transaction and do not allow unrelated user data or SentinelOS base packages to be removed.

  5. Verify the base system.

    Run the SentinelOS release and drift audits after removal.

11. Troubleshooting

Resolve common fault states methodically.

Gold theme but no AEGIS apps

Verify aegis-sentinel-suite. A base system should not retain the conditional theme without the complete suite.

App command missing

Check the package version and desktop file. Reinstall the owning signed package rather than creating unmanaged aliases.

Vault permission error

Confirm the signed-in account, vault ownership and package initialisation. Do not solve a user-vault problem by running the desktop application as root.

Checksum mismatch

Preserve both copies, stop import or restore, confirm the expected digest and investigate storage or modification history before trusting either file.

Index cannot find an item

Confirm the import completed, the item is in an authorised location and S.C.A.N recorded the expected metadata before rebuilding only the affected index.

A.R.C change caused instability

Restore the previous setting or snapshot, verify suite health and document the failed change before attempting another configuration.