Adding to the roadmap, and setting aside

Pytheus proposes. You decide. Anything it surfaces can be taken up or set aside, and that judgment stays with your team rather than the engine.

Adding to the roadmap

Adding something to the roadmap does two things at once: it records an append-only decision, and it creates a matching action on your roadmap. The capability, the maturity change and the expected impact carry over, so the new action already knows what it is meant to achieve. If you do not have roadmap-write access it lands in an unscheduled intake rather than being dropped.

Setting something aside, with a reason

Deciding not to act is also a decision, and recording it matters when an auditor or an executive later asks why a known gap was left open. Set something aside for a real reason: the capability may be out of scope for your business, the risk may be accepted deliberately, or the work may already be underway somewhere the platform cannot see.

The record is append-only

Decisions are never overwritten. Changing your mind adds a new entry rather than editing the old one, so the history shows what you knew and when. See Turning decisions into roadmap actions.