BafGo Port · Walkthrough

01

Install BafGo

Install once, then run bafgo init. A .bafgo/ folder appears in your repo. That's the whole install.

$ npm config set @bafgo:registry https://npm.bafgo.com/

$ npm install -g @bafgo/cli

$ bafgo init

→ .bafgo/ created

.bafgo/
  rules/        ← your rules
  changes/      ← units of work
  events.jsonl  ← who approved, when · hash-chained
  links.json    ← the trace, generated
  manifest.json ← fingerprints, generated
  keys.yaml    ← trusted public keys · signed approvals

02

The rule

A rule is a requirement written so it can be checked. Here's the one your agent will draft from the ticket next.

Rule R-123

Timer keeps running while the screen sleeps

when  a timer is active and the display sleeps
then  the countdown continues
     the chime still fires at zero
why   product decision · timers must stay trustworthy

03

Tell your agent what to do

You give the intent. Your agent reads the ticket, drafts the rule, and links the work. You don't run any of it.

BAFGO-42 Jira

Timer keeps running while the screen sleeps

you: "handle this ticket" → your agent reads it → drafts R-123 · records CH-42

your agent runs these

$ bafgo rule new R-123 --title "Timer keeps running while the screen sleeps" --when "a timer is active,the display sleeps" --then "the countdown continues,the chime still fires" --source "Jira BAFGO-42"

$ bafgo rule specify R-123

$ bafgo claim CH-42 --rule R-123 --tracker BAFGO-42

$ bafgo link R-123 --code index.html --unit timer-core.test.js

$ bafgo stage CH-42 --demo preview.bafgo.com/r-123

→ rule drafted · 3 links recorded

What each verb does

ruledraft the rule from the ticket, when → then

claimtake the work, linked to its ticket

linkattach the code and tests to the rule

stagepublish the demo for review

Your agent reads Jira, Azure DevOps, and Loom with its own tools, drafts the rule, and records the work. BafGo keeps the trace. Nothing to install server-side, nothing to maintain when an upstream API changes. Point your agent at the agent guide for the exact commands.

04

Track & review

Every rule, its tests, and who approved it, all in one place.

R-123Timer keeps running while the screen sleepsimplemented

R-124Adding a duplicate item is a no-opverified

R-125Clearing checked items keeps only the uncheckedverified

R-128Dark mode feels right at night · exploratorydraft

rule · R-123→ code · index.html→ unit · timer-core.test.js→ demo · r-123→ approved

Approved by dana · 2m ago · on record

It's all files in your repo: events.jsonl is hash-chained, manifest.json fingerprints the work, and an optional key (bafgo keygen) makes approvals signed and re-checkable.

Watch one rule go from requirement to approved.

Install BafGo

The rule

Tell your agent what to do

Track & review

That's the whole thing.