Developers

For anyone who programs against Brick Work (its REST API, command line and MCP server) or works on it: builds it, contributes, releases it or runs it from a checkout. Using Brick Work through its screens is in the User guide.

• Tutorials: Script your collection, from an API token to reading and changing the collection.
• Concepts: the data model and its 4.0 design, the import pipeline, the source layer, collection sync and wishlists and portable files.
• Reference: the API v2 contract and the API v2 reference of every operation, the MCP server and its tools and resources, the command line and the code reference of brickwork.core. The API, MCP and code references are generated from the contract, the server and the docstrings when the site is built.

The project

These live at the root of the repository on GitHub:

• Contributing: set-up, tests and how a change lands.
• Releasing: how a release is cut.
• Security: how to report a vulnerability.
• Changelog: what changed in each release.
• Licence: MIT.

Decisions that bind future work are recorded as ADRs in docs/adr/ in the repository.