-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
A: Yes. The JSONL log is portable, transparent, and queryable via plain text or scripts. You can log decisions manually or integrate the MCP server with any system capable of stdio execution or JSON-RPC.
A: That's completely fine. Record what you know at decision time:
problemandchosen_solutionare mandatory.rejected_alternatives,predictions, anddomainare optional.- Predictions can be added later using
record-prediction.
A: Indefinitely. The log is an append-only JSONL file without deletion routines or retention limits.
A: No. Storage is a single append-only
JSONLfile (~/.local/share/mcp-decisions/decisions_log.json). Zero server setup, zero schema migrations, zero third-party drivers.
A: No. The log is immutable by design. To supersede a decision, record a new decision setting
status="SUPERSEDED"and cross-reference the previous decision ID inadr_ref.
A: Yes. Append-only writes to line-delimited JSON files are concurrency-safe under standard OS filesystem POSIX append semantics.
Compare observed empirical values against the initial prediction:
- 90–100 (SUCCESS ✅): Prediction was accurate.
- 50–89 (PARTIAL_SUCCESS
⚠️ ): Outcome was close, but drifted slightly.- 0–49 (FAILED ❌): Outcome missed expectations significantly.
Outcome Gate is an in-band reminder embedded inside MCP tool response payloads. It lists open predictions from the current session that still lack recorded outcomes, ensuring feedback loops are completed before sessions conclude.