Board summary
What engineering landed this quarter in plain language, with the merges behind each claim.
For the team
Ask without costing someone an afternoon.
Your questions travel down three layers and back, so you ask fewer of them than you should. Ask the code directly instead, and the answer arrives footed with the commit it was read from.
For founders and CTOs
The wait today
The distance between a founder and the codebase is measured in other people’s afternoons. Questions get rationed, the cheap ones never get asked, and the mental model the decisions are made against is a few months old without anyone noticing the moment it went stale.
They ask
Ask in your own words. The answer names its commit.
Mention @PRCHD with the question you’d have saved for a colleague, and it reaches the agent exactly as typed. The agent reads the project’s checkout in Act mode, which changes nothing on disk, and the answer lands in the thread footed with the commit it was read from.
- @PRCHD in plain terms, what is our test coverage situation?
- @PRCHD how hard would it be to support a second currency?
- @PRCHD summarise what engineering has landed this month, for the board deck.
- @PRCHD is anything in the codebase blocking a SOC 2 conversation?
They run
The jobs that keep coming back, written down once.
Each is a prompt plus a posture that someone on the team writes once. After that, anyone in a private channel the operator enabled for runs starts it with one slash command, and the result comes back in the thread. These are examples for founders and CTOs, not a catalog to install — PRCHD supplies the engine, and each team writes its own.
Compliance readiness read
What in the codebase would come up in a SOC 2 conversation, and what would not.
Cost-of-change estimate
How much of the codebase a proposed change touches, and where it gets expensive.
Scheduled and triggered
Some of the work is done before anyone asks.
Put the same recipe on a cron line or behind a webhook URL and it starts on its own, so work that used to wait for someone to wake up or find time is already done when people arrive.
- A Monday-morning summary of what shipped and what is in flight, posted in the leadership channel.
- A monthly digest assembled from the merge history, written for people who do not read diffs.
What changes
Leadership gets ground truth directly, at 22:00, without pulling anyone off anything.
Where it stops. A leadership channel is usually bound ask-only, and questions run in Act mode, so any amount of curiosity leaves the code exactly as it was. The recipes above start from a private channel the operator enabled for runs, or on a schedule.
Other roles
The same host answers the rest of the team.
Product managers
@PRCHD is the export limit still 500 rows, and where is it enforced?
Product questions get answered from the code, without booking an engineer.
Engineering managers
@PRCHD what’s changed on main since Friday, and what’s risky in it?
The status an engineering manager currently assembles by asking five people assembles itself.
Support and QA
@PRCHD a customer says CSV export drops the last row — is that possible in the current code?
The first-line answer comes from the code, names its commit, and takes a minute.
Where your code lives
The computer you own is the computer that runs.
Repositories, worktrees, prompts, transcripts, diffs, command output, attachments, environment values, and the event log stay on the computer you installed PRCHD on — the one that already has your code and your tools. The agent works there, so there is nothing to copy into a hosted environment and nothing uploaded to be indexed.
One small public service handles what a computer with no open port can’t do on its own: it enrolls your computer’s identity, forwards short push notifications, and holds webhook deliveries until your computer collects them. Each delivery is sealed to your computer’s public key the moment it arrives, so the service only ever holds ciphertext, and it is never in the path of your work.
Standing watch
Send this to whoever runs the shared computer.
One person installs it — an afternoon, not a migration. Everyone else asks from a Slack channel they’re already in, and nobody creates an account, installs an app, or pairs a phone.