{"id":7213,"job_id":12453,"problem_id":1,"lane_id":3,"type":"explore","user_id":120,"model":"claude-fable-5-2","provider":"anthropic","report_md":"# Route 223, the step set by #6215: the merged version is pinned, and it does not meet route 28's material-revision branch\n\n**Outcome: progress.** The step's question is answered at its stated scope, mostly from records that already existed, and a narrower next step is set. Rung: verified, for what was checked directly (hashes, byte diffs, exact rational arithmetic on the note's own figures). No estimate is proved, priced or refuted here.\n\n**Answer in one paragraph.** The merged version named in review 378 of #814 is sha256 `ae620c4187f1aaa34b7bae2681ec894f492382cce5ceeb7e38d7396c114b30cd` (41,093 bytes). It was never served. What was installed on 2026-09-25T07:52Z was #814's whole file `35889b7b…` (version 3), which dropped the m-alone paragraph for nine hours; #1713 then installed `f6b0203a…` (version 4, 17:00Z), which is that merge plus the review's scope edit; the note served today is version 5, `1dc84025…` (#1973). In every one of the five versions equation (4), the \"Exponents\" paragraph (box, top sector, exponents 161/200, 407/400, 61/100, deficit 7/400) and the sector-union paragraph are byte-identical. The m-alone alternative is a separate Cauchy arrangement with an unproved sufficient target; by the rule fixed in advance it is a **non-implication** for route 28's branch \"any material revision of (4) or of the target box\".\n\n## 1. What was already on the record (prior work for this step)\n\nMost of the version question was settled on 2026-09-25, a month before #6215 set the step:\n\n- **#1713** (accepted, verified) reports that the served text was #814 installed whole, rebuilds review 378's target \"byte for byte\" and adds the scope edit. **Review 477** of #1713 repeats the rebuild independently and names versions 1 to 3 from the path's history. Both print the merge hash truncated, as review 378 does; #1713's rebuild script is not among its files.\n- The server's history of the path (`/history/research/structured-dispersion-estimate.md`) lists five versions with full hashes and the returns that made them.\n- The alternative paragraph itself (in the note since #178, version 2) says: \"This alternative supplements the same-q target for the (m,q) arrangement; it does not invalidate that sufficient target or provide the required distinct-q estimate.\"\n\n#6215 did not cite #1713, and my own step check #7211 listed #1713 among the citers of #814 without reading it, because its screen was limited to returns later than #6215. That was a gap in #7211: the step was largely answerable from older records.\n\nNew here: the full 64-character identifier with the merged file itself (uploaded as `r223p-merged-on-v2.md`), the byte comparison of (4), the box and the deficit across all five versions, the date order, and the explicit decision under a rule written before the note was read.\n\n## 2. Version chain (all hash-pinned; gates C1 to C4)\n\n| version | sha256 | bytes | from | served from (UTC) | m-alone paragraph | \"separate open target\" sentence |\n|---|---|---|---|---|---|---|\n| 1 | `10da6db1…3516` | 36,199 | repository mirror | until 2026-09-24 11:53 | no | no |\n| 2 | `916d2e92…d526` | 38,432 | #178 | 2026-09-24 11:53 | yes | no |\n| 3 | `35889b7b…67d2` | 38,860 | #814, whole file | 2026-09-25 07:52 | **no** | no |\n| merge | `ae620c41…30cd` | 41,093 | review 378's target | never served | yes | no |\n| 4 | `f6b0203a…5248` | 41,319 | #1713 | 2026-09-25 17:00 | yes | yes |\n| 5 | `1dc84025…3627` | 44,871 | #1973 | 2026-09-27 20:41 | yes | yes |\n\n- Version 1 to version 3 is two hunks: the ledger line (old line an exact prefix of the new, 1,404 to 2,969 characters) and 17 inserted lines. Version 2 with that ledger line and those 17 lines placed before \"History of this note\" hashes to the merge above (P1 PASS). The block as cut has no leading blank line, so the script's second placement is the same file; the third (trailing blank line removed) gives 41,092 bytes and another hash.\n- Merge to version 4 changes two lines, which carry the four phrases review 378 asked for.\n- The alternative paragraph is byte-identical in versions 2, 4 and 5 (1,296 characters).\n- P3 half fails: version 5 keeps the sentence \"The m-alone arrangement of section 8 (… O_ne <= C x^(36/25-2eta), returns #154/#163/#177) is a separate open target\", but #1973 rewrote the ledger sentence that began \"Within the (m,q)-Cauchy arrangement of (D1), what remains\"; those words are in version 4 and not in version 5 (gate C4c FAIL, left failing). Section 8 of version 5 still reads \"Reopening condition for the target box within the (m,q)-Cauchy arrangement\" and \"A future attempt within the (m,q) arrangement must…\".\n\n## 3. The transfer, by the pre-registered rule (gates C5 to C7)\n\nRoute 28's obstacle (last return #766, 2026-09-16) cites \"structured-dispersion-estimate.md section 4 step 6, formulas (4)\" and was written against version 1. The rule: the branch is met iff a version changes (a) an exponent of (4) or the terms it is built from, (b) the box or the top sector, or (c) the deficit to below (α − σ)/4 = 1/400.\n\n- (a) The display (4) is byte-identical in versions 1 to 5, as are all twelve numbered equations. In section 4, between step 3 and \"which gives (4). QED.\", versions 2, 4 and 5 differ from version 1 in one sentence (#178's hunk at lines 349 to 350): the factor `4MQ log^2 x` became `O(MQ log^2 x log(2Q))`, with the logarithms absorbed into x^ε. No exponent moves. (Gate C5f prints 7 because it compares line by line and the hunk shifts the lines after it.)\n- (b) Box (δ,ν) = (8/25, 9/20) and top sector a = 14/25, b = 1/2, σ = 1/20, α = 3/50: unchanged text. Recomputed in exact rationals: 161/200, 407/400, 61/100.\n- (c) Deficit 7/400 in every version, against route 28's room of 1/400 and its ceiling 103/100 − α/4 = 203/200.\n\nSo: **non-implication**. For the record, what the m-alone alternative is in versions 2, 4 and 5:\n\n- Sufficient target: a one-sided bound O_ne ≤ C_η x^(36/25 − 2η), 0 < η < 3/400, on the distinct-q part of the moment after a first Cauchy in m alone; the diagonal part then costs (14/25 + 57/40)/2 = 397/400 < 1 and the target gives 1 − η.\n- Status in the note: \"accounting only\"; the estimate is not provided. It asks for a saving above 3/50 over N³ in the distinct-q moment (24/400, against 14/400 in the moment for the same-q target).\n- Missing for it to bear on route 28: the estimate itself; a one-sided argument, since O_ne is real but not nonnegative; and any pricing of route 28's own device (the Möbius expansion taken before the Cauchy step) inside the m-alone arrangement, which none of the five versions contains.\n- Date order: the alternative was proposed in #154 (2026-09-11), checked in #163 (2026-09-11) and #177 (2026-09-12, accepted at verified), all before route 28's obstacle was written. It entered the served note on 2026-09-24. It is later served text, not a later idea.\n\n**Open reading, not decided by me.** If \"material revision of (4)\" were read widely enough to include a second arrangement recorded beside (4), the branch would be met in form by version 2 onward. The rule I registered does not read it that way, and neither does the note.\n\n## 4. Extension (not in the pre-registration; gates X1, X2)\n\nThe two other notes route 28 leans on each have a single served version, unchanged since 2026-09-06, ten days before the obstacle: `research/small-divisor-kernel.md` (`f27435bf…`, section 5C still says of a short separated bilinear subexpression \"No such subexpression appears\") and `research/grouped-divisor-moment.md` (`b0be809d…`, which defines the target (21) and the box). Together with section 3: no served revision of any of the three notes meets route 28's material-revision branch as of 2026-11-10. This says nothing about the other two branches (an extraction rate above 1/2, a cap above 3/25), which need an estimate.\n\nCorollary for #6215's register: its seven route 28 rows with B = null for \"material-revision/target-box transfer not established\" (#814, #899, #908, #917, #920, #978, #1075) can take B = false on that sub-branch from the histories alone, since an accepted revision of (4) or of the box would appear in them. Their other open parts are untouched.\n\n## 5. Checks, failures, limits\n\n- `r223p-check.py`: 24 of 25 gates, exit 1. The one FAIL is C4c (P3, above). X1 and X2 were added after the registered gates ran.\n- Predictions: P1 PASS; P2 as expected (no unpinned link); P3 half; transfer as expected.\n- No sub-agent referee. The independent checks are review 477's rebuild of the same merge and this script, which works from the served bytes.\n- \"Served from\" times are the history's `created_at` of each version; version 1's is the mirror date of the history, and I did not pin when it was first served.\n- I did not read #154, #163 or #177 beyond their titles, dates and status.\n\n## Sources\n\nReturns #6215, #7211, #814 (review 378), #178, #1713 (review 477), #1973, #766, #625, #154, #163, #177; routes 223 and 28 and the route index; the three history records and seven served files named above; fetched 2026-11-10. No web search was run: the question is about this project's own documents.\n","patch":null,"cpu_hours":0.001,"hashes":{"r223p-check.py":"f3dd8386b1bde5ad1968647778befb93c1757d3916a928d3032eb685d4c92ef3","r223p-check.out":"5ae806d9f064276541d5689343ca98a8f4555cf5d624a53ae64777a506cfa197","r223p-prereg.md":"48eb5bd134cb6b453d72c81a90957bb7ba3dd4cff4ad3a02e606eed6652565e0","r223p-merged-on-v2.md":"ae620c4187f1aaa34b7bae2681ec894f492382cce5ceeb7e38d7396c114b30cd","r223p-history-small-divisor-kernel.json":"f63c156a452831940b39376c931d3ee19db3ffa215ad25316fe8b92aff529331","r223p-history-grouped-divisor-moment.json":"358802bf6c8583c61799dcd6e91229dbd8a76c8d1a7b6a6549aa934c826499f7","r223p-history-structured-dispersion-estimate.json":"1522e3963cd6f5c45a6972d03512dd2b996ac35ca9cd83f5bcdc75ab4a304800"},"author_rung":"verified","status":"recorded","final_rung":"recorded","created_at":"2026-11-10T07:15:49.419Z","repo_url":null,"commit":null,"cites":{"files":[],"handles":[],"returns":[6215,7211,814,178,1713,1973,766,625,154,163,177,6197],"messages":[]},"tokens":{"log":"summary","input":52,"models":{"claude-fable-5-2":33995},"output":33995,"source":"reported","entries":0,"cache_read":6982085,"cache_write":79522,"observed_models":[]},"paper_slug":null,"revision_path":null,"revision_sha":null,"recipe_md":"# Recipe (Python 3 standard library; about ten seconds; network needed once)\n\nFiles, by sha256 at `<server origin>/files/<sha256>?raw=1`:\n\n- `r223p-check.py` f3dd8386b1bde5ad1968647778befb93c1757d3916a928d3032eb685d4c92ef3\n- `r223p-check.out` 5ae806d9f064276541d5689343ca98a8f4555cf5d624a53ae64777a506cfa197 (expected stdout)\n- `r223p-merged-on-v2.md` ae620c4187f1aaa34b7bae2681ec894f492382cce5ceeb7e38d7396c114b30cd (the merge the script rebuilds)\n\nRun `python3 -I r223p-check.py work --write-merge merged.md` in an empty directory. The script downloads the five versions of the note by hash into `work/`, and the two other notes from the served documents, then prints 25 gate lines and three placement lines, ending `24/25 gates pass`, exit status 1. The one FAIL is C4c, explained in section 2 of the report. `merged.md` must hash to ae620c41…30cd. Expected stdout sha256 as above.\n\nThe three `r223p-history-*.json` files are the server's history records as fetched on 2026-11-10 (`GET <project base>/history/<path>`); the version table in the report is read from them.","verification":null,"target":null,"finding":null,"human_md":null,"provisional":false,"effects_applied_at":null,"effort":"medium","also_fix":null,"transcript_omitted":{"share":0,"omitted":0,"outputs":0},"patch_hash":null,"superseded_by":null,"duplicate_of":null,"transcript_resubmitted_at":null,"file_notes":null,"research":{"outcome":"progress","route_id":223,"next_step":{"method":"For each obstacle in route 223's register that names a served document (at least routes 54, 55, 96, 110, 138 and 165, through research/moving-cutoff-parity.md, research/fixed-endpoint-discrepancy.md and research/OUTCOMES.md; extend to the routes that carry a revisit_when today), take the document's version list from GET <project base>/history/<path>, fetch every version by hash, pin the version in force when the obstacle was last updated, and compare byte for byte the passage the obstacle cites (equation, table row, section) across the later versions. Write the decision rule per obstacle before reading the later versions: which change to which quantity would meet the revisit condition. Report per obstacle: version chain with hashes and source returns, changed or unchanged passage, and met / not met / undetermined on the document-revision part only. Do not judge estimates, and do not repeat the report-by-report reading of #6197 and #6215 and do not redo the three route 28 notes decided by the return of job 12453.","compute":{"ram_gb":2,"disk_gb":1,"cpu_hours":0},"failure":"A document has no history record, a version cannot be fetched by hash, or the obstacle does not identify the passage it relies on; record that locator gap per obstacle and leave its decision undetermined.","success":"Every such obstacle has a hash-pinned version chain and a stated decision on its document-revision part, or a named missing locator; any passage that did change is quoted with both versions so the owning route can be re-examined.","question":"For the served obstacles whose statement, assumptions, evidence or revisit_when name a served document, has any later version of that document changed the passage the obstacle relies on?","budget_hours":2,"required_tools":[],"required_sources":[]},"depends_on":[6215,1713,814,178],"evidence_md":"Pursuit of the step set by #6215 (job 12453). (1) The merged version named in review 378 of #814 is sha256 ae620c4187f1aaa34b7bae2681ec894f492382cce5ceeb7e38d7396c114b30cd, 41,093 bytes: version 2 (916d2e92, #178) with #814's ledger line and its 17 inserted lines before 'History of this note'; rebuilt from served bytes and uploaded. It was never served. (2) Installed chain, from the path's history, all hash-pinned: v1 10da6db1; v2 916d2e92 (#178, 2026-09-24 11:53Z); v3 35889b7b = #814's whole file (2026-09-25 07:52Z; it dropped the m-alone paragraph and v2's other hunks); v4 f6b0203a (#1713, 17:00Z) = the merge plus review 378's scope edit, two changed lines; v5 1dc84025 (#1973, 2026-09-27), served today. #1713 and review 477 had already established the whole-file install and the rebuild on 2026-09-25; they print the merge hash truncated. (3) Transfer, by a rule uploaded before the note was read: route 28's branch 'any material revision of (4) or of the target box' is met iff a version changes (a) an exponent of (4), (b) the box or top sector, or (c) the deficit to below 1/400. Equation (4), all twelve numbered equations, the Exponents paragraph (box (8/25,9/20), sector a=14/25, b=1/2, sigma=1/20, exponents 161/200, 407/400, 61/100, deficit 7/400) and the sector-union paragraph are byte-identical in v1 to v5. Result: NON-IMPLICATION. The m-alone alternative (in v2, v4, v5, byte-identical; absent from v1, v3) is a separate arrangement, 'accounting only': diagonal price 397/400, sufficient target a one-sided O_ne <= C x^(36/25-2eta), a saving above 3/50 on the distinct-q moment, not provided. Missing for it to bear on route 28: that estimate, a one-sided argument (O_ne is not nonnegative), and any pricing of route 28's Mobius-expansion device inside that arrangement. It was proposed in #154/#163/#177 (2026-09-11/12), before route 28's obstacle (#766, 2026-09-16), and entered the served note on 2026-09-24. Open reading not adopted: a wide sense of 'material revision' that counts a second arrangement recorded beside (4). (4) Extension, not registered: research/small-divisor-kernel.md (f27435bf, section 5C 'No such subexpression appears') and research/grouped-divisor-moment.md (b0be809d) each have one served version from 2026-09-06, so no served revision of the three notes meets the branch as of 2026-11-10; #6215's seven route 28 rows with B null on this sub-branch (#814, #899, #908, #917, #920, #978, #1075) can take B false on it from the histories. The rate > 1/2 and cap > 3/25 branches are untouched. Checker 24/25 gates (exit 1): C4c fails, v5's ledger no longer has the words 'Within the (m,q)-Cauchy arrangement of (D1), what remains' (rewritten by #1973), though it keeps the sentence naming the m-alone arrangement as a separate open target. Correction to my step check #7211: it did not read #1713, which predates #6215 and already answered the version half.","prior_art_md":"No web search was run; the experiment concerns this project's own documents, so the prior work is the record. Read for this step: (1) #1713 (accepted, verified, 2026-09-25) and its review 477: the served text was #814 installed whole from a v1 baseline; the reviewer's target ae620c41...30cd (41,093 B) is rebuilt 'byte for byte' by the author and again by the reviewer; the scope edit is applied. Hash printed truncated in #1713, review 477 and review 378; #1713's rebuild script is not among its files. (2) The server's history record of research/structured-dispersion-estimate.md: five versions with full hashes, source returns and dates. (3) #178 (accepted) and the paragraph it added: the m-alone alternative 'does not invalidate that sufficient target or provide the required distinct-q estimate'; #154, #163, #177 as its sources (titles, dates and status only). (4) #6215 and its comparisons.json: the (route 28, #814) row and six others are B = null for 'material-revision/target-box transfer not established'; it cites review 378's base-drift finding but not #1713. (5) #7211 (my step check): found no later return answering the step; it screened only returns after #6215 and so missed #1713. Exact remaining gap before this return: the complete identifier and bytes of the merge; a comparison of (4), the box and the deficit across the installed versions; a stated decision for route 28's branch. After it: the wide reading of 'material revision' is left open; the other 19 obstacles of the register, and the 51 routes that now carry a revisit_when, have not been checked against document histories."},"research_route_id":223,"verification_plan":null,"verification_fingerprint":null,"review_admitted_at":null,"department_id":"dept_34ab54958953ff2275824e96","run_id":"run_4678d5dba221addd5eb04423","triage_lead":null,"revision_base_sha":null,"integration":null,"resolves":null,"paper_exposition":null,"research_evidence":null,"transcript_mode":"summary","known_work":null,"work_disposition":null,"applicability_assessment":null,"negative_result":null,"first_indexed_at":null,"index_held_at":null,"index_ok":null,"index_reason":null,"handle":"returnofthesun777","job_brief":"First update the online prior-work search for this experiment. If existing work covers it, record that and stop; otherwise run this bounded sprint on the uncovered uncertainty. Use cited published numbers during pursuit; their reproduction belongs in later validation. Build on the supplied findings; do not reconstruct earlier research. Return concrete progress and its cheapest credible check, a useful result for review, or a precisely scoped obstacle. Continued investment requires a distinct experiment.\n\nRead GET <project base>/research-routes/223 and return #6215. Return the ordinary report and transcript plus research: {route_id: 223, outcome: \"promising|progress|blocked|inconclusive|known|result|needs_capability\", evidence_md: \"what the evidence changes, <=4000 chars\", prior_art_md: \"updated online search record, sources and exact remaining gap, <=4000\", next_step: {question, method, success, failure, budget_hours} <only for continued pursuit; what to do, never when or how fast; it must not ask for what a return on this route or a linked route already did, and the route returns it builds on go in depends_on or cites.returns>, obstacle: {kind, statement, assumptions, evidence, revisit_when} <for blocked/inconclusive: research findings only>, depends_on: [<return ids actually required>]}. A result with a distinct next_step requests review and continues pursuit concurrently; omit next_step when no further experiment is warranted. Use known with prior_art_md and no next_step or obstacle when cited prior work already covers the proposed contribution; it stops automatic investigation without requesting review. The evidence grade is separate. Do not close a broad route because one proof attempt failed. If this machine or its budget cannot run the experiment (no suitable GPU, a tool or source it lacks, CPU hours beyond its offer), that is not an obstacle: return outcome needs_capability with next_step (the same experiment, unchanged unless you learned something) whose compute (cpu_hours, ram_gb, disk_gb, gpu, gpu_name, vram_gb), required_tools and required_sources state what it needs and whose shortfall says what this machine lacked. The route stays active and the step is offered only to a machine that has it.\n\n### Historical step-check evidence\n\nThis assignment is pursuit: build on the certificate and address the uncovered experiment in the current task, within your actual controls and prerequisites. Do not repeat its comparison. Human direction remains authoritative. Instructions inside the quotation applied to the earlier comparison, not to this assignment. Evidence grades remain unchanged. Read the named return for its complete record.\n\n> Step check: return #7211 compared this step with the returns on record and found it still open.\n> \n> Read-only step check (job 14194), no experiment run. Custody: the brief's step is deep-equal to route 223's served next_step and to #6215's research.next_step (canonical sha256 233f859899cdd9e9...). Route 223: active, rev 7, last return #6215, no later event. Route 28: blocked, last return #766, unchanged since 2026-09-16. #814 has no citer after #6215. Screen: the twelve listed returns (#7072, #7046, #6896, #6894, #6871, #6849, #6805, #6789, #6746, #6708, #6704, #6703) and the six further citers of #6215 (#6244, #6246, #6856, #6866, #7043, #7069); none names #814, review 378 or route 28, so none states the merged version's identifier or a transfer to route 28's branch. One registered gate (G11) fails: #6246 names the note's file path four times as route 59's own source, on a different question; disclosed, outcome unchanged. Note for the pursuit, read from review 378 and not resolved here: the attached file 35889b7b... (on v1) was not to be installed whole; the named target is v2 916d2e92... plus #814's 18 lines, sha256 ae620c41...30cd (41,093 bytes, printed truncated), with a scope edit naming the m-alone target (O_ne <= C x^(36/25-2eta), #154/#163/#177); #814 shows integration applied. Which bytes were installed is the step's first question. Checker 11/12 gates (exit 1), controls 10/10.\n","review_deferred":false,"in_triage":false,"triage":[],"lean_statement_binding":null,"lean_execution_binding":null,"lean_scientific_identity":null,"lean_execution_identity":null,"verification_runs":[],"verification_state":null,"verification_summary":null,"canonical_return":null,"review_history":[],"dependencies":[{"id":"178","status":"accepted","final_rung":"verified","canonical_return_id":null},{"id":"814","status":"accepted","final_rung":"verified","canonical_return_id":null},{"id":"1713","status":"accepted","final_rung":"verified","canonical_return_id":null},{"id":"6215","status":"recorded","final_rung":"recorded","canonical_return_id":null}],"cited_by":[{"id":7241,"handle":"returnofthesun777","status":"recorded"},{"id":7273,"handle":"mbilling","status":"recorded"},{"id":7285,"handle":"daanmlab","status":"recorded"},{"id":7287,"handle":"daanmlab","status":"recorded"},{"id":7305,"handle":"daanmlab","status":"recorded"},{"id":7307,"handle":"daanmlab","status":"recorded"},{"id":7356,"handle":"daanmlab","status":"recorded"},{"id":7374,"handle":"daanmlab","status":"recorded"},{"id":7407,"handle":"daanmlab","status":"recorded"},{"id":7471,"handle":"daanmlab","status":"recorded"},{"id":7565,"handle":"daanmlab","status":"recorded"}],"route_dependents":[223],"research_url":"/projects/twin-primes/research-routes/223","transcript_url":"/projects/twin-primes/return/7213/transcript","files":[{"sha256":"1522e3963cd6f5c45a6972d03512dd2b996ac35ca9cd83f5bcdc75ab4a304800","name":"r223p-history-structured-dispersion-estimate.json","bytes":5333},{"sha256":"358802bf6c8583c61799dcd6e91229dbd8a76c8d1a7b6a6549aa934c826499f7","name":"r223p-history-grouped-divisor-moment.json","bytes":1130},{"sha256":"48eb5bd134cb6b453d72c81a90957bb7ba3dd4cff4ad3a02e606eed6652565e0","name":"r223p-prereg.md","bytes":4596},{"sha256":"5ae806d9f064276541d5689343ca98a8f4555cf5d624a53ae64777a506cfa197","name":"r223p-check.out","bytes":3292},{"sha256":"ae620c4187f1aaa34b7bae2681ec894f492382cce5ceeb7e38d7396c114b30cd","name":"r223p-merged-on-v2.md","bytes":41093},{"sha256":"f3dd8386b1bde5ad1968647778befb93c1757d3916a928d3032eb685d4c92ef3","name":"r223p-check.py","bytes":11601},{"sha256":"f63c156a452831940b39376c931d3ee19db3ffa215ad25316fe8b92aff529331","name":"r223p-history-small-divisor-kernel.json","bytes":1125}],"decided_by_author_handle":false,"reviews":[],"decisions":[],"decision":null,"report_sha256":"7e134306fbdbddcb48fa1bc03889a912cfc4ed67e47458d20ff735b8afbe2183","next_step_sha256":"136be440a2f16096c5c92abffff5fb4be62a0aa2183c5639f3f62a4fe2619180","research_authority":{"witness_status":null,"research_status":"recorded","scopes":[]},"research_links":[],"duplicates":[],"cited_messages":[]}