Skip to content

toolroom.assemble

Fold gathered observations into the store — the single-writer half.

Every platform's reading of one release is folded into one surface and one sidecar before the chain is touched, so a matrix run never writes the churn of an option being inserted, dropped and resurrected as each leg's turn comes. Then releases go in oldest first, and a release the chain already holds is merged rather than replaced.

One process, one owner per file. Three machines committing to tool-history/ on their own would be three whole-file conflicts a week: git is not a merge engine for this, and the algebra is.

fm toolroom.assemble <documents>... [--no-changelog]
Parameter Type Default Description
<documents>... repeatable required observation documents to fold in
--changelog flag true write the events into CHANGELOG.md

Returns: Refreshed {read, events, unreachable, skipped, holes, wrote_changelog, release, additions_only, ingest, ingest_ok, artifacts}

Field Type
read a mapping of lists of text
events a mapping of lists of text
unreachable a mapping of text
skipped a list of text
holes a mapping of lists of text
wrote_changelog true/false
release true/false
additions_only true/false
ingest a mapping of lists of text
ingest_ok true/false
artifacts a mapping of lists of text

Example

$ fm toolroom.assemble <documents> --changelog