Repository navigation
glossary sheme
github-actions[bot] edited this page Nov 5, 2026
·
1 revision
DRAFT. Spelled sheme (older scheme).
Source material that isn't code, kept next to the projects it belongs with:
- images and graphics project files (e.g. GIMP)
- Blender and CAD project files, and their renders
- photos: they follow the same patterns of use
- notes and notebooks, playgrounds, live-code docs, VM or container sandboxes, partial ttystories, test areas
- some PDFs and other documents from outside sources (third-party authorship) kept for their reference value
The boundary: a layout template from a design program is a sheme. The code that realizes that design is a project that uses the sheme as its starting point.
A lot of valuable work has no build or release. Shemes give it a proper home in the scope, instead of loose folders.
Inside a scope.
- The old scrapnote defines SHEME differently: "organizing the processing
routes of delegations: HF uploaders, publish routines, deploy automation".
Is that still part of sheme, or now a different element (postroad?)? [
TODO] - How to link third-party reference material: through exhibits? [
TODO] - Idea: GIMP history bound to VCS: a new branch per session, a commit per action named after it, undo as revert, frame-by-frame export of changes.
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