For teams that build with AI

Code moves at AI speed. Now the whole team can keep up.

Pilcrow turns every repository into a project anyone can follow. Read its documents and add your own, ask what changed, question any sentence, and see what could break before it ships.

Project workspace

Merchant onboarding main

+ Add documents

OverviewDocumentsAsk AIDiscussionsTasksChanges & risks

documents/kyc-requirements.md · from KYC requirements v3.docx

Director verification

Every business account names at least one director. Before an account is activated, each director must pass identity verification, including directors added after sign-up.

Ask / comment Ask AI Create task Suggest a fix

Verification results are kept for seven years and can be exported on request. Where a provider is unavailable, the account stays pending and the applicant is told why.

Ownership checks

A person holding a quarter or more of the business is treated as a beneficial owner and verified on the same terms.

Made for the people around the code: product, operations, compliance and leadership, and the engineers who answer them.

Engineering got faster. Everything around it didn’t.

The code changes every day

AI writes more of it each week. Release notes can’t keep up, and nobody outside engineering reads a diff.

The documents live somewhere else

Specs and policies sit in inboxes and shared drives, drifting away from the code they describe.

Questions disappear into chat

Asked once in a busy thread, answered once, then lost. So the same question gets asked again.

Pilcrow puts each project’s documents, conversations and changes in one place that anyone on the team can open.

01 · Projects

Every repository becomes a project anyone can open.

Pilcrow reads the documents already in your repository and shows them as clean, readable pages. Anyone can add more, without Git, Markdown or a developer’s spare hour.

Bring what you already have. Word, PDF, Excel, HTML or Markdown. Word and PDF become readable pages, and the original is kept beside them.
Saved where the code lives. Contributions are committed to the branch you connect, directly or through a pull request, as the project prefers.
Kept apart from what you ship. Documents go into the folders you choose, and Pilcrow’s release gate can hold a deploy until the check that keeps those folders out of your build has passed.
One home per project. Overview, documents, Ask, discussions, tasks and changes, side by side.

Project workspace

Merchant onboarding main

Documents426 added this month

Discussions72 waiting on you

Tasks122 blocked

Changes & risks3need review

Find a document…

DOCXKYC requirements v3documents/kyc-requirements.md8

PDFPartner agreementdocuments/partner-agreement.md3

XLSXFee schedule 2026documents/fee-schedule.xlsx5

HTMLOnboarding flowdocs/onboarding-flow.html1

MDArchitecture overviewdocs/architecture.md12

02 · Ask

Ask the project what you’d ask an engineer.

Project Ask knows the repository: its documents, its code and its recent commits. Ask in plain words, and get answers that show their evidence.

Points to the source. Commits, files and documents are cited, so you can check the answer yourself.
Honest about certainty. A suspicion is called a suspicion, with a suggested check, never a promise that a release is safe.
Private and scoped. Your conversations belong to your account, and only reach the projects you can already see.

Ask Pilcrow · Merchant onboarding Private to you

What shipped last week?

23 commits landed between 21 and 28 October, on two branches.

main Director verification moved to a background job a81d04e, and the upload limit was raised to 25 MB 5c2e9f0.
release/2.4 A fix for duplicate webhook deliveries 9b7d311.

Sources · 23 commit reports · documents/kyc-requirements.md

What went into a81d04e?

It moves director verification out of the sign-up request and into a background job, so a slow provider no longer times out sign-up.

jobs/verify_directors.ts+142
signup/activate.ts+9−38
test/verify_directors.test.ts+64

Still worth checking: an account can now be activated before verification finishes. Confirm that matches the KYC requirements.

What doesn’t look right?

One suspicion, not a confirmed failure:

Retries have no upper limit

jobs/verify_directors.ts:88 If the verification provider is down, the job retries forever and the queue keeps growing.

Suggested check: run the job against a provider that answers 503 and watch the retry count.

03 · Discuss

Select any sentence. Ask, tag, decide, assign.

Every question sits on the exact words it’s about, with the right person tagged. Every answer becomes a decision or a task, not another lost message.

1

Select

Highlight a word, a sentence or a whole section of any document.
2

Tag

@mention a teammate. They hear about it in Pilcrow, by email, or in Teams or Slack.
3

Decide

Agree or disagree on the record. Agreed decisions reach your team’s AI coding agents; disagreements are kept out of their context.
4

Assign

Turn the passage into a task with an owner and a due date, linked back to the words that prompted it.

Got a requirements document? Pilcrow drafts the tasks.

Upload a Word file or PDF and Pilcrow proposes task cards from the requirements it states. A person reviews, edits and assigns each one, and every card remembers the version and quote it came from.

04 · Changes & risks

Know what went in, and what could break.

For leads: choose the branches that matter. Every commit on them gets a plain report of who changed what, the areas it touches, whether checks passed, and what looks risky.

Changes & risks · Merchant onboarding

AS

Move director checks to a background job

a81d04emainArjun Shah · 2 hours ago

Possible regressionChecks pass
SO

Stop duplicate webhook deliveries

9b7d311release/2.4Sam Okafor · yesterday

Needs lead reviewChecks pending
LN

Raise the document upload limit to 25 MB

5c2e9f0mainLeela Nair · 2 days ago

No findingsChecks pass
PK

Tighten payout retry timing

e07a6b2release/2.4Priya Kapoor · 3 days ago

Checks failing

a81d04e · main · Arjun Shah

Move director checks to a background job

Implementation & review

Changed Verification now runs after sign-up, in a background job. signup/activate.ts:41

Suspected regression Retries have no upper limit. jobs/verify_directors.ts:88

CI evidence

3 of 3 checks pass

Deployment gate Waiting for a lead’s review of the live branch head.

ApproveNeeds changes

Branch by branch
Watch main, a release branch, or both. Missed events are recovered from branch history.
Findings with citations
Optional code analysis lists what changed and what might regress, each pointing at the line.
Delivered where you work
Pilcrow’s inbox, email, or a private message in Teams or Slack, each retried on its own.
A gate before production
Hold a deployment until a lead has reviewed it and the required checks pass.

Fits the tools your team already uses.

Your coding agents read the decisions too. Over MCP, Claude Code, Cursor and other agents see what the team agreed, so the next change they write already knows.

GitHub
Microsoft Teams
Slack
Email
MCP for coding agents
Word & PDF
Excel & CSV
HTML & Markdown

Up and running before your next stand-up.

1
Sign in with your work email
We send you a link. There’s no password to set or forget.
2
Connect a repository
Install the Pilcrow GitHub App on the repositories you choose. Pilcrow sees those and nothing else.
3
Bring the team in
Invite people by email, or let colleagues join with your company’s email domain.

Built to be trusted with your work.

Your repository stays the source of truth

Documents are committed to Git, versioned with the code they describe.

People see only their projects

Access follows the project, and each team decides how open it is.

Every decision has a real name on it

Authorship comes from sign-in, not a name someone typed.

Answers show their working

The assistant cites its evidence and never certifies a release.

Give everyone a way into the project.

Start with one repository. Invite the people who keep asking you what changed.