peterbamuhigire State the procedure's purpose and boundary in one or two sentences.
Use When
- Name a concrete positive trigger.
Do Not Use When
- Name the nearest neighbour and its distinct trigger.
Inputs
| Artefact | Source or provider | Required? | If absent |
|---|---|---|---|
| <upstream skill, user, repository, or source> | yes | Stop or return the named narrow fallback. |
Workflow
- Inspect the inputs and stop if a required artefact is absent.
- Apply the domain decision rules and record the chosen branch.
- Produce the outputs and evidence together.
- Validate acceptance conditions; repair a failed check and rerun it before handoff.
Outputs
| Artefact | Consumer | Acceptance condition |
|---|---|---|
Evidence Produced
| Evidence | Consumer | Acceptance condition |
|---|---|---|
| Release owner | Names the check, result, and unresolved gap. |
Capability Contract
Read access is required. State whether search, edit, execute, network, or delegation is needed. Default audit, critique, analysis, and planning work to read-only. Require explicit authority for mutation, publishing, destructive actions, spending, and certification claims.
Degraded Mode
When a required capability is unavailable, return the narrowest useful qualified result, name the evidence gap, and mark affected checks not assessed; never convert an unassessed check into a pass.
Decision Rules
| Choice | Action | Failure or risk avoided |
|---|---|---|
Quality Standards
- State observable, domain-specific acceptance criteria and release blockers.
Anti-Patterns
- . Fix: .
- . Fix: .
- . Fix: .
- . Fix: .
- . Fix: .
Worked Example
Show a realistic input, the decisive branch, the output, and the evidence that proves acceptance. Do not invent facts to make the example look complete.
References
- Link each required local reference directly, or state that the entrypoint is self-contained.