Skip to content

Add deterministic traverse-starter UI flow #4

Description

@enricopiovesan

Purpose

Implement the end-to-end user flow: enter a note → send to Traverse runtime → render runtime-provided structured output. The UI must not compute any business fields itself.

Definition of Done

  • User can enter a short note or starter input
  • UI sends input to Traverse runtime
  • UI renders runtime-provided structured result fields: title, tags, note type, suggested next action, workflow/event status
  • UI does not compute these fields locally
  • Feature is deterministic — no live AI/model access required

Constraints

The following fields are runtime-owned; the UI renders only:

  • Deterministic tags
  • Note type
  • Suggested next action
  • Workflow/event status

Dependencies

Depends on #3 (runtime event client boundary).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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