Updated
Routing an idea
How ASI OS suggests where an idea belongs, waits for your confirmation, and only then delivers it.
An idea captured in one place often belongs to work that already exists elsewhere. Routing finds that place without acting on the idea before you agree.
The six steps
The idea text arrives from a captured idea, a capture row, a note dropped into a thread, or the search box.
The system searches all activities that are not Closed. Active ones rank normally; ones on Hold are shown but marked. Matches are lexical, so there are no embeddings. Term aliases can widen the query.
The top three to five candidates are shown read-only, each with a score, a status and the matching snippet. You get one lettered option per candidate, plus "new activity" and "hold it in the inbox activity".
You pick. Nothing is written before this point.
The idea is copied verbatim into the target's next-steps file under a "Routed from" heading. The source notes where it went, and the idea record is marked Routed with its destination.
The target picks the idea up at its next run. A routing report flags any routed section older than seven days.
Copy and wait, not execute
Two behaviours were possible: run the idea inside the target immediately, or copy it and wait for you to run the target. The rule is copy and wait for ideas.
An idea is by definition not yet decided work. Executing it in the target would skip the confirmation you asked for. The one exception is notices the system writes itself, which may be delivered directly.
Targets that are not allowed
- A Closed activity is never a target, because anything delivered there would never be read.
- An activity on Hold can be a target, with a warning.
Ideas about help content go first to the help-content owner, named in a routing table, before ranking starts.