Folio Assistant Core

Complete initialization

https://litlfred.github.io/folio-assistant/bootstrap/process/Process_CompleteInitialization · bootstrap:Process · JSON-LD · part of bootstrap.jsonld

labelComplete initialization
summaryA SUB-PROCESS of initialize-harness, called after a harness is installed and also when the location turns out to be a layer instantiating the chosen harness already.
descriptionA SUB-PROCESS of initialize-harness, called after a harness is installed and also when the location turns out to be a layer instantiating the chosen harness already. It is how an agent — the one that installed the harness, or one dispatched for exactly this with nothing but this diagram and the declaration — makes sure EVERY initialization step is done. THE STEPS ARE NOT LISTED HERE. They are named by the declarations: the layer's `<name>.json` and every declaration it `needs`, read from the sibling checkouts. A declared directory is a step (it exists); a declared asset is a step (the file is there); a dependency's `<name>/docs/bootstrap/initialization.md` is a step (it was followed); the root README and the sections it opts into are steps; the `repository` a declaration names makes the site steps — a Pages workflow, a `gh-pages` branch, Pages switched on, the address answering. A harness above bootstrap names more in the same way — a work-plan store it declares as a directory is a directory step — and bootstrap does not need to know which. The skill `initialization-steps` has the table. IDEMPOTENT BY CONSTRUCTION. Every step is CHECKED before anything is done, and a done step is left alone, so running this twice changes nothing the second time. Nothing is replaced: a step that would overwrite what somebody wrote is a step for a person, not for the agent. FOUR STATES, NOT TWO. done; not done; could not determine — the check could not run (no forge CLI, no network), which is NEVER reported as done; and stated — the declarations name it but nothing can observe it (reading and following instructions), exactly as a stated precondition is never reported as satisfied. THE PRIMARY STEP IS DRAWN, not left in the list: A_CheckDocuments, the harness's JSON Schemas and JSON-LD at the IRIs they name, checked first after the declarations are read. Everything after it — directories, README, the site — is either how those documents are reached or how a person reads about them. WHERE TOOLS ARE AVAILABLE, a toolset may perform the same checks (`initialization-steps`); otherwise the agent reads files. The diagram is the same either way. NO work-plan element on any activity, and isExecutable is false, for the reasons initialize-harness gives.
requireshttps://litlfred.github.io/folio-assistant/bootstrap/process/Process_HumanAgentDiscussion
https://litlfred.github.io/folio-assistant/bootstrap/process/Process_LogMessage
sourcehttps://litlfred.github.io/folio-assistant/bootstrap/processes/complete-initialization.bpmn
depictionhttps://litlfred.github.io/folio-assistant/bootstrap/processes/complete-initialization.svg
isPartOfhttps://litlfred.github.io/folio-assistant/bootstrap/directory/processes

Sequence flows