Docs
This page is a map, not a manual. Each question routes to the document that owns it — the reference pages on this site, or the repository document that holds the depth — so nothing here can drift far from its source.
Cited release v1.20.1
Pick the row that matches why you came. Each one links the shortest correct first read.
The reference pages mirror the shipped command surface of the cited release. If a page and the repository ever disagree, the repository is right and the page has a defect.
Nine forgeos commands — status, next, prompt, brief, intake, doctor, version, adopt, and update — each with its purpose and read/write behavior. Reading commands answer; writing commands dry-run by default and change files only under --apply.
forgeos status reads the state ledger, forgeos next names the next safe slice, forgeos prompt prints the complete session package, and forgeos doctor reports prerequisites — all four read-only.
Twelve checks — eight of them gating — run by one command, with identical behavior on Windows PowerShell 5.1 and POSIX bash. Nothing is called done until the checks are observed passing.
Two routes in, and both end at the same place: your project carries the portable half of ForgeOS and passes its own validation suite. No package-manager channel is listed anywhere on this site until one ships.
Download the archive and its checksum from the release, verify before you trust it, then sync into your project. The first sync is a dry run; review it, then apply.
Start a new project from the repository itself — inspect it first, start from a specific tag, then make the history yours.
First-time adoption is a guided procedure, not a copy step: the adoption guide walks it end to end, and the upgrade guide owns everything that happens afterwards.
Trust claims are the easiest to overstate, so each route below leads to the policy itself — stated in the repository's own words, not this site's summary of them.
The safety hooks are a safety net against accidents, not a security boundary — the policy says so in exactly those terms. The hosted security page explains the limits and routes private reports to the repository advisory flow.
Application paths stay closed until a human opens a narrow implementation window that fails closed in every direction; safety hooks refuse destructive actions with the reason; validation gates demand observed evidence.
Repository issues are the support channel — bug reports, feature requests, and questions, each with a template. Support is best effort with no response-time guarantee, and what is not supported is named rather than implied.
Contributions are judged on evidence: a change ships for both supported platforms, reproduces the bug before fixing it, and never weakens a check to get a pass.
Anonymized write-ups from real adoptions — each verified defect becomes a permanent self-test case. This is the proof behind "proven by adoption, not only self-test."
The transparency pages follow the same rule as everything else here: proven things are marked proven, intentions are marked intentions.
Now, next, and later in the honest status vocabulary — including what is listed as not yet proven, and what is deliberately not built.
Every published version, newest first — what shipped, the artifact it ships as, and the SHA-256 checksum that makes a download verifiable before you trust it.
ForgeOS meets CLI-based coding tools in the environment where they already run. The repository README names the supported tools and their adapter files; this page describes only what the integration does.
Different coding tools read the same operating contract through thin adapter entry points that hold pointers, never rules of their own — so every tool obeys identical rules.
The workflow commands — from /start-task through /finish-task — surface as slash commands inside the tool's own environment, so the governed loop runs where the work happens.
Every document this page routes to is versioned with the code it describes. This site hosts no rendered copies yet; when hosted copies come, each will state the version it documents. Browse the repository. Documentation index.