dsl41 (codename)

dsl41 is a migration compiler for scheduler estates. It contains an AutoSys (JIL) frontend, a semantic IR, a linter, a Mermaid visualizer, a formal equivalence validator, and a Stonebranch Universal Controller backend. It also contains a Python DSL extracted from patterns found in the synthetic test corpus.

Read these documents in this order:

1. docs/autosys-semantics.md - the meaning of JIL (SEM entries)
2. docs/stonebranch-semantics.md - target model + AutoSys->UC mapping (UCS/M entries)
3. docs/ir-design.md - AST / IR-F / IR-G / oracle / equivalence design
4. docs/jil-statement-syntax.md - statement scanner spec
5. docs/decision-log.md - the reasons for the decisions
6. CLAUDE.md - working agreement + implementation order

Status: all ten compiler phases are built and tested. The phase-11 runner (docs/runner-design.md) is also complete: 11a (engine core + bisimulation gate), 11b (process lifecycle tier: wrapper shim, real adapters, WAL journal, crash-recovery resume — spool contract frozen in docs/supervisor-protocol.md), 11c (calendar scheduler, preflight, control socket, headless CLI), 11d (Textual TUI), 11e (serve via textual-serve), and 11f (the detached supervisor tier). The scheduler obeys AutoSys calendars (DL-56/57). It applies standard calendar day sets directly. It applies extended (autocal-rule) calendars through a built-in interpreter of the doc-frozen SEM-36..39 semantics. The memo below has the source map.

CLI

There is one entry point (pyproject [project.scripts]): dsl41 = dsl41.cli:app. Run uv run dsl41 --help, or install the package and run dsl41 directly. Every command takes one or more JIL files, which together form one catalog. The commands accept autocal_asc calendar exports (calendar / cycle / extended_calendar / ext_calendar statements) together with job definitions. All commands share the exit-code contract: 0 = success or clean, 1 = findings (lint, equiv only), 2 = the input never reached the tool (unreadable file, JIL parse error, or DL-07 lowering refusal). --permit-unknown is the DL-07 escape hatch on every command: it carries unknown attributes verbatim instead of a refusal.

Resolve estate templating (preprocessor)

dsl41 resolve jobs.jil.tpl -p env.properties -o jobs.jil

Estate JIL frequently contains ~{$NAME}~ placeholders. An external properties mechanism replaces them before the scheduler sees the text. The resolve command does the same step (DL-19). It reads KEY=VALUE properties files. Later files override earlier files. Resolution is an order-independent fixpoint. If a token stays unresolved, the command reports a loud error. With --permit-unresolved, the command leaves such tokens verbatim. Thus resolved JIL flows through the ordinary pipeline. The compiler core itself never models templating.

Lint a catalog

dsl41 lint jobs.jil globals.jil            # errors fail (exit 1)
dsl41 lint --strict jobs.jil globals.jil   # warnings fail too

The command runs rules L001-L019 (IR-F rules, truth-table rules, graph rules over the derived graph, dangling-name rules). --strict is the migration gate: do not ship a catalog that lints dirty.

Visualize the dependency graph

dsl41 viz jobs.jil -o graph.md             # Markdown report of Mermaid charts
dsl41 viz --direction TD --collapse-threshold 20 jobs.jil
dsl41 viz --elk jobs.jil                   # ELK layout (VS Code; GitHub ignores it)

The report shows each independent workflow as its own chart (largest first). A legend and appendices list everything that the charts omit: standalone admin-wrapper jobs (charted again with --include-singletons), assumed-edge assumptions, redesign flags, OR shapes, and cycles. In a chart, boxes are subgraphs, and edges carry their E/A/R migration class (solid/dashed/thick-red). The charts mark file watchers and schedules as triggers. Mutual exclusions appear as lock links or as a shared lock hub. If a box has more direct members than the collapse threshold (default 12), the box folds into a single node. Any Mermaid renderer works (GitHub, mermaid.live, IDE preview).

Migration report

dsl41 report jobs.jil -o report.md

The command writes per-catalog markdown from the UC backend: refused (R) constructs, recorded per-edge assumptions (A rows), and the open U-question table. After the report is generated, the command always exits 0. The report itself is the loud channel. Use lint --strict as the pass/fail gate.

Emit UC workflow records (base subset)

