archspec 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3b50ec4f86cfdf9e4f95b1cf4a28c4dec212d711781675dedd6648f13aed7c1f
-  data.tar.gz: 9303aefb00b161004cc515b0d1b2ad03b3e60f396ef34b9dc86be4e7a1825650
+  metadata.gz: 07a83d8f3402826cb160272cea2739a3ad9542bc7d35fd6590544c39fcf7c597
+  data.tar.gz: 5d087f15b56575032c262a7f7e097270b4bad4bb09acd066003bfbbc338900eb
 SHA512:
-  metadata.gz: 56bd81e5ee880404a80c7f29d498c58903bd8d087c5e8deb80af060d6d169c3b40e471eb09758500d6522516d83090b435b45ab243f780978539840b9548681e
-  data.tar.gz: a3dc2d41b6b97edd3ddacb8c84632c0b8ae81471c9132ec02ddbf66ce68d8dd916d068aeb366a8bed99f996ed6f81cda8a3a48b502459b0d25afc525d81df95d
+  metadata.gz: c1ee035facb38cb68d9bde3b469f6fdd0e98bf434437254c3f9123cb7eb4ca9cfb2206ce0e4ad01fd25179054cc91e0c821de729026a08e69bb2cfb99092c084
+  data.tar.gz: de5d78b6d8e71e26d2a9cc67e6ad0854f532b876bd7e885536e867ddf27d5fb1a324b3bdb79e63f4d880c0194de036e94c2ae77d10219bedd19f6d84008e0d6b

data/README.md

@@ -1,20 +1,24 @@
+<div align="center">
+
 # ArchSpec
 
-Static analysis for your architecture. A linter for Ruby and Rails boundaries.
+<strong>Executable architecture specifications for Ruby and Rails</strong>
+
+<p>Declare your components and boundaries in one <code>Archspec.rb</code>, and every change gets checked in CI, whether a person or a coding agent wrote it. No AI involved, just Prism.</p>
+
+Battle tested in [<picture><source media="(prefers-color-scheme: dark)" srcset="https://rubyllm.com/assets/images/logotype_dark.svg"><img src="https://rubyllm.com/assets/images/logotype.svg" alt="RubyLLM" height="30" align="absmiddle"></picture>](https://rubyllm.com) and at [<picture><source media="(prefers-color-scheme: dark)" srcset="https://chatwithwork.com/logotype-dark.svg"><img src="https://chatwithwork.com/logotype.svg" alt="Chat with Work" height="30" align="absmiddle"></picture>](https://chatwithwork.com)
 
-ArchSpec turns your application's architecture into executable checks. Declare
-your components, dependencies, and boundaries in one file, then check every
-change in CI, whether a person or a coding agent wrote it. It is plain static
-analysis: it reads Ruby source with Prism, never boots the app, and no AI is
-involved in checking your code.
+[![Gem Version](https://badge.fury.io/rb/archspec.svg)](https://rubygems.org/gems/archspec)
+[![Gem Downloads](https://img.shields.io/gem/dt/archspec)](https://rubygems.org/gems/archspec)
+[![CI](https://github.com/crmne/archspec/actions/workflows/ci.yml/badge.svg)](https://github.com/crmne/archspec/actions/workflows/ci.yml)
 
-It maps conventional Rails files to constants and checks the structural rules
-you write down: components, layers, constant references, inheritance, mixins,
-named method calls, method protocols, cycles, and Rails boundaries.
+<img src="https://archspecrb.dev/assets/images/archspec-check.png" alt="archspec check reporting an architecture violation with a code frame, the offending span underlined, and the evidence as a note" width="760">
 
-It does not try to infer the "true" design pattern of arbitrary Ruby code. You
-describe the architecture your team wants. ArchSpec checks whether the code still
-matches it.
+</div>
+
+---
+
+ArchSpec turns your architecture into executable checks: components, layers, constant references, inheritance, mixins, named method calls, method protocols, naming conventions, cycles, and Rails boundaries. It is plain static analysis: it reads Ruby source with Prism, never boots the app, and no AI is involved in checking your code. The full Discourse app, 1,899 files, checks in 2.5 seconds.
 
 ## Why ArchSpec?
 
@@ -32,6 +36,10 @@ to remember, and checks them on every change:
 - query objects do not call obvious write methods
 - generated code follows the same boundaries as hand-written code
 
+ArchSpec does not try to infer the "true" design pattern of arbitrary Ruby code.
+You describe the architecture your team wants. ArchSpec checks whether the code
+still matches it.
+
 ## Show me the code
 
 Start with conventional Rails boundaries:

data/lib/archspec/evaluator.rb

@@ -7,10 +7,15 @@ module ArchSpec
     def evaluate(definition, graph, todo: Todo.empty)
       diagnostics = parser_diagnostics(graph) + definition.rules.flat_map { |rule| rule.evaluate(graph) }
 
+      # Deduplicate before rejecting. One statement can raise several diagnostics
+      # that differ only in evidence, because `include Foo` is both an includes
+      # edge and a constant reference. Todo entries are matched on evidence, so
+      # rejecting first would drop the recorded diagnostic and report its
+      # surviving sibling as new.
       diagnostics
-        .reject { |diagnostic| graph.suppressed?(diagnostic) || todo.include?(diagnostic) }
         .sort_by { |d| [d.location.path, d.location.line, d.rule, d.message, d.evidence] }
         .uniq { |d| [d.rule, d.message, d.location.path, d.location.line] }
+        .reject { |diagnostic| graph.suppressed?(diagnostic) || todo.include?(diagnostic) }
     end
 
     private

data/lib/archspec/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ArchSpec
-  VERSION = '1.0.0'
+  VERSION = '1.0.1'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: archspec
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Carmine Paolino
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-08-19 00:00:00.000000000 Z
+date: 2026-08-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: prism