docs: add distribution strategy page with three doors - #80
Merged
Merged
Conversation
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.
What
docs/DISTRIBUTION.md: the distribution strategy fordoc(andmem, which followsthe same doors). It defines the three supported paths — local single-player (current
default, honestly labeled), ByteFolk-hosted SaaS (gated behind demand signals plus
multi-tenant/privacy/paid-infra prerequisites), and guided self-hosting (current main
path) — with per-door identity, cost, and compliance boundaries.
deployments, per-deployment client sessions; SaaS is just a preset deployment address),
the guidance surfaces (
doc initrouting question, README/landing three doors,doc doctordoor report), operator security boundaries, and migration between doors asa product promise per GOAL.md north star 5.
[Unreleased]Added entry.Why
The core value (person-to-person sharing) only holds when a deployment is reachable by
other people, and default users do not deploy. Making the three doors and their boundaries
explicit keeps product copy honest about current capability versus roadmap, and keeps SaaS
from opening before its compliance and tenancy prerequisites exist.
Validation
Docs-only change; no runtime behavior change. Markdown reviewed locally; CHANGELOG and
README links checked against upstream main (rebased onto c3e8944).