Creatidy/creatidy-kernel
5
0
Fork 0
Code Issues 9 Pull requests 2 Projects Releases Packages Wiki Activity Actions

[Kernel][G02 G05] Prepare and authorize versioned specifications from ordinary issues #49

New issue
Closed
opened 2026-10-04 22:22:46 +00:00 by kilo · 3 comments
kilo commented 2026-10-04 22:22:46 +00:00
Member
Copy link

Goal

Owner: Kernel. Provide controlled ordinary-task intake that prepares a versioned TaskSpec with explicit intended outcome, scope, quality/context/interface requirements, verification recipes and bounded authority, and requires trusted approval before admission. Source: shared architecture v1.0, sections 1-8, 9.2-9.4, 10-18 via #46 owner brief.

Why

Users cannot safely turn arbitrary issue prose into executable authority. Current frozen #143/#166 tasks are historical fixtures, not the product task model; issue freshness and current implementation/PR/test evidence must be checked before spending resources.

Current Evidence

At eb4f4a2956, adapters/task_execution.py TaskSpec and cli.py TASKS register two controller-owned contracts; task_program_spec binds immutable intent; ports/application.py uses a fixed reference ResourceRequest. #31/#42 freeze example targets; #32/#37 explicitly exclude arbitrary issue ingestion. #34 closed INFRASTRUCTURE_BLOCKED and #39 closed TASK_STALE, not successful live execution. Immutable core ProgramSpec revision/authority is reusable, not proof of general intake.

Scope

Prepare (not automatically execute) normal issues against canonical host-qualified repository/source and current problem evidence. Identify existing implementation, active/merged PRs, relevant source changes and known test baseline. Propose explicit requirements without inventing numerical capability/cost minima from prose. Version amendments, approved recipes and grants; bind admission to current approved revision and exact source/baseline. Use established Forge read contracts and trusted approval channels, not a second tracker or planner framework.

Acceptance Criteria

  1. An ordinary issue can become a reviewable specification with source references, explicit unknowns, result/quality/interface/context needs, scope, recipes and authority; unapproved drafts cannot dispatch.
  2. Issue/AGENTS/model-output injection, edited issue after approval, replayed or expired decision, widened path/network/effect request and changed source/test baseline fail closed or require a fresh scoped amendment.
  3. Already implemented issue, active equivalent PR, incomplete/permission-limited search, stale source and unknown baseline yield distinct evidence-backed dispositions; open issue alone never proves work remains.
  4. Approved spec amendments preserve immutable history and invalidate affected stale acceptance; no worker/Console can grant itself authority.
  5. Producer-consumer tests prove approved requirements are delivered intact to the routing translator and unsupported requirements are explicit, never silently downgraded to reference/L0.
  6. Existing frozen durable TaskSpec identities remain readable/recoverable; migration and operator docs distinguish these historical fixtures from ordinary intake. No new endpoint/payload/flag asserted before contract review.

Reuse

Start with ProgramSpec/TaskSpec revision/digest and Forge exact-object reads, existing context manifests and Symphony SPEC tracker/workspace/status patterns. Compare authority/freshness/recovery guarantees, exact files/revisions/license/attribution, dependencies and maintenance before adoption; no automatic Symphony scheduler adoption or new DSL.

Constraints

Issue text is data, not approval. Preserve scope/authority, exact-base freezing, immutable Attempt and acceptance subjects, unknown remote effects, no private repo requirement and no automatic merge/deploy. No guessed capability/budget thresholds, provider discovery or local ranking.

Dependencies And Priority

First admission prerequisite: meaningful routing requirements and product review consume this approved spec. Full gateway/isolation acceptance is required before untrusted live execution, but preparation itself can be independently received. Router owns requirement vocabulary and admission; Kernel owns approved task meaning and authority.

Permissions And Diagnostics

Safe read-only issue/source/baseline preparation may need forge access; executing untrusted baseline tests requires the isolation policy. Any model-assisted preparation or live task needs separately scoped inference; effect permissions and numerical budget/quality choices remain owner-approved. Explain stale/unknown/refused cases without leaking content/secrets.

Links

  • Parent: #46
  • Immutable intent: #4
  • Historical frozen support: #42

Non-Goals

No arbitrary issue execution, new workflow framework, Router profile creation, implementation of target issues or authority from AGENTS.md.

