Expand description
§Loom bootstrap state
K1BootstrapState registers the version-2 k1-loom-bootstrap KTO stream and reconstructs one process-wide first-run state from canonical history. begin records the entered username, full name, and derived public key before the bootstrap effects. complete requires that exact Begin record and stores the resulting user, loom-devs group, saved Profile, public Kmap root, and imported package coordinates.
The one-time bootstrap trusts its same-machine Rust and Web inputs. State contains no archive digest, source digest, SHA-256, or other code hash. ImportedPackage stores only the logical package name and stable semantic version.
The first accepted Begin and first matching Complete win. Repeating an exact record is idempotent and returns its canonical transaction ID; a different identity or completion is rejected. Malformed canonical payloads and reorganization make the instance unavailable. Reopening replays from genesis. Version-1 state is intentionally unsupported because this migration runs against disposable blank state. There is no separate state file, migration, retry, rollback, repair, background work, credential storage, or authority bypass.