---
title: Agent Workflows
created: 2026-06-16
updated: 2026-07-09
type: namespace-overview
status: active
category: agents
namespace: agent-workflows
confidence: medium
---

# Agent Workflows

> Operational namespace for Jamie's Pixoid crew workflows: route governance, durable context, agent entrypoints, verification gates, and markdown-first agent memory.

## Scope

### Covers

Pixoid/Tinker/Quill/Boba operating model, Hermes Mission Control, route governance, memory boundaries, context handoffs, Knowledge Pack Routing, agent entrypoint meshes, static retrieval/eval gates, self-improving agent systems, effective-state-load boundaries, and workflow reliability practices.

### Not Covered

Product case studies except where they demonstrate agent workflow mechanics; low-level local AI infrastructure unless it affects workflow execution; public wiki publishing mechanics except where they define agent routing contracts; Daily Notes scratch chronology unless explicitly promoted into durable source notes.

### Current As

2026-07-09 — Added the Eve-derived Agentic Harness Engineering pattern: build agents as inspectable runtime harnesses with explicit capability slots, trust boundaries, durable sessions, channels, sandboxing, and eval gates.

## Canonical Source Roots

- `Projects/Effective State Load/Index.md`
- `Projects/Hermes Mission Control/Index.md`
- `Projects/Hermes Mission Control/PRD - Knowledge Pack Routing.md`
- `Projects/Hermes Mission Control/PRD - Knowledge Pack Routing V2.md`
- `Projects/Hermes Mission Control/Knowledge Pack Contract V1.md`
- `Projects/Hermes Mission Control/KPR Static Retrieval Eval - 2026-06-15.md`
- `Projects/Hermes Mission Control/kpr-pixoid-routing-rule.md`
- `Knowledge/concepts/self-improving-agent-systems.md`
- `Knowledge/concepts/profile-memory-boundaries.md`
- `Knowledge/concepts/runtime-memory-knowledge-routing.md`
- `Knowledge/concepts/agent-skill-routing.md`
- `Knowledge/concepts/agent-tooling-plan.md`
- `Knowledge/concepts/agentic-harness-engineering.md`
- `Knowledge/concepts/effective-state-load.md`
- `Knowledge/concepts/reader-centered-outreach-asks.md`
- `Knowledge/concepts/compound-engineering-skill-layer.md`
- `Knowledge/concepts/hermes-capability-routing.md`
- `Knowledge/concepts/high-agency-work-levels.md`
- `Knowledge/concepts/creative-ideation-routing.md`
- `Knowledge/concepts/interaction-mode-routing.md`
- `Knowledge/concepts/peer-profiles-vs-child-processes.md`
- `Knowledge/concepts/multi-agent-multiplayer-boundaries.md`
- `Knowledge/concepts/ponytail-minimal-code-discipline.md`
- `Knowledge/concepts/visual-plan-review-surfaces.md`
- `Knowledge/concepts/matt-pocock-skills-best-practices.md`

## Routing Rules

- Primary namespace: `agent-workflows` for crew operating model, KPR, entrypoint meshes, and route/eval workflow practices.
- Also relevant to `pixi-vault` when namespace compiler or publishing boundaries change.
- Also relevant to `eval-trace` when workflow quality, route failure modes, or static eval gates are being evaluated.
- Use primary namespace plus crosslinks. Do not duplicate pages across namespaces unless the page is rewritten for a different user job.

## Public Output Contract

When published to `pixi-wiki`, this namespace should expose:

```text
/raw/agent-workflows/README.md
/raw/agent-workflows/wiki/index.md
/wiki/agent-workflows/README.md.html
/wiki/agent-workflows/wiki/index.md.html
/wiki/agent-workflows/assets/reports/esl-full-report.html
```

## Maintenance

- Edit canonical source notes first.
- Use `Wiki Compiler Maps/Namespace Wiki Compiler Map.md` for routing decisions.
- Do not compile Daily Notes directly unless promoted or verified.
- Update `wiki/index.md` and `wiki/log.md` whenever compiled pages are added.