Skip to content

ARCHITECTURE.md

Latest commit

 

History

History
149 lines (125 loc) · 6.01 KB

ARCHITECTURE.md

File metadata and controls

149 lines (125 loc) · 6.01 KB

🏛️ Architecture — Hack23/.github Organisation Meta Repository

Documentation-only repository. No build, no runtime, no application code, no user data. Architecture is therefore an information-architecture description of how GitHub renders the org profile and how default community-health files propagate across all Hack23 repositories.

Property Value
Owner CEO (James Pether Sörling)
Classification 🟢 Public
Stack Markdown · GitHub Flavored Markdown · Mermaid · GitHub-rendered HTML
Hosting github.com (managed by GitHub, Inc.)
Build None — GitHub renders Markdown server-side
Review cycle Annual (or on material change)
ISMS reference Secure Development Policy

1. Repository structure

Hack23/.github/
├── README.md                  # This repo's own meta README (navigation hub)
├── FUNDING.yml                # Default GitHub Sponsors config — inherited by all Hack23 repos
├── ARCHITECTURE.md            # ← you are here
├── SECURITY_ARCHITECTURE.md   # Defense-in-depth controls (ISMS-aligned)
├── THREAT_MODEL.md            # STRIDE + MITRE ATT&CK threat model
└── profile/
    └── README.md              # Org profile rendered at github.com/Hack23

There is no source code, no CI workflow, no package. All "behaviour" is provided by GitHub's first-party rendering of these Markdown files.

2. How the org profile renders

flowchart LR
    A[Maintainer] -->|"Signed commit + PR"| B[GitHub branch protection]
    B -->|"Required reviews + status checks"| C[main branch]
    C -->|"profile/README.md"| D[github.com/Hack23<br/>org profile page]
    C -->|"FUNDING.yml"| E[💖 Sponsor button on every Hack23 repo]
    C -->|"README.md / *.md"| F[Repo browse views]
    D --> G[Public visitors]
    E --> G
    F --> G
Loading
  • profile/README.md is the special path GitHub looks for in any organisation's .github repo to render the public org landing page (https://github.com/Hack23).
  • FUNDING.yml at the root of the org-level .github repo is inherited by every repository in the org that does not ship its own .github/FUNDING.yml. The 💖 Sponsor button on every Hack23 repo flows from this single file.
  • All other .md files in this repo are addressable directly via raw GitHub URLs and serve as canonical references for ISMS audits and external citations.

3. Information architecture (profile README sections)

mindmap
  root((🔒 Hack23<br/>Org Profile))
    🛡️ ISMS Transparency
      Public ISMS-PUBLIC
      Information Security Policy
      Compliance Frameworks
    🍎 Discordian Blog
      30+ posts
      Manifesto
      ISMS coverage
    🚀 Flagship Projects
      🗳️ Riksdagsmonitor
      🇪🇺 EU Parliament Monitor
      🔌 European Parliament MCP Server
      🕵️ Citizen Intelligence Agency
      📋 CIA Compliance Manager
      🥋 Black Trigram
      🎮 Game Template
      ☁️ Lambda in Private VPC
      🧪 Sonar-CloudFormation-Plugin
    🔑 Security Services
      Security Architecture
      Cloud Security & DevSecOps
      Compliance & Regulatory
      Open Source & OSPO
      Training & Culture
    💖 Sponsor
      github.com/sponsors/Hack23
    🌐 Sitemap
      hack23.com (8 languages)
      Per-project features/docs
    👨‍💼 About
      James Pether Sörling
      Certifications
      Talks & Press
Loading

4. Cross-organisation link map

The profile is the canonical entry point for SEO and discoverability across every Hack23 surface. Every flagship project README and every hack23.com page links back to this profile, and the profile links forward to every product surface.

graph LR
    P[github.com/Hack23<br/>profile/README.md] --> H[hack23.com]
    P --> I[Hack23/ISMS-PUBLIC]
    P --> R[Hack23/riksdagsmonitor → riksdagsmonitor.com]
    P --> E[Hack23/euparliamentmonitor → euparliamentmonitor.com]
    P --> M[Hack23/European-Parliament-MCP-Server → npmjs.com]
    P --> C[Hack23/cia]
    P --> CC[Hack23/cia-compliance-manager → ciacompliancemanager.com]
    P --> B[Hack23/blacktrigram → blacktrigram.com]
    P --> S[github.com/sponsors/Hack23]
    P --> L[linkedin.com/in/jamessorling]
    P --> BL[hack23.com/blog.html]
    H --> P
    I --> P
    R --> P
    E --> P
    M --> P
    C --> P
    CC --> P
    B --> P
Loading

5. Change-management architecture

Stage Control
Authoring Local Markdown edit, optional Mermaid preview
Submission Pull request (no direct push to main)
Authentication GitHub MFA (TOTP / WebAuthn) — per Access Control Policy
Integrity GPG/SSH-signed commits — verified by GitHub
Review At least one approving review by an org owner
Audit trail Immutable Git history, GitHub audit log, signed-commit verification
Publication Merge → main → GitHub renders within seconds
Continuity Distributed Git replication (every clone is a backup)

6. References