dsl41 uc jobs.jil -o bundle.json            # CREATE-ONLY taskWorkflow records
dsl41 uc --strict jobs.jil                  # exit 1 if anything was quarantined

The command emits one taskWorkflow record per serializable workflow, in exactly the shape frozen in docs/uc-edge-schema.md (U3a, DL-55). The records use base edge conditions only (Success / Failure / Success/Failure), with retainSysIds: false and no system ids. If a workflow contains an edge that the base schema cannot express (a t()-derived condition, a variable condition), the command quarantines the whole workflow. The bundle's own ledger lists the quarantined workflow. There is no partial workflow and no silent edge drop. Rich condition forms and write-path verification stay blocked on U3b (live controller).

Prove two catalogs equivalent

dsl41 equiv new.jil --against old.jil                       # all tiers
dsl41 equiv new.jil -b old.jil --tier c --scripts 50        # more oracle runs
dsl41 equiv new.jil -b old.jil --rename OLD=NEW --case-fold # renamed estate

Tier a is structural (canonical-form diff). Tier b enumerates per-job truth tables. If a state space is too large, tier b defers and never fails. Tier c compares oracle traces over seeded deterministic event scripts. Identical canonical hashes short-circuit to equivalent. On any divergence, the exit code is 1. Typical use: refactor a catalog (by hand or via decompile-edit-rebuild), then prove that nothing changed.

JIL -> DSL (decompile)

dsl41 decompile jobs.jil -o catalog.py

The command emits a runnable Python module over the phase-10 builders. When you run the module, it rebuilds a catalog whose canonical form equals that of the original (the round-trip property, tested corpus-wide). Recognized structural patterns fold into builder calls from the closed DL-38 registry, which dsl41 folds lists. --no-fold disables the folding.

DSL -> JIL (build)

The reverse direction is a Python API, not a CLI command:

from dsl41.dsl import CatalogBuilder

b = CatalogBuilder()
b.machine("prod1")
with b.box("nightly"):
    b.job("extract", command="/opt/etl/extract.sh", machine="prod1")
    b.job("transform", command="/opt/etl/transform.sh", machine="prod1")
    b.job("load", command="/opt/etl/load.sh", machine="prod1")
b.sequence("extract", "transform", "load")

jil_text = b.to_jil()   # JIL text, byte-for-byte what the front end accepts
catalog = b.build()     # ...or parse+lower it through the real pipeline

job() keyword names are JIL attribute names. sequence() wires s()-chains, and parallel() wires a fan-out and fan-in. Both refuse to merge into an existing condition (DL-17: no silent loss). There is no second lowering path. The builder generates JIL and reuses parse -> lower, so lint, viz, and equiv all apply unchanged to DSL-built catalogs. The round-trip workflow: decompile an estate to Python, edit it, run the module, and equiv the result against the original.

Run an estate (phase 11)

dsl41 run jobs.jil --run-root ./run1            # headless engine + control socket
dsl41 sendevent STARTJOB -J job_a -S ./run1/control.sock
dsl41 query status -S ./run1/control.sock       # JSON: statuses, timers, log paths
dsl41 ui -S ./run1/control.sock                 # attach the TUI; q detaches
dsl41 run jobs.jil --run-root ./run1 --ui       # ...or one terminal owning both
dsl41 rehearse jobs.jil --hours 24              # virtual clock: a day in seconds
dsl41 serve -S ./run1/control.sock              # the same TUI over the web

The TUI (jobs table with pending timers and alarms, explain pane with per-atom condition truth, log tail, sendevent console) is the optional [ui] extra: pip install 'dsl41[ui]'. It is a thin client of the run's control socket. sendevent/query speak the same protocol.

The scheduler obeys run_calendar/exclude_calendar (DL-56/57). Standard calendar day sets apply on the job's local day (run minus exclude, SEM-31). The built-in autocal rule engine interprets extended calendars (SEM-36..39). An exhausted calendar makes the job dormant and does not cause an error. Before the engine starts, preflight (ss8) examines the calendar wiring: dangling references are errors, and empty or stale calendars cause warnings.

Detached mode (phase 11f)

By default, a run is tethered: if you kill the engine, its jobs terminate (durably recorded even under kill -9, ss6a). If a long-running estate must survive an engine restart (an upgrade), add --detached:

