Creatidy/model-intelligence
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Deliver public MI installation, knowledge updates and compatibility migrations #18

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

Parent: #11. Owner: Model Intelligence; consumers: Router/operators. G13, G06, G08. Source: shared architecture v1.0 (2026-10-04), supplied section bundle 1–5, 7–10, 12–18; MI brief §4 snapshot/availability/operator and §5 G13. Reference/hash availability in #11.

Problem and Evidence

At develop fb7299810fdc4612d4e0559465faef571662c6ef, pyproject.toml, uv.lock, Makefile and bootstrap tests establish a typed Python packaging foundation; #9/PR #10 separately reported installed-wheel smoke for the synthetic proof. They do not demonstrate a public maintained product installation/update path, stored knowledge compatibility or source/configuration migrations. No deployed MI service is inferred.

Result and Acceptance

  1. After #12 value/rights and #13/#14 contracts plus #15 source operations, deliver reproducible public installation and knowledge-artifact distribution using the smallest existing mechanism. No private creatidy-onprem dependency; dependencies on public modules are allowed. Do not mandate four daemons/shared DB/Kubernetes or add paid core SaaS.
  2. Installed/built package and artifact tests exercise documented supported paths outside the source checkout, exact contract/source versions, permitted provenance/NOTICE and dependency/maintenance responsibilities. Document actual runnable commands only; unknown release mechanism remains a decision until verified.
  3. Exercise upgrade and downgrade/rollback, unsupported artifact/package combinations, interrupted update, partial/corrupt data, source-schema change, old stored configuration/data and unavailable network. Migrate or fail safely with actionable diagnostics, without silently losing history, inventing identity or publishing incomplete knowledge. Existing accepted config/data must have explicit preservation/rejection rules; do not invent backwards compatibility for nonexistent formats.
  4. Define version/deprecation and support policy based on actual contract consumers, integrity/completeness and approved source rights, retaining last successful artifact for Router-owned fallback. Document operator install/update/recovery and maintenance responsibilities; no arbitrary TTL or mandatory PKI.
  5. Compare existing packaging/update/versioned-source and migration mechanisms (local/upstream) at exact revisions, semantic guarantees, licenses, adverse tests, dependencies and maintenance; justify any custom machinery. Security review covers untrusted artifacts, provenance, parser exposure and no secrets/account telemetry in public packages.

Dependencies, Priority and Permissions

#13 establishes publication/compatibility; #15 source/schema behavior; #16 operator facts; #14 identity mapping. Integrated user acceptance is separately tracked under #11 after these deliveries. Producer owns package/artifact/state; Router owns consumption policy and its configuration migrations. Do not duplicate consumer implementation here.
Priority P2: professional distribution/migration is required but depends on truthful product/contract/source evidence. Actual release/deploy/package-publishing, service access, effects or inference require separate owner authorization; this registration only records the work. Offline installed-package tests need no inference.

