Prove public local installation, trusted connections and compatible upgrades #11

New issue

Open

opened 2026-10-04 23:04:49 +00:00 by kilo · 0 comments

kilo commented

2026-10-04 23:04:49 +00:00

Member

Goal

Owner: Console packaging/operations. Deliver a public local installation and safe upgrade path without private services or secrets in artifacts.

Why / Current Evidence

A static scaffold build is not a supported product install. Console seed d6468f3 has only public license/README. Initial development host Node24.19.0/npm11.17.0/Linux-WSL; producer baseline Kernel eb4f4a2956712bfaf39a3271e1523e7f77a91e26, Router 8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b, MI fb7299810fdc4612d4e0559465faef571662c6ef. Source sections 2,3,5,8-10,12; G09/G11/G13.

Scope / Non-Goals

Supported static/session artifact choice, user-local connection/preferences, explicit trusted instance/schema discovery, install/update/rollback and settings/projection migrations, reviewed browser/platform matrix. No four mandatory services, private onprem installer, Kubernetes/broker, provider configuration migration, credentials generation or automatic deployment.

Acceptance Criteria

Clean public installation outside source checkout with licensed artifact, no workspace-specific paths/private dependencies/embedded secrets; Router-only and unconfigured optional modules work honestly.
Reject unsupported security/authority versions and unsafe endpoints; retain user settings across upgrade or explicit backed-up migration, recover from interrupted update and incompatible cache.
Uninstall/cache clearing cannot cancel tasks or alter producer state; define private metadata retention/export and revocation cleanup.
Linux/WSL development and supported browser coverage proved separately from producer native filesystem/platform support.
Production local server/auth boundaries settled by contract study; dev/preview loopback tooling not advertised as hardened remote hosting.

Constraints

Exact origin/TLS/session trust, privacy/reporting policy, dependency/notice review and compatibility matrix required. Reuse standard web packaging/secure serving mechanisms; no custom installer/platform when adequate exists. Priority P2 after contract/auth decisions and feature proofs. Any installed live connection/promotion/publication/deployment requires separate owner scope; registration authorizes none.

Links / Dependencies

Parent #1; Console #2/#3/#7 and validation/governance/conditional-surface issues. Kernel Creatidy/creatidy-kernel#62; Router BioMedical-IT/scarcity-router#185; MI Creatidy/model-intelligence#18 and /issues/19.

## Goal Owner: Console packaging/operations. Deliver a public local installation and safe upgrade path without private services or secrets in artifacts. ## Why / Current Evidence A static scaffold build is not a supported product install. Console seed d6468f3 has only public license/README. Initial development host Node24.19.0/npm11.17.0/Linux-WSL; producer baseline Kernel eb4f4a2956712bfaf39a3271e1523e7f77a91e26, Router 8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b, MI fb7299810fdc4612d4e0559465faef571662c6ef. Source sections 2,3,5,8-10,12; G09/G11/G13. ## Scope / Non-Goals Supported static/session artifact choice, user-local connection/preferences, explicit trusted instance/schema discovery, install/update/rollback and settings/projection migrations, reviewed browser/platform matrix. No four mandatory services, private onprem installer, Kubernetes/broker, provider configuration migration, credentials generation or automatic deployment. ## Acceptance Criteria - Clean public installation outside source checkout with licensed artifact, no workspace-specific paths/private dependencies/embedded secrets; Router-only and unconfigured optional modules work honestly. - Reject unsupported security/authority versions and unsafe endpoints; retain user settings across upgrade or explicit backed-up migration, recover from interrupted update and incompatible cache. - Uninstall/cache clearing cannot cancel tasks or alter producer state; define private metadata retention/export and revocation cleanup. - Linux/WSL development and supported browser coverage proved separately from producer native filesystem/platform support. - Production local server/auth boundaries settled by contract study; dev/preview loopback tooling not advertised as hardened remote hosting. ## Constraints Exact origin/TLS/session trust, privacy/reporting policy, dependency/notice review and compatibility matrix required. Reuse standard web packaging/secure serving mechanisms; no custom installer/platform when adequate exists. Priority P2 after contract/auth decisions and feature proofs. Any installed live connection/promotion/publication/deployment requires separate owner scope; registration authorizes none. ## Links / Dependencies Parent #1; Console #2/#3/#7 and validation/governance/conditional-surface issues. Kernel https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/62; Router https://forgejo.creatidy.com/BioMedical-IT/scarcity-router/issues/185; MI https://forgejo.creatidy.com/Creatidy/model-intelligence/issues/18 and /issues/19.

kilo added a new dependency

2026-10-04 23:05:48 +00:00

#2 Define supported producer reads and the browser authentication boundary

kilo added a new dependency

2026-10-04 23:05:48 +00:00

#12 Establish producer conformance, browser and security acceptance with explicit live gates

~~kilo referenced this issue 2026-10-04 23:26:31 +00:00~~

Bootstrap Creatidy Console: architecture, repository foundation and integration backlog #15

~~kilo referenced this issue 2026-10-04 23:27:33 +00:00~~

Bootstrap Creatidy Console: product architecture, repository foundation and integration backlog #1

kilo referenced this issue

2026-10-04 23:53:23 +00:00