Handbook
PDP Follow-up Pack
Architecture target (AFF v0.1). Implementation flags live in implementation-status.md. Do not treat this document as a shipped product contract.
Updated
Architecture target (AFF v0.1). Implementation flags live in implementation-status.md. Do not treat this document as a shipped product contract.
Purpose
Provide a sequence of development questions rather than repeatedly asking the same capability rating.
Question families
| Family ID | Example prompt | Stage | Relationship |
|---|---|---|---|
pdp.goal.target_behavior |
“What specific behavior will be different when this goal is successful?” | setup | self |
pdp.goal.action_commitment |
“What action will you take before the next check-in?” | setup | self |
pdp.goal.action_state |
“What is the current state of the planned action?” | follow-up | self |
pdp.goal.action_learning |
“What happened when you tried the action, and what did you learn?” | follow-up | self |
pdp.goal.blocker_support |
“What support, context, or decision would make progress easier?” | follow-up | self/manager |
pdp.goal.observer_change |
“What change have you observed in the target behavior?” | evidence | selected observer |
pdp.goal.example_impact |
“Describe a recent situation where the changed behavior affected the team, customer, or outcome.” | evidence | self/observer |
pdp.goal.outcome_signal |
“What measurable or observable outcome has changed?” | outcome | self/manager |
pdp.goal.sustainability |
“What will keep this behavior in place after the goal closes?” | closure | self/manager |
pdp.goal.close_confidence |
“How confident are you that the behavior is now sustainable?” | closure | self/manager/observer |
Recurrence policy
- Setup questions are one-time.
- Action-state questions may recur weekly with
skip_periods = 0for up to four active weeks. - Observer-change questions should normally use monthly or quarterly windows.
- Outcome questions should wait until the action has had time to affect outcomes.
- Sustainability questions activate only near closure.
Force-next behavior
When a PDP creates force_next_once for a capability family:
- Reserve one PDP slot in the next survey.
- Select the cadence-appropriate variant.
- Consume the obligation on successful presentation.
- Do not repeat in the same survey.
- Apply the follow-on cooldown configured by the goal.
Safeguards
- Maximum two consecutive surveys may contain the same capability rating by default.
- Action checks may be more frequent than observer ratings.
- A respondent can decline because they have not observed enough change.
- PDP results are not automatically exposed to all tenant administrators.