New ICM Concept: the LOOP CLOSE

Hey everyone,

I just came across something and I'm curious how you may handle the samething?

It's basically long running work tasks within a stage, that we want updates and logs to be created from. Currently I only binded updates to SHIP stage, this is why it came up during the BUILD stage. Below was our simple solution. Curious on your thoughts if this works cleanly, anything I'm missing or if it's completely unnecessary for some reason.

###

Promote Identity from exit artifact to gate (the core, KISS)

Introduce exactly one new ICM concept: the LOOP CLOSE — the boundary of a repeating unit of work inside a stage (a region sweep, a ticket, a phase iteration).

Rule: a loop iteration is not done until L1 Identity and the engineering log reflect it — not just L4/L5.

Lands as edits to files that already exist:

.forge/icm/STAGE-MATRIX.md — a short "Loop close (iteration gate)" block + a row in BUILD

2 comments

New ICM Concept: the LOOP CLOSE