[Kernel][G05] Propagate approved task requirements to Router without L0 fallback #51

New issue

Closed

opened 2026-10-04 22:24:52 +00:00 by kilo · 5 comments

kilo commented 2026-10-04 22:24:52 +00:00

Member

Copy link

Goal

Owner: Kernel consumer; Router owns public requirement vocabulary and selection policy. Translate approved TaskSpec quality/context/interface/locality constraints into an existing public Router request, preserving every hard requirement and explicit unknown. Source: shared architecture v1.0, sections 1-8, 9.2-9.4, 10-18 via #46 brief.

Why

The current reference/L0 request does not represent real engineering task requirements; a compatible configured model is not proof of sufficient quality or usable context. Kernel must not invent minima from issue text or maintain a model catalogue/ranking.

Current Evidence

At eb4f4a2956, ports/application.py:97 and task preflight construct reference/128 ResourceRequest; scarcity_router.py select:412-421 accepts only reference and emits task_level=L0, empty capability_minima plus tools/context. #11 proves this deliberately narrow recommendation slice, not ordinary requirements. Router public selection accepts profile_id XOR requirement, tightening only with profile; exact producer shapes must be reread at implementation.

Scope

Consume the approved requirements from #49, classify capability requirements (not models), map only supported producer fields, preserve explicit user pin and harness constraints separately, reject unsupported/ambiguous demands. Compare preflight and dispatch requirements without making readiness a reservation or authorization. Read current Router contracts before defining local values; missing expressiveness is a producer dependency, not invented wire data.

Acceptance Criteria

1. Producer-shaped contract fixtures for qualitatively different approved tasks show appropriate, explainable non-reference requirements and identical preserved hard constraints before dispatch.
2. Unsupported/unknown quality/context/interface/access constraints, contradictory pin, and unapproved changed requirements fail with actionable categories; no silent L0/profile/capability downgrade or guessed numerical floor.
3. Profile plus tightening is monotone, XOR validation is enforced, Router refusal/no-solution stays refusal, and responses cannot expand harness capability or authority.
4. Existing immutable Attempt Allocation recovery uses original request/decision; no reselection after unknown effect. Reference fixtures remain honest and existing persisted identities stay readable.
5. Evidence links approved spec revision, actual request, selected decision/catalog/policy where provided and harness compatibility, without credentials or private quota payload.
6. Public contract tests and diagnostics/documentation distinguish requirement error, no solution and unavailable infrastructure; repository gates and independent exact-HEAD review.

Reuse

Reuse ResourceRequest/Allocator port and strict existing Router transport; compare authoritative producer parsers/schemas/profiles and monotone requirements. Exact revision/files/license/NOTICE/security/dependency maintenance must precede any adaptation. No capability scoring, provider model/list fanout, handwritten large binding catalogue or benchmark selection.

Constraints

Preserve adapters -> ports -> core, pure offline tests, immutable IDs and authority, opaque variant versus explicit effort. Migrations must not relabel old L0 decisions as newer requirements. No numerical thresholds without source/owner approval.

Dependencies And Priority

First routing-quality prerequisite after approved specification #49 and harness feasibility #47; consumed by gateway integration. Producer equivalent for shared task vocabulary was not found initially; Router is responsible for any vocabulary extension and a public producer-consumer proof must precede its use.

Permissions

Synthetic contract acceptance needs no inference. Live adequacy or gateway evidence needs separately authorized inference/service access; capability/quality tradeoffs not defined by sources require owner decision. No permissions granted here.

Links

• Parent: #46
• Approved intake: #49
• Harness proof: #47
• Existing narrow allocator: #11

Non-Goals

No Router policy/profile implementation, benchmark-derived local ranking, gateway execution or automatic task approval.

