Fragment Reuse Matrix¶
Planning matrix — instantiates Remix-Aware Rhetorical Design
A table crossing each likely-to-travel fragment against its probable reusers, invited uses, misuse risks, and required anchors, so an artifact's afterlife is planned before release.
Before you can design a fragment's afterlife, you have to lay it out where you can see it whole. Fragment Reuse Matrix is the planning table that does this: rows for each fragment likely to travel independently — a claim, a chart, a heading, a code block, a clause — and columns for who is likely to reuse it, what uses are invited, what could go wrong, and what anchor each fragment must carry. Its defining idea is that it is a static cross-tabulation built before release — a forecast laid on a grid, not a record of what actually happened and not a live attack. By forcing every high-risk fragment onto the same table against the same questions, it turns "we should think about how this gets reused" into a completed matrix that tells the rest of the design work exactly which fragments need anchors, which need boundaries, and which are simply too dangerous to leave detachable.
Example¶
An open-source team is about to publish documentation for a new library. They know from long experience that nobody reads docs top to bottom — people copy the fragment they need and leave. So they build a fragment reuse matrix. The rows are the fragments they expect to travel: the quickstart code block, the benchmark chart, the license clause, the "not production-ready" warning, the one-line project description. The columns are reusers (a beginner copying to a side project, a blogger writing a tutorial, a competitor citing the benchmark, an enterprise legal team reading the license), invited uses, misuse risks, and required anchors. Filling the grid, one cell lights up: the quickstart block will be copied by beginners without the adjacent security note, and the misuse risk is real. The matrix doesn't fix it — but it tells them precisely which fragment needs the warning welded into the code comment, and which reuser (the copy-paste beginner) that fix is for. Every downstream mechanism now has a target list.
How it works¶
- Enumerate fragments at the grain of circulation. List the parts that actually travel on their own, not the document's ideal sections. The rows are chosen by detachability, not by outline.
- Cast the reusers as columns or a column. Populate the plausible audience set — ally, teacher, critic, opponent, algorithm — so each fragment is considered against who will carry it.
- Fill invited-use and misuse-risk cells. For each fragment/reuser intersection, record what reuse you want and what distortion you fear. The cross-product is the point: the same fragment can be a gift to one reuser and a liability with another.
- Derive the required anchor. Each row ends in a verdict — the anchor, boundary, or "do not fragment" call — that hands off to the mechanisms that will actually attach it.
Tuning parameters¶
- Fragment granularity — word/phrase versus block/section rows. Finer rows catch more travelling pieces but explode the table; coarser rows are manageable but miss the sentence that does the damage.
- Reuser resolution — a few broad audience columns versus many specific personas. More personas surface more distinct risks but multiply cells.
- Risk scoring — freeform notes versus a scored severity/likelihood field. Scoring lets you triage and sort; freeform captures nuance but resists prioritization.
- Coverage threshold — mapping every fragment versus only the high-risk few. Full coverage is thorough but expensive; a triaged subset is fast but can miss a sleeper.
- Anchor verdict discipline — whether every row must end in a concrete action or may be left "note only." Forcing a verdict prevents analysis that goes nowhere.
When it helps, and when it misleads¶
Its strength is that it makes the whole afterlife visible at once and assigns each risk an owner: after the matrix, no downstream mechanism has to guess which fragments matter or for whom. It is the natural first move of the archetype because it produces the target list everything else consumes.
Its failure mode is treating the completed grid as reality rather than a forecast — the map is not the territory, and a tidy matrix can breed a false sense of control over how fragments will actually behave once released.[n1] Real reuse is messier and more inventive than any pre-release table; the classic misuse is over-investing in an exhaustive matrix that predicts the wrong risks confidently while missing the one that lands. The guarding discipline is to keep the matrix lightweight, prioritize by severity times likelihood, and revise it against real reuse rather than defending the original forecast.
How it implements the components¶
extractable_fragment_map— the rows are the map of fragments likely to travel independently, chosen at the grain of circulation.downstream_circulation_model— the reuser columns model who will reuse each fragment and to what end, from ally to opponent.reuse_boundary_rule— the invited-use cells state, per fragment, which reuses are welcomed and which are out of bounds.
It does not implement attribution_and_provenance_handle or reuse_telemetry_loop — recording how a fragment changes over time, and tracking versions so stale excerpts are recognizable, is Fragment Versioning Log's job; the matrix is a pre-release plan, not a running record. Nor does it implement adversarial_remix_red_team: it forecasts reusers on paper, whereas Downstream Remix Red Team actually enacts them.
Related¶
- Instantiates: Remix-Aware Rhetorical Design — produces the fragment-and-reuser target list the whole design depends on.
- Sibling mechanisms: Fragment Versioning Log · Downstream Remix Red Team · Quote Survivability Test · Pull-Quote and Caveat Pairing · Context Header Template · Canonical Link and Attribution Handle · Remix License Notice · Misquote Response Protocol · Social Card and Snippet Preview
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Fragment Reuse Matrix operates as a non-executable information artifact that externalizes static or prospective structure because it a table crossing each likely-to-travel fragment against its probable reusers, invited uses, misuse risks, and required anchors, so an artifact's afterlife is planned before release.
Independent corroboration: The frozen evidence defines Fragment Reuse Matrix as 'A table crossing each likely-to-travel fragment against its probable reusers, invited uses, misuse risks, and required anchors, so an artifact's afterlife is planned before release', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Rhetoric
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Designing extractable claims for audiences, contexts, and possible distortion is fundamentally rhetorical invention and audience analysis.
Related originating lineages:
- Communication & Media Studies — Remix, circulation, gatekeeping, and context collapse materially shape the downstream-reuse model.
- Computer Science & Software Engineering — Reusable documentation and copyable code fragments supply concrete release and misuse cases.
- Human-Computer Interaction — Persona matrices and pre-release design risk mapping contribute the tabular artifact.
Review resolution: Both reviewers agree that rhetoric is primary. I retain communication_media_studies, human_computer_interaction, computer_science only as formative origin lineage(s), without treating every later application as an origin. cross_disciplinary_synthesis is appropriate because the exact artifact combines contributions from multiple professional lineages. Reach is multi_domain as a separate applicability judgment: it does not widen or narrow the recorded provenance. Encyclopedia synthesis is true because the exact generalized artifact is an encyclopedia-authored combination or refinement. The secondary differences are reconciled with no unresolved primary-provenance ambiguity.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] "The map is not the territory" — Alfred Korzybski's principle that a model is never identical to the reality it represents; a reuse matrix is a forecast of circulation, not circulation itself, and must be revised against what actually happens. ↩