# golboni/news architecture
> Architecture diagram of the GitHub repository golboni/news, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-06-19). It is an AI-made overview: check details against the source.
- Interactive diagram: https://gitdiagram.com/golboni/news
- Repository: https://github.com/golboni/news
## Overview
1. **What this repository is**
- This is not a traditional application repo with source code, build scripts, and runtime services.
- It is a **content-production and publishing repository** for the **Atlantean Chronicle — Weekly Build** workflow.
- The core output is a set of **static HTML issue pages** plus supporting media assets and operating instructions.
2. **Primary control plane: the project instructions**
- `CHRONICLE_PROJECT_SYSTEM_PROMPT.md` is the most important orchestrating artifact.
- It defines the Chronicle’s **section order, design system, color variables, editorial standards, weekly workflow, checklist, privacy rules, squad context, and setup instructions**.
- In architecture terms, this file acts as the **policy and template layer** that governs how every weekly issue is created.
3. **Operational runbook**
- `SOP-007-Chronicle-Build.md` is referenced in the README as the formal process document for the build.
- It covers the **Thursday prep + Friday 20-minute build process**, file locations, troubleshooting, and issue numbering reference.
- This is the **process boundary** separating content planning from actual issue assembly.
4. **Main content artifacts: weekly issue pages**
- The files `atlantean-chronicle-vol1-no1.html` through `atlantean-chronicle-vol1-no8.html`, plus `chronicle-vol1-no9.html`, are the actual **published issue outputs**.
- Each HTML file appears to represent a single numbered Chronicle release in volume 1.
- These files are the **primary product surface** of the system.
5. **Public entry points**
- `index.html` is likely the main landing or directory page for the Chronicle.
- `mobile-news.html` is a separate presentation layer for mobile consumption.
- Together, these represent the **navigation/access layer** that routes readers to the issue pages.
6. **Media subsystem**
- The `photos/` and `pics/` directories store visual assets used by the HTML issues and/or landing pages.
- These are supporting resources rather than standalone content units.
- Their role is the **asset dependency layer** for layout, illustration, or story imagery.
7. **Editorial workflow and data flow**
- The README describes a workflow where the system prompt is loaded into Claude Projects, a prior issue is uploaded as a project file, and a memory document is also supplied.
- The build flow is: **instructions + prior issue + memory/context → next weekly issue draft → saved as HTML artifact**.
- This means the repo supports a **human-in-the-loop editorial pipeline**, not an automated compile/deploy pipeline.
8. **State and continuity model**
- Issue numbering is the key continuity mechanism: `No. 6`, `No. 7`, `No. 8`, `No. 9`, etc.
- The repository preserves prior issues as a historical archive and uses them as context for future builds.
- The architecture is therefore **append-only and sequential**, with each issue depending on the editorial state established by previous ones.
9. **External dependencies and boundaries**
- The README explicitly references **Claude Projects** and **Forgejo** as outside systems.
- The system prompt is meant to be pasted into Claude project instructions, and the SOP is meant to be pushed to an external docs location.
- So the repo itself is only one part of the ecosystem; the broader architecture includes **AI-assisted authoring** and **external documentation management**.
10. **No application runtime or backend**
- There is no evidence of server code, package manifests, databases, or build tooling.
- The repository is best understood as a **static publishing bundle with editorial governance**, not a software service.
- Any architecture diagram should show a **manual/content workflow** rather than a runtime application stack.
11. **How to diagram it**
- The clearest diagram would have:
- a **governance/input layer** (`CHRONICLE_PROJECT_SYSTEM_PROMPT.md`, SOP, memory/context files),
- a **content production step** in Claude,
- a **static issue output layer** (`*.html` issue files),
- a **navigation/access layer** (`index.html`, `mobile-news.html`),
- and a **media asset layer** (`photos/`, `pics/`).
- The arrows should emphasize **editorial generation and reuse of prior issues** rather than data processing or service calls.
12. **Repository summary in one sentence**
- This repo is a **static, AI-assisted weekly publication system** where a locked editorial prompt and operating procedure drive the creation of sequential HTML Chronicle issues supported by shared media assets and entry pages.
Main entry points: [`atlantean-chronicle-vol1-no1.html`](https://github.com/golboni/news/blob/main/atlantean-chronicle-vol1-no1.html) (Issue archive), [`chronicle-vol1-no9.html`](https://github.com/golboni/news/blob/main/chronicle-vol1-no9.html) (Current issue), [`CHRONICLE_PROJECT_SYSTEM_PROMPT.md`](https://github.com/golboni/news/blob/main/CHRONICLE_PROJECT_SYSTEM_PROMPT.md) (System prompt), [`readme.txt`](https://github.com/golboni/news/blob/main/readme.txt) (README)
## Diagram (Mermaid)
```mermaid
flowchart TD
subgraph group_governance["Governance"]
node_system_prompt["System prompt
editorial policy"]
node_readme["README
workflow guide
[readme.txt]"]
node_briefing["Issue briefing
context note"]
end
subgraph group_production["Production"]
node_editorial_flow(("Build flow
manual pipeline"))
node_workflow_output["Publish artifact
generated HTML"]
end
subgraph group_publication["Publication"]
node_issue_archive["Issue archive
static issue set"]
node_current_issue["Current issue
static HTML issue"]
node_vol1_no1["Vol 1 No. 1
issue page"]
node_vol1_no8["Vol 1 No. 8
issue page"]
node_index["Index
landing page
[index.html]"]
node_mobile_news["Mobile news
mobile view
[mobile-news.html]"]
end
subgraph group_assets["Assets"]
node_photos[("Photos
media folder")]
node_pics[("Pics
media folder")]
end
subgraph group_external["External"]
node_claude_projects["Claude Projects
authoring workspace"]
node_forgejo["Forgejo
docs host"]
end
node_system_prompt -->|"loaded into"| node_claude_projects
node_readme -->|"describes"| node_editorial_flow
node_briefing -->|"supplies context"| node_claude_projects
node_issue_archive -->|"provides continuity"| node_briefing
node_system_prompt -->|"governs"| node_editorial_flow
node_editorial_flow -->|"executes in"| node_claude_projects
node_claude_projects -->|"produces"| node_workflow_output
node_workflow_output -->|"materializes as"| node_current_issue
node_current_issue -->|"linked from"| node_index
node_current_issue -->|"adapted for"| node_mobile_news
node_index -->|"navigates to"| node_issue_archive
node_mobile_news -->|"navigates to"| node_issue_archive
node_photos -->|"supports"| node_current_issue
node_pics -->|"supports"| node_current_issue
node_issue_archive -->|"includes"| node_vol1_no8
node_issue_archive -->|"includes"| node_vol1_no1
node_forgejo -->|"documents"| node_readme
click node_system_prompt "https://github.com/golboni/news/blob/main/CHRONICLE_PROJECT_SYSTEM_PROMPT.md"
click node_readme "https://github.com/golboni/news/blob/main/readme.txt"
click node_briefing "https://github.com/golboni/news/blob/main/Chronicle-No8-Briefing.md"
click node_issue_archive "https://github.com/golboni/news/blob/main/atlantean-chronicle-vol1-no1.html"
click node_current_issue "https://github.com/golboni/news/blob/main/chronicle-vol1-no9.html"
click node_vol1_no1 "https://github.com/golboni/news/blob/main/atlantean-chronicle-vol1-no1.html"
click node_vol1_no8 "https://github.com/golboni/news/blob/main/atlantean-chronicle-vol1-no8.html"
click node_index "https://github.com/golboni/news/blob/main/index.html"
click node_mobile_news "https://github.com/golboni/news/blob/main/mobile-news.html"
click node_photos "https://github.com/golboni/news/tree/main/photos"
click node_pics "https://github.com/golboni/news/tree/main/pics"
classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_system_prompt,node_readme,node_briefing toneBlue
class node_editorial_flow,node_workflow_output toneAmber
class node_issue_archive,node_current_issue,node_vol1_no1,node_vol1_no8,node_index,node_mobile_news toneMint
class node_photos,node_pics toneRose
class node_claude_projects,node_forgejo toneIndigo
```
## Components
### Governance
Editorial rules, operating notes, and continuity context.
- [System prompt](https://github.com/golboni/news/blob/main/CHRONICLE_PROJECT_SYSTEM_PROMPT.md): editorial policy · Primary instruction set for section order, design system, standards, and weekly workflow. · `CHRONICLE_PROJECT_SYSTEM_PROMPT.md`
- [README](https://github.com/golboni/news/blob/main/readme.txt): workflow guide · Repository overview and usage notes for the Chronicle build process. · `readme.txt`
- [Issue briefing](https://github.com/golboni/news/blob/main/Chronicle-No8-Briefing.md): context note · Supporting editorial context for the next issue build. · `Chronicle-No8-Briefing.md`
### Production
Human-in-the-loop issue creation and sequencing.
- **Build flow**: manual pipeline · Human-in-the-loop process that turns guidance and prior context into a publishable issue.
- **Publish artifact**: generated HTML · The saved static issue artifact produced by the editorial workflow.
### Publication
Static HTML outputs and reader entry points.
- [Issue archive](https://github.com/golboni/news/blob/main/atlantean-chronicle-vol1-no1.html): static issue set · Sequential volume 1 issue pages preserved as historical context and reusable source material. · `atlantean-chronicle-vol1-no1.html`
- [Current issue](https://github.com/golboni/news/blob/main/chronicle-vol1-no9.html): static HTML issue · Latest published Chronicle issue in the sequence. · `chronicle-vol1-no9.html`
- [Vol 1 No. 1](https://github.com/golboni/news/blob/main/atlantean-chronicle-vol1-no1.html): issue page · Representative early Chronicle issue page. · `atlantean-chronicle-vol1-no1.html`
- [Vol 1 No. 8](https://github.com/golboni/news/blob/main/atlantean-chronicle-vol1-no8.html): issue page · Representative late Chronicle issue page before the current release. · `atlantean-chronicle-vol1-no8.html`
- [Index](https://github.com/golboni/news/blob/main/index.html): landing page · Primary directory or entry page for the Chronicle. · `index.html`
- [Mobile news](https://github.com/golboni/news/blob/main/mobile-news.html): mobile view · Alternative reading surface optimized for mobile access. · `mobile-news.html`
### Assets
Shared visual resources used by the pages.
- [Photos](https://github.com/golboni/news/tree/main/photos): media folder · Shared photographic assets referenced by issue pages. · `photos`
- [Pics](https://github.com/golboni/news/tree/main/pics): media folder · Additional image assets used by the Chronicle pages. · `pics`
### External
Outside systems used in the workflow.
- **Claude Projects**: authoring workspace · External AI workspace where the prompt and context are assembled into a new issue draft.
- **Forgejo**: docs host · External repository/docs boundary referenced by the workflow.
## Connections
- System prompt → Claude Projects: loaded into · The project prompt is pasted into the external AI workspace.
- README → Build flow: describes · Repository instructions point to the manual build procedure.
- Issue briefing → Claude Projects: supplies context · Briefing material seeds the next issue draft.
- Issue archive → Issue briefing: provides continuity · Previous issues and notes feed the next build context.
- System prompt → Build flow: governs · Editorial policy constrains the build process.
- Build flow → Claude Projects: executes in · The build is carried out through the external authoring workspace.
- Claude Projects → Publish artifact: produces · The AI-assisted drafting step yields the publishable HTML artifact.
- Publish artifact → Current issue: materializes as · The generated artifact becomes the latest issue page.
- Current issue → Index: linked from · The landing page points readers to the current issue.
- Current issue → Mobile news: adapted for · A separate mobile presentation exposes the issue content.
- Index → Issue archive: navigates to · The landing page provides access to the archive of issues.
- Mobile news → Issue archive: navigates to · The mobile surface also routes into the issue archive.
- Photos → Current issue: supports · Photographic assets are embedded in the published issue.
- Pics → Current issue: supports · Additional image assets support layout and stories.
- Issue archive → Vol 1 No. 8: includes · Representative prior issue in the numbered sequence.
- Issue archive → Vol 1 No. 1: includes · Representative earliest issue in the numbered sequence.
- Forgejo → README: documents · External docs management is part of the publishing ecosystem.