Nested Outline Reading

Dynalist stores work as nested, collapsible lists instead of flat pages, so a plan and its sub steps live in one document. A Beam agent watches a chosen document or folder for new or edited lines, reads the indentation and text to work out which items are goals and which are sub tasks, and applies a customer set rule to decide which lines are ready to leave the outline, such as anything moved under a heading marked done or next. Items still nested under an unfinished parent, or lacking enough detail to act on, get routed to a person before anything is created downstream.

Tag Based Routing

Dynalist lets a person mark lines with tags, so a shopping list, a project plan, and a reading list can share one workspace without mixing together. A Beam agent reads the tags on each item and matches them against a rule set by the customer, for example sending anything tagged urgent to a messaging tool right away and filing anything tagged reference into a separate document store on a set schedule. Lines with a tag the rule set has not covered, or more than one conflicting tag, are left alone and flagged for a person to sort out by hand.

Cross Document Linking

A single Dynalist workspace can hold many linked documents, so a plan in one file can point to detail in another. A Beam agent follows those links when it reads a source line, pulling in the linked page's content so the record it writes elsewhere is complete rather than a bare title, then applies the customer's rule for what to send and where. A link that points to a missing or archived page, or a document a person has marked private, is routed to a human instead of being written through automatically.