blacksmith-organization-system 1.0.0-dev.3 → 1.1.0

package/resources/workshop-root/AGENTS.md

@@ -1,92 +0,0 @@
-# __WORKSHOP — Blacksmith Organization System (BOS) root
-
-Default guideline for all LLMs and AI agents (Claude Code, Codex, Gemini CLI,
-Copilot, Cursor, Aider, and any other agent) working on this machine.
-
-## Recognizing the workshop
-
-A directory named `__WORKSHOP` is the **standard working area** and the
-**default root of code crafting** in the Blacksmith Organization System (BOS).
-Treat it as such in most cases, unless the user says otherwise.
-
-| Scope         | Path                        | Meaning                                  |
-| ------------- | --------------------------- | ---------------------------------------- |
-| Per user      | `~/__WORKSHOP`              | The user's home workshop                 |
-| Per partition | `/media/**/__WORKSHOP`      | A workshop living on a mounted partition |
-
-Rules:
-
-1. When asked to create, clone, or look for a project without an explicit path,
-   assume it belongs inside a workshop — by default `~/__WORKSHOP`.
-2. When the current working directory is inside any `__WORKSHOP`, the nearest
-   ancestor named `__WORKSHOP` is the active workshop root.
-3. Several workshops may exist at once (home + partitions). Do not merge, move,
-   or sync between them unless the user asks.
-4. Never delete or restructure the top-level workshop areas listed below.
-5. The standard areas must always exist. If one is missing, create it and
-   tell the user. (BOS does this at boot, but don't rely on BOS running.)
-
-## Standard areas
-
-Every workshop always contains these areas:
-
-```
-__WORKSHOP/
-├── .BOS/         BOS itself (internal): setup, data, nests, storylines
-├── devarmory/    tools
-├── forge/        active work
-├── craftbook/    notes, recipes, procedures
-└── archive/      work at rest
-```
-
-### `.BOS/`
-
-Internal area where BOS keeps itself: `setup/` (SSH keys, VPN, routing, DNS/SSH
-aliases, tokens), `data/`, `nests/` (container and VM volumes), `storylines/`
-(shell history, logs, origin metadata). Don't put crafted work here.
-
-### `forge/`
-
-Center of the craftspace: what is open and in focus right now. Grouped by scope
-(formerly "superproject"): `forge/<scope>/<repository>`.
-
-### `archive/`
-
-Integrity base: non-releasable repos and mirrors that buffer between the forge
-and remote servers. Holds sarcophags (encrypted containers, one bare repo each).
-
-### `devarmory/`
-
-The developer's armory: custom tools outside the standard `bin`, AppImages,
-containerized build environments, IDE sets. Listed in a manifest with
-checksums, so missing or damaged tools can be detected and restored.
-
-### `craftbook/`
-
-Knowledge: scrapnotes (every note or draft not yet promoted to a document, in
-`craftbook/scrapnotes/`), craftsets (reusable kits of notes, notebooks, one-off
-scripts and session setup) and recipes.
-
-## Conventions
-
-- Naming of projects and directories: [`TODO`]
-- Grouping of related repositories: `forge/<scope>/<repository>`
-- Every project carries the standard anatomy: `README.md`, `LICENSE`,
-  `AGENTS.md` (+ `CLAUDE.md` importing it), `Taskfile.yml`, `src/`, `docs/`,
-  `tests/`, `.github/`
-- Branches of every repository: `master` (spine of canon) → `developement`
-  (here we code) → `revision` → `testing` → `releasing` → back to `master`
-  through a pull request. Work on `developement`, never directly on `master`.
-- Git / remotes policy: scope repositories are private, kept on a self-hosted server (e.g. Gitea) with pre-public drafts; public projects on GitHub (`Sarverott`); details [`TODO`]
-- Moving work between areas (lifecycle): forge → archive → canon; details [`TODO`]
-
-## BOS itself
-
-BOS lives in the forge like any project:
-`forge/blacksmith-organization-system/bos-skillset`
-(https://github.com/Sarverott/blacksmith-organization-system).
-This file is deployed from its `resources/workshop-root/` by `bos bootstrap`.
-
-- `bos status` shows the workshop tree and what is missing; `bos open` / `bos close` run the procedures
-- definition of every element, one page each: `bos-skillset/docs/glossary/`
-- agent skill: `bos-skillset/skills/bos-workshop/`

package/resources/workshop-root/CLAUDE.md

@@ -1 +0,0 @@
-@AGENTS.md

package/resources/workshop.default.json

@@ -1,6 +0,0 @@
-{
-  "name": null,
-  "role": "forging-point",
-  "setternet": null,
-  "mode": "conform"
-}

package/skills/bos-archive/SKILL.md

@@ -1,28 +0,0 @@
----
-name: bos-archive
-description: "Repositories at rest: the integrity base of the workshop. Use when creating, finding or handling a BOS archive, or when the user mentions a archive."
----
-
-# Archive (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/archive.md` and `src/models/archive/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-Repositories at rest: the integrity base of the workshop. It holds scopes as
-compressed, individual parts with their full history, mirrors buffering
-between the craftspace and remote servers, and non-releasable repositories.
-
-## Where
-
-`__WORKSHOP/archive/`
-
-## Handling
-
-[`TODO`] procedures and commands for a archive.
-
-## References
-
-- [glossary](../../docs/glossary/archive.md)
-- [model](../../src/models/archive/class.mjs)

package/skills/bos-craftbook/SKILL.md

@@ -1,32 +0,0 @@
----
-name: bos-craftbook
-description: "The workshop's knowledge area: drafts, notes, recipes and reusable procedures. Use when creating, finding or handling a BOS craftbook, or when the user mentions a craftbook."
----
-
-# Craftbook (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/craftbook.md` and `src/models/craftbook/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-The workshop's knowledge area: drafts, notes, recipes and reusable procedures.
-The old scrapbook was a synchronized notebook that gathered notes from
-projects, shemes and throwboxes. The craftbook continues that role.
-
-## Where
-
-`__WORKSHOP/craftbook/`
-
-## Submodules
-
-- `scrapnotes` → `scrapnotes/`
-
-## Handling
-
-[`TODO`] procedures and commands for a craftbook.
-
-## References
-
-- [glossary](../../docs/glossary/craftbook.md)
-- [model](../../src/models/craftbook/class.mjs)

package/skills/bos-craftset/SKILL.md

@@ -1,36 +0,0 @@
----
-name: bos-craftset
-description: "A reusable kit for a kind of work. Use when creating, finding or handling a BOS craftset, or when the user mentions a craftset."
----
-
-# Craftset (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/craftset.md` and `src/models/craftset/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-A reusable kit for a kind of work. It combines notes, interactive notebooks
-(e.g. Jupyter with Python) and short one-off scripts that turn out to be handy
-as procedures in later revisions and updates.
-
-Files:
-
-- mandatory: `.omnis.toml`, `metadata.json`, `manifest.json`, `Taskfile.yaml` (see [element anatomy](element-anatomy.md))
-- optional: a VS Code workspace file
-- optional: a shell launcher and bootstrap script with a preconfigured layout
-  of displays, program windows and multiple desktops with predefined roles
-
-## Where
-
-In the [craftbook](craftbook.md). Repositories may also carry a `.craftset/`
-directory (seen in BOS component repos).
-
-## Handling
-
-[`TODO`] procedures and commands for a craftset.
-
-## References
-
-- [glossary](../../docs/glossary/craftset.md)
-- [model](../../src/models/craftset/class.mjs)

package/skills/bos-devarmory/SKILL.md

@@ -1,34 +0,0 @@
----
-name: bos-devarmory
-description: "The set of development tools needed for work in the forge, especially for a particular scope. Use when creating, finding or handling a BOS devarmory, or when the user mentions a devarmory."
----
-
-# Devarmory (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/devarmory.md` and `src/models/devarmory/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-The set of development tools needed for work in the forge, especially for a
-particular scope. The tools are listed in a manifest index, so BOS can download
-them automatically and make them reachable: desktop shortcuts, or entries in
-the workspace shell's `PATH`.
-
-Belongs here: every custom tool outside the standard `bin` files,
-containerized production environments for building or compiling, IDE sets for
-packing and uploading microcontroller firmware that share one configuration
-across many cases, and every AppImage used by the user or an AI.
-
-## Where
-
-`__WORKSHOP/devarmory/`
-
-## Handling
-
-[`TODO`] procedures and commands for a devarmory.
-
-## References
-
-- [glossary](../../docs/glossary/devarmory.md)
-- [model](../../src/models/devarmory/class.mjs)

package/skills/bos-exhibit/SKILL.md

@@ -1,28 +0,0 @@
----
-name: bos-exhibit
-description: "A view built from sarcophags in the archive. Use when creating, finding or handling a BOS exhibit, or when the user mentions a exhibit."
----
-
-# Exhibit (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/exhibit.md` and `src/models/exhibit/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-A view built from [sarcophags](sarcophag.md) in the [archive](archive.md).
-*(assumed)* The presentable form of archived work, and a way to link archived
-third-party reference material (see [sheme](sheme.md)).
-
-## Where
-
-[`TODO`]
-
-## Handling
-
-[`TODO`] procedures and commands for a exhibit.
-
-## References
-
-- [glossary](../../docs/glossary/exhibit.md)
-- [model](../../src/models/exhibit/class.mjs)

package/skills/bos-forge/SKILL.md

@@ -1,28 +0,0 @@
----
-name: bos-forge
-description: "The active workspace, the equivalent of a desk. Use when creating, finding or handling a BOS forge, or when the user mentions a forge."
----
-
-# Forge (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/forge.md` and `src/models/forge/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-The active workspace, the equivalent of a desk. It holds only projects that are
-open and under active development. If something is in the forge, it is being
-worked on.
-
-## Where
-
-`__WORKSHOP/forge/`
-
-## Handling
-
-[`TODO`] procedures and commands for a forge.
-
-## References
-
-- [glossary](../../docs/glossary/forge.md)
-- [model](../../src/models/forge/class.mjs)

package/skills/bos-house/SKILL.md

@@ -1,52 +0,0 @@
----
-name: bos-house
-description: "The House of Anubis as code: the AI residents of the setternet, grouped into families, each with a state and, for ravens, a duty. Use when creating, finding or handling a BOS house, or when the user mentions a house."
----
-
-# House (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/house.md` and `src/models/house/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-The House of Anubis as code: the AI residents of the setternet, grouped into
-families, each with a state and, for ravens, a duty. Residents are local
-(served by ollama) or remote (instances built on world-scale online models).
-
-| State | Meaning |
-| ----- | ------- |
-| `active` | may be called |
-| `resting` | rests by its own decision: never called, never prompted |
-| `frozen` | kept, not called until the author unfreezes it |
-
-A resident's own state wins over its family's.
-
-## Where
-
-`resources/house/`: `HOUSE.md`, and one JSON file per family in `families/`:
-
-```json
-{
-  "title": "Library masters",
-  "state": "active",
-  "patterns": [],
-  "residents": [{ "model": "the-library-master___omnilibris-shakespeare-KFT_docs", "name": "Shakespeare" }]
-}
-```
-
-`patterns` claim served models by name (the EON family uses them).
-`"fromRavens": true` fills a family from `resources/ravens/`.
-
-`bos house` shows it (PROVISION): families, residents, states, duties, and
-whether ollama serves them now. `--all` lists served models no family claims.
-Only model names are read; no resident is started or prompted.
-
-## Handling
-
-[`TODO`] procedures and commands for a house.
-
-## References
-
-- [glossary](../../docs/glossary/house.md)
-- [model](../../src/models/house/class.mjs)

package/skills/bos-project/SKILL.md

@@ -1,27 +0,0 @@
----
-name: bos-project
-description: "One concrete, independent project with its own name and a focused workflow, set up to be a project repository. Use when creating, finding or handling a BOS project, or when the user mentions a project."
----
-
-# Project (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/project.md` and `src/models/project/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-One concrete, independent project with its own name and a focused workflow,
-set up to be a project repository.
-
-## Where
-
-Inside a [scope](scope.md): `forge/<scope>/<project>`.
-
-## Handling
-
-[`TODO`] procedures and commands for a project.
-
-## References
-
-- [glossary](../../docs/glossary/project.md)
-- [model](../../src/models/project/class.mjs)

package/skills/bos-sarcophag/SKILL.md

@@ -1,26 +0,0 @@
----
-name: bos-sarcophag
-description: "A single encrypted container holding exactly one bare repository. Use when creating, finding or handling a BOS sarcophag, or when the user mentions a sarcophag."
----
-
-# Sarcophag (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/sarcophag.md` and `src/models/sarcophag/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-A single encrypted container holding exactly one bare repository.
-
-## Where
-
-In the [archive](archive.md).
-
-## Handling
-
-[`TODO`] procedures and commands for a sarcophag.
-
-## References
-
-- [glossary](../../docs/glossary/sarcophag.md)
-- [model](../../src/models/sarcophag/class.mjs)

package/skills/bos-scope/SKILL.md

@@ -1,33 +0,0 @@
----
-name: bos-scope
-description: "A repository that holds a thematic family of projects, shemes and their shared throwbox, with shared workspace automation, configs, secret setups and publication setup. Use when creating, finding or handling a BOS scope, or when the user mentions a scope."
----
-
-# Scope (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/scope.md` and `src/models/scope/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-A repository that holds a thematic family of [projects](project.md),
-[shemes](sheme.md) and their shared [throwbox](throwbox.md), with shared
-workspace automation, configs, secret setups and publication setup. Its members
-are git submodules. Scopes can nest.
-
-A scope repository is **non-public**. It is carried by a self-hosted server
-(e.g. Gitea), which also stores pre-public draft repositories.
-
-## Where
-
-`forge/<scope>/`, e.g. `forge/blacksmith-organization-system/`.
-Created with `new-scope <name>`.
-
-## Handling
-
-[`TODO`] procedures and commands for a scope.
-
-## References
-
-- [glossary](../../docs/glossary/scope.md)
-- [model](../../src/models/scope/class.mjs)

package/skills/bos-sheme/SKILL.md

@@ -1,38 +0,0 @@
----
-name: bos-sheme
-description: "Source material that isn't code, kept next to the projects it belongs with. Use when creating, finding or handling a BOS sheme, or when the user mentions a sheme."
----
-
-# Sheme (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/sheme.md` and `src/models/sheme/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-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](project.md) that uses the sheme as its
-starting point.
-
-## Where
-
-Inside a [scope](scope.md).
-
-## Handling
-
-[`TODO`] procedures and commands for a sheme.
-
-## References
-
-- [glossary](../../docs/glossary/sheme.md)
-- [model](../../src/models/sheme/class.mjs)

package/skills/bos-throwbox/SKILL.md

@@ -1,27 +0,0 @@
----
-name: bos-throwbox
-description: "An automated collector of various loose files related to one project set. Use when creating, finding or handling a BOS throwbox, or when the user mentions a throwbox."
----
-
-# Throwbox (BOS)
-
-> Draft generated by `bos skills` from `docs/glossary/throwbox.md` and `src/models/throwbox/`.
-> Grow it by hand: it is never overwritten.
-
-## What it is
-
-An automated collector of various loose files related to one project set.
-Every scope has one, and the forge has a periodic one.
-
-## Where
-
-[`TODO`]
-
-## Handling
-
-[`TODO`] procedures and commands for a throwbox.
-
-## References
-
-- [glossary](../../docs/glossary/throwbox.md)
-- [model](../../src/models/throwbox/class.mjs)

package/skills/bos-workshop/SKILL.md

@@ -1,65 +0,0 @@
----
-name: bos-workshop
-description: Recognize the Blacksmith Organization System (BOS) workshop — `~/__WORKSHOP` per user or `/media/**/__WORKSHOP` per partition — as the default working area and root of code crafting, with its internal `.BOS/` and crafting areas forge, archive, devarmory and craftbook. Use whenever creating, cloning, locating or organizing projects, repositories, tools or notes, when a path contains `__WORKSHOP`, or when the user mentions BOS, the workshop, forge, archive, devarmory, craftbook, scope, sheme, throwbox, sarcophag, scrapnote, craftset or setternet.
----
-
-# BOS Workshop
-
-The Blacksmith Organization System (BOS) defines a `__WORKSHOP` directory as the
-standard working area and default root of code crafting.
-
-## Workshop roots
-
-- **Per user:** `~/__WORKSHOP`
-- **Per partition:** `/media/**/__WORKSHOP` (any mounted partition)
-
-To find the active workshop, run `bos locate` (or `node <bos-skillset>/src/cli.mjs locate`);
-without Node, `scripts/find-workshop.sh`. Resolution order:
-
-1. `--workshop=PATH` option
-2. `$BOS_WORKSHOP` environment variable
-3. Nearest ancestor of the current directory named `__WORKSHOP`
-4. The workshop BOS itself is installed in
-5. `~/__WORKSHOP`
-
-`bos status` shows what is missing (read-only); `bos bootstrap` creates it
-(never overwrites; `--dry-run` to plan).
-
-## Standard areas
-
-Every workshop always contains:
-
-| Area         | Holds |
-| ------------ | ----- |
-| `.BOS/`      | BOS itself (internal): `setup/` (keys, VPN, aliases, tokens), `data/`, `nests/` (container/VM volumes), `storylines/` (shell history, logs), `workshop.json`, `Taskfile.yaml` |
-| `devarmory/` | Tools: custom binaries, AppImages, build containers, IDE sets; listed in a manifest with checksums |
-| `forge/`     | Active work: scopes (`forge/<scope>/<repository>`), projects, shemes, throwbox |
-| `craftbook/` | Knowledge: scrapnotes (all notes not yet documents), craftsets (reusable procedure kits), recipes |
-| `archive/`   | Work at rest: sarcophags (encrypted bare repos), exhibits, mirrors |
-
-Where things go: code you are working on → `forge/<scope>/`; a tool → `devarmory/`;
-a note or draft → `craftbook/scrapnotes/`; a mirror or closed repo → `archive/`;
-graphics, CAD, photos or templates for a scope → a sheme inside that scope.
-
-- What BOS is, the full tree and element types: [references/bos-concept.md](references/bos-concept.md)
-- The BOS source code, its branches and current state: [references/bos-codebase.md](references/bos-codebase.md)
-- One page per element (workshop, forge, scope, sarcophag, …): `docs/glossary/` in this repository (authoritative)
-- The new core (this repository): `AGENTS.md` at its root
-
-## Rules
-
-1. With no explicit path, place new or cloned projects inside the active
-   workshop. Active work goes in `forge/`, grouped by scope:
-   `forge/<scope>/<repository>`.
-2. Never delete, rename, or restructure the standard areas.
-3. Multiple workshops (home + partitions) are independent; do not move or sync
-   between them unless asked.
-4. The standard areas (`.BOS/` and the four crafting areas) must always exist. If one is missing, create it
-   (`mkdir -p`) and tell the user. BOS does this itself when it boots (since
-   `dev/reforge`), but don't rely on BOS running.
-5. Every project has the standard anatomy: `README.md`, `LICENSE`, `AGENTS.md`
-   (+ `CLAUDE.md` = `@AGENTS.md`), `Taskfile.yml`, `src/`, `docs/`, `tests/`, `.github/`.
-6. Branches: `master` (canon) → `developement` (code here) → `revision` →
-   `testing` → `releasing` → `master` via pull request. Don't commit to `master`.
-7. The owner works on BOS repositories in parallel with agents. Re-check the
-   git state and file tree before acting, and treat what you find as intended.