Ghost-ALICE OS

Documentation

언어: 🇺🇸 English 🇰🇷 한국어

Ghost-ALICE OS documentation is bilingual at the reader-facing documentation layer. English remains the default repository entry path. Korean counterparts live under docs/ko/ with the same subdirectory shape.

Every paired document has a language switch near the top. The language policy defines its format.

Core 0.5.1 and Ghost-ALICE Autopilot 0.5.1 use the routing and managed completion APIs. Ghost-ALICE Autopilot requires Core 0.5.1 or later. Source checks, native runtime validation and publication establish separate evidence.

The responding model judges claims against original sources and the complete answer against the user objective. Core authenticates the records; the native host displays the answer. See the Core architecture for the standalone flow and the Autopilot architecture for the addon’s proof application and approved-plan continuation.

Quick Install

From the cloned Core repository, install Core and Ghost-ALICE Autopilot together with automatic agent-platform detection:

bash install.sh --addon autopilot

The agent continues approved work across status questions and corrections, retains its authorized boundaries, and connects each completion claim to the relevant item’s evidence. The installation guide covers cloning, OS-native commands and explicit platform selection.

Start Here

  1. Install or update from getting-started/installation.md.
  2. Recover blocked updates from getting-started/troubleshooting.md.
  3. Understand the repository map from reference/repository-structure.md.
  4. Understand the installer architecture from reference/installer-architecture.md.
  5. Use SUPPORT.md and GitHub Issues for public questions.
  6. Use SECURITY.md for private vulnerability reporting.

Documentation Layout

Area Role English Korean
Getting Started Install, update, recovery, and uninstall procedures getting-started/ ko/getting-started/
Concepts Project model and documentation language policy concepts/ ko/concepts/
Reference Repository map, public skills, hooks, and command surfaces reference/ ko/reference/
Policies Runtime, platform, and evaluator contracts policies/ ko/policies/
Release Public release checks and validation guidance release/ ko/release/

Document Map

Intent English Korean
Architecture and responsibilities ../architecture.md ../architecture_ko.md
Documentation index docs/README.md ko/README.md
Installation and update flow getting-started/installation.md ko/getting-started/installation.md
Git/update troubleshooting getting-started/troubleshooting.md ko/getting-started/troubleshooting.md
Uninstall cleanup getting-started/uninstall.md ko/getting-started/uninstall.md
Repository structure reference/repository-structure.md ko/reference/repository-structure.md
Installer architecture reference/installer-architecture.md ko/reference/installer-architecture.md
Skill catalog guide reference/skills.md ko/reference/skills.md
Official addons reference/official-addons.md ko/reference/official-addons.md
Language policy concepts/language-policy.md ko/concepts/language-policy.md
Runtime gate matrix policies/session-gate-matrix.md ko/policies/session-gate-matrix.md
Platform compatibility policies/installer-platform-compatibility-matrix.md ko/policies/installer-platform-compatibility-matrix.md
Tool output semantics policies/tool-output-semantics.md ko/policies/tool-output-semantics.md
Platform adapter compliance policies/platform-adapter-compliance.md ko/policies/platform-adapter-compliance.md
Live smoke regression policies/live-smoke-regression.md ko/policies/live-smoke-regression.md
Evaluator artifact contract policies/evaluator-artifact-contract.md ko/policies/evaluator-artifact-contract.md
Public release checklist release/public-release-checklist.md ko/release/public-release-checklist.md

Canonical Contributor Documents

CONTRIBUTING.md, SUPPORT.md and official-docs/ use English as the canonical contributor path. Keep control tokens literal; paired reader guides are listed above.

Update Rule

  1. Update the English default page first.
  2. Update the Korean counterpart in the same change when the reader-facing meaning, path, command, or policy changes.
  3. Keep CLI flags, paths, hook names, skill names, enum values, and schema fields literal.
  4. Translate the surrounding explanation and preserve executable tokens.
  5. Keep English documents linked to English documents and Korean documents linked to Korean counterparts when a counterpart exists.
  6. Update this map whenever a user-facing document is added, moved, or paired.