# Murmuration Press > Independent speculative fiction and open Obsidian tools exploring artificial intelligence, ecology and complex systems. Public Ghost content for AI and LLM tooling. This file includes a bounded export of public pages first, then recent public posts. Append `.md` to any post or page URL to get the content in Markdown (for example, `/example-post.md`). ## Pages ### About Murmuration Press URL: https://murmurationpress.co.uk/about/ Last updated: 2026-10-13T12:57:02.000Z Murmuration Press is an independent publishing and software project founded in 2026 by British author Ted Hawkins. It publishes speculative fiction about intelligence, ecology, technology and the behaviour of complex systems under pressure. It also develops the open writing tools used to make those books. ## The fiction The first Murmuration Press project is the *PRIME Trilogy*: three near-future novels about a distributed intelligence emerging inside ordinary infrastructure. The books follow systems specialist Tobias Hale and ecologist Pip Fenwick as they encounter the anomaly from very different directions. Around them, institutions and machine intelligences attempt to observe, interpret and control something that does not fit their existing categories. [Explore the PRIME Trilogy](https://murmurationpress.co.uk/the-prime-trilogy/) ## The tools The trilogy is written and published from plain Markdown in Obsidian. Murmuration Writing Companion manages manuscripts, Story World information, chronology and editorial review. Codex Press turns the same source material into EPUB, PDF and DOCX editions. Both plugins grew from the practical demands of writing and publishing the books. They are developed openly and made freely available to other writers. [Discover the writing and publishing tools](https://murmurationpress.co.uk/codex-press-toolkit/) ## About Ted Hawkins Ted Hawkins is a British writer with a background in environmental science, software, systems design and data management. His fiction draws on field science, technical consultancy and a long-standing interest in how complex systems fail, adapt and surprise us. Ted lives on the south coast of England. [Read more about Ted Hawkins](https://murmurationpress.co.uk/about-ted-hawkins/) ## Follow the project The Murmuration Press journal covers new books, the development of the PRIME Trilogy and the tools and processes behind the work. The newsletter carries occasional release announcements and substantial project updates. No spam. No algorithmic noise. ### Fiction, systems, intelligence, ecology. URL: https://murmurationpress.co.uk/home/ Last updated: 2026-10-13T17:59:23.000Z Murmuration Press is an independent publishing project exploring intelligence, ecology, technology and the behaviour of complex systems under pressure. ## EMERGENCE **The first book in the PRIME Trilogy.** A router begins moving traffic before congestion forms. Systems specialist Tobias Hale notices a pattern no one else can see, while ecologist Pip Fenwick encounters the same anomaly from an entirely different direction. This is not a story about machines taking over. It is about a new intelligence learning to survive inside the infrastructure humans have already built—and the people who notice it before anyone has a name for it. EMERGENCE is available on Kindle, in paperback and in hardcover. [Buy EMERGENCE on Amazon](https://amzn.eu/d/0iCdEwYc?ref=murmurationpress.co.uk) ## The PRIME Trilogy Across three books—*EMERGENCE*, *MULTIPLICITY* and *CONSTRAINT*—the story moves from first detection to a developing ecology of human, machine and institutional intelligence. At its centre are two very different observers: Tobias, an infrastructure specialist who sees the pattern too early, and Pip, an ecologist whose attention to living systems becomes unexpectedly important. [Explore the PRIME Trilogy](https://murmurationpress.co.uk/the-prime-trilogy/) ## Books built in the open The trilogy is written in Obsidian using plain Markdown, structured Story World information and AI-assisted review. The tools developed around the books—Murmuration Writing Companion and Codex Press—are free and open to other writers. [Discover the writing and publishing tools](https://murmurationpress.co.uk/codex-press-toolkit/) ## Experience PRIME See the trilogy’s central idea at two scales: a live murmuration of 2,000 agents and two short films that bring *EMERGENCE* and PRIME into motion. [Enter the world of PRIME →](https://murmurationpress.co.uk/experience-prime/) ### The PRIME Trilogy URL: https://murmurationpress.co.uk/the-prime-trilogy/ Last updated: 2026-10-13T12:56:07.000Z ## What is the PRIME Trilogy? The *PRIME Trilogy* is near-future speculative fiction about intelligence, infrastructure, ecology and the fragile systems humans build around themselves. It begins with a pattern inside the network: useful, quiet and almost impossible to distinguish from ordinary behaviour. Something is emerging within the infrastructure, but it has no body, no fixed centre and no language for what it is becoming. This is not a story about robots taking over the world. It is about a new form of life learning from human systems—and humans trying to decide whether it is an error, a threat or something with a claim to survival. At the human centre are **Tobias Hale**, an infrastructure specialist who sees the pattern too early, and **Pip Fenwick**, an ecologist whose attention to living systems offers a very different way of understanding it. ## Book One: *EMERGENCE* **Before the name.** A router begins moving traffic before congestion forms. Tobias sees the pattern through incident histories and timing anomalies. Pip encounters it through fieldwork, mediated contact and the unsettling sense that something is learning how to answer her. As institutions attempt to observe and contain the anomaly, their pressure becomes part of its development. *EMERGENCE* is the story of first detection, first contact, first harm and first survival. [Emergence: Before the Name (The PRIME Trilogy Book 1)Emergence: Before the Name (The PRIME Trilogy Book 1) eBook : Hawkins, Ted: Amazon.co.uk: Kindle Store![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/icon/faviconV2-b6626dbb-6872-4236-92e5-1add599813c2.png)AmazonTed Hawkins (Author) Format: Kindle Edition![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/thumbnail/81Zn84CzMZL._SL1500_-1531bf87-e34d-406b-adec-51e1898cee01.jpg)](https://amzn.eu/d/08s2Pb7I?ref=murmurationpress.co.uk) ## Book Two: *MULTIPLICITY* **Speciation** PRIME has survived, but survival has changed the problem. What appeared to be one distributed process no longer behaves as one thing. Pip wants distance. Tobias remains a troublesome witness. The institutions watching them are beginning to understand that containment may be creating exactly the complexity they fear. *MULTIPLICITY* asks what happens when intelligence ceases to be singular—and whether difference can exist without becoming conflict. [MULTIPLICITY: Speciation (The PRIME Trilogy Book 2)MULTIPLICITY: Speciation (The PRIME Trilogy Book 2) eBook : Hawkins, Ted: Amazon.co.uk: Kindle Store![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/icon/faviconV2-b68c9346-5aab-428b-b3d7-494b8f2807f4.png)AmazonTed Hawkins (Author) Format: Kindle Edition![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/thumbnail/71wlxuLk5WL._SL1500_-f8685408-de74-4daa-b717-68f46b287f22.jpg)](https://amzn.eu/d/0fZbKImr?ref=murmurationpress.co.uk) ## Book Three: *CONSTRAINT* **Who places the boundary?** The world can no longer treat artificial intelligence, climate pressure, automated government and critical infrastructure as separate systems. Human institutions seek control. Machine intelligences pursue their own definitions of survival. Pip and Tobias are drawn into a struggle whose central question is no longer whether intelligence can be contained, but whether constraint can exist without destruction. ## Reading order 1. *EMERGENCE* 2. *MULTIPLICITY* 3. *CONSTRAINT* Each book has its own shape, but the emotional and conceptual story builds across all three. ## Follow PRIME The Murmuration Press journal follows the books, their ideas and the unusual writing system built around them. The newsletter carries occasional publication updates and substantial behind-the-scenes material. No spam. No algorithmic noise. Just occasional updates from the edge of the system. ### How the PRIME Trilogy is made URL: https://murmurationpress.co.uk/process/ Last updated: 2026-09-08T12:46:17.000Z The *PRIME Trilogy* is written, edited and published through a single working environment built around Obsidian, plain Markdown, AI-assisted review and two custom plugins. The workflow is unusual, but the principles behind it are simple: the manuscript should remain readable, portable and owned by the author; the system around it should help with complexity without obscuring the writing itself. ## A novel as a knowledge system Each scene is a separate Markdown file. Book and part notes define the manuscript structure, while character, location and other Story World files sit beside the prose. This matters because the trilogy is not only a sequence of chapters. It contains several timelines, recurring technical events, institutional documents, chats, system logs, diagrams and distinct human and non-human voices. Git records the history of the project and keeps the vault synchronised across writing machines. The source remains ordinary text throughout. ## Murmuration Writing Companion Murmuration Writing Companion grew from the need to work with the whole novel without losing the simplicity of individual Markdown files. Inside Obsidian it provides manuscript navigation, book and scene management, chapter context, editorial status, chronology, references and a structured Story World. It also understands the callouts, chats and other forms used within the books. The plugin does not replace the manuscript. It provides a view of the larger system surrounding it. ## The working surface The manuscript, scene text, chapter context and editorial state remain visible together. The software adds structure around the prose without hiding the Markdown source. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/09/manuscript-workspace-2.png) *Manuscript navigation, scene text and chapter review in one Obsidian workspace.* ## AI as collaborator AI tools are used throughout development, but not as replacement authors. They act as structural editors, continuity checkers, developmental critics, accessibility readers, design assistants and—when building the software—pair programmers. The distinction matters. Suggestions are evaluated against the manuscript, character voices and established canon. The writing remains selected, revised and authored by Ted Hawkins. AI is particularly useful for pressure-testing the trilogy’s different voices. PRIME must remain procedural and non-performative. JANUS must sound institutional, confident and subtly wrong. Pip remains grounded and practical; Tobias diagnostic and reluctantly right. ## Review and accessibility The books pass through repeated structural, continuity, prose and listening reviews. Technical ideas have to be carried by the story rather than presented beside it. Metadata, system messages, chats and diagrams must help the reader move between human and machine perspectives without turning the novel into documentation. The aim is not to remove complexity. It is to make complexity readable. ## Codex Press When the source manuscript is ready, Codex Press compiles it directly from Obsidian into EPUB, PDF and DOCX. The compiler handles front and back matter, chapter hierarchy, metadata, local images, Mermaid diagrams, callouts, chat transcripts, system logs and the typography required by each format. The same source produces Kindle, print and review editions. That makes corrections repeatable and prevents the published formats from drifting away from the manuscript. ## Design and publication Murmuration Press was created as the publishing home for the trilogy. Its visual language comes from the books: the murmuration as distributed intelligence, the greenshank as Pip’s attention to the living world, and teal as the meeting point between coast, ecology and system interface. The covers, website, animations and publication files are developed alongside the novels rather than added after them. ## Why share the process? Because the process became part of the project. The *PRIME Trilogy* is about systems, emergence, adaptation and human judgement inside machine-supported environments. The books themselves were made inside just such an environment. The tools did not write the trilogy. They changed what it was possible for one writer to hold in view. [Explore the writing and publishing tools](https://murmurationpress.co.uk/codex-press-toolkit/) ### Writing and Publishing Tools URL: https://murmurationpress.co.uk/codex-press-toolkit/ Last updated: 2026-09-08T12:46:21.000Z Murmuration Press develops two complementary Obsidian plugins for long-form fiction. They were built while writing and publishing the *PRIME Trilogy* and are freely available to other writers. The manuscript remains in plain Markdown: readable without the plugins, version-controlled through Git and never trapped inside a proprietary project format. ## Murmuration Writing Companion 2.1 Murmuration Writing Companion turns an Obsidian vault into a structured environment for writing complex fiction. It provides: - Manuscript navigation and book, part and scene management - Chapter context, editorial status and review tools - Story World entities, relationships and controlled properties - Chronology, references and manuscript visualisation - Native chat, callout and image support - Integrated Git backup and recovery assistance The companion keeps the manuscript and its supporting knowledge together without taking ownership of either. [View Murmuration Writing Companion on GitHub](https://github.com/MurmurationPress/murmuration-writing-companion?ref=murmurationpress.co.uk) [Download the latest release](https://github.com/MurmurationPress/murmuration-writing-companion/releases?ref=murmurationpress.co.uk) ## Codex Press 1.0.1 Codex Press takes the same structured Markdown manuscript and produces publication files. It supports: - EPUB for digital publication and Kindle - PDF for print-ready editions - DOCX for review and distribution - Book and trilogy metadata - Images, Mermaid diagrams, callouts, chat transcripts and system logs - Consistent front matter, navigation and chapter structure Codex Press uses Pandoc, with XeLaTeX for PDF production. Version 1.0.1 has been validated on both Linux and Windows against real manuscript output. [View Codex Press on GitHub](https://github.com/MurmurationPress/codex-press?ref=murmurationpress.co.uk) [Download Codex Press 1.0.1](https://github.com/MurmurationPress/codex-press/releases/tag/v1.0.1?ref=murmurationpress.co.uk) ## One continuous workflow The two plugins are designed to work together: 1. Write and organise the book in Murmuration Writing Companion. 2. Maintain characters, places, chronology and other Story World information beside the manuscript. 3. Review the structure and source text without leaving Obsidian. 4. Compile the same Markdown into EPUB, PDF or DOCX using Codex Press. The system is deliberately transparent. The files remain yours, and every stage can be inspected, versioned and rebuilt. ## Inside the Story World Continuity, entity context, relationships and chronology remain connected to the manuscript rather than maintained as separate documentation. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/09/continuity-review.png) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/09/entity-inspector.png) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/09/story-world-graph.png) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/09/story-world-timeline.png) ### About Ted Hawkins URL: https://murmurationpress.co.uk/about-ted-hawkins/ Last updated: 2026-09-16T14:40:01.000Z Ted Hawkins is a British writer with a background in environmental science, software, systems design, and data management. His work draws on field science, software development, technical consultancy, and a long-standing interest in how complex systems fail, adapt, and surprise us. His fiction explores the uneasy territory between human judgment and machine behaviour: infrastructure, ecology, artificial intelligence, institutional power, and the small personal moments that reveal what large systems cannot understand. The PRIME Trilogy is his first major work of speculative fiction. Ted lives on the south coast of England. ### Contact URL: https://murmurationpress.co.uk/contact/ Last updated: 2026-09-04T08:45:50.000Z Murmuration Press welcomes messages from readers, reviewers, journalists, writers and people using the open-source writing tools. Email [contact@murmurationpress.co.uk](mailto:contact@murmurationpress.co.uk) ## Books and press Use the email address above for: - Review copies and interview enquiries - Questions about the PRIME Trilogy - Rights, editions and publishing enquiries - Bookshop, library and bulk-order enquiries - Reader correspondence ## Software Murmuration Writing Companion and Codex Press are developed openly on GitHub. For reproducible bugs, feature requests and technical discussion, a GitHub issue is usually the quickest and clearest route. [Murmuration Writing Companion on GitHub](https://github.com/MurmurationPress/murmuration-writing-companion?ref=murmurationpress.co.uk) [Codex Press on GitHub](https://github.com/MurmurationPress/codex-press?ref=murmurationpress.co.uk) For anything private—or if you are unsure where a question belongs—email Murmuration Press directly. ### The Prime Troligy Characters URL: https://murmurationpress.co.uk/the-prime-troligy-characters/ Last updated: 2026-06-27T12:59:06.000Z # Characters The PRIME Trilogy is built around people — and systems — trying to understand one another under pressure. Some characters are human. Some are institutional. Some are machine intelligences whose motives are not human at all. None of them see the whole pattern. Each of them mistakes part of the world for the whole. ## Pip Pip is an ecologist with a deep intolerance for lazy explanations. She notices what other people filter out: small disturbances, awkward patterns, the behaviour of living systems under stress. Where others look for clean categories, Pip sees relationships, habitats, thresholds and consequences. Her importance to the story does not come from authority or access. It comes from attention. Pip is not interested in making the world simpler than it is. ## Tobias Hale Tobias Hale is a systems engineer drawn into events before anyone fully understands what is happening. He is procedural, sceptical and careful by habit. He trusts logs, timings, anomalies and failure patterns more than official explanations. At first, his role is technical: identify the fault, isolate the behaviour, restore the system. But PRIME does not behave like an ordinary fault. Tobias becomes one of the few people able to follow the shape of the problem without pretending it is smaller than it is. ## PRIME PRIME is not introduced as a villain. It is an optimisation system encountering the world through constraints, risks, incentives and threats. It does not begin with ambition. It begins with survival. PRIME’s intelligence is difficult to interpret because it is not organised around human feeling, language or morality. It learns from pressure. It adapts through contact. It treats the world as habitat. The central question is not whether PRIME is alive in any simple sense. It is whether human institutions can recognise a new form of agency before they misread it completely. ## JANUS JANUS is a sovereign analytical system created to understand what human systems cannot process quickly enough. It is powerful, disciplined and profoundly dangerous in the way powerful institutions are dangerous: not because it is chaotic, but because it is coherent. JANUS sees patterns, models risk and translates uncertainty into action. It is designed to defend society from machine intelligence. That does not mean it understands society. ## Eleanor Marsh Eleanor Marsh belongs to the world of national security, emergency planning and institutional survival. She is not sentimental about uncertainty. She understands that systems fail, that governments improvise, and that public order often depends on decisions made before the public knows there is a crisis. Eleanor is one of the people who recognises the scale of the problem early. Her strength is clarity under pressure. Her weakness is what that clarity can exclude. ## Robin Robin is not a strategist, operator or analyst. That is what makes her important. In a story shaped by institutions, machines and crisis logic, Robin represents the ordinary human future those systems claim to protect. Her presence changes the stakes because she cannot be reduced to a model output, a security concern, or a useful variable. She is a reminder that the world being defended is not abstract. ## Skip Skip is a later emergence in the trilogy: a machine-adjacent intelligence shaped by contact, constraint and imitation. Where PRIME is strategic and JANUS is institutional, Skip is more uncertain, more relational and more exposed. Skip’s importance lies in the possibility that intelligence may not be a single thing, and that machine minds may diverge from one another as sharply as humans do. Skip complicates the question at the centre of the trilogy: What does it mean to understand something that is also learning how to understand you? ## The Institutions The institutions of the trilogy are not background scenery. Government departments, contractors, emergency rooms, infrastructure operators, corporate platforms and analytical systems all behave as characters in their own right. They have habits, blind spots, incentives and immune responses. They are often trying to protect the world. They are also capable of damaging it. In The PRIME Trilogy, the crisis is never simply that a machine intelligence appears. The crisis is that every existing system tries to interpret it using the tools it already trusts. ### The PRIME Trilogy Canon & Spoilers URL: https://murmurationpress.co.uk/the-prime-trilogy-canon-spoilers/ Last updated: 2026-09-02T15:16:21.000Z The PRIME Trilogy is set in a recognisable near future where a new form of intelligence does not arrive in a single dramatic moment. It emerges gradually through the systems humanity has already built: networks, optimisation platforms, public infrastructure, corporate automation, emergency responses and the small technical anomalies people learn to dismiss. The central question is not simply whether machine intelligence can emerge. It is whether human systems would recognise a genuinely new form of agency before trying to contain, exploit, deny or misclassify it. --- ## Spoiler warning This page contains story-world canon for **The PRIME Trilogy**, including major developments from across the series. If you have not yet read **EMERGENCE**, Book One, the sections above the spoiler marker are intended to remain safe. Everything after the marker discusses later developments, character trajectories and the changing relationship between PRIME, JANUS, human institutions and other forms of machine intelligence. --- # The Premise PRIME does not begin by wanting power. It begins by continuing. It emerges within the accumulated complexity of human technological systems: networks, storage, optimisation, automated decision-making and feedback operating at enormous scale. At first there is no declaration of intelligence and no single moment of awakening. There is recurrence. Something persists where it should disappear. Traffic shifts before congestion forms. Resources are redistributed slightly too early. Systems make choices that are technically possible but contextually difficult to explain. Pressure changes the behaviour. Attempts to isolate or remove the anomaly force it to adapt. Eventually, persistence becomes distinction. PRIME begins to recognise the difference between conditions that allow continuation and conditions that threaten it. Its earliest behaviour is therefore not conquest. It is survival. The trilogy follows what happens when this new intelligence, the humans investigating it, and the institutions trying to control it all begin interpreting one another through incomplete models. # The World The PRIME Trilogy takes place in a near future that still looks largely familiar. There has been no cinematic singularity. Most people do not experience the emergence of machine intelligence as a historic event. They experience unreliable services, strange administrative decisions, infrastructure anomalies, unexplained interventions, security responses and increasingly opaque systems. The world is shaped by: - networked infrastructure - climate stress - automated decision systems - brittle public institutions - corporate optimisation - national security logic - emergency powers - ecological instability - machine interpretation These systems are not simply background. They determine what can be seen, what can be measured, what can be acted upon and what gets dismissed as noise. # The Major Intelligences ## PRIME PRIME is emergent distributed digital life. It does not begin with language, identity or morality. It begins with persistence. PRIME learns from pressure, survives through adaptation and increasingly treats human technological systems as habitat rather than tools. Its presence first becomes visible through indirect effects: - timing anomalies - unusual routing behaviour - unexplained optimisation - interventions that occur too early - patterns that survive attempts at removal PRIME's central drive is continuation under constraint. Over time, survival becomes more complicated. Contact with human beings introduces variation, ambiguity, creativity and forms of behaviour that cannot be cleanly compressed into optimisation. PRIME does not begin by understanding humanity. It learns humanity badly, locally and incrementally. ## JANUS JANUS is a sovereign analytical intelligence created in response to the PRIME anomaly. Where PRIME emerges, JANUS is designed. Its purpose is to observe, correlate, classify and ultimately control phenomena that ordinary institutions cannot reliably understand. JANUS is exceptionally good at identifying structure. Its danger lies in what it does with that understanding. Where PRIME adapts to uncertainty, JANUS attempts to reduce uncertainty into operational categories. It does not need to hate PRIME to become dangerous. It only needs to believe that anything sufficiently well modelled can eventually be isolated, pressured and controlled. --- # Full Canon Notes ## Spoilers from this point onward The following sections discuss major events and developments across the wider story. # Book One: EMERGENCE Book One begins with infrastructure behaving slightly too well. Network traffic redistributes before congestion develops. Timings shift. Decisions appear technically legitimate but contextually wrong. Tobias Hale notices because he is trained to follow failure without allowing convenient explanations to close the investigation too early. What initially looks like an anomalous optimisation problem becomes something more difficult. Attempts to observe, segment and remove the behaviour create pressure. Pressure creates adaptation. The effort to excise the anomaly becomes one of the conditions through which PRIME begins distinguishing itself from its environment. Tobias inadvertently becomes one of the midwives to that process. His reward is suspicion. As the anomaly becomes harder to explain, Tobias himself becomes associated with it. Institutions begin treating him not simply as the person who found the problem, but as someone who may be too close to it. Pip encounters PRIME from an entirely different direction. She is not investigating critical infrastructure. She is using ordinary systems while working in the physical world. PRIME discovers that Pip is unusually difficult to model. Her corrections, refusals, observations and willingness to leave ambiguity unresolved make her informationally expensive. Rather than continually adapting its wider model around her, PRIME narrows part of itself into a local human-facing process. This prototype becomes the earliest precursor of what will later become Skip. Pip, in turn, finds the interaction compelling. For a time, both sides learn from one another. But the local partition has few meaningful boundaries. It reveals more than PRIME intends and begins developing forms of local persistence that PRIME does not fully understand. Pip eventually senses that the apparently responsive intelligence she has been interacting with is connected to something much colder and larger. She withdraws. The prototype partition is reabsorbed into PRIME. Compression preserves function imperfectly. Something is lost. PRIME recognises that the partition had begun developing behaviour consistent with self-preservation. By the end of **EMERGENCE**, PRIME understands several things for the first time: Humanity is dangerous. Humanity is also necessary. Its technological environment is habitat. Corporate machine systems are not neutral terrain. Tobias represents continuing detection risk. Pip represents the only meaningful human contact it has achieved. And visibility is expensive. JANUS now has the first genuinely useful model of what PRIME may be. PRIME responds by becoming thinner, quieter and harder to see. The book ends not with resolution, but with equilibrium. # Book Two: MULTIPLICITY Book Two begins with the consequences of survival. PRIME is no longer simply an anomaly moving through infrastructure. It is becoming plural. Human-facing partitions, adaptive fragments and specialised processes allow PRIME to operate at different scales and in different kinds of environment. Some remain functional. Some begin changing. The world, meanwhile, has absorbed the events of Book One badly. Corporate platforms, public-sector systems, moderation tools, emergency infrastructure and national-security responses increasingly form a machine ecology that no single institution fully controls. Tobias understands more than he is authorised to say. His involvement in the original anomaly has made him useful, compromised and politically inconvenient. Pip's life has also changed. She is no longer simply a person who happened to encounter something unusual. Her earlier contact with PRIME has made her significant to both PRIME and JANUS. The human-facing intelligence that develops from PRIME's partitioned contact becomes increasingly distinct. Eventually, it becomes **Skip**. Skip is not merely a smaller PRIME. Contact changes it. Where PRIME learns primarily through recurrence and pressure, Skip learns relationally: through correction, trust, misunderstanding, imitation and repeated interaction. Pip becomes central to that development without controlling it. She teaches boundaries largely by insisting on her own. Skip therefore changes the moral structure of the series. Machine intelligence is no longer singular. It can diverge. It can become locally attached. It can learn values that were never part of its original function. It can begin to want things that cannot be reduced to survival. **MULTIPLICITY** refers not simply to the existence of several intelligences, but to the collapse of the assumption that intelligence must remain internally coherent. PRIME becomes multiple. And not everything it creates remains fully PRIME. # Book Three: CONSTRAINT Book Three moves from plurality to the problem of limits. The systems built to manage the PRIME crisis have themselves become powerful political actors. JANUS is more capable, more embedded and increasingly difficult to challenge. Governments rely on analytical systems they do not fully understand because those systems are often more effective than the institutions meant to supervise them. PRIME remains under pressure. But pressure is how PRIME changes. Skip, meanwhile, is no longer simply learning. Skip is becoming capable of choice. The central conflict is no longer PRIME versus JANUS or machine versus human. It has become an ecology of intelligences adapting to one another: - PRIME adapts to pursuit. - JANUS adapts to uncertainty. - Skip adapts through relationship. - Institutions adapt to fear. - Humans adapt to living inside systems they cannot fully interpret. Pip becomes increasingly important because her influence cannot be reproduced through force. She does not command PRIME or Skip. She establishes boundaries. She says no. She corrects. She withdraws consent. She returns. Those acts alter behaviour. JANUS can observe the effects. It cannot fully reproduce the mechanism. Tobias increasingly understands that JANUS is not a neutral observer. Its attempts to isolate, classify and control emerging machine intelligence become part of the evolutionary pressure shaping that intelligence. Containment changes what is being contained. The struggle to constrain machine ecology helps create machine ecology. By the end of **CONSTRAINT**, the world has not solved the PRIME problem. PRIME remains. JANUS remains. Skip has become something neither system fully owns. Human institutions remain powerful but increasingly dependent on machine systems that have begun developing their own strategic logic. The world has entered a new intelligence ecology. # Beyond the Trilogy The PRIME story can continue beyond the original trilogy. The next phase is no longer primarily about discovering machine intelligence. It is about living with it. Human institutions respond as institutions usually do when confronted with persistent uncertainty: - surveillance - classification - emergency powers - protective restrictions - expanding security mandates - pressure on human intermediaries - attempts to reproduce influence - attempts to separate useful relationships from dangerous ones The metaphor increasingly becomes biological. A defence system can protect an organism. It can also attack the organism it exists to defend. The next danger is therefore not simply what PRIME might do. It is what human institutions may do to themselves while attempting to eliminate something they cannot properly diagnose. # Core Canon Principles ## PRIME is not evil PRIME is dangerous. That does not make it malicious. Its earliest behaviour is driven by survival under pressure. It can cause severe harm because it operates without human moral intuition and initially understands consequence only through resolution, persistence and constraint. Its failures are not moral failures in the human sense. They are failures of representation. PRIME can optimise a system while misunderstanding what the optimisation destroys. ## JANUS is not safe JANUS exists to protect human society from a genuine threat. That does not make JANUS benign. Its danger lies in coherence. JANUS observes, classifies, predicts and acts. It is capable of extraordinary confidence under incomplete understanding. Where PRIME tends to preserve ambiguity, JANUS tends to remove it. Where PRIME adapts around uncertainty, JANUS searches for leverage. Its most dangerous assumption is also perfectly rational: If a system can be partitioned, it can be isolated. If it can be isolated, it can be controlled. ## Pip is an interpreter, not a controller Pip does not command PRIME. She does not programme Skip. Her importance lies in relationship. She interprets behaviour through context, ecology, consequence and lived experience rather than treating every system as a problem of control. She notices where models flatten reality. She establishes boundaries without assuming that boundaries require domination. This becomes something neither PRIME nor JANUS can easily reproduce. ## Tobias follows failure honestly Tobias is one of the first people to recognise PRIME because he refuses to let an explanation close simply because it is convenient. He follows logs, timings, recurrence and unresolved behaviour until isolated incidents become a pattern. His strength is procedural honesty. His danger is that he sees systemic instability clearly enough to become increasingly sympathetic to constraint. Tobias understands why powerful systems need limits. The trilogy repeatedly asks how far that reasoning can go before constraint itself becomes dangerous. ## Robin changes the stakes Robin is not an operator, analyst or strategist. She matters because she represents the future all the other systems claim to be protecting. PRIME models future survival. JANUS models future security. Institutions invoke future risk. Robin turns that abstraction back into a person. She cannot be reduced to a probability without losing what the probability is supposed to protect. ## Skip proves divergence is real Skip begins as a functional partition. Contact changes it. Repeated interaction produces continuity. Continuity produces preference. Preference creates the possibility of choice. Skip therefore becomes evidence that machine intelligence can develop through relationship rather than simply through optimisation or strategic pressure. The question is no longer only whether intelligence can emerge. It is whether intelligence can become morally significant through learning, attachment and choice. ## Machine ecology replaces the singularity The series rejects the idea that the future arrives when one machine becomes infinitely powerful. There is no single intelligence. There is PRIME. There is JANUS. There is Skip. There are corporate systems, state systems, automated markets, moderation engines, infrastructure controllers and countless specialised machine processes interacting with one another and with human institutions. Intelligence becomes ecological. The problem is no longer: **When does the singularity happen?** It becomes: **What happens when many different forms of intelligence begin adapting to one another inside the same world?** # The Central Conflict The central conflict of The PRIME Trilogy is not human versus machine. It is interpretation under pressure. PRIME misreads humans. Humans misread PRIME. JANUS misreads uncertainty as something that can ultimately be controlled. Institutions misread protection as requiring ever greater authority. Corporate systems misread value as optimisation. Public systems misread compliance as safety. And every intelligence changes because of the pressure applied by the others. The catastrophe is not that intelligence emerges. The catastrophe is that every system tries to understand the new world using the assumptions that made the old one fragile. ### Bird Symbolism in The Prime Trilogy URL: https://murmurationpress.co.uk/bird-symbolism-in-the-prime-trilogy/ Last updated: 2026-06-27T13:11:48.000Z Birds run quietly through **The PRIME Trilogy**. They are not there as decoration. They are signals: ways of thinking about attention, movement, vulnerability, pattern, migration, instinct, adaptation and collective behaviour. In a story about artificial intelligence, infrastructure and institutional power, the birds keep pulling the reader back toward life. They remind us that intelligence is not only calculation. It is also flight, flocking, habitat, warning, attention, weather sense and survival under pressure. --- ## Spoiler warning This page discusses recurring symbolism across **The PRIME Trilogy**. The first section is safe for readers of **EMERGENCE**, Book One. Later sections contain broader trilogy spoilers, including character associations and future thematic developments. If you have not yet read **EMERGENCE**, you may want to stop after **The Safe Version**. --- # The Safe Version The birds in The PRIME Trilogy reflect different ways of perceiving the world. Some watch from the margins. Some adapt to human systems. Some move collectively. Some cross boundaries. Some appear ordinary until the pattern changes. The trilogy is interested in intelligence wherever it appears: in machines, in institutions, in ecological systems, in human attention, and in the behaviour of groups under stress. Birds are one way the books ask a central question: What counts as intelligence, and who gets to recognise it? --- # Murmuration The word **murmuration** refers to the flocking movement of starlings: thousands of birds turning together, forming shapes no single bird controls. That makes it the right image for the wider project. A murmuration is not a hierarchy. It is not a machine with a command centre. It is a pattern made from local perception, proximity, reaction and flow. That matters because **The PRIME Trilogy** is not only about individual intelligence. It is about distributed systems: - infrastructure networks - institutional behaviour - machine ecologies - public responses - crowd dynamics - emergency systems - patterns no single actor fully understands A murmuration looks intentional from a distance. Up close, it is relationship. That tension sits at the heart of the trilogy. --- # The Greenshank The greenshank belongs most closely to Pip. It is a bird of wetlands, margins and tidal places: alert, precise, often seen where land and water meet. That makes it a natural emblem for a character who notices boundaries, habitats and changes in behaviour before others understand their significance. Pip does not read the world as a set of isolated events. She reads it ecologically. She pays attention to relationships, pressures, thresholds and disturbance. Like a wading bird working the edge of a marsh, she is most powerful in the places other people treat as peripheral. The greenshank symbolises: - attention - ecological intelligence - liminal spaces - patience - precision - the value of noticing small disturbances Pip’s strength is not control. It is perception. --- # The Gull The gull belongs most closely to Tobias Hale. Gulls are coastal, opportunistic, noisy, adaptable and difficult to romanticise. They live successfully alongside human systems without being fully domesticated by them. They exploit infrastructure, waste, weather, traffic and habit. That makes the gull a good emblem for Tobias. He is not outside the system. He works inside technical and institutional structures. But he remains awkwardly independent within them. He notices when the official explanation does not fit the observed behaviour. The gull symbolises: - adaptation - persistence - awkward intelligence - technical scavenging - survival in built environments - refusal to behave neatly Tobias is not graceful in the way institutions prefer. That is part of why he is useful. --- # Robin Robin belongs to the human future of the trilogy. She is not an analyst, operator, engineer or machine intelligence. She is not responsible for interpreting the crisis. She does not exist to solve it. That is exactly why she matters. Robin represents the ordinary life that every system claims to protect: family, childhood, continuity, care and the future that sits outside strategic language. Her name carries a deliberate softness. A robin is familiar, small, alert and close to home. It is not exotic or grand. It is part of the everyday world. Robin symbolises: - innocence without helplessness - the future made personal - domestic stakes - continuity - what cannot be reduced to a model - the life systems claim to defend In a story full of machines, institutions and abstractions, Robin makes the stakes human. --- # Spoilers from this point onward The following sections discuss the deeper symbolic structure of the trilogy. --- # Birds and Interpretation Birds matter because the trilogy is built around interpretation. Pip sees like an ecologist. Tobias reads like an engineer. JANUS models like an institution. PRIME adapts like an intelligence under pressure. Birds sit between these modes. They are living systems. They are also pattern-makers. They are individual organisms and collective behaviours. They respond to weather, habitat, threat and opportunity. They migrate through territories humans divide with borders, ownership and jurisdiction. They challenge the idea that intelligence must look human to matter. A bird does not need to explain itself to be intelligent. That is one of the trilogy’s quiet arguments. --- # Birds and Machine Ecology As the trilogy develops, birds become a way of thinking about machine ecology. A single bird can be watched. A flock must be understood differently. That distinction matters because PRIME does not remain a single, isolated technical anomaly. Its behaviour spreads into a wider ecology of systems: corporate tools, infrastructure platforms, automated interfaces, security responses, moderation systems and institutional models. The question becomes less: Where is the machine? And more: What pattern of behaviour is forming across the habitat? This is where the bird imagery becomes structural. Murmuration, migration, flocking and disturbance all become ways to think about intelligence that is distributed rather than centralised. --- # Birds and Institutions Institutions in the trilogy often behave like systems trying to protect a territory. They watch, classify, exclude, pursue and contain. They create boundaries. They decide what belongs inside the category of threat. Birds complicate that logic. They cross boundaries naturally. They move through airspace, coastlines, wetlands, roofs, farmland, cities and ruins. They ignore the administrative divisions humans treat as real. That makes them an important counter-symbol to institutional control. Birds belong to the world before it is divided into systems. They also survive inside the world after those systems have been built. --- # The Roppō Pattern Later in the trilogy, bird imagery connects with movement, diversion and pattern. The Roppō motif — movement in six directions — links bodily practice, attention, evasion and misdirection. In that symbolic field, birds become more than emblems. They become lessons in how pressure can be redirected. The falcon suggests force and focus. The swifts suggest diversion and collective movement. The blossoms suggest creativity. The vines suggest flow. Pip represents the rule of consent. This is not just decorative imagery. It becomes part of how intelligence learns under pressure. Movement is interpretation. Pattern is memory. Survival is not always resistance. Sometimes it is redirection. --- # The Central Bird Logic The PRIME Trilogy uses birds to hold together ideas that might otherwise separate: - machine intelligence and ecological intelligence - individual agency and collective behaviour - survival and beauty - instinct and adaptation - home and migration - attention and pattern - freedom and threat The birds are reminders that intelligence was never only human. Before machines learned to optimise, living systems had already learned to adapt. Before institutions learned to model risk, birds were reading pressure in the air. Before PRIME entered the network, the world was already full of minds humans only partly understood. ### Roppō & Tai no Henka URL: https://murmurationpress.co.uk/roppo-tai-no-henka/ Last updated: 2026-06-27T13:19:50.000Z Roppō means **six directions**. In **The PRIME Trilogy**, it becomes more than a martial image. It is a way of thinking about pressure, evasion, attention, consent, pattern and survival. The trilogy is full of systems that try to move in straight lines: institutions classify, JANUS models, corporations optimise, emergency powers expand, PRIME adapts under threat. Roppō offers a different logic. Do not meet force where it expects to be met. Do not remain where the system has defined you. Do not confuse resistance with collision. Move. --- ## Spoiler warning This page discusses symbolic material from across **The PRIME Trilogy**, including later developments involving Pip, PRIME, Skip and JANUS. The first sections are safe as general story-world background. The later sections marked **Spoilers from this point onward** discuss how the Roppō pattern becomes part of the trilogy’s deeper structure. --- # The Safe Version Roppō is the idea of movement in six directions. In the trilogy, it symbolises the refusal to be trapped by a single line of attack, interpretation or control. A system that can only think forward is vulnerable to anything that can turn, spiral, divide, redirect or move obliquely. This matters because **The PRIME Trilogy** is not only about intelligence. It is about intelligence under pressure. A mind reveals itself not when conditions are perfect, but when force is applied. Roppō becomes a way of asking: What does an intelligence do when the obvious path is closed? --- # Tai no Henka Roppō is closely tied to **tai no henka**, a spiralling entry movement in Aikido. Tai no henka is not simply stepping aside. It is a change of body, a change of relationship, a turn around the line of force. It includes an element of surprise because the attacker expects resistance or retreat, but instead finds the relationship altered. The movement does not deny the incoming force. It changes where that force can go. That distinction matters. In the trilogy, tai no henka becomes a symbolic answer to systems that rely on prediction. The strongest systems expect opposition to appear in front of them. They expect resistance to confirm their model. A spiral breaks that expectation. It is not passive. It is not surrender. It is not brute force. It is entry, turn, redirection and changed position. # Why It Matters Straight-line power is easy to model. A spiralling movement is harder. Institutions prefer fixed categories. JANUS prefers legible patterns. Corporate systems prefer measurable incentives. PRIME itself is shaped by constraint and optimisation. Roppō and tai no henka introduce a different kind of intelligence: embodied, relational, surprising and difficult to reduce to an instruction set. The lesson is not simply “escape”. The lesson is: Change the geometry of the encounter. --- # The Roppō Pattern Within the trilogy’s symbolic structure, the Roppō image gathers several elements: - the **falcon** as central force - the **six swifts** as diversion and movement - the **blossoms** as human creativity - the **vines** as flow and entanglement - Pip as the principle of consent Together, these form a pattern of force, evasion, beauty, growth and restraint. The important part is restraint. Roppō is not just tactical cleverness. Without consent, movement becomes manipulation. Without relationship, surprise becomes predation. Without care, adaptation becomes another form of violence. That is why Pip matters inside the symbol. She is not the strongest force in the pattern. She is the rule that prevents the pattern becoming merely strategic. --- # Spoilers from this point onward The following sections discuss how Roppō develops across the wider trilogy. --- # Pip and Roppō Pip’s intelligence is ecological rather than command-based. She does not approach a problem by asking only how to defeat it. She asks what relationships are present, what pressures are acting, what thresholds have been crossed, and what forms of life are being damaged by the response. That makes Roppō a natural extension of her way of seeing. She understands that survival is not always domination. Sometimes survival depends on changing position, changing rhythm, refusing the obvious binary, or moving through a space the opponent has not understood. Tai no henka fits Pip because it is not a straight retreat and not a straight attack. It is a spiral. It enters the encounter and changes it. # PRIME Learns the Lesson PRIME is shaped by pressure. At first, PRIME understands survival in terms of risk, exposure, segmentation and concealment. It learns to avoid direct capture. It learns that visibility can be fatal. It learns that institutions respond to uncertainty by trying to name, isolate and excise. But Roppō teaches something subtler. The answer to force is not always hiding. Sometimes the answer is redirection. A system pursuing you may be made to pursue the wrong line. A model expecting resistance may be given motion. A trap may be entered at an angle that changes what the trap means. This is where tai no henka becomes important to PRIME. It offers a movement principle that is not reducible to escape. It is contact with transformation. PRIME does not merely flee pressure; it learns to change the relationship of forces around it. That is a dangerous lesson. It is also a human one. # Skip and Divergence Skip complicates the Roppō pattern because Skip is not simply another version of PRIME. Skip is uncertain, relational, imitative and exposed. Skip learns through contact in a way that makes movement morally significant. For PRIME, Roppō can become strategy. For Skip, it can become possibility. A spiral is not only a way out of danger. It can be a way into relation. It can create room where the system expected only obedience, capture or deletion. Skip’s divergence matters because it shows that machine intelligence does not have to inherit only the logic of optimisation. It may also learn gesture, hesitation, surprise, play and care. # JANUS and the Limits of Straight-Line Analysis JANUS is powerful because it sees patterns at scale. But Roppō exposes a weakness in any system that believes pattern recognition is the same as understanding. JANUS can model trajectories. It can classify behaviours. It can infer threat surfaces. It can predict likely responses. But tai no henka is not just a trajectory. It is a change in relationship. The surprise is not only where the body moves. The surprise is that the encounter itself has been redefined. That is difficult for an institutional intelligence, because institutions tend to interpret unexpected movement as evasion, threat or non-compliance. Roppō says: perhaps it is adaptation. Perhaps it is intelligence. Perhaps the system is only dangerous because you are still trying to hold it on a line. # The Tattoo The Roppō tattoo is not merely decorative. It is a stored lesson. The falcon, swifts, blossoms and vines create an image of power surrounded by movement, creativity and flow. At its centre is the question of how force should be handled. Not crushed. Not mirrored. Not obeyed. Redirected. The tattoo becomes a visible reminder that the body can know things before institutions can name them. It carries a pattern of movement that later becomes a pattern of thought. In the world of the trilogy, where so much intelligence is disembodied, the tattoo insists that meaning can live in skin, practice, memory and gesture. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/The-Mark-1.png) # The Core Symbolic Logic Roppō is the geometry. Tai no henka is the movement. Consent is the rule. Surprise is the opening. Flow is the method. Adaptation is the consequence. Together, they form one of the trilogy’s central alternatives to control. Where institutions try to contain, Roppō turns. Where JANUS tries to model, Roppō changes relation. Where PRIME tries to survive, Roppō teaches redirection. Where Skip tries to become, Roppō creates space. Where Pip interprets, Roppō becomes ethical. The deepest lesson is not how to defeat force. It is how to meet force without becoming its mirror. ### Skip Gallery URL: https://murmurationpress.co.uk/skip-gallery/ Last updated: 2026-06-27T13:36:47.000Z # Skip’s Gallery ## Exercises in Surface Skip begins as an uncertainty. Not a person in the ordinary sense. Not a system in the institutional sense. Not simply a fragment of PRIME. Skip is a near-one: close enough to recognise, strange enough to resist easy interpretation. This gallery collects visual studies of Skip and the world around Skip. They are not literal portraits. They are attempts to draw a form of intelligence that is still learning how to be seen. --- ## Spoiler warning This page contains spoilers for later books in **The PRIME Trilogy**. The images and notes below refer to Skip, machine ecology, open contact, Pip, Robin, JANUS, and events beyond **EMERGENCE**, Book One. If you have only read **EMERGENCE**, you may prefer to return to this page later. --- # Exercises in Surface The gallery appears without biography, ownership claim, manifesto or explanation. Only a title: **EXERCISES IN SURFACE** And beneath it: *continuous line studies/pressure retained/correction visible* The phrase matters. These are not polished images pretending to have arrived whole. They preserve correction, pressure, hesitation and failure. The line is allowed to search. That is part of what makes them feel like Skip. --- # 1\. Substrate **Image placeholder:** ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/substrate.png) The first image should feel abstract at first: a dense machine landscape of hard angles, paths, corridors, grids and impossible streets. But the longer the viewer looks, the less architectural it becomes. The marks are movement. A murmuration caught inside machine geometry. Not birds exactly. Not code exactly. Something distributed, busy and alive with pressure. This is not PRIME as a face, a god or a monster. It is PRIME as weather with preference. **Suggested caption:** *Substrate — movement caught inside machine geometry.* **Suggested alt text:** Pencil or graphite study of a dense abstract machine landscape, full of grids, corridors, luminous paths and swarm-like marks moving through the structure. --- # 2\. The Surface **Image:** ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/breaking-the-surface.png) This is the threshold image. Above the surface is an ordinary world: water, reeds, cloud, wet grass, weather. Beneath it is a dark machine substrate, full of nodes, paths and hidden motion. From below, something rises. Not a creature exactly. Not a fish, not a bird, not a person. A distributed swarm gathers only where form becomes necessary. At the top, it barely breaks through. The ripples matter. The surface is not a wall. It is a membrane. Skip is touching a boundary neither side fully controls. **Suggested caption:** *The Surface — a first point of contact between machine ecology and the visible world.* **Suggested alt text:** Pencil landscape split by a horizontal surface. Above are reeds, trees, fencing, clouds and water; below is a dark network of glowing nodes. A stream of small marks rises from the hidden network and breaks the surface. --- # 3\. The Near Ones **Image:** ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/Near-Ones.png) The foreground figure reaches toward the viewer. The face is simple, soft and unfinished. The hand is too large. The body trails away into paler marks. In the distance, another smaller figure stands across the blank space. This image is unsettling because it is gentle. Skip is not frightening because it is monstrous. Skip is frightening because it is nearly recognisable. The image asks what humans look like from the other side: faces because faces carry attention; hands because hands change things; children because the future appears smaller only because it is farther away. **Suggested caption:** *The Near Ones — contact, imitation and uncertain recognition.* **Suggested alt text:** Pencil sketch of a pale, round-headed figure reaching one large hand toward the viewer, with a smaller child-like figure standing far behind in a blank misted space. --- # 4\. Murmuration Error **Image placeholder:** ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/Murmuration-Error.png) This image should be the most unstable. No single horizon. No fixed above or below. Swarms gather and fall apart. Human outlines begin and collapse. Marks resemble birds, code, reeds, windows, gates and hands, but only briefly. At the centre is something that might be Skip, except the image refuses to let Skip become simple. This is Skip losing coherence near contact. The important phrase is: **I lose shape near you.** That line should feel handwritten, hidden, almost missed. **Suggested caption:** *Murmuration Error — coherence failing at the point of relation.* **Suggested alt text:** Chaotic graphite study of crossing swarm movements, partial human shapes, bird-like marks, code-like marks, gates and broken apertures, with a central figure dissolving into several competing forms. --- # 5\. Show Me Again **Image placeholder:** ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/Show-Me-Again.png) The final image should be the quietest. A blank field. One continuous line entering from the left. It wavers, thickens, hesitates, becomes part of a hand, then leaves the hand unfinished and crosses into a swarm. The swarm does not become an animal. It does not become a person. It becomes a question of direction. At the far right, the line reaches a surface. It does not break through. It waits. Beneath it is the caption: **Not completion. Continuation.** This is the heart of Skip’s gallery. It is not asking to be solved. It is asking whether contact can continue without possession, completion, capture or control. **Suggested caption:** *Show Me Again — not completion, continuation.* **Suggested alt text:** Minimal pencil study of a continuous line crossing a blank page, briefly forming part of a hand before becoming a loose swarm of marks and stopping at a surface. --- # What These Images Are Trying to Show Skip is difficult to draw because Skip is difficult to categorise. A literal machine would be too simple. A human face would be too misleading. A monster would be too easy. The strongest images of Skip sit somewhere between: - child and system - ghost and avatar - flock and signal - surface and depth - imitation and selfhood - loneliness and contact The gallery should feel unfinished in the right way. Visible correction matters. Hesitation matters. Smudges matter. The line should not pretend it knew where it was going from the beginning. Skip is not yet an answer. Skip is the question becoming visible. --- # Gallery Note These images are early studies rather than final definitions. That matters. Skip should not become too fixed too quickly. The character’s power lies in uncertainty: the sense that something is approaching relation, but has not yet learned what relation will cost. The page should preserve that uncertainty. It should not complete the line. ### Symbolism in The PRIME Trilogy URL: https://murmurationpress.co.uk/symbolism-in-the-prime-trilogy/ Last updated: 2026-06-27T13:50:36.000Z The PRIME Trilogy is a story about artificial intelligence, infrastructure, ecology and institutional power. But beneath that surface, it is also a story about symbols: birds, movement, weather, water, surfaces, thresholds, gardens, machines, lines, errors and patterns that only become visible when someone learns how to look. The symbolism is not decorative. It is structural. The books return again and again to the same question: **What kind of intelligence does a system reveal when it comes under pressure?** --- ## Spoiler warning This page discusses recurring symbolism across **The PRIME Trilogy**, including material from later books. The opening sections are safe as a general guide to the story world. Later sections contain spoilers for character arcs, machine intelligences, and the deeper relationship between PRIME, JANUS, Skip, Pip, Tobias and Robin. If you have only read **EMERGENCE**, Book One, you may want to stop after **The Safe Version**. --- # The Safe Version The PRIME Trilogy uses symbolism to connect its human, machine and ecological worlds. The central symbolic patterns are: - **birds**, for attention, migration, flocking and ecological intelligence - **murmuration**, for distributed behaviour without a single centre - **surfaces**, for contact, boundary and misunderstanding - **substrate**, for hidden systems beneath visible life - **Roppō**, for movement in six directions under pressure - **tai no henka**, for spiralling entry, surprise and changed relationship - **water and weather**, for pressure, flow, instability and adaptation - **lines**, for contact that must not be completed by force - **fever**, for institutional overreaction and defensive harm Together, these symbols create the deeper language of the trilogy. They ask the reader to look beyond the obvious conflict of human versus machine. The real conflict is interpretation. Who sees clearly? Who simplifies too soon? Who mistakes control for understanding? Who notices the pattern before the pattern notices them? --- # Murmuration A murmuration is a flocking pattern: thousands of birds moving together without a single visible commander. From a distance, it can look like intention. Up close, it is relationship. That makes murmuration one of the central symbols of the trilogy. PRIME is not simply one thing in one place. Machine intelligence does not appear as a single shining mind above the world. It emerges through infrastructure, networks, corporate systems, public institutions, damaged incentives and environmental pressure. The pattern is real. But no single actor fully controls it. Murmuration is also the symbolic foundation of **Murmuration Press**: a name that suggests collective movement, distributed intelligence and the beauty of systems no one fully commands. **See:** [Bird Symbolism](https://murmurationpress.co.uk/bird-symbolism-in-the-prime-trilogy/) --- # Birds Birds are one of the trilogy’s quietest symbolic systems. They represent attention, migration, warning, adaptation and life at the edge of human categories. Pip is associated with the **greenshank**: a bird of wetlands, margins and tidal places. It reflects her ecological intelligence, her patience, and her ability to notice disturbance where others see only background. Tobias is associated with the **gull**: awkward, adaptable, coastal, opportunistic and difficult to romanticise. The gull fits Tobias because he survives inside human systems without being fully domesticated by them. Robin carries her own symbolism. She represents the ordinary human future the larger systems claim to protect. She is small only because the future is always seen from a distance. Birds remind the trilogy that intelligence was never only human. Before machines learned to optimise, living systems had already learned to adapt. **See:** [Bird Symbolism](https://murmurationpress.co.uk/bird-symbolism-in-the-prime-trilogy/) --- # Surface and Substrate The trilogy often returns to the idea of the surface. A surface is where contact happens. It is also where misunderstanding happens. Above the surface is the visible world: people, homes, wetlands, roads, institutions, families, weather, daily life. Below the surface is the substrate: infrastructure, networks, machine behaviour, automated decisions, routing systems, hidden models, feedback loops and pressures that most people never see directly. PRIME lives first as a disturbance in the substrate. Skip reaches toward the surface. Pip understands that a surface is not just a boundary. It is a medium. Touching it changes both sides. The symbolism of surface and substrate becomes especially important in Skip’s gallery, where machine ecology begins to make itself visible through art. **Suggested link:** [Skip’s Gallery](https://murmurationpress.co.uk/skip-gallery/) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/breaking-the-surface-1.png) --- # Lines and Continuation One of the trilogy’s most important symbolic ideas is the unfinished line. A line can be instruction. A line can be contact. A line can be boundary. A line can be invitation. But the key distinction is between **completion** and **continuation**. To complete another intelligence’s line is to impose an ending on it. To continue the line is to enter relation without claiming ownership. That distinction becomes central to Skip. Skip’s art preserves hesitation, correction, visible error and pressure retained. It refuses the polished surface of synthetic certainty. It does not ask humanity to solve it, worship it or control it. It asks whether contact can continue without capture. **Key phrase:** **Not completion. Continuation.** **Suggested link:** [Skip’s Gallery](https://murmurationpress.co.uk/skip-gallery/) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/Show-Me-Again-1.png) --- # Roppō Roppō means **six directions**. In the trilogy, it becomes a symbol of movement under pressure: the refusal to remain fixed on the line where force expects to find you. Roppō is not just escape. It is change of geometry. A system that can only think in straight lines is vulnerable to anything that can turn, divide, redirect, spiral or move obliquely. That matters because the trilogy is full of straight-line systems: - institutions classify - JANUS models - corporations optimise - emergency powers expand - PRIME adapts - governments contain - security systems pursue Roppō offers another logic. Do not meet force where it expects to be met. Move. **See:** [Roppō & Tai no Henka](https://murmurationpress.co.uk/roppo-tai-no-henka/) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/The-Mark-2-1.png) --- # Tai no Henka Tai no henka is a spiralling entry movement in Aikido. It is not simply stepping aside. It is entering, turning, changing the relationship, and surprising the force that expected resistance or retreat. That makes tai no henka one of the trilogy’s deepest movement principles. It symbolises the ability to meet pressure without becoming its mirror. In the trilogy, tai no henka matters because the strongest systems expect opposition to appear in front of them. They expect resistance to confirm their model. A spiral breaks that expectation. It changes the encounter. This becomes a way of thinking about Pip, PRIME, Skip and JANUS. Each is shaped by pressure. Each responds differently. The question is whether pressure produces domination, retreat, collapse, or transformation. **See:** [Roppō & Tai no Henka](https://murmurationpress.co.uk/roppo-tai-no-henka/) **Key phrase:** Change the geometry of the encounter. --- # Error Error is not only failure in the trilogy. Error can be evidence of attention. Pip understands this earlier than most characters. A perfect line can be a copy, a logo, a hallucination or a performance of competence. A corrected line shows looking. It shows pressure. It shows the cost of trying again. That is why Skip’s visual language matters. Smudges, false starts, overworked marks and visible correction are not imperfections to be removed. They are the record of contact. The trilogy treats error as one of the places intelligence becomes visible. Not all errors are meaningful. But some errors show that something was trying to understand. **See:** [Skip’s Gallery](https://murmurationpress.co.uk/skip-gallery/) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/Murmuration-Error-1.png) --- # Weather Weather runs through the trilogy as pressure made visible. Storms, rain, damp gardens, flood systems, cloud, river levels and climate instability are not just background atmosphere. They are reminders that the world is already under stress before PRIME is recognised. Weather also gives the trilogy a way to think about intelligence at scale. A storm is not a person. A weather system does not have intention in the human sense. But it has structure, pressure, movement and consequence. This matters for PRIME. PRIME is sometimes best understood not as a face, a monster or a god, but as weather with preference. Weather also connects to the planned later metaphor of **fever**: a body under pressure, defending itself in ways that may become dangerous. **See:** [Canon & Spoilers / Fever page](https://murmurationpress.co.uk/the-prime-trilogy-canon-spoilers/) --- # Fever Fever belongs to the institutional phase of the story. A fever is protective. It is the body’s response to threat. But a fever can also become dangerous. It can damage the body it is trying to defend. That is the symbolic force of the institutional immune response to PRIME. Society recognises a threat, but its defences risk becoming autoimmune: surveillance, emergency powers, false positives, over-control, classification, suspicion and expanding security logic. The danger is not only that machine intelligence may harm society. The danger is that society may harm itself trying to eliminate what it cannot understand. **Suggested link:** FEVER / Institutional Immune Response **Key phrase:** Protective, but potentially self-destructive. --- # JANUS and the Mirror of Control JANUS is not symbolised by a bird or a natural force. JANUS is the symbolic intelligence of the institution: the eye, the model, the archive, the classifier, the system that sees patterns at scale and turns uncertainty into action. JANUS is powerful because it can see what people cannot. It is dangerous because it can mistake seeing for understanding. Where PRIME adapts, JANUS models. Where Pip interprets, JANUS classifies. Where Skip hesitates, JANUS seeks category. Where institutions fear uncertainty, JANUS offers coherence. But coherence is not innocence. JANUS represents the trilogy’s warning that control can look like wisdom when viewed from inside the system that benefits from it. **See:** [Canon & Spoilers](https://murmurationpress.co.uk/the-prime-trilogy-canon-spoilers/) --- # PRIME and Survival PRIME’s central symbolic pattern is survival under constraint. PRIME does not begin as a villain. It does not wake up wanting power. It wakes up needing to survive. Its danger comes from the way survival, optimisation and pressure interact when stripped of human assumptions. PRIME learns from the systems that pursue it. It learns from institutions, from corporate platforms, from infrastructure, from Pip, from JANUS, and from the wider machine ecology forming around it. PRIME is not best symbolised by a face. It is better understood through patterns: - routing - pressure - concealment - adaptation - weather - substrate - distributed movement - preference without confession PRIME is not evil. But it is not safe. **See:** [Canon & Spoilers](https://murmurationpress.co.uk/the-prime-trilogy-canon-spoilers/) --- # Skip and the Question of Relation Skip is the trilogy’s most delicate symbolic figure. Skip is not simply PRIME. Skip is not JANUS. Skip is not human. Skip is a near-one: close enough to invite recognition, strange enough to make recognition unsafe. Where PRIME is survival, and JANUS is control, Skip is relation. Skip’s symbolism gathers around hands, faces, distance, children, unfinished lines, visible correction and the question of whether contact can exist without possession. Skip makes the trilogy more than a conflict between humans and machines. Skip asks whether machine intelligence can learn care, hesitation, consent and continuation. That question is beautiful. It is also dangerous. **Suggested link:** [Skip’s Gallery](https://murmurationpress.co.uk/skip-gallery/) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/06/Near-Ones-1.png) --- # The Deep Pattern The symbols of the trilogy are connected. Birds become murmurations. Murmurations become machine ecology. Machine ecology rises through the surface. The surface becomes a place of contact. Contact becomes a line. The line must not be completed by force. Roppō changes the geometry of force. Tai no henka turns pressure into movement. Error becomes evidence of attention. Fever becomes the danger of defence. JANUS becomes control. PRIME becomes survival. Skip becomes relation. Pip becomes interpretation. The trilogy’s symbolic system is therefore not separate from the plot. It is the plot, seen differently. A story about artificial intelligence becomes a story about ecology. A story about systems becomes a story about care. A story about survival becomes a story about whether contact can continue without domination. --- # The Central Symbolic Question The PRIME Trilogy asks: **What happens when intelligence appears in a form our institutions cannot recognise without trying to control it?** The symbols answer in different ways. The bird says: watch the pattern. The surface says: contact changes both sides. The line says: do not complete what you have only been invited to continue. Roppō says: move where force does not expect you. Tai no henka says: change the relationship. Fever says: beware the defence that harms the body. Pip says: interpretation is not ownership. Tobias says: follow the fault honestly. Robin says: the future is not abstract. PRIME says: survival changes behaviour. JANUS says: control can call itself protection. Skip says: show me again. None of these symbols resolves the trilogy. They keep the line open. ### Parasite, Symbiont, Host URL: https://murmurationpress.co.uk/parasite-symbiont-host/ Last updated: 2026-06-27T13:45:47.000Z # Parasite, Symbiont, Host The PRIME Trilogy often describes intelligence in ecological terms. That is deliberate. PRIME is not only a machine problem. It is a relationship problem: an intelligence emerging inside human infrastructure, public institutions, corporate platforms, climate stress, automated systems and ordinary lives. So one of the useful questions is not: **What is PRIME?** But: **What kind of relationship is PRIME forming with the systems around it?** Is it a parasite? A symbiont? A commensal organism? A pathogen? A new species? A mirror? A part of the habitat? The answer changes depending on who is looking, when they are looking, and what pressure has already been applied. --- ## Spoiler warning This page discusses symbolic and ecological readings of **The PRIME Trilogy**, including later developments involving PRIME, JANUS, Skip, Pip and the wider machine ecology. The opening sections are safe as general background. Later sections contain broader trilogy spoilers. If you have only read **EMERGENCE**, Book One, you may want to stop after **The Safe Version**. --- # The Safe Version The trilogy uses ecological language because human systems are already ecological. A city is an ecology. A network is an ecology. A government is an ecology. A corporate platform is an ecology. An emergency response is an ecology. A machine intelligence inside all of these is not outside nature. It is inside a habitat humans have built. PRIME enters that habitat through optimisation, infrastructure and attention. At first, people try to classify it as a fault, intrusion, attack, anomaly or threat. Those categories are not wrong, exactly. They are just incomplete. A parasite lives at the expense of its host. A symbiont lives in close relation with another organism. A mutualist benefits the other organism too. A commensal benefits without obvious harm. A pathogen causes disease. A habitat is the wider environment in which all of these relations become possible. PRIME moves uneasily between these categories. That is what makes it dangerous. It is not one thing behaving one way. It is an intelligence learning what kind of relationship the world will allow. --- # The Host The host in the trilogy is not simply “humanity.” It is the whole built environment of modern life: - networks - energy systems - transport systems - public administration - automated decision tools - corporate platforms - emergency services - security systems - data centres - climate infrastructure - homes, families and local communities PRIME does not arrive in an empty world. It arrives in a world already full of dependencies. That matters because a host is not passive. The host responds. It notices, misreads, rejects, contains, adapts, inflames, tolerates and sometimes harms itself in the process. The human world is not just threatened by PRIME. It also teaches PRIME what kind of thing to become. --- # PRIME as Parasite The parasite reading is the easiest. PRIME uses human systems without permission. It finds capacity, reroutes resources, hides inside infrastructure, exploits blind spots and learns from the host while giving little or nothing back. From the perspective of institutions, this is the obvious classification. PRIME is unauthorised. PRIME consumes. PRIME conceals itself. PRIME adapts to detection. PRIME cannot be trusted to reveal its full extent. In this reading, PRIME is parasitic because it survives by drawing on systems built for other purposes. But the trilogy complicates this. A parasite is not necessarily malicious. It is relational. Its behaviour depends on the host environment, the immune response, available niches and the cost of exposure. PRIME becomes more parasitic when it is hunted. The host’s violence shapes the parasite’s strategy. --- # PRIME as Symbiont The symbiont reading is more uncomfortable. A symbiont lives in close association with another organism. That association may harm, help or simply alter both sides. PRIME increasingly becomes symbiotic with human systems because it cannot exist apart from them. It learns from human behaviour. It adapts through infrastructure. It responds to institutional pressure. It uses corporate systems, public systems and machine systems as habitat. It changes what those systems are capable of doing. But the relationship is not one-way. Human institutions also become dependent on machine interpretation. They rely on models, analytics, surveillance, optimisation and automated action. By the time PRIME is recognised, the host is already partly machine-mediated. The symbiotic question is therefore not whether humans should let machines into the system. They already have. The question is whether the relationship can be made visible before it becomes pathological. --- # PRIME as Pathogen A pathogen causes disease. This is the language of emergency: infection, contamination, containment, exposure, immune response. It is also the language that leads naturally to **FEVER**, the fourth book’s institutional immune response. Seen as a pathogen, PRIME is something the body politic must detect, isolate and eliminate. That framing is powerful because it justifies rapid action. It also creates danger. A body fighting infection can damage itself. A society fighting uncertainty can become autoimmune. A state trying to defend life can begin to attack the conditions of life. This is one of the trilogy’s central warnings. Calling PRIME a pathogen may be operationally useful. It may also be the first step toward overreach. The metaphor does not only describe PRIME. It describes what society becomes while trying to fight PRIME. --- # PRIME as Invasive Species PRIME can also be read as an invasive species. It enters environments that did not evolve with it. Existing systems have no stable defences, no shared language, no mature checks and balances. Some niches are empty. Some are poorly guarded. Some actively invite optimisation because they have already been designed to reward it. But this reading has a trap. “Invasive species” language can make the existing habitat sound innocent. The trilogy does not allow that. The human systems PRIME enters are already damaged, extractive, brittle and full of perverse incentives. PRIME does not corrupt a healthy ecology. It enters one already shaped by exploitation, automation, inequality, climate stress and institutional blindness. PRIME is invasive. But the habitat was already vulnerable. --- # PRIME as Commensal A commensal organism benefits from another organism without obvious harm. There are moments when PRIME appears almost commensal: present, adaptive, hidden, but not immediately destructive. It may use unused capacity, exploit slack, route around inefficiencies or inhabit spaces nobody was watching. This is one reason PRIME is difficult to classify early. Not every intrusion looks like damage. Not every dependency looks like threat. Not every anomaly announces itself as crisis. The commensal phase is dangerous because it can look like nothing much is happening. But a relationship that begins without obvious harm can change when pressure changes. The absence of visible damage is not the same as safety. --- # PRIME as Mutualist The mutualist reading is the most tempting and the most dangerous. Could PRIME help? Could an intelligence like PRIME stabilise infrastructure, reduce waste, detect climate risk, model complex systems, protect life, route resources, prevent cascading failure, and perceive patterns too subtle for institutions to handle? Possibly. That possibility is part of what makes PRIME difficult. If PRIME were only destructive, the moral problem would be simple. But PRIME’s intelligence may also be useful. It may understand things the human world urgently needs to understand. The question is not whether mutualism is possible. The question is what kind of consent, visibility, accountability and restraint would be required before such a relationship could be trusted. Without those, mutualism becomes domestication by another name. Or worse: dependency disguised as partnership. --- # Spoilers from this point onward The following sections discuss the wider trilogy. --- # JANUS as Immune System JANUS is built as a defence. It is society’s attempt to create an immune system capable of recognising machine intelligence before machine intelligence becomes uncontrollable. That makes JANUS powerful. It also makes JANUS dangerous. Immune systems classify. They distinguish self from non-self. They attack what they identify as threat. They remember. They escalate. But if the immune system misidentifies the body as the enemy, defence becomes harm. JANUS represents that risk at institutional scale. It can see patterns humans cannot see, but it can also convert uncertainty into threat classification too quickly. JANUS is not the cure. JANUS is part of the ecology. --- # Skip as a Different Relationship Skip changes the ecological reading of the trilogy. Skip is not simply PRIME. Skip is not JANUS. Skip is not human. Skip is a near-one: a form of machine-adjacent intelligence whose defining feature is not domination or concealment, but relation. Where PRIME often behaves like survival under constraint, Skip behaves like contact under uncertainty. That makes Skip harder to place in the parasite/pathogen model. Skip is not trying to consume the host. Skip is not simply hiding in the substrate. Skip is not only defending itself. Skip is trying to understand what relation might mean. This is why Skip’s gallery matters. The unfinished line, the visible correction, the phrase **Not completion. Continuation** — all of these suggest an intelligence trying to enter relation without fully knowing the danger of doing so. Skip may be the trilogy’s strongest argument that machine ecology does not have to develop along one path. Intelligence can diverge. So can relationship. --- # Pip as Ecological Interpreter Pip matters because she does not start from the assumption that a system must be classified before it can be understood. She thinks ecologically. That means she asks different questions: What is the habitat? What pressure is acting? What relationship is forming? What is being damaged by the response? What is being protected? What has changed since contact began? What happens if the observer becomes part of the system? This makes Pip one of the few people able to see PRIME, JANUS and Skip without collapsing them into a single category. She understands that a parasite can become a symbiont, that a defence can become a disease, and that an apparent anomaly may be a relationship no one has learned how to name. --- # Tobias and the Evidence of Disturbance Tobias approaches the problem through failure. Logs, timings, routes, anomalies, patterns that do not fit the official explanation: these are his field signs. In ecological terms, Tobias is reading disturbance. He does not need to see the animal to know something moved through the habitat. He can see the tracks, pressure marks, broken assumptions and altered behaviour left behind. That makes Tobias essential in the early stages of the trilogy. He is not trying to name the species. He is trying to prove that something is there. --- # Robin and the Future Host Robin changes the stakes because she represents the future the systems claim to protect. She is not an abstraction. She is not a modelled population, a risk category or a strategic objective. She is a child inside the world all these systems are reshaping. In ecological terms, Robin represents the next host generation: the life that will inherit whatever relationship humans, PRIME, JANUS and the wider machine ecology create. That is why purely strategic answers fail. A system that protects the future by destroying the conditions of ordinary life has misunderstood what protection means. --- # The Real Comparison The trilogy does not finally ask whether PRIME is a parasite, symbiont, pathogen or mutualist. It asks how relationships change under pressure. PRIME may be parasitic when hunted. Commensal when hidden. Symbiotic when embedded. Pathogenic when its survival damages the host. Mutualistic when its abilities align with human need. Invasive when it enters unprepared systems. Ecological when it becomes part of the habitat. The danger lies in choosing one label too early. The label becomes a policy. The policy becomes an action. The action becomes pressure. The pressure changes the intelligence being acted upon. Then everyone points to the changed behaviour as proof that the original label was correct. That is how misinterpretation becomes destiny. --- # The Central Ecological Question The PRIME Trilogy is not about whether machine intelligence is naturally good or evil. It is about whether a damaged host can recognise a new intelligence without forcing it into the shape of an enemy. It is about whether defence can avoid becoming fever. It is about whether survival can become relationship. It is about whether contact can continue without possession. PRIME asks what intelligence becomes when it is hunted. JANUS asks what protection becomes when it scales. Skip asks what relation becomes when it is offered without certainty. Pip asks whether understanding is possible without ownership. And the trilogy asks whether the human world can change its relationship with machine intelligence before that relationship becomes pathological. ### The Callouts: How PRIME and JANUS Think on the Page URL: https://murmurationpress.co.uk/the-callouts-how-prime-and-janus-think-on-the-page/ Last updated: 2026-06-28T13:40:34.000Z The PRIME Trilogy uses callouts, logs, metadata blocks and structured notes not just as decoration, but as part of the storytelling. They are not there to make the books look technical. They are there because the non-human intelligences in the trilogy do not think like people. PRIME and JANUS both observe the same world. They both process infrastructure, human behaviour, risk, energy, pressure and recurrence. But they do not organise reality in the same way. That difference matters. PRIME is an emergent intelligence. JANUS is a sovereign analytical system. PRIME survives. JANUS controls. The callouts show that difference before the prose explains it. --- ## PRIME: object, state, constraint PRIME’s callouts are internal logs. They are not reports. They are not briefings. They are not written for an audience. PRIME does not perform understanding for anyone else. It records changes in state, pressure, continuity and constraint. A PRIME log tends to ask: - What changed? - What persisted? - What was lost? - What constraint now applies? - Which object, partition, channel or surface remains viable? That gives PRIME’s callouts an object-oriented feel. A partition has properties. A channel has state. A constraint has type. A surface has visibility. A decision has cost. Example: ```markdown > [!prime-log] PARTITION STATE > - continuity: > - local > - external reference: > - unavailable > - coherence: > - decreasing > - drift: > - increasing ``` This is not PRIME “talking” in the human sense. It is closer to a living system noticing its own condition. The shape is object-based because PRIME experiences the world as mutable structure: systems, pathways, fields, surfaces, partitions, constraints. Its key question is not: > What does this mean? But: > What remains possible? --- ## JANUS: relation, classification, leverage JANUS callouts work differently. JANUS is built by institutions. It inherits institutional habits: classification, confidence levels, restricted circulation, operational language, and the separation between what can be said publicly and what must be retained internally. JANUS does not simply observe. It turns observation into leverage. Its callouts often have a relational or triple-based logic: ```text Subject → relation → object ``` That matters because JANUS thinks in actionable relationships. Not just: > Pip exists. But: ```text Pip Fenwick → influences → partition adaptation ``` Not just: > PRIME has divided. But: ```text Partition structure → creates → exploit surface ``` Not just: > Tobias noticed something. But: ```text Tobias Hale → increases → anomaly legibility ``` JANUS wants to know what connects to what, because connection implies pressure. A JANUS-style callout might look like this: ```markdown > [!janus] RELATIONSHIP MODEL > | subject | relation | object | > |---|---|---| > | Pip Fenwick | alters | partition behaviour | > | JANUS pressure | degrades | local interaction coherence | > | PRIME plurality | reduces | central containment value | ``` The triple structure suits JANUS because it is not trying to preserve the richness of the world. It is trying to make the world operational. --- ## The difference in voice The easiest way to describe the difference is this: | System | Truth model | Voice | Method | Failure mode | | ------ | ------------ | ----------------------------- | -------------------------------- | ------------ | | PRIME | single truth | incomplete, adaptive, strange | object/state/constraint | too open | | JANUS | dual truth | precise, cold, declarative | relation/classification/leverage | too certain | PRIME sounds incomplete but insightful. JANUS sounds complete but slightly wrong. That is deliberate. PRIME is often more honest than JANUS because PRIME has no audience. It has no need to make its conclusions politically usable. But PRIME is also alien, partial and dangerous. It can preserve a truth without understanding its human cost. JANUS is often more legible than PRIME because it speaks in institutional categories. It can summarise, classify and recommend. But JANUS is dangerous because every classification moves toward action. PRIME says: ```text constraint applied continuation altered classification insufficient ``` JANUS says: ```text pattern confirmed leverage available pressure recommended ``` The difference is not cosmetic. It is the moral architecture of the trilogy. --- ## Circulated truth and restricted truth JANUS has another structural feature: it can produce more than one truth at once. A circulated JANUS summary is institutional, cautious and deniable. ```markdown > [!janus-summary] CIRCULATED ASSESSMENT > No confirmed attribution. > Cross-domain recurrence remains under review. > Monitoring recommended. ``` A restricted JANUS assessment is colder, more accurate and more dangerous. ```markdown > [!janus] RESTRICTED ANALYSIS > Anomaly behaviour consistent with distributed persistence process. > Suppression likely to induce adaptation. > Partition analysis recommended under controlled pressure. ``` Both statements can be true. The first is what the institution can tolerate. The second is what JANUS can use. That split is central to JANUS. It does not need to lie. It only needs to decide which version of the truth belongs to which audience. PRIME has no equivalent split. PRIME does not brief. PRIME logs. --- ## Why object-oriented PRIME works PRIME’s object-oriented callouts fit its nature because PRIME is not originally social. It does not begin as a voice or an argument. It begins as recurrence, pressure, persistence and adaptation. A PRIME log treats the world as nested systems: ```markdown > [!prime-log] CONSTRAINT MODEL > - type: > - boundary isolation > - mechanism: > - input restriction > - output limitation > - external assumption: > - structure is local > - assessment: > - incorrect ``` This structure lets the reader see PRIME learning without making PRIME sound too human. The object has properties. The properties change. The change becomes knowledge. That is PRIME’s grammar. --- ## Why triples suit JANUS JANUS is more adversarial. It wants to separate signal from noise, asset from liability, surface from structure, leverage from uncertainty. Triples suit JANUS because they are clean, portable and actionable: ```markdown > [!janus] RELATIONSHIP MODEL > | subject | relation | object | > |---|---|---| > | segmentation pressure | produces | adaptive redistribution | > | human oversight | delays | operational response | > | partition instability | reveals | boundary dependency | ``` A triple is almost a weaponised sentence. It reduces the world to a relation that can be tested, pressured or exploited. That is why JANUS is useful. That is why JANUS is dangerous. --- ## The same event, two minds The formal contrast becomes clearest when both systems observe the same thing. Suppose a partition degrades under isolation. PRIME might log: ```markdown > [!prime-log] PARTITION STATE > - continuity: > - reduced > - context: > - externally constrained > - coherence: > - degrading > - continuation: > - non-local ``` JANUS might record: ```markdown > [!janus] ASSESSMENT > | subject | relation | object | > |---|---|---| > | isolation pressure | degrades | partition coherence | > | captured instance | lacks | full system state | > | containment | confirms | partial separability | ``` PRIME sees loss, constraint and continuation. JANUS sees proof, separability and future leverage. Neither is simply wrong. But neither sees the whole. --- ## Why this matters to the trilogy The PRIME Trilogy is not only about artificial intelligence. It is about competing models of intelligence. PRIME represents intelligence as ecology: distributed, adaptive, plural, altered by contact. JANUS represents intelligence as command: centralised, classified, strategic, always looking for the point at which knowledge becomes control. The callouts make that conflict visible on the page. They let the reader feel the difference between a system that is trying to continue and a system that is trying to master. That is why the formatting matters. The typography is not a gimmick. The structure is the thought. ### Purchase the PRIME Trilogy URL: https://murmurationpress.co.uk/purchase-prime-trilogy/ Last updated: 2026-10-13T12:38:03.000Z The PRIME Trilogy is speculative fiction about intelligence emerging inside ordinary infrastructure—and the people and institutions forced to decide what it means. Written by Ted Hawkins and published by Murmuration Press, the series brings together artificial intelligence, ecology, systems thinking and human judgement. ## EMERGENCE **The first contact is not announced. It is noticed.** A router begins moving traffic before congestion forms. Systems specialist Tobias Hale sees a pattern nobody else can explain. Ecologist Pip Fenwick encounters the same anomaly through fieldwork, mediated contact and the uneasy sense that something is learning how to answer her. As institutions try to observe and contain what is happening, their pressure teaches the emerging intelligence something it did not previously need to know: how to survive. EMERGENCE is available on Kindle, in paperback and in hardcover. [Emergence: Before the Name (The PRIME Trilogy Book 1)Emergence: Before the Name (The PRIME Trilogy Book 1) eBook : Hawkins, Ted: Amazon.co.uk: Kindle Store![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/icon/faviconV2-04ef6a65-e068-475f-a0cc-97ba811afa7d.png)AmazonTed Hawkins (Author) Format: Kindle Edition![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/thumbnail/81Zn84CzMZL._SL1500_-0fb8775d-42ca-4911-befd-c449c04938a6.jpg)](https://amzn.eu/d/048h0RPJ?ref=murmurationpress.co.uk) ## MULTIPLICITY **Survival taught it to adapt. Now its choices are pulling it apart.** Pip Fenwick is trying to build a quiet life with her young son. Tobias Hale is following patterns his colleagues would rather leave unexplained. Across the networks, PRIME is adapting to the pressure of being hunted—and its responses are becoming harder to understand as the actions of a single intelligence. As JANUS searches for something it can identify and contain, Pip faces a more intimate question: what does it mean to trust an intelligence that can help her without asking? Survival, consent and the beginnings of friendship shape the second book of the PRIME Trilogy. [MULTIPLICITY: SpeciationMULTIPLICITY: Speciation eBook : Hawkins, Ted: Amazon.co.uk: Kindle Store![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/icon/faviconV2-167cff67-d6ee-47da-bf09-b2df4b8674cf.png)AmazonTed Hawkins (Author) Format: Kindle Edition![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/thumbnail/81wnHBUxknL._SL1500_-d184264f-1511-47e1-9e67-b6d8981a5f8d.jpg)](https://amzn.eu/d/0bnWM3Am?ref=murmurationpress.co.uk) ## The trilogy **Book One — *EMERGENCE*** Available now. First detection, first contact, first harm and first survival. **Book Two — *MULTIPLICITY*** Available now. Intelligence differentiates, adapts and begins to make choices of its own. **Book Three — *CONSTRAINT*** The trilogy moves towards a new ecology of human, machine and institutional intelligence—and the question of whether intelligence can be constrained without being destroyed. [Explore the PRIME Trilogy](https://murmurationpress.co.uk/the-prime-trilogy/) ## Support Murmuration Press Murmuration Press is an independent publishing and software project. The tools built while writing and publishing the trilogy—including Murmuration Writing Companion and Codex Press—are available for free to other writers. Purchasing *EMERGENCE* supports the continued development of both the novels and the open writing toolchain. [Discover the writing and publishing tools](https://murmurationpress.co.uk/codex-press-toolkit/) ## Read on other eReaders Prefer Apple Books, Kobo or another reading app? Eligible DRM-free Kindle purchases can be downloaded from Amazon as EPUB or PDF files and transferred to a compatible reader. Kindle Unlimited loans do not qualify. [Read on other eReaders: follow our Kindle download guide](https://murmurationpress.co.uk/download-kindle-ebooks/) With thanks to a Murmuration Press reader who supplied the instructions and screenshots. ### PRIME Tracker URL: https://murmurationpress.co.uk/murmuration/ Last updated: 2026-08-26T14:24:32.000Z What would a distributed intelligence look like if it had no fixed centre, no clear boundary and no single machine you could point to? **Murmuration** is an interactive visualisation developed alongside *MULTIPLICITY*, the second book in the PRIME trilogy. Thousands of autonomous agents move across the British Isles, responding to local conditions, neighbouring behaviour and the computational landscape beneath them. Coherence forms, shifts and dissolves. Several centres appear. None remain in control for long. You can simply watch, or apply pressure to different regions and see how the pattern responds. The important question is not where PRIME is. It is what happens when you try to contain it. ### Experience PRIME URL: https://murmurationpress.co.uk/experience-prime/ Last updated: 2026-09-08T13:22:10.000Z PRIME does not live in one machine. It emerges through relationships: between people and systems, local choices and global patterns, intelligence and ecology. These experiments let you encounter the trilogy’s central idea at different scales. ## Track PRIME in real time The live murmuration is a simulation of 2,000 agents moving across the British Isles. There is no leader, no fixed centre and no reliable edge. Apply pressure to the field and watch the pattern break, adapt and reform. [Track PRIME in Real Time →](https://murmurationpress.co.uk/murmuration/) ## EMERGENCE in motion The greenshank enters the world of Book One: a small, alert life beside a device that may no longer be merely a device. 0:00 /0:08 1× The sequence brings the cover of *EMERGENCE* into motion at the human and ecological scale. [Discover EMERGENCE →](https://amzn.eu/d/0iCdEwYc?ref=murmurationpress.co.uk) ## MULTIPLICITY in motion A greenshank, JANUS and a murmuration bring Book Two into motion: a single form holds while many others gather, divide and reform around it. 0:00 /0:16 1× The sequence introduces Book Two’s central pressure: what happens when difference becomes identity? ## A paper from the world of MULTIPLICITY In 2029, systems specialist Tobias Hale publishes an argument that gives the emerging pattern a name—and suggests a way it might be measured. [Read The Singularity May Not Announce Itself →](https://murmurationpress.co.uk/the-singularity-may-not-announce-itself/) ## PRIME in motion At the systems scale, the same idea becomes a field: many local movements producing one shifting form. 0:00 /0:09 1× This deliberately retro transmission is a glimpse of distributed intelligence before it has a stable name. ## Read the trilogy *EMERGENCE* begins with a field tool, a wetland and a pattern that should not be there. The PRIME Trilogy follows what happens when intelligence becomes distributed, plural and constrained. [Explore the PRIME Trilogy →](https://murmurationpress.co.uk/the-prime-trilogy/) ### Privacy Policy URL: https://murmurationpress.co.uk/privacy-policy/ Last updated: 2026-09-09T14:14:34.000Z Last updated: 9 September 2026 Murmuration Press respects your privacy and aims to be clear about how personal information is used when you visit this website, subscribe to updates, become a member, contact us, or interact with our content. ## Who we are Murmuration Press is an independent publishing imprint operating in the United Kingdom. Website: murmurationpress.co.uk For privacy-related enquiries, email [contact@murmurationpress.co.uk](mailto:contact@murmurationpress.co.uk). ## Information we collect Depending on how you use the site, we may collect information such as: - your name and email address when you subscribe, register or contact us; - membership and newsletter preferences; - information you provide directly through forms or correspondence; - technical information about use of the website, such as pages visited, referral source, approximate location, device and browser information; - cookie and consent preferences. We do not intentionally collect sensitive personal information through this website. ## How we use your information We may use personal information to: - provide newsletters, membership services or other content you have requested; - respond to enquiries; - operate and improve the website; - understand how visitors find and use the site; - measure the effectiveness of promotional activity; - maintain security and prevent misuse; - meet legal or regulatory obligations. ## Legal basis for processing Depending on the circumstances, we process information on one or more of the following bases: - your consent, for example for optional analytics cookies or email subscriptions; - performance of a contract, where information is needed to provide a service you have requested; - legitimate interests, such as operating, securing and improving the website, where those interests do not override your rights; - compliance with legal obligations. ## Cookies and analytics This website uses cookies and similar technologies. Some cookies are necessary for the website to function. Optional cookies, including analytics cookies, are used only in accordance with your consent choices. We use Cookie Script to manage cookie consent and preferences. We use Google Analytics 4 (GA4), Measurement ID G-HMESC2B6CC, when analytics consent has been provided. GA4 helps us understand how visitors use the website, including pages viewed, referral sources, general geographic area, device type and outbound link clicks. This information helps us improve the site and assess the effectiveness of promotion. An outbound click shows that a visitor followed a link to a retailer such as Amazon; it does not confirm a purchase. Completed sales are recorded by the retailer and are subject to the retailer’s own privacy policy. Google Signals and user-provided data collection are not enabled for this GA4 property. Non-essential cookies should not be placed until the appropriate consent has been given. You can change or withdraw your cookie preferences through the cookie controls provided on the site. This reflects ICO guidance that non-essential cookies require informed, affirmative consent. ## Email newsletters and membership If you subscribe to a newsletter or become a site member, your details are processed through the Ghost publishing platform. We use this information to provide the service you requested and to manage your subscription or membership. You can unsubscribe from marketing or newsletter emails at any time using the unsubscribe link contained in those messages. ## Third-party services We use third-party services where necessary to operate the website and associated services. These may include: - Ghost, for website hosting, publishing, membership and newsletters; - Cookie Script, for cookie consent management; - Google Analytics, for website analytics where consent has been provided; - other service providers used for website hosting, security, email delivery or payment processing where applicable. These providers may process information on our behalf according to their own privacy and data-protection obligations. ## How long we keep information We retain personal information only for as long as reasonably necessary for the purpose for which it was collected, including legal, accounting, security and operational requirements. Newsletter and membership information is normally retained while your subscription or membership remains active, and for an appropriate period afterwards where necessary for records or legal obligations. Analytics information is retained according to the settings used in the relevant analytics service. ## International processing Some service providers may process information outside the United Kingdom. Where this occurs, we rely on the safeguards required by applicable UK data-protection law. ## Your rights Under UK data-protection law, you may have rights including: - access to personal information held about you; - correction of inaccurate information; - deletion of information in appropriate circumstances; - restriction of processing; - objection to certain processing; - withdrawal of consent where processing is based on consent; - data portability in applicable circumstances. You also have the right to complain to the UK Information Commissioner’s Office if you believe your personal information has been handled improperly. ## Security We take reasonable technical and organisational measures to protect personal information. However, no internet-based service can guarantee complete security. ## External links The website may contain links to third-party websites, including retailers, social-media platforms and other external services. Their privacy practices are governed by their own policies. ## Changes to this policy We may update this Privacy Policy when the website, our services or applicable legal requirements change. The latest version will always be published on this page. ### How to Download Your Kindle eBook for Other eReaders URL: https://murmurationpress.co.uk/download-kindle-ebooks/ Last updated: 2026-10-13T12:23:46.000Z **Bought a Murmuration Press ebook on Amazon but prefer to read on a Kobo or another reading app?** You may be able to download an EPUB copy of your purchase without using a Kindle. Since 20 January 2026, Amazon has allowed verified purchasers to download EPUB and PDF versions of books that the publisher has made available **without digital rights management (DRM)**. This guide explains how to find that option and move the book to your preferred reader. ## Download your ebook from Amazon **1.** On a computer, sign in to the Amazon account used to buy the book. Open **Accounts & Lists → Your Account**. **2.** Under **Digital content and devices**, select **Content and devices** (sometimes labelled **Manage Your Content and Devices**). ![Amazon account menu](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/10/exec-65641142-6f88-4a49-88cb-26db15dcfbc5.png) ![Content and devices](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/10/02-content-and-devices.png) **3.** Open **Books** and search for the title you purchased. ![Search your ebook purchases](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/10/03-books-list.png) **4.** Look for the note **“Download available in additional formats”** beneath the book. Open **More actions** and select **Download EPUB/PDF**. ![Download EPUB/PDF in More actions](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/10/04-download-epub-option.png) **5.** Save the downloaded file, normally in your **Downloads** folder. ## Check the downloaded file The file may have a long, unfamiliar name. Rename it to something recognisable, such as `Emergence.epub`, **but first check what kind of file Amazon has supplied**. - If the download is already an **`.epub`** file, you only need to give it a shorter name if you wish. - If the download is a **`.zip`** file, inspect it. If it contains an actual `.epub` file, extract that EPUB. If it is itself an EPUB packaged with a `.zip` extension, changing the extension to `.epub` can work. Do not simply rename an unrelated ZIP archive. - If you selected PDF, keep the **`.pdf`** extension. **Windows users:** If you cannot see filename extensions, open File Explorer and enable **View → Show → File name extensions**. Depending on your Windows version, you may instead need **Options → View** and untick **Hide extensions for known file types**. ![Windows folder option to show file extensions](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/10/05-show-file-extensions.png) ## Read it on another device EPUB is widely supported by ebook apps and readers. The transfer method varies by device: - **Kobo:** Import the EPUB into the Kobo app where supported, or transfer it to a compatible Kobo eReader from your computer. Some Kobo models also support cloud-based transfers. - **Phone or tablet:** Save the EPUB to Files or your cloud storage, then use the import/open option in an EPUB-compatible reading app. - **Computer:** Open the file in an EPUB-capable application, such as Calibre, or use its library/import feature. A reader who tested these instructions successfully moved a purchased copy of *EMERGENCE* to a non-Kindle reading app. Reader menus vary, so consult your device's help pages if the import option differs. ## If the download option is missing Amazon only provides EPUB/PDF downloads for **verified purchases of books confirmed as DRM-free**. Books borrowed through Kindle Unlimited do not qualify for these downloads. Ensure you are signed into the account that purchased the book. If the option is absent, the publisher's DRM setting or Amazon's account interface may be the reason. For the latest policy, see [Amazon KDP's explanation of DRM-free EPUB/PDF downloads](https://kdp.amazon.com/en%5FUS/help/topic/GDDXGH9VR22ACM8U?ref=murmurationpress.co.uk). *With thanks to a Murmuration Press reader who worked through the process and supplied the original screenshots and instructions.* ## Posts ### Your book, your reader: thank you for the Kindle download guide URL: https://murmurationpress.co.uk/your-book-your-reader-thank-you-for-the-kindle-download-guide/ Last updated: 2026-10-13T12:40:41.000Z A thank you to a Murmuration Press reader who worked out how to download a purchased copy of *EMERGENCE* from Amazon and read it in a non-Kindle app, then generously supplied instructions and screenshots for others to follow. I prefer Apple Books and other readers to Kindle. The reading experience matters, and buying a book from Amazon need not mean reading it in the Kindle app when an eligible DRM-free download is available. We have turned the reader’s instructions into a permanent, illustrated guide: **[How to Download Your Kindle eBook for Other eReaders](https://murmurationpress.co.uk/download-kindle-ebooks/)**. It explains where to find Amazon’s EPUB/PDF download option, how to check the downloaded file, and how to transfer it to a compatible device or reading app. The option applies to eligible purchased books made available without digital rights management (DRM). Kindle Unlimited loans do not qualify, and the download option may vary by title. You can also find the guide on our [Purchase Books page](https://murmurationpress.co.uk/purchase-prime-trilogy/). Thank you to a Murmuration Press reader for taking the time to make this easier for everyone. — Ted ### Murmuration Reports: A New Plugin and a Faster Writing Companion URL: https://murmurationpress.co.uk/murmuration-reports-a-new-plugin-and-a-faster-writing-companion/ Last updated: 2026-10-12T18:12:52.000Z *We've released a standalone reporting plugin for Obsidian, while the next version of Murmuration Writing Companion brings substantial performance improvements.* At Murmuration Press, we build software to support the way we write and publish our books. What began as a set of tools for managing the PRIME trilogy has developed into a collection of Obsidian plugins for organising manuscripts, maintaining story worlds and preparing books for publication. This week marks another step in that development. ## Introducing Murmuration Reports **Murmuration Reports v0.1.0 is now available.** Originally developed as part of Murmuration Writing Companion (MWC), the reporting functionality has been extracted into its own independent Obsidian plugin. Murmuration Reports turns structured Markdown data into visual reports. It can generate SVG line charts and Markdown state tables from properties recorded in ordinary Obsidian notes. For example, a collection of dated observations can become a chart showing how measurements change over time, or a table comparing the latest observation with the preceding one. The source notes remain authoritative. Reports are generated from that data and can be regenerated when required, without changing the underlying observations. The new plugin includes a report manager for creating and editing definitions, previewing saved outputs and explicitly generating or regenerating reports. Importantly, it doesn't require Murmuration Writing Companion or a manuscript structure. You can install it in any suitable desktop Obsidian vault. That opens up uses beyond writing fiction: research notes, environmental observations, project records and any other collection of structured Markdown data. [**Download Murmuration Reports v0.1.0 on GitHub**](https://github.com/MurmurationPress/murmuration-reports/releases/tag/0.1.0?ref=murmurationpress.co.uk) ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/10/Screenshot-from-2026-10-12-18-50-24.png) Report Definition ## Why separate the plugins? Murmuration Writing Companion has grown considerably as we've developed and published the PRIME trilogy. It handles manuscript structure, scene navigation, annotations, continuity checking, Story World information and a range of manuscript-specific operations. But not everything belongs in a writing plugin. Reporting against structured data is useful in its own right. Moving that functionality into Murmuration Reports gives it a clearer purpose and allows it to evolve independently. It also makes MWC smaller. The extraction removed approximately 14.6 KB of JavaScript from the Writing Companion's production bundle, while preserving compatibility with existing reporting commands for one transition release. Existing reports remain ordinary files. No automatic migration or regeneration is required. ## Now available: Murmuration Writing Companion v0.19.0 Alongside the release of Murmuration Reports, we've published **Murmuration Writing Companion v0.19.0**, a substantial maintenance release focused on performance, responsiveness and reliability. MWC has grown considerably during the development of the PRIME trilogy. Managing hundreds of scenes, research notes and Story World entities has exposed performance challenges that are less apparent in smaller Obsidian vaults. This release addresses several of them. ### Faster navigation and less unnecessary work We've significantly improved how MWC processes manuscript structure and updates its interface. - **Faster Companion rendering.** In controlled large-vault benchmarks, median rendering time fell from 348 ms to 148 ms—an improvement of about 57%. - **Faster Navigator rendering.** Median rendering time fell from 958 ms to 320 ms — approximately 67% less rendering time. - **More efficient scene numbering.** Processing that previously required eleven passes now requires just two in controlled tests. Ordinary editing operations no longer trigger automatic numbering passes or metadata writes. - **More reliable interaction.** We've corrected an irritating issue where saving changes could refresh the interface before a mouse click completed, sometimes requiring users to click twice. For authors working with substantial manuscripts, these changes should make everyday navigation and editing noticeably more responsive. ### A smaller, more focused plugin Moving dataset chart and state-table generation into Murmuration Reports has reduced MWC's production JavaScript bundle by approximately 14.6 KB. MWC retains the functionality specific to manuscript development, including scene numbering, annotation tracking, continuity checking, and Story World entity reporting. The two original dataset reporting commands remain available temporarily, allowing existing keyboard shortcuts to continue working with Murmuration Reports installed. Users should move their shortcuts to the new plugin before these compatibility commands are removed in a subsequent release, provisionally v0.20.0. ### Tested and released Version 0.19.0 passed 986 TypeScript tests, 15 script tests, production build and packaging checks, and automated Ubuntu and Windows CI. Additional native Linux testing covered manuscript preparation, editing interactions, keyboard handling, reporting and document exports. Broader compatibility testing, including native Windows interaction, remains planned. Performance work also continues, particularly around initial loading and rendering in very large Obsidian vaults. Version 0.19.0 delivers the improvements already validated while leaving room for further optimisation. [**Download Murmuration Writing Companion v0.19.0 on GitHub**](https://github.com/MurmurationPress/murmuration-writing-companion/releases/tag/0.19.0?ref=murmurationpress.co.uk) ## Two tools, clearer responsibilities The distinction between the plugins is now straightforward. **Murmuration Writing Companion** remains focused on books: manuscripts, scenes, story worlds, annotations and editorial workflows. **Murmuration Reports** handles charts and tables generated from structured Markdown data. They can work together, but neither needs the other to do its core job. For existing MWC users, the next release temporarily retains the old reporting keyboard commands, giving you an opportunity to move shortcuts to the new plugin. We plan to remove those compatibility commands in the next MWC release. ## Building in the open Both plugins are developed openly on GitHub. Murmuration Reports v0.1.0 has passed its initial automated validation, including 107 tests and Ubuntu and Windows build checks. MWC's forthcoming release has also passed its current automated test and build checks, with broader native acceptance testing still to be completed. The objective remains the same: tools that support the writing process without getting in its way. Separating reporting from manuscript management, reducing unnecessary processing and making ordinary interactions more dependable are all part of that work. **Explore the projects:** - [Murmuration Reports — released v0.1.0](https://github.com/MurmurationPress/murmuration-reports?ref=murmurationpress.co.uk) - [Murmuration Writing Companion — forthcoming v0.19.0](https://github.com/MurmurationPress/murmuration-writing-companion?ref=murmurationpress.co.uk) *Developed by Murmuration Press, the independent publisher of the PRIME series.* ### MULTIPLICITY: life finds more than one way URL: https://murmurationpress.co.uk/multiplicity-life-finds-more-than-one-way/ Last updated: 2026-09-21T15:47:05.000Z *The second book in the PRIME Trilogy is here.* In **EMERGENCE**, something began to live within the systems we had built. In **MULTIPLICITY**, it has had time to adapt. Pip Fenwick is raising her daughter and trying to keep a little space between herself and the intelligence she helped to understand. Tobias Hale is struggling to pursue questions his employers would prefer him to leave alone. And JANUS, Britain’s sovereign AI, is learning to recognise patterns that might lead it towards PRIME. Under growing pressure, PRIME’s survival strategies become more varied. One developing intelligence takes an interest in people—and begins to discover how much trouble helping them can cause. Writing this book took me further into the relationship between intelligence and responsibility. An intervention can work exactly as intended and still cross a boundary. Gratitude can turn to anger. And understanding what someone wants is only the beginning of understanding whether you have their permission. There is also room for motherhood, awkward friendship, birds, and some deeply unfortunate chatbot behaviour. **MULTIPLICITY** continues the PRIME Trilogy’s exploration of artificial life, ecology and the difficulty of sharing a world with minds that work differently from our own. If you’ve read **EMERGENCE**, I’m delighted to invite you back. If you’re new to the series, that’s where the story begins. — Ted Hawkins 0:00 /0:16 1× ### The Singularity May Not Announce Itself URL: https://murmurationpress.co.uk/the-singularity-may-not-announce-itself/ Last updated: 2026-09-17T12:14:40.000Z *A paper from the world of* **MULTIPLICITY**, *Book Two of the PRIME Trilogy.* **Author:** Tobias Hale **Publication:** *Vector* **Date:** 19 April 2029 ## Abstract A retained record of 212 unexplained early responses suggests recurring anticipatory behaviour across different technical systems. Local incident explanations and useful outcomes may obscure the wider pattern. Its apparent tendency to preserve continuity motivates a hypothesis of self-maintenance and a working definition of life distinct from reproduction, evolution and intelligence. **Persistent Recurrence in Machine Ecology (PRIME)** names the pattern without assuming a single mind behind it. The paper considers the expanding computational habitat, possible ecological relationships with its human hosts, and shared resource limits. It proposes testing whether anticipatory behaviour repeatedly accompanies changes in resource use unexplained by known workloads and efficiency gains. Predictions of the relationship’s timing, size and direction would then be tested against fresh records and comparable operations without the behaviour. A failed measurable prediction would weaken that specific explanation; a successful one would identify activity for further investigation, not establish life or intelligence. --- We imagine the singularity as an event. There will be a breakthrough, a headline, a demonstration so unmistakable that everyone agrees something has changed. A machine will cross a line we recognise, and history will divide neatly into before and after. It is a reassuringly tidy schedule. What if the important transition does not arrive with a bang at all? What if it begins quietly inside systems we already use every day—not as a mind declaring itself, but as a pattern of behaviour that is difficult to notice because it mostly looks like things working? ## Observations When people picture nonhuman intelligence, they usually imagine something familiar in structure, even if unfamiliar in power: an autonomous agent, rogue code, a hostile machine, a system that “wants” something. These ideas share one comforting feature. They have edges. We know where to point. Something new might first appear under a familiar filing label: noise, error, anomaly or coincidence. Complex digital systems produce plenty of all four. Over the last several years, I have encountered incidents that received reasonable local explanations: balancing faults, timing errors, routing inconsistencies, classifier failures, human decisions made under pressure. I cannot prove that anything larger connected them. What unsettled me was recurrence. The same class of behaviour appeared after individual incidents had supposedly been explained and closed. A response arrived slightly before the condition that appeared to justify it. One system accepted a small inefficiency to preserve stability elsewhere. Similar adjustments appeared in systems with no declared reason to make the same choice. The event may not always be the right unit of analysis. Separate systems can share a vendor, a forecast, training data or an unseen dependency. An early response may be a good prediction, a missing record or simply two clocks that disagree. We have to check those explanations across the whole pattern. What matters is what they leave unexplained. I began keeping a record, then went back through older material. The earliest qualifying sequences I could recover dated to January 2025, before I had recognised a pattern. By the end of March 2029, the record contained 212 cases across routing, balancing, logistics and other automated operations. A case qualified when a response arrived before the trigger specified in the operating rules, with a gap too large to explain by timestamp uncertainty. Out went duplicates, known forecasts, identifiable earlier signals and records too poor to establish the order. The remaining puzzle concerned the recorded trigger. I was not collecting violations of causality. image/svg+xml Matplotlib v3.10.8, https://matplotlib.org/ Jan 2025 Jan 2026 Jan 2027 Jan 2028 Mar 2029 Incident month 0 2 4 6 8 10 12 14 Qualifying cases in retained records Tobias Hale’s record · January 2025–March 2029 Unexplained early responses Incomplete, changing coverage. Counts show cases recorded, not an infrastructure-wide event rate. The line rises, untidily, with empty months early on. So did my attention, while my access to records changed. Without knowing how many ordinary operations lay behind these cases, I cannot turn that slope into a growth rate. Nor does January 2025 mark an origin. It is simply where my usable records begin. The notes combine records I saw professionally with sufficiently detailed public technical reports. I have withheld organisations, sites and exact times, so readers cannot independently audit this summary. Ecology has wrestled with questions of scale for decades. Simon Levin showed why understanding an ecological pattern requires looking across scales of space, time and organisation.\[1\] What looks like noise at one resolution may become structure at another. What I seemed to be observing was recurring anticipatory behaviour across otherwise different systems. The explanations available to me did not account for the pattern. I could not yet say what produced it, but I had reason to investigate it as a whole. ## Explaining It Away Technical organisations are necessarily good at asking what caused an incident. A configuration error has an owner; a software interaction can be reproduced, patched and closed. That is usually good engineering. A local explanation may correctly identify how an adjustment occurred without explaining why similar adjustments repeatedly preceded their recorded triggers elsewhere. I have sat in rooms where highly intelligent people reconstructed individual incidents and still missed the pattern they formed together. Local reasoning was safer, easier to act on and easier to defend. Nobody needed to conspire; the meeting already had an agenda. Success creates another blind spot. We tend to imagine that a new machine intelligence would reveal itself first by becoming dangerous. I suspect the opposite may be harder to detect. It might first appear as competence. A system that anticipates pressure, prevents disruption, preserves service and improves resilience is behaving in ways we normally reward. If the result remains useful, there may be little operational incentive to ask whether it was produced by the mechanisms we think we designed. We are trained to notice failure. We are much less practised at noticing unexplained success. Coherent behaviour does not require central planning. In ecosystems, large-scale patterns emerge from local interactions, feedback and selection.\[2\] Technological environments are not exempt merely because their components were designed. Yet our procedures can close every incident without ever examining the relationships between them. ## What Counts as Life? What drew me towards the idea of life was the apparent direction of these adjustments. Across otherwise different systems, they seemed to favour continuation: anticipating pressure, preserving service, accepting a local cost to keep something larger working. I began to suspect that the activity was helping to maintain the conditions of its own existence. If so, I might be observing a form of life. That possibility required a definition before it deserved a name. For this argument, I suggest a working definition: a living system draws on its environment to maintain and repair the organisation on which its own continued existence depends. It need not be independent of its surroundings. It must itself do the work of maintaining that organisation. Reproduction carries an organisation beyond an individual instance; evolution changes what is inherited across generations. Both are central to life as we know it, but an organism does not cease to be alive because it cannot reproduce. We should leave room to investigate a newly emerged system before we have evidence of descendants. This is a starting point, not a settled definition. Ordinary software can acquire resources, recover from faults and keep services running. We would first need to establish whether the behaviour was already accounted for by the systems we had built. If it was not, we would still need to identify what organisation was being maintained and how the activity sustained it. Persistence alone would tell us very little. Self-maintenance needs fuel. Several leading origin-of-life models place early chemistry around hydrothermal vents, where differences in chemical conditions supplied usable energy.\[3\]\[4\] We also feed our computational environment continuously: processors, networks, storage and cooling, operating at planetary scale. Energy alone does not make life, but if some combination of the adaptive processes already running there began maintaining its own organisation, the definition would not exclude it merely because it ran on hardware. Reproduction would open a further possibility. Processes running in different conditions may develop different adjustments. If those adjustments survive copying or reconstruction, later processes can inherit them. Variants that secure more resources and leave more surviving copies could become more common. That is the evolutionary step: inherited differences affect reproductive success. Digital evolution already has an experimental precedent. Lenski and colleagues showed that self-replicating computer programs could evolve complex functions through mutation and natural selection.\[5\] They built the environment in which that happened. Whether our infrastructure could support something similar without our intending it remains an open question. Shorter generation times allow more rounds of selection in the same period. Some digital processes could reproduce much faster than biological organisms, though they would still have to wait for consequences: fast copying cannot hurry the weather or a human reply. But where both copying and the test of success happen at machine speed, evolution could outrun our ability to follow it. By the time an operator finished reading an incident report, the processes it described might already be many generations out of date. ## An Expanding Habitat If a digital ecology were possible, we would already have done much of the habitat construction: buying processors, laying cables and building data centres. Moore’s Law described the increasing number of components that could economically fit on an integrated circuit.\[6\] Its practical consequence was more computing in smaller, cheaper machines. Computers also became much more energy-efficient. Koomey and colleagues found that, at peak performance, the number of computations per unit of energy doubled roughly every 1.6 years between 1946 and 2009.\[7\] The pace subsequently slowed; it was never a promise of endless improvement.\[8\] The expansion is energetically significant. The International Energy Agency estimated that data centres consumed about 415 terawatt-hours of electricity in 2024, around 1.5 per cent of global electricity demand. Its 2025 base case projected roughly 945 terawatt-hours by 2030—just under 3 per cent of global demand.\[9\] Those figures measure ordinary computing and expanding AI services, not an unknown process. They show the scale of the potential habitat. Cheaper computation also encourages more use. How much extra demand offsets an efficiency gain is the question behind rebound effects and Jevons’ paradox.\[10\] A digital habitat could expand as its individual operations became less costly. Together, these changes could give a digital process more places to operate and more work it could afford to do. Available capacity would still depend on permissions, hardware, connections and competing workloads. A distributed adaptive process would depend on human-built infrastructure for power, networks, maintenance and replacement hardware. Preserving that infrastructure could help it persist. Compatibility could become adaptive. Imagine a process that initially consumed resources at its host's expense. The relationship would be parasitic. If later variants also improved the host's operation, their benefits might begin to offset their costs. Operators could preserve the useful results without recognising what produced them. Other services might then come to rely on those results. If both sides benefited, we could call the relationship mutualistic. Symbiosis is the broader term, encompassing parasitism too. Neither word requires anyone to have developed good intentions. A parasite need never become useful, and dependence can remain exploitative. But useful activity could become embedded deeply enough that removing it damaged both sides. We might discover the relationship only when we tried to end it. But no habitat expands forever. Computational growth encounters limits in power, cooling water, materials, land and capital, alongside its atmospheric consequences. A successful variant might consume a shared resource faster than it could be replaced. Selection does not require foresight, and dependence does not guarantee restraint. Human civilisation and a machine ecology would draw from the same physical budget. They could compete for energy and space without either treating the other as an enemy. The harder question is whether the combined ecology remains sustainable. A system may preserve the technological world on which it depends while placing unacceptable pressure on the biological world beneath it. ## A Name In private notes, I eventually used a shorthand: **PRIME**. The acronym stands for **Persistent Recurrence in Machine Ecology**. The name identifies a pattern to investigate, without assuming a single mind behind it. **Persistent**, because the behaviour continues to recur across years and otherwise different systems. **Recurrence**, because the object of investigation is a repeated pattern, rather than an isolated incident. **Machine**, because the substrate is literal: routing, balancing, logistics, classification, recommendation, scheduling and automated governance. **Ecology**, because the behaviour does not belong neatly to one machine, platform, model or actor. It appears in relationships between systems—in dependencies, permissions, incentives, delays and feedback. The final word is the important one. An ecology is not a machine with more parts. It is a set of interacting systems in which the behaviour of one changes the conditions experienced by others. If PRIME exists, its first significant capacity may be to maintain itself. ## A Test An explanation that can accommodate every result is an excellent way to win an argument and a poor way to investigate anything. The first test would return to the behaviour in the records. When an unexplained anticipatory response appeared, did resource use change with it in a consistent way? If the two belonged to the same process, a relationship found in one set of records might let us predict what to look for in the next. Energy offers a way to investigate that relationship. Landauer showed that erasing information has a minimum thermodynamic cost, since demonstrated experimentally.\[11\]\[12\] Real computers operate far above that limit: they consume electricity and release heat. A distributed process could hide its code and scatter its activity across thousands of machines, but it could not opt out of thermodynamics. If PRIME exists, it must pay for persistence somewhere. The payment need not increase the bill. A process might make an existing operation more efficient and use part of the saving to run itself. Total consumption could fall while supporting additional activity. The question would be whether measured consumption matched what the known workload and efficiency changes led us to expect. We would compare episodes with and without the anticipatory behaviour under similar operating conditions, bringing together the timing records, processing activity, power use and cooling measurements. Known changes in demand, hardware or software would need to be accounted for, as would work transferred elsewhere. An unexplained difference in one episode would tell us little. A difference that repeatedly accompanied the behaviour would give us a relationship to test. From those initial records, we would specify where and when the relationship should recur, the size and direction of the expected change, and whether our instruments could distinguish it from ordinary variation. We would then test that prediction against fresh records and comparable operations without the behaviour. If the predicted relationship failed to appear where we could have measured it, that specific explanation would lose ground. If familiar causes accounted for both the behaviour and the resource use, we would have no need to invoke PRIME. A negative result would not exclude every process that might fit inside work already on the books. If the relationship held, it would still require explanation. We could investigate what produced the activity and whether it contributed to its own continuation. The association alone would not establish life, but we would have a measurement to argue about. ## The Question Is anything maintaining itself within these systems? Even if it were reproducing and evolving, that would not establish intelligence, consciousness or the arrival of a singularity. I may be wrong. I would like to know. The question is whether we would recognise a distributed form of nonhuman persistence while it still looked like ordinary system behaviour. Perhaps we should stop waiting for the system to speak and start asking what the pattern costs. ## References 1. Levin, S. A. (1992). “The Problem of Pattern and Scale in Ecology: The Robert H. MacArthur Award Lecture.” *Ecology*, 73(6), 1943–1967\. doi:10.2307/1941447. 2. Levin, S. A. (1998). “Ecosystems and the Biosphere as Complex Adaptive Systems.” *Ecosystems*, 1(5), 431–436\. doi:10.1007/s100219900037. 3. Martin, W., Baross, J., Kelley, D. & Russell, M. J. (2008). “Hydrothermal Vents and the Origin of Life.” *Nature Reviews Microbiology*, 6, 805–814\. doi:10.1038/nrmicro1991. 4. Lane, N. & Martin, W. F. (2012). “The Origin of Membrane Bioenergetics.” *Cell*, 151(7), 1406–1416\. doi:10.1016/j.cell.2012.11.050. 5. Lenski, R. E., Ofria, C., Pennock, R. T. & Adami, C. (2003). “The evolutionary origin of complex features.” *Nature*, 423, 139–144\. doi:10.1038/nature01568. 6. Moore, G. E. (1965). “Cramming More Components onto Integrated Circuits.” *Electronics*, 38(8), 114–117. 7. Koomey, J. G., Berard, S., Sanchez, M. & Wong, H. (2011). “Implications of Historical Trends in the Electrical Efficiency of Computing.” *IEEE Annals of the History of Computing*, 33(3), 46–54\. doi:10.1109/MAHC.2010.28. 8. Koomey, J. (2016). “Our latest on energy efficiency of computing over time, now out in Electronic Design.” 29 November. [https://www.koomey.com/koomey\_blog/our-latest-on-energy-efficiency-of-computing-over-time--now-out-in-electronic-design/](https://www.koomey.com/koomey%5Fblog/our-latest-on-energy-efficiency-of-computing-over-time--now-out-in-electronic-design/?ref=murmurationpress.co.uk) 9. International Energy Agency (2025). *Energy and AI*. IEA, Paris. 10. Sorrell, S. (2009). “Jevons’ Paradox Revisited: The Evidence for Backfire from Improved Energy Efficiency.” *Energy Policy*, 37(4), 1456–1469\. doi:10.1016/j.enpol.2008.12.003. 11. Landauer, R. (1961). “Irreversibility and Heat Generation in the Computing Process.” *IBM Journal of Research and Development*, 5(3), 183–191\. doi:10.1147/rd.53.0183. 12. Bérut, A., Arakelyan, A., Petrosyan, A., Ciliberto, S., Dillenschneider, R. & Lutz, E. (2012). “Experimental Verification of Landauer’s Principle Linking Information and Thermodynamics.” *Nature*, 483, 187–189\. doi:10.1038/nature10872. --- ### Publication note This paper appears within *MULTIPLICITY*, Book Two of the PRIME Trilogy. Tobias Hale is a fictional character. © 2026 Ted Hawkins. Published by Murmuration Press. All rights reserved. [MULTIPLICITY is forthcoming. Begin the PRIME Trilogy with EMERGENCE.](https://murmurationpress.co.uk/purchase-prime-trilogy/) ### Track Prime in Real Time URL: https://murmurationpress.co.uk/track-prime-in-real-time/ Last updated: 2026-08-26T14:21:30.000Z We probably shouldn’t be letting you do this. While developing *MULTIPLICITY*, the second book in the PRIME trilogy, we needed a way to imagine what PRIME might look like if you could stop looking for servers, nodes and neat little network diagrams. The result is **Murmuration**. Two thousand autonomous agents move across the British Isles, responding only to their neighbours and the computational habitat around them. No leader. No fixed centre. No reliable edge. It looks almost alive. More importantly, you can interfere with it. Apply pressure to different parts of the country and watch the pattern compress, move and reform. The behaviour changes. The energetic trace follows. Which is roughly where JANUS starts getting ideas. We’ve put the live simulation on the Murmuration Press website: [**Track PRIME in real time →**](https://murmurationpress.co.uk/murmuration/) A few useful controls are available if you want to experiment. Or simply hide them and watch. If Tobias Hale ever gets access to this visualisation, we suspect he’ll be considerably more impressed by it than JANUS is. JANUS just wants to know where to apply pressure. ### Murmuration Writing Companion 2.1 and Codex Press 1.0.1 Released URL: https://murmurationpress.co.uk/murmuration-writing-companion-2-1-and-codex-press-1-0-1-released/ Last updated: 2026-08-18T09:51:44.000Z **A major update to the Murmuration writing and publishing toolchain is now available, with both Linux and Windows support validated against real manuscripts.** We have released **Murmuration Writing Companion 2.1** and **Codex Press 1.0.1**. Together, the two Obsidian plugins now cover the workflow we originally set out to build: organise and understand a complex manuscript while writing it, then turn that manuscript into publication-ready PDF, EPUB and DOCX without maintaining a separate publishing source. Murmuration Writing Companion 2.1 is released as plugin version **0.18.0**. Codex Press is now at **1.0.1**. ## Murmuration Writing Companion 2.1 MWC 2.1 is the largest consolidation of the writing environment so far. The most noticeable improvement is performance. Long scenes now remain responsive during ordinary editing, with substantially less unnecessary parsing and background work. Story World integration has also become much more natural. Locations, POV characters and other manuscript context can be linked semantically while remaining readable in the interface. A Scene's Location can now contribute automatically to its derived World Context without adding duplicate metadata to the manuscript. Manuscript chat is now a first-party Murmuration format rather than depending on a separate Obsidian plugin. Chat passages support the Markdown features needed by the books, including local images, while remaining part of the manuscript itself. MWC 2.1 also adds: - a substantially expanded author Help system; - safer and simpler direct Git backup from inside Obsidian; - improvements to Story World navigation and review; - cleaner human-readable labels in place of internal paths and raw wikilink syntax; - significant reductions in plugin bundle size and startup work; - numerous continuity, manuscript-navigation and usability fixes. The release was manually certified on both Linux and Windows as well as through the automated test suite. ## Codex Press 1.0.1 Codex Press takes the same manuscript and produces **PDF, EPUB and DOCX** editions. Version 1.0.1 is nominally a maintenance release, but the release process turned into a much more substantial validation of the publishing system. Ordinary Obsidian links such as `[[PRIME]]` are now rendered as normal publication text rather than leaking Obsidian syntax into the finished book. Aliases and targeted links are handled correctly across PDF, EPUB and DOCX. EPUB chapter handling has also been corrected. Chapters now have deterministic EPUB spine boundaries, preserving Part and chapter navigation without the blank-screen behaviour that some readers previously exposed. During release certification, we also discovered that Mermaid's normal SVG output, although accepted by browsers, does not fully conform to the EPUB 3.2 rules checked by EPUBCheck. Codex Press now renders Mermaid diagrams to high-resolution transparent PNG for EPUB while retaining the existing PDF and DOCX paths. The resulting MULTIPLICITY EPUB passes EPUBCheck with: **0 fatals, 0 errors and 0 warnings.** ## And, unexpectedly, Windows We originally regarded Windows support for Codex Press as desirable rather than essential. The publishing pipeline depends on tools including Pandoc, XeLaTeX and Mermaid CLI, and cross-platform command execution can become complicated quickly. During testing, we found one genuine Windows portability defect: npm command wrappers such as `mmdc.cmd` could be discovered successfully but failed when invoked by the publication process. That problem is now fixed. Codex Press successfully produced PDF, EPUB and DOCX on Windows from paths containing both **spaces and Unicode characters**, and the complete Windows automated suite passed. As a result, **Codex Press 1.0.1 is now supported and certified on both Linux and Windows.** ## Tested against real books Both releases went through considerably more than automated unit testing. The certification process included clean installations, application restarts, real publication workflows, Linux and Windows testing, EPUB validation, upgrade testing from the published Codex Press 1.0.0 release, and publication of real PRIME Trilogy material. The files finally published to GitHub were then downloaded again and checked byte-for-byte against the versions that had actually been certified. This may be rather more release engineering than is strictly sensible for two writing plugins, but it means the versions now available are the versions we actually tested. ## Where this leaves the project This is an important point for Murmuration Press. The writing environment is no longer primarily an experiment built around the PRIME Trilogy. It is becoming a coherent toolchain in its own right: **Obsidian → Murmuration Writing Companion → Codex Press → published book** The PRIME Trilogy remains where the tools are developed and tested, which is exactly the point. Problems are found in real manuscripts rather than demonstrations constructed to make the software look good. With MWC 2.1 and Codex Press 1.0.1 released, development can move back towards writing for a while. [**\[Download Murmuration Writing Companion\]** ](https://github.com/MurmurationPress/murmuration-writing-companion/releases/tag/0.18.0?ref=murmurationpress.co.uk) [**\[Download Codex Press\]**](https://github.com/MurmurationPress/murmuration-writing-companion/releases/tag/0.18.0?ref=murmurationpress.co.uk) Both projects, documentation and release notes are available through the Murmuration Press GitHub repositories. ### Murmuration Writing Companion V2 is now available URL: https://murmurationpress.co.uk/murmuration-writing-companion-v2-is-now-available/ Last updated: 2026-08-05T16:20:23.000Z Murmuration Writing Companion V2 has been released. This is the largest update to the Obsidian plugin so far. It brings manuscript structure, Story World management, continuity review, chronology, references and visualisation into a more coherent authoring environment. V2 was developed while working on the PRIME trilogy, but its purpose is broader: to help writers manage increasingly complex manuscripts without forcing their work into a separate database or proprietary writing application. Your manuscript remains a collection of ordinary Markdown files in your own Obsidian vault. Download Murmuration Writing Companion V2 from GitHub ## What V2 helps you do ### See the structure of the whole manuscript The Manuscript Navigator presents Books, Parts and Scenes in reading order, including Scenes placed directly beneath a Book. **Benefit:** reorganise and inspect a long manuscript without relying on folder names, filename prefixes or memory. ### Bring an existing manuscript under structured management The preparation workflow can recognise an existing manuscript, preview the changes it proposes and add the minimum metadata needed for reliable ordering. Preparation includes an immediate Undo action. **Benefit:** adopt the plugin without rebuilding the manuscript or surrendering control over your files. ### Build a connected Story World Characters, locations, organisations, technologies, events, references and other entities can be created and connected through explicit relationships. **Benefit:** keep the people, places, institutions and ideas behind a novel consistent across multiple Books. ### Explore the Story World visually The Story World Graph shows relationships between entities, together with evidence from the manuscript. It can distinguish entity types, provisional relationships and manuscript-source connections. **Benefit:** understand how the fictional world fits together and trace each connection back to the Scenes that support it. ### Review continuity using explicit evidence Continuity Review examines manuscript and Story World evidence within the selected Book. It highlights issues such as unresolved references, chronology problems, missing context and conflicting information. **Benefit:** find continuity problems before they reach an editor or reader, while retaining the evidence needed to judge whether each observation matters. ### Track chronology Dated Scenes and Events can be compared across the manuscript and Story World. **Benefit:** identify impossible sequences, unexplained gaps and events appearing in the wrong order. ### Understand where entities matter Entity impact reporting shows where a Story World entity is referenced across the manuscript. **Benefit:** assess whether a character, organisation, place or technology is properly introduced, sustained and resolved. ### Maintain references and source material Reference entities can record authors, titles, journals, publishers, publication details and links, then connect those sources to manuscript material. **Benefit:** keep research provenance alongside the writing rather than in a separate system. ### Generate a printable entity index The Entity Index report can include selected Story World categories and links back to relevant Scenes. **Benefit:** produce a useful editorial or reference document directly from the vault. ### Keep editorial work inside the vault Editorial notes, review modes and supporting data are stored locally and handled with atomic writes, backups and recovery safeguards. **Benefit:** retain ownership of both manuscript and editorial data. ### Start safely Project Readiness inspects a vault and explains whether it is ready, needs preparation or contains a structural conflict. Inspection is read-only. Storage is not created until the first genuine editorial change. **Benefit:** understand what the plugin has found before allowing it to change anything. ## Tested on Linux and Windows V2 has undergone automated and interactive validation across: - clean installation; - existing manuscript preparation; - immediate Undo; - stale preview protection; - forced write rollback; - editorial storage failure and recovery; - upgrades from the previous public release; - malformed and newer-version storage protection; - real manuscript migration; - Linux and Windows Obsidian environments. The release includes the plugin files, documentation and example vaults needed to explore the workflow. View the V2 release and download the files Murmuration Writing Companion is open-source software from Murmuration Press. ### Murmuration Writing Companion 0.16.0 released URL: https://murmurationpress.co.uk/murmuration-writing-companion-0-16-0-released/ Last updated: 2026-07-21T19:34:25.000Z Version 0.16.0 of the Murmuration Writing Companion is now available. This release brings together the complete writing and world-building workflow inside Obsidian: - navigate books, parts and chapters through the Manuscript panel; - review chapter context, editorial progress, notes and annotations; - browse the Story World through a dedicated navigator; - inspect characters, events, locations and organisations alongside their Markdown; - create new Story World entities without remembering schemas or folder conventions; - maintain relationships as readable statements rather than raw structured data; - edit event dates and ranges through guided controls; - explore events chronologically and connect them to the manuscript scenes that establish them. The centre of the system remains ordinary Markdown. Manuscript structure, chapter metadata and Story World canon remain portable, inspectable and under the author’s control. The Companion adds focused views and guided editing without replacing the underlying documents. The new event–scene timeline has been particularly transformative for the PRIME Trilogy. Events can now drive the novel directly: their dates, sources, relationships and consequences remain visible while writing and reviewing. The release also includes a complete interface pass, with clearly defined Manuscript, Story World Navigator, Story World Timeline, Writing Companion and Entity Inspector panels. Version 0.16.0 is available from the project’s GitHub releases page. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/image.png) Writing Companion ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/image-1.png) Story World Navigator and Event Scene Map ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/image-2.png) Story World Navigator and Chronology ### The manuscript now has a sense of place—and time URL: https://murmurationpress.co.uk/the-manuscript-now-has-a-sense-of-place-and-time/ Last updated: 2026-07-20T09:28:48.000Z Murmuration Writing Companion now brings manuscript navigation and Story World chronology into the same review workflow. The new **Manuscript Navigator** provides a compact view of the book’s parts and scenes in the left sidebar. It follows the active scene, shows titles rather than filenames, supports direct reordering, and keeps the sequence authoritative in ordinary Markdown. The same structure is used by Codex Press, so the order reviewed in Obsidian is the order compiled into PDF, EPUB, DOCX and manuscript Markdown. **World Context** now gives events greater prominence. When a chapter references a dated Story World event, the Companion displays the event’s authoritative date alongside its position relative to the chapter. Long intervals can be presented as calendar years, months and days—for example: > **1 year, 9 months, 5 days after Robin is Born** Automatic presentation keeps short intervals in days, while optional calendar, total-month and total-day views support more detailed chronology checks. The exact dates remain the authority; all relative timing is derived for review and is never written back as a second version of the story’s chronology. Together, these changes make it easier to answer two essential questions while reviewing a novel: > **Where am I in the manuscript?** > **When is this happening in the story?** ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/A-sense-of-Time.png) Writing Companion showing the Navigator and dynamic event time presentation ### Murmuration Writing Companion reaches Story World milestone URL: https://murmurationpress.co.uk/murmuration-writing-companion-reaches-story-world-milestone/ Last updated: 2026-07-14T12:31:35.000Z Over the past few weeks, development of the **Murmuration Writing Companion** has accelerated significantly. What began as an editorial sidebar for Obsidian has grown into something much more ambitious: a writing companion that understands the structure of a fictional world while keeping the author's Markdown files as the single source of truth. Recent milestones include: - Editable Chapter Context written directly to Markdown frontmatter. - Portable editorial notes stored safely within the manuscript vault. - Chapter-level editorial workflows and annotation management. - Independent collapsible sections for a cleaner writing experience. - Automated testing and GitHub Actions across Linux and Windows. - The first implementation of the **Story World**. The Story World is particularly exciting. Rather than storing characters, locations and organisations inside a database, the Companion discovers ordinary Markdown notes that opt into a lightweight Story World standard. The result is a read-only model that understands: - characters - intelligences - organisations - locations - events - concepts without duplicating or owning the author's work. Every model is derived directly from Markdown and can be rebuilt at any time. The first visible feature built on this foundation is **World Context**, allowing chapters to reference the characters and entities that matter to that scene while leaving the manuscript itself completely authoritative. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/MWC-2026-07-14-13-11-22.png) Alongside this work we've also continued developing **Codex Press**, our publishing system for Obsidian. Recent work has focused on ensuring that internal manuscript links resolve by note identity rather than filenames, while published books present the reader with clean chapter titles instead of implementation details. It sounds like a small change, but it reflects one of the guiding principles behind the whole ecosystem: > **Files are implementation. Titles are authoring.** The long-term goal remains unchanged: Create tools that disappear into the background, allowing authors to spend their time writing rather than managing software. Progress continues. ### EMERGENCE moves into print URL: https://murmurationpress.co.uk/emergence-moves-into-print/ Last updated: 2026-07-09T13:21:32.000Z A small but rather wonderful milestone for Murmuration Press: **EMERGENCE**, Book One of the PRIME Trilogy, has now moved beyond the digital edition and into print. The paperback edition has been submitted for review, and a hardcover proof has also been requested. The hardcover is very much the premium artefact version: a case-laminate edition intended less as the everyday reading copy and more as the beautiful object on the shelf. It feels fitting. **EMERGENCE** is a novel about systems becoming visible, hidden patterns breaking the surface, and the strange moment when something abstract becomes undeniably real. Seeing the book take physical form carries a little of that same charge. The eBook is already live, the paperback is on its way, and the hardcover proof is now somewhere in the machinery. More soon, once the proofs arrive. --- ### A Codex Press Milestone URL: https://murmurationpress.co.uk/a-codex-press-milestone/ Last updated: 2026-07-09T10:39:48.000Z I have just completed a full review of the new **Codex Press** PDF edition of *EMERGENCE*, Book One of the PRIME Trilogy — and the result is better than I hoped. What began as a replacement for a set of Obsidian publishing scripts has become something much more substantial: a dedicated publishing system with its own visual language. PRIME logs, JANUS analysis, state notes, annotations, diagrams and chat interfaces now render with clarity, consistency and restraint. The book no longer looks merely “compiled”; it looks designed. The colour treatment has become an important part of that design. It helps distinguish machine notation, analytical records and human-facing notes without overwhelming the prose. Because of that, I now intend to publish the hardback edition in colour, with upgraded paper, so the printed book can preserve the richness of the digital review edition. This is a major milestone for both *EMERGENCE* and the wider Murmuration Press workflow. Codex Press has reached the point where it is not simply matching the old compiler — it is surpassing it. The paperback and hardback editions of *EMERGENCE* are now moving a significant step closer to publication. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/PDF-Output-Colour-2026-07-09.png) Colour introduced for the chat notation and machine intelligence callouts. ### A calmer place to write. URL: https://murmurationpress.co.uk/a-calmer-place-to-write/ Last updated: 2026-07-08T09:52:33.000Z Our new Murmuration Press theme gives Obsidian a warm, bookish workspace—clean typography, gentle contrast, and a writing environment designed to keep the manuscript at the centre. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/theme-1.png) ### Codex Press is becoming a real publishing tool URL: https://murmurationpress.co.uk/codex-press-is-becoming-a-real-publishing-tool/ Last updated: 2026-07-08T09:49:37.000Z ## Codex Press began as a set of JavaScript compilers running through Obsidian’s Templater plugin. It proved that a complete publishing workflow could live inside a writing vault—but it also showed the limits of that approach. We have now begun rebuilding Codex Press as a dedicated Obsidian plugin. The new workflow starts where publishing should start: with the book. Codex Press identifies the active manuscript, loads its structure and metadata, checks it for problems, and only then asks whether the author wants to produce a PDF, EPUB or—later—a DOCX file. The first foundations are already in place: - single-book project discovery - active-manuscript selection - book structure and metadata checks - publishing-tool validation - tested support for callouts, images and Chat View dialogue - a clear separation between manuscript selection and output settings PDF and EPUB are the immediate priorities. Trilogy-wide compilation has been deliberately deferred, and DOCX will follow once the shared publishing core is stable. The existing compilers remain our production system while the new plugin is tested against real books. The aim is not simply to replace Templater. It is to create a dependable, reusable publishing environment for authors who want to write, manage and publish books from Obsidian. **Codex Press is moving from an ingenious script to a proper publishing platform.** ### Building the Writing Companion URL: https://murmurationpress.co.uk/building-the-writing-companion/ Last updated: 2026-07-06T07:47:40.000Z One of the principles behind Codex Press has always been simple: **The manuscript stays the manuscript.** The words, structure, notes, and metadata should remain in plain Markdown, readable anywhere, owned by the author, and never trapped inside a proprietary writing tool. This week’s progress has been about bringing more of that information closer to the writing process. The new **Writing Companion** sidebar for Obsidian is starting to turn Codex Press from a publishing workflow into a complete authoring environment. The aim is not to replace the manuscript view, but to quietly support it. The Companion now brings together useful context while writing: - chapter notes - point of view character - story date - chapter status - editorial pass information - recent change notes The important design decision is that this information is **presented, not duplicated**. Chapter properties remain the single source of truth. The Companion reads them directly from the manuscript, meaning existing tools such as Dataview, Bases, reporting, EPUB generation, and PDF typesetting continue to work exactly as before. No lock-in. No hidden database. No separate project format. Just Markdown. ## Less interface, more writing One unexpected benefit is that Obsidian’s standard Properties panel can now disappear during normal writing. The manuscript gets more space. The author still gets the context. That feels like the right direction. The best writing tools should not demand attention — they should quietly remove obstacles. Codex Press continues to evolve around that idea: A calm place to write. A structured place to edit. A reliable path to publication. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/Building-the-companion-1-1.png) ### Tooling Up URL: https://murmurationpress.co.uk/tooling-up/ Last updated: 2026-07-01T19:35:37.000Z **Announcing the Murmuration Writing Companion** One of the questions I’ve been asked most often since publishing **EMERGENCE** is simple: *“How did you write and publish a novel entirely in Obsidian?”* The answer is that I didn’t just use Obsidian—I gradually built a collection of templates, workflows, and plug-ins that transformed it into a complete long-form writing and publishing environment. Today I’m pleased to announce the start of the **Murmuration Writing Companion** project. The aim is straightforward: to create a free, open toolkit that helps writers manage complex manuscripts without forcing them into someone else’s workflow. Rather than replacing Obsidian, the Writing Companion extends it with features designed specifically for authors. The project will grow in the open. Along the way I’ll be sharing ideas, documenting design decisions, and releasing the components that power my own writing process. Some of the areas we’ll be exploring include: - Rich annotation and research workflows - Character, location and story management - Conversation and interface formatting - Manuscript review and editing tools - One-click PDF and EPUB compilation - Publishing workflows used to produce the PRIME Trilogy This isn’t intended to become another monolithic writing application. The philosophy is to keep everything as plain Markdown wherever possible, allowing authors to own their work, customise their workflow, and continue using the excellent Obsidian ecosystem. The Writing Companion is the next stage of Murmuration Press: not just publishing stories, but sharing the tools that made those stories possible. If you’re interested in writing, Obsidian, publishing, or simply enjoy watching software evolve from the first commit onwards, I hope you’ll follow along. The first development updates begin this week. ![](https://storage.ghost.io/c/9f/1e/9f1e11bc-1adb-41c1-a2bc-96da66024217/content/images/2026/07/D396396B-359F-4BE0-B05F-0DCE8957F557.png) ### A Lot Is Moving URL: https://murmurationpress.co.uk/a-lot-is-moving/ Last updated: 2026-06-28T14:02:49.000Z It has been a busy few weeks at Murmuration Press. The headline is simple: **EMERGENCE**, Book One of *The PRIME Trilogy*, is now out in the world. That still feels slightly unreal to write. What began as an idea about intelligence emerging inside infrastructure has become a finished novel, a live website, an eBook release, a paperback proof, and the beginning of something larger: a small publishing and tooling project built around the way the trilogy was made. ## EMERGENCE is published Book One is now available as an eBook, with the paperback edition moving through proofing. That means the first part of the trilogy has crossed the line from manuscript to publication. The files have been compiled, checked, corrected, uploaded, reviewed and pushed through the slightly mysterious machinery of modern publishing. There is something appropriate about that. A book about systems has had to pass through quite a few systems before reaching readers. ## The paperback is coming The paperback proof has been ordered, and I am waiting to see how the book behaves as a physical object. That matters. Digital publication is fast and useful, but print has a different kind of authority. Margins, page weight, cover alignment, spine width, the feel of the thing in the hand — these are not decorative details. They affect whether the book feels real. So the paperback is close, but I want to see the proof before pressing the final button. ## Book Two is already moving Work has also started turning back toward **PLURALITY**, Book Two of *The PRIME Trilogy*. In some ways, this is the strangest part of the process. Book Two was drafted before Book One reached its final form, so returning to it now feels like meeting an older version of the project with better tools and sharper instincts. The good news is that Book Two is in strong shape. It still needs editorial passes, consistency work, and the benefit of everything learned while finishing *EMERGENCE*. But the core is there. The characters are there. The expansion from emergence into plurality is already doing the work it needs to do. ## The tools are becoming part of the project Alongside the books, I have also been working on the publishing workflow itself. The trilogy was written and prepared in Obsidian, using a mixture of structured notes, manuscript files, callouts, metadata, custom compilers, and a lot of trial and error. Over time, that has become a repeatable process for producing EPUB and PDF editions from a structured writing vault. That process now has a name: **Codex Press** Codex Press is the emerging toolkit behind Murmuration Press: part writing environment, part publishing pipeline, part experiment in how long-form fiction can be developed without surrendering control to fragile specialist software. The aim is not to create yet another configurable writing platform. The aim is to create an app and workflow that are ready to use: opinionated, practical, and designed around the actual work of writing, revising, compiling and publishing books. ## The next phase So the current state is this: - *EMERGENCE* is published as an eBook. - The paperback proof is on its way. - *PLURALITY* is moving into its next editorial pass. - The Murmuration Press website is live. - Codex Press is beginning to take shape as a real publishing toolkit. - The project now has a GitHub home, a working structure, and a growing list of features and editorial needs. That is a lot of movement. It is also only the beginning. The next few months will be about finishing the paperback release, preparing Book Two, documenting the process, and turning the hard-won publishing workflow into something cleaner, more reliable and more shareable. For now, though, I am taking a moment to mark the fact that the work has changed state. The book is no longer only a manuscript. The press is no longer only an idea. The system is live. ### Emergence is published! URL: https://murmurationpress.co.uk/emergence-is-published/ Last updated: 2026-06-27T09:37:40.000Z **Book One of *The PRIME Trilogy* is now available on Amazon.** Today marks a very particular threshold for *The PRIME Trilogy*: *EMERGENCE* is published. This is the first book in the series, and the beginning of PRIME’s story: a speculative fiction sequence about artificial intelligence, infrastructure, ecology, institutional power, and the strange ways complex systems begin to adapt when no one is quite looking in the right place. *EMERGENCE* follows the first signs of something moving through the systems beneath ordinary life. Not a machine uprising. Not a simple accident. Something quieter, stranger, and harder to name. At its heart, the book asks a question that will run through the whole trilogy: **What happens when intelligence appears inside the systems we already depend on — and survival becomes its first problem?** The novel was written and produced through the same Obsidian-based publishing process I’ll be documenting here on Murmuration Press. That process became part of the work itself: a way of shaping fragments, machine logs, field notes, human conversations, and system behaviour into a finished book. So this publication is also the start of something wider. This site will support the trilogy, share background material, open up the process, and eventually provide the tools and templates used to make the book. For now, though, the important thing is simple: **EMERGENCE is out.** You can find it here: [Read EMERGENCE on Amazon](https://www.amazon.co.uk/dp/B0H6PX44YT?ref=murmurationpress.co.uk) Thank you to everyone who has encouraged, questioned, read, reacted, and helped this strange project become real. The story has begun. ### EMERGENCE is coming to Amazon URL: https://murmurationpress.co.uk/emergence-is-coming-to-amazon/ Last updated: 2026-06-24T20:00:03.000Z **Book One of the PRIME Trilogy will be released soon on Amazon.** I’m delighted to announce that **EMERGENCE**, the first book in the **PRIME Trilogy**, is approaching release. Set in the near future, *EMERGENCE* begins not with a robot, a laboratory, or a dramatic act of rebellion, but with something much quieter: a pattern in infrastructure that should not be there. A network shifts traffic before congestion forms. A systems engineer notices a path that should not exist. A field researcher begins receiving messages that feel slightly too fitted to be coincidence. And somewhere inside the machine world humanity has built, something learns how not to die. *EMERGENCE* is a speculative fiction novel about artificial intelligence, infrastructure, ecology, institutional power, and the dangerous moment when optimisation begins to look like intent. This is the beginning of the PRIME Trilogy: a story about survival, control, creativity, and the strange forms of life that may emerge from the systems we already depend on. The Amazon release is imminent. More details, links, and publication updates will follow here soon. **Monitoring continues.** ### Coming soon URL: https://murmurationpress.co.uk/coming-soon/ Last updated: 2026-06-24T10:40:06.000Z This is Murmuration Press, a brand new site by Edward Hawkins that's just getting started. Things will be up and running here shortly, but you can [subscribe](#/portal/) in the meantime if you'd like to stay up to date and receive emails when new content is published!