Abstract Work¶
Core Idea¶
A content identity distinct from any of its concrete carriers — the play apart from any performance, the algorithm apart from any source file — held together by five roles: work, instances, an identity criterion, attribution, and lineage. The identity criterion is load-bearing: it decides which variations preserve the work and which fork a new one.
How would you explain it like I'm…
Same Song, Many Ways
Think of your favorite song. It's still the same song whether you hear it on the radio, sing it yourself, or play it on a toy piano. The song isn't any one of those — it's the thing that stays the same no matter how you play it. The 'work' is the song; each way you hear it is just one copy of it.
The Story Behind The Copies
Abstract Work means treating the IDEA of something as separate from any single copy of it. A story like Cinderella is the same story whether it's a book, a movie, or your grandma telling it out loud — the story is the 'work,' and each book or movie is one 'instance' of it. The work is what stays the same when you swap one copy for another; the copies are what change while the work stays put. To make this work you need a rule for what counts as 'the same work': a translation of Cinderella is still Cinderella, but a totally different story isn't. That rule is the important part, because it decides which changes keep it the same work and which create a brand-new one.
The Work Versus Its Copies
Abstract Work is the commitment to recognize a content identity that's distinct from any of its concrete carriers — the play apart from any performance, the symphony apart from any recording, the recipe apart from any meal. The work is what persists when you swap one carrier for another; the carriers are what change while the work stays the same. Five roles travel together: the work (the abstract identity), its instances (concrete realizations), the identity criterion (what counts as the same work versus a different one — same content, allowable variation, required faithfulness), the attribution (who produced the work, often different from who produced a given copy), and the lineage (which revisions and editions count as updates versus a fork into a new work). Drawing the line wrong is a real failure: collapse it and you can't even ask whether two performances are of the same piece; over-multiply it and every reprint becomes its own work and lineage turns to noise. The identity criterion is the load-bearing piece — it does the work of deciding which variations preserve the work.
Abstract work is the structural commitment to recognize a content identity distinct from any of its concrete carriers — the play apart from any performance, the symphony apart from any recording, the algorithm apart from any source file, the statute apart from any printed copy. The work is what persists when one carrier is swapped for another; the carriers are what change while the work stays the same. Five roles travel together: the work, the abstract identity itself; the instances, its concrete realizations; the identity criterion, specifying what counts as the same work across instances versus a different work (same content, allowable variation, requisite faithfulness); the attribution, who produced the work, often distinct from who produced any given instance; and the lineage, the revisions and editions that count as updates to the same work versus those that fork a new one. The pattern is forced wherever the same content is realized in multiple carriers, and drawing the line wrong is recognizable failure: collapse the distinction and you cannot ask whether two performances are of the same piece or whether a translation is of the same novel; over-multiply it and every printing becomes its own work while lineage shatters into noise. The structural force is the separation of identity from carrier, which lets operations range over carriers — 'any version of this,' 'the canonical form of,' 'all renditions of that' — queries unaskable in a system that can refer only to carriers. The identity criterion is load-bearing: a schema that omits it has not earned the work level. The skeleton is substrate-neutral even though 'work' is most at home among cultural artifacts; the bare type-token distinction is its structural cousin.
Broad Use¶
- Bibliographic systems: the work–expression–manifestation–item hierarchy lets a catalog answer "any version of this?" rather than only "this exact edition?"
- Music: the composition is the work; performances, recordings, and score editions are instances, and royalty law turns on the distinction.
- Software: the program is the work; a binary build, a running process, and a deployed container are instances.
- Engineering and design: a design or type-certificate is the work; manufactured units are instances, so recalls target the work and serial-tracking the instances.
- Law: a statute is the work; printed copies and database renderings are instances — the work has legal effect, the instances are renditions.
- Recipes and procedures: the recipe or protocol is the work; each meal or each run is an instance.
Clarity¶
Lets a system ask what travels under the same name across carriers and what changes — a question unaskable where one can refer only to the carriers themselves.
Manages Complexity¶
Gives operations a correct altitude: range over carriers for citation and recall, drill to a carrier for audit and reproduction, instead of treating every copy as sui generis.
Abstract Reasoning¶
Predicts a system's pathologies from how it draws the line: too loose collapses distinct works, too tight shatters lineage — the same diagnosis whether the substrate is music, code, or sculpture.
Knowledge Transfer¶
- Bibliography to software: a novel in several translations, editions, and copies maps role-for-role onto a program in several versions, builds, and installed instances.
- Cataloguing to release engineering: "is a translation a new work?" and "is a fork a new project?" are the same identity-criterion choice, so a fix in one medium illuminates the other.
Example¶
A repository that conflates the program with its build artifacts cannot reproduce a reported bug, because the bug report cites the work while reproduction requires the exact instance that was never made addressable.
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
- Abstract Work presupposes, typical Abstraction — The file: abstract_work is the OUTPUT of an abstraction operation when the result is a content-identity carried across swappable carriers — presupposes abstraction but adds the load-bearing instance-set + identity-criterion that abstraction-in-general lacks. The 0.93 similarity is parent-to-product.
Path to root: Abstract Work → Abstraction
Not to Be Confused With¶
- Abstract Work is not Abstraction in general because abstract work is the specific output of abstraction when the result is a content-identity carried across swappable carriers, adding an instance set and identity criterion that abstraction need not yield.
- Abstract Work is not Versioning because versioning orders revisions inside an already-drawn identity whereas abstract work is the prior commitment that owns the fork-versus-update decision.
- Abstract Work is not Representation because a representation stands for something across a referential gap whereas a work's instances are realizations of it, not signs pointing at it.