Repository navigation
devlog VISION
github-actions[bot] edited this page Nov 6, 2026
·
2 revisions
BOS turns a programmer's scattered machines, drives and servers into one workshop with a fixed shape, and keeps that shape by code: it builds the base of the environment, listens to what changes in it, and inspects it as one coherent whole. On top of that it runs the craft loop: branches, steps, phases and versions that every BOS project follows the same way, for people and AI agents alike.
This repository is the core: a TypeScript module that does all of it. bos-skillset builds the agents' skills and the Claude Code plugin on top of it.
-
Contributors committee. Every agent and every person is a member: same
loop, same checks, own
dev/<name>branch, own container, own name on the commits (agents sign as co-authors). - Everything is coded. Structures and mechanics are code, not only prose: a behaviour is a procedure, a structure is a model, the loop is data plus an engine. Prose explains why; code says how.
-
Plain mechanics, small files. (from the old devlog, entry 1: the legacy
code was "overartistic"; references stay short, names say what things are.)
One concern per file, collected by the nearest
_index.ts; a procedure has aDESCRIPTION.md. - Elements declare themselves. (old devlog, entry 2: "model is autodeclaring own internals".) A model declares its directory, children and descriptor files once, statically; the same declaration creates it (bootstrapping) and checks it (inspecting).
- Create only what is missing. BOS never overwrites or deletes without an explicit, dry-run-aware step.
-
One door to the machine. The core reaches files, clocks and the
environment only through a
Host, so it can later run in more places than Node (decision on which: later). - The way of working is data. The rules of the environment and the situations met before live in the almanac, written for people and read by code. They ship with the core, so a new project starts with the same flow, and a case can be judged before it is done.
-
Agents have their own space.
docs/.agents/is written by agents and read by people;docs/devlog/is where the owner speaks.
The checklist is TODO.md; the versions are in ROADMAP.md.
-
Clear the ground. Branch
development, legacy code tagged and removed, shell scripts inscripts/, the devlog in its standard look, the TypeScript toolchain (tsc, vitest, biome, commitizen, commitlint, husky, Taskfile, CI). - Proof of work. The core builds the base of a workshop, listens to its changes and inspects it as a coherent environment; scopes carry GRIH versions; the devlog is read as data.
-
The loop as code. The branch loop as data (
.github/bos.json: stations, directions,rejection, automerge, bumps per station) and its engine (bos flow); GitHub workflows that only call the core and run the routine: checks on pull requests, a release on every merge intomaster(tag, npm, docs, wiki, webhooks), the short waydevelopment → masterfirst, the full loop later. -
Workplaces.
dev/<name>branches merged intodevelopment; a container per agent host CLI (Codex, Claude Code) and one for the owner; workmodes as sets of Taskfile tasks with file watchers and git hooks. - The skillset on the core. bos-skillset depends on this package and drops its own copies of the core; its skills, MCP and plugin stay there.
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