This user story deals with expected behaviour when encountering a topic/context/first-order collection.
Perhaps it is discovered when declared as the context
for an Object. The collection can then be used as the canonical source for content for that context, and it's members queued for asynchronous processing.
A scaling issue exists here in that a collection could be massive and cause an undue delay in processing a new Note if every other member of the collection needs to be processed first. Implementors should take care to not require the full context during processing of an Object.