Bendik Aagaard LynghaugandClaude Fable 5.1
96b3746643
Test / test (pull_request) Successful in 1m7s
portal serve runs a site; portal lint is what iris was; portal plan, build, report and the rest are what portal-trainer was. One source at one version, so the three never disagree about what content means. Both histories are merged in (subtree). The release attaches the bare binary for a content repo's CI. The trainer's plans, intakes, engines and reference prompt come along; its runs stay in the old repo. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt
22 lines
847 B
YAML
22 lines
847 B
YAML
name: How does an answer become a finished job?
|
|
description: >
|
|
Every page asks one question. Every answer lands with the person
|
|
whose job it is, and carries its own next steps.
|
|
alternatives:
|
|
- name: A visitor answers
|
|
description: >
|
|
They pick what they came for and fill in the few fields that
|
|
person needs. They are told who reads it and when.
|
|
- name: The right role sees it
|
|
description: >
|
|
Each role has a desk listing what is theirs, with one button per
|
|
step your process allows - quoted, approved, closed.
|
|
- name: Nothing waits unseen
|
|
description: >
|
|
Every case has a state and an owner, so what is open, and with
|
|
whom, is always one page away.
|
|
- name: Describe your business and get a first draft
|
|
description: Five answers in your own words.
|
|
action: /
|
|
consequence: [Start]
|