Keep only the philosophy on the design principles and architecture pages - Design principles, English and Korean: delete the sentences that described the current installer, the host formats still in Core code and the context gateway's failure as an exception to the self-failure principle; they stated the current code, which the decision record tracks as unmet decisions - Design principles, English and Korean: delete the clause on line 3 that repeated "not a ceiling" - Architecture, English and Korean: delete the two runtime-detail paragraphs (binding to the latest human input, review lookup, installed runtime modules); the source repository owns runtime behavior
Separate what Ghost-ALICE cannot guarantee from what Core code does not block - Design principles, English and Korean: hosts and generative backends are outside Ghost-ALICE and their behavior is not guaranteed; Core code blocks no tool or answer by design - Design principles, English and Korean: an adapter carries a Core rule in the contract's words only when the model needs it before it has read the contract or cannot read it - The structure diagram's edge labels use the same wording - Every page's language line links both languages as 🇺🇸 English | 🇰🇷 한국어
Use Mermaid's default diagram rendering - Remove the look, layout, edge curve and spacing settings from every diagram
Draw diagram edges as straight lines without shadows - Give every diagram the classic look, the dagre layout and linear edges, so GitHub draws straight lines and no box shadows - Space the layers of the structure boundary figure so its arrow label stays clear of the Core box
Define Core, adapters and the structure boundaries - Define Core as the collection of how the generative backend works under the philosophy - Define an adapter as the layer that translates Core for one host - Open the architecture pages with the structure boundaries and draw what sits inside and outside Ghost-ALICE - End the design principles with why each boundary sits where it does, and link the two sections both ways - Call the recording part Core code, including the retired guard name - Keep the English and Korean pages aligned
Note the intake warning exception at Stop on the architecture pages - A supported Stop adds no output, except one intake warning when the session first waits for an input whose origin Core could not confirm, once per session and cause - Architecture and ko/아키텍처 say so in the Stop row and the diagram's no-output node, in English and Korean
Restructure the wiki by language and reading order - English pages at the root, Korean pages under ko/ - One sidebar per language with the numbered reading order - Page names follow page titles; drop duplicate H1 headings - Label language switches in the other language - Add previous and next links; remove the footer - Remove the link-only onboarding, troubleshooting and Windows pages - Remove Autopilot statements from Home and Addon Authoring