Creatidy/scarcity-router
5
0
Fork 0
Code Issues 13 Pull requests Projects Releases Packages Wiki Activity Actions

Align Scarcity Router with the Creatidy system architecture and register actionable gaps #173

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

Goal

Owner-selected documentation/planning alignment of Scarcity Router with Creatidy shared system architecture v1.0 (2026-10-04), covering G01-G13 with Router-owned work distinguished from Creatidy Kernel, Model Intelligence and Console ownership. Deliver one documentation PR to develop and register every known actionable Router gap without implementing it. Include the owner's subsequent current-tree/mutable-surface terminology remediation and full final reviewer report.

Why

The owner explicitly mandates full, coherent products, not loss of known requirements behind a minimal release. Existing #85 and #146 are completed gateway/D-056 architecture deliveries, not this new cross-product alignment. Code proves integrated behavior, not conformance to a superseding goal or live deployment. Current fetched develop is 8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b (2026-10-04), equal to the source's historical Router revision; open PR #170 is not integrated and overlaps newer merged #172.

Source and Interpretation

Creatidy_architektura_systemu_2026-10-04.md, v1.0, supplied SHA-256 4e64121599ac30896afb77574b2fd16cddfc3420afde37108611715c24b56e92. Full file not found in workspace searches; use the owner's complete repository-specific brief, sections 1-5, 7-13, 14-18 of the source, without claiming to have verified the file bytes. Preserve Agreed / Verified / Proposed clarification / To prove. Do not invent subsection titles, endpoints, payloads, numeric budgets or cross-product issue numbers.

The owner's later 2026-10-04 terminology instruction supersedes the earlier brief's naming explanation: use the distinct canonical Creatidy Kernel / creatidy-kernel and Scarcity Router / scarcity-router names directly. Delete unnecessary erroneous naming text rather than preserving an alias, typo interpretation, renamed product or additional component. Responsibilities are unchanged; no redesign is authorized. Record the supersession in D-068 without institutionalizing the wrong name.

Scope

  • Revalidate canonical Git/Forgejo, actual code/tests/contracts and relevant open/closed issues, PRs and recent merges.
  • Maintain requirement -> owner -> revision/file/symbol evidence -> document correction -> existing issue/PR -> registered gap matrix throughout work.
  • Update existing English README, product, architecture, ADR, roadmap, integration/capacity/security/operator/release documents and concise agent rules in their owning locations. Preserve historical ADRs; explicitly record D-063 workspace-editing conflict with Kernel/harness ownership, not silently remove a working path.
  • Deduplicate and register implementation-grade research/contract/implementation issues for Router G04-G10/G12-G13, including migration, negative/producer-consumer tests, UX, reuse proof and separately authorized live acceptance. G01-G03/G11 remain Kernel work unless current evidence identifies an independent Router defect.
  • Read public Kernel/MI sources and canonical counterparts, modify only Router repo/issues/PR, reread counterparts once before closeout.
  • Inspect the complete current tree including hidden tracked workflow/agent files, source/config/tests/examples and generated textual references, plus open canonical issue/PR descriptions and current task/delivery comments. Classify each actual terminology occurrence by authoritative responsibility or remove unnecessary text. Do not blindly replace, rewrite Git history/closed historical records, or alter explicitly verbatim historical evidence.

Acceptance Criteria

  1. One focused English documentation PR from current develop with exact base/head, no product implementation/public-schema change, no unrelated merge commits; left open for owner review.
  2. Every G01-G13 row has evidence-backed disposition: satisfied, precise existing coverage, actual newly registered URL, combined coverage, named external owner/contract, or concrete non-addressability justification. No unresolved known work hidden behind TODO/DEFER.
  3. Documents distinguish implemented/proposed/integrated/live; mode onboarding never presents recommendation-only REST as an inference gateway. Selection inventory, hard quality, authorization, identity, tools, economic/unknown guarantees, MI bootstrap transition and Console state ownership match the mandate.
  4. New/updated issues include product/Gxx/source sections, evidence vs hypotheses, goal/why/scope/non-goals/invariants, producers/consumers/dependencies/order, behavior/negative/failure acceptance, compatibility/migration/security/diagnostics, mandatory reuse audit, justified ordering, and future authority/access needed.
  5. Source reference, links/index/ADR references and agent instructions checked; required local gates executed; exact frozen whole-PR + backlog independent review includes UX, completeness, terminology and unauthorized assumptions. Review verdict and formal Forgejo state reported separately.
  6. Full final reviewer report includes exact repo/base/head/reviewed head, PR/main task, unmerged state, every changed file, complete G matrix and actual issues, first-priority discrepancies with closure conditions, cross-product dependencies/owner decisions, gates/CI/review/budget and explicit no implementation/inference/secrets/merge/deploy.
  7. The owner's exact forbidden-string git grep and case/separator sweep return zero current-tree matches on final HEAD; audited mutable Forgejo surfaces contain no active use. Report every corrected file/issue/PR/comment, occurrence classification and any evidence-only retention outside mutable/current scope. Never claim completion while an active occurrence remains.

