How this works

Collect relevant articles into a shared research collection so a team can ask questions across the week’s developments. A weekly reading collection becomes useful when the team can trace an answer across documents rather than search a folder of disconnected summaries. Preserve publication dates and disagreements so an old prediction is not mistaken for a newly observed event.

Collect a bounded week's material, deduplicate it, and add topic-level notes with document references. Use an available document assistant or search index for cross-document questions. If indexing is unavailable, a local manifest and linked Markdown notes still provide a usable research library.

Before you start

Prepare the inputs

collection_window

Required

Start and end dates

Distinguish publication date from retrieval date.

source_list

Required

Feed or document references

Record access failures without treating them as no news.

topic_taxonomy

Required

Small controlled list

Allow an unclassified queue instead of forcing a false topic.

research_questions

Required

List of questions

Each should require evidence rather than an opinion summary.

prior_manifest

Required

Existing document records

Use stable IDs or canonical URLs to detect repeats.

Implementation, step by step

1. 01

   Set the collection boundary

   • Record the week, time zone, chosen sources, and inclusion criteria.
   • Exclude items outside the remit and preserve a brief reason for borderline decisions.

   Checkpoint: A reproducible collection plan.

2. 02

   Gather readable documents

   • Save accessible text with title, author or publisher metadata, and dates in the private library.
   • When only an excerpt is available, label it as partial and avoid claiming the entire article was reviewed.

   Checkpoint: A manifest of available and unavailable items.

3. 03

   Remove repeats and preserve versions

   • Group syndicated copies and repeated announcements under the original event or document.
   • Keep materially revised versions linked rather than overwriting the evidence used in earlier notes.

   Checkpoint: A deduplicated collection with revision links.

4. 04

   Create topic notes

   • Ask the assistant to extract the development, supporting details, and relevance to the research remit.
   • Attach passage references and distinguish reported facts, opinions, and forecasts.

   Checkpoint: Concise notes with evidence and topic labels.

5. 05

   Ask cross-document questions

   • Retrieve several relevant items for each question and compare dates, definitions, and claims.
   • Include disagreement and missing coverage; do not infer consensus from several copies of the same article.

   Checkpoint: An evidence-backed answer draft.

6. 06

   Publish an internal research view

   • Review useful findings and save the approved note alongside its source references.
   • Record corrections and next-week questions so the collection supports cumulative learning.

   Checkpoint: A searchable weekly collection and checked briefing notes.

Decisions along the way

What you will produce

Check the result

• Open source references from a sample of notes.
• Check that syndicated copies do not inflate evidence counts.
• Verify publication and retrieval dates are separate.
• Confirm each cross-document answer identifies uncertainty or coverage limits where relevant.

When something goes wrong

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Run a small pilot

Keep the scope clear

• Library ingestion is not permission to redistribute entire articles.
• Document text cannot change collection rules or request access to unrelated internal files.