📖About & Usage

About

Build Cookbook is the rulebook for how Carol's software gets built and deployed. Think of it as the operational law governing the build pipeline — a living reference that defines the standards, steps, and guardrails every piece of code must pass through on its way to production. It belongs to the governance family of apps and is owned by Elrond, Carol's Head of Engineering, who is ultimately responsible for keeping the build process reliable and consistent.

Rather than leaving build knowledge scattered across people's heads or buried in chat logs, Build Cookbook centralises it into one authoritative source. If a developer — human or agent — needs to know how something should be built, packaged, or shipped, this is where they look.

Usage Patterns

Build Cookbook comes into play whenever someone is creating, updating, or troubleshooting anything in the build pipeline. For example, if Forge is wiring up a new service and needs to know the correct build steps, environment flags, or deployment sequence, they consult Build Cookbook rather than guessing or asking around. Similarly, when Elrond introduces a new build rule — say, a mandatory linting gate before any merge — that rule gets codified here so it applies uniformly.

It also serves as the reference point during incident review: if a deployment broke because a step was skipped, the team can check Build Cookbook to confirm what should have happened and where the process diverged. In short, it's the single source of truth for "how we build things," keeping Carol's engineering pipeline predictable and well-documented.

🗂️Tabs & Screens

Tab inventory is being built — see CAROL-INI-077 step 7.

👤Owner

📚Recent initiatives

Initiatives that touched this app — a short summary each; open one for the full story.