Design Pattern · September 2026
Preserve, Amplify, Encode, or Reject
Choose how to handle a claimed differentiated capability after testing what makes it valuable.
Under the pillar AI Workforce™, Native Alpha™, and Recomposition
Inputs
A capability claim, outcome evidence, peer comparison, automation test, learning path, relationships, and rights.
Method
Preserve direct human work when presence creates value. Amplify it by removing surrounding burden. Encode only what can be governed without losing the source. Reject false differentiation.
Output
A disposition with evidence, owner, rights choice, and review date.
Boundary
The four choices can coexist across parts of one capability.
Stop
Stop encoding when it weakens trust, learning, control, portability, or the advantage itself.
Put this to work
Preserve, Amplify, Encode, or Reject application record
Apply Preserve, Amplify, Encode, or Reject to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A preserve, amplify, encode, or reject 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.
Review the prompt
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.