Reference pages document exact shapes: the commands an operator runs, the schemas that tooling parses, the manifest keys that bind a runtime, and the grammars that make an artifact well-formed or malformed. They are written to be checked against the source, not read end to end. Each one opens with a plain-language statement of what the thing is and who touches it, then gets specific.
If you are looking for why any of this is shaped the way it is, that belongs to How It Works. If you are looking for the TypeScript interfaces behind the CLI and the engine, that is the generated API documentation.