Skip to content

Implement on-prem small-team access — merge held for maintainer review - #7

Merged
dbowm91 merged 79 commits into
mainfrom
plans/on-prem-small-team-user-access
Oct 15, 2026
Merged

dbowm91 merged 79 commits into
mainfrom
plans/on-prem-small-team-user-access

Conversation

@dbowm91

@dbowm91 dbowm91 commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Scope and product boundary

This PR implements optional on-prem small-team user access in the Rust runtime. The single-owner SBC/LAN workflow remains the default. Provider topology, upstream credentials, private model endpoints and routing remain operator-controlled through TOML/environment; user identities, sessions, profiles, budgets, usage and audit remain in SQLite. This does not add SaaS organizations, hosted IAM, billing, or native remote-access/VPN service.

Implemented and qualified milestones

  • M001–M013: admin bootstrap, personal credentials, browser sessions and CSRF, principal attribution, model profiles, user and instance budgets, recovery, administration UI, integrations, cross-protocol admission, and the measured physical Pi 5 envelope. Historical closure records remain under plans/closure/on-prem-user-access/.
  • M014 closed: Rustls resolves to 0.23.46 on the PR candidate, with no advisory suppression. Exact candidate 7462263ec482c5fda4bd1a70a9a55b0efc313cd3 passed hosted dependency audit, CI and installer checks. main retains its prior Rustls resolution until this PR merges.
  • M015 closed: independent authz review defects in hard-cost reservation proof bounds and browser-session access to /api/user-budget were corrected and re-reviewed. Exact runtime candidate d8fd9c2a5cbcd4cda317a215e17e9a188699cb71 passed default/no-default Rust suites and hosted CI, installer and dependency audit. See plans/closure/on-prem-user-access/015-status.md.
  • M016 closed: final integration and merge-readiness reconciliation is recorded in plans/closure/on-prem-user-access/016-status.md.

Pi 5 operating envelope

M012 measured a physical Pi 5 with MMC storage. Solo operation is practical; up to 2–4 concurrent requests work with degraded tails, while 8-way concurrency saturates (p50 about 4.1 s and concurrent p95 up to about 14 s). Forty-nine named user records are inexpensive metadata, not 49 simultaneous inference sessions. See docs/raspberry-pi.md and the M012 closure. The separate Pi MMC tail-attribution workstream is nonblocking and is not part of this PR’s implementation.

Final candidate and checks

Merge disposition

Merge held pending maintainer review. GitHub reports no submitted reviews (reviews: [], reviewDecision empty). Automated checks are green and M015 has no unresolved security finding, but a maintainer must review the reconciled PR and decide whether to merge. This PR remains open and has not been merged.

Physical SBC and reference Linux host remain unprovisioned, so per
the plan's stop conditions the milestone cannot close and no
capacity claim is published. This pass lands the SBC runner
boundary contracts, full local gates (1008 default + 1009
no-default Rust, 185 tooling), and the blocked closure record;
work packages 2-4 resume when hardware exists.
check 7m52s pass, installer shells pass; cargo-deny unchanged
pre-existing rustls advisory failure (separate triage).
@dbowm91 dbowm91 changed the title Implement on-prem small-team user access (correctives M008–M012 registered) Implement on-prem team access — TLS security and final review gates open Oct 15, 2026
@dbowm91 dbowm91 changed the title Implement on-prem team access — TLS security and final review gates open Implement on-prem small-team access — final reconciliation in progress Oct 15, 2026
@dbowm91 dbowm91 changed the title Implement on-prem small-team access — final reconciliation in progress Implement on-prem small-team access — merge held for maintainer review Oct 15, 2026
@dbowm91
dbowm91 merged commit 88f58bb into main Oct 15, 2026
4 checks passed
@dbowm91
dbowm91 deleted the plans/on-prem-small-team-user-access branch October 15, 2026 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant