Recommendations
A recommendation is a concrete action derived from your signals — what AskEngine thinks you should do, with the evidence to justify it.
How it works
A recommendation moves through a lifecycle: open → accepted or dismissed → shipped → validated. Accepted work that is set aside goes stale, and when its signal archives, the recommendation goes archived with it. Each carries a confidence word (high, moderate, low), cites the signals behind it, and makes nuance explicit when confidence matters. Lists return everything except archived unless you filter for it.
Every recommendation has a work packet: the problem, the beliefs behind it, verbatim evidence and nuance, and a definition of done in belief terms — rendered as markdown, ready to paste into an issue tracker or hand to a coding agent.
What you can do
Decide it: accept or dismiss. Then record what actually happened: shipped, validated, or stale. Recording validated closes the loop for good — the recommendation and its linked signals archive together as a win. Decisions are reversible while the loop is open: reopen a dismissed or accepted recommendation, and a stale one reopens back to accepted. A shipped or validated one can't reopen — restoring its archived signal is what brings a closed loop back. You can also link the ticket, issue, or PR where the work is tracked.
When it's quiet
No open recommendations means analysis has nothing worth your roadmap right now. AskEngine stays silent rather than inventing work — a quiet list is a real reading, subject to the same caution as a quiet signal board.
From your agent
list_recommendations— every recommendation with its lifecycle state.get_recommendation— the full body and action items.get_work_packet— the paste-ready brief for an issue tracker or coding agent.- Lifecycle verbs:
decide_recommendation,record_recommendation_outcome,reopen_recommendation,link_recommendation_work_item.