Trust & Provenance

This page is the shortest honest answer to the trust question: Noosaga is useful as a map, not as a final authority.

Noosaga uses AI heavily, but it does not ask you to trust a single model response. It asks you to inspect the workflow around that response: generation, verification, source cues, correction, and ongoing review.

What the AI Drafts

Most explanatory content on Noosaga begins as an AI-assisted draft:

• subfield overview articles and framework timelines prepared by Noosaga before users browse them
• framework articles
• concept maps and concept explanations
• Genealogy responses for tracing concepts and inherited assumptions
• quiz questions and explanations
• many relationship claims between frameworks

Some labels, dates, and structural metadata are then checked, refined, or removed through later stages. The initial subfield map is an internal population/backfill process, while the user-facing generation choice is usually which framework should receive deeper articles, concept maps, timelines, concept explanations, or quizzes. So "AI-assisted" here does not mean "one prompt, published untouched."

Current Model Stack

Noosaga uses one centrally configured generation model for runtime drafting, rewriting, synthesis, and final user-facing content. The exact model is configured in deployment rather than hardcoded into the public interface.

Noosaga may also use a separately configured reviewer/editor model for critique, verification, source-grounded review, policy review, and editorial feedback. The reviewer model does not replace the generation model for final articles, framework lists, or timelines. A separate embedding model is used for retrieval.

During upstream provider traffic or rate-limit incidents, Noosaga may use a configured temporary fallback model and surface a warning. The model stack can change as reliability improves. The trust claim is not that one model is always right; it is that model output passes through a structured workflow, source checks, correction tools, and visible review.

What Verification Means

When a framework is verified, the system is trying to answer a narrower question than "is this perfect?"

It is checking whether the framework appears to be:

• recognizable as a real framework for the current subfield
• labeled in a canonical or source-backed way where possible
• plausible enough to support downstream content

Verification can improve a framework label, refine dates, attach source-backed metadata, or remove a bad framework entirely. It does not mean peer review, consensus, or infallibility.

What The Product Is Good For

Use Noosaga when you want to:

• get oriented in an unfamiliar field
• see the main frameworks before reading deeply
• compare rival schools quickly
• find which concepts should be learned first
• trace what came before a theory and what it argued against
• decide what books, papers, or courses to pursue next

That is the right level of trust to bring to the product.

What You Should Not Assume

Do not assume that:

• every relation edge is universally agreed on
• every article gets the emphasis exactly right
• every timeline date is precise to the year
• every concept map is exhaustive
• every Genealogy timeline is a source-backed chronology
• Noosaga is the right thing to cite for a contested scholarly claim

The product is a map. Maps are useful because they simplify. They also leave things out.

How Corrections Happen

Noosaga has a visible correction loop.

Propose edit

If you notice a bad date, weak article paragraph, missing concept, or wrong relationship, use Propose edit in the relevant section. The system previews the operation summary before applying changes.

Atlas Review

Atlas Review is the maintenance layer for ongoing quality review. It tracks issues in public threads, proposes specific fixes, and keeps execution human-approved.

Source suggestions

When a page offers source suggestions or source leads, treat them as pointers, not proof. Suggestions still need to be checked before they become authority for a map, date, article, or relationship claim.

That matters because quality should not improve through silent rewrites alone.

How To Use Noosaga Responsibly

For everyday use:

• use it to orient yourself
• compare multiple frameworks, not just one
• follow its pointers into deeper reading

For classrooms and research:

• frame it as an exploratory tool, not a reference work
• pair it with textbooks, primary sources, and domain-specific scholarship
• treat relationship claims as hypotheses worth checking
• cite the underlying sources rather than the map when precision matters

The Short Version

Trust the product for orientation.

Do not trust it as your final authority.

Trust the workflow more than any single output.

If something looks wrong, assume it is revision-ready and use the correction loop.

Contact

Questions about content quality or methodology: axel@noosaga.com