Why the Project Is Called BitSpeed

BitSpeed is a useful name only if it leads to a clear job. For Inspect, that job is explaining where observed transfer time goes. The name should get you to a measurement you can examine, rather than a promise that every request will become faster.

That is also why the project contains separate tools. Understanding a request and moving a file safely are related problems, but they have different correctness tests. Inspect needs to keep timing evidence and interpretation apart. Transfer needs to prove which bytes survived interruption and when a complete destination can be reported.

Inspect works from observations through explicit calculations to limited interpretations.

Neither tool needs an LLM to produce its result. Inspect uses deterministic rules. Transfer is being developed around immutable snapshots, chunk hashes and a documented persistence sequence. Keeping each command independently useful makes the project’s boundaries easier to understand, and easier to test.

For now, Inspect is released and Transfer is in development. That distinction belongs beside the name, not hidden several clicks away.