Ten papers, in the order the argument was built.
Each one isolates a question and changes what the next question can be. Together they are the argument Puppeteer implements.
The Puppeteer Papers Series
The series does not begin by declaring a Puppet; it isolates the properties that make one possible.
That subject is the Puppet.
Performative in the Austinian sense: the act does something rather than merely describing something.
The interesting problem is whether populations of them can remain practical under concurrency, distribution, elasticity and changing topology.
Puppeteer is the distributed-systems substrate that makes populations of those subjects practical.
Many systems preserve the database state that results from a business operation. Puppeteer starts at the write path: the operation, its parameters and its checks are recorded as they happen.
The note asks what that changes for mapping, interoperability and the meaning that has to be reconstructed later.
Follow the argument through the papers.
What is a durable unit of state?
Foundational principle
The foundational principle: operation-centric encoding removes a representational defect shared across databases, DDD, REST and event sourcing.
Anti-Porous Architecture: A Unified Design Principle for CQRS + Actor + Event-Sourcing Systems
FOUNDATIONSARCHITECTURE
Precondition
Separating a program from its values makes it a durable, replayable unit of state — the precondition for compilation, caching and dense journaling.
Program–Value Separability: The Structural Precondition for Compilation, Caching and Dense Journaling in a DSL Runtime
PROGRAMVALUE
What becomes possible once that unit exists?
Consequence
Splitting an event into an immediate branch and a deferred branch — now and later consequences — makes eventual consistency opt-in.
Reactions and the Partition: Opt-In Eventual Consistency in Actor-Native Systems
CAUSALITYCONSISTENCY
Consequence
Recording cross-actor messages as program operations preserves continuity edge by edge, without orchestration.
Preserving Semantic Continuity Across Actors: A Tell-Based Approach Without Orchestration
PARTICIPANTSCONTINUITY
Unification
Deployment is replay, replication is sharing history, backup is copying the program, and offline operation is delayed replay — four operations, one journal.
The Journal as Substrate: Unifying Deployment, Replication, Backup and Offline Operation in Distributed Systems
REPLAYSUBSTRATE
What infrastructure burden comes from the conventional model?
Diagnostic, turned outward
A diagnostic typology for the stack layers that exist only to compensate for the underlying persistence model.
Most Infrastructure Layers Are Symptoms of the Persistence Model
PERSISTENCEINFRASTRUCTURE
Apply the typologyOperational implication
A journaled-program substrate makes the datacenter no longer a structural requirement of running production software.
After the Substrate: Building Software Without a Datacenter
INFRASTRUCTUREDEPLOYMENT
Who may assert what, and what survives a change of staging?
Authority
Separating the three authorities over an output — the domain, the actor and the assembler — removes assertions made beyond their warrant, so observers receive testimony instead of inference.
Inference without Authority: The Three Authorities That Govern an Output
AUTHORITYOUTPUT
Measured result
A domain is not its deployment. A staging — where it runs, how it is hosted, which client observes it — is built against the domain, while the domain references none of them.
5 stagings · 6 clients · 0 domain edits
Zero domain edits was shared by the comparison baseline. The architectural difference was where outward obligations and reconstitution lived.
Identity Precedes Staging: One Play, Many Stages
IDENTITYSTAGING
Put it on a host that movesOpen investigation
The subject becomes explicit
Executing a sequence consumes capabilities; it does not produce one. Assembly constitutes the composition itself as a verb of a subject — one recorded definition, and later invocations that restate nothing about how it was constituted.
The Assembled Verb: Repertoire, Assembly, and the Authorship of a Verb
ASSEMBLYCAPABILITY
From verb to actWorking draft
0AThe Assembled VerbA program acquires verbs of its own.
0BThe Enacted VerbThose verbs acquire a past.
0A made the verb a unit. 0B asks which exercises of that verb become acts of the subject — and therefore part of its history.
Counts measured on the engine’s own lab subjects, not on deployed ones. Not claimed: durable atomicity, entitlement, store integrity or agency.
The Enacted Verb: How a Subject Acquires a History of Its Own
Pre-deposit working draft — not yet deposited on Zenodo.
ADMISSIONHISTORY
Next question What makes one subject the same subject?
A system cannot safely conclude that nothing happened unless there is durable evidence that it actually checked.
A Puppet is waiting for a confirmation. The confirmation never arrives.
When Attention brings it back, the system has to tell these apart:
Absence becomes meaningful only when observation leaves evidence.
If any of this bears on what you are building, we would like to hear which part.
Start a Technical Conversation