How development happens here

The process rather than the code: who writes it, how a piece of work moves, what it runs on, and what runs periodically. One page per member.

This describes the process rather than the code, for a contributor reading from a clone and for the coding agent beside them. Bee Box is early: one maintainer, changing fast. Bug reports are invited; pull requests are not yet solicited (CONTRIBUTING.md).

Agent coding, and the checks around it covers where those instructions live, how the two model families review each other's work, and the strictness the code is held to: strict types, lint rules that are never weakened to make code pass, noisy output treated as a bug, the pre-commit hooks, and the rule that nothing learned on a real box reaches this repository unscrubbed.

Testing has the philosophy and one page per verification instrument: tests with typed fakes for every external service, the smoke walk that boots a real box before a merge, browser tours, field tests, and the two that test agents rather than code, knowledge audits and session critiques.

The development workflow covers how a piece of work moves: its own worktree, branch, and session, started from a briefing and landed on main by the finish skill; the issue queue and its categories and next-action tags; recurring work under schedules/; document comments; the planning taxonomy under docs/plans/ and how a plan is reconciled when the work lands; and exhibits, the page an agent builds to show work with exactly one ask on it.

Technologies and AI services names the stack and the external model services a box can be configured to use.

Members