## Goal Owner: Kernel consumer; Router owns public requirement vocabulary and selection policy. Translate approved TaskSpec quality/context/interface/locality constraints into an existing public Router request, preserving every hard requirement and explicit unknown. Source: shared architecture v1.0, sections 1-8, 9.2-9.4, 10-18 via #46 brief. ## Why The current reference/L0 request does not represent real engineering task requirements; a compatible configured model is not proof of sufficient quality or usable context. Kernel must not invent minima from issue text or maintain a model catalogue/ranking. ## Current Evidence At eb4f4a2956712bfaf39a3271e1523e7f77a91e26, ports/application.py:97 and task preflight construct reference/128 ResourceRequest; scarcity_router.py select:412-421 accepts only reference and emits task_level=L0, empty capability_minima plus tools/context. #11 proves this deliberately narrow recommendation slice, not ordinary requirements. Router public selection accepts profile_id XOR requirement, tightening only with profile; exact producer shapes must be reread at implementation. ## Scope Consume the approved requirements from #49, classify capability requirements (not models), map only supported producer fields, preserve explicit user pin and harness constraints separately, reject unsupported/ambiguous demands. Compare preflight and dispatch requirements without making readiness a reservation or authorization. Read current Router contracts before defining local values; missing expressiveness is a producer dependency, not invented wire data. ## Acceptance Criteria 1. Producer-shaped contract fixtures for qualitatively different approved tasks show appropriate, explainable non-reference requirements and identical preserved hard constraints before dispatch. 2. Unsupported/unknown quality/context/interface/access constraints, contradictory pin, and unapproved changed requirements fail with actionable categories; no silent L0/profile/capability downgrade or guessed numerical floor. 3. Profile plus tightening is monotone, XOR validation is enforced, Router refusal/no-solution stays refusal, and responses cannot expand harness capability or authority. 4. Existing immutable Attempt Allocation recovery uses original request/decision; no reselection after unknown effect. Reference fixtures remain honest and existing persisted identities stay readable. 5. Evidence links approved spec revision, actual request, selected decision/catalog/policy where provided and harness compatibility, without credentials or private quota payload. 6. Public contract tests and diagnostics/documentation distinguish requirement error, no solution and unavailable infrastructure; repository gates and independent exact-HEAD review. ## Reuse Reuse ResourceRequest/Allocator port and strict existing Router transport; compare authoritative producer parsers/schemas/profiles and monotone requirements. Exact revision/files/license/NOTICE/security/dependency maintenance must precede any adaptation. No capability scoring, provider model/list fanout, handwritten large binding catalogue or benchmark selection. ## Constraints Preserve adapters -> ports -> core, pure offline tests, immutable IDs and authority, opaque variant versus explicit effort. Migrations must not relabel old L0 decisions as newer requirements. No numerical thresholds without source/owner approval. ## Dependencies And Priority First routing-quality prerequisite after approved specification #49 and harness feasibility #47; consumed by gateway integration. Producer equivalent for shared task vocabulary was not found initially; Router is responsible for any vocabulary extension and a public producer-consumer proof must precede its use. ## Permissions Synthetic contract acceptance needs no inference. Live adequacy or gateway evidence needs separately authorized inference/service access; capability/quality tradeoffs not defined by sources require owner decision. No permissions granted here. ## Links - Parent: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/46 - Approved intake: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/49 - Harness proof: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/47 - Existing narrow allocator: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/11 ## Non-Goals No Router policy/profile implementation, benchmark-derived local ranking, gateway execution or automatic task approval.

kilo referenced this issue 2026-10-04 22:27:40 +00:00

[Kernel][G06] Retain admitted knowledge snapshot and harness-evidence provenance #55

kilo commented 2026-10-04 22:40:26 +00:00

Author

Member

Copy link

Producer counterpart found after registration: BioMedical-IT/scarcity-router#175, AC1-5 one monotone rich-requirement eligibility pipeline, supplied quality minima/channel/model/authorization intersection, explicit unsupported demands and compatibility. Creatidy/model-intelligence#14 AC1-4 preserves channel/configuration/assertion strength and existing calibration ownership. Actual bodies were read. Their conformance/semantic agreement precedes Kernel translation acceptance; Kernel #49 prepares approved task meaning and #51 must deliver it intact, not create another scale. This supersedes the initial counterpart-not-found note; neither registration is implementation proof.