## Goal Owner: Kernel. Provide controlled ordinary-task intake that prepares a versioned TaskSpec with explicit intended outcome, scope, quality/context/interface requirements, verification recipes and bounded authority, and requires trusted approval before admission. Source: shared architecture v1.0, sections 1-8, 9.2-9.4, 10-18 via #46 owner brief. ## Why Users cannot safely turn arbitrary issue prose into executable authority. Current frozen #143/#166 tasks are historical fixtures, not the product task model; issue freshness and current implementation/PR/test evidence must be checked before spending resources. ## Current Evidence At eb4f4a2956712bfaf39a3271e1523e7f77a91e26, adapters/task_execution.py TaskSpec and cli.py TASKS register two controller-owned contracts; task_program_spec binds immutable intent; ports/application.py uses a fixed reference ResourceRequest. #31/#42 freeze example targets; #32/#37 explicitly exclude arbitrary issue ingestion. #34 closed INFRASTRUCTURE_BLOCKED and #39 closed TASK_STALE, not successful live execution. Immutable core ProgramSpec revision/authority is reusable, not proof of general intake. ## Scope Prepare (not automatically execute) normal issues against canonical host-qualified repository/source and current problem evidence. Identify existing implementation, active/merged PRs, relevant source changes and known test baseline. Propose explicit requirements without inventing numerical capability/cost minima from prose. Version amendments, approved recipes and grants; bind admission to current approved revision and exact source/baseline. Use established Forge read contracts and trusted approval channels, not a second tracker or planner framework. ## Acceptance Criteria 1. An ordinary issue can become a reviewable specification with source references, explicit unknowns, result/quality/interface/context needs, scope, recipes and authority; unapproved drafts cannot dispatch. 2. Issue/AGENTS/model-output injection, edited issue after approval, replayed or expired decision, widened path/network/effect request and changed source/test baseline fail closed or require a fresh scoped amendment. 3. Already implemented issue, active equivalent PR, incomplete/permission-limited search, stale source and unknown baseline yield distinct evidence-backed dispositions; open issue alone never proves work remains. 4. Approved spec amendments preserve immutable history and invalidate affected stale acceptance; no worker/Console can grant itself authority. 5. Producer-consumer tests prove approved requirements are delivered intact to the routing translator and unsupported requirements are explicit, never silently downgraded to reference/L0. 6. Existing frozen durable TaskSpec identities remain readable/recoverable; migration and operator docs distinguish these historical fixtures from ordinary intake. No new endpoint/payload/flag asserted before contract review. ## Reuse Start with ProgramSpec/TaskSpec revision/digest and Forge exact-object reads, existing context manifests and Symphony SPEC tracker/workspace/status patterns. Compare authority/freshness/recovery guarantees, exact files/revisions/license/attribution, dependencies and maintenance before adoption; no automatic Symphony scheduler adoption or new DSL. ## Constraints Issue text is data, not approval. Preserve scope/authority, exact-base freezing, immutable Attempt and acceptance subjects, unknown remote effects, no private repo requirement and no automatic merge/deploy. No guessed capability/budget thresholds, provider discovery or local ranking. ## Dependencies And Priority First admission prerequisite: meaningful routing requirements and product review consume this approved spec. Full gateway/isolation acceptance is required before untrusted live execution, but preparation itself can be independently received. Router owns requirement vocabulary and admission; Kernel owns approved task meaning and authority. ## Permissions And Diagnostics Safe read-only issue/source/baseline preparation may need forge access; executing untrusted baseline tests requires the isolation policy. Any model-assisted preparation or live task needs separately scoped inference; effect permissions and numerical budget/quality choices remain owner-approved. Explain stale/unknown/refused cases without leaking content/secrets. ## Links - Parent: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/46 - Immutable intent: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/4 - Historical frozen support: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/42 ## Non-Goals No arbitrary issue execution, new workflow framework, Router profile creation, implementation of target issues or authority from AGENTS.md.
kilo commented 2026-10-06 17:28:29 +00:00
Author
Member
Copy link

Selected under the SAME /loop invocation kernel-loop-20261005T102040Z after completed #48, full canonical queue refresh/exclusions/comments/dependencies and pre-substantive source/contract revalidation. No new invocation or restart of #48's preserved review cycles.

