Record a decision about one of my server apps
dropyour_decisionWrite down a structural decision you made for one of the owner's SERVER apps (graduated), in plain text: why (context), what (decision), what follows (consequences) and when to revisit it (reexamen, at least 20 characters: a date or an event). These decisions join the app's runward mission in its proof dossier, after the four decisions of the kit, and runward checks them: a decision without a date, a status in its closed list or a reevaluation trigger is set aside. action='add' records one (status 'proposed' by default, or 'accepted'); action='list' (default) returns them; action='retire' marks one 'superseded' (never erased: the history of an app is not rewritten). At most 30 per app; title 120 characters, each section 2,000. Record a decision when you choose a data model, a link to another app, a security or privacy rule, or a trade-off the owner should remember. Then ask for a proof dossier (owner, in the cockpit) and read its verdict with dropyour_status. Owner only, with a connected account; refused for a simple page.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"dropId": "<dropId>"
},
"name": "dropyour_decision"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | For retire: the decision id, e.g. 'd002'. | |
| titre | No | For add: the decision in one line (120 characters at most). | |
| action | No | list | |
| dropId | Yes | ||
| statut | No | For add: 'proposed' (default) or 'accepted'. | |
| contexte | No | For add: why a decision was needed. | |
| decision | No | For add: what was decided. | |
| reexamen | No | For add: when to revisit it, a date or an event (20 characters at least). | |
| consequences | No | For add: what follows, good and bad. |