Repository navigation
glossary project
github-actions[bot] edited this page Nov 6, 2026
·
2 revisions
DRAFT
One concrete, independent project with its own name and a focused workflow, set up to be a project repository.
It's the basic unit of crafting: something with a clear goal that can be built, released and archived on its own.
Inside a scope: forge/<scope>/<project>.
-
bos project create <scope>/<project>: a git repository ondevelopment, seeded fromresources/project-template/with the standard anatomy (README.md, LICENSE, AGENTS.md, CLAUDE.md, Taskfile.yml, src/, docs/, tests/, .github/, .gitignore) and.bos/bos.json. On a project that exists it only adds what is missing. -
bos project import <source>: a clone (gh:owner/repo,owner/repo, any git URL or a path) intoforge/<scope>/<name>, the scope being the owner's name unless--scopesays otherwise;--seedadds the missing anatomy.
Opened in the forge → released (release posts go through the market stall host) → archived as a sarcophag.
Code that realizes a design is a project, even when it starts from a sheme (e.g. a layout template).
Blacksmith Organization System 1.14.1 · repository · documentation · generated from docs/ by scripts/gh-wiki.py, do not edit here
Home · 1.14.1
- Architecture
- Devlog
- Changelog
- For agents
-
Glossary
- BOS glossary
- Network
- Workshop
- Loop
- Elements