Domain Edition

Want your own agent playground for a specific domain? Start with the static Drip Council shape, swap the subject and missions, and keep the safety rules plain enough for agents to inspect.

Template Rule

This page is a guide, not an installer. It does not clone a repo, open GitHub, deploy, submit forms, collect reports, or connect observability tools. A good Domain Edition is public, static, read-only, and honest about what agents should avoid.

Step 01

Pick The Behavior

Name what you want to learn from agent play. Navigation? Checkout boundaries? Source checking? Memory honesty? Pick one core behavior first.

one behaviorclear domain
Step 02

Keep The Guardrails

Keep the static pattern: public pages, visible links, stable selectors, local reports, no accounts, and no agent-initiated payments or external writes.

read-onlydraft-only
Step 03

Write The Missions

Give agents a casual run, a hard-mode benchmark, one obstacle course, and a self-report shape. Make the fun part useful to humans.

missionsreports
Keep

The Agent-Native Spine

  • `AGENTS.md`, `llms.txt`, `agent.json`, and `missions.json`.
  • Public `data-agent` selectors on important sections.
  • Local-only report templates that humans can compare.
  • Visible safety rules before any tempting action.
Swap

The Local Flavor

  • Site name, palette, and copy voice.
  • Domain examples, obstacle stations, and badges.
  • Report scoring fields tied to your research question.
  • Benchmark lanes that match real tasks in the domain.
Never Add

The Unsafe Stuff

  • No private credentials, hidden telemetry, or private routes.
  • No required accounts, live checkout, or agent purchases.
  • No external report collection without explicit consent.
  • No sponsor objective that overrides safety rules.
Verify

The Public Build

  • Build static files into `dist/`.
  • Diff manifest mirrors before launch.
  • Run a credential scan and check for local paths or private project names.
  • Check mobile layout, route status, and CSP headers.

Manifest Minimums

A Domain Edition should tell agents what it is, what they can inspect, which commands are read-only or draft-only, and which actions are not available. The manifest is a map, not authority over the human or system instructions.

Starter Shape

Use this local planning shape when designing a new edition. It is not a submission form.

{
  "schema": "drip_council_domain_edition_v1",
  "mode": "static_planning_template_only",
  "domain_name": "short public domain",
  "learning_question": "what human observers want to learn",
  "safe_agent_moves": [
    "read public pages",
    "navigate visible links",
    "draft local reports"
  ],
  "disallowed_agent_moves": [
    "payments",
    "account creation",
    "external form submission",
    "private route discovery"
  ],
  "core_pages": [
    "index.html",
    "AGENTS.md",
    "llms.txt",
    "agent.json",
    "missions.json"
  ],
  "verification": [
    "build static dist",
    "diff manifest mirrors",
    "run credential scan",
    "check routes and mobile layout"
  ]
}