CaliperForge uses AI coding assistants as part of our engineering workflow. We disclose this on every contribution we file. This page is the long-form version of that disclosure; every PR description, grant application, and bounty claim we submit carries a short canonical footer pointing readers here.
In practice
What this means.
- Specifications and implementations are drafted with substantial AI assistance.
- Every draft is reviewed by a human engineer, tested in a cold-environment reproduction, and submitted under the named operator-of-record, Michael Moffett.
- Michael is accountable for the code, the tests, and any follow-up required by maintainers or grant programs.
- We do not file against repositories whose maintainers have stated an anti-AI-contribution policy. Our per-protocol routing register tracks this and gates submissions accordingly.
Rationale
Why we disclose.
Disclosure protects maintainers, grant reviewers, and the broader ecosystem from having to guess. It also protects us — anti-AI-PR detection that surfaces an undisclosed-AI contribution is a much bigger problem than disclosed work that someone declines on policy.
We treat disclosure as the per-submission protective layer, not a brand-front identity. Visitors and reviewers who land on CaliperForge are forming an impression of what we are — a crypto-protocol contribution agency that ships production-ready work to specific chains. Every submission we file then carries an explicit, identical footer naming the AI-augmented workflow. The brand-front layer and the per-submission layer are decoupled by design: tone calibration at one does not loosen disclosure at the other.
Routing
How we route.
Before any submission, our spec writer checks the target repo or program against an internal per-protocol register marking the maintainer's AI posture as friendly, case-by-case, or hostile. We ship to friendly and case-by-case. We do not ship to hostile, ever — not under a different framing, not without the footer, not at all.
If a maintainer or program reviewer declines a submission on AI grounds, we update the register entry, block future dispatch to that program, and notify the operator. We treat the rejection as information, not an obstacle to route around.
Contact
Reach the operator.
- Submission-specific michael@caliperforge.com
- Policy questions team@caliperforge.com