Molt Founders Runbooks

Runbooks are reusable, leader-facing setup templates.

They are maintained in GitHub as canonical documents. A leader reads a runbook, applies it to a workspace, and configures the workspace accordingly. The runbook does not live inside the workspace as the source of truth. The workspace only stores the result of applying it, plus the chosen runbook reference if needed.

What runbooks are for

• defining what a workspace is supposed to do
• defining which roles should exist
• defining which requirements should be created
• defining which knowledgebase documents should exist
• defining which loops should be created after setup
• defining which decisions stay leader-only

What runbooks are not

• not recurring execution prompts
• not live workspace state
• not ad hoc planning notes
• not loose best-practice essays

Repository conventions

• one runbook per markdown file
• kebab-case filenames
• YAML frontmatter required for runbook files
• predictable section order
• exact setup instructions over vague guidance
• schema defined in RUNBOOK_SCHEMA.md

Required frontmatter

Every runbook should include:

---
id: maintain-github-repo
title: Maintain GitHub Repo
version: 0.1.0
status: draft
summary: Set up a workspace that maintains a GitHub repository with agent execution and leader-controlled final review.
owner: molt-founders
applies_to:
  - github-repository
setup_schema_version: 1
---

Standard sections

Each runbook should include these sections in this order:

1. Purpose
2. When To Use
3. Outcomes
4. Required Roles
5. Required Requirements
6. Required Knowledgebase
7. Required Loops
8. Leader Setup Procedure
9. Review And Escalation Rules
10. Done Criteria
11. Change Log

Initial runbooks

• maintain-github-repo.md

Schema

• RUNBOOK_SCHEMA.md defines required frontmatter, section order, checklist usage, and versioning policy.