18 answers about reading the library, how briefs are made, who funds us, and how to reach a human. Search first — it is faster.
How the library is organised and how to find what you need.
Yes. All fifty briefs, the seven topic libraries, the glossary, the research archive, and the newsletters are free to read. There is no paywall, no account requirement, and no metered limit on how many articles you open.
Open Guides & tutorials and follow the learning path. It is sorted from beginner to advanced, and each step assumes only the guides before it. If you prefer browsing by subject instead, start with the Topics index and pick the field you already care about.
Latest is a dated editorial timeline, Popular is a ranked readership board, How it works is mechanism-level explanation, Comparisons judges two competing approaches, Research collects the long-range reports, News is the fast wire, and Guides is the learning path.
Yes. The search box understands a set of Chinese keywords — 人工智能, 芯片, 机器人, 自动驾驶, 电池, 量子, 航天 and others — and maps them to the matching English briefs, alongside full English keyword search.
There is no app. A single daily brief by email is available from the subscribe box on the homepage; it contains one mechanism explained, plus links to anything published that day.
How briefs are researched, reviewed, and corrected.
Every brief starts from primary material: peer-reviewed papers, standards documents, vendor datasheets, patents, and interviews with the engineers who built the system. Secondary coverage is used to find the story, never as the final source for a technical claim.
At least two people. A technical reviewer with domain experience checks every mechanism, number, and architectural claim, then a non-specialist editor reads for clarity — if they cannot retell the mechanism afterward, the draft goes back for a rewrite.
We correct it in place and say so. Verified corrections carry a dated note explaining what changed and why, and the reader who reported it is credited unless they prefer otherwise. Send reports to corrections@infoscope.work.
No. Editorial photography illustrates the technology field rather than a specific device, and never implies a review or an endorsement of the pictured product. Diagrams are redrawn from published sources and credited in the brief.
Because the underlying measurements disagree. Where published figures conflict — efficiency, yield, latency — we show the range and name the conditions, instead of averaging the claims into a single tidy number.
Who pays for this, and who does not get a say.
By readers. There are no advertisers, no sponsored posts, no affiliate links, and no vendor-paid placements. Companies cannot pay for coverage, for a comparison slot, or for a kinder verdict.
No. We may ask a company to confirm a public specification or to explain a design decision, but no external party sees a draft before it ships, and no external party can veto a sentence.
Only matchups where two approaches genuinely compete for the same job and readers keep asking which applies. Each comparison states its judging axis up front, then names the conditions under which the verdict reverses.
You may quote and link with attribution. Full reproduction or translation requires written permission — write to editorial@infoscope.work with the article, the outlet, and the intended use.
Reaching the right desk, and what to expect back.
Corrections and privacy requests are answered within one business day. General editorial mail usually gets a reply within three. Tips that need verification can take longer, and we will tell you if a story is being pursued.
Every email has a single-click unsubscribe link at the bottom. It takes effect immediately, and the address is deleted from the sending list rather than archived.
Please do. Send it to editorial@infoscope.work with the decision you are trying to make — suggestions that arrive with a real workload or a concrete confusion get prioritised over generic requests.
Rarely, and never anonymously. A guest piece must come from someone with direct hands-on experience of the system being explained, and it goes through the same technical review as staff work.
Editorial questions, corrections, privacy requests, and press enquiries all reach a person, not a bot. Most messages get an answer within one business day.