Skip to main content
Lab notebook · libs/edilint

edilint climb

Where edilint started, the summit it is working toward, the rules it may not break, and every merge of the last 30 days, each tied to the roadmap waypoint it served or marked unplanned.

Latest leg: No changes merged on 2026-11-20

Now climbingchecking

Checking the operator for recent events…

Merge-queue moves and narrated legs appear here when the operator is reachable.

Base, summit and ropes

Base

The problem the climb started from

Invisible EDI defects (homoglyphs, short counts, mixed line endings, trailer miscounts) pass through healthcare clearinghouses and fail downstream. edilint is a public Go linter and fixer for X12, HL7v2 and EDIFACT that makes those defects visible in CI, climbing from v0.6.0 toward the v1.0 "legitimately useful" exit criteria.

Source: ROADMAP.md#current-status · climbing since 2026-08-01

Summit

Where it is trying to get to, as measured

Roadmap gates met (Now list)
58.3%
target ≥ 100%
7 of 12 checked, 4 verified (3 claimed, unverified)
±0 pts since Nov 21
Merges per week
0 merges
target ≥ 3 merges
±0 merges since Oct 23
GitLab pipeline success ratio
100%
target ≥ 95%
±0 pts since Oct 28

Source: .loom/climb.yaml · as of 2026-11-21

Ropes

