BLOMBoundary Layer Labs

Docs

BLOM Docs

BLOM is product management software built for building with AI. It keeps your people and AI agents working from the same plan. How to use BLOM, how the BLOM method works, and how to connect your agents.

Start here

The BLOM method in brief

BLOM keeps the facts of your work apart, and your organization decides the process that produces them. What was intended, approved, built, verified, merged, deployed, and put in front of users are separate facts, and every handoff keeps what's known, what's authorized, and what's still open.

1 · HIERARCHY

What you build

Your organization, its teams, and its products, with the items below each product.

e.g.Harbor › Member onboarding › Invitations

2 · PDLC

How you work

Your steps, your gates, and who approves what. Each Job records the version of the process it runs under.

e.g.Define → Specify → Build → Verify → Release

3 · STANDARDS

The rules work meets

Each standard applies by its own rule of applicability, not by where an item sits.

e.g.The Security standard applies to every Job that changes sign-in.

4 · SPECS

What's intended

Specs, ADRs, and plans, by revision, in your repository and pinned to a commit.

e.g.P-Spec 1-2 r4, at commit 4e1a9c2

5 · TASKS

The work

Jobs create, change, or retire items. A report, such as a Bug, records what's wrong and reaches work only through a Job.

e.g.Bug "Invite link opens twice", taken on by Job invite-expiry-build

6 · COORDINATION

No two on one step

A claim shows who holds each step, and a handoff passes on what the next one needs.

e.g.Codex claims the build, and another agent sees it's taken.

7 · AUDIT

Who did what

Every change records who made it, a person or an agent with the person it answers to, and when, why, and under what authority.

e.g.09:14 · Claude for Ada Lovelace revised P-Spec 1-2.

THE RULE

Facts stay apart

An approval isn't proof something was built. A merge isn't a deployment, and a deployment isn't a release to users.

Connect Codex or Claude Code to BLOM

Your agent reaches BLOM's MCP server at your organization's own address, with its own key. It acts as the key's agent, never as you: every change records the agent and the person it answers to.

The quick path

On API keys, in Organization

  1. 1

    Create a key

    Name it, such as "Claude Code on Ada's laptop". Change its access, where it reaches, or when it expires, if you like.

  2. 2

    Copy the prompt

    Paste it into your agent. It holds every instruction but the key.

  3. 3

    Run the command

    The agent gives you one command for your own terminal, which asks for the key without showing it.

  4. 4

    The agent connects

    It reads BLOM's primer, then tells you the organization it answered for and the standards in force.

Its work is recorded as Claude · Ada Lovelace Never paste a key into a chat, a repository, a task, or a document.

Start, refresh, and return

Three recipes cover an agent's session with a task.

Start

  1. Find work with blom_read_queue.
  2. Export the task's context with blom_export_context.
  3. Claim the step with blom_claim.

Refresh

  1. Refresh the context with blom_export_context.
  2. Renew the claim with blom_renew_claim, with a short note.
  3. Give the step back with blom_release_claim.

Return

  1. Finished: blom_complete with one of the step's outcomes.
  2. Then blom_return_closure: what changed, the checks, the evidence, and what's left.

A closure is a handoff, not completion.

The MCP tools

Eighteen tools: for task work, for learning BLOM, for drafts a person accepts, and for notes, reviews, and feedback. No tool approves anything.

blom_read_primerBLOM's method in brief, with your organization's products, processes, and adopted standards
blom_read_queueThe next actions waiting on the agent, with their claim state
blom_claimClaim a next action before working on it
blom_completeComplete a next action with one of its outcomes
blom_draft_standardDraft a standard, which governs nothing until it's approved
blom_record_reviewRecord a review on the Job it serves: evidence, never approval
And twelve more, from reading items and standards to adding a note to a task.

Browse the docs

Can't find what you need?

Write to us, and we'll answer and add it here.

service@boundarylayerlabs.com