[GH-ISSUE #131] CLI residual unknown update command cannot submit resolved states #76

Closed
opened 2026-10-15 18:20:53 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @morluto on GitHub (Jul 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/131

Problem

unknown-update in the CLI exposes only a fixed subset of residual-unknown fields and cannot represent the full input contract needed for valid resolved updates.

In src/cliUnknownCommands.ts, update payload is hardcoded:

  • required_authority: null
  • required_confidence: "observed"
  • resolution: null

(and no CLI flags for these values).

That makes it impossible to perform legal transitions that require evidence-linked authorization and resolution details (e.g., status: "resolved").

Reproduction

# create a known unknown
echo "$(node scripts/rea.mjs unknown-record --question \"res test\" --severity high --domain d --authority analyst-inference --confidence observed --evidence ev_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa)"

# extract unknown_id from output and use it here:
ID=unk_<value>

node scripts/rea.mjs unknown-update --id "$ID" --revision 1 --status resolved --severity high --evidence ev_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb

Actual output:

ok: false
error: null

Impact

The CLI provides no path for users to perform valid resolved updates even when they should be the target behavior of residual unknowns.

Files

  • src/cliUnknownCommands.ts
Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/131 ### Problem `unknown-update` in the CLI exposes only a fixed subset of residual-unknown fields and cannot represent the full input contract needed for valid resolved updates. In `src/cliUnknownCommands.ts`, update payload is hardcoded: - `required_authority: null` - `required_confidence: "observed"` - `resolution: null` (and no CLI flags for these values). That makes it impossible to perform legal transitions that require evidence-linked authorization and resolution details (e.g., `status: "resolved"`). ### Reproduction ```bash # create a known unknown echo "$(node scripts/rea.mjs unknown-record --question \"res test\" --severity high --domain d --authority analyst-inference --confidence observed --evidence ev_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa)" # extract unknown_id from output and use it here: ID=unk_<value> node scripts/rea.mjs unknown-update --id "$ID" --revision 1 --status resolved --severity high --evidence ev_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ``` Actual output: ```text ok: false error: null ``` ### Impact The CLI provides no path for users to perform valid resolved updates even when they should be the target behavior of residual unknowns. ### Files - src/cliUnknownCommands.ts
bsakaguchi 2026-10-15 18:20:53 +00:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@morluto commented on GitHub (Jul 17, 2026):

Superseded by the current session-scoped residual-unknown MCP contracts. The standalone unknown-update CLI adapter cited here was removed; updates now pass through updateUnknownInputSchema and BinarySession Evidence-ledger semantics.

<!-- gh-comment-id:5001295110 --> @morluto commented on GitHub (Jul 17, 2026): Superseded by the current session-scoped residual-unknown MCP contracts. The standalone unknown-update CLI adapter cited here was removed; updates now pass through updateUnknownInputSchema and BinarySession Evidence-ledger semantics.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#76
No description provided.