## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `rotator-cuff-tear`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/rotator-cuff-tear/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/rotator-cuff-tear/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/rotator-cuff-tear/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/rotator-cuff-tear/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/rotator-cuff-tear/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/rotator-cuff-tear/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `rotator-cuff-tear` v4 · content_hash `2f98379ba052981f…` · thread_head genesis
- **thesis (c1):** Rotator cuff abnormalities appear incidentally on MRI in people without shoulder symptoms, so a tear on a scan is not automatically the cause of the pain.
  - c2 [observational/active] Conservative treatment produces clinical stability even while fatty infiltration of the muscle progresses, so the tissue getting worse and the patient getting b
  - c3 [rct/active] Surgical versus non-surgical management for partial rotator cuff tears has systematic review evidence, and structural severity predicts outcome better than labo
  - c4 [rct/active] Bony morphology of the shoulder is associated with retear risk after repair, and early versus delayed mobilisation after repair has been compared systematically
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/rotator-cuff-tear/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/rotator-cuff-tear/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `rotator-cuff-tear`
- **title:** Rotator cuff tears: four tendons holding a shallow joint, and what a scan can tell you
- **url:** https://miscsubjects.com/a/rotator-cuff-tear
- **register:** accessible
- **updated:** 2026-08-05T09:19:47.304Z

## Body

Start with the number that should be read before any scan report, because it changes what the report means.

A 2026 study in JAMA Internal Medicine looked at shoulder MRIs from people with no shoulder symptoms at all, and compared them with scans from people who had pain.

**96% of the pain-free shoulders had rotator cuff abnormalities. So did 98% of the painful ones.**

[[embed:source:s1]]

One thousand and thirty-nine of 1,076 shoulders that felt completely normal showed something a radiologist would write down. The authors draw the obvious conclusion and put it in the abstract: these findings often represent normal age-related change rather than disease, and they call into question the value of routine imaging for shoulder pain with no injury behind it.

This does not mean your scan is wrong or that your pain is imaginary. It means the scan cannot tell you which of the findings on it is responsible for what you feel — because nearly everyone your age has those findings, and most of them have no pain.

## What the rotator cuff is, and what "tear" actually describes

Four muscles wrap the shoulder blade and their tendons converge into a cuff over the top of the arm bone. Their job is to hold the ball centred in a very shallow socket while the big muscles move the arm. The shoulder is the most mobile joint in the body and it pays for that with the least inherent stability, which the cuff supplies.

"Tear" covers a wide range. A partial-thickness tear means the tendon is damaged part of the way through. A full-thickness tear means there is a hole all the way through, which is not the same as the tendon being detached or the arm not working. Many full-thickness tears function well, and the distinction that matters clinically is usually not partial-versus-full but whether it was torn by an injury or wore through over years.

A sudden tear in a younger person after a specific event is a different problem with a different urgency from a degenerative tear found on a scan in someone in their sixties. Most of the literature below is about the second.

## Conservative treatment works clinically, while the muscle keeps degenerating

This is the most interesting finding in the field and it takes a moment to absorb.

A study followed people over 50 with rotator cuff tears treated without surgery, and tracked both how they were doing and what the muscle looked like. The clinical outcome was favourable. Meanwhile, muscle wasting and fatty infiltration got measurably worse — in 54.3% at two years and 71.4% at five.

And the two did not track each other: no correlation was found between the function score and the structural change.

[[embed:source:s2]]

The authors describe the fatty degeneration as an inexorable process, independent of how the person is doing clinically.

So there are two different things happening in your shoulder, and they are not the same story. One is how it feels and works. The other is what the tissue is becoming. Treating without surgery addresses the first and does not stop the second — and the second, on its own, does not appear to be what determines whether you are comfortable and functional at five years.

## Surgery wins on the statistics and loses on the threshold

For partial tears there is a direct comparison, and its result deserves to be read exactly as written. A 2026 systematic review found surgery statistically superior to non-surgical treatment — and then found the size of that advantage sat below the minimum difference a patient would actually notice.

[[embed:source:s3]]

Statistically superior, clinically below the threshold of perception. That is a genuinely useful thing to know before consenting to an operation, and it is the kind of finding that gets reported in headlines as "surgery works better".

