Ideas
Ideas that are not yet agreed as pykit work. An entry has no ID and no status,
and it does not authorize starting work. When the owner takes one up, it becomes
a New epic or feature, its section moves into that file, and the entry is
deleted. A dropped idea is deleted too.
| Idea | Summary | Source |
|---|---|---|
| model-vocabulary | A shared model vocabulary, normative for both ORM packages: audit-column semantics, a shared status enumeration and natural-key rules. Waits for an application that needs one of these to behave the same on Django and SQLAlchemy. |
F12.13, retired from E12 2026-09-29 |
| sqlalchemy-helpers | A SQLAlchemy AsyncIdempotencyStore, session and unit-of-work helpers, and readiness checks. Waits for a SQLAlchemy application to ask for them. |
F12.5, retired from E12 2026-09-29 |
| cloudevents-envelope | A CloudEvents envelope builder. Waits for the outbox/inbox subsystem to need one. | F12.6, retired from E12 2026-09-29 |
| claim-check | The claim-check pattern for large messages. Waits for a second storage backend. | F12.7, retired from E12 2026-09-29 |
| django-cloud-messaging-adapters | Django cloud messaging adapters. Waits for a second cloud backend; depends on messaging staying in rn-forge-django until F15.5 splits it (E15 design). |
F12.10, retired from E12 2026-09-29 |
| product-installer-contract | A shared ProductInstaller contract. Shared installer mechanics stay in rn-forge-tooling: do not create rn-forge-selfkit. Waits for a second product that needs the same contract. |
F12.8, retired from E12 2026-09-29 |
| devops-adapters | More rn-forge-devops adapters (ADR-0012): Azure DevOps Pipelines as a CI platform, and pnpm or nx and Maven or Gradle workspaces that read the graph from the stack's own tool. Waits for kiln to schedule an Azure DevOps pipeline or a multi-package Node or Java archetype. |
E16 review, 2026-10-15 |
| tool-version-probe | Ask an external executable for its version in rn-forge-commons. Waits for a second application that probes tools. |
F17.5 review, 2026-10-23 |
| release-recovery-drill | A live drill of tag-only release recovery. | S14.2.5, amended 2026-10-03 |
| sonar-branch-analysis-plan | Decide whether to change the Sonar plan so branch dispatch can read its quality gate. | S14.4.2, amended 2026-10-03 |
| auth-version-counter-retention | InMemoryAuthorizationVersions keeps one counter per account ever invalidated (16,000 after 16,000 invalidations, measured in S22.8.4). Deleting a counter can make an old context current, so a bound needs a protocol that keeps invalidation across caches sharing versions. |
S22.8.4, owner 2026-11-16 |
model-vocabulary
The model conventions guide
describes what both ORM packages supply today and keeps the rest advisory, as
the owner decided on 2026-09-25. These are the rules this entry would make
normative for both packages; applications could still treat them as advice. The
audit columns and version already exist in both packages. The status
enumeration and natural keys are the new parts.
There is no shared model base class or repository protocol. Django's ORM is active-record and SQLAlchemy's is data-mapper, so they differ on transactions, lazy loading, the identity map and migrations. A shared protocol would shrink to what both query APIs have in common. What is shared is a vocabulary that each package's base class follows without sharing code.
Audit columns
Every persisted entity carries four:
| Column | Type | Nullable | Meaning |
|---|---|---|---|
created_by |
string identifier | yes | The principal's subject at creation. Null for rows created by a migration or a system process. |
create_time |
timestamp with time zone | no | Set once, on insert. Never updated. |
updated_by |
string identifier | yes | The principal's subject at the last write. Null under the same conditions as created_by. |
update_time |
timestamp with time zone | no | Set on insert and on every update. |
- Times are UTC and timezone-aware.
- On a freshly inserted row,
update_timeequalscreate_time; it is never null. - The actor is the
Principal.subjectfromrn_forge.web.auth, so the audit trail names the caller the same way on every stack. - The Python names above are the contract. How one package maps them to database columns does not leak into the vocabulary.
status
Every entity carries a status drawn from one shared enumeration:
| Value | Meaning |
|---|---|
ACTIVE |
The normal state. Visible and mutable. |
INACTIVE |
Retained and readable, excluded from normal listings, not mutable through ordinary endpoints. |
DELETED |
Soft-deleted; see below. |
An application that needs a domain lifecycle (DRAFT, SUBMITTED, APPROVED,
…) models it as its own column and does not overload status. Django's Status
has five values today (Active, Inactive, Error, Deleted, Expired), so
adopting this enumeration changes it.
Optimistic concurrency
- The column is named
version. - It is a monotonically increasing
int, starting at 1 on insert. - The ORM layer bumps it on every write; the caller never does.
- A write that supplies a stale version fails; it does not silently win.
This is the only structural type declared over a persisted object: a Versioned
thing has a primary key and an int version, exactly the two values
check_precondition takes.
Natural keys
- A model declares its natural key as an ordered list of field names. Dotted
paths reach through a foreign key:
["code"],["organisation.code", "code"]. - The fields are unique together, and every one is non-nullable.
- The natural key is stable: fixtures, seed scripts and cross-environment references use it, so an ordinary update endpoint does not change it.
- A surrogate primary key still exists. The natural key is for loading and referencing, not for being the primary key.
Soft delete
Soft delete is a nullable delete_time column, not a status, in AIP-164's
shape, as ADR-0010 records.
F12.2 builds it.
tool-version-probe
Apollo probes ffmpeg, ffprobe, yt-dlp and osascript once at startup and
reports each as a version, present, or missing. Its version parsing is a
heuristic with application-specific fallbacks: a presence-only special case for
osascript, and the first 80 characters when no version token matches. Taken
up, it is a free function returning str | None, with "" for a tool that ran
and printed no version, not a Process classmethod: those return Self.
release-recovery-drill
Delete a package's latest GitHub Release while keeping its tag, rerun the
original main push workflow, and confirm the release is recreated from the tag
with its wheel and sdist and the tag still at its original commit; a second
rerun must skip it. The local scenarios with real Git repositories and mocked
gh cover the path. The drill is destructive and owner-run, so do it only if
the added confidence is wanted.
sonar-branch-analysis-plan
The organization's Sonar plan rejects reading non-main branch data, so a
dispatched branch scan cannot read its quality gate. Pull request analysis works
and is the validation route. Decide whether a plan change is worth it. The first
full task sonar:local run (2026-11-13) hit the same limit: the scan uploaded,
then reading the gate failed with "Organization is not allowed to access data
from non main branches".