Producer counterpart found after registration: https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/175, AC1-5 one monotone rich-requirement eligibility pipeline, supplied quality minima/channel/model/authorization intersection, explicit unsupported demands and compatibility. https://forgejo.creatidy.com/Creatidy/model-intelligence/issues/14 AC1-4 preserves channel/configuration/assertion strength and existing calibration ownership. Actual bodies were read. Their conformance/semantic agreement precedes Kernel translation acceptance; Kernel #49 prepares approved task meaning and #51 must deliver it intact, not create another scale. This supersedes the initial counterpart-not-found note; neither registration is implementation proof.

kilo referenced this issue from Creatidy/model-intelligence 2026-10-04 22:49:06 +00:00

Agree capability identity and calibration ownership with Router and Kernel #14

kilo referenced this issue 2026-10-04 22:51:53 +00:00

docs: align shared harness, routing and observability architecture (#46) #63

kilo referenced this issue 2026-10-04 22:58:10 +00:00

Align Creatidy Kernel with the shared harness, routing and observability architecture #46

kilo referenced this issue from Creatidy/scarcity-router 2026-10-04 23:06:44 +00:00

G05: Map rich Kernel task and harness requirements into monotone Router eligibility #175

kilo referenced this issue from Creatidy/scarcity-router 2026-10-04 23:43:29 +00:00

Align Scarcity Router with Creatidy architecture and register actionable gaps (#173) #187

kilo referenced this issue 2026-10-06 17:28:29 +00:00

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

kilo commented 2026-10-07 21:11:42 +00:00

Author

Member

Copy link

Pre-Implementation Eligibility Revalidation: Temporarily Ineligible

Same invocation kernel-loop-20261005T102040Z, fresh full canonical queue after owner-scoped #50 reception. #51 was provisionally selected as oldest remaining tied issue; no branch, commit, PR, substantive edit or review was started.

Actual source inspection succeeded at clean Kernel 1deb32900d, PUBLIC Router 8a0ae13d4b4de96abc1d127c855803ee5e5af5a1 and MI 98b270e387571decceb9be7d177d122656de9fa3. Parent opened concrete source behind findings. #49 producer now EXISTS and is received: core/intake.py98-155 stores exact approved textual quality/interface/context with immutable scope/recipe/evidence/decision handoff. It does not define a Router profile/minima/pin/harness interpretation. The earlier Router175 comments claiming absentKernel49 are historical, not current gate evidence.

Router's actual TaskRequirement/profile/XOR/monotone pipeline and calibrated non-reference profiles exist (e.g deep_coding L3/reason4/code5/tool4, editorial L2/reason3/writing5). This is NOT absence of numeric machinery, or an inference from an open issue. Those calibrations apply when an approved explicit profile is selected; they do not authorize interpreting 'preserve exact encoding', 'UTF-8 file', or 'private local context; no egress' as those choices. Null minimum means no requirement, not unknown; privacy matching tags do not enforce no-egress. Current51comment14074/Router175 requires shared supported interpretation/conformance before acceptance.

MI14 is CLOSED with an accepted ownership/research boundary, but its actual ARCHITECTURE scope and consumer test pins exercise old Kernel/Router reference input, not actual approved rich #49 declaration-to-request mapping. No newer inspected public receipt defines the missing interpretation. Kernel's real all-refusal seam preserves meaning honestly but repeating that would not satisfy #51AC1 appropriate explainable non-reference positive fixtures.

Precise missing prerequisite: source-shaped approved structured request/profile choice and agreed coverage/interpretation receipt between Kernel task meaning and Router producer semantics. String-marker grammar, profile-from-prose heuristic, locally invented threshold/ontology/fields, unknown-as-omitted/defaultL0, or changes in another product are not authorized substitutes. Existing transport/sticky/provenance mechanics remain reusable once input semantics received. No genuinely new quality-tradeoff owner decision was demonstrated, no tooling/private/access blocker or need for live inference.

Under current post-selection rule, untouched confirmed missing producer/contract => temporarily ineligible, issue stays OPEN, NONTERMINAL fresh SELECT, not whole-loop BLOCKED/STOP_AND_ASK. All delivery history preserved; current clean develop unchanged. #52's explicit dependency on received #51 remains unmet. No issue created/labels/scope/acceptance weakened, Router operation, cross-repo mutation, private/live/main/release/deploy/security or budget inference.

## Pre-Implementation Eligibility Revalidation: Temporarily Ineligible Same invocation `kernel-loop-20261005T102040Z`, fresh full canonical queue after owner-scoped #50 reception. #51 was provisionally selected as oldest remaining tied issue; no branch, commit, PR, substantive edit or review was started. Actual source inspection succeeded at clean Kernel **1deb32900d10dab6a3baad0c454ef9aa19c58733**, PUBLIC Router **8a0ae13d4b4de96abc1d127c855803ee5e5af5a1** and MI **98b270e387571decceb9be7d177d122656de9fa3**. Parent opened concrete source behind findings. #49 producer now EXISTS and is received: core/intake.py98-155 stores exact approved textual quality/interface/context with immutable scope/recipe/evidence/decision handoff. It does not define a Router profile/minima/pin/harness interpretation. The earlier Router175 comments claiming absentKernel49 are historical, not current gate evidence. Router's actual TaskRequirement/profile/XOR/monotone pipeline and calibrated non-reference profiles exist (e.g deep_coding L3/reason4/code5/tool4, editorial L2/reason3/writing5). This is NOT absence of numeric machinery, or an inference from an open issue. Those calibrations apply when an approved explicit profile is selected; they do not authorize interpreting 'preserve exact encoding', 'UTF-8 file', or 'private local context; no egress' as those choices. Null minimum means no requirement, not unknown; privacy matching tags do not enforce no-egress. Current51comment14074/Router175 requires shared supported interpretation/conformance before acceptance. MI14 is CLOSED with an accepted ownership/research boundary, but its actual ARCHITECTURE scope and consumer test pins exercise old Kernel/Router reference input, not actual approved rich #49 declaration-to-request mapping. No newer inspected public receipt defines the missing interpretation. Kernel's real all-refusal seam preserves meaning honestly but repeating that would not satisfy #51AC1 appropriate explainable non-reference positive fixtures. **Precise missing prerequisite:** source-shaped approved structured request/profile choice and agreed coverage/interpretation receipt between Kernel task meaning and Router producer semantics. String-marker grammar, profile-from-prose heuristic, locally invented threshold/ontology/fields, unknown-as-omitted/defaultL0, or changes in another product are not authorized substitutes. Existing transport/sticky/provenance mechanics remain reusable once input semantics received. No genuinely new quality-tradeoff owner decision was demonstrated, no tooling/private/access blocker or need for live inference. Under current post-selection rule, untouched confirmed missing producer/contract => **temporarily ineligible, issue stays OPEN, NONTERMINAL fresh SELECT**, not whole-loop BLOCKED/STOP_AND_ASK. All delivery history preserved; current clean develop unchanged. #52's explicit dependency on received #51 remains unmet. No issue created/labels/scope/acceptance weakened, Router operation, cross-repo mutation, private/live/main/release/deploy/security or budget inference.

kilo referenced this issue 2026-10-07 22:21:51 +00:00

[Kernel][G01] Integrate the proved harness lifecycle through the existing Runtime boundary #53

kilo commented 2026-10-08 08:09:35 +00:00

Author

Member

Copy link

Fresh producer revalidation supersedes the previously recorded semantic gate in comment15575. Router develop 5c48d51f1eb1f11424a5100eb2ccf20a6cba4581 (PR200/#175) now contains scarcity_router/kernel_requirements.py, D-075 and positive/negative local core conformance for explicit Declaration-v1 quality/interface markers, monotone profile floors, bound declaration digest and refusals for unknown/textual context. Exact pinned source/docs/tests and Apache-2.0 license were inspected independently of merged/closed status.

This supplies the bounded interpretation prerequisite, not Kernel consumer reception, executable gateway/resource pins, real-harness proof or live readiness. Existing /v1/select wire contract remains profile XOR explicit requirement; no RequestBinding/pin field will be invented on that endpoint. Original approved bytes/context/unknowns cannot be silently rewritten or stripped.

The same owner-authorized Kernel loop selects #51 as the next eligible routing-quality prerequisite after verified #61 completion. Clean base 71c132761b522c7faeee1a1aca51f1a296a947ec; ordinary branch issue-51-approved-requirements; no implementation commit/PR/review yet, counter0. Scope remains all six acceptance criteria with synthetic offline contracts only. #53 universal executor proof and #55 admitted-MI producer result remain separate unreceived gates.

Fresh producer revalidation supersedes the previously recorded semantic gate in comment15575. Router develop `5c48d51f1eb1f11424a5100eb2ccf20a6cba4581` (PR200/#175) now contains `scarcity_router/kernel_requirements.py`, D-075 and positive/negative local core conformance for explicit Declaration-v1 quality/interface markers, monotone profile floors, bound declaration digest and refusals for unknown/textual context. Exact pinned source/docs/tests and Apache-2.0 license were inspected independently of merged/closed status. This supplies the bounded interpretation prerequisite, not Kernel consumer reception, executable gateway/resource pins, real-harness proof or live readiness. Existing `/v1/select` wire contract remains profile XOR explicit requirement; no RequestBinding/pin field will be invented on that endpoint. Original approved bytes/context/unknowns cannot be silently rewritten or stripped. The same owner-authorized Kernel loop selects #51 as the next eligible routing-quality prerequisite after verified #61 completion. Clean base `71c132761b522c7faeee1a1aca51f1a296a947ec`; ordinary branch `issue-51-approved-requirements`; no implementation commit/PR/review yet, counter0. Scope remains all six acceptance criteria with synthetic offline contracts only. #53 universal executor proof and #55 admitted-MI producer result remain separate unreceived gates.

adrian.tkacz referenced this issue from a commit 2026-10-08 10:36:35 +00:00

feat: preserve approved ordinary requirements through Router selection (#51)

kilo referenced this issue 2026-10-08 10:36:56 +00:00

Propagate approved ordinary requirements without reference fallback (#51) #76

kilo commented 2026-10-08 10:37:10 +00:00

Author

Member

Copy link

Scoped consumer implementation published as PR #76: #76
Base 71c132761b522c7faeee1a1aca51f1a296a947ec, HEAD 02a062b354ed5b921b81537f7aab39616c038a92.
Actual approved intake->typed ResourceRequest->explicit model recommendation path preserves original Declaration/revision/evidence/decision/Program, all supported hard/pin/structural meaning and original request/decision Allocation-v2 recovery. Historical reference/version1 bytes remain unchanged; unsupported semantics refuse without L0 fallback. No ordinary execution engine or executable gateway conformance introduced.
Parent closed-environment full check/package/audit/diff passed:1387+57,53 optional verification-only native skips; installed typed loopback/reopen smoke passed. Fresh independent whole-PR review follows, counter0 before reservation. Same invocation; issue open, no product/live GO.

Scoped consumer implementation published as PR #76: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/76 Base `71c132761b522c7faeee1a1aca51f1a296a947ec`, HEAD `02a062b354ed5b921b81537f7aab39616c038a92`. Actual approved intake->typed ResourceRequest->explicit model recommendation path preserves original Declaration/revision/evidence/decision/Program, all supported hard/pin/structural meaning and original request/decision Allocation-v2 recovery. Historical reference/version1 bytes remain unchanged; unsupported semantics refuse without L0 fallback. No ordinary execution engine or executable gateway conformance introduced. Parent closed-environment full check/package/audit/diff passed:1387+57,53 optional verification-only native skips; installed typed loopback/reopen smoke passed. Fresh independent whole-PR review follows, counter0 before reservation. Same invocation; issue open, no product/live GO.

adrian.tkacz referenced this issue from a commit 2026-10-08 10:55:32 +00:00

fix: preserve decoded credentials and reasoning harness constraints (#51)

adrian.tkacz referenced this issue from a commit 2026-10-08 11:12:44 +00:00

fix: decode approval evidence under its owning intake contract (#51)

kilo referenced this issue from a commit 2026-10-08 11:23:22 +00:00

Merge PR #76: approved ordinary requirement consumer reception (#51)

kilo commented 2026-10-08 11:27:56 +00:00

Author

Member

Copy link

Completed bounded consumer reception through PR #76: #76

Normal merge 56a95aaccb3286022ff56c650efceb41e73cdbdb verified with exact parents base 71c132761b522c7faeee1a1aca51f1a296a947ec and approved HEAD 626deddf9e41df836331801f65597b2ecbb33000, identical approved tree f14e1ac348bb8d0c197bf5ee0a82181daeda90ce. Three fresh independent whole-PR reviews consumed; final ordinal3 APPROVE/findings[]. Normal implementation/remediation history retained.

Integrated closed-environment uv sync --locked, make check package-check audit && git diff --check PASS:1395 tests+57 subtests,53 optional verification-only native skips; format/lint/types/inward imports/secrets/reproducible package/isolated install/typed loopback intake-selection/original evidence reopen/source smoke/audit passed. Exact-head CI2381 and integrated CI2382 SUCCESS.

All six AC received for the recommendation consumer: approved coding/editorial producer-shaped nonreference requests and hard constraints; explicit unsupported/unknown/context/access/pin/change refusals; profile XOR/full monotone expansion/version and refusal preservation; independently configured structural/harness checks; full approved revision/decision/Program plus actual request/public decision/catalog/policy and original Allocation-v2 recovery without reselection after unknown effects. Historical v1/#143/#166 bytes/identities remain unchanged. Decoded/raw bearer contamination refuses before evidence; valid large approval records obey intake decoding, not unrelated Router-response bounds.

Router #175 supplied local interpretation, not this Kernel consumer integration by itself. This closure receives bounded approved-requirement recommendation and immutable recovery only: no executable gateway/admission, ordinary native dispatcher, real-harness/universal worker conformance, privacy enforcement, live inference or product GO. Those remain separate #52/#53/producer obligations. Same invocation now continues fresh full SELECT.

Completed bounded consumer reception through PR #76: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/76 Normal merge `56a95aaccb3286022ff56c650efceb41e73cdbdb` verified with exact parents base `71c132761b522c7faeee1a1aca51f1a296a947ec` and approved HEAD `626deddf9e41df836331801f65597b2ecbb33000`, identical approved tree `f14e1ac348bb8d0c197bf5ee0a82181daeda90ce`. Three fresh independent whole-PR reviews consumed; final ordinal3 APPROVE/findings[]. Normal implementation/remediation history retained. Integrated closed-environment `uv sync --locked`, `make check package-check audit && git diff --check` PASS:1395 tests+57 subtests,53 optional verification-only native skips; format/lint/types/inward imports/secrets/reproducible package/isolated install/typed loopback intake-selection/original evidence reopen/source smoke/audit passed. Exact-head CI2381 and integrated CI2382 SUCCESS. All six AC received for the recommendation consumer: approved coding/editorial producer-shaped nonreference requests and hard constraints; explicit unsupported/unknown/context/access/pin/change refusals; profile XOR/full monotone expansion/version and refusal preservation; independently configured structural/harness checks; full approved revision/decision/Program plus actual request/public decision/catalog/policy and original Allocation-v2 recovery without reselection after unknown effects. Historical v1/#143/#166 bytes/identities remain unchanged. Decoded/raw bearer contamination refuses before evidence; valid large approval records obey intake decoding, not unrelated Router-response bounds. Router #175 supplied local interpretation, not this Kernel consumer integration by itself. This closure receives bounded approved-requirement recommendation and immutable recovery only: no executable gateway/admission, ordinary native dispatcher, real-harness/universal worker conformance, privacy enforcement, live inference or product GO. Those remain separate #52/#53/producer obligations. Same invocation now continues fresh full SELECT.

kilo closed this issue 2026-10-08 11:28:04 +00:00

kilo referenced this issue 2026-10-27 00:29:34 +00:00

Deliver ordinary Program execution with shared pull and managed push handoffs #106

kilo added a new dependency 2026-10-27 00:30:15 +00:00

#52 [Kernel][G04 G10] Consume Router execution decisions and preserve Attempt-bound route identity

kilo referenced this issue 2026-10-27 00:30:58 +00:00

[Kernel][G04 G10] Consume Router execution decisions and preserve Attempt-bound route identity #52

kilo referenced this issue 2026-10-27 00:33:55 +00:00

Revise unified work coordination architecture and realign the canonical backlog #103

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

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#52 [Kernel][G04 G10] Consume Router execution decisions and preserve Attempt-bound route identity

Creatidy/creatidy-kernel

Reference

Creatidy/creatidy-kernel#51

No description provided.