How a system or process actually works: the inputs, the steps, the parts, and where it breaks.
2 credits·in-depth·about 2–4 min·12 domains
Name the system: a market mechanism, a supply process, a piece of infrastructure, a regulatory procedure. It explains it in one line, then step by step, names the moving parts and what makes it work, where it can break, why it is built the way it is, and what people commonly get wrong about it.
Anyone who has to explain a thing to someone else, or who has been nodding along to a term for too long.
These are the headings the result renders, read from the same promise the form makes before you spend a credit. A section that depends on what the record holds is rendered when it can be and never promised here.
It explains the documented mechanism, not a theory of it. Where experts disagree about how something works, the disagreement is stated; a step the record does not describe is an open question.
A claim the scan could not source is marked as such rather than dressed up. How the grades work →
A domain may name it in its own words and price it on its own terms; each row is what that domain shows.
Each defense contract type moves the point on a dial between the taxpayer paying whatever the work actually costs and the contractor eating any cost growth beyond an agreed ceiling, with oversight burden (DCAA audits, Cost…
AI tools make individual workers faster almost everywhere they're deployed, but that speed only becomes company earnings when the surrounding workflow, headcount, and handoffs are redesigned around the new capability — and…
Congress has never written a law saying which bills the US government pays first if borrowing stops, so Treasury's crisis procedure is to hold all payments centrally rather than run a skip-list.
The fastest way to judge the result is to pick a subject you know cold and read it against what you know. The scan names its credit cost before it runs.