Appendix: Spec Map

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Platform Specification.

Use this matrix when you know what you want to do in the book and need the law (platform-spec), a workflow guide (book/reference/), or the Rust crate that implements it. The platform-spec column is authoritative; Book and crate links are explanatory and implementation-traceability aids.

How to use this map

1. Start with the Book chapter for context and examples.
2. Open the linked platform-spec feature or hub for requirements and maturity.
3. Use the reference guide for a practical workflow.
4. Follow a crate link only when you need to investigate implementation or conformance evidence.

Do not infer a guarantee from a crate name or a Book summary. If an entry has several standard links, begin with the broader hub and follow the feature that owns the exact question.

Ch	Book chapter	Primary platform-spec	Book reference	Compiler / service crates
01	It works on my machine	Tooling / CLI, Build, analyze, run	Downloads, CLI	beskid_cli
02	PATH not found — tooling anyway	LSP, VS Code extension	LSP, CLI	beskid_lsp, beskid_cli
03	Project.proj or it didn’t happen	Project manifest, Scaffolding	Projects	beskid_analysis (resolution)
04	Where does this file go?	Program structure, Modules and visibility	Project resolution	beskid_analysis
05	Names nobody agreed on	Name resolution	Semantic analysis	beskid_analysis
06	Monorepo as coping mechanism	Workspace and lock contracts	Workspace monorepo	beskid_analysis
07	The compiler is not your therapist	Surface syntax, Type system	Semantic rules	beskid_analysis (parse/semantic)
08	Green tests, red production	Contracts and effects / testing	Testing	beskid_cli (test), beskid_tests
09	Contracts, effects, and polite threats	Contracts and effects	Semantic rules	beskid_analysis
10	Memory without another billion-dollar mistake	Memory model	—	beskid_analysis, beskid_runtime
11	Fibers: cheaper than threads	Evaluation / fibers, Execution / channels	—	beskid_runtime, corelib concurrency
12	The normative bible	Community / spec maintenance	Interop canonical map	—
13	Reading the law	Platform specification (all domains)	Architecture graphs	Crate-to-spec anchors
14	From source to something that runs	Build pipeline, Codegen and IR	CLI commands	beskid_analysis, beskid_codegen, beskid_engine, beskid_aot, beskid_pipeline
15	Mods: plugins with consequences	Compiler mods, Compiler Mod SDK	—	beskid_mod, AOT host
16	Corelib: batteries with opinions	Core library, api.json	corelib command	beskid_cli, compiler/corelib
17	Execution: ABI, host, and runtime	Execution, Conformance	—	beskid_abi, beskid_runtime
18	Packages without npm trauma	Registry client, Foreign library import	Publish first package, pckg	beskid_pckg, pckg service
19	Public API that survives review	Modules and visibility, Code style and naming	—	beskid_analysis
20	/// comments that are not lies	Documentation comments, api.json	doc command	beskid_analysis, beskid_cli
21	FFI and forbidden friendships	Interop, Extern dispatch	—	beskid_abi, beskid_runtime
22	So you want to contribute	Spec authority, Release policy	GitHub doc feedback	Superrepo + submodules

Domain quick links

Domain	Hub
Language meta	/platform-spec/language-meta/
Compiler	/platform-spec/compiler/
Execution	/platform-spec/execution/
Core library	/platform-spec/core-library/
Tooling	/platform-spec/tooling/
Community	/platform-spec/community/

For full language indexing, see Beskid Specification.

For the navigation method behind this table, see 13. Reading the law. For the authority and maturity model, see Specification authority and decisions.