The process
How BCM works
Five steps from idea to shipped — every one backed by GitHub, CI, and a permanent record.
01
Scope your project
- →Submit through blackcode.consulting (agency scope) or directly on BCM.
- →Your project is structured using BMAD methodology — broken into stories with explicit acceptance criteria before any artisan touches the code.
- →You receive a written scope confirmation before work begins. No surprises.
02
GitHub repo is created automatically
- →BCM's GitHub App creates a private repo in the BlackCodeMarket-Projects org.
- →The repo is seeded with: README (scope doc), docs/stories/ (one file per story), tests/acceptance/ (Playwright test stubs), and a CI workflow.
- →Acceptance criteria exist as checkboxes in the story files from day one. The artisan knows exactly what done means.
03
Artisan claims and delivers
- →Open jobs appear on the BCM job board (no PII exposed). Vetted artisans sign in with GitHub and apply.
- →A BCM operator assigns the artisan — they receive a GitHub repo invite and access to the full scope.
- →Every commit triggers Playwright CI. The project status in BCM updates automatically via GitHub webhooks.
04
Tests pass. You approve.
- →When all Playwright tests pass, you receive a delivery notification.
- →You review the work against the acceptance criteria in the story files.
- →Approve delivery → escrow releases → the build is logged permanently on the Ledger of Execution.
05
Logged on the Ledger
- →Every completed project becomes a public Ledger entry — GitHub link, CI badge, project type, date shipped.
- →Founders can opt out of public listing for confidential projects.
- →The Ledger is BCM's proof of work — immutable, GitHub-backed, not marketing copy.
Ready to start?
Post your project through our scope intake. Your repo will be created within minutes of submission.