[Kernel][G13] Prove public installation, contract compatibility and safe state/profile migration #62
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#60 [Kernel][G01-G13] Accept the installed controlled-task path end to end
Creatidy/creatidy-kernel
Reference
Creatidy/creatidy-kernel#62
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Priority: P2
Type: implementation/integration.
This active scope supersedes conflicting historical descriptive scope, priorities and dependencies. The entire previous body is preserved unchanged under Historical Scope And Evidence; its evidence, unknowns, dispositions and review counters are not reset. PR #104 is integrated at
ace7175e087cd70e207594f5631c8f4f70fabfd4; historical pending wording is not current integration status. Prepared A/B are registered as #105/#106. Publication is not feature implementation or overall alignment acceptance.Goal
Make declared installed driver/harness/core profiles usable and upgrades/refusals non-destructive.
Why
A reproducible wheel and synthetic WSL or ciphertext check is not an executed platform/migration matrix. Retain PR #102's exact evidence.
Scope
Public install/configure/diagnose/update/recover/uninstall paths, independent versioned driver/contract/harness/profile/platform cells, immutable records and owner-owned profile/ciphertext safety.
Acceptance Criteria
Dependencies
No whole-issue upstream gate; native predecessor plan: none. Receive each affected producer version when that cell is implemented; SR #185 / MI #18 accepted obligations do not become unfinished global gates, and SR #186 release/platform scope does not block CK's independent installed compatibility work. Accompany #105/#106 and interface changes rather than form a cycle with final #60 reception. Native edge publication is separate from this body amendment.
Constraints
ADR 0012 and ADR 0011 govern this work. Keep inward dependencies (
adapters -> ports -> core) and a self-contained public core. No new coding agent, tracker, catalogue, gateway or generic workflow DSL; no credential/runtime-state copying. Preserve old bytes, IDs and unknowns, all historical evidence and review counters, and #53 CLOSED/NOT IMPLEMENTED with PR #85 CLOSED/UNMERGED; its diagnostic is not accepted implementation. Require synthetic offline tests plus the installed path and fresh independent exact-subject review. Live inference/effects/releases require separate authority. Registration/publication grants no production credentials, paid/live execution, external mutation, release or deployment authority.The single active priority above follows the integrated Priority Contract: P2 is required integration, evidence/operability or installed reception, not a budget or deadline. Eligibility and evidence precede priority; no rank bypasses prerequisites, owner decisions or STOP_REVISE. Historical descriptive priorities are superseded, not deleted. Excluded invalid/wontfix/duplicate dispositions and unchanged /loop ordering remain intact; this amendment selects no feature for execution.
PR #102 merge
26c7eb15a71affc11aba760387e2dae806053d4b, reviewed head66eae9bd2b9337ce9f8c29608baac7b0dc37c34c, establishes bounded synthetic storage/schema/profile byte/mtime safety only, not a full platform/migration pass, real host rollout, recipient/key migration or real-profile transition. Its ordinal 1 REQUEST_CHANGES and ordinal 2 fresh APPROVE, plus earlier PR #97 ordinal 2/10, remain immutable historical delivery evidence. Maintain ADR 0011 trust labels: TRUSTED_DEVELOPMENT is trusted native task-level STOP/deadline behavior, not strict per-syscall expiry or hostile-worker isolation; same-principal provider-auth exposure and unproved egress cannot be represented as isolation, and no broader-profile fallback is permitted.Producer evidence correction supplied for this publication: SR develop
4a182affa4775a4a38b47860ad7622a099c56c4a, #222/PR #223, integrates default-off D-082 opt-in MI admission. It does not establish real-source positive adoption or expand this Kernel issue's external scope; Router/MI operation and policy remain their owners' responsibility.Links
ace7175e087cd70e207594f5631c8f4f70fabfd4).ace7175e08/docs/adr/0012-unified-work-coordination-and-drivers.mdace7175e08/docs/adr/0011-task-level-authority-and-trusted-development.mdace7175e08/docs/architecture/target.mdace7175e08/docs/architecture/migration.md;ace7175e08/README.md; #61ace7175e08/docs/architecture/backlog-alignment.mdace7175e08/docs/architecture/successor.md (g13-compatibility-evidence-matrix-planned); PR #97: #97 ; receipt: #62 (comment)Historical Scope And Evidence
Goal
Owner: Kernel. Deliver documented public install/lifecycle/upgrade compatibility with proved migration of existing durable state and actual user profile ciphertext, and an honest Linux/WSL support matrix; future platforms remain explicit evidence work, not implicit support. Source: shared architecture v1.0, sections 1-8, 9.2-9.4, 10-18 via #46 brief.
Why
Git history cannot recover an uncommitted encrypted user profile. Renaming fields or passing package tests does not establish safe upgrade, native harness/gateway compatibility or supported platform operation.
Current Evidence
At
eb4f4a2956, tools/check_package.py covers reproducible wheel/sdist and installed smoke; sqlite_store.py uses versioned codecs/storage checks and Linux-only mount evidence; operator_profile.py parses dotenv/optional user-supplied SOPS and has no complete migration contract. #44/PR #45 removed private normal-path dependency but does not prove all installed lifecycle/platform scenarios. Router protocols/config and MI proof version are distinct, not one global protocol.Scope
Define support/compatibility matrix for package/core records, native harness versions, Router public interfaces and MI publication refs. Prove atomic/fail-safe upgrade/rollback or refusal, preserving opaque IDs, actual ciphertext/profile metadata and user state with synthetic encrypted fixtures. Validate installed lifecycle/default paths/source acquisition/doctor/recovery/export without private repo; explicitly test Linux and WSL storage distinctions and future-platform acceptance plan. Release activation remains owner-controlled.
Acceptance Criteria
TRUSTED_DEVELOPMENTas trusted native execution with task-level deadline/STOP semantics, not strict per-syscall expiry or hostile-worker isolation. It must state that Codex provider auth inHOMEmay be readable to terminal tools, that no production/remote-write secrets are permitted in the task identity, and that native egress is unverified unless the exact sandbox test proves it. Ordinary same-principal local coding is an explicit trust choice; a task requiring secret secrecy or enforced egress control is unsupported without evidence. Never fall back to a broader profile.Reuse
Use existing locked packaging/smoke, SQLite migration/backup codecs and optional generic SOPS executable behavior. Compare exact native/producer version contracts and existing migration tools/atomic file patterns, verifying revision/license/service terms/security/negative/dependency/maintenance before adoption. No custom secrets manager or installer platform.
Dependencies And Priority
Upgrade safety must accompany any #48/#52/#55/#57/source-cache identity changes, not follow data loss. Final public acceptance consumes this matrix. Router/MI own producer migrations; consume their accepted compatibility rather than duplicate them. MI #18 is distribution counterpart; Router producer counterpart to be linked after discovery.
Constraints And Permissions
Synthetic ciphertext only, never read/copy real secrets or profiles in this repo. No rewrites of immutable identities, default cloud requirement, package publication/release/main change. Inference-free installation/migration fixtures require no model calls; supported OS/filesystem access and real key/profile migration need separately scoped owner authority. Exact unknown migration policy requires an explicit decision, not guessed destructive behavior.
Links
Non-Goals
No actual user ciphertext/secret access, new secrets manager, installer framework, publication or live task authorization.
Actual Router counterparts now fetched: BioMedical-IT/scarcity-router#185 AC1-6 separately versions schema/artifact/calibration/protocol/package, refusal, atomic migration, rollback and retained pins/audit; BioMedical-IT/scarcity-router#186 AC1-6 owns public artifacts/platform journeys and external release gates. MI Creatidy/model-intelligence#18 owns installed lawful artifacts/update interruption/migrations. These producer obligations do not prove Kernel existing ciphertext/immutable state survival or installed Linux/WSL matrix. Kernel #62 must receive compatible contracts and prove its own profile/state/install reception. Actual safe hostless-cache migration is Kernel #61; concurrency state ownership is #59. No release activation or real user profile access is granted.
The source-grounded G13 compatibility-evidence matrix is committed as
c9464c7cc7c7094b57206cef9552f1bf31cfbba7and submitted in PR #97: #97. It distinguishes exact package/store/profile/runtime evidence from cross-producer, platform, profile-migration and release unknowns without claiming global support or changing migration behavior.make checkandmake package-checkpassed. This is a preparation slice; issue #62 remains open pending exact producer contracts and installed/migration acceptance.PR #97 is integrated in merge commit
d681c29a213e302d6d4cb54668e4d684bedd7855, with first parent base98656f6e6ed5fed3d254405cf551665ebcb6c4edand reviewed headc9464c7cc7c7094b57206cef9552f1bf31cfbba7; Git confirms the reviewed head is an ancestor of currentdevelop. Exact-head workflow #2921 succeeded, independent review ordinal 2/10 approved with no findings, andmake check/make package-checkpassed on the approved tree. This integrates only the evidence-bounded matrix preparation; actual migration/compatibility acceptance is incomplete, so issue #62 remains open.Selected under the resumed
/loop(only independently executable issue this cycle; #52/#55/#56/#57/#58/#59/#60 gated as recorded). Bounded platform/storage/profile reception slice proposed in PR #102 (Refs #62; keep this issue open).Delivered: synthetic WSL topology scenarios (
9p/drvfsDrvFS refusal, WSL-native ext4 acceptance through the same native-Linux gate), explicit non-Linux platform refusal without quiet fallback, future-schema safe refusal with records preserved unchanged, and the operator-profile ciphertext safety contract (Kernel never writes profiles; failed/corrupt decryption leaves ciphertext byte-identical including mtime; fixed value-free diagnostics) using a fakesopsexecutable and synthetic ciphertext. The G13 matrix rows and migration documentation now state the exercised evidence level and the requiredTRUSTED_DEVELOPMENTlabels.Remaining open scope on this issue: real WSL/Windows/macOS host evidence, Windows install/signing, real encrypted-profile/key migration, producer version matrix cells beyond the bounded recommendation/reference contracts, uninstall tooling and release/publication (owner-gated).
Bounded platform/storage/profile reception slice integrated in PR #102 (Refs #62; issue deliberately stays open). Supported normal merge produced
26c7eb15a71affc11aba760387e2dae806053d4bwith exact parents base038da8be9c4d07e3ccc92c107862125f979a5c47and approved head66eae9bd2b9337ce9f8c29608baac7b0dc37c34c; develop advanced from the approved base, the approved head is its ancestor, and the integrated tree is byte-identical to the reviewed head. CI succeeded on the exact head (#3247, 2m24s).Review ledger for this delivery: ordinal 1 REQUEST_CHANGES with one P3 finding (the oversized decrypted-output bound was claimed but unexercised; corrupt cases did not assert mtime), remediated in
66eae9bdby exercising the 4 MiB + 1 bound and asserting mtime; ordinal 2 fresh APPROVE with empty findings on the remediated head, including independently executedmake check(1516 passed/85 skipped/106 subtests) andmake package-check, canonical MCP identity verification and complete two-commit delta inspection.Delivered: synthetic WSL topology scenarios (
9p/drvfsrefusal, WSL-native ext4 acceptance through the same native gate), explicit non-Linux platform refusal without quiet fallback, future-schema safe refusal preserving records and announced version, and the operator-profile ciphertext safety contract (failed/corrupt/oversized decryption leaves synthetic ciphertext byte-identical including mtime; loads read-only; fixed value-free diagnostics). G13 matrix rows and the migration reception section state the exercised evidence level and the AC7TRUSTED_DEVELOPMENTlabels.Remaining open scope on this issue: real WSL/Windows/macOS host evidence, Windows install/signing, real encrypted-profile/key migration (separately scoped owner authority), producer version matrix cells beyond the bounded recommendation/reference contracts, uninstall tooling and release/publication.
Implementation submitted for independent review in PR #117, head
4eff73258980fa736cbc143175e9587c5557c723, base97fedb7e3c67026c5987a2806a419cef914fdad7. Offlinemake checkpassed 2503 tests, 89 skipped and 106 subtests;make package-checkpassed including installed legacy migration, synthetic SOPS/age profile and uninstall-retention checks. This is not yet reviewed, integrated, accepted or evidence of real owner profile migration.