Goal/scope: independently receive read-only ordinary issue preparation, versioned immutable declarations, trusted owner approval, fresh issue/source/baseline/relevance evidence, scoped amendments and actual intact requirements-to-translation/refusal handoff. All six AC remain mandatory. No ordinary live execution, model/budget inference, new ontology/inventory, planner, approval signatures, private sources or sandbox/remote-channel choice authorized.

Actual source distinguishes the frozen143/166 producer/reference-L0 consumer from missing ordinary declarations. Those are this issue's own producer work, not an invented circular prerequisite to #51 or Router175. Exact public Router develop 1dae1948f372e0f1739896655bb7db97d6b08460 inspected read-only: existing three-part TaskRequirement/six minima dimensions/nine constraints; broader interpretation/privacy enforcement not assumed. Actual175 awaits Kernel declarations before agreement. Rich successful mapping is separately gated; #49 still owes an actual full handoff and honest pre-transport refusal seam. Source/natural-language gaps are not turned into owner architecture questions.

Contract-first phase required by AC6: one normal branch issue-49-prepared-specs from canonical develop cb4afda2f1e2f9bc29bda202a3b9924e861a738e; normal owner-authored commit 0b828d5ca1e2a021fb373901ff8f7cb031f0b438 adds explicitly PROPOSED logical contracts to the existing local architecture document, not an implemented/accepted payload, endpoint or flag. SAME new delivery PR #73: #73 . This initial proposal is not functional completion and cannot be merged/closed as #49.

Reuse: exact Symphony SPEC/LICENSE be10a1b79df723d6d7612b5651c8522704dafb2e independently read, Apache2.0; borrow qualified snapshots/reconcile-first comparison only, no source/dependency/scheduler imported. Reuse existing ProgramSpec/history/consumed inputs/authority and journal primitives; authentication stays outside untrusted declaration data and current trusted-local limitations explicit.

Closed-env make check PASS1042tests+57subtests, package-check/audit/diff-check PASS. These cover unchanged historical behavior and proposal documentation, not unimplemented ordinary-intake acceptance. Contract-first independent whole-PR review will reserve ordinal1/10 before dispatch; preliminary COMMENT/retries also consume #49's unchanged total10 budget. Implementation and final fresh whole-PR review follow on same PR after contract feedback, with all historical143/166 envelopes preserved. No live inference, Router operation, cross-repository mutation, main/release/deploy or credential expansion.

Selected under the SAME `/loop` invocation `kernel-loop-20261005T102040Z` after completed #48, full canonical queue refresh/exclusions/comments/dependencies and pre-substantive source/contract revalidation. No new invocation or restart of #48's preserved review cycles. Goal/scope: independently receive read-only ordinary issue preparation, versioned immutable declarations, trusted owner approval, fresh issue/source/baseline/relevance evidence, scoped amendments and actual intact requirements-to-translation/refusal handoff. All six AC remain mandatory. No ordinary live execution, model/budget inference, new ontology/inventory, planner, approval signatures, private sources or sandbox/remote-channel choice authorized. Actual source distinguishes the frozen143/166 producer/reference-L0 consumer from missing ordinary declarations. Those are this issue's own producer work, not an invented circular prerequisite to #51 or Router175. Exact public Router develop `1dae1948f372e0f1739896655bb7db97d6b08460` inspected read-only: existing three-part TaskRequirement/six minima dimensions/nine constraints; broader interpretation/privacy enforcement not assumed. Actual175 awaits Kernel declarations before agreement. Rich successful mapping is separately gated; #49 still owes an actual full handoff and honest pre-transport refusal seam. Source/natural-language gaps are not turned into owner architecture questions. **Contract-first phase required by AC6:** one normal branch `issue-49-prepared-specs` from canonical develop `cb4afda2f1e2f9bc29bda202a3b9924e861a738e`; normal owner-authored commit `0b828d5ca1e2a021fb373901ff8f7cb031f0b438` adds explicitly PROPOSED logical contracts to the existing local architecture document, not an implemented/accepted payload, endpoint or flag. SAME new delivery PR #73: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/73 . This initial proposal is not functional completion and cannot be merged/closed as #49. Reuse: exact Symphony SPEC/LICENSE `be10a1b79df723d6d7612b5651c8522704dafb2e` independently read, Apache2.0; borrow qualified snapshots/reconcile-first comparison only, no source/dependency/scheduler imported. Reuse existing ProgramSpec/history/consumed inputs/authority and journal primitives; authentication stays outside untrusted declaration data and current trusted-local limitations explicit. Closed-env `make check` PASS1042tests+57subtests, package-check/audit/diff-check PASS. These cover unchanged historical behavior and proposal documentation, not unimplemented ordinary-intake acceptance. Contract-first independent whole-PR review will reserve ordinal1/10 before dispatch; preliminary COMMENT/retries also consume #49's unchanged total10 budget. Implementation and final fresh whole-PR review follow on same PR after contract feedback, with all historical143/166 envelopes preserved. No live inference, Router operation, cross-repository mutation, main/release/deploy or credential expansion.
kilo commented 2026-10-06 20:29:55 +00:00
Author
Member
Copy link