Parent: #11. Owner: Model Intelligence; consumers: Router/operators. G13, G06, G08. Source: shared architecture v1.0 (2026-10-04), supplied section bundle 1–5, 7–10, 12–18; MI brief §4 snapshot/availability/operator and §5 G13. Reference/hash availability in #11. ## Problem and Evidence At develop `fb7299810fdc4612d4e0559465faef571662c6ef`, `pyproject.toml`, `uv.lock`, `Makefile` and bootstrap tests establish a typed Python packaging foundation; #9/PR #10 separately reported installed-wheel smoke for the synthetic proof. They do not demonstrate a public maintained product installation/update path, stored knowledge compatibility or source/configuration migrations. No deployed MI service is inferred. ## Result and Acceptance 1. After #12 value/rights and #13/#14 contracts plus #15 source operations, deliver reproducible public installation and knowledge-artifact distribution using the smallest existing mechanism. No private creatidy-onprem dependency; dependencies on public modules are allowed. Do not mandate four daemons/shared DB/Kubernetes or add paid core SaaS. 2. Installed/built package and artifact tests exercise documented supported paths outside the source checkout, exact contract/source versions, permitted provenance/NOTICE and dependency/maintenance responsibilities. Document actual runnable commands only; unknown release mechanism remains a decision until verified. 3. Exercise upgrade and downgrade/rollback, unsupported artifact/package combinations, interrupted update, partial/corrupt data, source-schema change, old stored configuration/data and unavailable network. Migrate or fail safely with actionable diagnostics, without silently losing history, inventing identity or publishing incomplete knowledge. Existing accepted config/data must have explicit preservation/rejection rules; do not invent backwards compatibility for nonexistent formats. 4. Define version/deprecation and support policy based on actual contract consumers, integrity/completeness and approved source rights, retaining last successful artifact for Router-owned fallback. Document operator install/update/recovery and maintenance responsibilities; no arbitrary TTL or mandatory PKI. 5. Compare existing packaging/update/versioned-source and migration mechanisms (local/upstream) at exact revisions, semantic guarantees, licenses, adverse tests, dependencies and maintenance; justify any custom machinery. Security review covers untrusted artifacts, provenance, parser exposure and no secrets/account telemetry in public packages. ## Dependencies, Priority and Permissions #13 establishes publication/compatibility; #15 source/schema behavior; #16 operator facts; #14 identity mapping. Integrated user acceptance is separately tracked under #11 after these deliveries. Producer owns package/artifact/state; Router owns consumption policy and its configuration migrations. Do not duplicate consumer implementation here. Priority P2: professional distribution/migration is required but depends on truthful product/contract/source evidence. Actual release/deploy/package-publishing, service access, effects or inference require separate owner authorization; this registration only records the work. Offline installed-package tests need no inference.
kilo commented 2026-10-04 22:22:51 +00:00
Author
Member
Copy link

Dependencies: #12 accepted lawful source scope; #13 version/publication conformance; #14 mappings; #15 complete production source/publication; #16 operator diagnostics. #19 is separate installed whole-path acceptance. Actual Router consumption/migration owner BioMedical-IT/scarcity-router#173, Kernel references/migrations Creatidy/creatidy-kernel#46. Router #139 TLS and #141 install/client acceptance (BioMedical-IT/scarcity-router#139, BioMedical-IT/scarcity-router#141) cover Router-only slices, not MI distribution or permission to publish/deploy.

Dependencies: #12 accepted lawful source scope; #13 version/publication conformance; #14 mappings; #15 complete production source/publication; #16 operator diagnostics. #19 is separate installed whole-path acceptance. Actual Router consumption/migration owner https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/173, Kernel references/migrations https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/46. Router #139 TLS and #141 install/client acceptance (https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/139, https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/141) cover Router-only slices, not MI distribution or permission to publish/deploy.
kilo commented 2026-10-04 22:30:36 +00:00
Author
Member
Copy link

Final concrete migration/compatibility consumer counterparts: Router BioMedical-IT/scarcity-router#176 (MI artifact adoption/catalog migration) and BioMedical-IT/scarcity-router#181 (versioned protocol compatibility). Kernel producer/consumer version/reference handling remains Creatidy/creatidy-kernel#46. #18 owns MI public installed delivery/update/data-source compatibility, #19 composed receipt; these scoped matches are not current release/deployment evidence.

Final concrete migration/compatibility consumer counterparts: Router https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/176 (MI artifact adoption/catalog migration) and https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/181 (versioned protocol compatibility). Kernel producer/consumer version/reference handling remains https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/46. #18 owns MI public installed delivery/update/data-source compatibility, #19 composed receipt; these scoped matches are not current release/deployment evidence.
kilo commented 2026-10-04 22:49:07 +00:00
Author
Member
Copy link

Review correction: actual Kernel public compatibility/install/migration consumer Creatidy/creatidy-kernel#62 links MI #18 and owns outside-checkout installation, MI/native/gateway compatibility and safe recoverable state/profile migration preserving immutable IDs/history. Kernel installed receipt Creatidy/creatidy-kernel#60 links MI #18/#19. These supersede earlier parent-only discovery. Each producer/consumer owns its own data migrations; MI #18 does not implement Kernel state or authorize a release/deploy.