## Who does badly without surgery, and it is simpler than expected

If conservative treatment is a reasonable first move for most degenerative tears, the practical question is who it fails. A 2026 study tested whether blood markers of inflammation and metabolism added anything to the prediction. They did not.

[[embed:source:s4]]

Tear size was the strongest predictor of short-term failure without surgery. Not inflammatory markers, not metabolic ones — the size of the hole.

That is a straightforward conversation to have with whoever is reading your scan: not "is there a tear", because at your age there probably is and so has almost everyone else, but how big it is.

## If you do have it repaired

**Muscle quality predicts whether the repair holds.** A 24-year retrospective series found the bony shape of the shoulder — the angles surgeons often measure — showed no association with re-tearing. What did predict it was how fatty the muscle had already become: grade 4 fatty change carried roughly five times the odds of a re-tear.

[[embed:source:s5]]

That connects back to the earlier finding. The fatty change is happening quietly regardless of symptoms, and it is what determines whether a repair will hold. It is an argument for deciding about surgery on muscle quality rather than on pain alone.

**Moving early is safe and the advantage is temporary.** A 2026 review of the randomised evidence on early versus delayed movement after repair found early mobilisation reliably improved range of motion in the first six weeks to three months, especially forward flexion and outward rotation — and that the advantage largely disappeared by six to twelve months.

[[embed:source:s6]]

Useful in both directions: getting moving sooner is not reckless, and it is not buying a better shoulder at a year either. It is buying a more comfortable first three months.

## Ten people over sixty with shoulder pain

Ten people over sixty have shoulder pain and get scanned. Roughly all ten have a rotator cuff abnormality on the report — and so would roughly all ten of a group of the same age with no pain whatever. Most do well with conservative treatment, and their muscles continue to degenerate anyway, which does not appear to determine how they feel at five years. Among those with partial tears, the ones who have surgery do statistically better and by a margin below what a person can perceive. The ones most likely to fail conservative treatment are the ones with bigger tears, and the ones whose repairs fail are the ones whose muscle had already turned fatty.

## Fatty muscle is not a healing problem

No repair peptide has randomised human trial evidence in rotator cuff tears. There is a specific reason to be more sceptical here than elsewhere: the structural process that determines the outcome of a repair is fatty infiltration of muscle, which is a different biological problem from tendon healing, and nothing in the tissue-repair literature addresses it. Any claim otherwise has to explain how it reverses fatty change in muscle. That argument, where it exists, belongs on a page naming both the compound and this condition with its tier stated. The operator of this site has a commercial interest in compounds of that kind, which is why the objection is stated here rather than left out.

## What to ask about your own scan

1. **Read your scan report against the 96%.** An abnormality is nearly universal at these ages. It identifies a finding, not the cause of your pain.
2. **Separate the two questions.** Was it torn by an event, or did it wear through? The answers point to different urgencies.
3. **Ask how big the tear is, not whether there is one.** Size was the strongest predictor of conservative treatment failing.
4. **Ask about the muscle, not just the tendon.** Fatty change carries roughly five times the odds of a repair re-tearing, and it progresses quietly whether or not you feel worse.
5. **If surgery is offered for a partial tear, ask for the effect size.** It was statistically superior and below the level a patient can notice.
6. **After a repair, moving early is not reckless.** It gives a better first three months and no measurable difference at a year.


## Claims (4)

- **c1** [observational w=?] Rotator cuff abnormalities appear incidentally on MRI in people without shoulder symptoms, so a tear on a scan is not automatically the cause of the pain.
  - who_claims: webhook
  - sources: s1
- **c2** [observational w=?] Conservative treatment produces clinical stability even while fatty infiltration of the muscle progresses, so the tissue getting worse and the patient getting better are not contradictory.
  - who_claims: webhook
  - sources: s2
- **c3** [rct w=?] Surgical versus non-surgical management for partial rotator cuff tears has systematic review evidence, and structural severity predicts outcome better than laboratory biomarkers.
  - who_claims: webhook
  - sources: s3, s4
- **c4** [rct w=?] Bony morphology of the shoulder is associated with retear risk after repair, and early versus delayed mobilisation after repair has been compared systematically.
  - who_claims: webhook
  - sources: s5, s6