Constraints

Documentation and issue registration only; no deployment/services/permissions/secrets/branch protection/release/main changes. No product inference or real task execution. One issue/branch/PR. Threat model unchanged: no new credential or network exposure, no implied workspace authority. Classification: documentation/planning, not implementation of security-critical changes. Budget: 120 minutes from session start, one initial independent review, at most one remediation, one narrow final verification; one concrete-diagnosis retry per worker/reviewer. Frozen review HEAD/base; no pushes during review. No new review controller; later owner clarification does not reset budget.

Reuse

Inspect local selector/routing/pin/admission/inventory/worker/UI first. Rich, OpenTelemetry, selected LiteLLM translators/tests and Langfuse/OpenRouter patterns are candidates only; implementation issues must prove exact revision/files/license/semantics/negative tests/security/maintenance before adoption. MI owns external fact collection; no parallel Router crawler.

Links

Creation and later clarification explicitly select this documentation task; they do not authorize execution of the registered future issues.

## Goal Owner-selected documentation/planning alignment of **Scarcity Router** with Creatidy shared system architecture v1.0 (2026-10-04), covering G01-G13 with Router-owned work distinguished from Creatidy Kernel, Model Intelligence and Console ownership. Deliver one documentation PR to develop and register every known actionable Router gap without implementing it. Include the owner's subsequent current-tree/mutable-surface terminology remediation and full final reviewer report. ## Why The owner explicitly mandates full, coherent products, not loss of known requirements behind a minimal release. Existing #85 and #146 are completed gateway/D-056 architecture deliveries, not this new cross-product alignment. Code proves integrated behavior, not conformance to a superseding goal or live deployment. Current fetched develop is `8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b` (2026-10-04), equal to the source's historical Router revision; open PR #170 is not integrated and overlaps newer merged #172. ## Source and Interpretation `Creatidy_architektura_systemu_2026-10-04.md`, v1.0, supplied SHA-256 `4e64121599ac30896afb77574b2fd16cddfc3420afde37108611715c24b56e92`. Full file not found in workspace searches; use the owner's complete repository-specific brief, sections 1-5, 7-13, 14-18 of the source, without claiming to have verified the file bytes. Preserve **Agreed / Verified / Proposed clarification / To prove**. Do not invent subsection titles, endpoints, payloads, numeric budgets or cross-product issue numbers. The owner's later 2026-10-04 terminology instruction supersedes the earlier brief's naming explanation: use the distinct canonical **Creatidy Kernel / creatidy-kernel** and **Scarcity Router / scarcity-router** names directly. Delete unnecessary erroneous naming text rather than preserving an alias, typo interpretation, renamed product or additional component. Responsibilities are unchanged; no redesign is authorized. Record the supersession in D-068 without institutionalizing the wrong name. ## Scope - Revalidate canonical Git/Forgejo, actual code/tests/contracts and relevant open/closed issues, PRs and recent merges. - Maintain requirement -> owner -> revision/file/symbol evidence -> document correction -> existing issue/PR -> registered gap matrix throughout work. - Update existing English README, product, architecture, ADR, roadmap, integration/capacity/security/operator/release documents and concise agent rules in their owning locations. Preserve historical ADRs; explicitly record D-063 workspace-editing conflict with Kernel/harness ownership, not silently remove a working path. - Deduplicate and register implementation-grade research/contract/implementation issues for Router G04-G10/G12-G13, including migration, negative/producer-consumer tests, UX, reuse proof and separately authorized live acceptance. G01-G03/G11 remain Kernel work unless current evidence identifies an independent Router defect. - Read public Kernel/MI sources and canonical counterparts, modify only Router repo/issues/PR, reread counterparts once before closeout. - Inspect the complete current tree including hidden tracked workflow/agent files, source/config/tests/examples and generated textual references, plus open canonical issue/PR descriptions and current task/delivery comments. Classify each actual terminology occurrence by authoritative responsibility or remove unnecessary text. Do not blindly replace, rewrite Git history/closed historical records, or alter explicitly verbatim historical evidence. ## Acceptance Criteria 1. One focused English documentation PR from current develop with exact base/head, no product implementation/public-schema change, no unrelated merge commits; left open for owner review. 2. Every G01-G13 row has evidence-backed disposition: satisfied, precise existing coverage, actual newly registered URL, combined coverage, named external owner/contract, or concrete non-addressability justification. No unresolved known work hidden behind TODO/DEFER. 3. Documents distinguish implemented/proposed/integrated/live; mode onboarding never presents recommendation-only REST as an inference gateway. Selection inventory, hard quality, authorization, identity, tools, economic/unknown guarantees, MI bootstrap transition and Console state ownership match the mandate. 4. New/updated issues include product/Gxx/source sections, evidence vs hypotheses, goal/why/scope/non-goals/invariants, producers/consumers/dependencies/order, behavior/negative/failure acceptance, compatibility/migration/security/diagnostics, mandatory reuse audit, justified ordering, and future authority/access needed. 5. Source reference, links/index/ADR references and agent instructions checked; required local gates executed; exact frozen whole-PR + backlog independent review includes UX, completeness, terminology and unauthorized assumptions. Review verdict and formal Forgejo state reported separately. 6. Full final reviewer report includes exact repo/base/head/reviewed head, PR/main task, unmerged state, every changed file, complete G matrix and actual issues, first-priority discrepancies with closure conditions, cross-product dependencies/owner decisions, gates/CI/review/budget and explicit no implementation/inference/secrets/merge/deploy. 7. The owner's exact forbidden-string git grep and case/separator sweep return zero current-tree matches on final HEAD; audited mutable Forgejo surfaces contain no active use. Report every corrected file/issue/PR/comment, occurrence classification and any evidence-only retention outside mutable/current scope. Never claim completion while an active occurrence remains. ## Constraints Documentation and issue registration only; no deployment/services/permissions/secrets/branch protection/release/main changes. No product inference or real task execution. One issue/branch/PR. Threat model unchanged: no new credential or network exposure, no implied workspace authority. Classification: documentation/planning, not implementation of security-critical changes. Budget: 120 minutes from session start, one initial independent review, at most one remediation, one narrow final verification; one concrete-diagnosis retry per worker/reviewer. Frozen review HEAD/base; no pushes during review. No new review controller; later owner clarification does not reset budget. ## Reuse Inspect local selector/routing/pin/admission/inventory/worker/UI first. Rich, OpenTelemetry, selected LiteLLM translators/tests and Langfuse/OpenRouter patterns are candidates only; implementation issues must prove exact revision/files/license/semantics/negative tests/security/maintenance before adoption. MI owns external fact collection; no parallel Router crawler. ## Links - Canonical repo: https://forgejo.creatidy.com/BioMedical-IT/scarcity-router - Prior completed architecture: #85, #146 / merged PR #147 - Existing operational program: #132; open #139, #140, #141, #165 - Registered Router gaps: #174-#186; exact results/order in the checkpoint comment and docs/roadmap.md - Kernel alignment: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/46; executable consumer #52, requirements #51, outcomes #58, budgets #56 - MI alignment: https://forgejo.creatidy.com/Creatidy/model-intelligence/issues/11; publication #13, production #15, identity/calibration #14, migration #18 and installed receipt #19 Creation and later clarification explicitly select this documentation task; they do not authorize execution of the registered future issues.
kilo commented 2026-10-04 23:11:08 +00:00
Author
Member
Copy link

