public: source that can be exported to GitHubmaintainers: maintainer-visible source and metadata
Why This Concept Exists
Git assumes that source visibility is mostly a repository problem. If code is in the repository, it is usually visible to everyone who can read that repository. Teams work around that with private forks, split repositories, embargoed branches, security advisories, environment-variable rituals, and careful timing. Glyph treats visibility as part of source control. The same project can have multiple views. A realm says “this is the source visible under this policy.”Realm Versus Branch
| Branch | Realm |
|---|---|
| Names a line of Git history. | Names a permissioned source view. |
| Usually used for active work. | Usually used for visibility boundaries. |
| Merging changes the branch tip. | Publication changes what the realm can see. |
| Does not explain who may read it. | Exists to make visibility explicit. |