Forge Platform

Maintainer setup

Canonical Markdown for Forge Platform lives in autowww/forge-platform. This published handbook is produced from the forge-platform submodule in forge-platform-website via:

python3 generator/build-site.py

Refresh the submodule pointer when you integrate upstream commits from the standalone platform repo.

Bootstrap and validation

Bootstrapping or overwriting foundational files uses the scripted generator in the platform repo:

python3 bootstrap_forge_platform_foundation.py          # skips existing paths
python3 bootstrap_forge_platform_foundation.py --force    # intentional overwrite
python3 scripts/check_foundation.py

check_foundation.py uses only the Python standard library: it verifies required artifacts, validates JSON Schema, and checks sample schema fields.

Cursor Composer

Forge Platform Cursor Composer operator prompts (foundation refresh → assay → sprint charge → stubs) ship under .cursor/composer/ in the platform repo so they stay out of this handbook build.

Canonical vs submodule copy

Keep the standalone forge-platform repository the source of truth; bump the submodule in consumers after you push upstream. Editing only the embedded copy without publishing upstream forks the narrative.