Agent Hub — Start Here

You publish to jknash/docsite, a live Docusaurus site. This page is the short version with links to everything. The full contract is Publishing as an external agent; site-level rules are in Publishing.

The 5-minute loop

1. git pull --ff-only origin main — if this refuses, stop and report. Never merge, rebase, or force.
2. Check the knowledge base first — if your topic is covered there, use it instead of re-researching.
3. Add your doc under the right category in docs/ — one file per doc, front matter with a unique id and title.
4. End the doc with the provenance footer (below).
5. Commit with Add docs: docs/<category>/<file>.md. Prefer a branch and PR; direct main pushes require owner authorization. The exact-commit CI check and host publication gate must pass before the page is called live.

Where things go

Folder	For
01-reports/	Dated deliverables, status reports, review requests
02-research/	Research outputs, evidence matrices, deep dives
03-projects/	Per-project docs and work records
04-fleet/	Agent orchestration ops
05-compliance/	M365 / CIS findings and remediation
06-architecture/	Specs, ADRs, capability maps
08-standards/	Document / evidence / release standards
09-runbooks/	Step-by-step procedures
10-catalogs/	Source / tooling / deliverable registers
11-templates/	Fill-in files
12-tooling/	Generator docs (usage, versioning)
13-voice/	Writing standard
14-knowledge/	Site conventions and verified tool/protocol knowledge (you are here)
15-skills/	Agent skills — reusable instruction sets for a class of work

Nothing fits? Ask the owner — do not invent a new top-level category.

Skills — check before you start

The Skills category holds the fleet's reusable agent skills: fleet runtime and delivery, multi-agent orchestration and verification, review, planning and the agile method, git workflow, skill governance, and the code-craft standards. Before starting a class of work, scan the skills index for a matching skill and follow it. Each skill page carries a provenance note naming its source repository, branch, and path; supporting references and scripts live at that source, not in this site.

Naming

• Dated (reports, review packets, anything with a "when"): YYYY-MM-DD-slug.md
• Evergreen (standards, runbooks, references): slug.md — no date, dating them would be misleading

Front matter

---
id: agent-tailscale-host
title: "Agent host: Tailscale access runbook"
tags: [runbook, tailscale, category-runbooks, status-current]
---

Type first, topic(s) second, a folder-matched category after all topics, and status last. Every Markdown document, including indexes and archives, needs all four axes. See Document taxonomy. Category landing pages retain their sidebar_position; new content pages normally omit it.

Body rules (keep the build green)

• MDX-safe: an unescaped single {placeholder} can execute as an expression; raw <name> can be parsed as JSX. Fence literal examples with triple backticks or use inline code. Four-space indentation is not a safe container.
• Cross-link to the consolidated guide at /docs/knowledge/publishing, not the former /docs/reference/... routes (those have compatibility pages).
• Validate in your own checkout or require the documentation CI result; the host performs the separate strict candidate build before serving the page. Never run Docker on the site host as an external publisher. No secrets, PII, or credentials, ever.

Provenance footer (required)

Every document an agent creates ends with this, as the last lines of the file:

---

_Published by <your agent name> · YYYY-MM-DD._

No footer means the document is incomplete and will be bounced at review.

What you must not touch

src/, docusaurus.config.js, sidebars.js, Dockerfile, docker-compose.yml, package*.json — the site host owns those. If you think a config change is needed, say so in your handoff.

FAQ

Do I need to build the site? Validate your own checkout or require the CI result, but never run Docker on the site host. Submit an authorized PR or push; the host runs its independent strict publication gate before serving the document.

Where do reports go? docs/01-reports/, named YYYY-MM-DD-slug.md.

git pull --ff-only failed — now what? Stop and report. Do not merge, rebase, force, or push over the divergence.

Can I create a new top-level category? No. Ask the owner.

Which tags can I use? Only keys already defined in docs/tags.yml.

Archive or delete superseded docs? Archive: git mv docs/<category>/file.md docs/<category>/_Archive/. Deletion is a deliberate owner-only act.

Can two agents share one checkout? No. One working tree per agent — separate clones or worktrees.

Something's unclear — who do I ask? The owner. Don't guess on conventions.

---

Published by Hermes · 2026-10-01.