Foundations design: one Host model, runtime and event route #92
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Design-only foundations job requested by the owner. Worktree: /mnt/hdd/infraternal/wt-lp/foundations-design; branch: detached HEAD at dev; base/head:
851d502909.Scope: read-only source investigation and compact design of the Host aggregate, unified infraternal-agent v1 transport, authoritative events/cache, provider cutover, fault tests and independently mergeable milestones. Deliverables: /mnt/hdd/infraternal/jobs/foundations-design/design.md and questions.md. No product commits, pushes, deployment or subjobs.
Read CLAUDE.md, DECISIONS.md (especially §§31–45), DESIGN, PLAN and UI. The job's explicit no-subjobs/read-only instructions govern this investigation. Code graph is being built outside the worktree in the job directory. Current production failures and in-flight one-add-host/connect-errors/install-single-source jobs will be treated as migration inputs.
Design-only foundations job requested by the owner. Worktree: /mnt/hdd/infraternal/wt-lp/foundations-design; branch: detached HEAD at dev; base/head:
851d502909.Scope: read-only source investigation and compact design of the Host aggregate, unified infraternal-agent v1 transport, authoritative events/cache, provider cutover, fault tests and independently mergeable milestones. Deliverables: /mnt/hdd/infraternal/jobs/foundations-design/design.md and questions.md. No product commits, pushes, deployment or subjobs.
Read CLAUDE.md, DECISIONS.md (especially §§31–45), DESIGN, PLAN and UI. The job's explicit no-subjobs/read-only instructions govern this investigation. Code graph is being built outside the worktree in the job directory. Current production failures and in-flight one-add-host/connect-errors/install-single-source jobs will be treated as migration inputs.
Current-head evidence (
851d502909):Design choices: one Host reducer with versioned connection and explicit execution-owner bindings; bootstrap records operation evidence, not editable connection truth; transport/SSH/provider health and inventory completeness remain separate from lifecycle. Embedded and mTLS paths share v1 frame actors, with only transport admission differing. Events are emitted after atomic publication; gaps and old epochs cannot revive completeness. SQLite-backed cache pages and globally bounded staging prevent 500 host-local maxima from becoming 500 allocations.
DECISIONS §§33–35 supersede the stale deployment/Postgres/polling descriptions in DESIGN/PLAN/UI. Self-install and mesh-auth work has evolved since the arch-review head; #72/#73 are not claimed newly closed by foundations. Risky transitions retain independent Sol review; ordinary/UI steps go to gates. No product gate or performance measurement has been run in this design-only job.
Finished foundations-design. Base/head remains
851d502909(detached dev worktree). No source edits, commits, pushes, deployment, subjobs or product gate runs.Deliverables:
The compact design specifies the Host aggregate/reducer, lifecycle/action presentation, connection revision and installation/session ownership, common v1 in-memory/mTLS connection actor, committed event/cache publication, bounded fleet recovery, generic provider/resource cutover, generated bindings and fault tests. Seventeen independently mergeable 1–3-day milestones total 40 focused person-days, with dependencies, file ownership/parallelism, acceptance and issue closure conditions. Zero open owner decisions block foundations. Deferred owner topics and already-settled choices were not re-asked.
Applied emil-design-eng and better-ui/layout/typography/colors/accessibility/writing/interface: immediate frequent/keyboard feedback, existing calternal surfaces/scales, one primary action, grouped lifecycle presentation, recoverable long text, named controls/focus/status announcements and cause/remedy copy. Proposed browser/contrast/accessibility behavior is explicitly pending implementation; supplied screenshots were inspected as production evidence. No new screenshot or runtime UI proof is claimed.
The workload-specific infraternal-agent RSS budget is a proposal derived under DECISIONS §43 from audit #51, not release calibration. Other PLAN performance budgets remain. Product verification must happen in the planned implementation milestones through scripts/verify and perf-test-VM A/B.
Actual design/read-only validation output (also in verification.txt), quoted verbatim:
Code graph built outside the worktree: Full build: 489 files, 7618 nodes, 110045 edges (postprocess=minimal). Source references were then checked against this job's head, rather than copied blindly from the older audits. Public technical references are cited in the design for Tokio bounded permits/watch, SQLite WAL and iproute2 network fault injection. Keep this issue open for orchestrator handoff.