2.2 KiB
22 — Brand, naming and product copy
Working name
DevRunbook
Use as a working product name. Domain, trademark and company-name clearance are not part of this specification and must be completed before public launch.
Descriptor
Verified playbooks for agentic development
Primary tagline
From intent to verified change.
Alternative taglines
- Build the task before the agent builds the code.
- Reusable development workflows, adapted to every repository.
- Give coding agents a better contract.
- Compose. Constrain. Verify.
Positioning statement
DevRunbook is a self-hostable playbook platform for developers and technical operators who use coding agents. It transforms a task, repository profile and validation policy into a precise, reusable and inspectable execution contract.
Messaging pillars
Repository-aware
Reuse real commands, stacks, protected paths and policies.
Safe autonomy
Choose exactly how far the agent may go and how it must recover from failure.
Verifiable output
Every implementation task includes checks, completion criteria and a final evidence report.
Versioned quality
Playbooks have versions, lifecycle, evaluations and transparent limitations.
Self-hosted trust
Keep private playbooks and repository context under operator control.
Vocabulary
Use:
- Playbook
- Repository profile
- Composition
- Generated run
- Run Pack
- Validation
- Guardrail
- Evidence
- Provenance
- Lifecycle
Avoid:
- magic prompt;
- one-click perfect code;
- guaranteed fix;
- autonomous employee;
- AI brain;
- prompt engineering secrets.
Example homepage copy
Hero
Give Codex a better task.
Turn a bug, audit, cleanup or feature request into a repository-aware playbook with explicit scope, guardrails, validation and a definition of done.
Primary action: Explore playbooks
Secondary action: Create repository profile
Trust strip
- Deterministic composition
- Git-versioned playbooks
- Read-only Gitea integration
- Self-hostable by design
Composer callout
See where every instruction came from.
DevRunbook separates platform safety rules, playbook logic, repository facts and your current choices—so the final task remains understandable before it reaches Codex.