From idea to a running change — and back
Every change takes the same path: captured in Git, deployed automatically, documented for humans in the wiki and for the AI in the "Second Brain." The loop closes because the AI reads its own knowledge back and assists the next change.
⎇Git as the source of truth
Every compose file and config lives in Forgejo. Edit, commit — whatever is in Git is the valid state. A rollback is a simple "revert" with full history.
📦Dockhand on Unraid
A push triggers a redeploy via a signed webhook (HMAC): Dockhand pulls the new state and restarts the stack — no SSH needed. Dockhand runs as a container on Unraid.
📖Wiki.js for humans
In parallel, the human-readable docs land in the wiki — architecture, runbooks, stack pages. The wiki itself is mirrored back to Git, so it is doubly backed up.
🧠Second Brain for the AI
An AI-curated, Git-backed knowledge store: what happened is logged directly, durable knowledge is proposed by the AI as a pull request — a human reviews and merges. Trust tiers prevent "knowledge pollution."