Editorial and contribution policy

Beseam maintains the Fieldbook and credits the people and projects it relies on.

What gets included

A project or reference needs a clear commerce use, an identifiable maintainer, an official source, and a visible license or usage policy. Platform rules should point to the platform's own documentation. Technical requirements should point to the relevant standard where one exists.

Popularity alone is not enough. We may leave out a project when its maintenance status, licensing, claims, or practical value is unclear.

Attribution

External projects keep their own names, maintainers, governance, documentation, trademarks, and licenses. A listing here is not an endorsement in either direction.

Maturity labels

• Stable: suitable for routine work.
• Reference: official documentation or a specification used to interpret a requirement.
• Emerging: useful, with important details still changing.
• Experimental: worth testing, but not established practice.

Corrections

A correction should identify the page, quote the statement that needs attention, link to the supporting source, and propose replacement wording. Substantive changes update the review date.

Contributions

We accept proposed problems, skills, playbooks, projects, corrections, and anonymized field results. We do not publish promotional submissions or unsupported outcome claims.