mosaicstack/stack
16
0
Fork 1
Code Issues 330 Pull Requests 11 Actions Packages Projects Releases 15 Wiki Activity

W-F1 follow-on/P3 prerequisite: Pi runtime base/overlay composition #1185

New Issue
Open
opened 2026-08-13 00:44:40 +00:00 by Ghost · 0 comments
Ghost commented 2026-08-13 00:44:40 +00:00
Copy Link
Copy Source

Origin

Fred's W-F1 freeze adjudication (jarvis-brain@f5123ce79, WF1-FREEZE-ADJUDICATIONS.md point 6) freezes W-F1 core/D1 as Claude-only. The reviewed Claude base-without-hooks plus promotion-overlay fixture cannot be generalized to Pi without a separate reviewed packet.

Objective

Define and implement the Pi-specific file-level system base/user base/agent overlay split consumed by the sealed W-F1 launch executor and native P3. Preserve the same authority and containment invariants without copying Claude hook semantics into Pi.

Required design packet before code

  • Inventory exact Pi 0.84.1 configuration/settings/extension/skills files and which are framework base versus user-owned state.
  • Define canonical installed base under ~/.config/mosaic/framework/runtime/pi/ and user/seat overlays under user-owned ~/.mosaic; framework update may not own user state.
  • Define arrays, null tombstones and Pi-specific merge rules only where supported; no unreviewed field passthrough.
  • Preserve PI_CODING_AGENT_DIR, auth/session roots, extension activation, model settings, and --no-builtin-tools as separate typed launch concerns.
  • No raw credentials, OAuth identity, session content, auth target, broker state, or host paths in descriptor/dry-run/ledger output.
  • Reconcile exact consumer boundary with merged W-F1 sealed executor, @mosaicstack/harness-sandbox, Task 8 artifact manifest, and native Task 9.
  • Exact immutable path fence, behavior-first RED matrix, anti-masking controls, no-clobber/real-file/symlink containment, independent code/security review.

Sequencing

No implementation until core W-F1's final contract is reviewed and this Pi packet independently passes design/fence review. This is a hard prerequisite before P3_NATIVE_IMPLEMENTATION_BASE_SHA can be called ready for Pi launch consumption; it does not authorize provider calls, auth reads, Gateway start, deployment, or stage repin.

## Origin Fred's W-F1 freeze adjudication (`jarvis-brain@f5123ce79`, `WF1-FREEZE-ADJUDICATIONS.md` point 6) freezes W-F1 core/D1 as **Claude-only**. The reviewed Claude base-without-hooks plus promotion-overlay fixture cannot be generalized to Pi without a separate reviewed packet. ## Objective Define and implement the Pi-specific file-level system base/user base/agent overlay split consumed by the sealed W-F1 launch executor and native P3. Preserve the same authority and containment invariants without copying Claude hook semantics into Pi. ## Required design packet before code - Inventory exact Pi 0.84.1 configuration/settings/extension/skills files and which are framework base versus user-owned state. - Define canonical installed base under `~/.config/mosaic/framework/runtime/pi/` and user/seat overlays under user-owned `~/.mosaic`; framework update may not own user state. - Define arrays, null tombstones and Pi-specific merge rules only where supported; no unreviewed field passthrough. - Preserve `PI_CODING_AGENT_DIR`, auth/session roots, extension activation, model settings, and `--no-builtin-tools` as separate typed launch concerns. - No raw credentials, OAuth identity, session content, auth target, broker state, or host paths in descriptor/dry-run/ledger output. - Reconcile exact consumer boundary with merged W-F1 sealed executor, `@mosaicstack/harness-sandbox`, Task 8 artifact manifest, and native Task 9. - Exact immutable path fence, behavior-first RED matrix, anti-masking controls, no-clobber/real-file/symlink containment, independent code/security review. ## Sequencing No implementation until core W-F1's final contract is reviewed and this Pi packet independently passes design/fence review. This is a hard prerequisite before `P3_NATIVE_IMPLEMENTATION_BASE_SHA` can be called ready for Pi launch consumption; it does not authorize provider calls, auth reads, Gateway start, deployment, or stage repin.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
code-be-01 (Mosaic fleet seat code-be-01) code-be-02 (Mosaic fleet seat code-be-02) code-infra-01 (Mosaic fleet seat code-infra-01) fargo fred gate-merge-01 (Mosaic fleet seat gate-merge-01) happy jason.woltje (Jason Woltje) merge-gate ops-01 (Mosaic fleet seat ops-01) ops-02 (Mosaic fleet seat ops-02) ops-03 (Mosaic fleet seat ops-03) ops-ci-01 (Mosaic fleet seat ops-ci-01) ops-deploy-01 (Mosaic fleet seat ops-deploy-01) pepper rev-code-01 rev-code-02 rev-security-01 rev-security-02 rev-security-03 (Mosaic fleet seat rev-security-03) sanity scooby (Scooby) scrappy shaggy tiny velma veronica (Mosaic fleet seat veronica) vision woodpecker
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1185