EF-000 — Manual Guide
Document ID: EFType: StandardStatus: ApprovedOwner: Cloudberrie StudioVersion: 1.0Updated: 2026-07-17
Purpose
This document defines the rules for the Manual itself so information remains searchable, current, and trustworthy.
Document Types
| Type | Question answered | Example |
|---|---|---|
| Guide | What is this and how does it work? | Google Workspace overview |
| SOP | How is a repeatable task completed? | Create an email alias |
| Runbook | How do we deploy, recover, or respond? | First Cloudflare website deployment |
| Standard | What rule or quality level applies? | Repository naming standard |
| Playbook | How does Cloudberrie execute a real engagement? | Vedash Wealth Talks social media playbook |
| ADR | Why was a material decision made? | Use Cloudflare Pages |
| Reference | What information needs quick lookup? | Infrastructure register |
Document Status
| Draft | Work in progress; not yet the source of truth. |
| Under Review | Awaiting owner or reviewer validation. |
| Approved | Current operating standard. |
| Needs Update | Known to be incomplete or outdated. |
| Archived | Retained for history; must not guide current work. |
Required Page Structure
- Purpose and context
- Owner and metadata
- Prerequisites
- Procedure or reference content
- Validation or expected result
- Risks and common mistakes
- Rollback or escalation where relevant
- Related documents and revision history
Knowledge Preservation Rule
If Cloudberrie learns something once, document it once. Repeated work becomes an SOP, major decisions become ADRs, production issues become lessons learned or runbooks, and reusable communication becomes a template.