Reconcile standalone and Foundry architecture and deployment guidance #239

New issue

Closed

opened 2026-10-31 22:06:49 +00:00 by kilo · 1 comment

kilo commented

2026-10-31 22:06:49 +00:00

Member

Goal

Reconcile current Scarcity Router architecture, transport guidance, repository location and standalone packaging with the owner's 2026-10-31 architecture directive.

Why

Foundry integration and #224 deployment investigation expose stale product-ownership, D-084 and Docker transport statements. The examples/ Compose build context is incorrect. This issue is not a replacement for #224's implementation obligations or review capacity.

Scope

Update material current-facing architecture, security, product, roadmap, release and operational references; record a prospective decision distinguishing the owner-directed TLS deployment direction from the still-accepted #224 Tier-B requirement pending formal disposition. Preserve historical decisions and the independent standalone server/optional worker. Correct and verify standalone Compose build context.

Acceptance Criteria

Document Router/MI/Kernel/Console/Foundry ownership and standalone operation without invented runtime dependencies.
State loopback, supported host namespace, bridge and cross-host transport accurately; do not implement non-loopback plaintext or claim unverified acceptance.
Preserve #224 obligations and review history; identify any pending Tier-B retirement decision.
Correct migrated canonical operational references and stale D-084 claims; retain historical provenance.
Validate documentation, package/build and full repository gates, and obtain fresh independent review at exact refs assessing security, standalone compatibility, UX and prior requirements.

Constraints

No downstream repository changes, release, deployment, merge without authority, host-security controls or extra daemons. No use of #224 exceptional review ordinals. Preserve existing owner changes.

Links

Owner directive 2026-10-31; #224, #227, #238; D-056, D-078, D-081, D-083, D-084.

## Goal Reconcile current Scarcity Router architecture, transport guidance, repository location and standalone packaging with the owner's 2026-10-31 architecture directive. ## Why Foundry integration and #224 deployment investigation expose stale product-ownership, D-084 and Docker transport statements. The `examples/` Compose build context is incorrect. This issue is not a replacement for #224's implementation obligations or review capacity. ## Scope Update material current-facing architecture, security, product, roadmap, release and operational references; record a prospective decision distinguishing the owner-directed TLS deployment direction from the still-accepted #224 Tier-B requirement pending formal disposition. Preserve historical decisions and the independent standalone server/optional worker. Correct and verify standalone Compose build context. ## Acceptance Criteria - Document Router/MI/Kernel/Console/Foundry ownership and standalone operation without invented runtime dependencies. - State loopback, supported host namespace, bridge and cross-host transport accurately; do not implement non-loopback plaintext or claim unverified acceptance. - Preserve #224 obligations and review history; identify any pending Tier-B retirement decision. - Correct migrated canonical operational references and stale D-084 claims; retain historical provenance. - Validate documentation, package/build and full repository gates, and obtain fresh independent review at exact refs assessing security, standalone compatibility, UX and prior requirements. ## Constraints No downstream repository changes, release, deployment, merge without authority, host-security controls or extra daemons. No use of #224 exceptional review ordinals. Preserve existing owner changes. ## Links Owner directive 2026-10-31; #224, #227, #238; D-056, D-078, D-081, D-083, D-084.

kilo commented

2026-10-31 22:17:50 +00:00

Author

Member

Phase A in progress on isolated checkout/branch issue-239-architecture-reconciliation, based on freshly fetched develop 209f7d39f3ecebbd1b98b11d7c44c63192fe50a4. Existing #224 investigation checkout and its uncommitted Compose correction remain untouched. Proposed D-085 preserves #224 Tier-B as an accepted but unimplemented obligation pending explicit formal disposition; bridge deployment guidance requires verified TLS. Compose config resolves to the repository root and an actual image build succeeded; package-check and basedpyright passed. Full validation and independent security/architecture review remain pending; no PR or integration is claimed.

Phase A in progress on isolated checkout/branch `issue-239-architecture-reconciliation`, based on freshly fetched `develop` `209f7d39f3ecebbd1b98b11d7c44c63192fe50a4`. Existing #224 investigation checkout and its uncommitted Compose correction remain untouched. Proposed D-085 preserves #224 Tier-B as an accepted but unimplemented obligation pending explicit formal disposition; bridge deployment guidance requires verified TLS. Compose config resolves to the repository root and an actual image build succeeded; package-check and basedpyright passed. Full validation and independent security/architecture review remain pending; no PR or integration is claimed.

kilo referenced this issue

2026-10-31 22:40:32 +00:00

Reconcile standalone and Foundry deployment architecture (#239) #240