docs: single-repo multi-repo-deployment variant (no backend changes) - #117
Open
ggPeti wants to merge 4 commits into
Open
docs: single-repo multi-repo-deployment variant (no backend changes)#117ggPeti wants to merge 4 commits into
ggPeti wants to merge 4 commits into
Conversation
added 4 commits
August 5, 2026 13:59
- example-config.toml: document that instance config = one [user-repo] per instance, [agent] is supplied by the deployment config, secrets are provisioned separately - docs/multi-repo-deployment.md: single-repo-variant topology (host instance + confidential tenant instance), operator-config ownership, stdlib deps import machinery
- remove registry language (no repos map/confidential flags); each instance is one flat [user-repo] config - add exact topology table (instance/repo/branch/config source/agent), tenant wiring (hostnames/ssh 2795/webProxy 28084), encryption split, deploy keys, stdlib deps contract, and the verification performed - example-config.toml: config generated from the deployment repo, not trotter-only
- commit multi-repo-design.md (was untracked) and reference it from docs/ as ../multi-repo-design.md so committed readers can follow it - add a Deployment status section: changes are open PR/MRs (nothing merged or activated); the live host tracks welker prod-backend which does not yet carry the stdlib contract; the c-instance container is provisioned only on first nixos-rebuild of trotter's branch - align the stdlib namespace section with the corrected contract (full pointy surface; both #pointy.namespaces.<ns>.steps.<id> and #packages.<system>.pointy.namespaces.<ns>.steps.<id> reach built steps) - wording: no backend source changes (docs + example-config comments)
- deployment doc: shrink the stdlib import section to a summary + link to the canonical pointy-stdlib README (contract was triplicated); list-ify the tenant provisioning paragraph; unify tenant-registration terminology; drop the git-diff parenthetical from Verification - example-config.toml: fix broken sentence grammar, drop the [agent] comment that restated the file header, clarify --model/runner phrasing and 'new draft' -> 'new session' - leave multi-repo-design.md prose untouched
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
1 participant
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.
Summary
Deployment documentation for the single-repo multi-repo-deployment variant: one running pointy instance serves exactly one user repo; confidentiality for
pointy-welker-cis enforced by a dedicated tenant (pointy-c-instance) with its agent disabled by construction.docs/multi-repo-deployment.md— precise topology (host instance →pointy-welker; confidential tenant →pointy-welker-c), operator-config ownership (trotterconfig/pointy.nix/ c-instanceconfig/pointy-config.toml), encryption split, stdlibdepsimport contract, and verification record.backend/example-config.toml— comment-only: instance config is one[user-repo];[agent]is supplier by the deployment config; generated from the deployment repo's unencrypted config.No backend source changes (diff vs
mainis docs/example-config only).