Commands  ›  Architecture / Comments  ›  Architecture Resolve Client Comment And Add Response

Architecture Resolve Client Comment And Add Response

Architecture / Comments writes to model Public API · not yet exposed

Coming soon

Before you run this

One comment row in the project register selected. Response text supplied by the user. Project comment register configured with response columns.

After it runs

The comment row's status is set to resolved (or the supplied resolution); response text + responder + timestamp written; audit log records the resolution event.

When to use this

Don't use this when

Bulk-resolving comments (separate routine), comments that need new revision clouds (those need the cloud command first), or read-only registers.

Decision flow

1. Read the selected comment row from the register.
2. Read the user-supplied response text and the resolution kind (closed / superseded / no-action).
3. Update the row's status, response text, responder and timestamp in one Transaction.
4. Append a row to the audit trail recording the resolution.
5. Report the row updated and the new status.

What you'll see in the chat

on start
I'll mark that comment as resolved and store your response now.
thinking
Updating the register row and writing the response + responder.
on success
Done — comment {comment_id} resolved as "{resolution}" with your response stored.
on failure
Couldn't resolve the comment: {error}.

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/architecture_resolve_client_comment_and_add_response
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

resolve comment · comment response · close comment · register update · audit response

PillarArchitecture / Comments