feat(core): step 5 — rules registry, 8 rules, scoring
4 months ago
Authored
grim- defineRule primitive + async evaluateRule producing RuleResult envelopes
(skipped-not-thrown for bad config/evidence), typed registry keyed id@version
- rules @1: account-age, min-merged-prs, pr-rate-limit (interval CoV evidence),
max-files-changed, english-only, crypto-address, honeypot, profile-readme
- scoring: abstract signal taxonomy (4 categories, missing categories degrade),
0-100 composition; fast-check properties: range, red-flags-never-raise,
determinism
- per-rule unit tests over fixture contexts (normalized captured events);
contracts: RuleResult envelope
Parentdda5e16
33 files changed
- DECISIONS.md+34−0
- VERIFICATION-QUEUE.md+10−0
- all-summaries.md+43−0
- bun.lock+8−0
- packages/contracts/src/rules.ts+20−0
- packages/core/fixtures/change-request.opened.event.json+27−0
- packages/core/fixtures/comment.created.event.json+24−0
- packages/core/package.json+5−1
