Ghost-ALICE OS

Ghost-ALICE OS is an agent governance layer for AI work. It keeps intent, boundaries, evidence, and runtime state inspectable across supported agent runtimes.

It is not a prompt library, a chatbot wrapper, or a standalone agent runtime. It is the operating layer that makes agent work auditable before the agent claims completion.

Quick Start

macOS, Linux, WSL, or Git Bash:

git clone https://github.com/AidALL/ghost-alice.git ~/ghost-alice
cd ~/ghost-alice
bash install.sh

Windows Command Prompt or PowerShell:

git clone https://github.com/AidALL/ghost-alice.git %USERPROFILE%\ghost-alice
cd %USERPROFILE%\ghost-alice
.\install.cmd

Public install guidance uses OS-native entrypoints with the same long flag surface. Windows uses .\install.cmd ...; macOS, Linux, WSL, and Git Bash use bash install.sh .... install.cmd keeps the Windows native wrapper path, Python 3.11+ installer contract, UTF-8 console setup, and -NoProfile -ExecutionPolicy Bypass; this handles PowerShell execution policy blocks and does not change the user or machine execution policy.

Official Addons

Official addons are maintained as separate repositories and installed from the Ghost-ALICE core checkout with a short alias.

macOS, Linux, WSL, or Git Bash:

bash install.sh --addon <addon>

Windows Command Prompt or PowerShell:

.\install.cmd --addon <addon>

Some official addons add only capability skills. Others can extend runtime workflow behavior. Addon-specific behavior, state files, pause/resume controls, and removal details live in each addon repository.

The autopilot repository is an addon package consumed by the core installer. This install example is not a full runtime compatibility claim; read the addon repository compatibility-matrix.json before making one.

Custom, tenant, or local development addons use --addon-source.

bash install.sh --addon-source /path/to/addon-repo

.\install.cmd --addon-source C:\path\to\addon-repo

Documentation Map

Project Guarantees

• Ghost-ALICE OS is a governance operating layer for agent sessions, not a general-purpose operating system.
• User intent, boundaries, verification criteria, and install state are first-class surfaces.
• Session routing consumes recorded intent and downstream gate state before tool execution.
• Completion claims require fresh evidence when the work has been executed, fixed, or verified.
• The installer tracks managed surfaces and avoids broad deletion when ownership cannot be proven.

Agent visibility command surface:

• Claude Code uses /visibility strict|dynamic|minimal as its workspace command.
• Codex handles /visibility through the trusted UserPromptSubmit hook pseudo-command path.
• Every platform can inspect and change the same profile value through _shared/agent_visibility_cli.py.
• The install-time default is dynamic. Use bash install.sh --visibility dynamic or .\install.cmd --visibility dynamic to set the initial profile; --agent-visibility remains a compatibility alias.
• Visibility changes the user-facing governance message surface only. It does not weaken hook execution, strict-grade logs, or Work-Impact Projection.

Full uninstall:

bash install.sh --uninstall

.\install.cmd --uninstall

Contributing And Validation

Before changing skills, installer behavior, or public command surfaces, read AGENTS.md. After creating or modifying a skill, pass Phases 1-5 of official-docs/derived/skill-compliance-checklist.md.

Public surface validation:

python3 scripts/validate_public_surfaces.py

Session gate contract validation checks the repository contract in skill-catalog/session-gates.json and the user-facing policy surfaces:

python scripts/check_skill_gate_contract.py

Installer compatibility groups:

python3 scripts/run_installer_compat_tests.py --list
python3 scripts/run_installer_compat_tests.py --group public-surface-contract

License

Ghost-ALICE OS project-owned source code and documentation are licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and THIRD_PARTY_NOTICES.md.