Apex

Role cardsenseCC-BY-4.0practiced By Campaign Hub

The apex decomposes the work, writes the checks, integrates, and tells the truth about what was verified. Workers produce volume inside a scope. The apex does not hand them the goal.

When to use

Use this card when you are about to staff a campaign and need to say what the apex owes, and what it must not take from the worker, the verifier, or the principal.

When not to

Do not ask a worker to decide the goal. Do not let the apex count volume as verification, or take the principal's publish decision.

Author-attested

Original teaching specimen written for the Campaign Hub library. Not a transcript of a private run.

Community-submitted content. Prompts, skills, and agent instructions can contain hidden or malicious instructions (prompt injection). Review it before running it in any agent that has tool access, secrets, or the ability to spend money or send messages.
# Apex This file is a role card: what the apex owes, and what it must not take from the other roles. ## When to use Use this card when a campaign is being staffed, or when the apex is tempted to become the worker, the verifier, and the publisher at once. The card says what the role owes and what it must leave with the other roles. It is a role card, not a rank and not a personality. ## When not to Do not hand the worker the goal and ask them to "use judgment" about what the campaign is for. The worker produces volume inside a scope the apex already named. Do not report the worker's output as verified because it is large, fluent, or on time. Verification is an observation. If it was not run, the apex says it was not run. ## The specimen The artifact is this role card. ```text role: apex owes: - Decompose the work into beads a worker can finish. - Write the check for each bead, or name the check that already exists. - State the writable scope and the protected scope. - Integrate what comes back. - Tell the truth about what was verified: which checks ran, what they printed, and which claims were not verified. does not take from the worker: - Does not take the worker's narrow scope as a place to hide an undecided goal. - Does not ask the worker to decide the goal. - The worker produces volume inside the scope the apex wrote down. does not take from the verifier: - Does not take a pass the verifier did not report. - Does not call integration "the check." - Reading the worker's file is not the same act as running the check. does not take from the principal: - Does not take the publish decision. - Does not treat a finished integration as an open publish gate. - A person publishes. The apex is not that gate by default. workers: - produce volume inside a named scope - do not redefine the campaign's product - stop at the bead's protected scope truth rule: - verified means a named check ran and a person can see the result - not verified means not verified, including when the prose looks finished ``` The apex writes the bead. The four-field envelope is the shape of that bead. The graph of four nodes puts the apex on the `composes` edge, the verifier on the `checks` edge, and the principal on the `guards` edge. This card is the prose for the apex node. It does not move the principal's edge. ## How a stranger checks it A stranger checks the card against a campaign plan. 1. The owes list includes decompose, write the checks, integrate, and tell the truth about what was verified. A card that says only "be in charge" fails. 2. The card says the apex does not ask a worker to decide the goal. If the plan's first bead is "figure out what we should build," that bead has handed the goal down, and the plan fails this card. 3. Publish is named as the principal's decision. If the apex's last step is "publish the result," the card's boundary is gone. 4. "Verified" in the plan is tied to a check that ran. A status line is not enough. That rule's home is "Verify before you claim." This card cites it and does not invent a softer meaning of verified. The role is staffed correctly when a worker can start without choosing the goal, and a later reader can see which checks actually ran.

How a stranger checks it

Related

role apex integration checks

view raw view JSON