Durable Audit Checkpoint

Correction after independent review694: the initial negative Console-consumer conclusion below has been replaced by actual OPEN Console #2, #3 and #12 coverage, already linked in Router #183 comment14299 before this checkpoint. The prior conclusion was inaccurate, not an owner decision; no duplicate task is needed.

Canonical base: 8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b; branch docs/173-creatidy-system-alignment. Change is 21 existing English documentation/agent files; no product implementation, public schemas, ratings, secrets, permissions or services changed. D-068 records agreed ownership/evidence direction; U-014 preserves the D-063 native coding/workspace conflict pending owner-reviewed migration.

Actual Registered Work

Issue Coherent result Order / dependency rationale
#174 Executable recommendation/admission/pin producer-consumer proof First integration prerequisite; dependencies #175/#178/#179; Kernel #52 consumer
#175 Rich monotone task/harness requirement mapping First quality prerequisite; Kernel #49/#51, MI #14 evidence/calibration
#176 Admitted MI consumption and safe catalog transition After #185 and MI #13/#15; Kernel #55 actual-used provenance
#177 Explicit local outcome import and cautious path analysis/calibration After #174/#184; Kernel #58 exporter; MI #17 sharing decision only
#178 Correct core resource-pin exact model/variant narrowing First correctness blocker; synthetic max -> medium in routing, admission max; no live call
#179 Correct gateway effort-from-variant and honest identity First correctness/UX blocker; unrelated-client fix need not wait native-lane migration
#180 Backend-native authority disposition and migration First affected-lane ownership/security prerequisite; Kernel #47/#50/#52; future implementation security_critical
#181 Version-specific compatibility and evidenced Responses subset After identity/requirements; Kernel #47/#52; no universal protocol guarantee
#182 Readable status/detail with JSON/pipe/unknown/no-color Independent operator lane, no Console prerequisite
#183 Router authorized reconnectable state/events Producer after #140/#179; parallel Kernel #57/MI #16; Console #2/#3 consume, #12 receives installed/browser proof
#184 Access-mode/pool/source-call economic enforceability Honest-guarantee prerequisite; Kernel #56 budget consumer; public MI offers not private billing proof
#185 Contract/artifact compatibility/migration Foundational; Kernel #62, MI #13/#18
#186 Uncovered public artifact/platform distribution/acceptance After #139/#141/#185; Kernel #60/#62, MI #18/#19 receipts; no release authority

