Summary

• replace positional actor transport selection with fluent operation dispatch for async, configured sync, send_to, and schedule
• keep direct committed calls as the preferred default and separate delivery/reminder options from final operation arguments
• reject declared operation names that collide with dispatcher or reference methods
• use operation and delivery_mode terminology throughout persistence, diagnostics, and authorization
• make internal methods with more than two arguments keyword-only
• preserve the original schema migration and rename persisted columns through a new reversible migration

Breaking change

The positional transport forms are removed. Use fluent selection:

account.disable(reason: "fraud")
account.async.disable(reason: "fraud")
account.sync(timeout: 10.seconds).status
send_to(account).disable(reason: "fraud")
schedule(at: 1.hour.from_now).evaluate(account_id:)

Direct calls remain preferred when delivery defaults are sufficient.

Persisted dispatch vocabulary also changes:

• message_name becomes operation
• message_kind becomes delivery_mode
• effect callback message-name columns become operation columns

Migration 20260813000000_rename_message_dispatch_columns.rb performs the reversible rename. Existing migrations are unchanged.

Correctness and security

• direct calls and configured sync accept declared public messages and queries
• async, send_to, and schedule accept declared public actor messages only
• private actor methods remain inaccessible
• actor-to-actor delivery and reminders remain staged transactionally and return nil
• failed or rejected source turns discard staged delivery
• outer transport keywords remain distinct from identically named operation arguments
• explicit observables remain unchanged and opt in

TDD evidence

Before the fluent implementation, the focused suite reported 16 runs with 4 failures and 10 errors. Fluent selection failed with ArgumentError: wrong number of arguments (given 0, expected 1).

Before the collision fix, the focused suite reported 19 runs, 74 assertions, and 2 failures because conflicting operations such as class, send, and tap were accepted instead of raising SolidObjects::InvalidActor.

The completed focused suite reports 19 runs, 99 assertions, 0 failures, 0 errors, and 0 skips.

Validation

• bundle exec ruby -Itest test/integration/fluent_dispatch_test.rb
• migration up/down/up smoke test on SQLite
• static audit: 0 internal methods with more than two positional parameters
• bundle exec rake

Final bundle exec rake result:

• 428 tests, 1,434 assertions, 0 failures, 0 errors
• 14 expected local environment-gated adapter skips
• Standard Ruby passed
• RuboCop inspected 185 files with no offenses
• RBS generation and validation passed
• Steep reported no type errors
• Brakeman reported 0 security warnings

GitHub CI passed SQLite, PostgreSQL, MySQL with mysql2 and Trilogy, Redis, JavaScript, the Ruby/Rails compatibility matrix, static checks, and Greptile review.

The gem version is bumped to 0.12.0; no tag was created and no release was published.