So you want to contribute, huh?

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

Caution

This chapter is informative. Governance and enforceable process live under Community / spec maintenance.

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.

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 | GitHub Actions, gh run view. | | Contact | Maintainer reach-out. |

Tip

Maintainer: Piotr Mikstacki

• Email: pmikstacki@cybernomad.it
• GitHub: @pmikstacki
• Site: pmikstacki.me
• LinkedIn: see Contact — profile URL not pinned in repo yet.

flowchart TD
  idea[Behavior change idea] --> spec[Platform-spec delta]
  spec --> code[Compiler / runtime / tooling]
  code --> tests[beskid_tests / e2e]
  tests --> ci[Green CI]
  book[Book chapter] -.informative.-> spec

Finish the book

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