Recued
Menu
← Back to recipes

Retire a decision

by recued-core v2 34 views

Use “Retire a decision” in Recued. Removes one logged decision and its reasoning. Destructive and approval-gated — the record is the only copy.

Complete workflow

Decision Log 5 pinned recipes

Use Decision Log in Recued for records and local first. It includes 6 built-in actions and 3 ready-to-run workflows. Actions that change data use Recued's approval controls.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Retire a decision
This recipe

Use “Retire a decision” in Recued. Removes one logged decision and its reasoning. Destructive and approval-gated — the record is the only copy.

pack:decision-logdecisionrecords
by recued-core pinned v2

Use “Log a decision” in Recued. Records a decision you made and why, so the reasoning survives the moment. A review date is stamped for you.

pack:decision-logdecisionrecords
by recued-core pinned v1

Use “List logged decisions” in Recued. Searches the decision log by status, newest first, and shows each decision with its review date.

pack:decision-logrecordssearch
by recued-core pinned v3
Stamp a decision's review date
Background automation

Use “Stamp a decision's review date” in Recued. Records watcher for newly logged decisions. Computes the review date from the decision's own review window so every decision carries one without the author having to work it out.

pack:decision-logrecordswatcher
by recued-core pinned v2
View pack details, dependencies, and permissions →

Retiring is deleting

Removes one logged decision and the reasoning stored with it. The record is the only copy — there is no archive tier and no undo.

It needs FULL access at install

⛔ This recipe is DENIED if the pack was installed with write access — pick all. It deletes (decision.delete), and deleting is classed destructive, which write does not grant.

⚠ The refusal is operation_not_granted at the gateway, before the recipe's first step runs — so a wrongly-scoped install fails on the delete, not on the lookup, and nothing is half-removed.

You will be asked first

The delete is approval: always, so a run pauses at the preflight gate and holds until you approve or deny. An unanswered approval expires on the preflight.stale_after_days window and the run fails rather than acting on a decision you never confirmed.

How it works 5 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (5 steps)
◆ decision recued-core.decision-log.decision.get
Get decision on decision log
■ found compare
Check if decision record id has data
⚠ found_guard guard
Stop if found equals
◆ retired recued-core.decision-log.decision.delete
Delete decision on decision log
■ card to_summary
Format results as a summary card
▼
Output
summary card
Settings 1 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

decision id setting = [object Object]

Uses (2 operations)

Pack operation Get decision on decision log recued-core.decision-log.decision.get
Pack operation Delete decision on decision log recued-core.decision-log.decision.delete

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

What it's allowed to do

Destructive Pack Decision Log external change
Read: decision.get · No approvalDestructive: decision.delete · Always asks

About

Tags

pack:decision-logdecisionrecords

Details

5 steps 1 configurable settings recipe_id: retire-decision