Repository navigation
glossary omnis
.omnis.toml: a halo of weak hashes around a model's files. Each hash alone is broken or collides; together they pin a file down, as triangulation does. A draft (phase 2): it can be redefined later.
An element keeps its own BOS files in .bos/ (decision Q15: .bos/ stays,
no .craft/). Every model has its own .bos/.omnis.toml (decision Q16),
which describes that model only: a submodel has its own file and its own
area. It lists the model's files without naming them or showing their
content:
[moriatur]
UNIXUSAT = 1793968000000
[allocators]
KEYNAME = ["crc32", "a12y", "adler32"]
VALUEDATA = ["sha1", "md5", "crc32"]
[hallows]
<key> = "<value>"-
key (where the file is): base32 of the
KEYNAMEallocators run onpath, relative to the element, with/. By defaultcrc32(path) + a12y(name) + adler32(path). -
value (what the file holds): base32 of the
VALUEDATAdigests of its raw bytes. By defaultsha1 + md5 + crc32. -
allocators: three for the key, three for the value, changeable (Q16).
The file records the ones it was made with, so it is read back with them.
Keyname allocators:
crc32,adler32(of the path),a12y(of the name). Valuedata allocators:sha1,md5,crc32. -
a12y: the owner's own algorithm, not a numeronym like a11y. It takes
the first letter, the length and the last letter of any string:
a12y("authenticity") == "a12y",a12y("ab") == "a2b". Simple yet useful, e.g. for 4-byte words of compression dictionaries. - base32 is RFC 4648 without the
=padding, because a bare TOML key cannot hold=.
Only these files are counted:
- regular files: no directories, links, pipes or devices;
- files that no
.gitignoreof the element leaves out. An ignored directory is never entered unless something in it is re-included:node_modulesor.venvare left to their lock files (package-lock.json,uv.lock), which are counted and stand for them as a finality checksum; - files outside other models: the walk stops at a directory with a
.bos/of its own; - files whose name begins and ends with a letter. So
.omnis.tomlnever counts itself.
The owner calls the idea a triangulum. A weak hash on its own collides: many inputs give the same output. Several weak hashes taken together act like coordinates, and each one narrows down which file it is. And the table only holds hashes, so it can be shared or mirrored without showing what it guards.
Comparing it with the files now says at once what changed while a project was closed, and shows changes nobody meant to make (an injection). More uses will come (Q16).
-
src/core/omnis.ts:a12y,crc32,adler32,base32,counted,ownFiles,omnis(host, root, files, allocators),omnisToml,readOmnis,drift. A file's digests go through the Host (host.digest(path, algorithm)). What no.gitignoreleaves out: in a git working treeLocalGit.files(); outside one (an area of the workshop)src/core/ignore.ts(treeFiles), which reads the.gitignorefiles as git does. - The procedure
sealing(bos.omnis({ seal })):bos project omnisshows what drifted since the halo was sealed, andbos project sealwrites it (only when something changed;--dry-runonly says so). -
bos workshop status: the findingomnis-driftfor every project whose sealed halo no longer matches its files.
- [
TODO] Outside a git repository there is no.gitignorereading yet: the halo is made only for git working trees. - [
TODO] What else seals a model:bos close, the routine?
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