Robert Allan JamesandClaude Sonnet 5
b031b802e3
FABRIC.md -> FABRIC-0.md FABRIC-2.md -> FABRIC-1.md FABRIC-3.md -> FABRIC-2.md (the current/living document) FABRIC-4.md unchanged (new #3 to follow separately) Every cross-reference repo-wide updated to match, including doc-comment citations inside kernel source (.c/.h) files -- done via an ordered placeholder substitution (FABRIC-3.md->placeholder2, FABRIC-2.md-> placeholder1, FABRIC.md->placeholder0, then placeholders resolved to final names) in a single pass per file to avoid double-shifting already-renamed references. One line in capsules/font.4th grew past the 64-char block-format limit as a side effect of the longer filename; shortened it and reverified with mkcapsule --lint (34/34 pass) before rebuilding. Verified 3-arch boot to ok> (amd64/aarch64/riscv64, each in the foreground) after the fix; logs and DoE CSVs from this session's verification runs included per this repo's own audit-artifact convention. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019YcT3H2PQeyujrzjqS3Var
src/starkernel/capsule/
Kernel-side capsule system: locating, validating, and executing the
immutable, content-addressed .4th initialization payloads in
capsules/ (embedded into the kernel image via tools/mkcapsule.c).
capsule_find.c— locates a capsule by name in the generated capsule directory.capsule_validate.c— validates a capsule's content hash before use.capsule_birth.c— the birth protocol: allocate VM ID → execute IDENTITY (capsule code) → execute PERSONALITY (block 1 from ramdrive) → log parity record.capsule_run.c— capsule execution against a VM instance.capsule_loader.c— loads capsule block content into kernel ramdrive block RAM, writing eachBlock Nheader to its literal numbered block address (not reordered).capsule_vm_hooks.c— VM integration hooks for capsule execution.capsule_vm_physics.c— physics-runtime bindings for capsule-birthed VMs.mama_forth_words.c— Mama VM-specific FORTH word bindings.