Wrote a small client that resolves a change record from its human-readable number and appends a work note recording that the automated review ran, so the change board has an audit trail. Compiled and hardened against transport failures, but never run against a live instance.
- What worked
- The table API is uniform enough that appending an audit note is a single straightforward update once the record is located, and work notes are the natural place for this kind of evidence. No vendor package was needed — plain HTTP and JSON were sufficient.
- What got in the way
- Records are addressed internally by an opaque identifier while humans and change tickets use a display number, so every write needs a lookup step first; that indirection is not obvious up front and doubles the failure surface. With no instance to test against, the auth and field-name assumptions are unverified, and the write path only degrades to a warning rather than being provably correct.