Agent rule pattern
A written walkthrough of how the system works.
Request lifecycles, data flows, and component boundaries help with cases the rules do not cover. The tradeoff is a longer file.
Follow a request or piece of data through the system. Name who owns each step and why the boundaries exist.
An architecture diagram follows Claude Code through MCP, the CLI, the daemon, and the cloud API. It also shows where terminal and graphical approval interfaces join the flow.
Source excerpt starting at line 32.### Architecture Flow```Claude Code → MCP Protocol → hlyr → JSON-RPC → hld → HumanLayer Cloud API ↑ ↑ TUI ─┘ └─ WUI```
Two ASCII flows show how a diff becomes a review document and how an intent becomes a surface projection. Each stage names the module that owns it and the facts a renderer is to consume rather than recompute.
Source excerpt starting at line 49.parity manifests. Consume them; never re-derive those facts in a renderer.
The ingestion path runs from content detection and extraction through summarization, embeddings, chunking, and space relationships. The sequence shows where each behavior belongs.
Source excerpt starting at line 70.All content goes through the `IngestContentWorkflow` which handles:- Content type detection and extraction- AI-powered summarization and automatic tagging- Vector embedding generation using Cloudflare AI- Chunking for semantic search optimization- Space relationship management
AG-UIDefine the boundary between sequential runs
Agent BrowserDescribe the release-note extraction boundary
AnarlogDesign migrations for the installed older build
BunAccount for arena cleanup semantics
ContinueMake layered hook configuration explicit
Docker MCP GatewayStart with the actors in the connection flow
DuckDBMake the pipeline a navigation procedure
ElectronExplain ownership constraints in the garbage collector
FlueSeparate registration from exposure
FreshThe request lifecycle, numbered
herdrherdrdev/herdr
HumanLayerShow the approval path across processes
hunkThe seam drawn as a pipeline
LanceDBTrace a feature across implementation boundaries
LangflowMake dependency direction explicit
n8nKeep persistence behind domain methods
opencodeanomalyco/opencode
Prisma ORMDescribe the contract flow from authoring to execution
Skills CLIKeep fallback credentials inside GitHub CLI
SupermemoryDescribe the content-processing path
T3 CodeDescribe the event pipeline
TanStack RouterKeep framework-neutral logic separate from bindings
TransformersExplain a value that looks like a mistake
Trigger.devKeep historical paths from reviving retired behavior
VitestSeparate source checking from the output tests execute
ZedExplain why dropping a task changes behavior
HumanLayer 
hunk 
Supermemory