Doc drift sweep
Every claim in the docs checked against the code, and a list of what is now wrong.
For the team
Find the sentences that stopped being true.
Documentation is accurate on the day it’s written. After that it drifts quietly, and the first reader to notice is usually a customer — unless you ask the code first.
For docs and technical writing
The wait today
Docs go wrong at the speed the code changes and get corrected at the speed somebody complains. The work is not the writing; it is finding the twelve sentences out of four hundred that stopped being true, which nobody can do on a schedule and everybody keeps meaning to.
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 does the quickstart still match the setup steps in the repository?
- @PRCHD what changed in the public API this month that the reference does not mention?
- @PRCHD which error codes can this endpoint actually return?
- @PRCHD is the rate-limit number in our docs the number in the code?
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 docs and technical writing, not a catalog to install — PRCHD supplies the engine, and each team writes its own.
API reference regeneration
A reference built from the actual handlers, types, and validation rules.
Changelog writer
A changelog written from the merges, in the product’s voice rather than in commit subjects.
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.
- Documentation updates raised as a branch whenever a public interface changes.
- A weekly drift report naming the pages that stopped being true.
- A trigger on a released tag that opens the docs PR.
What changes
Doc drift gets caught on a schedule, not by a customer.
Where it stops. From a channel, a recipe takes input text, and its posture stays the one the operator wrote. A drift sweep reports what it was written to report, however the request is worded.
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.
Founders and CTOs
@PRCHD how hard would it be to support a second currency?
Leadership gets ground truth directly, at 22:00, without pulling anyone off anything.
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.