Cases and evidence
Read field cases, pilots, validation records, and reference mappings with their evidence status made explicit.
This section shows how Adaptive Skills has been tried, reviewed, or mapped in real and bounded contexts. These records help readers judge maturity; they do not automatically become canonical guidance.
How to read the evidence
| Label | Meaning | What you may conclude |
|---|---|---|
| Field case | Skills were used in real project work with traceable context | The documented pattern was useful in that context |
| Pilot | A bounded trial tested a specific question | The stated hypothesis received limited support or rejection |
| Validation record | A contract, compatibility rule, or behavior was checked | The checked condition held for the recorded scope |
| Reference mapping | External material was compared with the library | Similarities and gaps were identified; no automatic adoption |
| Synthetic example | A constructed scenario explains a pattern | The pattern is understandable, not proven in production |
Always read what the record did not prove before generalizing a result.
Field cases
The Crisis Monitor case study documents two real product-work rounds and the separation among macro governance, micro execution, and consumer-local rules.
The Docs as runtime corpus — Crisis Monitor field case records a later documentation pilot where Blume user docs also became a versioned, validated corpus for the Cris assistant.
The Pulso pilot records a bounded use of design-system-intelligence against declared source material. Pattern promotion remains outside the skill’s authority.
Efficiency-layer evidence
- Crisis Monitor reference — project-specific reference record.
- First pilot — bounded pilot record.
- Pilot checklist — evaluation aid, not evidence by itself.
Validation and reference material
- Engineering skills hardening pack — compatibility and hardening guidance.
- Engineering skills reference map — external reference mapping.
Evidence boundaries
A record here does not promote a candidate, prove universal effectiveness, replace canonical SKILL.md, grant decision authority, or make synthetic examples equivalent to field evidence.
Next steps
- Read Current state before interpreting maturity.
- Read Evolution to understand how evidence can become a proposal.
- Use Validation case guidelines when creating a record.