Skip to content

[LEARN-01.2/.4–.5 / Akka orchestration] Qualify installed LEARN observation, persistent receiver and causal acceptance #4647

Open
1 of 1 issue completed

Description

@EHotwagner

Owner: Programme /root is accountable. Existing source executor /root/review_v2_adoption implements the bounded command-recipe producer delivery #4681. .github retains policy/telemetry/analysis, Coordination retains orchestration and Home/SystemAdmin retains the installed capability boundary. No experiment is selected.

Done when: Complete LEARN-01.2/.4–.5 and the selected Akka integration: genuine installed actor/usage capture and causal receiver acceptance, persistent storage/recovery, required refusal/conflict cases and selected adoption. Statistical or economic conclusions require the plan’s independent experiment evidence.

Current deliverable: Command-recipe producer source #4681 is accepted through PR #4684, protected merge18179c5f2debd2afa27ecb779c06afd16f05dbfb at2026-10-19T04:50:32Z. The actual PersistentV3.ImageClosure CLI now recomputes closed selection/trusted/recipe joins and emits canonical CommandProgram bytes without execution or authentic admission. Independent final-source review, actual CLI controls, complete repaired Host/source qualification and normal exact-head delivery/readback passed. The production selection remains acquisition-required. Existing source #4513, Coordination #962/#963 and receiver #4353/#4361 retain their accepted bounded scopes. No experiment, installed/native adoption or whole-outcome acceptance follows.

Decomposition under #4701: No new child is meaningful until its exact named supplier/candidate/genuine-work condition is supplied; Root retains accountable intake and the reopening event. Accepted evidence above retains only its recorded scope. Remaining full promise: Two cold OCI builds/comparison, served Manager→Host inactive qualification and protected readback; installed actor attribution, reader inventory, causal replay/conflict/refusal, capture and persistent restart/recovery; selected adoption and reproducible bounded policy decision remain. Community/adaptive scope remains conditional, not silently added to stable-policy core.

Next action: Root resolves the authentic provisioner through the existing Home/SystemAdmin boundary: independently acquired recipe/custody, trusted runtime profile, complete reader/native/search inventory, mappedUID/cgroup enforcement and original finite capability. Only then materialize one supplier-owned Delivery and a distinct LEARN-owned causal receiver Delivery. Reuse completed#4681 CommandProgram producer exactly. No new child is meaningful until its exact named supplier/candidate/genuine-work condition is supplied; Root retains accountable intake and the reopening event.

Blocked on: The command-recipe source producer is delivered independently of Home access; it does not supply genuine production activation. Genuine activation still needs the selected installed runtime, authentic root/controller capability supply, enforcing cgroup/UID profile, complete reader/runtime inventory and required cold-image/receiver qualification. Current production selection remains acquisition-required with null reader-profile/inventory hashes; this producer must not fabricate them or turn digest-shaped fields into admission. Root owns .github integration and Home/SystemAdmin supplies the installed profile/custody route; exact native supplier acceptance remains open. UTEL receipts do not establish these stronger LEARN guarantees, and missing LEARN activation does not block ordinary coordinator correctness.

Current determining clarification under #4701: The persistent receiver plan expressly leaves authentic provisioner supplying owner unresolved; production selection remains acquisition-required/null inventory. Root-owned generated recipes, digest-shaped fields, a controller factory, sourcePASS or UTEL receipt cannot supply authentic admission. All other existing conditions and original uncertain effects remain retained; this clarification grants no new authority or reservation release.

Acceptance evidence: owning plan; persistent receiver plan; #962/#963 and #4353/#4361. Reuse accepted O0–O3/Akka core without extending its scope. Unified v3 outcome index.

Decomposition design and scoped remaining acceptance: #4701; docs/coordination/2026-10-19-board-clearing-lifecycle-design.md (owning source plan; publication remains separate). No child is materialized for the attributed supplier/candidate gap until its concrete reopening condition is met.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions