BLOMBoundary Layer Labs
Start free
Menu

BLOM for documents

Every revision, and who approved it.

Compliance, legal, security, and operations teams keep their policies, contracts, and procedures in BLOM: written in Markdown, kept by revision, and approved one exact version at a time.

Start free Talk to us

Policies · Harbor Labs

Information Security Policy

Owner Compliance teamIn force r6Markdown

Revisions

r7Drafted by Claude for Ada LovelaceToday · governs nothing until it's approvedDraft
r6Approved for Adopt by Ada Lovelace12 Oct · "Annual review, with the access rules from the audit"In force
r5Approved for Adopt by Grace Hopper14 Jan · replaced by r6Replaced

Record

  1. Ada Lovelace approved r6 for Adopt.
  2. Grace Hopper reviewed r6: approve, with 2 findings.
  3. Claude for Ada Lovelace drafted r6.

From draft to approved, on the record.

The same four steps for a policy, a contract, or a procedure.

  1. 1 · WRITE

    In Markdown

    Write it in BLOM, or keep it in your Git repository, where each revision is pinned to a commit.

  2. 2 · REVIEW

    With the right people

    A review is the next step on its Job, waiting on the reviewer, and each review is recorded with its findings.

  3. 3 · APPROVE

    One exact revision

    An approval names the revision, its purpose, who approved it, and why. A draft governs nothing.

  4. 4 · KEEP

    Every revision, and the record

    Earlier revisions stay, and the record shows who drafted, reviewed, and approved what, ready to export.

For every team that signs off on documents.

Compliance

Policies and controls you can prove.

Know which revision of each policy is in force, who approved it, and which work it applies to.

  • The revision in force, and the draft that governs nothing until it's approved.
  • Policies that apply to work, by their own rules, so every Job that touches sign-in meets the security policy.
  • Departures recorded, never hidden: a rule that wasn't met stays on the record with its reason.
  • Retention and legal holds for the record, agreed with you on Enterprise.

e.g.Access Control Policy r4 in force since 3 Sep, approved by the compliance lead, applied to 12 open Jobs.

Security

Procedures and reviews that stay current.

Runbooks, incident procedures, and access reviews, each with an owner and a next review.

  • An owner for every procedure, a person or a team.
  • The next review, waiting on its owner in their queue.
  • Evidence beside each review, with its source and time.

e.g.Incident Response Runbook r9, owned by the security team, next review waiting on Grace Hopper.

Operations and HR

Handbooks everyone works from.

One version of each handbook and process, with every earlier one kept.

  • One source of truth for onboarding, expenses, and on-call.
  • Changes approved before they apply, and dated when they do.
  • Organized by team or product, with access by role.

e.g.Employee Handbook r12, approved by HR on 1 Oct, with the travel policy updated.

AI, with people in charge

Agents draft. People approve.

Let Claude or Codex draft a revision, compare it with the last one, or review it against your standards. Nothing an agent writes governs anything until a person approves it, and the record shows the agent with the person it answers to.

Claude for Ada Lovelace drafted r7DraftGoverns nothing until it's approved
Codex for Grace Hopper reviewed r7ReviewEvidence, not approval: 3 findings
Ada Lovelace approved r7 for AdoptIn force"Findings resolved; effective 1 Dec"

Why Markdown.

Plain text your people, your agents, and your auditors can all read.

  • Yours to keep

    Plain text files, in BLOM or in your own repository. Nothing locked in.

  • Easy to compare

    Every change between two revisions, line by line.

  • Read by agents

    The same text your people approve is the text your agents work from.

  • Ready for audit

    Each revision, its approval, and its record, exported together.

Bring your documents into BLOM.

Start free Talk to us