Document your package

Put ordinary comments in your Bend source and publish; there is nothing else to configure.

No signup or config beyond your BendHub account: publish to BendHub and the next hourly rebuild shows your package on this site.

What the site reads

On the page	Where it comes from
Package description	The hub's description for the upload; observed to be the first `#` line of the published entry file (bend-mathlib and bend-tensors). The hub's own code is not public, so this is observed.
Module header	The run of `#` lines at the top of a module, when the line after the run is blank, an `import`, or the end of the file; a run followed by a declaration is that declaration's doc instead.
Declaration docs	The contiguous `#` lines directly above a `def`, `law` or `type` (no blank line between). A line that is just `#` is a paragraph break, and backticks render as code.
Name and version	`bend <entry>.bend --publish` publishes by hash; `bend link <name>@<version> 0x<hash>` names a package already on the hub, or `bend <entry>.bend --publish <name>@<version>` after `bend login` names it at publish time.
License	Every file named exactly `LICENSE` (the entry directory or a subdirectory): an `SPDX-License-Identifier` is read first, otherwise a known license text is matched (MIT, Apache-2.0, GPL, …). A package without one shows `MIT-0`.
Status	`bend <file>.bend --check-only` for every `.bend` file, run on the pinned compiler (bend 2.0.36); each law is marked proved or open.

An example

# fastsort: a merge sort for Bend 2 with laws.
import Base

# Sorts a list of U32 in ascending order.
#
# Stable; runs in parallel on the CPU pool.
def sort(xs: List<&2, U32>) -> List<&2, U32>:
  ...

For AI agents

The build writes lemmas.txt, one tab-separated line per proved law (package/module, law, statement), and llms.txt, a plain-text index of the site.