Development record
itd-26 calls the licence gate a launch gate; launch says the restrictive-licence gate is not the release artefact's gate, and that its consumer is the lifeboat
itd-26 calls the licence gate a launch gate; launch says the restrictive-licence gate is not the release artefact's gate, and that its consumer is the lifeboat
A terminology drift (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-26-loot-oss-vendor.md:70— "launch-gate-licence-gate machinery itd-26 needs is the same machinery memory ingest needs" - End B:
.abcd/development/brief/04-surfaces/04-launch.md:477— "The restrictive-licence gate over kept originals is likewise not this artefact's gate. Its real consumer is the lifeboat"
itd-26 builds on a substrate it names as including the 'launch-gate-licence-gate'. The launch chapter says the restrictive-licence gate is not this artefact's gate: its real consumer is the lifeboat, it is future and inert at launch, and it insists on 'two mechanisms, never one name'. Calling it a launch gate attaches the gate to the surface that says it is not there.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 343.
Frontmatter
| id | iss-2610262032585048 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262032585048-itd-26-calls-the-licence-gate-a-launch.md
open on GitHub ↗ · commit history ↗
References1
- itd-26Raid the Open Ocean, Bring the Cargo Home with Papersrelated
mentions1
- iss-2610262034120625itd-26 builds loot's refusing licence check on itd-36's shared substrate, launch licence gate included; the library surface says that gate is not built and ingest never refuses on a licence