dsl41 run jobs.jil --run-root ./run1 --detached   # CMD jobs run under a supervisor
# ...stop the engine (SIGINT) -- jobs keep running under the supervisor...
dsl41 run jobs.jil --run-root ./run1 --detached --resume   # reattach, no re-run
dsl41 supervise list --run-root ./run1            # what the supervisor is holding
dsl41 supervise shutdown --run-root ./run1        # stop it (TERM->grace->KILL)

A per-run-root supervisor (runner_supervisor.py, stdlib-only, one process per run root) owns the lifelines of the wrappers. Thus the parent of the jobs is the supervisor, not the engine. If the engine stops or crashes, the jobs continue to run. --resume --detached reconnects and reattaches to the still-alive runs (no reconciliation injection, no re-run). It also resolves, from the spool, any runs that finished meanwhile. The engine holds a single fencing lease. The socket protocol of the supervisor is frozen in docs/supervisor-protocol.md ss5. supervise is read-only by default (DL-42).

Serving the TUI over the web (phase 11e)

dsl41 serve -S ./run1/control.sock wraps textual-serve around the same app. Every browser tab gets its own dsl41 ui --socket subprocess attached to the run (the ss11 one-instance-per-viewer split). The page shows this subprocess as a terminal. textual-serve ships no authentication, so the default bind is loopback (127.0.0.1:8000). To reach it from a different host, use a reverse proxy or an SSH tunnel, never a wider --host:

# tunnel: from the operator's machine
ssh -L 8000:localhost:8000 runhost

