Governance

This page says who looks after the practice, how decisions get made, and how it moves from one steward to a community-run body.

It's meant to be light. A young practice needs a few clear rules, not a constitution.

The steward

Anacay is the steward for now. It supports the practice the way a company supports a foundation: it gives time, hosting and a home on the web, and takes no control over what the practice says. The Support page says what it gives and what it gets.

The steward does:

• hold the domain (cpp.anacay.org), the GitHub repository and the LinkedIn page and group;
• pay for hosting and keep the site running;
• appoint the first editors and confirm new ones;
• enforce the Code of Conduct;
• step in only when the editors can't settle something themselves.

The steward doesn't:

• own the content. It's CC BY-SA 4.0, so anyone can copy, adapt or fork it;
• decide what the body of knowledge says. Editors call consensus; the steward doesn't override them on content;
• use the practice to sell anything. No Anacay services or offers appear in the body of knowledge, the site or the group. Anacay is named only as the practice's supporter and steward (in the footer, on the Support, About and licence pages, and in these founding documents), never with its services. It links to anacay.org, Anacay's page for the open work it supports, not to its commercial site;
• get first or private access to contributions, cases or survey data;
• earn money from the practice. It charges nothing and has no ads, sponsorships or paid tiers.

Editors

Editors keep the loop in HOW_IT_GROWS.md moving. They review edits, call rough consensus, write closing notes, and assemble each edition.

Editors don't get the last word because they're editors. They get it because they read the whole thread and write down why.

At the start, the only editor is the founder, Guillermo Martinez.

Next, we'll recruit a small editorial group of three to five practitioners. We're looking for people who:

• plan, or have planned, capacity for real systems;
• come from different settings: large fleets, AI fleets, cloud, mid-sized companies, supply and finance;
• write plainly and stay patient in a disagreement;
• can give an hour or two a week.

Seniority doesn't matter. A planner two years in, who remembers what was confusing, is as valuable as one with twenty.

How editors are added

1. Anyone can nominate someone, including themselves, in the "Governance" discussion category. A good nomination points to a few useful contributions.
2. The nomination stays open for 14 days. Anyone can comment.
3. The current editors decide by consensus. While there's only one editor, the founder decides and writes down why.
4. The steward confirms. It can only refuse for a Code of Conduct reason, and it has to say so.

Editors serve one edition at a time and can renew. Anyone can step down at any time, no explanation needed. An editor who's been inactive for six months moves to emeritus and is still credited.

Conflicts of interest

Everyone has one. The rule is to say so, and to step back when it matters.

Everyone. When you contribute to something that touches your employer, a client or a product you're paid to sell, say so in the thread. A line is enough: "I work for a cloud provider" or "I consult on this."

Vendors. Vendors are welcome as practitioners. They don't add their products as the answer. The body of knowledge describes methods, not tools. Tools can appear in the reading list or in a neutral comparison, never as a recommendation. A vendor's own employee doesn't edit a passage about that vendor's product.

Employers. Contributors never bring employer secrets (see HOW_IT_GROWS.md). An editor doesn't call consensus on a change that would mainly benefit their own employer or client. Another editor does. Until there is one, such a change waits for the editorial group.

Editors. Editors list their employer, or at least their sector, in EDITORS.md, and keep it current. An editor who proposed a change doesn't call consensus on it. While the founder is the only editor, the single-editor rules in HOW_IT_GROWS.md apply.

The steward. Anacay is an advisory company, and capacity planning is one of the things it advises on. So it has an interest too. That's why it doesn't decide content, doesn't promote its services here, and doesn't hold a majority of editor seats once the group has three or more editors.

The path to a community-run body

There are no dates on this path. Each stage starts when the conditions are met.

Stage 0: Seed (now). Anacay is steward. The founder is the sole editor. The practice runs on the rules in this repository.

Stage 1: Editorial group. Starts when at least three editors are in place, at least two of them unaffiliated with Anacay. Editors decide by consensus. The steward's role narrows to infrastructure and Code of Conduct enforcement.

Stage 2: Community council. Starts after edition 1, once there's a steady base of contributors. Contributors with at least one credited contribution in the last two editions choose a small council. The council owns governance changes, editor appointments and the roadmap. Editors keep their content role.

Stage 3: Independent home. The council chooses a long-term home. That might be a fiscal host, a foundation, or an existing professional body that fits, if one wants it. The steward hands over.

Anyone can propose moving to the next stage in the "Governance" category. Changes to this page follow the 30-day consensus period in HOW_IT_GROWS.md.

How the steward hands over

When the community body is ready, or if the steward can no longer do the job, Anacay will:

1. Transfer the repository to an organization the community controls, with its full history, issues and discussions.
2. Transfer the LinkedIn group by making the community's chosen people admins, then stepping down as owner.
3. Move the address. Help set up a new domain, and redirect cpp.anacay.org to it for at least two years.
4. Hand over the accounts: hosting, email aliases, analytics if any. No data is kept back.
5. Write it down. A short handover record in the repository, saying what was transferred and when.

If Anacay ever has to stop before a community body exists, it will hand the practice to the editors rather than shut it down. The licence already guarantees the content survives any steward: anyone can fork it.

When rules are unclear

Do the open, credited, plain thing. Then write down what you did, so the next person has a precedent.