Ghost-ALICE OS

Agent governance layer

Keep AI agent work inspectable by recording intent, declaring boundaries, requiring evidence, and preserving installer state across supported runtimes.

Read the docs Install Wiki Addons

Quick start

# macOS / Linux / WSL
git clone https://github.com/AidALL/ghost-alice.git ~/ghost-alice
cd ~/ghost-alice
bash install.sh --addon autopilot

# Windows Command Prompt / PowerShell
git clone https://github.com/AidALL/ghost-alice.git %USERPROFILE%\ghost-alice
cd %USERPROFILE%\ghost-alice
.\install.cmd --addon autopilot

Addons

Use official aliases when they fit. Bring your own addon repository for custom, tenant, or local development work with the same installer entrypoint.

Source	Purpose	Install	Details
official: autopilot	Continue explicitly approved autonomous runs one work item at a time.	`bash install.sh --addon autopilot` `.\install.cmd --addon autopilot`	AidALL/ghost-alice-autopilot
custom source	Install an addon you maintain, fork, tenant-package, or develop locally.	`bash install.sh --addon-source /path/to/addon-repo` `.\install.cmd --addon-source C:\path\to\addon-repo`	Authoring guide

Where to go next

The homepage is a navigation hub. Command truth lives in repo docs and installer help; background explanation lives in the Wiki.

Install

Core install, official addons, custom addon sources, status, doctor, update, and platform selection.

Open install guide

Uninstall

Full uninstall, platform uninstall, selected skill removal, and addon-specific removal boundaries.

Open uninstall guide

Compatibility

Bash-first installer command surface expectations across Codex and Claude Code.

Open matrix

Addon sources

Official aliases, custom repositories, tenant packages, and local development addons.

Open addon sources

Addon authoring

Manifest format and packaging guidance for addons you build or bring in.

Open authoring guide

Korean docs

Reader-facing Korean mirrors for README and repository documentation.

한국어 문서

How it works

Core philosophy. Quality floor first. Operating loop steps and Verification layers stay visible without making the homepage a policy manual.

Gate interaction map

This is the inventory layer: core governance checkpoints first, then workflow and domain packs that run on top. Quality floor as root rule means agent authority follows verified state, not forward momentum.

intent deltasession-intent-analyzer records the current goal, constraints, and criteria.

derived gate judgmentsgovernance consumers compare request state before execution.

boundaryboundary-contract locks allowed and prohibited surfaces.

checkpointtool-checkpoint guards the execution surface.

focusDynamic focus can move through micro, meso, macro, and meta scopes at the scope reopen point.

evidencecompletion-check binds each claim to a claim-evidence-map.

traceio-trace leaves file and tool access auditable.

handoffsupport handoff keeps recovery paths explicit.

Lifecycle support

The public entrypoint stays short; deeper onboarding, FAQ, and background discussion move to docs and wiki pages.

io-trace audit trail

File and external access can be inspected after a turn.

skill-evolution candidates

Behavioral improvement candidates remain report-only until explicitly accepted.

pending-merge review

Installed local edits are surfaced before being overwritten.

adversarial verification

Source-heavy or high-stakes claims can be checked through independent review.

jailbreak drift check

Current requests are compared against accumulated constraints.

runtime recovery

Installer state, support files, and cleanup reports preserve recovery context.