The Gemstone Publishing Repo
Relevant source files
The following files were used as context for generating this wiki page:
The Gemstone Publishing Repo (located at THE-GEMSTONE/) is a dedicated content and configuration repository within the IDAHO-VAULT ecosystem. Its primary purpose is to host "The Gemstone," an anonymous independent publication about Idaho, built using the Quartz v4 framework. It functions as a specialized publishing arm where agents work under direction to maintain the site, update automation, and manage the underlying content structure.
Sources: THE-GEMSTONE/README.md:1-3, THE-GEMSTONE/AGENTS.md:7-10, !/TOPOLOGY-CENSUS-root-20260706T100744Z.json:entry_count 31
System Architecture and Components
The repository is structured as a "publishing repo," meaning it focuses on content and site configuration rather than core application logic. It leverages Quartz v4 to transform Markdown content into a web-accessible publication.
Core Structure
The repository follows a standardized layout for Quartz and GitBook-style documentation management, organized into specific subdirectories:
| Path | Description |
|---|---|
content/ | Primary directory for publication content. Protected from unauthorized agent edits. |
quartz/ | Core Quartz v4 framework files and logic. |
public/ | Generated static assets for the published site. |
docs/ | Documentation for the publication project. |
node_modules/ | Project dependencies. |
Sources: THE-GEMSTONE/AGENTS.md:7-10, THE-GEMSTONE/AGENTS.md:27-28, !/TOPOLOGY-CENSUS-root-20260706T100744Z.json:entry_count 31
Data Flow Diagram
The following diagram illustrates the flow of content from agent contribution to the final publication state within the repository.
Agent Swarm Coordination
The repository is managed by "Logan's Unified Swarm" (LAF-US / PROJECT HORIZON). Multiple AI agents are assigned specific roles and branch prefixes to ensure isolated, traceable work.
Agent Registry and Roles
| Agent | Branch Prefix | Primary Role |
|---|---|---|
| GitHub Copilot | copilot/ | Inline editing, YAML frontmatter, and configuration changes. |
| Claude Code | claude/ | Structural work, automation, and build pipeline management. |
| Codex | codex/ | General code tasks and scripting. |
| Gemini | gemini/ | Research support and content development. |
Sources: THE-GEMSTONE/AGENTS.md:14-19
Operational Boundaries
Agents working within THE-GEMSTONE must adhere to strict governance rules:
- Approval Requirement: No merges to the
mainbranch are permitted without explicit approval from the repository owner (Logan Finney). - Content Protection: Content residing in
content/must not be altered without direct instruction. - Configuration Constraints: Agents are prohibited from changing
quartz.config.tssettings, specificallybaseUrlortheme, unless instructed. - Workflow: Agents work on individual branches; deliverables are submitted via Pull Requests (PRs), often facilitated by an auto-PR workflow.
Sources: THE-GEMSTONE/AGENTS.md:21-31
GitBook and Documentation Configuration
The repository supports Git-synced documentation standards, allowing content to be managed via external editors (such as Cursor or Claude Code) and synchronized with interfaces like GitBook.
Configuration Files
| File | Purpose |
|---|---|
.gitbook.yaml | Defines the root directory, readme/summary paths, and redirects for the documentation. |
SUMMARY.md | Defines the table of contents and navigation hierarchy for the published output. |
README.md | Serves as the homepage for the documentation or publication space. |
Sources: - gitbook.com -.md:30-45, - gitbook.com -.md:111-125
GitBook Structure Logic
The system prioritizes the SUMMARY.md file to determine how pages are grouped and linked. If this file is missing, the structure is inferred from the directory layout.
Content Standards and Metadata
Notes and articles within the repository utilize YAML frontmatter for lifecycle and SEO management.
Essential Frontmatter Fields
| Field | Description |
|---|---|
description | Page description for SEO and previews. |
icon | Navigation icon (e.g., Font Awesome names like book-open). |
hidden | Boolean to hide/show the page in the table of contents. |
layout | Controls visual elements like width, tableOfContents, and pagination. |
vars | Page-level variables for dynamic expressions. |
Sources: - gitbook.com -.md:265-285, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:315-325
Reusable Content Blocks
The system supports reusable content via an "include" mechanism, stored in the .gitbook/includes/ directory. These are referenced in Markdown using the {% include "/path/to/block" %} syntax, ensuring consistency for repeated instructions or disclaimers across multiple pages.
Sources: - gitbook.com -.md:162-170, - gitbook.com -.md:510-515
Summary
The Gemstone Publishing Repo serves as a structured, agent-maintained platform for independent journalism. By utilizing Quartz v4 and standardized Git documentation practices, it ensures that content is both machine-manageable and human-publishable. The rigid coordination between agents and the owner maintains the integrity of the publication's content while allowing for high-velocity updates through specialized AI workflows.
Sources: THE-GEMSTONE/AGENTS.md:7-12, VAULT-CONVENTIONS.from-pushable-2026-05-08.md:465-470