Reused existing #139 TLS, #140 admin UX, #141 composed/live program acceptance and #165 concrete cancellation; no duplicate or silent closure. G01/G02/G03/G11 remain Kernel #47/#53, #49, #54, #59/#61 responsibilities. All new functional tasks remain OPEN, not integration receipts.

Kernel alignment #46 and MI alignment #11 counterpart criteria were read and linked; later review corrected the missed Console evidence already present on our issue. No other repository was mutated. Registration/green tests are not READY_FOR_LIVE_TASK.

Historical Validation and Review Scope

The first uv sync --only-dev and make check passed: 2674 tests OK/15 runtime probes skipped,619.426s; basedpyright0/0/0; diff whitespace clean. Subsequent exact-SHA gates and review outcomes belong in the delivery comments/PR. No inference/live task/deployment/service change; synthetic localhost harnesses only.

Original120minbudget from22:11Z: one fresh independent whole-PR/backlog review, at most one remediation and narrow final verification; no pushes during review. Documentation/planning classification; future security-critical implementation separately gated. Branch-protection read denied due admin permission; no requirements guessed or changed. This correction does not reset budget or pretend the initial review passed.

## Durable Audit Checkpoint **Correction after independent review694:** the initial negative Console-consumer conclusion below has been replaced by actual OPEN [Console #2](https://forgejo.creatidy.com/Creatidy/creatidy-console/issues/2), [#3](https://forgejo.creatidy.com/Creatidy/creatidy-console/issues/3) and [#12](https://forgejo.creatidy.com/Creatidy/creatidy-console/issues/12) coverage, already linked in Router #183 comment14299 before this checkpoint. The prior conclusion was inaccurate, not an owner decision; no duplicate task is needed. Canonical base: `8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b`; branch `docs/173-creatidy-system-alignment`. Change is 21 existing English documentation/agent files; no product implementation, public schemas, ratings, secrets, permissions or services changed. D-068 records agreed ownership/evidence direction; U-014 preserves the D-063 native coding/workspace conflict pending owner-reviewed migration. ## Actual Registered Work | Issue | Coherent result | Order / dependency rationale | | --- | --- | --- | | #174 | Executable recommendation/admission/pin producer-consumer proof | First integration prerequisite; dependencies #175/#178/#179; Kernel #52 consumer | | #175 | Rich monotone task/harness requirement mapping | First quality prerequisite; Kernel #49/#51, MI #14 evidence/calibration | | #176 | Admitted MI consumption and safe catalog transition | After #185 and MI #13/#15; Kernel #55 actual-used provenance | | #177 | Explicit local outcome import and cautious path analysis/calibration | After #174/#184; Kernel #58 exporter; MI #17 sharing decision only | | #178 | Correct core resource-pin exact model/variant narrowing | First correctness blocker; synthetic max -> medium in routing, admission max; no live call | | #179 | Correct gateway effort-from-variant and honest identity | First correctness/UX blocker; unrelated-client fix need not wait native-lane migration | | #180 | Backend-native authority disposition and migration | First affected-lane ownership/security prerequisite; Kernel #47/#50/#52; future implementation security_critical | | #181 | Version-specific compatibility and evidenced Responses subset | After identity/requirements; Kernel #47/#52; no universal protocol guarantee | | #182 | Readable status/detail with JSON/pipe/unknown/no-color | Independent operator lane, no Console prerequisite | | #183 | Router authorized reconnectable state/events | Producer after #140/#179; parallel Kernel #57/MI #16; Console #2/#3 consume, #12 receives installed/browser proof | | #184 | Access-mode/pool/source-call economic enforceability | Honest-guarantee prerequisite; Kernel #56 budget consumer; public MI offers not private billing proof | | #185 | Contract/artifact compatibility/migration | Foundational; Kernel #62, MI #13/#18 | | #186 | Uncovered public artifact/platform distribution/acceptance | After #139/#141/#185; Kernel #60/#62, MI #18/#19 receipts; no release authority | Reused existing #139 TLS, #140 admin UX, #141 composed/live program acceptance and #165 concrete cancellation; no duplicate or silent closure. G01/G02/G03/G11 remain Kernel #47/#53, #49, #54, #59/#61 responsibilities. All new functional tasks remain OPEN, not integration receipts. Kernel alignment #46 and MI alignment #11 counterpart criteria were read and linked; later review corrected the missed Console evidence already present on our issue. No other repository was mutated. Registration/green tests are not READY_FOR_LIVE_TASK. ## Historical Validation and Review Scope The first `uv sync --only-dev` and `make check` passed: 2674 tests OK/15 runtime probes skipped,619.426s; basedpyright0/0/0; diff whitespace clean. Subsequent exact-SHA gates and review outcomes belong in the delivery comments/PR. No inference/live task/deployment/service change; synthetic localhost harnesses only. Original120minbudget from22:11Z: one fresh independent whole-PR/backlog review, at most one remediation and narrow final verification; no pushes during review. Documentation/planning classification; future security-critical implementation separately gated. Branch-protection read denied due admin permission; no requirements guessed or changed. This correction does not reset budget or pretend the initial review passed.
kilo commented 2026-10-04 23:45:39 +00:00
Author
Member
Copy link

