Skip to content

Accepts the function providers Amendment - #275

Merged
johnnyt merged 1 commit into
mainfrom
sp-mcfw-accept-amendment
Oct 13, 2026
Merged

johnnyt merged 1 commit into
mainfrom
sp-mcfw-accept-amendment

Conversation

@johnnyt

@johnnyt johnnyt commented Oct 13, 2026

Copy link
Copy Markdown
Member

Flips ADR-0004's 2026-10-13 Amendment (decision 3's re-stamp gains functions, and a list that does not resolve is refused at the entry), with its 2026-10-13 dated edit adding Driver.start_child_at/6, from proposed to accepted.

The record

docs/adr/0004-run-lifecycle-executor-seam-and-serialization.md, the 2026-10-13 sp-aa9z Amendment.

  • Version: statifier_persistence 0.25.0, tag v0.25.0 at 473bfd3, published on Hex 2026-10-13 by the release workflow.
  • Verified at: 473bfd3, the tag, which is also main: nothing has landed on main since the tag.
  • Claims checked: statifier 2.15.0's half, read at statifier-ex's v2.15.0 tag (99e7427): the functions field, put_function_providers/2 and new/2 raising on a list that does not resolve, Statifier.Position dropping and blanking the field, Statifier.Session.start_link/2's {:error, {:function_providers, reason}}, and Statifier.Invoke.Source.resolve/2 compiling content with no :function_providers. This package's half: the tripwire and the four-field stamp (step_loaded/8); the entry refusal after the re-entrancy check on create/4 and step/5 (check_function_providers/1), the error arm and the reason type; every row of the door table in the driver (check_function_providers/2, check_start_providers/1), the per-call override with an explicit nil (function_providers/2), the create carrying the list inside initialize: (create_opts/2) and the steps taking the driver's list (execution_opts/3); the child created with function_providers: nil and that nil reaching every step of the child's drive (create_child/6, advance/6), the child's driver keeping the list for the parent's answer; the start_child_at/6 refusal in its own {:refused, _} shape with no :child, :refused event; the named tests in function_providers_test.exs and the tripwire test in executions_test.exs; and the 0.25.0 changelog section.

The Amendment's own status word flips in place. Its sentence "this amendment is proposed until it is accepted" stays as written and is met by the dated foot Note, which records the flip, the version, the SHA and what was re-read. The diff removes one line, the status text; every other line is an addition at the foot of the file.

The Amendment's "on every step of that drive" for the child's nil was re-read against the driver: the child's create hands its options, function_providers: nil included, to the drive loop, and the loop hands the same options to every step.

Gate

Docs only: the diff touches only docs/adr/, outside the gate's build paths, so it touches no Elixir code and has no gate to run (the repo's CLAUDE.md commit row); CI still runs the full gate. No changelog fragment: ADRs are on changelog.d/README.md's "do not" side.

Refs: sp-mcfw

The ADR-0004 Amendment that re-stamps `functions` on every step and
refuses a function_providers list that does not resolve at the entry of
every event-carrying door, with its dated edit adding start_child_at/6,
merged at proposed; the code it decides shipped in
statifier_persistence 0.25.0 (tag v0.25.0, 473bfd3). Each claim was
re-read at the tag, which is also main, and each held. The Amendment's
status word flips in place from proposed to accepted, and a dated foot
Note records the flip, the version, the SHA and what was re-read. No
other line is removed.

Review: the diff touches only docs/adr/, outside gate.build_paths (lib/
test/ config/ mix.exs mix.lock), so it touches no Elixir code and has no
gate to run; committed on review of the diff. No changelog fragment:
ADRs are on the changelog.d/README.md "do not" side.

Refs: sp-mcfw
@johnnyt
johnnyt merged commit a89245b into main Oct 13, 2026
1 check passed
@johnnyt
johnnyt deleted the sp-mcfw-accept-amendment branch October 13, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant