Repository navigation
Decide the minimum KEL-132 and KEL-135 artifacts required by the product spine #325
Description
Activity
Resolution
Full completion of KEL-132 and KEL-135 is not required before the minimum functional product spine can proceed.
KEL-135
For the current macOS product spine, the required profile behavior is already available from the landed macOS T3 implementation:
- host-derived signed app/profile identity;
- current-Mac persistent profile selection and same-origin isolation;
- explicit fresh ephemeral development mode;
- lifecycle/profile ownership and restart behavior;
- current-Mac evidence is landed.
The remaining older-macOS row is separately deferred and does not affect the current-Mac product spine.
Therefore the product spine should consume the landed current-Mac KEL-135/T3 artifact rather than wait for whole-parent KEL-135 completion.
KEL-132
The current product spine does not exercise camera/microphone or depend on the broader GPU/media acceptance matrix.
KEL-132 remains important security/platform hardening, but its full cross-platform media/GPU completion is not required to prove:
- renderer bridge functionality;
- authenticated app-link behavior;
- guarded filesystem allow/deny;
- same-window Bun recovery;
- prebuilt developer execution.
For this product slice, the only requirement is that the existing webview construction used by the renderer path remains safe enough to launch the supported local application and does not regress the bridge path. Media/GPU-specific acceptance continues independently in KEL-132.
Routing decision
Remove whole-issue KEL-132 and KEL-135 blocking edges from the minimum product-spine route.
- KEL-135 current-Mac task-level artifact is treated as already satisfied for this slice.
- KEL-132 continues in parallel and remains required for its own broader security/platform acceptance, not for the first renderer/native functionality proof.
The functionality-critical path can now concentrate on KEL-139 → KEL-142 / KEL-141 → KEL-140 → KEL-143 → KEL-144, with KEL-102/T3, KEL-103 and KEL-118 supplying their exact predecessor artifacts.
Parent map: https://github.com/gyldlab/keld/issues/311
Question
Does the minimum KELD product spine require full completion of KEL-132 and KEL-135, or only specific task-level safety artifacts from those owners before KEL-139 and its implementation children can proceed?