Building a research service you can check

A map earns trust one link at a time

A research map is useful when you can follow a statement back to the record that supports it. A company name connected to a material can mean several things: a confirmed producer, a possible producer found in a search, or an analyst's lead. Those are different claims. Drawing them with the same confident line would make the picture easier to admire and harder to trust.

Substrata's chain atlas groups the existing bottleneck records by research stage. Its bars count records in the corpus. They do not measure world production, market share, or the economic importance of a stage. An empty stage means the research has a gap.

One corpus, several ways to read it

The atlas, search, company pages and assistant draw on the research records already used by the site. That means a corrected producer source can improve several surfaces at once. It also means an uncertainty label needs to survive every transformation.

The data-quality page explains the evidence vocabulary and offers JSON and CSV exports. The JSON includes a content digest so two people can establish whether they analysed the same snapshot. Its generation timestamp is separate from the date an analyst last assessed a claim.

Scores are arguments

A binding score combines four analyst judgements. It helps order a reading list; it does not turn uncertain research into a precise measurement. The rationale and assessment date belong beside the number. Readers should be able to disagree with the reasoning and submit a better source.

Expertise is part of the system

People who qualify a material, ramp a process or connect a grid know things that a public document may omit. The talent section connects the project's existing expertise needs to a contribution path. These are requests for research help, not employment offers.

In Substrata chat, asking the assistant and sending a contribution are separate actions. A contribution receives a receipt after it reaches the research inbox. It still needs review before it can change a sourced claim.

Keep the development record close

The roadmap, changelog and vision read the central development profile. They should describe the same project that readers use and builders work on. This article explains the design; the changelog records completed changes and the roadmap records unfinished work.