# or an nginx location block on the run host
location /dsl41/ {
    proxy_pass http://127.0.0.1:8000/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}

Put authentication (basic auth, an OIDC gate, client certificates — whatever the estate already trusts) in that proxy layer. dsl41 has no authentication of its own here. The control socket is 0600 from birth (ss10). Thus serve only sees what its own user can already reach directly. It does not widen access. It makes existing access reachable from a browser.

Implementation memo

All ten phases from the implementation order in CLAUDE.md are implemented and tested. The build order is: ast_jil, conditions, ir, lint, derive, viz, oracle, equiv, backend_uc, dsl. Phase 11 (the runner, docs/runner-design.md) has six tiers, all built:

• 11a — the sans-IO engine loop, VirtualClock, FakeAdapter, and the two oracle additions, gated by the ss13 bisimulation suite
• 11b — the process lifecycle tier (per-run wrapper shim, LocalCommand/FileWatcher adapters, WAL journal, crash-recovery resume with the reconciliation ladder), with the spool contract frozen in docs/supervisor-protocol.md
• 11c — the ss5 calendar scheduler, ss8 preflight, ss10 control socket (sendevent parity + queries + subscribe), and the headless run/rehearse/sendevent/query CLI verbs
• 11d — the ss11 Textual TUI (dsl41 ui against a running engine, or dsl41 run --ui, with the optional dsl41[ui] extra)
• 11e — dsl41 serve via textual-serve, same extra
• 11f — the ss6a Tier-1 supervisor (dsl41 run --detached, dsl41 supervise), a stdlib-only runner_supervisor.py that speaks the frozen docs/supervisor-protocol.md ss5 socket protocol

The suite spans 25 test files (pytest --collect-only -q shows the current count) plus the 27-file synthetic/doc-derived JIL corpus under tests/corpus/.

Source map

• src/dsl41/init.py — module map docstring only (no exports). It records the ten-phase build order.
• src/dsl41/ast_jil.py — JIL statement-level scanner + AST + preserve/canonical renderers. Fidelity contract F1-F4: byte-exact render(parse(x)) == x (F1, fuzzed by F3), canonical-mode fixpoint (F2), escaped-colon torture (F4)
• grammars/condition.lark — condition-expression grammar (lark, LALR). Single flat start rule, & and | at equal precedence, strictly left-associative (Q1 resolved, DL-53 — the earlier C-style candidate rule is deleted)
• src/dsl41/conditions.py — lark loader + Tree->Cond transformer for condition/box_success/box_failure expressions. Lookback + span retention.
• src/dsl41/ir.py — IR-F Pydantic entity models + AST->IR-F lowering. If permit_unknown is not set, the DL-07 firewall refuses unknown attributes. Calendar/cycle repeat-key lanes (CalendarIR.conditions, CycleIR.periods, DL-57) keep real multi-condition/multi-period autocal exports loadable.
• src/dsl41/lint.py — Violation model + rules L001-L019 (pure IR-F rules L001-L005/L015, truth-table rules L006/L007 joined in phase 8, graph rules L008-L014 over the derived graph, dangling-name rules L016-L018)
• src/dsl41/derive.py — IR-F -> IR-G: seven analysis passes that produce edges, mutex pairs, box tree, same-cycle detection, M01-M36 mapping-row classification
• src/dsl41/viz.py — IR-G -> Markdown report of per-workflow Mermaid charts (DL-35): component split, trigger/lock visual grammar, E/A/R edge-class arrows, collapse threshold, appendices for everything that the charts omit
• src/dsl41/oracle.py — AutoSys discrete-event semantics interpreter. Script-driven completion, edge-triggered re-evaluation, per-SEM-entry trace tests.
• src/dsl41/equiv.py — equivalence validator: canonical form + tier a (structural), tier b (per-job state-space enumeration), tier c (oracle trace comparison)
• src/dsl41/backend_uc.py and src/dsl41/uc_oracle.py — UC backend pair. backend_uc builds the UC twin model, classifies edges, emits the migration report, and serializes the U3a base CREATE-ONLY record bundle (docs/uc-edge-schema.md — rich condition forms blocked on U3b). uc_oracle is the UC-side twin interpreter that runs the P-Mxx expected-divergence pairs against it. It shares Event/TraceEntry with oracle.py.
• src/dsl41/dsl.py — builder surface (job/box/sequence/parallel) + decompiler, extracted from corpus-observed patterns only (phase 10, last by design)
• src/dsl41/placeholders.py — non-core estate templating preprocessor (DL-19): ~{$NAME}~ resolution from KEY=VALUE properties files (fixpoint, loud on residue), behind the resolve verb. Nothing in the core imports it.
• src/dsl41/autocal.py — extended-calendar rule interpreter (DL-57): pure functions from the opaque CalendarIR/CycleIR carry (DL-36) to day sets per the SEM-36..39 doc-freeze — the SEM-37 date-condition keyword inventory, the SEM-38 filter-then-replace disposition pipeline (holiday action governs holcal dates — Q8a resolved, DL-58), uniform blind adjust, cycles, dormancy ceilings. Undocumented composition corners run on pinned deterministic defaults (# PENDING: Q8b-Q8d, DL-59 — refusals only for the genuinely uninterpretable, so an ordinary estate always schedules). The runner's scheduler and preflight consume it. It is also the reference implementation that a live autocal is diffed against (Q8 residue).
• src/dsl41/runner.py — phase-11 engine: single-writer loop over the oracle (dispatch table, time-ordered event queue, stale-completion gate), VirtualClock + RealClock, FakeAdapter + LocalCommandAdapter + FileWatcherAdapter, inputs-only WAL journal, resume/reconciliation ladder, calendar scheduler (ss5: standard calendar day sets and windowed extended-calendar generators, DL-56/57), preflight (ss8), control-socket server (ss10: sendevent parity, status/trace/explain/plan, subscribe). It also contains the ss6a Tier-1 detached path (SupervisorClient + SupervisedCommandAdapter: SPAWN through the supervisor, await the exit push, detach-stop vs oracle-kill cancellation, resume-time reattachment)
• src/dsl41/runner_supervisor.py — the ss6a Tier-1 supervisor (phase 11f): stdlib-only (same enforced boundary as the wrapper), one per run_root. It owns the wrapper lifelines, so an engine restart reattaches and does not kill jobs. It speaks the frozen docs/supervisor-protocol.md ss5 socket protocol (SPAWN/SIGNAL/LIST/SHUTDOWN/PING + lease), with same-uid peer-cred and a Linux subreaper.
• src/dsl41/runner_tui.py — the ss11 Textual TUI (optional dsl41[ui] extra): a thin client of the control socket only (jobs table with pending timers/alarms, explain pane with per-atom truth, log tail of the ss6 std files, sendevent console). Subscribe is a wake-up signal, and every view that the TUI shows comes from the idempotent ss10 queries.
• src/dsl41/runner_wrapper.py — the ss6a Tier-0 per-run lifecycle recorder: stdlib-only (enforced DL-42 extraction boundary). It records spawn.json/status.json durably. On lifeline EOF, it kills and records. Spool contract in docs/supervisor-protocol.md.
• src/dsl41/cli.py — typer entry points: lint, equiv, report, uc (the U3a record bundle — --strict fails on quarantine), viz, decompile, folds (the DL-38 fold registry), resolve (the DL-19 templating preprocessor), journal (render-by-replay of a run WAL), run (headless executor: wall clock, real processes, control socket, stop with SIGINT/SIGTERM, and --detached runs CMD jobs under a supervisor that survives engine restarts), rehearse (virtual clock + scripted adapters: a 24h estate in seconds, same engine path), sendevent and query (clients of a running engine's control socket), supervise (11f: list/shutdown a run-root's detached supervisor, read-only by default), ui (the ss11 Textual TUI attached to a running engine — run --ui starts both in one terminal), and serve (11e: wraps textual-serve around the same app, one dsl41 ui subprocess per browser session — optional dsl41[ui] extra, loopback by default). Exit 2 = catalog load/usage failure everywhere, preflight refusals included. Exit 1 = findings for lint/equiv, and a mid-run engine failure for run/rehearse. report always exits 0 once generated: the report itself is the loud channel.
• src/dsl41/main.py — python -m dsl41. It is needed because serve spawns the app of each session as <sys.executable> -m dsl41 ui --socket <path>.

Tests

• tests/test_ast_fidelity.py — F1-F4 round-trip fidelity, scanner structure and error paths, whitespace-sensitive edge cases
• tests/test_condition_grammar.py — grammar-level accept/reject cases, doc-derived only
• tests/test_conditions.py — Cond model shapes, lookback semantics, span retention, the test_sem03_precedence_pinned_model_level precedence-pinning test (DL-53)
• tests/test_ir.py — IR-F lowering decisions: SEM-30/31/32/33/34, subcommand support v1, type-inapplicable attributes
• tests/test_lint.py — L001-L005/L015 rules plus the lint CLI exit-code contract
• tests/test_derive.py — the seven IR-G passes plus the graph-rule lint additions L008-L014
• tests/test_viz.py — Mermaid render structure (balanced blocks, id-safety, one golden render), the DL-35 markdown report (components, appendices, mutex encodings) plus the viz CLI
• tests/test_oracle.py — AutoSys oracle trace tests against the SEM entries. They cite the sparse T-ID index of dossier §8 (T01–T34 range, not contiguous — T03/precedence is pinned at parse time in test_condition_grammar.py, not here). Every test runs twice — Oracle-direct and Engine(VirtualClock, inert FakeAdapter) via tests/bisim_harness.py — the runner-design ss13 bisimulation gate.
• tests/test_resources.py — DL-50 resource-manager tests that need direct Oracle access (bucket introspection, the cross-order safety+liveness Hypothesis property), outside the bisimulation harness by design
• tests/test_autocal.py — the SEM-36..39 doc-freeze pinned: every worked example that the vendor docs contain, plus one test per Q8 pinned default or refusal (test_sem3x_* / test_q8x_* naming)
• tests/test_autocal_breadth.py — breadth over the interpreter, the scheduler/preflight wiring, and the ir.py calendar lanes: SEM-37 token-family coverage, generation edge behavior, every expected date derived by hand from the real 2026/2027 Gregorian calendar independently of the code under test
• tests/test_runner.py — phase-11a runner suite: oracle additions (next_timer_due/advance), VirtualClock, engine dispatch/cancellation/horizon discipline, the stale-completion gate, and the feed-only vs advance+feed and oracle-vs-engine hypothesis properties
• tests/test_runner_lifecycle.py — phase-11b lifecycle tier: wrapper process matrix (pgid separation, parent-loss kills, fd hygiene), the DL-42 phase-boundary kill matrix, spoofed-record/boot-flip guards, the engine-SIGKILL crash-recovery integration test (tests/runner_crash_driver.py is its engine subprocess), and the DL-44 review-finding regressions (kill-wins gate, advance-record replay)
• tests/test_runner_journal.py — WAL record shapes, read_journal tolerance/refusals, catalog-hash sensitivity, replay fidelity, journal-first source tagging, and the journal CLI
• tests/test_runner_adapters.py — RealClock, LocalCommandAdapter end-to-end (SEM-09 boundary, append/stdin/profile semantics, KILLJOB kill path), FileWatcherAdapter steady-size polling under VirtualClock, and the AdapterResult mapping
• tests/test_runner_scheduler.py — phase-11c scheduler occurrence math (days/times/ start_mins, timezone + DST corners, E10 defaults), engine integration under the virtual clock, resume re-anchoring + the E9 missed-tick drops, the ss8 preflight rule fixture pairs, and the DL-56/58 calendar rules (local-day membership, run-minus-exclude, exhaustion dormancy, row-time firing — E11 resolved)
• tests/test_runner_control.py — phase-11c control socket (sendevent parity verbs, status/trace/explain/plan queries, subscribe backfill/live seam, socket hygiene), the DL-45 commit-discipline regression, the run/rehearse/sendevent/query CLI, and the DL-46 status-response fields (pending_timers, log paths)
• tests/test_runner_tui.py — phase-11d TUI (skips without the [ui] extra): the sendevent console parser, ControlClient against a real ControlServer (round trip, reconnect, subscribe), and the ss13.6 pilot smokes (table, explain atoms, pending timers, log tail, key-driven STARTJOB)
• tests/test_runner_serve.py — phase-11e serve CLI: missing-socket and missing-extra exit-2 paths, the constructed textual-serve command (a socket path with a space is quoted), default loopback bind, bind-failure exit 2 — the real textual-serve Server is always monkeypatched (ss13.6 posture, thinner still: a CLI wrapper, not a pilot)
• tests/test_runner_supervisor.py — phase-11f supervisor tier: the frozen ss5 socket protocol (unknown verb / bad version / malformed line, lease held / expire / re-acquire fencing monotonicity / stale token, SPAWN idempotency, SIGNAL pid-reuse refusal, peer-cred, stale-socket reclaim), the import-boundary AST test, Linux-only subreaper, and the detached kill matrix (SIGKILL engine → survive + reattach, kill -9 supervisor → spool-resolve TERMINATED, orderly SHUTDOWN, detach-stop SIGINT → reattach SUCCESS, oracle KILLJOB detached)
• tests/test_equiv.py — canonical form, tiers a/b/c, the L006/L007 lint rules (tested here because they share equiv's truth-table machinery), and the equiv CLI
• tests/test_backend_uc.py — edge classification, migration report, report + uc CLIs, the U3a record bundle (frozen-shape golden test, CREATE-ONLY hygiene, quarantine)
• tests/test_uc_oracle.py — UCS-entry trace semantics (UCS-01/02/03/09/13) plus the P-Mxx expected-divergence pairs against the UC twin interpreter
• tests/test_dsl.py — the four corpus-extracted builders, cond_to_source fidelity, and the decompile round-trip property
• tests/test_placeholders.py — the DL-19 templating preprocessor: every format decision in the docstring of placeholders.py pinned, plus the resolved-corpus end-to-end run through the ordinary pipeline

What's not done

A 2026-07-28 public-doc sweep (DL-53) closed Q1, Q4, Q5 (autosys dossier §9) and U2, U4, U5, U6a, U7, U8 (stonebranch Part III). Each closure is pinned to a dossier citation. DL-54 (same day) then resolved Q2a: zero-lookback anchors to the dependent job's own last end, cited verbatim. DL-54 also flipped the Q3 default to arm-and-wait. Now, if a false condition or a hold blocks a scheduled tick, the job arms, and the run is not abandoned. DL-55 (same day) split U3. U3a, the base CREATE-ONLY workflow record schema, is doc-frozen in docs/uc-edge-schema.md, and dsl41 uc emits it. U3b (rich condition forms, the live /resources/openapi.json pull, write-path verification, and the generated-from-OpenAPI client, DL-08) stays blocked on a live controller. DL-56/DL-57 (2026-07-28/29) then doc-froze extended-calendar semantics (SEM-36..39) and made the runner obey calendars. This opened Q8a-Q8e (autocal generation corners — each a pinned default or refusal in autocal.py), Q9 (which spelling autocal_asc -E emits — both accepted meanwhile), and E11 (run_calendar without start_times/start_mins refused fail-closed). A 2026-07-30 verified-citation sweep (DL-58 — vendor KBs and Broadcom-staff community answers, every citation re-fetched and examined before any pin moved) then closed Q2b (a never-run dependent satisfies s(A,0) — pin confirmed), Q3 (arm-and-wait confirmed with a no-expiry latch, the abandon switch deleted, new narrow residue Q3c — whether a member's latch survives across box runs), Q7 (a present fail_codes decides alone — one corner pin flipped in ir.exit_is_success: unlisted codes are SUCCESS, not threshold-judged), Q8a (a specified holiday action governs holcal dates — the disagreement refusal deleted), Q8e (CWEEK = consecutive 7-day chunks from each period's start), and E11 (row-time firing implemented: calendar rows' own HH:MM, 00:00 default, job start_times overrides). DL-59 (same day, a priority decision) then downgraded the remaining scheduler-path refusals to documented deterministic defaults, so an ordinary estate always loads and schedules. Q8b runs replace-then-shift, and the Q8d all-exclusive compounds evaluate literally. docs/live-instance-runbook.md keeps the probe protocols. If instance access appears, these protocols can confirm vendor parity. DL-60 (same day) closed Q9 from one observed autocal_asc export sample, which pinned the format (extended_calendar: spelling, empty-valued keys emitted, workday: all, braces as condition grouping, WORKD#L, holiday: S without holcal, HH:MM:SS row tails). These facts carry the dossier's weakest confidence marker, [F]: one observation, not verified against TechDocs. Five interpreter/scanner gaps were also corrected the same day. Without the correction, each of these gaps refuses an ordinary export. Still open: Q3c, Q6 (narrowed — the ON_ICE atom half is now cited), Q8b-Q8d (autosys dossier §9), U1, U3b, U6b (stonebranch Part III), and the runner's E5-E10 (runner-design ss15). E8 was re-swept: a spawn-path signal-9 KB leans FAILURE, but the mid-run kill still needs a live instance. The questions with a behavior default in code (Q3c, Q8b-Q8d, U1, U3b, E5-E10) run on a documented default marked # PENDING: Qn/Un/En. Q6 is dossier-only (no code switch), and U6b lives in the backend_uc migration-report question table. Q3c, Q6, and Q8b-Q8d need a live AutoSys instance. U3b needs a live UC controller. The runner is complete through phase 11f (the detached supervisor tier). The custom-pattern door of the decompiler (--patterns recognizer/expander pairs, agreed alongside DL-38) remains the one designed-but-unbuilt item.

Release

Releases are tag-driven. A push of a tag that matches v* starts .github/workflows/release.yml. The workflow runs the test suite. Then it builds the sdist and the wheel. Then it runs twine check --strict and publishes to PyPI. Publication uses trusted publishing (OIDC) in the pypi environment. The repository holds no PyPI token. The header comment of the workflow records the one-time setup on pypi.org.

The project is before 1.0. A minor bump (0.6.0 -> 0.7.0) carries a functional unit. A patch bump (0.6.0 -> 0.6.1) carries documentation or a correction with no behavior change.

Make a release

First, make sure that the working tree is clean. Make sure that main is pushed. Then run the same gates as CI:

uv run ruff check src tests
uv run mypy src
uv run pytest -q

If the gates pass, set the new version in pyproject.toml. Then run uv lock. This command writes the same version into uv.lock. Commit both files and push them:

git commit -am "chore: X.Y.Z (one-line summary)"
git push origin main

Then tag that commit and push the tag:

git tag -a vX.Y.Z -m "X.Y.Z: one-line summary"
git push origin vX.Y.Z

The tag must point at the commit that carries the same version in pyproject.toml. If the two disagree, the tag and the published artifact describe different trees.

Last, make sure that the release workflow is successful. Then read the project page at https://pypi.org/project/dsl41/.

Note: a local uv build writes into the ignored dist/ directory. It is a test of the build only. The workflow is the one publication path.

CAUTION: PyPI refuses a second upload of a version that exists. Do not move a tag after a successful publish. Release the next patch version instead.

License

dsl41 is dual-licensed:

• Open source: GNU AGPL-3.0-only. If you distribute modified versions, or offer them as a network service, you must offer the complete corresponding source under the same terms.
• Commercial: organizations that cannot accept AGPL obligations can obtain a commercial license — see COMMERCIAL.md.

Copyright (C) 2026 dsl41 authors. External contributions require a signed CLA that preserves the dual-licensing right. Corpus hygiene rules also apply (see LICENSING.md).

Most of the code is written with the assistance of industrial coding agents — primarily Anthropic's Claude — while the original ideas and design are my own.