Design Pattern · September 2026

Capability Formation map

Identify which repeated work creates future judgment and replace that learning path before automation removes it.

Under the pillar AI Workforce™, Native Alpha™, and Recomposition

Inputs

Career stages, case exposure, supervision, feedback, error history, competency evidence, and planned automation.

Method

Mark which work builds knowledge, pattern recognition, exception handling, judgment, or credential progression and when repetition stops adding much.

Output

A learning exposure plan using practice, simulation, sampling, review, and graded authority.

Boundary

Routine work should not be preserved ceremonially. Preserve the learning, not the burden.

Stop

Stop removal when future workers lose the cases and feedback needed to become competent.

Put this to work

Capability Formation map application record

Apply Capability Formation map to a real piece of work and record what happened.

For: Operators redesigning a team, service, or AI workforce.
What you keep: A capability formation map application record you can review, revise, and send.
What counts as sound: Names a real setting
Shows the work before and after
Records exceptions
Uses an observable result
Ends with keep, revise, or stop

Do not infer that a task can move merely because it can be described.

Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.

The caseName the organization, setting, product, or piece of work without including confidential information.The decisionWhat must someone decide, and who owns that decision?Evidence in handList records, observations, measurements, rights, or prior work that can be checked.What is still unknownName missing evidence, disputed assumptions, and practical constraints.Future capabilityWhich cases, practice, feedback, and graded authority will replace learning removed by automation?

Review the prompt

Capability Formation map application record 1.0

PURPOSE
Apply Capability Formation map to a real piece of work and record what happened.

CONTEXT
The case: Not provided
The decision: Not provided
Evidence in hand: Not provided
What is still unknown: Not provided
Future capability: Not provided

METHOD
1. Name the work and intended result.
2. Apply the pattern as written.
3. Record what changed and what did not.
4. List exceptions and unintended work.
5. Decide whether to keep, revise, or stop.

TASK
Use the method below to produce a Capability Formation map application record.

RULES
Separate facts, inferences, assumptions, estimates, hypotheses, and unknowns. Do not invent evidence, performance, rights, customers, economics, or regulatory standing. Quote or link the source for material facts. State uncertainty. Name what would disprove the conclusion. End with the smallest credible test, an owner, a decision date, and a stop condition.

A SOUND ANSWER
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop

CAUTION
Do not infer that a task can move merely because it can be described.

You can leave any field blank. The prompt will mark it as not provided.

If the record survives your review, send the question, evidence, unknowns, and requested next step.

Share an apprenticeship risk Intellectual Frontiers on LinkedIn