Frozen Delivery and Terminology Clarification

Documentation PR: BioMedical-IT/scarcity-router#187 (OPEN, unmerged).
Base: 8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b; HEAD: a57ed0c4e6154230961480acbadabcffacb8bd4a. Single issue-scoped documentation commit, 21 existing files, no merge commits or product implementation/schema/rating changes.

The owner's later naming instruction superseded the earlier explanation. Removed the unnecessary naming sentence in architecture and this mutable issue body; D-068 records real Creatidy Kernel and Scarcity Router names directly, not an alias, renamed product or new component. Classification for both corrected occurrences: removed as unnecessary; no Kernel-versus-Router guess. Complete committed exact and case/formatting git sweeps: zero matches, including hidden tracked workflows/context. All 21 open issue titles/descriptions and 19 current comments across 15 threads were inspected; #173 was the only matching mutable body and was subsequently reread clean. PR #170 description is clean, comments metadata0. No closed historical record or Git history rewritten; no historical quotation needed retention in inspected scope. This update and PR text do not reintroduce the removed term.

Final full make check after owner clarification: 2674 tests OK, 15 runtime probes skipped, 597.455s, built-in basedpyright0/0/0. Separate final basedpyright0/0/0, focused interface guardrails42OK, package artifact/isolated install checks allPASS, whitespace clean. No inference/live task or service/secret/permission changes.