Same invocation/issue/PR73 continues. Contract-first ordinal1 COMMENT/nofindings preserved; implementation published normally as37fb62b. Complete-PR reviews2/3/4 returned concrete findings, all reproduced and repaired without resetting the 4/10 consumed budget or weakening acceptance:

  • 02fe54d...: closes baseline evidence cut after Forge reads, validates both snapshots, and retains actual PR base.ref target identity; same-SHA other-target and moving-target cases no longer falsely classify equivalence. 28 pre-fix failing cases; full1147tests+57subtests passed.
  • 61c0797...: earliest durable semantic receipt age across amendments, issue/provenance changes, aliases and reopen; genuinely new receipt positive; unchanged historical bytes retained. 10 pre-fix failures; full1166tests+57subtests passed.
  • Current c03124611d, treebf812160e566a98b89222326465dc64325b03390: immutable non-executable lower-age journal facts preserve newly learned conservative time100->50->151 without draft revision/expiry changes. Kind-aware namespace/subject recovery fixes accepted taskID'draft' consumption collision/store poisoning; legacy records remain readable byte-identically, no controller IDs banned. Five pre-fix failures; focused146tests, full 1188tests+57subtests, package/installed preparation-approval-real-refusal-reopen/audit/diff checks passed in closed synthetic environment.

Only existing journal/artifacts used; no new table/tracker/cache/globalservice/auth/profile. Historical143/166/CoreFSM/CLI unaffected. Current normal branch clean, ordinary owner-authored commits/pushes, no rewrite. Earliest-age evidence scope is the existing store/trusted-reader boundary, not globally atomic remote-state enforcement. Supported relevance remains explicit exact-byte obligations; arbitrary semantic criteria unknown. Ordinary live execution and successful rich mapping remain unsupported; real requirements-preserving refusal precedes transport.

Next whole-PR review ordinal5 will be reserved only after fresh exactHEAD/base currentness freeze. No current APPROVE/merge/closure claim, no issue selection advancement, live inference/Router operation/privateaccess/main/release/deploy/security expansion. Issue48 COMPLETE/history untouched.

Same invocation/issue/PR73 continues. Contract-first ordinal1 COMMENT/nofindings preserved; implementation published normally as37fb62b. Complete-PR reviews2/3/4 returned concrete findings, all reproduced and repaired without resetting the **4/10** consumed budget or weakening acceptance: - `02fe54d...`: closes baseline evidence cut after Forge reads, validates both snapshots, and retains actual PR `base.ref` target identity; same-SHA other-target and moving-target cases no longer falsely classify equivalence. 28 pre-fix failing cases; full1147tests+57subtests passed. - `61c0797...`: earliest durable semantic receipt age across amendments, issue/provenance changes, aliases and reopen; genuinely new receipt positive; unchanged historical bytes retained. 10 pre-fix failures; full1166tests+57subtests passed. - Current **c03124611d3f42f6feb228f56a633357c4a0a587**, treebf812160e566a98b89222326465dc64325b03390: immutable non-executable lower-age journal facts preserve newly learned conservative time100->50->151 without draft revision/expiry changes. Kind-aware namespace/subject recovery fixes accepted taskID'draft' consumption collision/store poisoning; legacy records remain readable byte-identically, no controller IDs banned. Five pre-fix failures; focused146tests, full **1188tests+57subtests**, package/installed preparation-approval-real-refusal-reopen/audit/diff checks passed in closed synthetic environment. Only existing journal/artifacts used; no new table/tracker/cache/globalservice/auth/profile. Historical143/166/CoreFSM/CLI unaffected. Current normal branch clean, ordinary owner-authored commits/pushes, no rewrite. Earliest-age evidence scope is the existing store/trusted-reader boundary, not globally atomic remote-state enforcement. Supported relevance remains explicit exact-byte obligations; arbitrary semantic criteria unknown. Ordinary live execution and successful rich mapping remain unsupported; real requirements-preserving refusal precedes transport. Next whole-PR review ordinal5 will be reserved only after fresh exactHEAD/base currentness freeze. No current APPROVE/merge/closure claim, no issue selection advancement, live inference/Router operation/privateaccess/main/release/deploy/security expansion. Issue48 COMPLETE/history untouched.
kilo commented 2026-10-06 22:18:10 +00:00
Author
Member
Copy link

