Repository navigation
Implement on-prem small-team access — merge held for maintainer review - #7
Merged
Merged
Conversation
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).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
plans/closure/on-prem-user-access/.7462263ec482c5fda4bd1a70a9a55b0efc313cd3passed hosted dependency audit, CI and installer checks.mainretains its prior Rustls resolution until this PR merges./api/user-budgetwere corrected and re-reviewed. Exact runtime candidated8fd9c2a5cbcd4cda317a215e17e9a188699cb71passed default/no-default Rust suites and hosted CI, installer and dependency audit. Seeplans/closure/on-prem-user-access/015-status.md.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.mdand 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
mainat9a0a903c9944b69a6c1ae9fa969bb8603d5c65d9.d2fb281ef5b4822eae2070d6709dc3bd93033b95; 79 commits ahead, 0 behind, 155 changed files.d8fd9c2a; subsequent commits are planning/status reconciliation only.Merge disposition
Merge held pending maintainer review. GitHub reports no submitted reviews (
reviews: [],reviewDecisionempty). 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.