Ghost-ALICE OS
| 언어: 🇺🇸 English | 🇰🇷 한국어 |

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.
Version 0.5.1
Core 0.5.1 and Ghost-ALICE Autopilot 0.5.1 use the current response-route and completion contract. Ghost-ALICE Autopilot requires Core 0.5.1 or later. Both projects use Apache-2.0.
How governed work proceeds
The responding model keeps the user’s objective and constraints, performs authorized work, and judges whether contrary evidence affects a required result or dependency. It corrects affected work when needed and preserves supported results and unresolved requirements.
- Input hooks record the current human input without storing the raw prompt. The responding model selects authorized work; a host tool passes that selection to Core for validation and storage.
- The model asks the host to run the needed tools and reads their actual observations. Valid unchanged evidence retains its original source and verification time.
- The model judges each claim against original evidence, then the complete answer against the user’s objective and constraints. Core authenticates and records both judgments, returning status and references.
- The model submits its answer through the native host. Core’s Stop guard checks the submitted review records. Unresolved required work remains visible.
A route or saved plan does not grant permission. A supported answer can accurately report unfinished work. New input reopens routing without invalidating unchanged evidence; recording errors do not require replaying the business operation.
See the Core architecture for the standalone flow and session gate matrix for the detailed contract. Installing Autopilot adds proof application and approved-plan continuation, as described in the Autopilot architecture.
Quick Start
From the cloned Ghost-ALICE repository, install Core and the official Ghost-ALICE Autopilot addon together. The installer automatically detects the available agent platforms:
bash install.sh --addon autopilot
See the detailed installation guide for cloning, OS-native entrypoints, platform selection, updates and troubleshooting.
Official Addons
Ghost-ALICE Autopilot continues explicitly approved work one item at a time within its session, scope and budget. Installation does not grant run approval. It is maintained in AidALL/ghost-alice-autopilot.
For native commands, custom addon sources, platform selection and removal, use the installation guide and official addon reference.
Documentation Map
| Need | Go to |
|---|---|
| Full installation and update commands | Installation and update guide |
| Uninstall scope and cleanup behavior | Uninstall cleanup procedure |
| Failed update, merge conflict, or reinstall recovery | Troubleshooting |
| Repository layout | Repository structure |
| Skill catalog reference | Skill catalog guide |
| Session gate contract | Session gate matrix |
| Installer compatibility contract | Installer platform compatibility |
| Design principles and architecture | GitHub Wiki |
| Official addon usage | Official addon reference |
| Addon authoring | Wiki: Addon Authoring |
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.
- The responding model selects current work from recorded intent; Core validates the submitted route before host tools execute permitted actions.
- Completion claims require owning evidence; valid unchanged proof is reused at its original source and time.
- The installer tracks managed surfaces and avoids broad deletion when ownership cannot be proven.
Agent visibility command surface:
- Claude Code uses
/visibility strict|dynamic|minimalas its workspace command. - Every platform, including Codex, can inspect and change the same profile value through
_shared/agent_visibility_cli.py. Codex has no/visibilitycommand. - The install-time default is
dynamic. Usebash install.sh --visibility dynamicor.\install.cmd --visibility dynamicto set the initial profile;--agent-visibilityremains 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.