echo6-docs/engine/prompts/fewshot.md
Matt Johnson 44f0257376 docs: migrate Authentik (SSO keystone) to edge2 CT 105
- 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>
2026-06-18 05:49:07 +00:00

52 lines
1.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# 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 35 real examples drawn from actual vault docs (runbook, reference, project, note).
---
## Template: Example Structure
### Input (document snippet)
```markdown
---
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
```json
{
"tags": ["mesh", "vpn"],
"entities": ["contabo", "headscale"],
"glossary_proposals": [],
"type": "runbook",
"confidence": 0.95
}
```
### Notes on this example
- `tags` uses only values from `topic_categories`
- `entities` matches names present in `entity_lexicon` (contabo is a proxmox_vps; headscale is a known service)
- `confidence` is 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 infer `runbook` from 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