# duckpigdog/sec-interview architecture

> Architecture diagram of the GitHub repository duckpigdog/sec-interview, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-03-31). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/duckpigdog/sec-interview
- Repository: https://github.com/duckpigdog/sec-interview

## Overview

1. This repository is a static Markdown knowledge base, not an application or service. Its “architecture” is primarily content organization: a top-level README, a SUMMARY index, and 32 chapter folders full of numbered `.md` files.

2. The main functional unit is the chapter folder. Each `ChapterN/` directory groups a set of interview-question articles for one topic area, with files named like `N-1.md`, `N-2.md`, etc. The numbering suggests ordered subsections within each chapter rather than independent modules.

3. `SUMMARY.md` is the navigation backbone. The README explicitly says it is the directory/table of contents, so any diagram should treat it as the central index that connects readers to the chapter content.

4. `README.md` is the repository front door and project positioning layer. It explains the scope: a very large collection of cybersecurity interview questions and reference answers covering areas such as blue team, red team, reversing, cryptography, binary analysis, AI, and blockchain.

5. The chapter folders form the main topical boundaries. Even though the file tree does not expose each chapter’s title, the structure clearly shows a partitioned curriculum-style layout: one topic family per chapter, many small markdown entries per topic.

6. The content flow is simple: contributors write or update Markdown files inside a chapter, then the summary index links them into the reading path. There is no evidence of compiled artifacts, generated binaries, databases, or runtime dependencies.

7. The repository boundary is documentation-only. All “business logic” lives in human-authored text; there are no source-code packages, tests, build scripts, or infrastructure manifests in the provided tree.

8. Collaboration is community-driven and PR-based. The README invites submissions, so the maintenance model is decentralized: contributors add or refine question-answer entries, and the index/chapters absorb the changes.

9. For an architecture diagram, the core nodes are: README as entry point, SUMMARY.md as index/router, and the chapter directories as content stores. The edges are mostly navigation links rather than runtime data flows.

10. The practical output is a browsable study/reference corpus rendered by Markdown viewers such as GitHub. In other words, the repository functions as an organized static knowledge base for exam/interview preparation in security-related domains.

