feat(discover): doc-approval review chain as the multi-capability goal - #77
Merged
Conversation
…o-plan card
Feedback: the examples weren't representative and the no-plan card read as
broken. New three-goal set, all real:
- "Price a quote" — core.calculate-price@1.2.0 (goal 1, auto-plans on load).
- "Review a document for approval" — doc-approval.analyze -> doc-approval.recommend,
a named-reference-app 2-capability governed chain (document text -> extracted
type/parties/amounts/confidence -> approve-or-route recommendation + rationale).
Verified: browserLocalPlan chains analyze -> recommend from a {document} fact.
EXECUTES once doc-approval.analyze@1.4.0 / recommend@1.4.0 land on the live
catalog with a pure_read risk class (traverse-framework/registry#424, #425);
until then this card plans and then fails closed on the authorization check.
- "Check a card number" — validation.validate-luhn@1.2.0.
Dropped: the abstract uncertainty.score chain and the no-plan card. renderNoPlan
stays as defensive handling for a live goal that returns zero candidates.
Supersedes the still-open #76 (same intent, better multi-cap example).
E2E updated: goal-1 (price) + luhn plan+execute; doc-approval spec added when
the registry PRs merge. npm test 5/5 (+1 skip), test:e2e 2/2, build clean.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feedback on the goal set: the examples weren't representative, and the no-plan card read as broken.
New goal set
core.calculate-price@1.2.0doc-approval.analyze → doc-approval.recommend— document text → extracted type / parties / amounts / confidence → approve-or-route recommendation + rationaledoc-approval.*@1.4.0with apure_readrisk class)validation.validate-luhn@1.2.0Verified:
browserLocalPlanchainsanalyze → recommendfrom a{ document }fact (mappings:facts.document → analyze, then all 5 of analyze's outputs → recommend's inputs). Until the@1.4.0capabilities are on the live catalog, clicking that card plans and then fails closed on the per-node authorization check — honest, not a crash, and it starts working automatically when the registry PRs merge (no further website change needed; a follow-up just promotes it to goal 1 + adds its E2E).Dropped: the abstract
uncertainty.scorechain and the no-plan card (renderNoPlanstays as defensive handling).Supersedes the still-open #76 — same intent, better multi-capability example. Close #76 in favour of this.
Verification
npm test5/5 (+1 networked skip) ·npm run buildclean ·npm run test:e2e2/2 (price + luhn plan+execute).🤖 Generated with Claude Code