A language-agnostic Apache-2.0 foundation for public open-source projects. It provides durable project context, deny-first agent overlays, typed documentation, community files, and fail-closed onboarding validation without choosing an implementation stack.
The copied repository intentionally fails onboarding / validate until initialization is complete.
-
In
.agents/onboarding.toml, setmode = "project". -
Set
identity.project,identity.owner, and a non-templateidentity.status. -
Set
taxonomy.intended_workspaceto the project name andtaxonomy.registration = "pending". -
Set
accounts.githubto the actualOWNER/REPOSITORYslug. -
In
.codex/onboarding.toml, mirror every validated identity field: setmodetoproject; keeptemplate_repositoryequal to the source template slug; setproject,context_boundary,intended_node_type,workspace, andtaxonomy_registrationto the corresponding shared-manifest values; keepshared_manifestset to.agents/onboarding.tomlandgit_requiredset totrue; and makewsl_requiredequal.agents/onboarding.toml'scapabilities.wslvalue. -
Replace template framing in
README.md,CONTEXT.md,STATE.md, andBOARD.md. -
Validate locally:
python scripts/validate_onboarding.py --root . --repository OWNER/REPOSITORY -
Push the initialization change and wait for
onboarding / validateto succeed. -
Review branch rules only after that first successful run. Choose either signed direct pushes without a required check, or a check-gated pull-request/pre-tested-branch flow; do not combine unrestricted direct-to-
mainpushes with this push-triggered check. -
Review the license, contribution, conduct, and security policies for the real project before inviting contributions.
Taxonomy registration remains a separate action after the real clone path is known.
This template's onboarding contract is intentionally opinionated for Johan-managed personal projects. Other adopters may replace or remove .agents/onboarding.toml, .codex/onboarding.toml, the validator, its tests, and the onboarding workflow together before establishing their own project contract.
After the first successful check, review the generated repository's description, topics, visibility, feature toggles, security settings, private vulnerability reporting, and branch rules. Those settings are not inherited from the template repository.
- Shared agent contract and thin project cockpit
- Tool-neutral onboarding metadata
- Minimal Codex and Claude overlays
- Typed documentation manifest and schema
- Standard-library validator and unit tests
- Read-only, immutable-SHA GitHub Actions validation
- Monthly GitHub Actions dependency updates
- Apache-2.0 license and concise contribution, conduct, security, issue, and pull-request guidance
No account connector, MCP server, plugin, browser, WSL, deploy, production, or tracker capability is enabled by the template. Add only the narrow capability needed for an approved project milestone.
Apache License 2.0. See LICENSE.