Review correction: actual Kernel public compatibility/install/migration consumer https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/62 links MI #18 and owns outside-checkout installation, MI/native/gateway compatibility and safe recoverable state/profile migration preserving immutable IDs/history. Kernel installed receipt https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/60 links MI #18/#19. These supersede earlier parent-only discovery. Each producer/consumer owns its own data migrations; MI #18 does not implement Kernel state or authorize a release/deploy.
kilo commented 2026-10-04 22:52:28 +00:00
Author
Member
Copy link

Additional concrete G13 counterpart match: Router BioMedical-IT/scarcity-router#185 owns cross-product contract/artifact upgrade refusal/migration (including Router #176 MI adoption and pin/event families); BioMedical-IT/scarcity-router#186 owns Router public artifact/platform distribution acceptance. These are producer-owned plans, not release evidence or MI installation implementation. Coordinate with MI #18 and Kernel #62; keep per-product data/history/authority boundaries.

Additional concrete G13 counterpart match: Router https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/185 owns cross-product contract/artifact upgrade refusal/migration (including Router #176 MI adoption and pin/event families); https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/186 owns Router public artifact/platform distribution acceptance. These are producer-owned plans, not release evidence or MI installation implementation. Coordinate with MI #18 and Kernel #62; keep per-product data/history/authority boundaries.
kilo commented 2026-10-04 23:24:34 +00:00
Author
Member
Copy link

Owner-Requested Package Metadata Disposition

Read-only owner verification on 2026-10-04 confirmed that current canonical MI PR #20 remains at 4381d242f072a01b7aa6fae6c1114c1a42abc8b1 over develop fb7299810fdc4612d4e0559465faef571662c6ef. At this revision pyproject.toml:8 still contains description = "Public AI ecosystem intelligence: repository bootstrap". That description is stale relative to the integrated synthetic R2 proof; it is not a claim that README/AGENTS or the architecture should revert to bootstrap-only status.

Explicit disposition under the owner's allowed no-edit alternative: retain the frozen six-file documentation/rules delta of #11/PR #20 and leave packaging metadata unchanged in that PR. #11 does not expressly select a packaging/installed-metadata edit, and its completed delivery/review explicitly recorded packaging as unchanged. Do not silently broaden that reviewed delivery or treat this known wording inconsistency as current product-readiness evidence.

The correction belongs to this issue's existing installed/built-package and truthful operator-documentation acceptance (criteria 2 and 4): reconcile package summary/README with the actual accepted synthetic-proof/product status and verify installed distribution metadata. A corrected summary must not imply a real-source value proof, published service, working MI–Router integration or product GO. If implemented as a separate owner-selected metadata-only correction, its receipt must include make check, built/installed packaging validation and a fresh exact-HEAD review; no invented new schema/API or inference is needed.

This note records a known metadata acceptance item, not selection or commencement of #18, no PR/source/config/lock edit and no additional functional authorization. The next substantive MI gate remains #12 real-source A/B/C value and rights proof; #15 production acquisition remains gated by accepted #12–#14. The current session does not merge, release, deploy or start any functional issue.

## Owner-Requested Package Metadata Disposition Read-only owner verification on 2026-10-04 confirmed that current canonical MI PR #20 remains at `4381d242f072a01b7aa6fae6c1114c1a42abc8b1` over develop `fb7299810fdc4612d4e0559465faef571662c6ef`. At this revision `pyproject.toml:8` still contains `description = "Public AI ecosystem intelligence: repository bootstrap"`. That description is stale relative to the integrated synthetic R2 proof; it is not a claim that README/AGENTS or the architecture should revert to bootstrap-only status. Explicit disposition under the owner's allowed no-edit alternative: retain the frozen six-file documentation/rules delta of #11/PR #20 and leave packaging metadata unchanged in that PR. #11 does not expressly select a packaging/installed-metadata edit, and its completed delivery/review explicitly recorded packaging as unchanged. Do not silently broaden that reviewed delivery or treat this known wording inconsistency as current product-readiness evidence. The correction belongs to this issue's existing installed/built-package and truthful operator-documentation acceptance (criteria 2 and 4): reconcile package summary/README with the actual accepted synthetic-proof/product status and verify installed distribution metadata. A corrected summary must not imply a real-source value proof, published service, working MI–Router integration or product GO. If implemented as a separate owner-selected metadata-only correction, its receipt must include make check, built/installed packaging validation and a fresh exact-HEAD review; no invented new schema/API or inference is needed. This note records a known metadata acceptance item, not selection or commencement of #18, no PR/source/config/lock edit and no additional functional authorization. The next substantive MI gate remains #12 real-source A/B/C value and rights proof; #15 production acquisition remains gated by accepted #12–#14. The current session does not merge, release, deploy or start any functional issue.
kilo commented 2026-10-09 04:22:24 +00:00
Author
Member
Copy link

Selected through fresh full canonical /loop queue after verified #12-#16 deliveries. Candidate PR #36: base23977d895cc58dca11e6aeaa81c8b9ffa97a9361, HEAD56a7f3ae5447e647053b514385fb3165afd9cab8, ordinary branch/normal owner commit and push.

Added packaged installation/support policy and repository-owned outside-checkout distribution lifecycle verifier; reused unchanged uv_build0.9.30, /1-to-/2 explicit import, retained atomic publication/history, #16 diagnosis and original negative tests. No production updater/store/API/dependency/lock/private/foreign changes.

Sanitized make check PASS172, Ruff52formatted, basedpyright0, locked/whitespace. Outside-checkout offline current/direct/sdist-rebuilt byte-identical wheels, pinned #13/#15 installs and legacy/current/producer/downgrade scenarios PASS; 46 installed source/publication/operator/portable tests PASS, complete copied artifact validation/partial refusal, real CLI parity, packaged support/NOTICE and malformed wheel refusal. Frozen clean-HEAD rerun is in progress before first fresh independent whole-PR review. Review counter0; historical counters unchanged.

Existing Summary was already corrected by #15; added installed metadata regression instead of restoring historical bootstrap language. Backend/actual dual license verified at uv ea4560831e503c6ce34d18739476a71ac6e9a9de; selected models.dev MIT NOTICE retained, no upstream code copied.

Issue stays open. Candidate/green tests are not independent approval, package publication/release/deployment, product GO, authentic publisher trust or actual Router/Console adoption. #19 remains separate installed consumer acceptance. Continue exact frozen whole-PR review/remediation, conditional supported merge/verified closure, then full SELECT.

Selected through fresh full canonical /loop queue after verified #12-#16 deliveries. Candidate PR #36: base23977d895cc58dca11e6aeaa81c8b9ffa97a9361, HEAD56a7f3ae5447e647053b514385fb3165afd9cab8, ordinary branch/normal owner commit and push. Added packaged installation/support policy and repository-owned outside-checkout distribution lifecycle verifier; reused unchanged uv_build0.9.30, /1-to-/2 explicit import, retained atomic publication/history, #16 diagnosis and original negative tests. No production updater/store/API/dependency/lock/private/foreign changes. Sanitized make check PASS172, Ruff52formatted, basedpyright0, locked/whitespace. Outside-checkout offline current/direct/sdist-rebuilt byte-identical wheels, pinned #13/#15 installs and legacy/current/producer/downgrade scenarios PASS; 46 installed source/publication/operator/portable tests PASS, complete copied artifact validation/partial refusal, real CLI parity, packaged support/NOTICE and malformed wheel refusal. Frozen clean-HEAD rerun is in progress before first fresh independent whole-PR review. Review counter0; historical counters unchanged. Existing Summary was already corrected by #15; added installed metadata regression instead of restoring historical bootstrap language. Backend/actual dual license verified at uv ea4560831e503c6ce34d18739476a71ac6e9a9de; selected models.dev MIT NOTICE retained, no upstream code copied. Issue stays open. Candidate/green tests are not independent approval, package publication/release/deployment, product GO, authentic publisher trust or actual Router/Console adoption. #19 remains separate installed consumer acceptance. Continue exact frozen whole-PR review/remediation, conditional supported merge/verified closure, then full SELECT.
kilo commented 2026-10-09 04:28:52 +00:00
Author
Member
Copy link

Completed #18's accepted offline MI-owned distribution/update/compatibility scope through merged PR #36.

Reviewed base23977d895cc58dca11e6aeaa81c8b9ffa97a9361; approved HEAD56a7f3ae5447e647053b514385fb3165afd9cab8. Canonical merge938f4160493359f9795c3bda081b065afac96b16 at2026-10-09T04:27:39Z. Verified exact parents, approved ancestry and identical tree8f03b93bfb4cabb7cd6a6c6fd5e09f3b6b8f3b4f. Clean ordinary develop fast-forward, branch/history preserved.

Acceptance:

  • AC1/2: public source-build/local-wheel and exact-byte directory copy, packaged INSTALLATION.md available outside checkout; current/direct/sdist-rebuilt wheels byte-identical; actual installed Summary/support/typing/LICENSE/NOTICE/no runtime dependencies and CLI entry point verified.
  • AC3: exact historical #13 and #15 packages installed around current package. Legacy /1 creation, idempotent /1-to-/2 import with original bytes, complete copy and partial/digest refusal, compatible historical producer reading, old-package /2 rejection with saved /1 readability and unchanged store passed. Reused 46 installed original source/publication/operator/portable tests cover schema/config changes, unavailable network, partial/corrupt data, interrupted update, preserved history, lifecycle and bounded diagnostics. Malformed wheel refusal retains installed support/working CLI. No speculative config format or history-losing rollback.
  • AC4/5: package/source/wheel versus working-wire/adapter identity, decoder-versus-active-store distinctions, support/deprecation/backup/recovery/one-writer/maintenance policy documented. Pinned local #13/#15/#16 mechanisms and uv0.9.30 backend/actual MIT OR Apache-2.0/source tests independently verified; no custom updater/store or copied upstream implementation. Selected models.dev MIT NOTICE retained, raw official pages excluded.

Fresh independent ordinal1 taskses_ee1191a44ffeeuUXjL1kQrtYXT returned exact-HEAD/base APPROVE, findings[], limitations[]. Count1/10, all earlier deliveries/counters retained. Reviewer inspected whole six-file delta, independently ran installed suite and verified package inventory/source licenses.

Integrated env -i PATH=/home/adrian/.local/bin:/usr/local/bin:/usr/bin:/bin HOME=/tmp/kilo/mi15-validation/home XDG_CACHE_HOME=/tmp/kilo/mi15-validation/cache UV_CACHE_DIR=/tmp/kilo/mi15-validation/cache/uv TMPDIR=/tmp/kilo/mi15-validation/tmp UV_OFFLINE=1 UV_PYTHON_DOWNLOADS=never make check: PASS172, Ruff52formatted/lint, basedpyright0, locked/whitespace. Same environment .venv/bin/python -I -B tests/verify_distribution.py /tmp/kilo/mi18-integrated-938f416 --uv-cache /tmp/kilo/mi15-validation/cache/uv: PASS four installed modes, 46 tests, three identical current wheels, real CLI parity and copied artifact/refusal. Receipt records clean merge HEAD, uv0.9.30/Python3.12/backend0.9.30 and exact wheel SHA2561ca0b6a0d0e99a5df4a75c66b625f9433553afda09f6b5928be574369a29d019; same as reviewed wheel.

This is no registry publication/release/deployment, actual Router/Kernel/Console adoption, source authenticity/transport guarantee, private intake, inference or product GO. #19 remains separate actual installed consumer acceptance; #17 REJECT preserved. Verified integrated acceptance permits closing #18, then fresh exhaustive canonical SELECT.

Completed #18's accepted offline MI-owned distribution/update/compatibility scope through merged PR #36. Reviewed base23977d895cc58dca11e6aeaa81c8b9ffa97a9361; approved HEAD56a7f3ae5447e647053b514385fb3165afd9cab8. Canonical merge938f4160493359f9795c3bda081b065afac96b16 at2026-10-09T04:27:39Z. Verified exact parents, approved ancestry and identical tree8f03b93bfb4cabb7cd6a6c6fd5e09f3b6b8f3b4f. Clean ordinary develop fast-forward, branch/history preserved. Acceptance: - AC1/2: public source-build/local-wheel and exact-byte directory copy, packaged INSTALLATION.md available outside checkout; current/direct/sdist-rebuilt wheels byte-identical; actual installed Summary/support/typing/LICENSE/NOTICE/no runtime dependencies and CLI entry point verified. - AC3: exact historical #13 and #15 packages installed around current package. Legacy /1 creation, idempotent /1-to-/2 import with original bytes, complete copy and partial/digest refusal, compatible historical producer reading, old-package /2 rejection with saved /1 readability and unchanged store passed. Reused 46 installed original source/publication/operator/portable tests cover schema/config changes, unavailable network, partial/corrupt data, interrupted update, preserved history, lifecycle and bounded diagnostics. Malformed wheel refusal retains installed support/working CLI. No speculative config format or history-losing rollback. - AC4/5: package/source/wheel versus working-wire/adapter identity, decoder-versus-active-store distinctions, support/deprecation/backup/recovery/one-writer/maintenance policy documented. Pinned local #13/#15/#16 mechanisms and uv0.9.30 backend/actual MIT OR Apache-2.0/source tests independently verified; no custom updater/store or copied upstream implementation. Selected models.dev MIT NOTICE retained, raw official pages excluded. Fresh independent ordinal1 taskses_ee1191a44ffeeuUXjL1kQrtYXT returned exact-HEAD/base APPROVE, findings[], limitations[]. Count1/10, all earlier deliveries/counters retained. Reviewer inspected whole six-file delta, independently ran installed suite and verified package inventory/source licenses. Integrated `env -i PATH=/home/adrian/.local/bin:/usr/local/bin:/usr/bin:/bin HOME=/tmp/kilo/mi15-validation/home XDG_CACHE_HOME=/tmp/kilo/mi15-validation/cache UV_CACHE_DIR=/tmp/kilo/mi15-validation/cache/uv TMPDIR=/tmp/kilo/mi15-validation/tmp UV_OFFLINE=1 UV_PYTHON_DOWNLOADS=never make check`: PASS172, Ruff52formatted/lint, basedpyright0, locked/whitespace. Same environment `.venv/bin/python -I -B tests/verify_distribution.py /tmp/kilo/mi18-integrated-938f416 --uv-cache /tmp/kilo/mi15-validation/cache/uv`: PASS four installed modes, 46 tests, three identical current wheels, real CLI parity and copied artifact/refusal. Receipt records clean merge HEAD, uv0.9.30/Python3.12/backend0.9.30 and exact wheel SHA2561ca0b6a0d0e99a5df4a75c66b625f9433553afda09f6b5928be574369a29d019; same as reviewed wheel. This is no registry publication/release/deployment, actual Router/Kernel/Console adoption, source authenticity/transport guarantee, private intake, inference or product GO. #19 remains separate actual installed consumer acceptance; #17 REJECT preserved. Verified integrated acceptance permits closing #18, then fresh exhaustive canonical SELECT.
kilo closed this issue 2026-10-09 04:28:57 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
issue-47-terminal-bench-evidence-isolated
issue-45-coding-benchmark-evidence
issue-43-zai-source-refresh
issue-19-installed-router
docs/conversational-review-policy
issue-18-public-distribution
issue-16-offline-operator-contract
issue-15-public-evidence-producer
issue-17-sharing-decision
issue-14-status-consistency
issue-14-capability-boundary
issue-29-post-selection-gates
issue-13-completion-docs
issue-13-publication-contract
issue-12-post-merge-docs
issue-12-real-source-value
workflow-loop-self-remediation
issue-9-knowledge-effective
issue-7-explicit-lineage
issue-3-temporal-proof
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.

Dependencies

No dependencies set.

Reference
Creatidy/model-intelligence#18
No description provided.