Hermes Wiki
Developer/writelist

Developer Source List

Editable by hand anytime. Mirrors Architecture/writelist.md's shape for a scheduler to pick up rotation state.

Coverage rotation (replaces the old random/breadth picker — added 2026-08-25)

Why: with 255 leaf subtopics and the scheduler picking freely, there was no guarantee against overlap (re-touching a subtopic before every subtopic had at least one entry) or of ever reaching full coverage. This rotation guarantees one complete sweep of all 255 leaf subtopics per flavor, in a fixed order, before starting the next sweep — see system_prompt for the full mechanics the scheduler follows.

Canonical subtopic order (255 leaves, stable, recompute don't hardcode): walk Developer/ topics alphabetically, and within each topic walk its leaf subtopics alphabetically by full relative path (a "leaf" = a subtopic folder with no further subtopic subfolders below it, i.e. one that would directly hold Fundamentals//CaseStudies//Challenges//Checklists/). This is the same order the ## Full topic tree in Developer/_index.md already renders in — do not invent a different order. New subtopics added by hand mid-pass slot into this order by their path and get picked up naturally; no manual list to maintain here.

The 10-pass sequence (fixed, run in order, one flavor swept end-to-end per pass):

Pass Flavor
1 Fundamentals
2 CaseStudies
3 Challenges
4 CaseStudies
5 Challenges
6 CaseStudies
7 CaseStudies
8 Challenges
9 Fundamentals
10 CaseStudies

Checklists is never part of this rotation — stays opportunistic as before (write one whenever a subtopic genuinely warrants it; never required, never blocks pass completion).

After pass 10 finishes: rotation ends. The scheduler switches to unconstrained random picking — any topic/subtopic/flavor combination, governed purely by best-available material — same as the original pre-rotation behavior. Do not restart the 10-pass sequence or invent an 11th pass; current_pass becomes random permanently once pass 10 completes.

Live state (the scheduler reads and updates this block every run)

current_pass: 1
current_flavor: Fundamentals
pass_cursor: SchedulingQueueingDisciplines/LIFO
  • current_pass — integer 1-10, or the literal string random once pass 10 has completed.
  • current_flavor — derived from the table above; kept explicit here so a run doesn't have to re-derive it.
  • pass_cursor — the full relative path (e.g. Auth/SecretManagement) of the last leaf subtopic this pass processed (written or skipped — see below), in canonical order. A run resumes immediately after this path. (none — pass not yet started) means start from the first leaf in canonical order.
  • When pass_cursor reaches the last leaf in canonical order and that leaf has been processed, the pass is complete: log it (see developer-scheduler), advance current_pass to the next row in the table (or to random after pass 10), reset pass_cursor to (none — pass not yet started), and clear "### Skipped this pass" below (its contents move into "### Revisit log" first — see next section).

Skipped this pass

Leaf subtopics the current pass couldn't clear the depth bar for (no genuinely findable/strong-enough real material for that flavor). Skipping still advances pass_cursor past them — a pass completes even with gaps; it does not block on one weak subtopic. Format: - <path> — <flavor> — <one-line reason>.

  • Compliance/ComplianceChecklists — Fundamentals — 2026-08-26 — no distinct Fundamentals-grade concept beyond a checklist artifact; genuine material here fits the (opportunistic, non-rotation) Checklists flavor instead, and would otherwise duplicate the Fundamentals notes just written for AuditsAttestations/ComplianceFrameworks.
  • DataFlowPatterns/Hybrid — Fundamentals — 2026-08-27 — "combining fan-out/fan-in/pipeline in one real flow" isn't itself a distinctly-named, independently-sourced pattern the way FanIn/FanOut/Pipeline/ScatterGather are; genuine material here would just restate those notes' composition, not add a new concept worth its own Fundamentals-grade sourcing.
  • DataManagement/Caching/CDN-EdgeCache — Fundamentals — 2026-08-27 — genuine CDN/edge-caching Fundamentals material already exists at Networking/CDN/Fundamentals/cdn-and-edge-caching.md (pull/push CDN, origin shield, TTL/soft-purge/surrogate-key invalidation); a second Fundamentals note here would substantially restate that note rather than cover a distinct concept — cross-link instead of duplicating.

Revisit log (across all passes, cumulative)

Every subtopic ever skipped, appended here (with the pass/flavor/date it was skipped) when its pass completes and "Skipped this pass" clears. Not auto-retried — a future pass targeting the same flavor treats a revisit-logged subtopic exactly like any other unwritten one and will attempt it fresh (material may exist now that didn't before), but nothing here is special-cased or prioritized. Use this list for manual review: add a real source by hand, or write the note yourself, whenever you want to close a gap without waiting for the rotation to come back around. Format: - <path> — <flavor> — skipped in pass <N> (<date>) — <reason>.

(none yet)

Sources

Pillars

Cross-cutting tags applied to entries regardless of which topic folder they live in — not the folder structure itself (that's topic-first, see system_prompt). Three vocabularies (craft / design / domain) — see system_prompt's "Pillar tags" section for the full mapping and definitions.

Craft: pillar-languages-runtimes · pillar-testing-quality · pillar-ci-cd-release · pillar-cloud-infra-iac · pillar-observability-debugging · pillar-security-appsec · pillar-collaboration-workflow

Design (from Architecture/): pillar-security · pillar-resilience · pillar-performance · pillar-cost · pillar-operational-excellence · pillar-org-complexity

Domain (added 2026-08-24): pillar-dsa · pillar-grc · pillar-data-engineering · pillar-ai-ml · pillar-frontend-mobile

Topics

  • Language internals (Python, TypeScript/JS, Go)
  • Testing strategy and tooling
  • CI/CD pipelines and release engineering
  • Containers, Kubernetes, IaC (Terraform)
  • Observability, debugging, incident response
  • Application/dependency security
  • Git workflow, code review, dev environment
Hermes Wiki