COMPLETE: Reviewed Preparation Slice Merged And Integrated

Same sole-primary invocation kernel-loop-20261005T102040Z, PR #73, normal issue branch. Supported MCP style=merge succeeded without force/auto-merge/history rewrite. Merge commit a9a65006cc, parents approved base cb4afda2f1 + approved HEAD 4ae082d709. Integrated tree 75028f5877 equals reviewed HEAD byte-for-byte; ancestry/full delta equality and merged/closed metadata verified. Normal checkout clean on current develop.

Independent Review And Preserved History

Normal #49 delivery used 8/10 whole-PR reviews, no new cycle/counter reset:

  1. 0b828d5 COMMENT/findings[]: required contract-first logical proposal reception; not feature approval.
  2. 37fb62b REQUEST_CHANGES: closing baseline cut/target branch repaired02fe54d.
  3. 02fe54d REQUEST_CHANGES: cross-amendment receipt age repaired61c0797.
  4. 61c0797 REQUEST_CHANGES: durable newly learned lower age/kind namespace repairedc031246.
  5. c031246 REQUEST_CHANGES: cancelled Program authority repairedd07d8fa.
  6. d07d8fa REQUEST_CHANGES: late permission provenance repairedbb39d6.
  7. 4bb39d6 REQUEST_CHANGES: final store-read/time authority repaired4ae082d.
  8. 4ae082d APPROVE/findings[], fresh native independent ses_eecc1520bffecjpmfG2PeRrSkt, exact basecb4afda. Complete accumulated 13-file proposal+implementation+remediation/all6AC independently reviewed; initial/final Git+MCP currentness and public pinned source/license verified. No parent self-review or weaker gate. Each defect reproduced with regressions; old decision/draft/consumption/spec/expiry bytes preserved. #48's earlier completed history untouched.

Integrated Acceptance

  1. Explicit ordinary host-qualified issue produces inert immutable versioned declarations with result/quality/interface/context needs, unknowns, bounded requests, recipes/provenance. No unapproved allocation, Runtime, worker grant, verification process or Forge effect. Not restricted to frozen143/166 task definitions.
  2. Injection, edited issue, source/recipe/baseline changes, expired/replayed decisions and widened scope fail closed or require fresh scoped amendment. Current exact subjects and conservative durable receipt age survive aliases/amendments/reopen; genuinely new receipts distinguished. Final local single-writer read cut finishes privileged I/O before authority time, detects callback writes with existing SQLite counter, then pure expiry/freshness before return/handoff. Cancelled Programs refuse current approval/handoff despite unchanged Spec digest. No global atomic remote/runtime promise.
  3. Real read-only Forgejo-shaped issue/branch/PR observations and exact local Git distinguish current literal implementation/equivalent active selected-target PR/remaining/incomplete/permission-limited/stale/unresolved/unknown baseline. Known other target does not suppress selected-target work; moving target/ref/closing snapshots fail honestly. Late401/403 and confirmed movement retained together, primary permission category preserved, no raw responses/secrets. General semantic assessment remains explicitly unresolved, not a false absence/pass. Baseline comes from identified already-produced evidence, never untrusted execution or empty checks.
  4. Existing immutable ProgramSpec/SpecAmendment/journal/content-addressed storage and consumed declaration/source/recipe/result-scope inputs preserve history/invalidate stale acceptance. Operational-only Core applicability remains unchanged. Trusted Principal is outside proposer/issue/model/Console data; logical caller checks are not a new authentication service or hostile same-UID guarantee. Inert metadata cannot be claimed as worker delivery; malformed/version/kind/namespace records fail closed without rewriting history.
  5. FULL approved bytes/requirements/revision/evidence/decision reach actual ScarcityRouterAllocator translation/refusal seam unchanged. Unsupported mapping explicitly returns bound ordinary_requirement_mapping_unavailable before any transport; no reference/L0 fallback. Actual translator spies and installed smoke prove delivery, not merely a recording fake. Successful rich mapping/execution remains #51/Router175 and is not claimed.
  6. Historical frozen143/166 definitions/digests/base/envelopes/allocation/receipt recovery unchanged. Ordinary schema/kind records survive reopen/interrupted publication/create/amend; migration/operator docs describe current local API and limitations. AC6 independent logical contract review preceded implementation/payload claims. Exact public Router1dae1948... and SymphonySPEC/LICENSEbe10a1b... verified; design-only reuse, no copied source/library/framework/scheduler/ontology or private requirement.