## Voxel graph (4 atoms · 10 edges)
- full graph: https://miscsubjects.com/api/articles/rotator-cuff-tear/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (6)
- chain valid: yes · head: `ac1298ec6efb6fad`

### s1 · pubmed
- title: Incidental Rotator Cuff Abnormalities on Magnetic Resonance Imaging
- url: https://pubmed.ncbi.nlm.nih.gov/41697693/
- summary: JAMA Internal Medicine 2026: shoulder MRI findings in people with no symptoms compared with people in pain. The authors conclude these findings often represent normal age-related change and question the value of routine imaging for atraumatic shoulder pain.
- quote: RC abnormalities were present in 96% of asymptomatic shoulders (1039 of 1076) and 98% of symptomatic shoulders (126 of 128).
- hash: `b4c89f23a89df86a`

### s2 · pubmed
- title: Clinical stability despite progressive fatty infiltration in patients over 50 years old with full-thickness rotator cuff tears
- url: https://pubmed.ncbi.nlm.nih.gov/42480798/
- summary: Joint Bone Spine 2026: people over 50 with rotator cuff tears treated without surgery did well clinically while muscle wasting and fatty change worsened in 54.3% at two years and 71.4% at five — with no correlation between the function score and the structural change.
- quote: However, progression of fatty muscle infiltration seems an inexorable process, independent of clinical evolution.
- hash: `e50ca62584662513`

### s3 · pubmed
- title: Surgical vs. non-surgical therapy for partial tears of the rotator cuff: a systematic review and meta-analysis of pooled studies with indirect comparison
- url: https://pubmed.ncbi.nlm.nih.gov/42151917/
- summary: BMC Musculoskeletal Disorders 2026: partial rotator cuff tears, surgery versus non-surgical care. Statistically superior, and by a margin below what a patient can actually perceive.
- quote: Although surgical treatment was statistically superior to non-surgical approaches, the observed differences remained below the minimal clinically important differences (MCID), indicating limited clini
- hash: `2475206f2750d610`

### s4 · pubmed
- title: Structural severity outweighs laboratory biomarkers in predicting short-term failure under nonoperative management for partial-thickness supraspinatus tears: a prospective cohort study
- url: https://pubmed.ncbi.nlm.nih.gov/41923019/
- summary: BMC Musculoskeletal Disorders 2026: inflammatory and metabolic blood markers added little beyond clinical and imaging variables. Tear size is the question worth asking.
- quote: CONCLUSIONS: Structural severity, particularly tear size, was the strongest predictor of short-term clinical failure in partial-thickness supraspinatus tears managed nonoperatively.
- hash: `5ee52577fe260aad`

### s5 · pubmed
- title: Does bony morphology of the shoulder affect rotator cuff retear rates? A 24-year retrospective cohort of rotator cuff repairs
- url: https://pubmed.ncbi.nlm.nih.gov/41953507/
- summary: Shoulder & Elbow 2026: a 24-year series finding no association between the bony angles surgeons measure and re-tearing. Advanced fatty change in the muscle carried roughly five times the odds.
- quote: Goutallier grade 4 was the potential predictor of retear regardless of sex (Odds ratio=5.25 (1.38, 20.02); p = 0.02).
- hash: `1303419b767de1bf`

### s6 · pubmed
- title: Early Versus Delayed Mobilization After Rotator Cuff Repair: A Systematic Review of Re-tear Rates, Pain, Function, and Range of Motion
- url: https://pubmed.ncbi.nlm.nih.gov/42255867/
- summary: Cureus 2026: randomised evidence on early versus delayed movement after repair. Moving sooner buys a more comfortable first three months and no measurable difference at a year.
- quote: Early mobilization consistently improved range of motion in the short term (6 weeks to 3 months), particularly forward flexion and external rotation, but these advantages generally diminished by 6-12
- hash: `ac1298ec6efb6fad`

## Provenance (0 model passes)
- chain valid: yes · head: `genesis`


## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/rotator-cuff-tear/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/rotator-cuff-tear/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"rotator-cuff-tear","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest rotator-cuff-tear|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim rotator-cuff-tear|tier|assertion`
- **iMessage ask:** `rotator-cuff-tear|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `rotator-cuff-tear`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/rotator-cuff-tear/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/rotator-cuff-tear/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*