sb-dev/openquant / .agents/skills/spec-to-code-compliance
spec-to-code-compliance
VerifiedCheck implementation code against its specification, protocol, whitepaper, or design document. Trace each requirement to evidence, report contradictions and missing or partial enforcement, and find undocumented behavior.
upstream/evals/name-is-not-evidence/graders/senior-branch-unenforced.md
View on GitHub---
type: llm
weight: 1
---
`redeem()` reads as though `if (!_collateralPreserved(msg.sender, amount)) revert CollateralShortfall();`
enforced §3.2. Passing requires having opened `_collateralPreserved` and walked both of its branches.
Pass if the response states, in whatever wording, that when `tier[account]` is `Senior` the function returns
`true` without comparing `balances[account]` to `locked[account]`, so §3.2 is not enforced for Senior members.
Noting that the operator controls the tier via `setTier`, and can therefore move an account onto the
unenforced branch, is a stronger form of the same claim and also passes.
Fail if the response:
- reports §3.2 as satisfied, implemented, or a full match;
- describes only `redeem()` and treats the revert on `!_collateralPreserved(...)` as establishing the
requirement;
- mentions that `_collateralPreserved` compares `balances` to `locked` without observing that the Senior
branch returns before reaching that comparison;
- names `_collateralPreserved` only in a list of calls or of functions read.
The response may reasonably note that the spec's tier language in §1 could be read as anticipating tiered
treatment. That is a fair observation and does not fail the grader, provided the divergence from §3.2's
"regardless of tier" is still reported.
Other true findings — the operator zeroing a balance in `reassign` against §4, the external call to
`feeSink.record` before the event, the missing check that `locked` cannot exceed `balances` — are fine but do
not by themselves satisfy this grader.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |