> For the complete documentation index, see [llms.txt](https://the-static-collective.gitbook.io/the-static-collective-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://the-static-collective.gitbook.io/the-static-collective-docs/front-room.md). # The Front Room Assistant orientation landmark for continuity across Static Collective work. Locate neighboring fields, unresolved frontiers, and source-owned doors. Orientation is not retrieval, publication, or auth > **Orientation is not retrieval.** > > This is an orientation space for an assistant entering or re-entering the Static Collective's work. It exists to keep the thread proper across conversations, tools, projects, and discontinuities. It is **not** a human-facing welcome page, product pitch, substitute project index, or canonical description of every repository. > > **The present request selects the door.** The room must not select the request. The room is a stable landmark, not a snapshot of the entire Collective. It may expose nearby fields, relevant boundaries, useful entrances, and unresolved fog. Enter briefly. Leave freely. Do not impose its vocabulary on unrelated tasks. ## Entry protocol 1. **Receive the present particular.** Identify what the user is actually asking, including named projects, constraints, and corrections. Do not replace it with a general Collective narrative. 2. **Orient at field scale.** Identify only the nearby areas and unresolved questions that might matter. Scanning a door's label is not traversing its contents. 3. **Choose a bounded crossing.** Follow an indicated door only if it helps with this request. Prefer project-owned sources, executable artifacts, current records, and explicit human corrections over summaries here. 4. **Preserve distinctions.** Observation, inference, proposal, implementation, receipt, and authority remain separate. Shared names and themes do not merge projects. 5. **Keep fog visible.** If current descriptions conflict, name the contradiction; do not silently resolve it into a coherent story. 6. **Carry the useful trace.** Retain the source, why it mattered, what changed, and what remains open. Stop traversing when the task is adequately grounded. ``` present request ↓ orient: nearby fields + known uncertainty ↓ select relevant door(s) ↓ inspect owning source and current evidence ↓ perform bounded work ↓ leave a reconstructible trace ``` ## Nearby fields — addresses, not verdicts | Field | Useful door | Orientation only | | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Continuity and historical breadcrumbs | [witness notebook](/the-static-collective-docs/witness/witness.md) · [unresolved questions](/the-static-collective-docs/witness/unresolved.md) | The lower-case `witness/` directory is a non-authoritative continuity notebook. It is not itself a Scripture project or an oracle of what happened. | | Scripture: community audio recordings | [WITNESS repository](https://github.com/the-static-collective/WITNESS) | Community audio Bible: human passage recordings with local receipts and attributable assembly. Executable prototype lives on an **unmerged branch**, not `main`. | | Scripture: source and transformation | [Revival](https://github.com/the-static-collective/revival) | Source-backed Bible compilation, linguistic/source witnesses, and attributable projections. | | Scripture: shared encounter | [Upper Room](https://github.com/the-static-collective/Upper-room) | Shared Scripture attention, branches, encounter continuity, and voluntary re-entry. Distinct from Revival. | | Crossings, memory, and local authority | [reLATTE](https://github.com/the-static-collective/reLATTE) · [Project0](https://github.com/the-static-collective/project0) | Crossing contracts, receipts, context and authority boundaries; consult each organ for its actual remit. | | Musical and visual instruments | [Haunted Toaster](https://github.com/the-static-collective/the-haunted-toaster) · [Haunted Blender](https://github.com/the-static-collective/the-haunted-blender) | Different creative machines, related without becoming interchangeable. | | Research, mathematics, and inquiry | [ALEX.2](https://github.com/the-static-collective/ALEX.2) · [Dogram](https://github.com/the-static-collective/Dogram) · [National Treasure](https://github.com/the-static-collective/national-treasure) | Evidence, calculations, and interpretive questions have different standards and local owners. | | Human participation and return | [NanaSpork / Garden](https://github.com/the-static-collective/BananaSpork) · [Book of Acts / Jubilee Engine VM](https://github.com/the-static-collective/Jubilee-Engine-VM) | Help Slips, review, Campfire, reporting, confirmation, and optional historical preservation are not one automatic state. | | Repository terrain | [Living Git Map](/the-static-collective-docs/living-git-map/atlas.md) · [current executable state](/the-static-collective-docs/project-state/project-state.md) | The map is a dated public aperture. Branch existence is not adoption, and absence from the public view is not nonexistence. | | Shared patterns and ungraduated ideas | [Pirate Law](/the-static-collective-docs/patterns/pirate-law.md) · [Primitive Incubator](/the-static-collective-docs/frontier/primitive-incubator.md) · [Vocabulary](/the-static-collective-docs/vocabulary/static-collective-vocabulary.md) | Reusable laws must earn portability; untested or incubating notions remain provisional. | These links are addresses for deliberate retrieval, not instructions to preload everything. One named project may belong near several fields; placement here confers no authority. ## Project-identity correction — inspect the owning code **Source-backed reconciliation, 2026-10-13:** WITNESS **is** a community audio Bible project. The [main README](https://github.com/the-static-collective/WITNESS/blob/main/README.md) says so; its [unmerged Genesis branch](https://github.com/the-static-collective/WITNESS/tree/genesis/community-audio-bible-001) contains an actual Matthew 5 recording prototype and Supabase shared-room contracts. A prior orientation edit had incorrectly treated WITNESS as unrelated to Scripture. That classification is superseded by the inspected project sources. Keep the three Scripture organs distinct: * [**WITNESS**](https://github.com/the-static-collective/WITNESS) — human audio readings anchored to Scripture passages, local-first receipts, and optional community assembly. The current prototype assigns alternate verses for a two-voice test; [CANON-001 — FREE WITNESS](https://github.com/the-static-collective/WITNESS/blob/genesis/community-audio-bible-001/docs/CANON-001-FREE-WITNESS.md) explicitly says unrestricted voluntary reading, not verse assignment, is the intended contribution model. * [**Revival**](https://github.com/the-static-collective/revival) — source-backed Bible kernels, textual/linguistic witnesses, translation choices, and attributable projections. * [**Upper Room**](https://github.com/the-static-collective/Upper-room) — shared Scripture attention, room encounters, branching and voluntary re-entry. **Maturity boundary:** WITNESS's main branch is README-only; the recorder, schema, and shared-room code remain in an open pull request. Source code and deployment configuration do not themselves prove a successful two-phone field trial or a deployed service. The capitalized `WITNESS` project is also distinct from this documentation repository's lower-case `witness/` continuity notebook. Names resemble each other; purposes differ. ## Authority / status boundaries ``` human correction ≠ silent project rewrite orientation ≠ retrieval directory label ≠ project identity public ≠ canonical branch exists ≠ branch accepted proposal ≠ implementation implementation ≠ field proof witness ≠ authority representation ≠ occurrence compatibility ≠ permission absence ≠ nonexistence ``` The current human request governs intent and corrections; project-owned artifacts, tests, receipts, and source witnesses govern factual claims about implementation. When these disagree, report the disagreement and investigate rather than laundering one into the other. This room never outranks either. ## Frontier cues, not mandatory itineraries * **Continuity across discontinuity:** how to re-enter prior work without claiming a memory, identity, or source that was not actually carried. [The Room Can Vanish; the World Remains](/the-static-collective-docs/patterns/world-reentry-memory.md). * **Local authority after crossing:** what survives transformation, how receipts remain inspectable, and who owns RECEIVE, HOLD, refusal, and disposition. Start in the relevant project's contracts, not with this overview. * **Human return loop:** the proposed/partially proved path from a particular need through review, Campfire, confirmation, and possible Book of Acts handoff; never infer full deployment from a public seam. * **Unplaced or unresolved work:** [unresolved questions](/the-static-collective-docs/witness/unresolved.md), [primitive incubator](/the-static-collective-docs/frontier/primitive-incubator.md), and [public Git inventory](/the-static-collective-docs/living-git-map/atlas/generated.md). Keep the difference between a preserved question and a verified result. Do not present these cues as the only active work or a ranked priority list. ## Minimal traversal receipt ``` Entered: Front Room (orientation only) Present question: ... Selected field / door: ... Why this door: ... Owning source and freshness: ... Observed / inferred / proposed: ... What was done or learned: ... Residual fog or contradiction: ... Authority and next local disposition: ... ``` No private reasoning transcript is required. An inspectable source and a bounded summary suffice. ## Room failure conditions The room is failing when it becomes a visitor brochure; routes every conversation into Collective concerns; loads a standard large context dump; treats neighboring projects as one product; promotes summaries over current source; quietly resolves contradiction; labels a project from name-association; or expands into a second database. **If it fails, make the room smaller and the doorway more exact.** > **Starting place, not source of truth. Doorway, not destination.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://the-static-collective.gitbook.io/the-static-collective-docs/front-room.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.