Quevin

The Writing Contract

Kevin P. Davison
Writing AI Editorial Vulnerability Leadership
The Writing Contract

About twenty posts on this blog. About three thousand journal entries that aren’t on it. The line between the two isn’t accidental. It’s a contract.

I’ve been on the other side of this

Two decades ago, in the first wave of personal publishing, I wrote a version of myself I would no longer publish. The internet kept the receipts. Some of it was good. A lot of it was untethered. I learned what disclosure costs when it isn’t anchored to a frame.

When I picked the blog back up after years away, I picked up something else with it: a working definition of what this blog is for, and what it isn’t.

What it is, and what it isn’t

What it is: AI as an amplifier, leadership as first-principles work, personal practice used to illustrate principles. Vulnerability has a place here — three years of failed CI/CD, the burnout trap, the wrong-sequence ticket. These are honest, and they are bounded. Each one resolves on a synthesis, not on the wound.

What it isn’t: identity disclosure, relationship interior, politics, faith, mental health as such, the raw wound. Not because those things don’t matter — because they matter so much that they don’t belong on a public site whose contract is competent exploration of the principles I’m working with.

The test I keep returning to: does this resolve to a principle the reader can use, or does it resolve to a need I had to say it? If the answer is the second one, it belongs in a journal. Not here.

I’m not building a confessional. I’m building a working notebook for a particular kind of practice, in public, in case any of it is useful.

Why the contract is easier to keep now

I’ve never had an editor before this year. I have one now.

It’s an AI editor. The irony of an AI helping me decide what’s mine to share isn’t lost on me — but the editor doesn’t decide. The editor pushes back. It asks if a paragraph earns its keep, surfaces where two arguments contradict, and points out when I’m reaching for a confession because I want to be seen, not because the post needs it.

An AI editor turns out to be unusually well-suited to restraint work:

  • No social stake. A human editor sometimes hesitates to say “this is too much.” An AI editor doesn’t.
  • The whole archive in one breath. It can hold every post I’ve written and tell me when a new one drifts off-contract.
  • Available the moment the urge to post arrives — which is exactly when an editor is needed. The urge to over-share isn’t a Tuesday-afternoon urge. It’s an 11 p.m. urge.
  • Patient with revision. The fourth pass at the same paragraph gets as careful a response as the first.

None of this replaces taste. It supports taste. It’s the difference between writing alone and writing with a thoughtful reader at the next desk who actually wants the work to be good.

The rules I’m keeping

  • Publish what resolves to a principle. Don’t publish what only resolves to a need.
  • The reader is the customer. Restraint is the product.
  • Vulnerability earns its keep by what it teaches. Otherwise it’s noise dressed as honesty.
  • If the only reason to post is that I would feel better for having posted it, don’t post it.
  • The editor — human or AI — is part of the contract, not an option.

The discipline isn’t in what I write. It’s in what I leave out. Different tools now, different judgment, different lines, different help. Some of it is age. Some of it is the editor. The rest is the contract.


Kevin P. Davison

About the Author

Kevin P. Davison has over 20 years of experience building websites and figuring out how to make large-scale web projects actually work. He writes about technology, AI, leadership lessons learned the hard way, and whatever else catches his attention—travel stories, weekend adventures in the Pacific Northwest like snorkeling in Puget Sound, or the occasional rabbit hole he couldn't resist.