fix(dreaming): drop opaque ids from topics; require a sample before the approval nag (v0.281.3) - #502
Merged
Merged
Conversation
…he approval nag (v0.281.3) Two defects visible in the first guidance lines the rebuilt topic maps produced on live tenants. - `f90fc16d7fb9a19` appeared as something "the fleet frequently works on". The digit rule exists for `v3`/`php8` but also admits hex handles; a long hex/base36 run (or a `tsk_…`-style prefixed id) is an identifier, not a name. - The approval-friction signal fired on instawp off THREE decisions (0 approved, 3 rejected = 100%). v0.280.0 fixed the missing denominator; a rate still needs a sample. Both the guidance line and the `policy.review` recommendation now also require ≥8 human approval decisions in the window. 137/137 governance + 18/18 tier-A policy. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two defects visible in the first guidance lines the rebuilt topic maps actually produced on the live tenants after #501.
1. Opaque identifiers read as topics
instawp, immediately after its map rebuilt:
f90fc16d7fb9a19is a handle. The digit rule inisEntityexists sov3/php8qualify, but it admits any hex run. Excluded: long hex/base36 tokens andtsk_…-style prefixed ids.2. The approval nag fired off three decisions
v0.280.0 fixed the missing denominator (a raw count of 3 rejections was firing on tenants that approve ~100%). But on instawp the window held 0 approved / 3 rejected = 100% — directionally true, and still far too thin to tell an owner their policy is miscalibrated or to tell every agent to expect rejection.
A rate needs a sample: both the guidance line and the
policy.reviewrecommendation now also require ≥8 human approval decisions in the window.137/137 governance + 18/18 tier-A policy.
🤖 Generated with Claude Code