vibecorp/platform · PR #5130 · Tag-based release notes config Demo PR (public-style)

Trust Certificate

Safe for auto-approval.

Cleared every required proof. Safe to merge.

82Trust score

Auto-approve

Intent

Implements tag-based release notes config.

Change class

Docs/config · feature add · external client touched

Ownership boundary

Files contained within docs/config module. Ownership unambiguous.

Low·Workflow: Docs & config changes·Reviewer cycles in history: 1

Required proof

Defined by Already covered (v3). Maintained by VibeOps — improves with every customer's replay misses.

No code-path touched

Found

Unit test added; CI green on retry branch.

Schema unchanged

Found

Detected in diff and verified by Trust Pack eval.

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…