SCHEMA — Anthony’s Systems Wiki
Purpose
Help Hermes understand and maintain Anthony’s agents, services, automations, model routing and technical decisions.
Rules
- Do not store passwords, API keys, recovery codes, or private SSH keys. A credentials-map.md records where secrets live; never their values.
- Preserve raw sources unchanged in raw/.
- Update existing pages instead of creating duplicates.
- Every page uses YAML frontmatter and links to at least two related pages.
- Separate facts from procedures: system page = what/where/configured; runbook = how to recover; concept = why; decision = what we chose and why; raw doc snapshots = official source.
- Record important choices in decisions/ with revisit triggers.
- Capture repeatable fixes in runbooks/, not articles.
- Record tests and experiments in experiments/ with explicit verdicts.
- Mark outdated material as deprecated; never silently delete.
- Include dates and version markers on technical instructions.
- Ask before writing more than ten pages at once.
Frontmatter
---
title: Page Title
type: system | infrastructure | concept | decision | comparison | runbook | experiment | query
status: active | experimental | deprecated | unresolved | archived
created: YYYY-MM-DD
updated: YYYY-MM-DD
review_after: YYYY-MM-DD
confidence: high | medium | low
tags: [from taxonomy]
sources: [raw/doc]
---Tag Taxonomy
- systems: hermes, nanobot, router, memory, browser, automation, infrastructure
- content: concept, comparison, decision, runbook, experiment, source
- status: active, experimental, deprecated, unresolved, archived
Freshness
Pages older than 90 days without update should be reviewed.
version_applies_to: and verified_on: should appear on operational pages.