Main entry points: [`SUMMARY.md`](https://github.com/duckpigdog/sec-interview/blob/main/SUMMARY.md) (SUMMARY.md), [`README.md`](https://github.com/duckpigdog/sec-interview/blob/main/README.md) (README.md), [`Chapter1`](https://github.com/duckpigdog/sec-interview/tree/main/Chapter1) (Chapter 1), [`Chapter7`](https://github.com/duckpigdog/sec-interview/tree/main/Chapter7) (Chapter 7)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_front_matter["Front matter"]
  node_readme["README.md<br/>entry point<br/>[README.md]"]
  node_summary["SUMMARY.md<br/>navigation index<br/>[SUMMARY.md]"]
end

subgraph group_content["Chapter corpus"]
  node_chapters_1_4["Ch. 1-4<br/>chapter band"]
  node_chapters_5_8["Ch. 5-8<br/>chapter band"]
  node_chapters_9_12["Ch. 9-12<br/>chapter band"]
  node_chapters_13_16["Ch. 13-16<br/>chapter band"]
  node_chapters_17_20["Ch. 17-20<br/>chapter band"]
  node_chapters_21_24["Ch. 21-24<br/>chapter band"]
  node_chapters_25_28["Ch. 25-28<br/>chapter band"]
  node_chapters_29_32["Ch. 29-32<br/>chapter band"]
  node_articles["Markdown pages<br/>content pages"]
  node_chapter1["Chapter 1<br/>chapter folder"]
  node_chapter7["Chapter 7<br/>chapter folder"]
  node_chapter15["Chapter 15<br/>chapter folder"]
  node_chapter23["Chapter 23<br/>chapter folder"]
  node_chapter26["Chapter 26<br/>chapter folder"]
  node_chapter32["Chapter 32<br/>chapter folder"]
end

node_readme -->|"documents"| node_summary
node_readme -->|"describes"| node_articles
node_summary -->|"indexes"| node_chapters_1_4
node_summary -->|"indexes"| node_chapters_5_8
node_summary -->|"indexes"| node_chapters_9_12
node_summary -->|"indexes"| node_chapters_13_16
node_summary -->|"indexes"| node_chapters_17_20
node_summary -->|"indexes"| node_chapters_21_24
node_summary -->|"indexes"| node_chapters_25_28
node_summary -->|"indexes"| node_chapters_29_32
node_chapters_1_4 -->|"contains"| node_articles
node_chapters_5_8 -->|"contains"| node_articles
node_chapters_9_12 -->|"contains"| node_articles
node_chapters_13_16 -->|"contains"| node_articles
node_chapters_17_20 -->|"contains"| node_articles
node_chapters_21_24 -->|"contains"| node_articles
node_chapters_25_28 -->|"contains"| node_articles
node_chapters_29_32 -->|"contains"| node_articles
node_articles -.->|"example"| node_chapter1
node_articles -.->|"example"| node_chapter7
node_articles -.->|"example"| node_chapter15
node_articles -.->|"example"| node_chapter23
node_articles -.->|"example"| node_chapter26
node_articles -.->|"example"| node_chapter32

click node_readme "https://github.com/duckpigdog/sec-interview/blob/main/README.md"
click node_summary "https://github.com/duckpigdog/sec-interview/blob/main/SUMMARY.md"
click node_chapter1 "https://github.com/duckpigdog/sec-interview/tree/main/Chapter1"
click node_chapter7 "https://github.com/duckpigdog/sec-interview/tree/main/Chapter7"
click node_chapter15 "https://github.com/duckpigdog/sec-interview/tree/main/Chapter15"
click node_chapter23 "https://github.com/duckpigdog/sec-interview/tree/main/Chapter23"
click node_chapter26 "https://github.com/duckpigdog/sec-interview/tree/main/Chapter26"
click node_chapter32 "https://github.com/duckpigdog/sec-interview/tree/main/Chapter32"

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_readme,node_summary toneBlue
class node_chapters_1_4,node_chapters_5_8,node_chapters_9_12,node_chapters_13_16,node_chapters_17_20,node_chapters_21_24,node_chapters_25_28,node_chapters_29_32,node_articles,node_chapter1,node_chapter7,node_chapter15,node_chapter23,node_chapter26,node_chapter32 toneAmber
```

## Components

### Front matter

Repository entry points and navigation index

- [README.md](https://github.com/duckpigdog/sec-interview/blob/main/README.md): entry point · Repository front door and project positioning · `README.md`
- [SUMMARY.md](https://github.com/duckpigdog/sec-interview/blob/main/SUMMARY.md): navigation index · Table of contents and primary reading path · `SUMMARY.md`

### Chapter corpus

Static markdown study content organized into chapter folders

- **Ch. 1-4**: chapter band · Early chapter set of numbered interview-answer articles
- **Ch. 5-8**: chapter band · Mid-early chapter set of numbered interview-answer articles
- **Ch. 9-12**: chapter band · Mid chapter set of numbered interview-answer articles
- **Ch. 13-16**: chapter band · Mid-late chapter set of numbered interview-answer articles
- **Ch. 17-20**: chapter band · Late chapter set of numbered interview-answer articles
- **Ch. 21-24**: chapter band · Late chapter set of numbered interview-answer articles
- **Ch. 25-28**: chapter band · Late chapter set of numbered interview-answer articles
- **Ch. 29-32**: chapter band · Final chapter set of numbered interview-answer articles
- **Markdown pages**: content pages · Leaf interview-question articles inside each chapter folder
- [Chapter 1](https://github.com/duckpigdog/sec-interview/tree/main/Chapter1): chapter folder · Representative chapter directory with many ordered markdown entries · `Chapter1`
- [Chapter 7](https://github.com/duckpigdog/sec-interview/tree/main/Chapter7): chapter folder · Representative dense chapter directory with many ordered markdown entries · `Chapter7`
- [Chapter 15](https://github.com/duckpigdog/sec-interview/tree/main/Chapter15): chapter folder · Representative dense chapter directory with many ordered markdown entries · `Chapter15`
- [Chapter 23](https://github.com/duckpigdog/sec-interview/tree/main/Chapter23): chapter folder · Representative dense chapter directory with many ordered markdown entries · `Chapter23`
- [Chapter 26](https://github.com/duckpigdog/sec-interview/tree/main/Chapter26): chapter folder · Representative dense chapter directory with many ordered markdown entries · `Chapter26`
- [Chapter 32](https://github.com/duckpigdog/sec-interview/tree/main/Chapter32): chapter folder · Representative late chapter directory with a small set of markdown entries · `Chapter32`

## Connections

- README.md → SUMMARY.md: documents · README points readers to the repository table of contents
- README.md → Markdown pages: describes · README frames the corpus as a static knowledge base
- SUMMARY.md → Ch. 1-4: indexes · Navigation path into the first chapter band
- SUMMARY.md → Ch. 5-8: indexes · Navigation path into the second chapter band
- SUMMARY.md → Ch. 9-12: indexes · Navigation path into the third chapter band
- SUMMARY.md → Ch. 13-16: indexes · Navigation path into the fourth chapter band
- SUMMARY.md → Ch. 17-20: indexes · Navigation path into the fifth chapter band
- SUMMARY.md → Ch. 21-24: indexes · Navigation path into the sixth chapter band
- SUMMARY.md → Ch. 25-28: indexes · Navigation path into the seventh chapter band
- SUMMARY.md → Ch. 29-32: indexes · Navigation path into the final chapter band
- Ch. 1-4 → Markdown pages: contains · Chapter band resolves to numbered markdown pages
- Ch. 5-8 → Markdown pages: contains · Chapter band resolves to numbered markdown pages
- Ch. 9-12 → Markdown pages: contains · Chapter band resolves to numbered markdown pages
- Ch. 13-16 → Markdown pages: contains · Chapter band resolves to numbered markdown pages
- Ch. 17-20 → Markdown pages: contains · Chapter band resolves to numbered markdown pages
- Ch. 21-24 → Markdown pages: contains · Chapter band resolves to numbered markdown pages
- Ch. 25-28 → Markdown pages: contains · Chapter band resolves to numbered markdown pages
- Ch. 29-32 → Markdown pages: contains · Chapter band resolves to numbered markdown pages
- Markdown pages → Chapter 1: example · Representative chapter directory showing the numbered file pattern
- Markdown pages → Chapter 7: example · Representative chapter directory showing a dense topic cluster
- Markdown pages → Chapter 15: example · Representative chapter directory showing a dense topic cluster
- Markdown pages → Chapter 23: example · Representative chapter directory showing a dense topic cluster
- Markdown pages → Chapter 26: example · Representative chapter directory showing a dense topic cluster
- Markdown pages → Chapter 32: example · Representative late chapter directory showing the same ordered pattern
