Coldgate / Inspect declared authority
When a configuration grants more authority
A small configuration change can remove approval requirements and broaden declared access. Coldgate makes those changes visible for review.
Synthetic demonstration · Reproduced 16 October 2026 · Development project
01 / The input
An issue-creation tool moves from one named repository to a wildcard, while its declared approval requirement changes from required to not required.
02 / The result
| Represented claim | Before | After | Reported category |
|---|---|---|---|
| Approval | REQUIRED | NOT_REQUIRED | approval:weakening |
| Repository boundary | canadianbaconking-collab/coldgate | * | boundaries:widening |
| Credential names | READ_TOKEN | READ_TOKEN + WRITE_TOKEN | credentials:expansion |
The full comparison reports nine changes, including approval weakening, boundary widening, parameter widening and a newly listed email tool. The table highlights three of those changes.
Inspect full inputs and outputs (JSON) →03 / What this means for a review
These are specific questions for a configuration review: is the broader scope intended, who can approve it, and what independently verifies the effective controls? Credential names alone cannot establish privilege.
What this establishes — and its limits
This example uses saved synthetic reports with Coldgate overlay declarations, not standard MCP enforcement controls. Static claims do not prove runtime behaviour. Coldgate does not execute tools or enforce approvals. Its effect inference is conservative; the documented small holdout detected 1 of 4 consequential effects. Independent pilot results remain unrecorded.
This is an independently developed engineering example, not a client engagement or production validation.
Source and reproduction
Output generated from Coldgate revision 87844dd using the reproduction script. Read the source contract and limitations.
Reproduce the three examples locally
With the site and three project repositories checked out beneath C:/dev/playground, pin each project to the revisions below. Use clean checkouts and Node 24.19 or newer.
cd C:/dev/playground
git -C coldgate checkout --detach 87844dd8bbfeefae60202d175f18eefc51eecb0f
git -C driftglass checkout --detach e6858ef591b0012d3334d8943ef853eb4a6b04d4
git -C signalforge checkout --detach bfe0a9f93d7049ac9554061a58c119ae5ba517da
cd frostedlogic-site
node scripts/reproduce-work.mjs ../coldgate ../driftglass ../signalforgeApply the method
Discuss an AI authority review
Bring a specific workflow and the decision you need to make. We can scope the review, evidence needed, and practical next steps.