Repository navigation
Description
Qualified existing-root owner closure checkpoint
- API chore: align API manager-compatible owner archives (#644) #653 .12 at31fc9d2099519f62b8ffe12ae9ee483fe071ab92 selects accepted SDK42/Deployment126/Identity9/Admin12/UI23 exact public archives.
- Checks/build,16 acceptance/9 regression/4 integration/5 unit and genuine script-disabled archive consumer pass locally. The previously failing genuine installed Keycloak/database/API/edge/browser program now passes its unchanged limits.
- Both exact-head hosted jobs123628313747/123628280634 pass every tier; actual installed programs take151.776/159.484seconds. Final review and proposal: restore existing trusted committer policy to cordis #620 blob b1a687db754ee2fac141919e6c63052d12bf2812 are verified.
- .12 archive has23 exact files/modes, producer31fc9d2099519f62b8ffe12ae9ee483fe071ab92, SHA-25601466d7fc7182769665f0097a9984af1dfb9e89798cc0ebfeea6cbf07b3fa006. Earlier failed .10/.11 observations/archives remain immutable.
- API feat: reconcile seed owner steps with verified final read-back (#644) #645 internal reconciliation and the public native seed coordinator/journal/resource-provider assembly remain separate. This compatibility slice does not fulfill those broader criteria below.
Keep every issue open; real Work/model execution remains Task10. No production/legacy action or Team data migration.
Goal
Implement API-owned headless SeedCoordinator and native Cordis composition for the approved seed-driven Task 3D capacity provider. CLI consumes the public package without starting an API server. SDK owns portable data contracts; Deployment owns artifact custody/private filesystem operations; resource providers retain owner records.
Acceptance criteria
- Commit public contracts and owner boundary documentation before outside-in tests and implementation.
- Preserve legacy same-repository seed coordination semantics through the public API-owned coordinator; do not import legacy sources or migrate Team data.
- Resolve exact accepted artifacts and isolated validator scope; block missing/ambiguous/incompatible providers and cyclic resources before live effects.
- Plan binds seed/schema/executable/provider identities, project/profile, trusted authority and owner preconditions; existing non-activating platform plan stays unchanged.
- Apply rechecks live authority and preconditions, publishes a single-writer private journal through Deployment custody, resumes verified idempotent receipts and reports partial/pending/recovery explicitly without destructive automatic rollback.
- Default headless construction uses native Cordis roots and typed selectable providers; no parallel instance cache or container.
- Built public archive consumer, owner applicable tiers/checks/build, and exact assembled acceptance qualify the advertised behavior.
- Preserve Keycloak approval and the exact proposal: restore existing trusted committer policy to cordis #620 approved-committers policy blob; keep every issue including platform#678 open.
Dependencies: SDK seed contracts treeseed-ai/sdk#487 and critical readability policy #643. Architecture authority: treeseed-ai/platform#773, docs/seed-architecture.md and docs/agent-architecture.md on feature/773-agent-composition. This issue does not authorize merges, production publication, legacy service changes, new Team authority or real Work/model execution (Task 10).
Manager-compatible owner closure checkpoint
Draft #653 consumes exact accepted SDK .42 / Deployment .120 / Identity .9 / Admin .12 / UI .23 archives. Local checks/build, exact compatibility, 9 regression / 4 integration / 5 unit and source-free public Node/types program pass. API .10 producer 60dd118, SHA-256 bc4df686c80d4b8f42848bf747113afd8b0efd7db41372841d01c057be71324b; 23 exact files/modes. Approved-committer blob remains b1a687db754ee2fac141919e6c63052d12bf2812.
Full local acceptance is 15 pass / 1 fail at the genuine installed worker exchange; writer.lock does not drain within the existing deadline. Emitted source corrects the earlier executable-mismatch interpretation. Temporary fixed-stage diagnostics were restored byte-for-byte. The same failure with the old closure remains held in #645; no dependency upgrade, public metadata proof or lower suite waives it. Complete runtime/hosted gates and headless native seed coordinator remain outstanding. All issues stay open; Work/models remain Task 10.
Activity
docs: specify seed owner-step recovery and receipt admission (#644)
docs: pin seed reconciliation SDK contract candidate (#644)
test: specify built seed reconciliation and lost-reply resume (#644)
test: define seed journal and owner boundary failure cases (#644)
test: pin canonical seed identities and dependency order (#644)
feat: reconcile seed owner steps with durable intent and verified res…
chore: integrate exact capacity owner closure for verification (#644)
docs: pin the fenced-handoff Deployment candidate (#644)
test: require the exact fenced-handoff host archive (#644)
fix: consume the fenced-handoff Deployment archive (#644)
fix: integrate fenced-handoff owner for seed verification (#644)
refactor: format seed reconciliation capability layers (#644)
refactor: retain formatted seed capability boundaries (#644)
chore: align API with exact capacity-compatible owner archives (#644)
4 remaining items
test: reject late invalidation in built seed reconciliation (#644)
test: pin final seed owner freshness without repeated effects (#644)
test: fence final seed authority and lease disposal (#644)
fix: verify final seed owner receipts before completion (#644)
adrianwebb commentedon Oct 29, 2026
Starting a separate exact owner-closure slice on feature/644-manager-owner-closure from freshly verified origin/cordis 92331d3. Preserve #645's internal reconciliation/freshness commits and immutable .9 artifact. The new closure selects SDK .42, accepted Identity .9/UI .23 and the current reviewed Admin .12/Deployment .120 candidates only after their acceptance. #620 committer policy stays exact. Documentation and outside-in compatibility checks precede adoption. The old installed-host failure remains recorded and unproven; this necessary owner upgrade requires fresh genuine installed verification and does not waive it or claim root cause.
docs: consume accepted cooperative staging owner closure (#644)
docs: identify the resumed API archive selection precisely (#644)
test: require accepted cooperative owner artifact (#644)
chore: adopt accepted cooperative staging archive (#644)
adrianwebb commentedon Oct 29, 2026
Current owner-closure candidate API #653 is .11 at 1bc44e7, consuming accepted Deployment .122 (cooperative archive publication). Both exact-head hosted verify jobs 123584665563 and 123584630253 passed. Local full acceptance remains 15 pass / 1 failure at the unchanged installation activation deadline; temporary restored diagnostics measured 146.631 seconds in staging before prepare/activate. No exchange/drain failure was reproduced on this .11 run, but that does not qualify the failing local boundary. Candidate stays held pending throughput diagnosis; no timeout/assertion change or blind rerun. Genuine script-disabled .11 archive consumer passed; archive SHA-256 b67da746f6b912094f86dc3e1a4dab367ca95a872442e6642516f134ace0c7b8 at producer 1bc44e7. Earlier .10 archive remains valid at producer 60dd118; its later README commit changed packaged documentation, so final-head byte equality is not claimed. All issues remain open; Work/model execution remains Task 10.
docs: select bounded durable Deployment candidate for API (#644)
docs: clarify retained API timing evidence (#644)
test: require exact bounded publication owner selection (#644)
chore: adopt exact bounded publication owner archive (#644)
chore: align API manager-compatible owner archives (#644)