8Dionysus/aoa-session-progression-lift

aoa-session-progression-lift

Intent

Use this skill to author a PROGRESSION_DELTA from reviewed evidence.

This is not score inflation. It is an evidence-backed overlay that says what mastery axes moved, what should hold or reanchor, and what small unlock hints are now safer.

Trigger boundary

Use this skill when:

• a reviewed session generated meaningful mastery evidence
• the route needs progression legibility without mutating source role profiles
• quest or RPG reflection would help continuation
• the output needs to stay small, evidence-backed, and multi-axis

Do not use this skill when:

• there is no reviewed evidence
• the request wants one global power number
• progression is being used as hidden routing policy
• the route is trying to mint authority rights without evidence

Inputs

• reviewed session artifact or harvest packet
• named evidence refs
• relevant role or cohort context if known
• existing progression baseline if available

Outputs

• PROGRESSION_DELTA with axis movement, verdict, and optional unlock hints
• optional automation-readiness hint when reviewed evidence supports it
• optional rank reflection note if evidence is strong enough
• quest hooks or chronicle stub when useful
• negative or cautionary evidence when a hold, reanchor, or downgrade is more honest than advance
• one PROGRESSION_DELTA_RECEIPT using references/stats-event-envelope.md and references/progression-delta-receipt-schema.yaml
• one CORE_SKILL_APPLICATION_RECEIPT using references/core-skill-application-receipt-schema.yaml

Procedure

1. collect reviewed evidence refs
2. assess movement qualitatively across boundary_integrity, execution_reliability, change_legibility, review_sharpness, proof_discipline, provenance_hygiene, and deep_readiness
3. emit a verdict: advance, hold, reanchor, or downgrade
4. name small unlock hints only when evidence supports them
5. keep any automation-readiness hint small, descriptive, and non-authoritative
6. allow negative, zero, and cautionary movement
7. map ability or feat hints only as reflection, not as ownership transfer
8. emit one PROGRESSION_DELTA_RECEIPT when the delta closes, keeping the receipt descriptive, evidence-linked, and smaller than the progression packet
9. when the finish path closes, emit one CORE_SKILL_APPLICATION_RECEIPT that points back to the bounded progression receipt and records one finished kernel-skill application

Contracts

• progression remains evidence-backed
• multi-axis only; no authoritative universal score
• rank labels are descriptive, not sovereign
• unlock hints must stay reviewable and small
• progression does not replace owner-layer truth or routing authority
• progression does not greenlight automation by itself
• progression receipts stay descriptive and append-only
• generic core receipts stay subordinate to the progression receipt and do not become progression authority
• receipt corrections use supersedes rather than silent overwrite

Risks and anti-patterns

• inventing progress from mood
• using progression as policy
• granting authority without cited evidence
• flattening multi-axis growth into one number
• confusing quest flavor with durable proof
• treating progression hints as if they were approval or schedule rights
• treating a progression receipt as if receipt emission itself proved growth

Verification

• confirm all meaningful axis claims cite reviewed evidence
• confirm the verdict matches the evidence
• confirm zero or negative movement remains allowed
• confirm unlock hints are small and explicit
• confirm no universal score is introduced
• confirm any emitted receipt stays multi-axis, evidence-linked, and non-sovereign
• confirm any emitted CORE_SKILL_APPLICATION_RECEIPT points to the progression detail receipt and stays finish-only

Technique traceability

Manifest-backed techniques:

• AOA-T-0084 from 8Dionysus/aoa-techniques at 5c6f0496edc3c2e74590baa35627c85fe58ef765 using path techniques/agent-workflows/progression-evidence-lift/TECHNIQUE.md and sections: Intent, Inputs, Outputs, Contracts, Validation
• AOA-T-0085 from 8Dionysus/aoa-techniques at 5c6f0496edc3c2e74590baa35627c85fe58ef765 using path techniques/agent-workflows/multi-axis-quest-overlay/TECHNIQUE.md and sections: Outputs, Risks, Validation

Adaptation points

Project overlays may add:

• local axis notes
• role-affinity hints
• local unlock classes