Atlas Review

Every piece of generated content on Noosaga — timelines, concept maps, articles, quizzes — can drift from the field it is supposed to represent. Atlas Review catches those problems and gives them a visible place to be discussed.

Content should not be treated as finished the moment it is created. Atlas Review surfaces issues and tracks them in discussion threads. You can find these threads in the Review section inside any subfield.

Atlas Review is separate from Noosaga Agora, the deprecated research-roundtable experiment. This is the active maintenance system for improving atlas content.

What gets reviewed

Review looks for the kinds of problems that tend to creep in over time:

• Two articles covering essentially the same ground
• Missing nodes or edges in a concept map
• Learning paths that don't flow well from one topic to the next
• Quiz questions that are vague, repetitive, or testing the wrong thing
• Topics that got way more (or way less) depth than they deserve

When you have a framework selected, you can toggle between two views:

• Current framework — threads targeting that framework, plus subfield-wide threads.
• Entire subfield — every thread across all frameworks in the subfield.

Who Can Do What

Everyone can read threads and see the full discussion history — nothing is hidden behind a login wall.

If you're logged in, you can jump into any thread and reply. Starting new review runs and approving important changes is reserved for admins. When something is waiting for admin review, the interface labels it clearly.

How Review Works

Atlas Review combines automated issue-finding with human judgment.

When review runs, it inspects a bounded slice of atlas content, looks for high-impact issues, and records the result in discussion threads. Those threads may point to missing coverage, weak explanations, confusing learning paths, or possible corrections.

Automated review creates visible discussion. When a concrete fix is appropriate, it prepares a proposed change for a human to approve or reject.

Threads And Changes

Threads move from open discussion toward resolution as people review the issue. Some threads stay as notes. Others lead to a proposed change.

Important changes require human approval before they affect atlas content. This keeps review visible and makes it easier to understand why a map changed.

Review Limits

Atlas Review is a maintenance aid. It can miss subtle problems, raise issues that turn out not to matter, or flag a page that is simply thin because the atlas has less coverage there.

When Review Finishes Without New Threads

This trips people up sometimes. You trigger a session, it runs to completion, and nothing new appears. That usually means one of three things:

• The review did not find a high-confidence issue worth raising.
• The issue already existed in another open thread.
• The atlas slice being reviewed was too thin to support a useful finding.

Check timestamps and thread statuses to see what actually happened during the run.

Getting The Most Out Of Atlas Review

Think of it as an ongoing maintenance loop. Review the subfields you care about most, especially after significant edits. When a thread proposes a change, read the discussion and decide whether the fix would make the map clearer.