vibecorp/checkout · PR #5538 · Sticky bucketing for billing redesign Demo PR (public-style)

Trust Certificate

Escalate to owner. Specific question required.

Required proof missing. Routed to owner with a clear human-ask.

82Trust score

Escalate

Intent

Implements sticky bucketing for billing redesign.

Change class

Feature flags · feature add · external client touched

Ownership boundary

Files contained within feature flags module. Ownership unambiguous.

High·Workflow: Feature-flag rollout changes·Reviewer cycles in history: 2

Required proof

Defined by Feature Flag Rollout Pack (v3). Maintained by VibeOps — improves with every customer's replay misses.

Kill-switch path

Found

Unit test added; CI green on retry branch.

Boundary isolation

Partial

Partial: covered for happy path, not for upstream 5xx storm.

Canary plan

Missing

Not present. Required by Integration Trust Pack v3.

Model route

Per-decision routing. Cheaper models do the classification; frontier model handles the reasoning; humans only on remaining ambiguity.

1

SLM (Kimi-style)

Naming, ownership classification, surface-level policy checks. Passed in 0.6s @ $0.003.

2

Claude Opus 4.7

Contract reasoning: would this retry storm an upstream that has no idempotency contract? Returned ambiguous.

3

Human (escalate)

Required only because contract proof remains missing. Routed to @connectors-team owner.

Human-ask · what reviewer actually needs to answer

Reviewer must validate the missing evidence items listed above.

Loading…