From 3fcb557c7a90c7a98f6e267a9f26cc8cabc17501 Mon Sep 17 00:00:00 2001 From: blocksifrdev Date: Tue, 15 Sep 2026 13:04:16 -0400 Subject: [PATCH] Drop the "Category King" framing It was internal strategy language that had leaked into a source comment. The loop it described is the protected execution loop; naming it after a positioning ambition told a reader nothing about what the code does. Co-Authored-By: Claude Opus 5 --- packages/pctr/src/protect.mjs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/pctr/src/protect.mjs b/packages/pctr/src/protect.mjs index 0bba845..98cdc1a 100644 --- a/packages/pctr/src/protect.mjs +++ b/packages/pctr/src/protect.mjs @@ -7,7 +7,7 @@ import { createTimeline } from './timeline.mjs'; import { requiresHumanApproval } from './trust.mjs'; import { trustDelta } from './observe.mjs'; -// The Category King loop, executed end to end: +// The protected execution loop, end to end: // PREVIEW -> ROUTE -> AUTHORIZE -> ENFORCE -> RECEIPT, with a replayable timeline. // Async because a real effect boundary is out of process: enforcement is I/O.