stellwerk 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 5a59c8761699131fdfb30f5a83782ba2b71a1bcc12bd59fed46f071a9306aba7
+  data.tar.gz: 1e7c0b76429f09eb9139493bf0e2b0a2b2f22599ed9e7d2b9ad6c5176ec571df
+SHA512:
+  metadata.gz: acfa6f9020aaf20e6ecc94b91cef9ac5331ab70b32f64113a0ebe6baa8ef5cb1f13dc2638cbd98a820bdf946d3598546abbafa550f710080f1f69086f213a8b7
+  data.tar.gz: d32d3de5760a3c9f01992cb0c24472b249220d13c859c07fd189e3b85876a8678b3ac0b7b0e52be4028d7da1699525aa758e01bfec2a908bedea8a2d3af36094

data/.tool-versions

@@ -0,0 +1 @@
+ruby 4.0.1

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.0.1] - 2025-12-10
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/IMPLEMENTATION.md

@@ -0,0 +1,70 @@
+# Stellwerk Implementation Notes
+
+We want to be able to enforce arbitrary restrictions on the graph.
+However, we also want to get some thing working, quickly.
+Ideally in a way that would be helpful with Clockwork.
+Let's start with a simple layered architecture.
+
+At some point it would be nice to ship
+
+- a template for hexagonal architecture
+- a separate CLI call to detect cycles between files
+
+## User Interfaces
+
+### CLI Call
+
+For now, don't take any arguments and just
+
+- ingest all ruby files in current and nested folders
+- check against configuration
+
+Later we can add a way to run on single files.
+
+🤔 If this is a tool for rails applications and needs application context, why not just a rake task? But compare packwerk
+
+### CLI Response
+
+- let's not care about compatibility with rubocop or anything like that for now. We probably want an LSP anyway at
+  some point.
+- set CI compatible exit code
+
+### Configuration
+
+For now, we just need an assignment of files to layers. However, later we probably want "components", "packages" or
+something like that as a generalized concept.
+
+OK so... let's assume for now all components are layers. Each component can consist of multiple files or folders.
+
+The simplest way to solve the immediate problem is to just use a YAML structure like so
+(assuming hashes in yaml are ordered)
+
+```yaml
+layers:
+  system_boundary:
+    - app/controllers
+    - app/jobs
+  business_logic:
+    - app/services
+    - app/interactors
+  queries:
+    - app/queries
+  models:
+    - app/models
+```
+
+Strings that are folder names would implicitly be completed with `+ "/**/*.rb"`.
+
+Considerations:
+
+- impractical if we want to reuse components in multiple rules
+- one-folder layers are a little verbose and I think we'll end up with lots of those
+- enqueuing jobs and running jobs from the queue are two different things... in terms of static dependencies,
+  jobs should probably live in the business logic layer
+- what about lib?
+
+## TODO
+
+- Shortcuts
+  - for CLI command, use a CLI library instead of hand-rolling it
+    - probably, `optparse` built into the stdlib

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2025 Philip Theus
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,71 @@
+# Stellwerk
+
+TODO: Delete this and the text below, and describe your gem
+
+Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/stellwerk`. To experiment with that code, run `bin/console` for an interactive prompt.
+
+## Installation
+
+TODO: Replace `UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG` with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org.
+
+Install the gem and add to the application's Gemfile by executing:
+
+```bash
+bundle add UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
+```
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+```bash
+gem install UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
+```
+
+## Usage
+
+TODO: Write usage instructions here
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Publishing to RubyGems
+
+1. Update the version in `lib/stellwerk/version.rb`. Push / merge to main.
+2. Build the gem:
+
+   ```bash
+   gem build stellwerk.gemspec
+   ```
+
+   This should produce `stellwerk-<version>.gem`.
+3. Sign in to RubyGems (only needed once):
+
+   ```bash
+   gem signin
+   ```
+
+4. Push the built gem:
+
+   ```bash
+   gem push stellwerk-<version>.gem
+   ```
+
+5. Tag the release:
+
+   ```bash
+   git tag v<version> && git push origin v<version>
+   ```
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/exterm/stellwerk. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/exterm/stellwerk/blob/main/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Stellwerk project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/exterm/stellwerk/blob/main/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "minitest/test_task"
+
+Minitest::TestTask.create
+
+require "standard/rake"
+
+task default: %i[test standard]

data/exe/stellwerk

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+
+require "stellwerk/command"

data/lib/stellwerk/command.rb

@@ -0,0 +1,3 @@
+require "stellwerk"
+
+

data/lib/stellwerk/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Stellwerk
+  VERSION = "0.0.1"
+end

data/lib/stellwerk.rb

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+require_relative "stellwerk/version"
+
+module Stellwerk
+  class Error < StandardError; end
+  # Your code goes here...
+end

metadata

@@ -0,0 +1,83 @@
+--- !ruby/object:Gem::Specification
+name: stellwerk
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: ruby
+authors:
+- Philip Theus
+bindir: exe
+cert_chain: []
+date: 1980-01-02 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: reference_extractor
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: activesupport
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+email:
+- philip@simplexity.quest
+executables:
+- stellwerk
+extensions: []
+extra_rdoc_files: []
+files:
+- ".tool-versions"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- IMPLEMENTATION.md
+- LICENSE.txt
+- README.md
+- Rakefile
+- exe/stellwerk
+- lib/stellwerk.rb
+- lib/stellwerk/command.rb
+- lib/stellwerk/version.rb
+homepage: https://github.com/exterm/stellwerk
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/exterm/stellwerk
+  source_code_uri: https://github.com/exterm/stellwerk
+  changelog_uri: https://github.com/exterm/stellwerk/blob/main/CHANGELOG.md
+  rubygems_mfa_required: 'true'
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 3.2.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 4.0.3
+specification_version: 4
+summary: Keep your Rails on track by enforcing a rules-based architecture.
+test_files: []