- Authentik -> edge2 CT 105 (Postgres pg_dump/restore; SECRET_KEY carried verbatim; zero-downtime until ~2s cutover) - Multi-block Caddy cutover: auth.echo6.co + notes.echo6.co outpost/forward_auth -> 100.64.0.36:9000 - runbook: add reboot tailscale-before-docker gotcha; clarify dnsmasq must NOT be repointed (points at Caddy host) - source left stopped + intact on Contabo as cold rollback Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Echo6 Vault Tagger — Few-Shot Examples
These examples will be populated from real vault documents during the tagger implementation step (Step 5). Each example should show an input document snippet and the exact JSON output the tagger should produce, demonstrating correct vocabulary usage.
TODO: Add 3–5 real examples drawn from actual vault docs (runbook, reference, project, note).
Template: Example Structure
Input (document snippet)
---
title: Headscale Setup
type: runbook
tags: [mesh, vpn]
updated: 2025-03-10
---
# Headscale Setup
Steps to install and configure Headscale on the Contabo VPS...
Expected JSON output
{
"tags": ["mesh", "vpn"],
"entities": ["contabo", "headscale"],
"glossary_proposals": [],
"type": "runbook",
"confidence": 0.95
}
Notes on this example
tagsuses only values fromtopic_categoriesentitiesmatches names present inentity_lexicon(contabo is a proxmox_vps; headscale is a known service)confidenceis high because type is explicitly set in frontmatter and tags are unambiguous- If the frontmatter had said
type: guide(not in the allowed list), the tagger would inferrunbookfrom the content and note the discrepancy
TODO: Add example 2 — reference doc (host description, multiple entities) TODO: Add example 3 — note/session doc (low entity density, inferred type) TODO: Add example 4 — ambiguous doc with glossary_proposals populated TODO: Add example 5 — doc where confidence drops below 0.6