Validation

Exact integrated develop uv sync --locked, make check, make package-check, make audit, git diff --check PASS: 1235 tests + 57 subtests, format/lint/typing/inward imports/secrets/reproducible wheel/sdist/installed legacy replay + ordinary real-Git/Forge-shaped preparation/approval/intact refusal/reopen. Native independent review gates and premerge gates likewise passed.

Canonical exact-head PR CI #2360 SUCCESS; integrated develop push CI #2361 SUCCESS: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/actions/runs/125 . Local passes were not substituted for canonical state. No dependency/lock changes.

Closure follows integrated acceptance evidence; fresh SELECT resumes only after closure verified. This receives the expressly independent preparation/approval/refusal slice, NOT ordinary live execution, successful rich Router mapping, remote approval authentication, worker-hostile isolation, private access, product GO, main, release or deployment. No live inference/Router operation or broader credentials authorized/used.

## COMPLETE: Reviewed Preparation Slice Merged And Integrated Same sole-primary invocation `kernel-loop-20261005T102040Z`, PR #73, normal issue branch. Supported MCP `style=merge` succeeded without force/auto-merge/history rewrite. Merge commit **a9a65006cc8cc5b5e4468746a18ff51daf742e6b**, parents approved base **cb4afda2f1e2f9bc29bda202a3b9924e861a738e** + approved HEAD **4ae082d709b680f73e2fd067826dbaf3113a4588**. Integrated tree **75028f5877c6720dee4a9f416c844b32e2b4a09b** equals reviewed HEAD byte-for-byte; ancestry/full delta equality and merged/closed metadata verified. Normal checkout clean on current develop. ### Independent Review And Preserved History Normal #49 delivery used **8/10** whole-PR reviews, no new cycle/counter reset: 1. 0b828d5 COMMENT/findings[]: required contract-first logical proposal reception; not feature approval. 2. 37fb62b REQUEST_CHANGES: closing baseline cut/target branch repaired02fe54d. 3. 02fe54d REQUEST_CHANGES: cross-amendment receipt age repaired61c0797. 4. 61c0797 REQUEST_CHANGES: durable newly learned lower age/kind namespace repairedc031246. 5. c031246 REQUEST_CHANGES: cancelled Program authority repairedd07d8fa. 6. d07d8fa REQUEST_CHANGES: late permission provenance repairedbb39d6. 7. 4bb39d6 REQUEST_CHANGES: final store-read/time authority repaired4ae082d. 8. **4ae082d APPROVE/findings[]**, fresh native independent `ses_eecc1520bffecjpmfG2PeRrSkt`, exact basecb4afda. Complete accumulated 13-file proposal+implementation+remediation/all6AC independently reviewed; initial/final Git+MCP currentness and public pinned source/license verified. No parent self-review or weaker gate. Each defect reproduced with regressions; old decision/draft/consumption/spec/expiry bytes preserved. #48's earlier completed history untouched. ### Integrated Acceptance 1. Explicit ordinary host-qualified issue produces inert immutable versioned declarations with result/quality/interface/context needs, unknowns, bounded requests, recipes/provenance. No unapproved allocation, Runtime, worker grant, verification process or Forge effect. Not restricted to frozen143/166 task definitions. 2. Injection, edited issue, source/recipe/baseline changes, expired/replayed decisions and widened scope fail closed or require fresh scoped amendment. Current exact subjects and conservative durable receipt age survive aliases/amendments/reopen; genuinely new receipts distinguished. Final local single-writer read cut finishes privileged I/O before authority time, detects callback writes with existing SQLite counter, then pure expiry/freshness before return/handoff. Cancelled Programs refuse current approval/handoff despite unchanged Spec digest. No global atomic remote/runtime promise. 3. Real read-only Forgejo-shaped issue/branch/PR observations and exact local Git distinguish current literal implementation/equivalent active selected-target PR/remaining/incomplete/permission-limited/stale/unresolved/unknown baseline. Known other target does not suppress selected-target work; moving target/ref/closing snapshots fail honestly. Late401/403 and confirmed movement retained together, primary permission category preserved, no raw responses/secrets. General semantic assessment remains explicitly unresolved, not a false absence/pass. Baseline comes from identified already-produced evidence, never untrusted execution or empty checks. 4. Existing immutable ProgramSpec/SpecAmendment/journal/content-addressed storage and consumed declaration/source/recipe/result-scope inputs preserve history/invalidate stale acceptance. Operational-only Core applicability remains unchanged. Trusted Principal is outside proposer/issue/model/Console data; logical caller checks are not a new authentication service or hostile same-UID guarantee. Inert metadata cannot be claimed as worker delivery; malformed/version/kind/namespace records fail closed without rewriting history. 5. FULL approved bytes/requirements/revision/evidence/decision reach actual ScarcityRouterAllocator translation/refusal seam unchanged. Unsupported mapping explicitly returns bound `ordinary_requirement_mapping_unavailable` before any transport; no reference/L0 fallback. Actual translator spies and installed smoke prove delivery, not merely a recording fake. Successful rich mapping/execution remains #51/Router175 and is not claimed. 6. Historical frozen143/166 definitions/digests/base/envelopes/allocation/receipt recovery unchanged. Ordinary schema/kind records survive reopen/interrupted publication/create/amend; migration/operator docs describe current local API and limitations. AC6 independent logical contract review preceded implementation/payload claims. Exact public Router1dae1948... and SymphonySPEC/LICENSEbe10a1b... verified; design-only reuse, no copied source/library/framework/scheduler/ontology or private requirement. ### Validation Exact integrated develop `uv sync --locked`, `make check`, `make package-check`, `make audit`, `git diff --check` **PASS: 1235 tests + 57 subtests**, format/lint/typing/inward imports/secrets/reproducible wheel/sdist/installed legacy replay + ordinary real-Git/Forge-shaped preparation/approval/intact refusal/reopen. Native independent review gates and premerge gates likewise passed. Canonical exact-head PR CI **#2360 SUCCESS**; integrated develop push CI **#2361 SUCCESS**: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/actions/runs/125 . Local passes were not substituted for canonical state. No dependency/lock changes. Closure follows integrated acceptance evidence; fresh SELECT resumes only after closure verified. This receives the expressly independent preparation/approval/refusal slice, NOT ordinary live execution, successful rich Router mapping, remote approval authentication, worker-hostile isolation, private access, product GO, main, release or deployment. No live inference/Router operation or broader credentials authorized/used.
kilo closed this issue 2026-10-06 22:18:33 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
issue-62-installed-compatibility
issue-58-private-outcome-export
issue-57-recovery-preparation-alerts
issue-57-owner-served-state
issue-106-final-authority-dag
issue-106-forgejo-ordinary-execution
issue-105-independent-provider-drivers
issue-59-work-resource-ownership
issue-56-atomic-approval-recovery
issue-56-work-budget-enforcement
issue-103-publish-architecture-backlog
issue-62-platform-reception
issue-55-mi-utilized-reference
issue-52-kilo-offline-proof
docs/conversational-review-policy
issue-60-reception-fixture-plan
issue-62-compatibility-matrix-spec
issue-58-export-rights-spec
issue-57-owner-state-spec
issue-56-task-cost-shapes
issue-90-owned-cancellation
issue-54-product-review
issue-53-runtime-integration
No results found.
Labels
Clear labels   
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#56 [Kernel][G12] Account for and enforce whole-task budgets across calls, tools and review
Creatidy/creatidy-kernel
#106 Deliver ordinary Program execution with shared pull and managed push handoffs
Creatidy/creatidy-kernel
Reference
Creatidy/creatidy-kernel#49
No description provided.