What does Lockstep capture from Confluence?

Architecture pages and runbooks in allowlisted spaces: the rules teams write down once and never re-read. Published pages are scanned for decision language; candidates go to the review queue for a human to confirm.

We have years of Confluence pages. Does Lockstep ingest all of it?

No. It reads the spaces you point it at, going forward. That keeps the record current and reviewable instead of flooding it with stale history.

Do we have to move our decision log out of Confluence?

No. Teams keep writing in Confluence. Lockstep reads the allowlisted spaces, and the binding version of each decision lives in Lockstep's record with a link back to its page.

Lockstep for Confluence

Confluence pages capture decisions once and never get re-read. Lockstep pulls the decisions out, makes them binding, and delivers them to the people and agents who need them.

What Lockstep captures from Confluence

an architecture decision recorded on a page
a policy or constraint written into a space
a spec change that engineering never hears about

How the loop runs

Lockstep captures the decision from Confluence, routes it to its owner for one-click confirmation that makes it binding, then briefs every engineer and every AI coding agent before they touch the code, and flags any pull request that drifts from it. See the full pipeline on how it works.

How to set up Lockstep for Confluence

In the Lockstep dashboard, open Connections, pick Confluence, and create the connection.
Allowlist the spaces Lockstep should read, by space key (for example ENG).
When a page is published in an allowlisted space, Lockstep scans it for decision language and drafts candidates in the review queue.
The owner confirms, edits, or rejects each draft. Owners can correct the scope or narrow the surface first; the confirmed text is what gets enforced, with a link back to its page.
Engineers and agents get the binding rules in their briefings, and the PR check flags conflicting changes.

Example: a decision captured from Confluence

Illustrative example

In Confluence

An architecture page in the ENG space: "All service-to-service calls go through the internal gateway. No direct calls between services."

Drafted decision

Service-to-service traffic goes through the internal gateway; direct calls between services are not allowed. Anchored to the page.

Approved record

An architect confirms it. An agent adding a new client between two services is briefed on the rule before it writes one. If the architecture changes, the old rule is superseded with lineage, so the history of who decided what stays intact.

Access & trust

Read-only, allowlisted spaces.

What Lockstep reads

Pages published in the spaces you allowlist, going forward

What Lockstep never does

Spaces you haven't allowlisted, or your page history in bulk
Editing your pages
Making anything binding on its own: every candidate waits for a human to confirm it
Storing secrets: tokens, keys, and credential-shaped strings are redacted at ingestion

Full details on the security page.

Frequently asked questions

What does Lockstep capture from Confluence?: Architecture pages and runbooks in allowlisted spaces: the rules teams write down once and never re-read. Published pages are scanned for decision language; candidates go to the review queue for a human to confirm.
We have years of Confluence pages. Does Lockstep ingest all of it?: No. It reads the spaces you point it at, going forward. That keeps the record current and reviewable instead of flooding it with stale history.
Do we have to move our decision log out of Confluence?: No. Teams keep writing in Confluence. Lockstep reads the allowlisted spaces, and the binding version of each decision lives in Lockstep's record with a link back to its page.