What must hold while climbing

  • Scope guards (what edilint is not)

    • Not an implementation-guide validator. SNIP Types 2–7 belong to pyx12 and commercial validators; the README says so and links them. Scope is SNIP Type 1 subset plus the hygiene layer SNIP doesn't name.
    • No licensed spec content. Envelope structure, control segments, and character sets are public knowledge; IG loop/segment tables are licensed X12 content and stay out. Same boundary for NCPDP (licensed) — flat-file *structure* checks only, if ever.
    • No network calls, no telemetry, no accounts. A linter that phones home is dead on arrival in healthcare shops.

    ROADMAP.md#scope-guards-what-edilint-is-not

  • Standing constraints (every agent, every workstream)

    • No proprietary material of any kind. All fixtures are synthetic and fictional.
    • Go, stdlib-first; new dependencies need a written justification in the MR/PR.
    • Plain factual prose in all docs — no marketing adjectives, no AI-tooling jargon.
    • American English spelling everywhere: code, comments, docs, and commit messages (behavior, catalog, normalize, analyze).
    • Every check has: a stable rule ID, table-driven tests (pass + fail fixtures), one-line rationale in the rule reference, and a documented false-positive story.
    • Repo conventions (layout, CI, commit format) are whatever v0.1 establishes; read before writing.

    ROADMAP.md#standing-constraints-every-agent-every-workstream

  • Definition of "legitimately useful" (v1.0 exit criteria)

    • Install to first useful finding in under two minutes on a stranger's machine
    • Passes its own dogfood: fi-fhir CI runs edilint on its X12 fixtures
    • Listed on awesome-edi; announced once on r/edi and the HL7/interop communities — factual post, no launch theater
    • One documented case (even a friend's shop) of a defect caught pre-send
    • Zero telemetry, zero network, zero accounts — verifiable by reading main()

    ROADMAP.md#definition-of-legitimately-useful-v10-exit-criteria

Read from the roadmap and spec · as of 2026-11-21

Altitude

Summit metrics as progress toward their targets: the top line is the target met, and the legend turns each metric’s line on or off. Every merge is a tick on the time axis, coloured by how it was joined to the route; inferred joins are dashed because they are a similarity match, not a key. When merges are too dense to tell apart they become one bar per day, split the same way, and a bar opens that day’s merges. Focus or hover a tick or bar for detail; the arrow keys move along the walk. Shaded bands are weather (main red, outages, breaker and storm holds) merged into episodes; review holds, the queue waiting on a person, run as the thin lane along the top. An inverted red marker stands on a merge that was later reverted (a false summit); flags are release tags. Lines and merges co-move here; nothing on this chart claims one caused the other.

Main red, Nov 7 03:08 – Nov 11 21:41 UTC, 114.5 h, edilint: main pipeline red.Base camp v0.5.0, 2026-11-01, tagged at a2d7c646b4d8.Base camp v0.6.0, 2026-11-04, tagged at be922860772e.
targetroadmap textunplannedMain redreview holds (top lane)base camp (tag)

Weather, false summits and base camps: tab to the first mark or hover one for its detail; the arrow keys move between marks.

2026-11-11MR !48join: unplannedoperator lane

fix(deps): build and release on Go 1.26.11 for GO-2026-6859

Served no written waypoint (off route: owner merge). Cost not recorded.

Commit d6394b794d62 on GitHub →

Weather

1 episode, about 114.5 hours held in the window (overlaps counted once).

  • Main red114.5 h1 episode

Episodes, longest first

  • Main red Nov 7 03:08 – Nov 11 21:41 UTC · 114.5 h · edilint's condition main pipeline red

Review holds are not counted as weather: 1 hold, about 0.8 hours, waited on a person and are drawn as the thin lane along the top of the chart.

Route as written and walked

The waypoints the roadmap lists, in written order, against the merges that served them. A waypoint walked before one written ahead of it is a slip; one with no merge in the window is dimmed.

13 written, 5 served, 8 off route

WrittenWalkedUnplannedwritten ordermerge time12345678910111213Oct 23Oct 29Nov 4Nov 10Nov 16

13 written, 5 served, 8 off route: 13 written waypoints, 5 with a step in the window, 8 steps that served one and 8 off the written route. 4 waypoints were walked out of written order and 8 have no step in the window. The written rail is in the order the roadmap lists its waypoints, not on the time axis; the walked rail is.

Route as written

Now 12 waypoints

  1. 1.

    Move `.github/workflows/ci.yml`, `.github/workflows/release.yml` and

    Now · planned · no step in this window · ROADMAP.md:284 @ d6394b79

  2. 2.

    Make `fix`'s BOM strip idempotent

    Now · done · walked out of written order · ROADMAP.md:300 @ d6394b79

    • MR !342026-11-01join: roadmap text
  3. 3.

    Cut `v0.5.0`

    Now · unverified · no step in this window · ROADMAP.md:311 @ d6394b79

  4. 4.

    Bump fi-fhir's pins

    Now · unverified · no step in this window · ROADMAP.md:323 @ d6394b79

  5. 5.

    Generate fi-fhir's EDI fixtures with `edilint gen 837p` and `gen 835

    Now · planned · no step in this window · ROADMAP.md:330 @ d6394b79

  6. 6.

    Document every install channel in `README.md`

    Now · done · walked out of written order · ROADMAP.md:339 @ d6394b79

    • MR !412026-11-03join: roadmap text
  7. 7.

    Add `TestREADMETranscriptsMatch` to `cmd/edilint/main_test.go` and delete

    Now · done · walked out of written order · ROADMAP.md:350 @ d6394b79

    • MR !392026-11-03join: roadmap text
  8. 8.

    Composite GitHub Action as a root `action.yml` with a smoke workflow

    Now · done · walked out of written order · ROADMAP.md:364 @ d6394b79

    • MR !422026-11-04join: roadmap text
  9. 9.

    Cut `v0.6.0`

    Now · unverified · no step in this window · ROADMAP.md:378 @ d6394b79

  10. 10.

    Derive the Action's default `version` from its own ref in

    Now · planned · no step in this window · ROADMAP.md:391 @ d6394b79

  11. 11.

    v1.0 exit evidence

    Now · planned · no step in this window · ROADMAP.md:403 @ d6394b79

  12. 12.

    Merge-train main dedup

    Now · planned · no step in this window · ROADMAP.md:407 @ d6394b79

Issues, specs and other waypoints 1 waypoint

  1. 13.

    Current Status

    walking · ROADMAP.md:11 @ d6394b79

    • MR !312026-10-27join: roadmap text
    • MR !322026-10-31join: roadmap text
    • MR !372026-11-01join: roadmap text
    • MR !382026-11-03join: roadmap text

Off the written route

8 steps: 8 owner merges.

  • MR !482026-11-11owner mergesfix(deps): build and release on Go 1.26.11 for GO-2026-6859
  • MR !472026-11-07owner mergesdocs(climb): declare tier 1 in .loom/climb.yaml
  • MR !462026-11-05owner mergesdocs(loom): declare the Mills climb in .loom/climb.yaml
  • MR !442026-11-04owner mergesci(action): build from source in action-smoke; prove the released tag only on tag pushes
  • MR !432026-11-04owner mergeschore(release): prepare v0.6.0
  • MR !402026-11-03owner mergesdocs(roadmap): 2026-11-03 Mills push — rows posted, first train row, carder-shaped Now lines
  • MR !362026-11-01owner mergeschore(release): prepare v0.5.0
  • MR !332026-11-01owner mergesdocs(roadmap): 2026-10-31 status — v0.5.0 blockers, Fix BOM idempotence defect, Mills intake posture

Legs

One chapter per day, narrated from the day’s merges, roadmap changes, metric readings and weather. Every sentence carries its evidence: a chip opens the merge, the roadmap line as written, the metric point or the weather band it rests on, and a sentence whose evidence could not be published is left out and counted. A day narrated again says “revised” and keeps its earlier versions; a day the model could not narrate within the rules is written from a fixed template and marked as one.

17 chapters, newest first. Arrow keys move between chapters; Tab moves through a chapter’s citations.

  1. Leg for traversetemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-20

    • Merges per week 0 merges → 0 merges −2 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 100% → 100% +50 pts rising over 7 days, toward target

    Co-moved: On 2026-11-20, 0 changes merged and no summit metric moved.

  2. Leg for descendingtemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-19

    Slipped
    Merges per week · Nov 19: Summit metric “Merges per week” on 2026-11-19: 0 merges. Jumps to the altitude chart.
    • Merges per week 1 merges → 0 merges −2 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 100% → 100% +50 pts rising over 7 days, toward target

    Co-moved: On 2026-11-19, 0 changes merged while Merges per week fell from 1 to 0 (away from its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

  3. Leg for traversetemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-18

    • Merges per week 1 merges → 1 merges −2 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 100% → 100% +33.3 pts rising over 7 days, toward target

    Co-moved: On 2026-11-18, 0 changes merged and no summit metric moved.

  4. Leg for traversetemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-17

    • Merges per week 1 merges → 1 merges −4 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 100% → 100% +20 pts rising over 7 days, toward target

    Co-moved: On 2026-11-17, 0 changes merged and no summit metric moved.

  5. Leg for traversetemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-16

    • Merges per week 1 merges → 1 merges −8 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 100% → 100% +11.1 pts rising over 7 days, toward target

    Co-moved: On 2026-11-16, 0 changes merged and no summit metric moved.

  6. Leg for ascendingtemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-15

    Moved
    GitLab pipeline success ratio · Nov 15: Summit metric “GitLab pipeline success ratio” on 2026-11-15: 100%. Jumps to the altitude chart.
    Slipped
    Merges per week · Nov 15: Summit metric “Merges per week” on 2026-11-15: 1 merges. Jumps to the altitude chart.
    • Merges per week 2 merges → 1 merges −8 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 50% → 100% +11.1 pts rising over 7 days, toward target

    Co-moved: On 2026-11-15, 0 changes merged while Merges per week fell from 2 to 1 (away from its target) and GitLab pipeline success ratio rose from 0.5 to 1 (toward its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

  7. Leg for traversetemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-14

    • Merges per week 2 merges → 2 merges −11 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 50% → 50% −41.7 pts falling over 7 days, away from target

    Co-moved: On 2026-11-14, 0 changes merged and no summit metric moved.

  8. Leg for descendingtemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-13

    Slipped
    Merges per week · Nov 13: Summit metric “Merges per week” on 2026-11-13: 2 merges. Jumps to the altitude chart.GitLab pipeline success ratio · Nov 13: Summit metric “GitLab pipeline success ratio” on 2026-11-13: 50%. Jumps to the altitude chart.
    • Merges per week 3 merges → 2 merges −11 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 66.7% → 50% −50 pts falling over 7 days, away from target

    Co-moved: On 2026-11-13, 0 changes merged while Merges per week fell from 3 to 2 (away from its target) and GitLab pipeline success ratio fell from 0.6667 to 0.5 (away from its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

  9. Leg for descendingtemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-12

    Slipped
    Merges per week · Nov 12: Summit metric “Merges per week” on 2026-11-12: 3 merges. Jumps to the altitude chart.GitLab pipeline success ratio · Nov 12: Summit metric “GitLab pipeline success ratio” on 2026-11-12: 66.7%. Jumps to the altitude chart.
    • Merges per week 5 merges → 3 merges −10 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 80% → 66.7% −33.3 pts falling over 7 days, away from target

    Co-moved: On 2026-11-12, 0 changes merged while Merges per week fell from 5 to 3 (away from its target) and GitLab pipeline success ratio fell from 0.8 to 0.6667 (away from its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

  10. Leg for descending

    Unplanned Go dependency fix merged while pipeline success ratio fell to 0.8.

    Slipped
    Merges per week · Nov 11: Summit metric “Merges per week” on 2026-11-11: 5 merges. Jumps to the altitude chart.GitLab pipeline success ratio · Nov 11: Summit metric “GitLab pipeline success ratio” on 2026-11-11: 80%. Jumps to the altitude chart.
    • Merges per week 9 merges → 5 merges −7 merges falling over 7 days, away from target
    • GitLab pipeline success ratio 88.9% → 80% −20 pts falling over 7 days, away from target

    Co-moved: On 2026-11-11, 1 change merged while Merges per week fell from 9 to 5 (away from its target) and GitLab pipeline success ratio fell from 0.8889 to 0.8 (away from its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

    Narrated by qwen38-27b-autoround-workhorse.

  11. Leg for weathered

    The climb on libs/edilint stalled under a red main pipeline with no merges.

    • Merges per week 9 merges → 9 merges ±0 merges flat over 7 days
    • GitLab pipeline success ratio 88.9% → 88.9% −11.1 pts falling over 7 days, away from target

    Co-moved: On 2026-11-10, 0 changes merged and no summit metric moved.

    Narrated by qwen38-27b-autoround-workhorse.

  12. Leg for weathered

    libs/edilint weathered the climb with zero merges and red pipelines.

    Slipped
    Merges per week · Nov 9: Summit metric “Merges per week” on 2026-11-09: 9 merges. Jumps to the altitude chart.GitLab pipeline success ratio · Nov 9: Summit metric “GitLab pipeline success ratio” on 2026-11-09: 88.9%. Jumps to the altitude chart.
    • Merges per week 13 merges → 9 merges +3 merges rising over 7 days, toward target
    • GitLab pipeline success ratio 91.7% → 88.9% −11.1 pts falling over 7 days, away from target

    Co-moved: On 2026-11-09, 0 changes merged while Merges per week fell from 13 to 9 (away from its target) and GitLab pipeline success ratio fell from 0.9167 to 0.8889 (away from its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

    Narrated by qwen38-27b-autoround-workhorse.

  13. Leg for descending

    Pipeline success ratio fell to 0.9167 while the main pipeline remained red all day.

    Slipped
    GitLab pipeline success ratio · Nov 8: Summit metric “GitLab pipeline success ratio” on 2026-11-08: 91.7%. Jumps to the altitude chart.
    • Merges per week 13 merges → 13 merges +7 merges rising over 7 days, toward target
    • GitLab pipeline success ratio 100% → 91.7% −8.3 pts falling over 7 days, away from target

    Co-moved: On 2026-11-08, 0 changes merged while GitLab pipeline success ratio fell from 1 to 0.9167 (away from its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

    Narrated by qwen38-27b-autoround-workhorse.

  14. Leg for weathered

    One unplanned documentation change merged while the main pipeline remained red.

    • Merges per week 13 merges → 13 merges +11 merges rising over 7 days, toward target
    • GitLab pipeline success ratio 100% → 100% ±0 pts flat over 7 days

    Co-moved: On 2026-11-07, 1 change merged and no summit metric moved.

    Narrated by qwen38-27b-autoround-workhorse.

  15. Leg for ascendingtemplate: written from the deterministic template, not by the model

    No changes merged on 2026-11-06

    Moved
    Merges per week · Nov 6: Summit metric “Merges per week” on 2026-11-06: 13 merges. Jumps to the altitude chart.
    • Merges per week 12 merges → 13 merges +12 merges rising over 7 days, toward target
    • Roadmap gates met (Now list) 33.3% → 33.3% +33.3 pts rising over 7 days, toward target
    • GitLab pipeline success ratio 100% → 100% ±0 pts flat over 7 days

    Co-moved: On 2026-11-06, 0 changes merged while Merges per week rose from 12 to 13 (toward its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

  16. Leg for ascending

    Unplanned documentation merge coincided with rising cadence and gates metrics.

    Moved
    Merges per week · Nov 5: Summit metric “Merges per week” on 2026-11-05: 12 merges. Jumps to the altitude chart.Roadmap gates met (Now list) · Nov 5: Summit metric “Roadmap gates met (Now list)” on 2026-11-05: no sample that day in the public series. Jumps to the altitude chart.
    • Merges per week 9 merges → 12 merges +11 merges rising over 7 days, toward target
    • Roadmap gates met (Now list) 25% → 33.3% +33.3 pts rising over 7 days, toward target
    • GitLab pipeline success ratio 100% → 100% ±0 pts flat over 7 days

    Co-moved: On 2026-11-05, 1 change merged while Merges per week rose from 9 to 12 (toward its target) and Roadmap gates met (Now list) rose from 0.25 to 0.3333 (toward its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

    Narrated by qwen38-27b-xtx-warm-canary.

  17. Leg for ascending

    libs/edilint merged 3 changes, serving a roadmap waypoint and raising cadence and gates metrics.

    Moved
    ROADMAP.md:364: Roadmap waypoint “Composite GitHub Action as a root `action.yml` with a smoke workflow” (Now), done. Opens the line as written, at the commit it was read from.Merges per week · Nov 4: Summit metric “Merges per week” on 2026-11-04: 9 merges. Jumps to the altitude chart.Roadmap gates met (Now list) · Nov 4: Summit metric “Roadmap gates met (Now list)” on 2026-11-04: no sample that day in the public series. Jumps to the altitude chart.
    • Merges per week 6 merges → 9 merges +8 merges rising over 7 days, toward target
    • Roadmap gates met (Now list) 8.3% → 25% +25 pts rising over 7 days, toward target
    • GitLab pipeline success ratio 100% → 100% ±0 pts flat over 7 days

    Co-moved: On 2026-11-04, 3 changes merged while Merges per week rose from 6 to 9 (toward its target) and Roadmap gates met (Now list) rose from 0.0833 to 0.25 (toward its target). This is co-movement on the same day only; the record does not show that any change moved a metric.

    Narrated by qwen38-27b-xtx-warm-canary.

Where this comes from

Live from the operatorgenerated 2026-11-21 11:25 UTC ()

Read from the Mills operator within the last ten minutes. Sanitized from the Mills chronicle read model: run, backlog and roadmap ids are hashed; titles, headlines and narrated sentences are scrubbed of paths, URLs, credentials, addresses and unpublished repository names; only climbs on published repositories are listed. Merge request numbers and short commit hashes are kept because they are public; so is the name of the model that narrated each leg, while its backend, prompts and traces are not. Merge request numbers are shown as text because the GitLab they live on needs a sign-in.