Skip to content

v0.8.0 - Learn by example

Choose a tag to compare

@jprisant jprisant released this 13 Jun 06:28
· 7 commits to main since this release
650e3a0

Learn by example: watch the frameworks work on real decisions, and see the numbers behind the claims.

This release adds the part a newcomer most wants - proof. You can now watch real decisions worked end to end, see real prompts in the styles people actually type, and read the measured evidence that the library routes and produces what it promises. No new frameworks; the catalog stays at 56. This is a documentation and trust release.

For everyone

  • A Showcase of real decisions, prompt to finished artifact. Three people work hard problems start to finish: a founder deciding fast, an engineer making an architectural call, and a policy analyst deliberating on paper. Each page shows the exact prompt typed and the full artifact it produced - a ranked risk register, a weighted option matrix, an argument map, a stakeholder trade-off grid - so you can judge the quality before you run anything. Sixteen worked journeys, including full recipe chains and runs done entirely by hand.
  • "Does this actually work?" - we measured it. A new page publishes the behavioral-eval results: the catalog routes the right framework for a situation 99% of the time with zero false-fires across 561 cases, and the artifacts meet their own quality bar on 99% of 315 checks. It also says plainly what the numbers do not prove.
  • A prompt gallery, so your messy prompt is fine. Real prompts in three styles: a one-line casual ask, a structured block, or just describing the mess to the advisor. A sparse prompt produces the same complete artifact as a polished one, because the framework does the structuring.
  • An operating guide. "Using the frameworks" takes you from running one framework to chaining several like a power user.

For builders

  • The example surfaces are hand-authored pages on the existing Astro Starlight site; nothing about the install surface, the skills, or the manifests changed (the manifest diff is version-only).
  • The behavioral-eval harness is reproducible and runs without an API key (scripts/eval/); every number on the trust page traces to a committed JSON you can audit.
  • Catalog-count drift is now a hard CI failure: the count gate was extended to the repo-facing docs and the README prose counts.

Full notes: RELEASE-NOTES.md. Technical detail: CHANGELOG.md.