[2026-05-22] taiga sync: .obsidian/community-plugins.json .obsidian/graph.json .obsidian/hotkeys.json .obsidian/plugins/obsidian-git/data.json .obsidian/plugins/obsidian-git/main.js

This commit is contained in:
Тайга
2026-05-22 13:00:45 +00:00
parent 4934fb8249
commit 08142fc8a5
273 changed files with 3814 additions and 12480 deletions
+6 -6
View File
@@ -1,7 +1,7 @@
---
namespace: work
tags: [system, self-modification, eagle, meta]
last_updated: 2026-05-14
last_updated: 2026-04-28
confidence: 1.0
---
@@ -20,7 +20,7 @@ How Eagle (and Alex via Claude Code) can safely evolve the system without breaki
Eagle reads and writes its own prompts. When Alex says "add X to the morning brief" or "change how inbox triage handles Y":
1. Read the current prompt: `~/Developer/personal-os/agent/prompts/<name>.md`
2. Draft the change, show the diff in Zulip
2. Draft the change, show the diff in Discord
3. On confirmation: write the file
4. Commit: `cd ~/Developer/personal-os && git add agent/prompts/<name>.md && git commit -m "[YYYY-MM-DD] prompt: <description>"`
@@ -73,7 +73,7 @@ VALUES (current_date, EXTRACT(WEEK FROM current_date)::int,
### Schema changes (PostgreSQL)
New tables, columns, or indexes require a SQL migration. Pattern:
1. Draft the SQL in Zulip (or Mattermost, post-migration), explain the purpose
1. Draft the SQL in Discord, explain the purpose
2. On "go": run via `psql personal_os -c "..."`
3. Update `~/obsidian/wiki/personal-os-schema.md` (this is auto-generated at 22:00, but a manual update is fine)
@@ -147,6 +147,6 @@ Before making any system change:
## See Also
- [[personal-os-architecture]] — full system map
- [[personal-os-agent-rules]] — Eagle's rules and channel routing
- [[personal-os-purpose]] — why this system exists
- `personal-os-architecture.md` — full system map
- `personal-os-agent-rules.md` — Eagle's rules and channel routing
- `personal-os-purpose.md` — why this system exists