BLOMBoundary Layer Labs
Start free
Menu

How it works

Set up your way. Then go around the loop.

BLOM is product management software built for building with AI. It keeps your people and AI agents working from the same plan. Ten steps, from your first standard to your next version, with a record of who did each one.

Start free See each step
The map of how work moves through BLOM Ten numbered steps. On the left, set up your way. Step 1: set your standards, or adopt BLOM's defaults, Specification, ADR, Testing, and Security. Step 2: define your PDLC, or adopt Recommended lifecycle or Minimum. An arrow leads from there into a loop. Plan the product. Step 3: decide capabilities, such as 1-2 Invitations. Step 4: decide features, such as 1-2-3 Roles at invite. Specify. Step 5: write your specs; revision r4 is pinned to commit 4e1a9c2. Design. Step 6: iterate in Design Lab; version 3 is approved. Build. Step 7: assign work to your team, here to Codex, answering to Grace Hopper. Step 8: build your specs; the Job builds r4, exactly. Ship. Step 9: test in dev, then launch to production, through dev, UAT, and Prod. Iterate. Step 10: iterate your way to success; v1.003 is the current version. A dashed arrow leads from step 10 back to step 3, to plan the next version. In the middle of the loop: every version goes around the loop, and BLOM records who did each step, when, and why. Plan the product Specify Design Build Ship Iterate Set up your way 1 Set your standards, or adopt ours Specification ADR Testing Security 2 Define your PDLC, or adopt ours Recommended lifecycle Minimum Plan the next version Every version goes around the loop. BLOM records who did each step, when, and why. 3 Decide capabilities 1-2 Invitations 4 Decide features 1-2-3 Roles at invite 5 Write your specs r4 · 4e1a9c2 6 Iterate in Design Lab v3 approved 7 Assign work to your team CoCodex · Grace Hopper 8 Build your specs Builds r4, exactly 9 Test in dev, then launch to production dev → UAT → Prod 10 Iterate your way to success v1.003 · current The map of how work moves through BLOM Ten numbered steps, from top to bottom. Set up your way. Step 1: set your standards, or adopt ours. Step 2: define your PDLC, or adopt ours. Plan the product. Step 3: decide capabilities. Step 4: decide features. Specify. Step 5: write your specs. Design. Step 6: iterate in Design Lab. Build. Step 7: assign work to your team. Step 8: build your specs. Ship. Step 9: test in dev, then launch to production. Iterate. Step 10: iterate your way to success. A dashed path leads from step 10 back up to planning, just before step 3, to plan the next version. Set up your way 1 Set your standards, or adopt ours 2 Define your PDLC, or adopt ours Plan the product 3 Decide capabilities 4 Decide features Specify 5 Write your specs Design 6 Iterate in Design Lab Build 7 Assign work to your team 8 Build your specs Ship 9 Test in dev, then launch to production Iterate 10 Iterate your way to success Plan the next version
Steps 1 and 2 set up your way. Steps 3 to 10 repeat for every version, and the dashed path leads back to planning.

Each step, up close.

The same ten steps as the map, in order.

  1. 1Set up your way

    Set your standards, or adopt ours

    Keep your standards and best practices in Markdown, or adopt BLOM's four: Specification, ADR, Testing, and Security. Each applies by its own rule.

  2. 2Set up your way

    Define your PDLC, or adopt ours

    Set the phases and gates of your product development lifecycle, or adopt BLOM's Recommended lifecycle or Minimum. Each Job records the version it runs under.

  3. 3Plan the product

    Decide your product's capabilities

    Add the capabilities under your product, numbered like 1-2. Each has an owner, a person or a team.

  4. 4Plan the product

    Decide each capability's features

    List the features under each capability, numbered like 1-2-3, such as Invite by link and Expiry. Each has its own owner.

  5. 5Specify

    Write your specs

    Specs are Markdown in your own Git repository. BLOM pins each revision to a commit, such as P-Spec 1-2 r4 at commit 4e1a9c2.

  6. 6Design

    Iterate in Design Lab

    Post prototype versions, compare them, and approve one exact version. A design approval isn't approval to build.

  7. 7Build

    Assign work to your team

    Every task has one assignee, a person or an agent. Claude Code and Codex connect through BLOM's MCP server, each with its own key.

  8. 8Build

    Build your specs

    A Job names the exact spec revision it builds, and its claim shows who holds the work. BLOM never runs your agents.

  9. 9Ship

    Test in dev, then launch to production

    A merge isn't a deployment. BLOM records dev, UAT, and production one by one, and a release to production makes the item's next version, such as v1.003.

  10. 10Iterate

    Iterate your way to success

    Know the current version and who is doing what. Every change records who made it, a person or an agent with the person it answers to, when, and why.

Start with your standards, or ours.

BLOM's four default standards and its two starter lifecycles are ready when you create your organization.

Start free Read the docs