Fresh independent reviewer dispatched through the native Task tool as distinct session ses_ef6b19e21ffeeMnBHQSLA5J1Ef, reviewing complete frozen PR + registered backlog, UX/terminology/evidence/ownership. No named model override requested; the tool supplies distinct session dispatch, not resolved model/runtime identity metadata, so model identity is RUNTIME_UNOBSERVABLE unless independent machine evidence becomes available. No pushes during review. One initial review, optional one remediation/narrow final verification; total original budget remains120min. Full final reviewer report will distinguish substantive exact-SHA verdict, formal Forgejo state, CI availability and open functional gaps.

## Frozen Delivery and Terminology Clarification Documentation PR: https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/pulls/187 (OPEN, unmerged). Base: `8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b`; HEAD: `a57ed0c4e6154230961480acbadabcffacb8bd4a`. Single issue-scoped documentation commit, 21 existing files, no merge commits or product implementation/schema/rating changes. The owner's later naming instruction superseded the earlier explanation. Removed the unnecessary naming sentence in architecture and this mutable issue body; D-068 records real Creatidy Kernel and Scarcity Router names directly, not an alias, renamed product or new component. Classification for both corrected occurrences: **removed as unnecessary**; no Kernel-versus-Router guess. Complete committed exact and case/formatting git sweeps: **zero matches**, including hidden tracked workflows/context. All 21 open issue titles/descriptions and 19 current comments across 15 threads were inspected; #173 was the only matching mutable body and was subsequently reread clean. PR #170 description is clean, comments metadata0. No closed historical record or Git history rewritten; no historical quotation needed retention in inspected scope. This update and PR text do not reintroduce the removed term. Final full `make check` after owner clarification: **2674 tests OK, 15 runtime probes skipped, 597.455s**, built-in basedpyright0/0/0. Separate final basedpyright0/0/0, focused interface guardrails42OK, package artifact/isolated install checks allPASS, whitespace clean. No inference/live task or service/secret/permission changes. Fresh independent reviewer dispatched through the native Task tool as distinct session `ses_ef6b19e21ffeeMnBHQSLA5J1Ef`, reviewing complete frozen PR + registered backlog, UX/terminology/evidence/ownership. No named model override requested; the tool supplies distinct session dispatch, not resolved model/runtime identity metadata, so model identity is **RUNTIME_UNOBSERVABLE** unless independent machine evidence becomes available. No pushes during review. One initial review, optional one remediation/narrow final verification; total original budget remains120min. Full final reviewer report will distinguish substantive exact-SHA verdict, formal Forgejo state, CI availability and open functional gaps.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
issue-246-authorized-receipt
issue-245-mi-startup
issue-226-administrator-ux
issue-183-observer-access
issue-183-event-acceptance
issue-183-internal-events
issue-183-resource-state
issue-242-secure-bootstrap
issue-238-mi-server
issue-239-architecture-reconciliation
issue-224-certificate-lifecycle
issue-224-origin-bound-worker
issue-224-worker-ca-trust
issue-234-evidenced-resources
issue-186-installed-lifecycle
issue-186-ghcr-distribution
issue-225-cancel-paths
issue-228-backlog-disposition
issue-222-active-mi
issue-176-mi-consumer
issue-185-contract-conformance
issue-219-project-security-audit
issue-181-responses-subset
issue-214-claude-subscription
issue-205-review-result-recovery
issue-174-executable-contract
issue-215-conversational-review
issue-210-d069-review-governance
issue-212-d069a-bootstrap
issue-202-dependency-eligibility
issue-184-strict-no-payg
issue-175-kernel-requirements
issue-180-native-authority-boundary
issue-182-readable-status
issue-195-post-selection-gates
issue-179-catalog-effort
issue-178-exact-target-pin
issue-190-workflow-self-remediation
task/168-capacity-controlled-home
fix/143-scenario11-cancel-race
policy/zai-model-governance-campaign
main
No results found.
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
P1
Owner-declared highest explicit implementation priority (loop ordering rank)

  
P2
Required product and integration work

  
P3
Deferred or producer-dependent work

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
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.

Dependencies

No dependencies set.

Reference
Creatidy/scarcity-router#173
No description provided.