ABI: the rail yard -- the SDK and CI's model for staging trains, recorded as given (Captain Bob)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
@@ -130,6 +130,22 @@ is verified (ADR §5); compatibility is checked against the old artifact's recor
|
||||
thought. That 'assembled' code can be the 'engine' for a train of named blobs as metaphorically rolling
|
||||
stock." Ruled "One train per capsule" (§1).
|
||||
|
||||
**The rail yard: the SDK and CI's model** (Captain Bob, 2026-11-19, recorded as given; nothing built):
|
||||
> "When we build the SDK, we can naturally think of a railroad yard for staging outgoing artifact capsule
|
||||
> 'trains' from first order preexisting 'cars' prior to writing new ones.. That would be the model and on
|
||||
> the CI side we can use messaging as semaphores in our staging yard with inbound and outbound trains and
|
||||
> the artifacts are the persistent part. Signed, sealed and versioned."
|
||||
|
||||
Read here as:
|
||||
- **The yard stages trains.** An outgoing train is made up first from cars that already exist, which are
|
||||
first-order and already built. New cars are written only for what is missing.
|
||||
- **In CI, messages are the semaphores.** They signal inbound and outbound trains through the yard: what
|
||||
may move, and when.
|
||||
- **What persists is the artifacts:** signed, sealed and versioned. The yard's moves are transient.
|
||||
|
||||
It ties in `(-`, the build marker that asks CI to clear a block for the next image (`plans/2026-11-18-
|
||||
capsule-blocks.md` §5), and Artemis keeping what is kept (ruling 3).
|
||||
|
||||
## 9. Open, for ruling one at a time
|
||||
|
||||
1. ~~Where artifacts come from~~ **Ruled 2026-11-19: "A host tool".** A C tool beside `mkcapsule` compiles
|
||||
|
||||
Reference in New Issue
Block a user