Skip to content

ci: q-verify is green — record it, and the lesson that got there - #12

Merged
nandanito merged 1 commit into
mainfrom
ci/q-verify-green
Jul 29, 2026
Merged

ci: q-verify is green — record it, and the lesson that got there#12
nandanito merged 1 commit into
mainfrom
ci/q-verify-green

Conversation

@nandanito

Copy link
Copy Markdown
Owner

q-verify passed its first real run. make verify — J twins, q lessons, the aj golden, the
eval reference solutions, and both eval-run checks — now executes on a GitHub runner. Article
3's published numbers are enforced off the author's laptop for the first time, which was the entire
point of the file.

Log read rather than trusting the tick, and checked for leakage since the repo is public: zero
author identifiers, no kdb+ startup banner
(it carries serial/email/host), .z.K printing 5f
alone, telemetry confirmed NO. "The job passed" and "the job was safe" are different questions.

The lesson, which is the reason for the COMPOUND entry

The first revision demanded a KX_INSTALL_TOKEN secret. That was inferred from a phrase in
licensing-notes.md and never measured. I curled the URL, got 401, and read it as confirmation.

The 401 came from my own mistyped URL, missing /install_kdb/~latest~/. The real endpoint
serves 200 unauthenticated, as do all payloads, and the installer's own download_file() uses a
bare curl with no auth header. Three signals were available before I wrote any YAML, all pointing
the other way.

A guess that produces a plausible error code is the most expensive kind, because the error looks
like evidence.
That 401 tested my typing, not my hypothesis — and I read it as though it had
tested the hypothesis. Same shape as the p# retraction two days ago: seeking confirmation where
confirmation is easy to manufacture. Rule recorded: when a check appears to confirm what you
already believed, verify the check before the conclusion.

Reading the installer was worth more than the token fix

setup_telemetry() tests the licence (.z.l[4] for "tld") and can set KX_UPLOAD_TELEMETRY=YES
before reaching the non-interactive branch that would default it to NO. A decision made
interactively — and recorded in licensing-notes.md — would have been left to a licence flag on CI.
Now forced and asserted.

A policy you chose interactively is not in force anywhere you automated.

🤖 Generated with Claude Code

First real run of q-verify passed end to end: J twins, q lessons, the aj golden,
the eval reference solutions, AND both eval-run checks now execute on a GitHub
runner. results.csv's correctness column and runs/traces.md are verified off the
author's machine for the first time, which was the entire point of the file.

Log read rather than trusting the tick, and specifically checked for leakage on a
public repo: zero author identifiers, no kdb+ startup banner (it carries
serial/email/host), `.z.K` printing `5f` alone, telemetry confirmed NO. "The job
passed" and "the job was safe" are different questions.

COMPOUND entry records the mistake that shaped this file, because it is the
transferable part. The first revision demanded a KX_INSTALL_TOKEN secret inferred
from a phrase in licensing-notes and never measured. I curled the URL, got 401,
and read that as confirmation — but the 401 came from MY OWN mistyped URL missing
the /install_kdb/~latest~/ segment. The real endpoint serves 200 unauthenticated,
as do all payloads, and the installer's own download_file() uses a bare curl with
no auth header. Three signals available before I wrote any YAML, all pointing the
other way.

A guess that produces a plausible error code is the most expensive kind, because
the error looks like evidence. That 401 tested my typing, not my hypothesis, and I
read it as though it had tested the hypothesis. Same failure shape as the p#
retraction two days ago: seeking confirmation where confirmation is easy to
manufacture. Rule going in: when a check appears to confirm what you already
believed, verify the CHECK before the conclusion.

Also recorded: reading the installer was worth more than the token fix.
setup_telemetry() tests the licence (.z.l[4] for "tld") and can set
KX_UPLOAD_TELEMETRY=YES before reaching the non-interactive branch that would
default it to NO — so a decision the author made interactively would have been
left to a licence flag on CI. A policy chosen interactively is not in force
anywhere you automated.

CLAUDE.md and README updated to say green rather than pending.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@nandanito
nandanito merged commit 2f682f5 into main Jul 29, 2026
1 check passed
@nandanito
nandanito deleted the ci/q-verify-green branch July 29, 2026 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant