Advanced~15 minHazelJS
DNA, Store, and Promotion
Multi-DNA packages, change prompt without rewriting tools, and grow from thin starters toward Meridian.
- Authors
- editorial-team
- Published
- Last reviewed
- Name Meridian’s DNA packages and roles
- Promote a prompt change via store → platform → overlay restart
- Describe a staging → prod packageRef story
On this page
DNA, Store, and promotion (F3–F6, F11, F17)
DNA packages (F3, F11)
| Package | Agent | Role |
|---|---|---|
@meridian/support-desk-agent | support-desk | CX + refund HITL |
@meridian/safe-desk-agent | safe-desk | Read-only fallback / twin |
@meridian/api-concierge-agent | api-concierge | Skillgate HTTP skills |
@meridian/fraud-triage-agent | fraud-triage | Risk + freeze HITL |
@meridian/router-agent | ops-router | Intent routing / delegate |
@meridian/helpdesk-agent | helpdesk | RAG policy FAQ (Phase 6) |
Lockfile pins packages under .hazel/agents/ after npm run store:sync.
Change prompt without rewriting tools
- Edit
dna/support-desk.marketplace.json(systemPrompt) — or nested DNA in platform YAML. npm run store:syncnpm run platform:sync- Restart
npm run dev(overlay on). - Chat again — same
@Toolcode, new governed prompt.
Disable overlay with AGENT_OS_DNA_OVERLAY=0 (decorator metadata only).
Related: /guides/design-an-agent-manifest.
On-ramp from thin starters (F17)
Scaffold with agent-os-starter / hazel agent new, then grow toward Meridian patterns (modules, DNA, Store, HITL, Skillgate). Do not pretend the thin starter is the flagship.
Checkpoint E
You can describe a staging → prod story: same packageRef / lock, different env platform overlays, restart to apply prompt/policy.
Artifact: Checkpoint E: staging/prod DNA promotion story
Sources
- Meridian Ops README — hazeljs-meridian-ops/README.md — mental model + quick start
- Meridian TOUR.md — F1–F22 curl walkthrough
- Flagship project plan (21) — docs/agent-os/21-flagship-project-plan.md
- HazelJS Agent OS guide
- HazelJS Agent package