Skip to content

Multi-capability showcase: doc-approval.pipeline workflow (extract → analyze → recommend) #111

Description

@enricopiovesan

Summary

Define doc-approval.pipeline chaining extractanalyzerecommend WASM capabilities for the doc-approval reference app on all platforms.

Why

Second domain app proves the embedded + multi-capability pattern is reusable, not traverse-starter-specific.

Depends on

  • Traverse #538 (doc-approval.extract)
  • New doc-approval.recommend capability in Traverse
  • manifests/doc-approval/ (see companion issue)

Blocked by

Definition of Done

  • Workflow + manifests authored
  • All seven doc-approval clients execute pipeline and render runtime output
  • Approver surface remains out of scope (Phase 1 submitter only)

Validation

  • Dev sidecar: register → execute pipeline → analysis + recommendation fields render

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedCannot proceed until blocker is resolvedruntime-clientTraverse runtime client boundary work

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions