Skip to content
Enso
Search
Ctrl
K
Cancel
GitHub
Select theme
Dark
Light
Auto
Menu
Architecture
Enso — vision and architecture
Glossary — one word, one meaning
Seams
Seams
Seam: the dialog vocabulary
Seam: the guards
Seam: logging
Seam: the observation vocabulary
Seam: the permission mode
Ported presentation files
Seam: presentation
Seam: storage
Seam: the thread runtime
Seam: the tool result descriptor
Seam: web providers
Flows
Flows
Flow: abort — clear the queue, hand it back, let the settle end the run
Flow: boot and launchers — the manifest, the isolation triple, the print mirror, the vendor links
Flow: a dialog — asked in the host, answered once, settled for every follower
Flow: the follow — snapshot, then frames; held, replayed, live
Flow: a tool call through the guard — one verdict, first block wins, always a record
Flow: prompt → run → settle — admitted on the POST, ended on the follow
Flow: resume — a stored thread, from the rail to live
Flow: a web_search call — route, authenticate, search, fall back, label
Generated reference
Generated flows
HTTP routes
Observation inventory
Core exports
Environment and configuration reference
Code-local decisions
Verification inventory
API reference
Enso — owned contracts
core
src
core/src
core/src/log-process
core/src/paths
core/src/pi-manifest
core/src/secrets
harness
harness/core
Development
Verification
Concepts
Concepts overview
Agent tooling — what earns its place, and what is missing
archive
Archive overview
Agent boundaries — what Claude Code gets right, and where a new harness should start
Agent failure modes, from the inside
Agent support systems — ask-user, todo, memory, advisor, compaction
Magpie — harvest record
Off-the-shelf survey — what covers pi-immediate-needs, and what does not
Harness design principles — what Claude Code gets structurally right
pi — immediate needs
Prompt-cache architecture — the constraint that shapes prompt layering
Provider auth and client identity
GitHub
Select theme
Dark
Light
Auto
Concepts overview
Agent tooling — what earns its place, and what is missing
Harness design principles — what Claude Code gets structurally right
pi — immediate needs
Prompt-cache architecture — the constraint that shapes prompt layering
Provider auth and client identity