Exercise 3: Two Genuinely Rails-Specific Findings — Possible Solution
====================================================================

FINDING ONE: RUBY'S OPEN CLASSES (CHAPTER 1)
------------------------------
Per this chapter, ActiveSupport extends Ruby's own core classes directly - 3.days.ago is a real method call added onto Ruby's built-in Integer class, a technique called monkey-patching that Ruby treats as an ordinary, idiomatic part of the language. This is grounded in a real fact about Ruby's language design: Ruby permits reopening any class, including its own core ones, which neither Python's community norms nor PHP's own capabilities support in the same way.

FINDING TWO: THE REVERSED SECRETS PHILOSOPHY (CHAPTER 11)
------------------------------
Per this chapter, config/credentials.yml.enc holds the application's actual secrets, encrypted, committed directly to the repository, while config/master.key - the only file able to decrypt it - is the one file excluded from version control. This is grounded in a real, verifiable fact about how Rails' own credentials system works, and it's the literal reverse of the .env-file pattern every sibling course in this series used, where the secrets themselves were excluded and nothing needed to be committed encrypted.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names two findings unique to Rails among the four frameworks, and correctly grounds each one in a specific, verifiable technical fact - Ruby's language-level support for reopening core classes, and Rails' own credentials system committing encrypted secrets while excluding only the key - rather than restating a similarity Rails already shares with Laravel elsewhere in the course.