This is the core guide to eight foundational workflow tools inside the fourteen-engine Project Telos roster. Each does a different job and leaves behind something you can check. For the complete Flywheel map, open the engine room. No jargon required.
If you only read one thing, read the next section. Everything else is the same idea, pointed at a different job.
Most AI tools hand you an answer and ask you to trust it. These tools do something plainer instead. They look at real material, check it against a rule that is written down rather than felt, and hand you a small record you can re-open later. If you understand these three steps, you understand the shared core pattern.
A file, an image, a web page, a stack of sources, a claim. The tool works from the actual material, not a vague summary of it.
Does the function only touch what it declared? Does every sentence trace to a source? Does the claim hold up when you try to break it? The rule is explicit, so the answer is not a matter of opinion.
What was seen, what changed, what stayed uncertain. A record a person can inspect after the answer has left the chat, and that reports one of three honest verdicts: it holds, it drifted, or it could not be verified.
Each tool points that same habit at a different job. You do not need all of them. Most people start with one that matches a problem they already have, then use the full fourteen-engine map when they need the larger Flywheel.
Pulls in what you want to read (a video, a web page, a PDF, a paper, a feed) and records exactly where each piece came from, so the source survives long after you have read it.
Turns a big pile of code, or dozens of repositories, into a readable map of how things actually connect, so you (or a model) can see the shape of a project instead of guessing.
Runs a team of agents with routing and quality gates, then records who did what and why in a witnessed causal ledger that can be replayed step by step.
Registers a thesis, steelmans its claims, measures them against a substrate, and refines the weakest axis until the result is useful, with the full paper trail included.
Re-derives a file's exact bytes in four independent implementations and reports MATCH, DRIFT, or UNVERIFIABLE without altering the file.
A programming language where every function has to declare, up front, what it is allowed to reach out and touch (files, the screen, the network). The compiler enforces it: reach for something you never declared, and the program will not build.
Turns material you already have into a course with a real integrity floor: spaced repetition, retrieval practice, and self-explanation checked by crucible. Every graded step stops and waits for you, and writes a witnessed receipt, so the record shows what you actually did.
A shared workbench with durable session state, workstation control, and sensory tools, where a person and a model can perceive and shape the same surface.
Start from the problem you already have. You can always add another tool later; they are built to hand work to each other.