jarvis-at-skic
68fc65e685
- New file: workstreams/backup-solution.md - DLM explanation: what it is, how it works, vs AWS Backup - EC2/compute backup Q&A: AMI vs EBS snapshot, stateful vs stateless matrix - Document gaps checklist (rename, DLM policy spec, golden AMI strategy, etc.) - Updated vssa-dpvp.md: note linking to backup-solution.md - Updated README.md: added backup-solution to workstreams index
36 lines
1.6 KiB
Markdown
36 lines
1.6 KiB
Markdown
# 🧠 Knowledge Wiki
|
|
|
|
> Automatically maintained by **Hermes** — synced every 4h from Discord channels.
|
|
> Last sync: see [brain.md](brain.md)
|
|
|
|
## Workstreams
|
|
|
|
| # | Workstream | File |
|
|
|---|-----------|------|
|
|
| 🔵 | VSSA — Digital Platform Value Proposition | [workstreams/vssa-dpvp.md](workstreams/vssa-dpvp.md) |
|
|
| 🔵 | AWS Backup Solution (DPVP) | [workstreams/backup-solution.md](workstreams/backup-solution.md) |
|
|
| 🟡 | VSSA — Enterprise Architect Consultancy | [workstreams/vssa-enterprise-architect.md](workstreams/vssa-enterprise-architect.md) |
|
|
| 🟢 | Cognitive Architect | [workstreams/cognitive-architect.md](workstreams/cognitive-architect.md) |
|
|
| 🟣 | SAP Delivery Powered By AI | [workstreams/sap-delivery.md](workstreams/sap-delivery.md) |
|
|
| 🏅 | Distinguished Engineer | [workstreams/distinguished-engineer.md](workstreams/distinguished-engineer.md) |
|
|
|
|
## Meta
|
|
|
|
| File | Purpose |
|
|
|------|---------|
|
|
| [brain.md](brain.md) | Live summary — status across all workstreams |
|
|
| [meta/infrastructure.md](meta/infrastructure.md) | Services, endpoints, platform health |
|
|
| [meta/discord.md](meta/discord.md) | Discord channels, bots, config |
|
|
| [meta/hermes-setup.md](meta/hermes-setup.md) | Hermes migration history & status |
|
|
| [meta/behavior.md](meta/behavior.md) | Operating rules & conventions |
|
|
|
|
## How this works
|
|
|
|
Hermes runs a cron job every 4 hours that:
|
|
1. Reads new messages from 5 Discord channels
|
|
2. Extracts decisions, action items, contacts, status changes
|
|
3. Updates the local wiki files under `/opt/data/wiki/`
|
|
4. Commits and pushes all changes to this repo
|
|
|
|
Every update is a Git commit — full history of the wiki is preserved here.
|