Repository navigation
glossary element anatomy
github-actions[bot] edited this page Nov 5, 2026
·
1 revision
DRAFT. A pattern seen across the author's annotations, written down to be confirmed: most BOS elements are a directory plus descriptor files.
| File | Role | Seen in |
|---|---|---|
metadata.json |
identity and origin: what it is, who or what host created it, when | craftset, storylines |
manifest.json / .manifest.json
|
integrity: checksums and security data | craftset, nests, storylines manifests/, devarmory manifest |
.index.json |
map: what is where | nests |
Taskfile.yaml |
procedures: the element's commands (Task) | craftset, .BOS
|
.omnis.toml |
[TODO] |
craftset, .BOS
|
workshop.json |
the workshop's own definition | .BOS |
If every element describes itself the same way, BOS doesn't need special code per element. One reader handles any directory: identify it (metadata), verify it (manifest), navigate it (index) and operate it (Taskfile). This is the "skeleton" of an ordered workspace. It also matches the old notes' wish for "taskfile, husky and a standard command set".
- Is this the intended rule for all elements (scope, project, sarcophag…), or only some? [
TODO] - What
.omnis.tomlholds, and how it differs frommetadata.json[TODO] - JSON schemas for these files [
TODO]
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