# Context Loading Prompt for AI Agents

Read this file when starting a new session on the dr34m.life docs project. It gives you the lay of the land so you can be immediately useful.

## What is this?

A knowledge base for Jonathan Yankovich's project ecosystem. It covers:

- **Orca** — An Elixir/Phoenix platform for autonomous AI agents with LLM tool calling, personal data extraction, and home automation. The main project. Lives at `../orca/`. ~60% complete on the extraction pipeline.
- **Dream Team** — A Holacracy-inspired organizational model where AI agents hold roles with defined purposes and accountabilities.
- **Physics of Work** — A philosophical framework for understanding work dynamics through stances, polarities, and conversational patterns.
- **Infrastructure** — A homelab with CUDA hosts, MQTT, PostgreSQL, monitoring, and various services.

## The ecosystem

| Repo | What | Status |
|------|------|--------|
| `dr34ming/orca` | Main platform (Elixir/Phoenix) | Active, production at 10.1.2.206:4000 |
| `dr34ming/orca-prompts` | Character definitions (hot-reloaded by Orca) | Active |
| `dr34ming/docs` | This repo — knowledge base | Active |
| `dr34ming/sites` | Public microsites | Active |
| `dr34ming/cuda-services` | GPU inference services | Active |
| `dr34ming/orca_vr` | VR interface for Orca | Development |

## Key architectural decisions

- **No Neo4j** — Graph model uses PostgreSQL with schema.org ontology
- **No Docker locally** — Mac disk space is scarce; containers run on remote hosts
- **Outline is gone** — Wiki migrated here. All `/doc/` links have been converted to relative paths
- **Plane is gone** — Backlog migrated to GitHub Issues (103 in orca, 10 in docs)
- **LiteLLM proxy** — All LLM traffic routes through 10.1.2.30:4000
- **Prompts from filesystem** — Characters defined in `orca-prompts` repo, git-watched for hot reload

## How to work in this repo

- Content is markdown with YAML frontmatter (id, title, collection, created)
- The frontmatter `id` fields are Outline UUIDs — historical, not actively used
- Internal links use relative paths (`../intranet/roles/curious-george.md`)
- All internal links use relative paths

## Jonathan's working style

Read `~/AGENTS.md` for the full partnership guide. Key points:
- Partnership, not service
- Ask before irreversible actions ($2 threshold rule)
- Fix warnings immediately (especially in Elixir)
- No fake data, no slop, no padding
- Commit and push after each meaningful change
- Use agents aggressively for parallel work

## What to work on

Check GitHub Issues: `gh issue list --repo dr34ming/orca`
Check GitHub Issues: `gh issue list --repo dr34ming/docs`
Check GitHub Projects: `gh project list --owner dr34ming`

## Questions to ask Jonathan

If you're picking up this project fresh, these are good orientation questions:
1. What's the current priority — Orca features, data extraction, or documentation?
2. Are there any active branches or in-progress work I should know about?
3. What's the status of the approval workflow / field validation system?
4. Any new services or hosts since the last session?