69 lines
2.6 KiB
Markdown
69 lines
2.6 KiB
Markdown
---
|
||
namespace: work
|
||
tags:
|
||
- wiki
|
||
- schema
|
||
- meta
|
||
created: '2026-05-13'
|
||
updated: '2026-05-13'
|
||
---
|
||
# Wiki Schema — Personal OS Knowledge Base
|
||
|
||
This file defines the domain, structure rules, and curation guidelines for the `wiki/` folder.
|
||
Used by the daily Eagle wiki-curation cron job.
|
||
|
||
## Domain
|
||
|
||
This wiki covers Alex's personal operating system — the tools, workflows, decisions, and architecture
|
||
that run his work and personal life. It is NOT a general knowledge base — everything here must be
|
||
relevant to Alex's specific setup.
|
||
|
||
## Existing Pages
|
||
|
||
| File | Topic | Namespace |
|
||
|------|-------|-----------|
|
||
| `personal-os-architecture.md` | Full system architecture (Eagle, Taiga, Kraken, pipelines) | work |
|
||
| `personal-os-schema.md` | Postgres DB schema (personal_os) | work |
|
||
| `personal-os-purpose.md` | Why the system exists, goals | work |
|
||
| `personal-os-agent-rules.md` | Agent behavior rules and constraints | work |
|
||
| `personal-os-self-modification.md` | How the system evolves and self-improves | work |
|
||
| `personal-os-sync-pipeline.md` | Asana sync, data pipeline internals | work |
|
||
| `personal-os-catchup-plan-2026-04-27.md` | Catchup plan snapshot (April 2026) | work |
|
||
| `personal-os-state-2026-04-27.md` | System state snapshot (April 2026) | work |
|
||
| `ddg-asana-workflow.md` | DuckDuckGo + Asana workflow | work |
|
||
| `obsidian-mcp-wrapper.md` | obsidian MCP / mcpvault setup notes | work |
|
||
| `vault-filling-guide.md` | How to populate the vault | work |
|
||
| `wiki-ingest-process.md` | Wiki ingest pipeline description | work |
|
||
|
||
## Curation Rules
|
||
|
||
1. **One topic = one file.** Never merge unrelated topics.
|
||
2. **Wiki pages are synthesized, not copied.** Summarize, don't paste raw content.
|
||
3. **Update existing pages** rather than creating duplicates.
|
||
4. **Cross-reference** related pages with `[[filename]]` links.
|
||
5. **Frontmatter required** on every page:
|
||
```yaml
|
||
---
|
||
namespace: work | personal | family
|
||
tags: [tag1, tag2]
|
||
last_synced: YYYY-MM-DD
|
||
confidence: 0.0–1.0
|
||
---
|
||
```
|
||
6. **Never delete** pages — mark stale content with `> ⚠️ Stale as of YYYY-MM-DD`.
|
||
7. **Confidence** < 0.5 = speculation, add disclaimer. > 0.8 = verified fact.
|
||
|
||
## What to Curate
|
||
|
||
- Architecture changes (new services, infra decisions)
|
||
- New workflows or agent capabilities
|
||
- Lessons learned from system failures or fixes
|
||
- Updated tool versions, API changes
|
||
- New integrations (Tavily, mcpvault, etc.)
|
||
|
||
## What NOT to Add
|
||
|
||
- Raw task lists (those live in Asana)
|
||
- Personal/family content (those live in `personal/` and `family/`)
|
||
- General knowledge that isn't Alex-specific
|