Repository navigation
devlog TODO
github-actions[bot] edited this page Nov 8, 2026
·
15 revisions
What is being worked on now. The idea of every phase: VISION.md; versions: ROADMAP.md; questions: BRAINSTORM.md; history: ../changelog/.
- AGENTS.md and CLAUDE.md for the core; Cleo's conclusions in
docs/.agents/CLEO.md - Branch
developmentcreated fromdevelopement(Q1) -
developmentpushed to GitHub;developementremoved here (Q1) -
developementremoved on GitHub (Q1; by the owner) - Remotes: this repo →
Sarverott/blacksmith-organization-system, bos-skillset →Sarverott/bos-skillset(Q2; local git config) - Read the Docs: the core has its own MkDocs site (RTD builds the core's repository since the rename) (Q2)
- npm:
package.jsonof the core isblacksmith-organization-system, repository URL the core's (Q2) - Legacy core tagged
legacy/v0.6.1and removed (Q3) - Shell scripts moved from
src/toscripts/ - Devlog in its standard look: README, VISION, ROADMAP, TODO, BRAINSTORM, PROPOSALS, ORDERS, INQUIRIES, Taskfile; draft and old devlog archived in the changelog
- TypeScript toolchain: tsc, vitest, biome, commitizen, commitlint, husky hooks through Taskfile, CI
check
- Core: Host, element anatomy, procedures, tool format, semver + GRIH
- Models: workshop, .BOS and its parts, devarmory, forge, scope, project, craftbook, archive, devlog
-
bos workshop bootstrap: the base of the environment, never overwriting -
bos workshop watch: changes as events in area › scope › project, recorded in storylines -
bos workshop status: the whole workshop as one report with findings -
bos scope version/bos scope bump: GRIH in<scope>/.bos/scope.json(Q5) -
bos devlog state: phases, questions, proposals, waiting orders → STATE.md - README of the core rewritten for the reforged BOS
- The procedures of
scripts/shell-procedures/listed as the next procedures of the core (scripts/README.md) - Development workshop:
WORKSHOP_ROOT/WORKSHOP_RENAME, the checkout's.env(now/run/media/sarverott/setternet-A62/__WORKSHOP) - Watching never goes deaf: one watcher per directory, noise not watched, an exhausted inotify is an error
- Q6–Q9 answered (changelog phase 1); old local branches tagged or deleted (Q9)
- Version
1.0.0: the flip of the reforge (Q7)
- Documentation:
docs/architecture/(models, interfaces, bridges) from theabout-*pages, which are removed - Documentation:
docs/scrapnote-example.mdarchived in the changelog, its ideas placed, the file removed - Documentation: one audience per README -
README.md(npm and everywhere),docs/README.md(the documentation's index),.github/README.md(GitHub) - Documentation:
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdfor the contributors committee - Glossary:
grihandcraft-loop(from the legacydocs/README.md) - The loop as data: stations, directions,
rejection, contributors, automerge per station (from gitrecon); default insrc/models/loop/data.ts, a project's own.bos/loop.json -
bos flow explain/next/next-pr/automerge, through the GitHub bridge (Host.run→gh) - Settings in
.github/bos.json:loop(replaces.bos/loop.json) andversioning(bumps per station) (chat 2) -
bos flow bump <station>: the project's version bumped perversioning, only when already released (tagged) (chat 2) - Checks split: one reusable set (types, lint, tests, build, docs, commits, package); on push only what changed; on pull requests all (chat 3)
- Workflows of the routine: revision (minor bump), release (tag, GitHub release, npm, wiki, webhooks, back into development), the full loop by hand; all with
workflow_dispatch(Q10, Q11) - GitHub wiki:
docs/.gh-wiki(ignored),scripts/gh-wiki.py+resources/docs-templates/,task docs:wiki(inquiry) - AGENTS.md: the routine, and what an agent pushes without asking (chat 1)
- First run of the routine:
developmentpushed, PRdevelopment → master,developmentpushed torevision -
scripts/reduced to what is required: replaced scripts removed (they stay inlegacy/v0.6.1), the rest listed as sketches to port (inquiry) - Tag
v1.0.0and GitHub pre-release: by the release workflow when PR #3 was merged; the wiki synced - Publishing secrets from the environment
publish-env(NPM_TOKEN,READTHEDOCS_API_TOKEN); Read the Docs activates and builds each release - Workflow steps as scripts:
scripts/workflows/*.sh, run astask workflows:<name> - 1.x on npm under
next:v1.1.0(PR #4);v1.0.0itself is not on npm (its tag predates the publish step) - The old
reforgebranch deleted on GitHub (all of it indevelopment) - Workflows named by what they are:
checks-*,loop-*,<registry>-<kind>-publish(inquiry) - The pull request to
masteropened by the revision workflow (revision → master), not by the agent (inquiry) -
.github/AUTHORS:bos project authors(procedurecrediting, glossaryauthors), kept by the revision workflow (inquiry) - Badges: one row in the GitHub, npm and documentation READMEs (inquiry)
- Publishing: npm on GitHub Packages (pre-releases too); container images on Docker Hub and ghcr.io for a full release (
Dockerfile) (the owner's stubs) - Rulesets, as the almanac's coded half (PP1 taken up):
resources/almanac/rulesets/(every project) anddocs/almanac/rulesets/(this one), judged bycore/ruling.ts,bos almanac rules | judge(inquiry) - Patterning: chains of solved situations,
core/patterning.ts(next events with probabilities, chains recalled),bos almanac recall(inquiry) - Q12: every full release is stable (images); an LTS line once two majors live side by side
- A version per commit on
dev/*(pre-commit hook,bos flow bump-commit); versions merge by the higher (bos flow merge-version,.gitattributes); a station bumps once its line is released (inquiry) - Releases that move:
nightly(revision),latest(every release), each with the package's.tgz(inquiry) - Package reports in every README (bundlephobia, socket.dev, Snyk, npmgraph); release files to VirusTotal (inquiry; rejected in Summary 1: no API access)
- Mirrors of the source: gitea.com, gitlab.com, bitbucket.org, sr.ht, every branch and tag, a status badge per place, the checks on each mirror's CI (inquiry)
- The four mirror secrets in
publish-env:MIRROR_GITEA_TOKEN,MIRROR_GITLAB_TOKEN,MIRROR_BITBUCKET_TOKEN,MIRROR_SOURCEHUT_SSH_KEY(the owner) - First run with them: gitea.com and sr.ht take every branch and tag (200 OK); a Bitbucket API token (
ATATT…) signs in asx-bitbucket-api-token-auth(found) - gitlab.com: the fine-grained token needs the project permission Code: Push (the owner; 200 OK since run 42139753049)
- bitbucket.org: green on the next run, else the token's scope
write:repository:bitbucketand the workspaceapokryf(the owner; 200 OK since run 42139753049) - The owner's review notes in the code: biome in more lines,
bos.ts, namespaces,BOS.<Model>,index.ts,JsonFile,packagePath, a readablecli.tsand views,Elementemits events (review) - Git hooks fail again when a check fails:
.husky/taskruns the task binary, not@go-task/cli's npm wrapper (found) - Lint green again on what the version bump writes:
package.jsonformatted as npm writes it (expandalways); actions/checkout and setup-node v5, on Node 24 (found) - The owner's map of bridges:
Bridge(base.ts) →Git→LocalGit/RemoteGit→ GitHub, Gitea, GitLab, Bitbucket, SourceHut;bridges/index.tsexports them all (owner) -
.omnis.toml, a draft:core/omnis.ts(a12y, crc32, adler32, base32, the TOML),Host.digest,LocalGit.files(); glossary page (Q15) -
.omnis.tomlwritten and checked:.bos/.omnis.tomlper model, changeable allocators, the walk stops at another model,bos project omnis | seal, the findingomnis-drift(Q16) - Mirrors sync on a push to
developmentonly, and a failed mirror never fails the run; mirrors only check, never publish (owner) - An open pull request
revision → masterfollows its version: title and description edited on each run (found: PR #9 said v1.4.9, released v1.4.10) - Examples:
examples/01-getting-started/, the library step by step; the owner's00-draft-snippets/kept as written (inquiry) - A
--workshopnot named__WORKSHOPholds one (found by the draft snippets: a second workshop in the partition root);new BOS()asks for a host;workshop.areas
Summary 1 (between Phase 2 and Phase 3, contains 29 steps from previous phases and summaries): extrasteps that was left not done in previous phases
-
steps from Phase 0- related with clearing the ground:- bos-skillset follows the rename: remote, package name, AGENTS.md,
developmentpushed,developementgone from GitHub with its dependabot PR (checked 2026-11-06); its Read the Docs project and two stale branches are notes for that repository (forge/NOTES-for-repositories.md) (Q2)
- bos-skillset follows the rename: remote, package name, AGENTS.md,
-
steps from Phase 1- related with the proof of work: none left -
steps from Phase 2- related with the loop as code:- The full loop driven (
revision → testing → releasing → master),testing/releasingmoved tomaster(Q9, Q10: later) - A language-model categorizer behind a bridge: ollama in a docker container (volume in the workshop's nests, the GPU), through its OpenAI-compatible endpoint; words → a case's fields, the verdict stays code (Q17)
- Sentiment of the flow, not of people: project linkings, abstractions, a writer's fingerprint (human or LLM, personal tone), code below our standard (Q17)
- Rulesets stay JSON; a Markdown page per ruleset generated from a template (as
.gh-wiki), for the GitHub wiki and Read the Docs:docs/_mkdocs/almanac.py,resources/docs-templates/ruleset.md(Q18) - Chains learned by BOS itself, from storylines and the commit history (cataclistics: "where in commits history it appears") (inquiry)
- The almanac's other sections read by code: roles (agent profiles, ollama modelfiles), scenarios, simulations (inquiry)
- A bare new project starts with the same flow:
bos project initseeds the anatomy, the almanac, hooks,.github/bos.jsonand the workflows (inquiry) -
rejected by the owner: no VirusTotal API access; the scan, its script and badges removedVIRUSTOTAL_API_KEYinpublish-env - ghcr.io takes the image: the package
ghcr.io/sarverott/blacksmith-organization-systemexists already (tagsdev,1.0.0-dev.3, pushed before this repository published), so the workflow's token, withpackages: write, is deniedwrite_packageuntil the package grants this repository Write in "Manage Actions access"; then re-run the jobghcrof run 42179570633 (the owner; found on v1.9.0; the package bos-skillset once claimed deleted,1.10.0there since) -
boswithout a command, in a terminal: a REPL (readline), each line one<model> <tool>;bos --replreads piped lines (review) - Watching by the models: each element declares what of it is watched, instead of one tree watcher (review)
- The release
stable: what passed the tests of deployment and of dependent projects, onreleasing(with the full loop) - An LTS line in
versioningonce two majors live side by side (Q12 b) - One shape of every model through
Element(Q13 c): structure on the class (Project.anatomy,Loop.defaultsbesidechildren), a file's default content and its JSON Schema in<model>/descriptors/;bos workshop statuschecks a descriptor against its schema (Q13) - Bridges applied to models (Q14 c with a): a model declares its type and its bridges (class defaults), a place overrides them in its
.craft/; procedures pick the bridges by that (Q14) - Presets of an element in its
.bos/(Q15:.bos/stays, no.craft/):bos.json(model type, bridges), the rest reconsidered (Q15) -
.omnis.tomloutside a git repository (areas of the workshop):.gitignoreread by BOS itself,core/ignore.ts;bos project seal --dir=<area>(Q16) - What seals a model besides
bos project seal:bos close, the routine (Q16) - A scope's VS Code workspace file in the scope, launched when the scope is opened; repositories in a scope are projects by default (Q15)
- The other kinds of bridges, from the owner's map: devops-integration, docs-publishers, apps-extensions, dedicated-implements, project-profiles, scoping-families (owner)
- The homepage:
resources/web/public/(webmanifest, robots.txt, sitemap.xml, llms.txt) generated from package.json, bos.json and the docs; built for GitHub Pages (owner) - Examples: react, vue, astro, each a submodule with its own package.json, run by
examples/Taskfile.yml(owner) - The second workshop the draft made in
/run/media/sarverott/setternet-A62/(.BOS,archive,craftbook,devarmory,forgebeside__WORKSHOP): removed (the owner); now found (areas-beside-workshop), stopped at bootstrap and solved bybos workshop repair - Mirrors: glossary page
archive/.repos-mirrors(each mirror a sarcophag):docs/glossary/repos-mirrors.md(Q6) - Procedure
archiving:bos archive mirror <forge path>→ bare clonearchive/.repos-mirrors/<scope>___<project>.git, dry run first, the forge copy removed only on confirmation, nothing uncommitted and every commit in the mirror (Q6) - Inspecting: a finding for clones in the forge that belong among the mirrors:
mirrored-in-forge, andwork-on-masternamesbos archive mirror(Q6) - Mirrors tried on the development workshop: a clone in
forge/test/mirrored, found by status, removed on confirm (Q6) - The home workshop's read-only clones moved to
archive/.repos-mirrors/(on the owner's order;bos archive mirror <path> --dry-runfirst) (Q6)
- The full loop driven (
- Reconcile the Dependabot batch with clean installs, docs export consistency and major-update evidence
- Review the newly reissued Biome 2.6.5 proposal separately from its initial 2.6.4 head
- Isolate pre-commit tests from Git's hook environment so temporary repositories cannot alter contributor refs
- Record final PR dispositions and checked commit SHAs for the owner
- Group routine bot updates, add lock/audit/container checks, and record the maintenance procedure in the agent notes
- A Docker image of BOS (
Dockerfile; Docker Hub and ghcr.io, done in phase 2) - The first image, with the first full release: v1.10.0 on Docker Hub and ghcr.io (after the package bos-skillset once claimed was deleted)
- The image's badge in the READMEs
- Containers: one per agent host CLI (Codex, Claude Code), one for the owner
- Contexts that isolate: procedures run in
node:vmcontexts, WASI, child processes or a cluster (review: "this all can be used now") - Workmodes: sets of Taskfile tasks with file watchers and git hooks
- Daemons:
bos daemon start | run | stop | reload | rotate | status | logs, a supervisor with a cluster of instances, shared or separate contexts, signals and monitor threads;scripts/devtools/ollama-serve.sh(inquiry) - ollama in a docker container with the GPU: the NVIDIA Container Toolkit on the machine (the owner), then a service run as a container (Q17)
- Daemons started and stopped with the workshop (
bos open,bos close) - The forge's elements made by BOS:
bos scope create,bos project create(the standard anatomy fromresources/project-template/; on an existing project only what is missing),bos project import(gh:owner/repo, any git URL, a path) (inquiry) - Live scenario on the development workshop:
Sarverott/mobile-croakerintoforge/rauson/(the scope its description names),Sarverott/bos-skillsetintoforge/blacksmith-organization-system/, both ondevelopment; findings toforge/NOTES-for-repositories.md(owner) - The loop follows a project's canon:
mainwhere origin keeps it there (found:canon-not-master) - Every area's elements made by BOS: craftbook (craftsets, recipes, scrapnote vaults), devarmory (a tool with its manifest entry), archive (sarcophags),
.BOS(setup, nests) (inquiry) - Importing from other places: a whole account or organisation of GitHub, GitLab, Gitea, Bitbucket into a scope; archives and notes into the craftbook (inquiry)
- Ttystories: the shells' histories (
.BOS/storylines/ttystories/:<ms>\t<dir>\t<command>;historydumps) combined, split into trees of command stories by directory, session and time, secrets redacted; command usage counted; stories become chains of the almanac's patterning, a source of knowledge for BOS (inquiry) - The git bridge (
LocalGitinsrc/bridges/git-integration/, tags only so far) grows: status, add, commit - Scrapnote vaults:
craftbook/<scope>___<project>/scrapnotes/as a git repository (Obsidian vault),<project>/docs/.scrapnotesits link, ignored by the project (Q8) - Workmode
scrapnotes: commit every saved note after a quiet moment;.obsidian/workspace*.jsonignored (Q8)
- An API reference on Scalar (
SCALAR_API_TOKENinpublish-env), once BOS has an HTTP API ([TODO] phase)
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