Skip to main content
reopt Handbook
reopt Handbook
Enterprise Eve Agent Development

Core Architecture

Ch1. Eve Mental ModelCh2. Source Code AtlasCh3. Project Layout and DiscoveryCh4. Compiler and Runtime Graph

Agent Quality Design

Ch5. agent.ts, Models, CompactionCh6. Context, Skills, Dynamic CapabilitiesCh7. Tools, Approval, ConnectionsCh8. Sandbox Secure Runtime

Operational Runtime

Ch9. Channels, Auth, StreamingCh10. Subagents, Workflows, Remote AgentsCh11. Schedules, State, HooksCh12. Evals and Quality Gates

Production Operations

Ch13. Observability and DeploymentCh14. Enterprise PatternsCh15. Migration and Governance

Appendix

Official Docs CrosswalkVerification ReportUpdates
Handbook›엔터프라이즈 Eve 에이전트›Ch3. Project Layout and Discovery
한국어English

Ch3. Project Layout and Discovery

How Eve turns agent directory slots into a source manifest, and why path-derived identity is an operations contract.

Key takeaways

  • agent/ is a declarative interface for context, authority, and execution capability.
  • Discovery derives identity from paths, so filenames become operational contracts.
  • Root agents, subagents, instructions, skills, and tools should be separated at the folder boundary first.

In Eve, agent/ is not just a folder. It is the interface that declares what the agent is, what it can see, and what it can ask the runtime to do.

Root Resolution: Nested And Flat

Eve supports a recommended nested layout and a flatter form.

LayoutShapeRecommendation
nestedapp root contains agent/Preferred for production apps
flatcurrent directory itself contains agent.ts, instructions.md, tools/Useful for small experiments

Recommended structure:

my-agent/
├── package.json
├── agent/
│   ├── agent.ts
│   ├── instructions.md
│   ├── tools/
│   ├── skills/
│   ├── connections/
│   ├── channels/
│   ├── sandbox/
│   └── subagents/
└── evals/

Slots Discovery Reads

SlotRoot agentSubagentPurpose
agent.tsyesyesmodel, output schema, compaction, experimental flags
instructions.md / .tsyesyesalways-on prompt
tools/*.tsyesyesauthored actions
skills/**yesyesload-on-demand procedures
connections/*.tsyesyesexternal MCP/OpenAPI tools
sandbox/**yesyesworkspace and backend config
hooks/**yesyesstream-event hooks
channels/**yesnoinbound delivery surfaces
schedules/**yesnocron or scheduled work
subagents/**yesnested local agentsdelegation units

Path-derived Identity

PathDerived identity
agent/tools/refund_charge.tsrefund_charge
agent/connections/linear.tslinear
agent/skills/release/SKILL.mdrelease
agent/subagents/reviewer/agent.tsreviewer

Names are public contracts. They appear in evals, traces, approval logs, and model behavior. Rename with the same care you would use for an API endpoint.

Diagnostics Are Release Artifacts

Discovery and compilation produce diagnostics when files are in the wrong slot, missing default exports, or shaped incorrectly. Treat .eve/diagnostics.json as release evidence.

DiagnosticAction
tool not discoveredverify file path and default export
subagent missing descriptionadd description to child agent.ts
schedule under subagentmove to root agent
unexpected skill layoutnormalize SKILL.md location

Instructions Strategy

Use instructions for stable identity and policy:

  • role and scope
  • safety and escalation rules
  • answer style
  • allowed and forbidden behavior
  • when to use skills or tools

Do not place every procedure in always-on instructions. Long task procedures belong in skills/.

Skills As Progressive Disclosure

Skills are procedure memory. A good skill description is a routing contract for the model.

Good skillPoor skill
"Release checklist for production deployment incidents.""Useful notes."
"Refund escalation policy for billing support.""Support stuff."

Use skills for long playbooks, team policies, domain procedures, and operational templates.

Subagent Boundaries

agent/subagents/<id>/agent.ts defines a child agent root. Declared subagents do not inherit the root agent's tools, skills, sandbox, or state by default. This makes them valuable security and quality boundaries.

Example split:

SubagentCapabilities
researcherread-only docs and warehouse connections
operatorapproval-gated write tools
reviewerstructured risk output schema

Discovery Checklist

AreaStandard
file namesstable, descriptive, risk-visible
toolsone capability per file, scoped inputs
skillsclear descriptions, no secrets
connectionsallow/block filters and approval documented
channelsroot-only, explicit auth
subagentsdescription, model, tools, and sandbox reviewed
diagnosticsclean before release

Related docs

Verification

Advanced Codex Usage · A checklist for validating advanced Codex team operations.

Custom commands and skills

Claude Code Command Master · Choose the commands for custom commands and skills and follow their availability rules and concrete examples.

Runbooks and Operations

Agentic Documentation · Design runbooks that separate diagnosis, recommendation, action, approval, and rollback.

Ch4. Compiler and Runtime Graph

How Eve transforms source manifests into compiled manifests and runtime agent graphs.

Ch6. Context, Skills, Dynamic Capabilities

Design context, skills, dynamic tools, dynamic instructions, and dynamic skills for high-quality Eve agents.

Ch2. Source Code Atlas

Read packages/eve/src by implementation responsibility and identify the files enterprise reviewers should understand.

Ch4. Compiler and Runtime Graph

How Eve transforms source manifests into compiled manifests and runtime agent graphs.

On this page

Root Resolution: Nested And FlatSlots Discovery ReadsPath-derived IdentityDiagnostics Are Release ArtifactsInstructions StrategySkills As Progressive DisclosureSubagent BoundariesDiscovery Checklist