Local review · This projection presents reviewed governance source; it is not runtime or remote publication evidence.

126 — The Fountain Coach Organization Web Projection

Fountain Coach needs a human-facing organization projection, not a GitHub clone. Agents administer the estate through typed Swift and FCIS-KIT instruments; Git preserves source history; FountainStore preserves the governed organization and publication projection; and the browser presents that state without becoming its authority.

Principal illustration — a deterministic vector governance projection. It describes the intended authority and browser boundary; it is not a live repository listing, Store receipt, deployment result, or claim that the source host has already been implemented.

The Fountain Coach organization should be visible as a coherent place on the web: a name, a set of repositories, release lines, governance documents, recovery state, and links between them. The writer should not have to infer that coherence from unrelated server paths. The browser must not become the place where an agent invents, mutates, or silently approves that state.

The decision

The organization landing page is a read-oriented projection of two authorities that remain distinct:

agent intention
      ↓ typed FCIS-KIT / Swift operation
source host + FountainStore authorities
      ↓ validated projection
human-facing organization web view

The page explains what exists and how it is related. It does not grant access, create a repository, promote a release, or declare a backup complete merely because a route rendered successfully.

This is deliberately smaller than GitHub. The initial product is an organization view that lets a human understand the estate while Codex and other admitted agents perform administration through the governed operation plane.

The four boundaries

The organization view may join these records by stable identities and digests. It must not flatten them into a single ambiguous “server status.”

What the human sees

1. What is this? — Fountain Coach, its purpose, and the source/publication boundary.
2. What is here? — repositories and governed public projections, each with a stable identity and state.
3. What changed? — current release or revision, predecessor, and checkable evidence.
4. What can I follow? — source, governance, Book, MIDI2, instruments, status, and recovery policy.

Every page states whether its content is a local, staging, or published projection. A generated registry or Store-backed catalog is preferred over a manually maintained inventory.

What the agent does

Codex is an agent peer, not the browser and not FountainStore. It uses admitted typed operations, validates target and authority, records correlation, and returns a terminal receipt that the projection can later show.

source.repository.admit
source.repository.release
organization.projection.refresh
recovery.projection.export
recovery.restore.verify

These names describe required operation classes; they do not claim that every operation already exists. A command or instrument is not executable merely because a page lists its name.

Storage and persistence

Git objects preserve source history and transportable repository state. FountainStore records preserve the typed organization projection, publication state, release lineage, operation receipts, and recovery references. Recovery storage preserves encrypted, digest-addressed projections and restore material under a separate custody boundary.

The browser reads a validated projection assembled from these authorities. A second disk on the same host is storage separation, not independent disaster-recovery custody.

The web view is not an administration console

The first organization projection is read-only. Any future mutation affordance must identify and invoke the same admitted instrument operation, consent boundary, target, lifecycle, and terminal result used by Codex.

Swift server, browser client

The web-facing host is a Swift projection service. TypeScript is allowed as presentation source only when compiled before deployment; a Node runtime, package registry, or JavaScript service is not production authority.

Acceptance boundary

This chapter is a governance contract and design projection. It does not claim that the Swift source host, organization catalog, browser routes, agent instruments, DNS, or public deployment are implemented.

1. stable organization and repository identity;
2. revision and content digest from the source authority;
3. matching FountainStore projection record;
4. visible local/staging/published distinction;
5. browser-accessible source/release/governance links; and
6. an independently readable terminal receipt for projection refresh.

Rules

1. The organization web view is a human-facing projection, not a source, Store, or authorization authority.
2. Agents administer through typed Swift/FCIS-KIT operations.
3. Git owns source objects and transport; FountainStore owns governed organization and publication projections.
4. Repository, release, publication, and recovery claims retain identities, provenance, digests, and state.
5. The initial organization projection is read-only.
6. TypeScript may be compiled into browser assets, but Node must not become a production runtime dependency.
7. Same-host storage separation is not independent recovery custody.
8. Unknown, stale, or uncorrelated state is shown as not established.

Governing sentence

The Fountain Coach organization is administered by typed agents and persisted by Git, FountainStore, and governed recovery storage; the browser is the readable face of that state, never its authority.