Rituals pattern: run result with lineage seal #188

New issue

Open

opened 2026-10-04 20:20:36 +00:00 by peterswimm · 0 comments

peterswimm commented

2026-10-04 20:20:36 +00:00

Owner

Part of #177.

What it's for: a ritual has finished. Show the result together with its proof (the lineage record and hash), its rubric score and a quick feedback prompt, laid out the same way everywhere.

Where it shows up today

macOS: ExecutionView.swift stacks separate hand-built cards: RubricEvaluationCard, DojoFeedbackCard and TryAnotherBackendCard
Flutter: lineage_review_screen.dart has a list and detail view with feedback
rituals run (Dart CLI) prints Lineage: <id> hash: <prefix>… backend: … tier: … but doesn't save the record
Blocks that exist: lineageEntry and safetyDecision

Please design

The result, plus a compact "sealed" proof line (id, short hash, backend, tier) that expands to the full record
Rubric score and per-criterion notes
The feedback prompt (dojo), and what happens after it's answered
Next actions: run again, run with another backend, save as a wish, export

Acceptance criteria

One result layout that replaces the three separate macOS cards and the Flutter review detail.
Collapsed and expanded proof.
CLI version.

Part of #177. **What it's for:** a ritual has finished. Show the result together with its proof (the lineage record and hash), its rubric score and a quick feedback prompt, laid out the same way everywhere. ## Where it shows up today - macOS: [`ExecutionView.swift`](https://git.toilville.dev/toilville/toilville_rituals/src/branch/main/apps/rituals-macos/Views/ExecutionView.swift) stacks separate hand-built cards: `RubricEvaluationCard`, `DojoFeedbackCard` and `TryAnotherBackendCard` - Flutter: [`lineage_review_screen.dart`](https://git.toilville.dev/toilville/toilville_rituals/src/branch/main/lib/ui/screens/lineage_review_screen.dart) has a list and detail view with feedback - `rituals run` (Dart CLI) prints `Lineage: <id> hash: <prefix>… backend: … tier: …` but **doesn't save the record** - Blocks that exist: `lineageEntry` and `safetyDecision` ## Please design - The result, plus a compact "sealed" proof line (id, short hash, backend, tier) that expands to the full record - Rubric score and per-criterion notes - The feedback prompt (dojo), and what happens after it's answered - Next actions: run again, run with another backend, save as a wish, export ## Acceptance criteria - [ ] One result layout that replaces the three separate macOS cards and the Flutter review detail. - [ ] Collapsed and expanded proof. - [ ] CLI version.