Skip to content

CIEL MCP App: Deliver core concept review workflows #2584

Description

@filiperochalopes

User story

As an MCP App user, I want a guided concept review workflow that covers preview, create, and bulk edit capabilities so I can work with CIEL concepts more efficiently in one place.

Use case

A user searches or previews concepts, reviews a worklist, creates a worklist when needed, and later applies staged edits in bulk from the same MCP App surface.

Requirements

  • Deliver the core MCP App workflow in phases without disrupting the existing user experience.
  • Support read-oriented concept review and worklist browsing flows.
  • Support human-approved worklist creation from the MCP App.
  • Support inline concept editing and bulk application of staged edits.
  • Keep the LLM and the browser UI aligned on the same server-side view state.
  • Preserve the widget-first persistence model for any mutating action.
  • Keep the implementation additive and consistent with the existing MCP App guardrails.

Acceptance criteria

  • Given a user opens the MCP App, when they review concepts or worklists, then the app shows the expected server-backed view state.
  • Given a user stages changes in the MCP App, when they apply them, then the changes are committed through the approved workflow.
  • Given the LLM interacts with the app, when it prepares data for the user, then it does not persist changes on its own.
  • Given the browser UI is used, when the user performs a mutating action, then the action follows the session-gated persistence path.
  • Given the app evolves across phases, when new functionality is added, then existing flows remain stable.

More details (collapsible)

Scope reference

This parent ticket groups the MCP App roadmap into two delivery phases:

  • Phase 1: read and create worklists
  • Phase 2: inline edits and bulk apply

The wording is intentionally generic to represent the broader product delivery rather than a single implementation detail.

Metadata

Metadata

Labels

signal/has-dependenciesRelies on other work or external inputssignal/large-scopeAffects multiple areas or systemssignal/needs-specMissing detail or ambiguous requirementsstage/triagedAI triage complete — scored and classifiedtype/featureNew or improved functionality

Type

No type
No fields configured for issues without a type.

Projects

Status
Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions