So you want to contribute, huh?

You read twenty-one chapters. You have opinions. Good: Beskid is not built by people who nod through enterprise standups without screaming internally.

This chapter is the on-ramp for contributors: where repos live, how spec-first workflow avoids “surprise, we changed language law in a drive-by PR,” and how to run tests without declaring war on CI.

Use the canonical Contributing guide for repository setup, Standard changes, and documentation rules.

What you will find here

Section	Topic
Repos and submodules	Superrepo, `compiler`, `pckg`, extension, corelib.
Spec-first workflow	Extend platform-spec before observable behavior.
Compiler contributor path	Crates, tests, pipeline phases.
Docs and website	`site/website`, trudoc, book vs spec.
Conformance and tests	Evidence and e2e policy.
CI and green builds	Woodpecker steps and retained logs.
Contact	Maintainer reach-out.

flowchart TD
accTitle: Spec-first contribution flow
accDescr: A behavior idea changes the Standard before code and focused tests, while the informative Book links back to the Standard.
idea[Behavior change idea] --> spec[Platform-spec delta]
spec --> code[Compiler / runtime / tooling]
code --> tests[focused test crate / e2e]
tests --> ci[Green CI]
book[Book chapter] -.informative.-> spec

Text equivalent: Start an observable behavior change in OpenSpec. Implement the approved rule, add focused tests, and require green CI. Book prose is informative and must link to the normative Standard.

Finish the book

Appendix: Spec map: chapter ↔ spec ↔ crates matrix.