{"$schema":"https://json.schemastore.org/sarif-2.1.0.json","version":"2.1.0","runs":[{"tool":{"driver":{"name":"codehealth","informationUri":"https://codehealth.canine.dev","rules":[{"id":"D3","name":"God Classes","shortDescription":{"text":"God Classes"},"helpUri":"https://codehealth.canine.dev/dimensions/D3"},{"id":"D4","name":"Code Duplication","shortDescription":{"text":"Code Duplication"},"helpUri":"https://codehealth.canine.dev/dimensions/D4"},{"id":"D5","name":"Coupling","shortDescription":{"text":"Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D5"},{"id":"D13","name":"Secret Scanning","shortDescription":{"text":"Secret Scanning"},"helpUri":"https://codehealth.canine.dev/dimensions/D13","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A07:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"],"owasp":"A07:2025"}},{"id":"D20","name":"ADR Quality","shortDescription":{"text":"ADR Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D20"},{"id":"D26","name":"Project Cohesion","shortDescription":{"text":"Project Cohesion"},"helpUri":"https://codehealth.canine.dev/dimensions/D26"},{"id":"D28","name":"Secrets (history)","shortDescription":{"text":"Secrets (history)"},"helpUri":"https://codehealth.canine.dev/dimensions/D28","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A07:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"],"owasp":"A07:2025"}},{"id":"D29","name":"Static Analysis (SAST)","shortDescription":{"text":"Static Analysis (SAST)"},"helpUri":"https://codehealth.canine.dev/dimensions/D29","relationships":[{"target":{"id":"CWE-79","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-89","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-78","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-94","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-77","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A05:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-79","CWE-89","CWE-78","CWE-94","CWE-77"],"owasp":"A05:2025"}},{"id":"D34","name":"Knowledge Freshness","shortDescription":{"text":"Knowledge Freshness"},"helpUri":"https://codehealth.canine.dev/dimensions/D34"},{"id":"D35","name":"Change Coupling","shortDescription":{"text":"Change Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D35"},{"id":"D44","name":"Platform End-of-Life","shortDescription":{"text":"Platform End-of-Life"},"helpUri":"https://codehealth.canine.dev/dimensions/D44"},{"id":"AX10","name":"Code composition","shortDescription":{"text":"Code composition"},"helpUri":"https://codehealth.canine.dev/dimensions/AX10"},{"id":"AX3","name":"Project dependency cycles","shortDescription":{"text":"Project dependency cycles"},"helpUri":"https://codehealth.canine.dev/dimensions/AX3"},{"id":"AX4","name":"Dependency direction","shortDescription":{"text":"Dependency direction"},"helpUri":"https://codehealth.canine.dev/dimensions/AX4"},{"id":"AX5","name":"Architecture \u0026 structure","shortDescription":{"text":"Architecture \u0026 structure"},"helpUri":"https://codehealth.canine.dev/dimensions/AX5"},{"id":"AXB1","name":"Runtime evidence locked \u2014 no reproducible boot","shortDescription":{"text":"Runtime evidence locked \u2014 no reproducible boot"},"helpUri":"https://codehealth.canine.dev/dimensions/AXB1"},{"id":"DM12","name":"Ambient inputs in the domain","shortDescription":{"text":"Ambient inputs in the domain"},"helpUri":"https://codehealth.canine.dev/dimensions/DM12"},{"id":"DM6","name":"Domain \u2194 infrastructure boundary","shortDescription":{"text":"Domain \u2194 infrastructure boundary"},"helpUri":"https://codehealth.canine.dev/dimensions/DM6"},{"id":"ED5","name":"Idempotency","shortDescription":{"text":"Idempotency"},"helpUri":"https://codehealth.canine.dev/dimensions/ED5"},{"id":"GD1","name":"Unfinished \u0026 placeholder code","shortDescription":{"text":"Unfinished \u0026 placeholder code"},"helpUri":"https://codehealth.canine.dev/dimensions/GD1"},{"id":"M1","name":"Documentation (README)","shortDescription":{"text":"Documentation (README)"},"helpUri":"https://codehealth.canine.dev/dimensions/M1"},{"id":"M2","name":"Architecture documentation","shortDescription":{"text":"Architecture documentation"},"helpUri":"https://codehealth.canine.dev/dimensions/M2"},{"id":"M3","name":"Folder \u0026 project structure","shortDescription":{"text":"Folder \u0026 project structure"},"helpUri":"https://codehealth.canine.dev/dimensions/M3"},{"id":"P1","name":"CI/CD gates","shortDescription":{"text":"CI/CD gates"},"helpUri":"https://codehealth.canine.dev/dimensions/P1"},{"id":"P2","name":"Observability","shortDescription":{"text":"Observability"},"helpUri":"https://codehealth.canine.dev/dimensions/P2"},{"id":"P3","name":"Security \u0026 performance tooling","shortDescription":{"text":"Security \u0026 performance tooling"},"helpUri":"https://codehealth.canine.dev/dimensions/P3"},{"id":"P6","name":"Release Hygiene","shortDescription":{"text":"Release Hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/P6"},{"id":"PF3","name":"Async \u0026 latency hygiene","shortDescription":{"text":"Async \u0026 latency hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/PF3"},{"id":"X10","name":"Duplicated predicate","shortDescription":{"text":"Duplicated predicate"},"helpUri":"https://codehealth.canine.dev/dimensions/X10"},{"id":"X20","name":"Mistyped argument guard","shortDescription":{"text":"Mistyped argument guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X20"},{"id":"X23","name":"Unguarded diagnostic materialisation","shortDescription":{"text":"Unguarded diagnostic materialisation"},"helpUri":"https://codehealth.canine.dev/dimensions/X23"},{"id":"X27","name":"Collection changed while being enumerated","shortDescription":{"text":"Collection changed while being enumerated"},"helpUri":"https://codehealth.canine.dev/dimensions/X27"},{"id":"X28","name":"Index access outside its own emptiness guard","shortDescription":{"text":"Index access outside its own emptiness guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X28"},{"id":"X9","name":"Subsumed condition operand","shortDescription":{"text":"Subsumed condition operand"},"helpUri":"https://codehealth.canine.dev/dimensions/X9"}]}},"results":[{"ruleId":"D4","level":"warning","message":{"text":"Near-duplicate member family (5 members, 65 shared lines): EventSourced/Domain.fs:1-159 | Videos/Step6/Domain6.fs:1-97 | Videos/Step7/Domain7.fs:1-116 | Videos/Step8/Domain8.fs:1-116 | Videos/Step9/Domain9.fs:1-116 \u2014 These 5 members are variants of one another: a block of 65 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members\u0027 grain \u2014 factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Domain.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"9adf6b294a433bf3afbe88117d6c0470438e71deb331efdf635affb468c3d4dc"}},{"ruleId":"D4","level":"warning","message":{"text":"Near-duplicate member family (5 members, 37 shared lines): Talk/Step3/Domain3.fs:1-85 | Talk/Step4/Domain4.fs:1-87 | Videos/Step3.fs:1-224 | Videos/Step4.fs:1-282 | Videos/Step5.fs:1-313 \u2014 These 5 members are variants of one another: a block of 37 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members\u0027 grain \u2014 factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step3/Domain3.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"c96b4b16235bb0b8c98fffb42679d4468940fe3afc00f45da60e58309163a77c"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (5 members, 50\u002B identical tokens): Talk/Step2/Tests2.fs:1-51 | Talk/Step3/Tests3.fs:1-51 | Talk/Step4/Tests4.fs:1-51 | Videos/Step4.fs:1-282 | Videos/Step5.fs:1-313 \u2014 These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below \u2014 it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members\u0027 grain \u2014 factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Tests2.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"27556fd68e9e86660b73017607207688bbce63c3c00381f5dcc074901d0adecc"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Talk/Step1/Program1.fs:1-67 | Talk/Step2/Program2.fs:1-83 | Talk/Step3/Program3.fs:1-82 | Talk/Step4/Program4.fs:1-120 \u2014 These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below \u2014 it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members\u0027 grain \u2014 factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step1/Program1.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"957ad914970de9e31cb59a766071b396d1ec3e7cb4dcc62431099f72cb719c42"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Videos/Step6/Application6.fs:1-136 | Videos/Step7/Application7.fs:1-136 | Videos/Step8/Application8.fs:1-104 | Videos/Step9/Application9.fs:1-135 \u2014 These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below \u2014 it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members\u0027 grain \u2014 factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Application6.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"bfcb464f030168dbcc9cc7485ad34b5eb20105d07eec3d491e3daeda886946b9"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Videos/Step6/Infrastructure6.fs:1-209 | Videos/Step7/Infrastructure7.fs:1-215 | Videos/Step8/Infrastructure8.fs:1-327 | Videos/Step9/Infrastructure9.fs:1-386 \u2014 These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below \u2014 it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members\u0027 grain \u2014 factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Infrastructure6.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"8bbac2017f3b824d4d8802b76c238fc90fd24ea543eb199347bf1ba8e125d4cc"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Videos/Step6/Tests6.fs:1-86 | Videos/Step7/Tests7.fs:1-86 | Videos/Step8/Tests8.fs:1-86 | Videos/Step9/Tests9.fs:1-86 \u2014 These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below \u2014 it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members\u0027 grain \u2014 factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Tests6.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"51504a629660114bdfad104e39a03f1c48f6d20639fbd6782130135835a62156"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (87\u201388 lines \u00D7 3): Videos/Step6/Application6.fs:50-136 | Videos/Step7/Application7.fs:50-136 | Videos/Step8/Application8.fs:17-104 \u2014 before extracting anything, compare \u0060Videos/Step6/Application6.fs\u0060 and \u0060Videos/Step7/Application7.fs\u0060 as WHOLE FILES: 94% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Application6.fs"},"region":{"startLine":50}}}],"partialFingerprints":{"codehealthFindingId/v1":"eee01711796bdbd2a5b040ce00c0e8cbe9eceb3fc35bc2f8cf81738d6164ae79"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (82 lines \u00D7 4): Videos/Step6/Tests6.fs:5-86 | Videos/Step7/Tests7.fs:5-86 | Videos/Step8/Tests8.fs:5-86 | Videos/Step9/Tests9.fs:5-86 \u2014 before extracting anything, compare \u0060Videos/Step6/Tests6.fs\u0060 and \u0060Videos/Step7/Tests7.fs\u0060 as WHOLE FILES: 94% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Tests6.fs"},"region":{"startLine":5}}}],"partialFingerprints":{"codehealthFindingId/v1":"d147ce137a8f5167993861cdb50b2969ac6fad19cafe6d595424bfe4e8d8e9e3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (75 lines \u00D7 2): Talk/Step2/Program2.fs:9-83 | Talk/Step3/Program3.fs:8-82 \u2014 before extracting anything, compare \u0060Talk/Step2/Program2.fs\u0060 and \u0060Talk/Step3/Program3.fs\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Program2.fs"},"region":{"startLine":9}}}],"partialFingerprints":{"codehealthFindingId/v1":"e2de5fbb04f080d6b5b80cb1426135f84ce32fa151f7d185248a823014b8ac33"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (74 lines \u00D7 2): Talk/Step4/Infrastructure4.fs:26-99 | Videos/Step5.fs:17-90 \u2014 before extracting anything, compare \u0060Talk/Step4/Infrastructure4.fs\u0060 and \u0060Videos/Step5.fs\u0060 as WHOLE FILES: 97% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step4/Infrastructure4.fs:26\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step4/Infrastructure4.fs"},"region":{"startLine":26}}}],"partialFingerprints":{"codehealthFindingId/v1":"c11eb177f175f478b62cef27245099ad80f6b91445f9f3f7c68fd8d31f21daa3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (68 lines \u00D7 2): Videos/Step7/Infrastructure7.fs:107-174 | Videos/Step8/Infrastructure8.fs:219-286 \u2014 before extracting anything, compare \u0060Videos/Step7/Infrastructure7.fs\u0060 and \u0060Videos/Step8/Infrastructure8.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Videos/Step7/Infrastructure7.fs:107\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step7/Infrastructure7.fs"},"region":{"startLine":107}}}],"partialFingerprints":{"codehealthFindingId/v1":"4817a2ca744bec10b1283bd6de31228263a39901666cd65d1eb16afd36a113be"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (48\u201359 lines \u00D7 3): Videos/Step3.fs:55-102 | Videos/Step4.fs:55-113 | Videos/Step5.fs:89-137 \u2014 before extracting anything, compare \u0060Videos/Step3.fs\u0060 and \u0060Videos/Step4.fs\u0060 as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Videos/Step3.fs:55\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members\u0027 bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step3.fs"},"region":{"startLine":55}}}],"partialFingerprints":{"codehealthFindingId/v1":"9464a69497990d5e30d26a46d45ace76031dfa5b9f380eee66dbbae2433d815b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (52 lines \u00D7 5): EventSourced/Domain.fs:47-98 | Videos/Step6/Domain6.fs:21-72 | Videos/Step7/Domain7.fs:27-78 | Videos/Step8/Domain8.fs:27-78 | Videos/Step9/Domain9.fs:27-78 \u2014 before extracting anything, compare \u0060EventSourced/Domain.fs\u0060 and \u0060Videos/Step6/Domain6.fs\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Domain.fs"},"region":{"startLine":47}}}],"partialFingerprints":{"codehealthFindingId/v1":"40a0369d9df72ed69b896c4c798929eb03e46999cd46967a3d0dbebe0ac2b016"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (46\u201347 lines \u00D7 2): Videos/Step1.fs:13-58 | Videos/Step2.fs:9-55 \u2014 before extracting anything, compare \u0060Videos/Step1.fs\u0060 and \u0060Videos/Step2.fs\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step1.fs"},"region":{"startLine":13}}}],"partialFingerprints":{"codehealthFindingId/v1":"10098e032c8aa33f914b610f46cdb12d0395f909659a6e2dffbb2b0603d40728"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (46 lines \u00D7 3): Videos/Step6/Infrastructure6.fs:164-209 | Videos/Step7/Infrastructure7.fs:170-215 | Videos/Step8/Infrastructure8.fs:282-327 \u2014 before extracting anything, compare \u0060Videos/Step6/Infrastructure6.fs\u0060 and \u0060Videos/Step7/Infrastructure7.fs\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Infrastructure6.fs"},"region":{"startLine":164}}}],"partialFingerprints":{"codehealthFindingId/v1":"2ae48df49cfb6a7c2c65c3493e85ab57ce2dce6e81acb785f9ec20727a1021ca"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (41\u201343 lines \u00D7 5): Talk/Step2/Tests2.fs:9-49 | Talk/Step3/Tests3.fs:9-49 | Talk/Step4/Tests4.fs:9-49 | Videos/Step4.fs:168-210 | Videos/Step5.fs:195-237 \u2014 before extracting anything, compare \u0060Talk/Step2/Tests2.fs\u0060 and \u0060Talk/Step3/Tests3.fs\u0060 as WHOLE FILES: 94% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step2/Tests2.fs:9\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Tests2.fs"},"region":{"startLine":9}}}],"partialFingerprints":{"codehealthFindingId/v1":"edd56df707a274d842f82e1097ca67c25660a3cb9dd0ac9ff839fc1f01986bf0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (40 lines \u00D7 4): Talk/Step2/Infrastructure2.fs:28-67 | Talk/Step3/Infrastructure3.fs:29-68 | Videos/Step3.fs:16-55 | Videos/Step4.fs:16-55 \u2014 before extracting anything, compare \u0060Talk/Step2/Infrastructure2.fs\u0060 and \u0060Talk/Step3/Infrastructure3.fs\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step2/Infrastructure2.fs:28\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Infrastructure2.fs"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"ba1a24e72928bb7085b865eb46a2a8f43d47c3ec9c49255c3122b4a655e29f51"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (34 lines \u00D7 3): Videos/Step3.fs:119-152 | Videos/Step4.fs:127-160 | Videos/Step5.fs:154-187 \u2014 before extracting anything, compare \u0060Videos/Step3.fs\u0060 and \u0060Videos/Step4.fs\u0060 as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step3.fs"},"region":{"startLine":119}}}],"partialFingerprints":{"codehealthFindingId/v1":"33d762c32e10ba79cf707839f17ba313cb3a1f5e82324a5881a633eccb57a040"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (33 lines \u00D7 3): Talk/Step2/Domain2.fs:53-85 | Talk/Step3/Domain3.fs:53-85 | Talk/Step4/Domain4.fs:55-87 \u2014 before extracting anything, compare \u0060Talk/Step2/Domain2.fs\u0060 and \u0060Talk/Step3/Domain3.fs\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 155 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Domain2.fs"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"d5525af404eb40b28f471be196a708cc3486298c0bf774e708016fcd85299851"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (30 lines \u00D7 2): EventSourced/Infrastructure/Agent.fs:8-37 | Videos/Step9/Infrastructure9.fs:74-103 \u2014 before extracting anything, compare \u0060EventSourced/Infrastructure/Agent.fs\u0060 and \u0060Videos/Step9/Infrastructure9.fs\u0060 as WHOLE FILES: 96% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Infrastructure/Agent.fs"},"region":{"startLine":8}}}],"partialFingerprints":{"codehealthFindingId/v1":"19b1473abc3fd8cd8f92b7178c8796876b509b65897f06949c63976b50f0b6d5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (28\u201329 lines \u00D7 2): Talk/Step2/Domain2.fs:29-57 | Videos/Step3.fs:96-123 \u2014 before extracting anything, compare \u0060Talk/Step2/Domain2.fs\u0060 and \u0060Videos/Step3.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step2/Domain2.fs:29\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Domain2.fs"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"2d325bb353c184f18a1ccba489618dd2932e59985c5cdca09148ff803dd366d1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15\u201328 lines \u00D7 2): Videos/Step6/Infrastructure6.fs:111-138 | Videos/Step7/Infrastructure7.fs:96-110 \u2014 before extracting anything, compare \u0060Videos/Step6/Infrastructure6.fs\u0060 and \u0060Videos/Step7/Infrastructure7.fs\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Videos/Step6/Infrastructure6.fs:111\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members\u0027 bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Infrastructure6.fs"},"region":{"startLine":111}}}],"partialFingerprints":{"codehealthFindingId/v1":"8fbb390d8b027561cb56ac6d7989ed0e7fac652252b71961e1f6858d9c8cf4f2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (26 lines \u00D7 3): Talk/Step1/Infrastructure1.fs:28-53 | Videos/Step1.fs:19-44 | Videos/Step2.fs:16-41 \u2014 before extracting anything, compare \u0060Videos/Step1.fs\u0060 and \u0060Videos/Step2.fs\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step1/Infrastructure1.fs:28\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step1/Infrastructure1.fs"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"8d9a5f2fc8c0837186a6d8776834379d7395c8eb860bbcebafa17def703d3cf9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (24\u201326 lines \u00D7 2): Videos/Step6/Infrastructure6.fs:71-94 | Videos/Step7/Infrastructure7.fs:68-93 \u2014 before extracting anything, compare \u0060Videos/Step6/Infrastructure6.fs\u0060 and \u0060Videos/Step7/Infrastructure7.fs\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Videos/Step6/Infrastructure6.fs:71\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Infrastructure6.fs"},"region":{"startLine":71}}}],"partialFingerprints":{"codehealthFindingId/v1":"47ef161694ceae3859a973e704cbd4e430ea1106cc0268e73b3468a1fc810e4a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (24\u201325 lines \u00D7 4): Videos/Step2.fs:45-69 | Videos/Step3.fs:59-82 | Videos/Step4.fs:59-83 | Videos/Step5.fs:94-117 \u2014 before extracting anything, compare \u0060Videos/Step3.fs\u0060 and \u0060Videos/Step4.fs\u0060 as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step2.fs"},"region":{"startLine":45}}}],"partialFingerprints":{"codehealthFindingId/v1":"e8f7fe4483d20efc31a8f4f68ce9ab2a4e2c6a829b243a4166a611faa789e2fc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (22\u201324 lines \u00D7 2): Videos/Step3.fs:159-180 | Videos/Step4.fs:216-239 \u2014 before extracting anything, compare \u0060Videos/Step3.fs\u0060 and \u0060Videos/Step4.fs\u0060 as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together \u2014 extracting one helper per block leaves the fork in place. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Videos/Step4.fs:242\u0060 calls \u0060runTests\u0060 and \u0060Videos/Step3.fs:184\u0060 does not \u2014 after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step3.fs"},"region":{"startLine":159}}}],"partialFingerprints":{"codehealthFindingId/v1":"5b328f30931781ba56090c3cd7e9c4f02151245c09361bf0625ae45b912f4ad8"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (23 lines \u00D7 3): Videos/Step7/Domain7.fs:94-116 | Videos/Step8/Domain8.fs:94-116 | Videos/Step9/Domain9.fs:94-116 \u2014 before extracting anything, compare \u0060Videos/Step7/Domain7.fs\u0060 and \u0060Videos/Step8/Domain8.fs\u0060 as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 153 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step7/Domain7.fs"},"region":{"startLine":94}}}],"partialFingerprints":{"codehealthFindingId/v1":"30894d4d9c26c070d69778d1591e23f128d4c1ba3d2f2ec049d85613a01d372f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19\u201321 lines \u00D7 6): Talk/Step2/Domain2.fs:44-64 | Talk/Step3/Domain3.fs:45-64 | Talk/Step4/Domain4.fs:47-66 | Videos/Step3.fs:111-130 | Videos/Step4.fs:120-138 | Videos/Step5.fs:147-165 \u2014 before extracting anything, compare \u0060Talk/Step2/Domain2.fs\u0060 and \u0060Talk/Step3/Domain3.fs\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 155 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Domain2.fs"},"region":{"startLine":44}}}],"partialFingerprints":{"codehealthFindingId/v1":"665f6fa9049719b4372e2ac29b37bbb0fd0b4ea31e0da3d88bada5bd75191f2d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (21 lines \u00D7 3): Talk/Step2/Domain2.fs:18-38 | Talk/Step3/Domain3.fs:18-38 | Talk/Step4/Domain4.fs:20-40 \u2014 before extracting anything, compare \u0060Talk/Step2/Domain2.fs\u0060 and \u0060Talk/Step3/Domain3.fs\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 155 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Domain2.fs"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"bdbf2dfe9bf71179c5c6bc4d69a41152fb563a734b1b9ccd15777a56402fc467"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20 lines \u00D7 3): Videos/Step6/Infrastructure6.fs:3-22 | Videos/Step7/Infrastructure7.fs:3-22 | Videos/Step8/Infrastructure8.fs:3-22 \u2014 before extracting anything, compare \u0060Videos/Step6/Infrastructure6.fs\u0060 and \u0060Videos/Step7/Infrastructure7.fs\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Videos/Step6/Infrastructure6.fs:3\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Infrastructure6.fs"},"region":{"startLine":3}}}],"partialFingerprints":{"codehealthFindingId/v1":"6140d8162c6e22de052280f8b204c692c5211bb56a62ed66f71cfa06f94e4bbc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18\u201319 lines \u00D7 10): Talk/Step2/Domain2.fs:50-68 | Talk/Step3/Domain3.fs:50-68 | Talk/Step4/Domain4.fs:52-70 | Videos/Step3.fs:117-134 | Videos/Step4.fs:125-142 | Videos/Step5.fs:152-169 | Videos/Step6/Domain6.fs:59-76 | Videos/Step7/Domain7.fs:65-82 | Videos/Step8/Domain8.fs:65-82 | Videos/Step9/Domain9.fs:65-82 \u2014 before extracting anything, compare \u0060Talk/Step2/Domain2.fs\u0060 and \u0060Talk/Step3/Domain3.fs\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 155 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Domain2.fs"},"region":{"startLine":50}}}],"partialFingerprints":{"codehealthFindingId/v1":"edd53b8c9b8b3a8964c475adda6f6b38be3f58d42f4f1be6787cd43792538b7e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17\u201319 lines \u00D7 3): Videos/Step6/Infrastructure6.fs:28-46 | Videos/Step7/Infrastructure7.fs:27-43 | Videos/Step8/Infrastructure8.fs:34-50 \u2014 before extracting anything, compare \u0060Videos/Step6/Infrastructure6.fs\u0060 and \u0060Videos/Step7/Infrastructure7.fs\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Videos/Step6/Infrastructure6.fs:28\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Infrastructure6.fs"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"3ffaed57a25dfeb16bbe2aa7c62f510a5047d26b0f5cd013437a67385030f485"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 8): EventSourced/Domain.fs:64-80 | Talk/Step3/Domain3.fs:29-45 | Talk/Step4/Domain4.fs:31-47 | Videos/Step5.fs:131-147 | Videos/Step6/Domain6.fs:38-54 | Videos/Step7/Domain7.fs:44-60 | Videos/Step8/Domain8.fs:44-60 | Videos/Step9/Domain9.fs:44-60 \u2014 before extracting anything, compare \u0060EventSourced/Domain.fs\u0060 and \u0060Talk/Step3/Domain3.fs\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Domain.fs"},"region":{"startLine":64}}}],"partialFingerprints":{"codehealthFindingId/v1":"97d39cb41bdcf90a69937849bc7f148f163803e68ea3c482ee72f52612d0948f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 7): Talk/Step1/Infrastructure1.fs:25-40 | Talk/Step2/Infrastructure2.fs:30-45 | Talk/Step3/Infrastructure3.fs:31-46 | Videos/Step1.fs:16-31 | Videos/Step2.fs:13-28 | Videos/Step3.fs:18-33 | Videos/Step4.fs:18-33 \u2014 before extracting anything, compare \u0060Talk/Step1/Infrastructure1.fs\u0060 and \u0060Talk/Step2/Infrastructure2.fs\u0060 as WHOLE FILES: 90% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step1/Infrastructure1.fs:25\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Talk/Step2/Infrastructure2.fs:48\u0060 calls \u0060loop\u0060 and \u0060Talk/Step1/Infrastructure1.fs:41\u0060 does not \u2014 after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step1/Infrastructure1.fs"},"region":{"startLine":25}}}],"partialFingerprints":{"codehealthFindingId/v1":"e696345d7c8ea7f500bea847bfc37612df9ad5e9a17f74464c4dd60b74af16f6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13\u201316 lines \u00D7 6): Talk/Step2/Domain2.fs:72-84 | Talk/Step3/Domain3.fs:72-84 | Talk/Step4/Domain4.fs:74-86 | Videos/Step3.fs:137-152 | Videos/Step4.fs:145-160 | Videos/Step5.fs:172-187 \u2014 before extracting anything, compare \u0060Talk/Step2/Domain2.fs\u0060 and \u0060Talk/Step3/Domain3.fs\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 155 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Domain2.fs"},"region":{"startLine":72}}}],"partialFingerprints":{"codehealthFindingId/v1":"0a639204ac271fc2084e5867e34d6f26b35ba0f2de699bca6dcd854dccd307a9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 3): Talk/Step1/Program1.fs:36-51 | Talk/Step2/Program2.fs:49-64 | Talk/Step3/Program3.fs:48-63 \u2014 before extracting anything, compare \u0060Talk/Step2/Program2.fs\u0060 and \u0060Talk/Step3/Program3.fs\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step1/Program1.fs:36\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step1/Program1.fs"},"region":{"startLine":36}}}],"partialFingerprints":{"codehealthFindingId/v1":"737fda9331cc7bae2744863560d4db84e19be154e4d50efcff08c8d0954ae1ec"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 11): EventSourced/Domain.fs:85-99 | Talk/Step2/Domain2.fs:50-65 | Talk/Step3/Domain3.fs:50-65 | Talk/Step4/Domain4.fs:52-67 | Videos/Step3.fs:117-131 | Videos/Step4.fs:125-139 | Videos/Step5.fs:152-166 | Videos/Step6/Domain6.fs:59-73 | Videos/Step7/Domain7.fs:65-79 | Videos/Step8/Domain8.fs:65-79 | Videos/Step9/Domain9.fs:65-79 \u2014 before extracting anything, compare \u0060EventSourced/Domain.fs\u0060 and \u0060Talk/Step3/Domain3.fs\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Domain.fs"},"region":{"startLine":85}}}],"partialFingerprints":{"codehealthFindingId/v1":"5495ce065762f77fe81dcea34e734df77364225b2ad0367aca59090854b99c0b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14\u201315 lines \u00D7 5): Talk/Step1/Domain1.fs:18-32 | Talk/Step2/Domain2.fs:22-35 | Talk/Step3/Domain3.fs:22-35 | Talk/Step4/Domain4.fs:24-37 | Videos/Step2.fs:72-85 \u2014 before extracting anything, compare \u0060Talk/Step1/Domain1.fs\u0060 and \u0060Talk/Step2/Domain2.fs\u0060 as WHOLE FILES: 91% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step1/Domain1.fs:18\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step1/Domain1.fs"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"c76ba3b091948a6458cca626f4718f269a4ec4793effbf1c07231ea32018843f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 3): Videos/Step7/Infrastructure7.fs:130-144 | Videos/Step8/Infrastructure8.fs:242-256 | Videos/Step9/Infrastructure9.fs:328-342 \u2014 before extracting anything, compare \u0060Videos/Step7/Infrastructure7.fs\u0060 and \u0060Videos/Step8/Infrastructure8.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step7/Infrastructure7.fs"},"region":{"startLine":130}}}],"partialFingerprints":{"codehealthFindingId/v1":"47c49902f0c4679184dddec8b3d51ab997caa92d0e831bb1fc618ff0f7ef19ea"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): EventSourced/Infrastructure/QueryHandler.fs:5-19 | Videos/Step9/Infrastructure9.fs:368-382 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Infrastructure/QueryHandler.fs"},"region":{"startLine":5}}}],"partialFingerprints":{"codehealthFindingId/v1":"6441ce7c336483e6aff9372c00700d8389332b49398c2c075b40ef1cff752d8a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 10): EventSourced/Domain.fs:62-75 | Talk/Step2/Domain2.fs:27-40 | Talk/Step3/Domain3.fs:27-40 | Talk/Step4/Domain4.fs:29-42 | Videos/Step3.fs:94-107 | Videos/Step5.fs:129-142 | Videos/Step6/Domain6.fs:36-49 | Videos/Step7/Domain7.fs:42-55 | Videos/Step8/Domain8.fs:42-55 | Videos/Step9/Domain9.fs:42-55 \u2014 before extracting anything, compare \u0060EventSourced/Domain.fs\u0060 and \u0060Talk/Step3/Domain3.fs\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Domain.fs"},"region":{"startLine":62}}}],"partialFingerprints":{"codehealthFindingId/v1":"76c4d66136eadfe22f1c55335358a36576e83b3f499d9206f703b4d700a4cd8b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13\u201314 lines \u00D7 4): Videos/Step6/Application6.fs:58-71 | Videos/Step7/Application7.fs:58-71 | Videos/Step8/Application8.fs:26-39 | Videos/Step9/Application9.fs:26-38 \u2014 before extracting anything, compare \u0060Videos/Step6/Application6.fs\u0060 and \u0060Videos/Step7/Application7.fs\u0060 as WHOLE FILES: 94% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Videos/Step6/Application6.fs:58\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Application6.fs"},"region":{"startLine":58}}}],"partialFingerprints":{"codehealthFindingId/v1":"d43cccf235b7148937781e108254922b7d36c8a0c540fd96a1cd963139169d41"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Videos/Step8/Infrastructure8.fs:96-109 | Videos/Step9/Infrastructure9.fs:176-189 \u2014 before extracting anything, compare \u0060Videos/Step8/Infrastructure8.fs\u0060 and \u0060Videos/Step9/Infrastructure9.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Videos/Step8/Infrastructure8.fs:96\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members\u0027 bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step8/Infrastructure8.fs"},"region":{"startLine":96}}}],"partialFingerprints":{"codehealthFindingId/v1":"f27bcab0ab355dc13fc339aa914a48cfd28c4034c351c155b0fb3152493938fb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Videos/Step8/Infrastructure8.fs:69-81 | Videos/Step9/Infrastructure9.fs:146-158 \u2014 before extracting anything, compare \u0060Videos/Step8/Infrastructure8.fs\u0060 and \u0060Videos/Step9/Infrastructure9.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step8/Infrastructure8.fs"},"region":{"startLine":69}}}],"partialFingerprints":{"codehealthFindingId/v1":"984fceb80000e7bd261d2a4de3760b33d84893cd5ffb17b023be48d51102a52a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 5): EventSourced/Domain.fs:126-137 | Videos/Step6/Domain6.fs:81-92 | Videos/Step7/Domain7.fs:87-98 | Videos/Step8/Domain8.fs:87-98 | Videos/Step9/Domain9.fs:87-98 \u2014 before extracting anything, compare \u0060EventSourced/Domain.fs\u0060 and \u0060Videos/Step6/Domain6.fs\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Domain.fs"},"region":{"startLine":126}}}],"partialFingerprints":{"codehealthFindingId/v1":"f7d6569855a62d2b154bc5d409d7c014a042ea906b0ca50ff764620cc3278732"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 3): Talk/Step1/Infrastructure1.fs:12-23 | Talk/Step2/Infrastructure2.fs:16-27 | Talk/Step3/Infrastructure3.fs:17-28 \u2014 before extracting anything, compare \u0060Talk/Step1/Infrastructure1.fs\u0060 and \u0060Talk/Step2/Infrastructure2.fs\u0060 as WHOLE FILES: 90% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step1/Infrastructure1.fs"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"ba7ee06b06cd8c3d4ec88190a5189be45803b8c4a542a8579298e01405dec1df"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 3): Talk/Step1/Program1.fs:14-25 | Talk/Step2/Program2.fs:14-25 | Talk/Step3/Program3.fs:13-24 \u2014 before extracting anything, compare \u0060Talk/Step2/Program2.fs\u0060 and \u0060Talk/Step3/Program3.fs\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step1/Program1.fs:14\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step1/Program1.fs"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"74b512c8d718da32ccbe587e79c59a82a58e6fda5ae532a0a78e951b364cfc9f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): EventSourced/Utils/List.fs:5-16 | Videos/Extensions/Seq.fs:5-16 \u2014 before extracting anything, compare \u0060EventSourced/Utils/List.fs\u0060 and \u0060Videos/Extensions/Seq.fs\u0060 as WHOLE FILES: 85% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Utils/List.fs"},"region":{"startLine":5}}}],"partialFingerprints":{"codehealthFindingId/v1":"0ff2514270659514154acf02c3449e8d4bbd257e598628ade5d6435eaea2336b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Videos/Step1.fs:76-87 | Videos/Step2.fs:116-127 \u2014 before extracting anything, compare \u0060Videos/Step1.fs\u0060 and \u0060Videos/Step2.fs\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step1.fs"},"region":{"startLine":76}}}],"partialFingerprints":{"codehealthFindingId/v1":"ea8b76f8f2a5e7de67477d01a01977600d3b09d35c09372acfa9833284fb40c4"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11\u201312 lines \u00D7 2): Videos/Step8/Infrastructure8.fs:113-123 | Videos/Step9/Infrastructure9.fs:193-204 \u2014 before extracting anything, compare \u0060Videos/Step8/Infrastructure8.fs\u0060 and \u0060Videos/Step9/Infrastructure9.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step8/Infrastructure8.fs"},"region":{"startLine":113}}}],"partialFingerprints":{"codehealthFindingId/v1":"a9ab7432d756dfe05956bcd956b03e7bca7cc68fa5e124e5cc39e9772d0023ae"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): EventSourced/Infrastructure/EventStorage/FileStorage.fs:22-32 | Videos/Step9/Infrastructure9.fs:218-228 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at \u0060EventSourced/Infrastructure/EventStorage/FileStorage.fs:22\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Infrastructure/EventStorage/FileStorage.fs"},"region":{"startLine":22}}}],"partialFingerprints":{"codehealthFindingId/v1":"06bae5156095560e250bf1ff33c9dae11571801ee0865fbf2b07e201d38eec9a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Talk/Step4/Infrastructure4.fs:3-13 | Videos/Step5.fs:3-13 \u2014 before extracting anything, compare \u0060Talk/Step4/Infrastructure4.fs\u0060 and \u0060Videos/Step5.fs\u0060 as WHOLE FILES: 97% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step4/Infrastructure4.fs:3\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step4/Infrastructure4.fs"},"region":{"startLine":3}}}],"partialFingerprints":{"codehealthFindingId/v1":"4455f27c8cea9adb1b47a8a3ca18cb6f47e7113ed1fa3dde8f73160c6988dba1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 3): Talk/Step2/Program2.fs:17-26 | Talk/Step3/Program3.fs:16-25 | Talk/Step4/Program4.fs:21-30 \u2014 before extracting anything, compare \u0060Talk/Step2/Program2.fs\u0060 and \u0060Talk/Step3/Program3.fs\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Talk/Step2/Program2.fs:17\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Program2.fs"},"region":{"startLine":17}}}],"partialFingerprints":{"codehealthFindingId/v1":"4d5b3c800e0c972dbc634d3ecfc7735e3b004cdd3dc37259fe1c51d0a04b4f5e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9\u201310 lines \u00D7 2): Videos/Step8/Infrastructure8.fs:178-186 | Videos/Step9/Infrastructure9.fs:240-249 \u2014 before extracting anything, compare \u0060Videos/Step8/Infrastructure8.fs\u0060 and \u0060Videos/Step9/Infrastructure9.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step8/Infrastructure8.fs"},"region":{"startLine":178}}}],"partialFingerprints":{"codehealthFindingId/v1":"9700ebdf6a10beb442d21e2a1928582acb494126ca072dfbf193cff4d08be9e2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7\u20139 lines \u00D7 2): Videos/Step7/Infrastructure7.fs:56-64 | Videos/Step8/Infrastructure8.fs:175-181 \u2014 before extracting anything, compare \u0060Videos/Step7/Infrastructure7.fs\u0060 and \u0060Videos/Step8/Infrastructure8.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step7/Infrastructure7.fs"},"region":{"startLine":56}}}],"partialFingerprints":{"codehealthFindingId/v1":"936e5af1083f59eee4c6170129caca04b037d24d0c9069ba534c0be08a33aeed"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 3): EventSourced/Infrastructure/EventStorage/FileStorage.fs:23-28 | Videos/Step8/Infrastructure8.fs:117-123 | Videos/Step9/Infrastructure9.fs:219-224 \u2014 before extracting anything, compare \u0060Videos/Step8/Infrastructure8.fs\u0060 and \u0060Videos/Step9/Infrastructure9.fs\u0060 as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Infrastructure/EventStorage/FileStorage.fs"},"region":{"startLine":23}}}],"partialFingerprints":{"codehealthFindingId/v1":"5559e6a2cfe21c4bffab40da9898bf3887c87dbaf3029173fb75d07413333b05"}},{"ruleId":"D20","level":"note","message":{"text":"No ADRs found: No ADRs found. No recognised ADR directory (\u0060docs/adr/\u0060, \u0060docs/decisions/\u0060, \u0060adr/\u0060, \u0060docs/rfcs/\u0060, an \u0060ADR0001/\u0060 folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (\u0060docs/adr/use-postgres.md\u0060, \u0060docs/adr/2024/0001-x.md\u0060); or a file anywhere whose name is ADR-shaped (\u00600001-use-postgres.md\u0060, \u0060adr-012-caching.md\u0060); or, when neither turned anything up, a document carrying the decision-record signature (an \u0022Architecture Decision Record\u0022 heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these \u2014 unnumbered files outside any recognised directory, without those headings \u2014 is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in \u0060docs/adr/\u0060."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"d2bea044ff79d7d275f5a91a6e2f548586178eaf480274c33960ad020c854631"}},{"ruleId":"D34","level":"note","message":{"text":"Dormant codebase: 28 of 28 significant files have no living knowledge \u2014 the codebase as a whole is dormant, not 28 separate risks. Counted over 28 of the 60 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"4c69f1e54b7dd6fe9029dd02df6ba8f8145b789f2f18dbdaa086c40ded49dba6"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step9/Infrastructure9.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"fe9a8b7f3a6fcb1b668925f4aa06e6f2af5b3e74fcd5e6ef5c91e4cf331ff90e"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step8/Infrastructure8.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"5b728eada0e6e152c5ee33893d34c815787c17d3df0a31795fa3ca6503fd2e7a"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step5.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"2b18a2bf034802f8cfccda6f46745d441e05b9a50206bb0e035762ffb8febcd8"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Program.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"ecab8d5085a1de6c953edd7a4f8b261fde73eaf32ea283cd4631084514941fa4"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step4.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"22ea5867c0a60d9fa4be8bcf09e87812806eff77fda1ab8b78442bc458214cc1"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Application.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"76e0da2bea537ccce1393a0432938930d78dfd06ccc1a6b4e7b3506b495c5746"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Infrastructure6.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"e7ad7c1b9bcbe1b61065eaf2da14a503cd552e148fe849363fcbbfca1ba3a609"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step7/Infrastructure7.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"c23bdde803a5de266bcc9a0f948191814fdc357d86d14c69a7b44248e7897523"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Infrastructure/Types.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"298c4356323da30d0c437aa37e6304c31ae86317c07064d1827a5f7ddb5835ba"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step3.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"161fa1571cacae5974152ad2dd9c09441197ec5b723d8cbaac05183b325543f8"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step4/Program4.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"c7cc953b24d300b4c9dbc64f5586322f45acf46c6301f26f9475e45d26a4d341"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Brainstorming/Domain.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"5acf124aa28b19a6b9eef98b8ffc598caf90250a0884ec5677d7a43418f2d870"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Program.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"7fc236e7b17dc6ed4d040b7730e6dc6994f87d7924bbc6adb2bce3b598047bc0"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step7/Application7.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"a7c21fd37ceddc6f1d6ec2b536fdb2659fdf2de00d5d9d61f8658d1da282eba2"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step6/Application6.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"c60d1a1c9399911540d4f338e79639083be006db497e3a0c90aa356b1dfd9c17"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Program.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"e75c806918455eef3058302c9feaa70a41eeb583fe25c43e69fdc17789b5afed"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Domain.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"ec6a99c5d12629e3abf39579a3e9786f5af4d73fa3067eb2ce5b4dcbc4d7785b"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step9/Application9.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"ae0e20cbd2cae90a2cf11eeee25a27775701a5ed2cc4df232e241bc69a7ea3a2"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Brainstorming/Program.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"ef5026d8288cdbf3ce9ab1724741d49bb9c8775ca567a6f2d31369d05029cd44"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step8/Application8.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"80a6b5bed66bcb65a724a8bfaa7349dc1bf5778360066ad4f882a6369c61cdf6"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step2.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"9a649f9d667acef518cb0ca92c7ca0bb806e6d6a4905cb908affb21ece03667a"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step9/Domain9.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"d44c83c7af1681b46063965082c8cc47b23aa55b4aaf72352be4fab1c8f2afd3"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step8/Domain8.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"4b7c30a5c78cc510c8ea1fe7a6869a7ca3038140ac80b9e2c318b4a01669c40c"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Step7/Domain7.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"191b6efc89e0d62f592a499f9642a8929413b80d2aa867d2e30303794d630547"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step2/Program2.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"1c41b871503851a7a3f6062d88140654190e73bf69f0c893c7784d272e235dfc"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step3/Program3.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"fd87589689ee3a4e3e88503bac201bb21ea5d450122c747e1a04c13ae7ffba45"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Step4/Infrastructure4.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"3a0819ef19877d4ae2325faac83f9b5b8af9cd3737099f38f39f47e1dbed02da"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned file: No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/Infrastructure/EventStorage/PostgresStorage.fs"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"0b75c87527e4345dffcc2bd114ef592fcacdd0d3e4362b9c57811291a1d52549"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET netcoreapp2.0: Talk/Talk.fsproj declares .NET netcoreapp2.0 as this project\u0027s target framework, and .NET Core 2.0, support ended 2018-10-01. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2018-10-01 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Talk/Talk.fsproj"},"region":{"startLine":5}}}],"partialFingerprints":{"codehealthFindingId/v1":"f8a8da723ab3dc6d2c5a252afcde622bb8dfcb36ef65ff8a8fd76d40d9af5e46"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET netcoreapp2.1: Videos/Videos.fsproj declares .NET netcoreapp2.1 as this project\u0027s target framework, and .NET Core 2.1, support ended 2021-08-21. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2021-08-21 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Videos/Videos.fsproj"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"c824cd4f6d40cf2fc89ca12356e788778bdd501d6ccd3e639793b9e549ade994"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET netcoreapp2.2: EventSourced/EventSourced.fsproj declares .NET netcoreapp2.2 as this project\u0027s target framework, and .NET Core 2.2, support ended 2019-12-23. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2019-12-23 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"EventSourced/EventSourced.fsproj"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"bef317989e56f8be015284dd63eb436b1298f1d4a88b4a13bafce49cab2cb8ee"}},{"ruleId":"M1","level":"warning","message":{"text":"No solution README: No README at the repository root \u2014 newcomers have no entry point."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"99571e6779d583f4e10f2ad6ba5fa5b359d5b9fdc36710de4024df30895d9e03"}},{"ruleId":"M2","level":"note","message":{"text":"No ADRs: No Architecture Decision Records found \u2014 no conventional ADR directory, no numbered \u0060NNNN-title\u0060 documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"670b3d6e36a756d63097d0dfbf90afd5fc761308800b9354894a07c3f4e4aa14"}},{"ruleId":"M2","level":"note","message":{"text":"No architecture diagram/doc: No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named \u0060architecture\u0060 or \u0060design\u0060 in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape \u2014 no \u0060## Architecture\u0060 heading, no \u0022architecture overview\u0022/\u0022high-level design\u0022 phrasing, no \u0022the architecture is \u2026\u0022 introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document \u2014 not evidence that nobody wrote the shape down."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"0c190e7c159d1850ee706c3ac4486e151e8a4fe169de4bf61436b9f399654f06"}},{"ruleId":"M3","level":"note","message":{"text":"No src/ separation: Production code isn\u0027t grouped under a src/ folder \u2014 it\u0027s spread across several top-level directories, so there\u0027s no one place that says \u0027this is the product\u0027."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"fdf7f5b24e313364d10170a5c2542959902fe0d26ed70edef3eaa10ec5bcdb1d"}},{"ruleId":"P1","level":"warning","message":{"text":"No CI pipeline: No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, \u2026) \u2014 changes aren\u0027t gated by an automated build/test."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"44f01af96e50474fba2df84d95ddf4f7e1d34c29c307830b9efc9057daa6b670"}},{"ruleId":"P2","level":"warning","message":{"text":"No structured logging: No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page \u2014 but when a run fails on a user\u0027s machine, neither they nor you have anything to read."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"9f10d71351c6778ebe84e761f82a90d4f9ed6c64f5e01975ede8fda7e4e2ebc5"}},{"ruleId":"P3","level":"note","message":{"text":"No SAST: No static application security testing detected. For this repository\u0027s stack, add \u0060semgrep --config=auto\u0060 plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) \u2014 this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge\u0027s web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen \u2014 if that is your case the row is wrong, and saying so is more useful than adding a second scanner."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"6e54424179c892f03ef2fd003130ac4bd43f39bbf3b1ca0a0143e25acb80ec87"}},{"ruleId":"P3","level":"note","message":{"text":"No dependency-update automation: \u0060paket.dependencies\u0060 declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices \u2014 including after an advisory is published against it. Add a \u0060.github/dependabot.yml\u0060 with one \u0060package-ecosystem\u0060 entry per ecosystem the tree uses (or an enabled \u0060renovate.json\u0060), and gate pull requests with \u0060actions/dependency-review-action\u0060."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"paket.dependencies"},"region":{"startLine":3}}}],"partialFingerprints":{"codehealthFindingId/v1":"fca76f9e7f8af5cbca13374b1cb689b030c8710ce7b1cc328b36ebe53a6c5e78"}},{"ruleId":"P6","level":"note","message":{"text":"No changelog: No CHANGELOG/HISTORY/RELEASES file \u2014 what shipped when isn\u0027t easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)"},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"dda5aa5aed8cbb292c3ef2b733bc138f614293ae6426c85e98bf31ef330d9415"}}],"taxonomies":[{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d","organization":"MITRE","informationUri":"https://cwe.mitre.org/","isComprehensive":false,"shortDescription":{"text":"The MITRE Common Weakness Enumeration (CWE)."},"taxa":[{"id":"CWE-259","guid":"ae9ad959-fbb6-9d5e-892d-3dca66da0b69","name":"Use of Hard-coded Password","shortDescription":{"text":"Use of Hard-coded Password"},"helpUri":"https://cwe.mitre.org/data/definitions/259.html"},{"id":"CWE-77","guid":"332c8ade-6612-9f56-a06b-d8d90b1a8750","name":"Improper Neutralization of Special Elements used in a Command (\u0027Command Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in a Command (\u0027Command Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/77.html"},{"id":"CWE-78","guid":"2e31ceaf-c7ae-2e5e-9661-cfb1362789cf","name":"Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/78.html"},{"id":"CWE-79","guid":"fd45580b-e8c4-fc5e-8c2f-aa8fab0b4dbf","name":"Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)","shortDescription":{"text":"Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/79.html"},{"id":"CWE-798","guid":"5e8f057d-fee3-995a-a0cb-9fc5b0d174d1","name":"Use of Hard-coded Credentials","shortDescription":{"text":"Use of Hard-coded Credentials"},"helpUri":"https://cwe.mitre.org/data/definitions/798.html"},{"id":"CWE-89","guid":"6d08fdad-37eb-c150-bbf0-d7d946863407","name":"Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/89.html"},{"id":"CWE-94","guid":"75e7f50c-6c2f-dd52-bf40-bf6c52b861fd","name":"Improper Control of Generation of Code (\u0027Code Injection\u0027)","shortDescription":{"text":"Improper Control of Generation of Code (\u0027Code Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/94.html"}]},{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61","version":"2025","organization":"OWASP Foundation","informationUri":"https://top10.owasp.org/2025/","isComprehensive":false,"shortDescription":{"text":"The OWASP Top 10:2025 web application security risks."},"taxa":[{"id":"A05:2025","guid":"87e86033-3231-8458-8e4a-5cb82743553a","name":"Injection","shortDescription":{"text":"Injection"},"helpUri":"https://top10.owasp.org/2025/A05_2025-Injection/"},{"id":"A07:2025","guid":"334ddd78-539d-d35c-83dd-253647eb7eaf","name":"Authentication Failures","shortDescription":{"text":"Authentication Failures"},"helpUri":"https://top10.owasp.org/2025/A07_2025-Authentication_Failures/"}]}],"properties":{"codehealthPublication":{"public":true,"notice":"This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings \u2014 which rule fired, in which file, on which line, and how to fix it \u2014 are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.","securityFindingsRedacted":0,"secretScannerRunsExcluded":0}}}]}