You already work this way. Over seven weeks we named the five layers underneath it — governance on the floor, the quality gate on top.
Preston Magouirk · DC CAP Enterprise AI Leadership Pilot · How it all connects.
Every week added a piece. In Week 2 we named the four competencies. In Week 3, the things you build. In Weeks 5 and 6, how you check the work. In Week 7 we put them together. Stack the pieces and you have the system this deck walks through — and you have been using it all along.
The four data tiers. The floor every other layer sits on. Classify before you upload.
Delegation, Description, Discernment, Diligence. The competencies underneath every move.
Automation, Augmentation, Agency. How the human and Claude split the work.
Prompt, Skill, Project, Agent. What you build, and what becomes reusable.
How you know the output is good. Week 6's verification set — Diligence, made into a checklist.
You start here every time. Before you write a prompt or open a Project, you classify the data. You use the four tiers to decide what Claude may see. When you are unsure, you move up one tier and treat the data as more restricted.
Student PII, FERPA records, SSNs, financial-aid detail. Stays out, no exceptions.
Budget data, staff evaluations, partner-confidential, small-cell aggregates under 10.
Strategy docs, grant narratives, program models, de-identified aggregates.
Published materials, public data. No restriction on use.
The governance framework on the hub holds the full tier definitions and the incident-response path. This is the question that comes before every other question in the system.
Every time you work with Claude, you draw on four skills. Name the ones the task needs, and you know where to put your attention.
Decide which part of the work goes to Claude and which stays with you. The judgment about division of labor.
Spec the work precisely — the goal, the context, the format, the constraints. The prompt and the Project instructions.
Judge the draft in real time. Catch where it is thin, off-voice, or wrong before it goes anywhere.
Check the claims, the numbers, the sources. The discipline that becomes the eight questions in Layer 5.
Adapted from the Anthropic 4D framework (Dakan & Feller, 2025). These are the named pieces of fluency — every higher layer is built from them.
The three modes are built from the four D's. Each mode is a different balance of human judgment and Claude's output — and each draws on a specific pair of competencies.
The bar shows the balance of execution. In Agency the human share looks small because the work has moved up front — the judgment lives in the process the designer wrote.
Four containers, one ladder. Each one makes a different thing reusable. Every higher container holds the lower ones, so moving up is cheap. Start at the bottom and promote only when the work demands it.
One person, one task, one time. The move lives in your head.
Same procedure, varied inputs. The team runs your best version every time.
Same body of knowledge, varied asks. Files, instructions, and governance in one workspace.
Cadence or event-driven, across roles, with an audit trail. Also called an orchestration — the build that puts you in Agency mode (Layer 3).
Default to the smallest container that survives the job. Most pilot builds land at Stage 2 or Stage 3 — that is the right call. The two highlighted containers are what each unit makes available this week.
Diligence turns into a checklist. These are Week 6's eight verification questions — the ones every new user asks the first time Claude lands a confident, wrong answer. You met the mechanics behind them in Week 5 and the build-questions in Week 7; this set is the quality gate. Run them on every container before anything leaves the workspace.
Why does Claude hallucinate?
Why does it sound confident when it's wrong?
Where is Claude most likely to be wrong?
What is context overload?
Why do my earlier rules fade?
What manual checks should I always run?
How do I ground Claude in real sources?
How do I build verification gates into the workflow?
Question 3 names the five danger zones: names, numbers, dates, citations, and your world. Those are the first places to check, every time.
Take a real task — a quarterly update to a university partner. The same five layers run, in order, whether you write it once or build it for the team.
Over these two weeks, each of the six units builds and shares at least one Skill and at least one Project in Claude Enterprise. No one turns anything in. The bar is simpler: a teammate opens it and uses it, ideally anyone in the org.
Take the move your unit makes again and again and write it down once — the steps, the standards, the voice. The team loads it and gets your best version every time.
Bundle your unit's working knowledge into one Claude Project — the files, the instructions, the data-tier rules. Anyone on the team produces a strong first draft against shared context.
These are the two team-horizon containers from Layer 4. One packages your best move. One packages your shared context. Both pass the eight questions and carry a governance line before you share them.
The pairing maps straight to the ladder. A Skill and a Project are the two containers that live at the team horizon, and together they cover what a team actually reuses.
A Skill carries how your team does something. A Project carries what your team works from. Build one of each and you have covered both halves of repeatable work.
The move that lived in one person's head becomes a Skill anyone can run. The context scattered across folders becomes a Project anyone can open. The unit keeps working when someone is out.
We named this the team horizon back in Week 2. A personal prompt sits at H1. An agent that runs across roles sits at H3. A Skill and a Project are what make the whole team faster — the realistic win for a 60-day pilot.
The three-horizons frame from Week 2 closes the loop. Each build lives at one horizon. This week, every unit plants something at H2 — the level where the whole team inherits the work.
The Monday-morning prep, the prompt you run every week. Where most Stage 1 work belongs, on purpose.
What every unit makes available this week. Your team loads the move and opens the context. The pilot's center of gravity.
The financial_modeling orchestration, the AI Development Office pipeline. Rare, and a year in the making. The Ship It deck walks one live.
This is
how we work now.
Governance on the floor. The four D's, the three A's, the four containers, the eight questions stacked on top. You run the whole thing every time you open Claude, and now you can name each layer. Build the two containers your team will use, make them available, and tell me where they break.