Skip to content

E15 — Package boundaries

State Active
Start Date 2026-10-15
Feature State Iteration Stories
F15.1 — Package boundary rule Closed release-4 2 Closed
F15.3 — rn-forge-data package Closed release-4 4 Closed
F15.4 — Domain errors in commons New deferred —
F15.5 — Framework-neutral messaging core New deferred —
F15.6 — Framework-neutral fixtures New deferred —
F15.7 — Framework-neutral Celery app factory New deferred —

Split framework-neutral areas out of rn-forge-commons into purpose-named packages, only when they pass the three-test rule of ADR-0011, and give every such package one adapter structure. A new adapter (an auth provider, a file format, a message store, an ORM) is then a module plus an extra, with no refactor of the core. rn-forge-auth and rn-forge-data qualify now. The messaging, fixtures and Celery areas of rn-forge-django, and the web dependency of the ORM packages, are deferred until a trigger fires.

The design holds the evidence, the adapter structure and the package contents. ADR-0011 records the rule and the adapter structure.

E13 owns all of the auth work. Its F13.2 creates the rn-forge-auth package under this epic's rule and adapter structure, and the rest of E13 adds the adapters in the same release. New adapter implementations are deliberately outside E15.

Back to the work index

F15.4 to F15.7 are tagged deferred. Do not start them unless the owner asks.

Governing decision: ADR-0011. Related: ADR-0002 (no aliases), ADR-0003 (extras and the facade), ADR-0004 (pinned tags).

Considered and rejected

  • A broad split of commons. Its base install is five small libraries, and a split removes no install weight.
  • rn-forge-logging, rn-forge-integration or rn-forge-resilience, rn-forge-messaging now, and rn-forge-fs, -lang or -runtime. The design gives the reason for each.

Answered questions

The owner answered the design's questions on 2026-10-15 in S15.1.1. The design records the answers.