Getting started
Turn it on
This module starts inactive. Ask your agent to activate it, or flip the switch on the Decision Log card on the homepage. Activation calls create_database with moduleSlug: "decision-log" and a name you choose, and unlocks the tools on this page. If it was active before and got switched off, the same call reactivates it instead of creating a duplicate.
Reference
Fields
What an entry in this module looks like.
| Field | Type | Notes |
|---|---|---|
| decision | string | Required. What was decided. |
| context | string | The situation or background that prompted the decision. |
| options_considered | string | The alternatives that were weighed before deciding. |
| reason | string | Why this option was chosen over the others. |
| expected_outcome | string | What was predicted to happen as a result of the decision. |
| actual_outcome | string | What actually happened after the decision was made. |
| domain | career | financial | relationship | health | other | Domain for this decision: career, financial, relationship, health, or other. |
Reference
Tools
Decision Log has 8 dedicated tools once active: add, list, update, and delete, plus a few built for how this module actually gets used.
decision_log_attach_photodecision_log_add_entrydecision_log_list_entriesdecision_log_update_entrydecision_log_delete_entrydecision_log_list_pending_outcomesdecision_log_record_outcomedecision_log_by_domain
Full tool reference, with parameters and return valuesTry it
Example prompts
Talk to your agent like this once Decision Log is active. It picks the right tool and fields on its own.
Log that I decided to switch to Postgres, because we needed real transactions. Expected fewer data bugs.
What decisions am I still waiting to see the outcome of?
Record the outcome of switching to Postgres: fewer data bugs, worth it.
How many of my decisions are financial?