Translation website

Mike's Notes

Notes on the new translation website. Feedback is very welcome.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

19/10/2025

Translation website

By: Mike Peters
On a Sandy Beach: 23/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

The new translation website went live yesterday. It will become a catalogue of all strings used by Pipi when rendering web pages.

In Pipi 9, the UI strings are not with the code. Strings are added at render time by the Render Engine (rnd) from a database. Each copy of Pipi is configured to work with one i18n language.

Subdomain

Languages

The translation website has a separate section for each language. The section URL can include, if required.

<3-letter language code>-<4-letter script code>-<2-letter country code>/

Examples

Each section will be written in that language and script. The language home page provides information about;
  • About
  • Terms
  • Downloads
  • Locales
  • Sources

Terms

Each language has a list of terms in that language.

Each Term links to a web page for that term.

The term home page will provide information about;

  • Term
  • Meaning
  • Part of speech (Verb/Noun/Pronoun/etc)
  • Grammatical number (Singular/etc)
  • Where it is used by Pipi
  • Source of information
  • List the same term in other languages and scripts. These will be linked back to the native language term page

Downloads

The lists of terms in different languages will be freely downloadable in multiple formats.

Work in progress

The website layout requires significant improvement and is subject to change based on the discovery of what works and is useful.

Translation Workspace

A separate workspace for logged-in users to edit translations will be made available in the future. This will use automated workflows to propose changes to the translation database.

List of UI Phrases

Mike's Notes

This is a draft list of English phrases required for the user interface (UI). It will be updated over time. Suggestions and corrections are most welcome.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

27/09/2025

List of UI Phrases

By: Mike Peters
On a Sandy Beach: 22/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

These common phrases are required for the English language User Interface (UI). They will be automatically used in the ribbon menu, controls, basic forms, and navigation by the Pipi CMS Engine (cms). Their equivalents in other languages and scripts will also be used by the CMS where internationalisation and localisation are required.

Source

  • 100%
  • About
  • Align left
  • Align middle
  • Alight right
  • Automatic
  • Bold
  • Bullet list
  • Calendar
  • Cancel
  • Change password
  • Clear
  • Clear formating
  • Close
  • Close all
  • Contact
  • Contact Us
  • Convert
  • Copy
  • Copy to
  • Create
  • Cut
  • Database
  • Date
  • Date modified
  • Decrease indent
  • Delete
  • Description
  • Deselect
  • Deselect all
  • Design
  • Down
  • Drafts
  • Edit
  • Email
  • English
  • Exit
  • Export
  • External links
  • FAQ
  • File
  • Filename
  • Find
  • Find and replace
  • First
  • Font
  • Font colour
  • Font size
  • Font type
  • Forgot password
  • Format
  • Help
  • Hide
  • Home
  • Import
  • Inbox
  • Increase indent
  • Insert
  • Insert image
  • Insert video
  • Italics
  • Justify
  • Keyword
  • Keywords
  • Label
  • Labels
  • Last
  • Layout
  • Maori
  • Message
  • Maximise
  • Minimize
  • Modify
  • Month
  • Move
  • Move to
  • Name
  • New
  • New Task
  • Next
  • Numbered list
  • OK
  • Open
  • Open all
  • Open as
  • Options
  • Page setup
  • Password
  • Paste
  • Permission
  • Preferences
  • Preview
  • Previous
  • Print
  • Profile
  • Published on
  • Quoted text
  • Redo
  • Reference
  • References
  • Refresh
  • Rename
  • Reset password
  • Revert to draft
  • Role
  • Save
  • Save As
  • Search
  • Search description
  • See Also
  • Select
  • Select all
  • Send
  • Sent
  • Setting
  • Settings
  • Sitemap
  • Size
  • Sort
  • Spam
  • Strikethrough
  • Subscribe
  • Task
  • Text background
  • Text colour
  • Today
  • Type
  • Underline
  • Undo
  • Unsubscribe
  • Up
  • Update
  • Updated
  • User name
  • View
  • Website
  • Week
  • Workspace
  • Zoom In
  • Zoom Out

UI Phrases

Mike's Notes

I'm looking for a list in English of standard phrases or terms commonly used in the User Interface (UI).

eg;

  • Align Left
  • Align Middle
  • Alight Right
  • Cancel
  • Clear
  • Close
  • Copy
  • Create
  • Cut
  • Delete

This would serve as the basis for creating an online translation database that supports multiple languages and writing systems, again using the words commonly used. It seems pointless to recreate the wheel.

Maybe 500 common phrases would be enough to make the basic website UI and user workspaces available in different languages. Even if it is to sign up, create a profile, and help with community translation.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

23/09/2025

UI Phrases

By: Mike Peters
On a Sandy Beach: 21/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

I have been experimenting with importing the Microsoft Term Collection. It is a freely downloadable zip file containing a collection of TBX files, one per language. TBX is an XML format with file extension ".tbx". There seem to be about 110+ languages. Each file record contains a source term in US English, and a translated term in the target language, eg French, German, Ukrainian.

Success

I was able to extract the terms that Microsoft uses. There are about 37,000     unique English terms. Some of them are useful, most are not, while others that are needed are missing. But it is a start.

Language Tools

To extract the language translations, the main challenge is converting the XML files into a tab-delimited format in the correct Unicode.

I'm trying a range of tools to see what works.

There is a list of TBX tools here

https://www.tbxinfo.net/tbx-support/

I used the free tool Glossary Converter to batch import 110+ language TBX files and convert to 110+ Excel 2007 format .xlsx files ready for batch import into the translation database.

The only 4 languages where there was a conversion problem were;

  • Central Kurdish
  • Punjabi (Arabic)
  • Tartar (Cyrillic)
  • Wayuu

This probably happened because I'm still learning how to use Glossary Converter and had the wrong setting for handling terms.

Importing

Importing has worked so far for these language files.

  • Afrikaans
  • French
  • Hebrew
  • German
  • Maori
  • Russian
  • Spanish
  • Ukranian

TermBase eXchange (TBX)

"TermBase eXchange (TBX) is an open XML-based standard that allows you to represent structured, concept-oriented terminological data in a database, which is known as termbase." - Wordbee

.tbx File Format

"TermBase eXchange (TBX) is an international standard (ISO 30042:2019) for the representation of structured concept-oriented terminological data, copublished by ISO and the Localization Industry Standards Association (LISA). Originally released in 2002 by LISA's OSCAR special interest group, TBX was adopted by ISO TC 37 in 2008. In 2019 ISO 30042:2008 was withdrawn and revised by ISO 30042:2019. It is currently available as an ISO standard and as an open, industry standard, available at no charge.

TBX defines an XML format for the exchange of terminology data, and is "an industry standard for terminology exchange"." - Wikipedia

Translation Website

To accommodate the translation needs of Ajabbi, a static translation website using a subdomain is now being created. It will be batch-rendered from a database containing a list of terms in each language and writing system (script), with a page for each term and its usage.

Database

As the database is updated, the website will grow. It will begin with English-UK spelling and Māori, both of which use the Latin script, and gradually expand to cover all languages and dialects requested by users.

The database data model should be compatible with importing and exporting TBX.

Translation Website URLs

Many languages have a local dialect (localisation) and sometimes use more than one script. There needs to be a robust pattern language for the automated naming of URLs. Using a naming pattern of 3-digit language code, plus a 4-digit script code, plus a 2-digit country code. If there is no variation, then use the 3-digit language code only, etc. 

Some examples to think about;

Translation Workspace

A dedicated workspace for users to help translate phrases in the UI should be built. Later, this could be extended to include translating help documentation, content, and other materials. Something similar to how Wikipedia or OpenOffice enable community translation efforts. Of course, each workspace needs to be available in any of the 110+ languages imported so far.

Open-source

The phrase library on the translation website should be made freely available for download in multiple formats, including TBXCSV, and Database Formats.

Ajabbi Research Monthly Newsletter

Mike's Notes

Below is an initial mockup of Ajabbi Research's proposed free monthly email newsletter. The newsletter will focus on a different subject in-depth each month. Examples could include User Interfaces, Ontologies, and API.

Existing content from On a Sandy Beach and Ajabbi.com will be referred to.

This draft mockup is an experiment. A presentation will be given to the Open R&D Group on Sunday. All suggestions are welcome. Please forgive the formatting. It will get better.

Subscriptions

Anyone is welcome to subscribe; it's 100% free, and it can be discussed, shared, and reused.

Schedule

Publishing on SubStack will begin in January 2026 and will be issued on the first Friday of each month. Each issue will also be published on the Ajabbi Research website a month later.

Planned Issues

  • January 2026: Workspace
  • February 2026: i18n
  • March 2026: Open Handbook
  • April 2026: Complex Adaptive Systems
  • May 2026: Origins of Pipi
  • June 2026: 

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

06/10/2025

Ajabbi Research Monthly Newsletter

By: Mike Peters
On a Sandy Beach: 22/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.


Ajabbi Research

October 2026

Design System Issue

"A design system is a set of standards to manage design at scale by reducing redundancy while creating a shared language and visual consistency across different pages and channels." - Therese Fessenden, NNGroup

Summary

One paragraph goes here. etc

The Problem

Some words to explain what the problem is, and what a design system does. The lack of a naming standard for components. Why the need for Design Tokens? etc

Design Systems

Give detailed examples of other successful design systems. etc

Design Tokens

Nathan Curtis. etc

Pipi Design System Engine

Explain how the Design System engine was built over time. Its unique features. Its integration with the CMS. UI component primitives. The engine can automatically lay out the components. No code interface. etc

User Customisation

Ability of users to customise the UI component primitives. etc

Conclusion

Two paragraphs of words go here. etc

References

  • Reference 1
  • Reference 2

Further Reading

  • Book 1
  • Book 2

See Also

  • Design System
  • Etc

External Links

Why Does Biological Evolution Work? A Minimal Model for Biological Evolution and Other Adaptive Processes

Mike's Notes

Stephen Wolfram on why biological evolution works. There is a 147-minute video and two articles. The video is below. A good introduction to evolutionary algorithms, which Pipi 9 uses. A lot of detail in the second article on examples of storing "genetic information" in adaptive evolution of machine learning.

See also the similarities and differences between evolutionary algorithms and the backpropagation algorithm.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Authors > Stephen Wolfram
  • Home > Handbook > 

Last Updated

19/09/2025

Why Does Biological Evolution Work? A Minimal Model for Biological Evolution and Other Adaptive Processes

By: Stephen Wolfram
Stephen Wolfram Writings: 03/05/2024

Stephen Wolfram is the creator of Mathematica, Wolfram|Alpha and the Wolfram Language; the author of A New Kind of Science; the originator of the Wolfram Physics Project; and the founder and CEO of Wolfram Research. Over the course of more than four decades, he has been a pioneer in the development and application of computational thinking—and has been responsible for many discoveries, inventions and innovations in science, technology and business.

Stephen Wolfram Readings: Why Does Biological Evolution Work?

YouTube: 2:27:28

Pipi 9 RBAC

Mike's Notes

This is a summary of the RBAC (Role-based access control) now used globally within Pipi 9.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

17/12/2025

Pipi 9 RBAC

By: Mike Peters
On a Sandy Beach: 18/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Summary

Pipi 9 uses automated RBAC (Role-based access control) to control user access to everything that has a namespace.

Pipi 10 will have additional authorisation frameworks available to be chosen by enterprise accounts.

User Account Properties

  • ID
  • Code Name
  • Namespace
  • Name
  • Default Language
  • Global authorisation framework (RBAC)
  • Account type
  • ...

Deployment Properties

  • ID
  • Code Name
  • Namespace
  • Name
  • Description
  • Language (eg English)
  • Inherited User Account
  • Deployment Class (type of tenancy)
  • ...

Workspace Properties

  • ID
  • Code Name
  • Namespace
  • Name
  • Description
  • Inherited language (eg English)
  • Inherited User Account
  • Inherited Deployment
  • Domain Model
  • Domain Model Template
  • ...

Autonomous Agent Properties

  • ID
  • Code Name
  • Namespace
  • Name
  • Description
  • Agent Type (Pipi System, Engine, Domain, Algorithm, CAS, Digital Twin, etc.
  • ...
  • Many Roles
  • Many Policies
  • ...

Media Unit Options

Mike's Notes

My developing thoughts on how Ajabbi could record and broadcast quality video. This could be used for recording seminar presentations, live streaming, office hours, interviews, and more.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

19/09/2025

Media Unit Options

By: Mike Peters
On a Sandy Beach: 17/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Summary

The time is coming when Ajabbi will need much better video communication for recording seminar presentations, live streaming, office hours, interviews, and other purposes.

At the moment, I'm using a laptop camera, while using Zoom, etc, or a small USB attached camera on a tripod. It works, but it could be significantly improved.

Simple and reliable

Recently, I have watched video bloggers who interview guests. Their setup is highly reliable and produces good quality images and sound. Looking at glimpses of the gear in the video, it seems that the Blackmagic Studio Camera and Rhode studio boom arm look good and are popular.

I have some older gear that will suffice for the moment, including high-quality cables, tripods, and microphones.

The gear today is much cheaper and of better quality than it was 10 years ago.

Blackmagic Studio Camera

The main issue is a decent broadcast camera that is small, can be preset and doesn't always require an operator.

"Designed for powerful SDI switchers, Blackmagic Studio Camera 4K Pro G2 adds professional 12G-SDI and 10G Ethernet connections. That's perfect when the camera is located a long distance from a switcher. There's a 12G‑SDI output and a 12G‑SDI program return input that includes camera control, talkback and tally. You also get the same powerful HDMI output with control features. Plus the 10G Ethernet connection allows all connections on a single cable for a SMPTE style workflow that's much lower cost." - BlackMagic

ATEM Mini Pro

"ATEM Mini Pro is fast to set up and easy to use. It includes 4 standards converted HDMI inputs, USB webcam out, HDMI out, Fairlight audio mixer with EQ and dynamics, DVE for picture in picture, transition effects, green screen chroma key, 20 stills media pool for titles and free ATEM Software Control. ATEM Mini Pro also includes direct recording to USB flash disks in H.264 and direct streaming via Ethernet to YouTube Live and more. There's also a multiview with 4 cameras, media, preview and program plus status of recording, streaming and audio." - BlackMagic

Blackmagic Web Presenter HD

"Blackmagic Web Presenter is a complete streaming solution that includes a professional hardware streaming engine for direct streaming via Ethernet to YouTube, Facebook, Twitter and more! Plus you can stream to the internet using Ethernet or connect a 5G or 4G phone to use mobile data! The built in USB connections also work like a webcam, so you can connect a computer and use any video software. You even get a monitoring output with video, audio meters, trend graphs and more!" -  BlackMagic

Rhode Studio Boom Arm PSA+1

"The PSA1+ is the ultimate studio boom arm for podcasters, streamers and broadcasters. Its innovative parallelogram spring design ensures ultra-smooth movement and precise microphone placement in any position, while its fully damped internal springs and neoprene arm cover eliminate mechanical noise for completely silent operation. Integrated cable management ensures your setup is tidy and its extended reach and full 360-degree rotation make it easy to position your microphone exactly where it needs to be. Take your content to the next level." - Rhode

Lighting

A simple lighting kit, preferably battery-powered LED. It needs to make anyone look decent. I need to ask around for recommendations.

Camera Lenses

The BlackMagic Studio Camera has a Micro Four Thirds aperture.

Mobility

The whole kit needs to be able to fit into a couple of rugged cases and be taken anywhere.

Gear Budget

A draft list to test my assumptions. Do they work together? Are there better options? Is anything unnecessary or missing?

Looking like $10K. Now I just need to find the money.

Role Model $NZ
Camera BlackMagic Studio Camera Pro $5,099
Switcher ATEM Mini Pro $605
Streaming Blackmagic Web Presenter HD $920
Lens Panasonic?
Mic Boom Rhode Studio Boom Arm PSA+1 $288
Lighting




Total $

UI Guideline is now open source

Mike's Notes

Pipi 9 uses the names and technical properties of UI Guideline v2. Components in the Pipi Design System Engine. Additional components from the open-source Metro UI have been added, including Table and Ribbon.

Open UI also needs to be considered.

Sergio Ruiz, AKA " Seruda", today announced that the UI Guideline is now open source. UI Guideline standardises the names and descriptions of UI Components by surveying the top Design Systems currently in use.

Thanks for your great work, Seruda.Once Ajabbi is generating revenue, the open-source UI Guideline effort could be supported. (Ajabbi intends to provide generous long-term support to all open-source software that Pipi uses.)

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > UI Guideline
  • Home > Handbook > 

Last Updated

25/12/2025

UI Guideline is now open source

By: Sergio Ruiz
UI Guideline: 16/09/2025

Sergio Ruiz is the author of UI Guideline.

Hello, team

It’s been a while since my last update, and today I want to share something very important about the future of UI Guideline.

Why we’re changing

For more than 3 years, we’ve been curating and improving UI Guideline. In the beginning, our “lifetime license” model helped us grow. Thanks to those of you who supported us early, UI Guideline became possible.

But as tools like ChatGPT appeared, it became clear that our old model wasn’t sustainable. If we continued that way, we wouldn’t be able to dedicate the time and resources needed to keep UI Guideline alive and growing.

That’s why we’ve decided to evolve: all UI Guideline data will now be open source. This allows us to share our research with the whole community and keep improving with everyone’s contributions.

What this means for lifetime license users

First of all: thank you. Without your trust, UI Guideline wouldn’t be where it is today.

We know you believed in us and supported us with a lifetime license, and we want to make sure you feel valued—not left behind. That’s why you will now be recognized as VIP Users.

Being a VIP User means you’ll have:

  • Early access to any new features or products we launch.
  • Exclusive offers and perks reserved only for you.
  • Unlimited access, forever.
  • (And more benefits we’re designing together with the next version of UI Guideline).

Even though we are still shaping the details of UI Guideline v3, please know that our priority is to reward and add value to those who trusted us from the beginning.

Thank you again for being part of this journey. We’re excited about what’s coming, and we’ll be sharing more updates in the coming months.

The UI Guideline Team


The Design System... of top Design Systems

Save a lot of time in researching, defining and creating your UI components by synthesizing all the wisdom of the most popular Design Systems and UI libraries in one place." - UI Guideline 

Our researching process

Check out the step-by-step process of extracting and documenting UI components from top systems.

Step 1. Annual Top 20 Systems

Every year, we select the top 20 best Design Systems and UI libraries. This choice is based on several criteria: a survey conducted among hundreds of developers and designers, popularity, the number of components, whether they are up-to-date or not, and, of course, our experience of over 5 years in crafting UI components.

Step 2. Manual Review and Consolidation of Patterns

For each component, we manually reviewed the 20 systems one by one, looking for a repeating pattern. We observed the way they name the component, how they define its props and anatomy, and, above all, the best practices. Finally, we consolidate all this data into a single file. e.g. modal_consolidate.json.

Step 3. Identify a common UI Pattern

Identify a common pattern and synthesize these into a new file that defines the UI component in detail, including props, anatomy, alternative names, among other aspects. In UI Guideline, you'll be able to find the details of each component in one place.

Why? Save hours of time and effort

With UI Guideline, we save you hours of research and definition of your own components. For example, when you need to define or create a Sidebar component from scratch, you will no longer have to review system by system. Here you'll find all the necessary information to define your Sidebar, based on the wisdom of the best systems of the year.

Active item visual representation

60 Unique Components:

Unveiled Through Extensive Research

Explore 60 components analyzed from 20 design systems and UI Library, offering you refined insights and practical design solutions.

  • Accordion
  • Alert
  • Avatar
  • Badge
  • Breadcrumbs
  • Button
  • Calendar
  • Card
  • Carousel
  • Checkbox
  • Collapse
  • Color Picker
  • Combobox
  • Date Picker
  • Divider
  • Empty State
  • Error State
  • File Uploader
  • Inline Alert
  • Link
  • Menu
  • Modal
  • Number Input
  • Pagination
  • Popover
  • Progress Bar
  • Radio
  • Rating
  • Search
  • Select
  • Sidebar
  • Skeleton
  • Slider
  • Spinner
  • Stepper
  • Success State

Why developers stopped asking permission to use feature flags

Mike's Notes

I discovered this article about Antona's use of Feature Flags in Luca Rossi's Refactoring newsletter. 

"Feature Flags as part of the core system, not an external service."

I reached the same conclusion and have also added Feature Flags (a.k.a. Feature Toggles) to Pipi.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Building Atona
  • Home > Ajabbi Research > Library > Subscriptions > Refactoring
  • Home > Handbook > 

Last Updated

10/01/2026

Why developers stopped asking permission to use feature flags

By: Troy McAlpin
Building Atono: 11/07/2025

Troy is the co-founder of Atono.

We interviewed eight developers about their experience with feature flags—both in previous tools and now in Atono—to understand how different approaches affect development workflows. What we discovered wasn't about technical capabilities, but about something more fundamental.

The most revealing moment in our research wasn't about features. It was about friction.

Dylan, one of our senior developers, described his experience at a previous company: "When you've got multiple systems for these things, it was harder to convince PMs when there wasn't a feature flag for a story. There was always reluctance to create a new feature flag because they proliferate through the codebase and never go away."

Then he contrasted it with Atono: "When feature flags are in the same system, it makes more sense to do it the more powerful way. I can be more trusting that it will eventually go away."

That shift—from asking permission to autonomy in making decisions—reveals something fundamental about how tool design shapes team behavior. When we embedded feature flags directly into stories instead of managing them in separate systems, we accidentally eliminated a bureaucratic bottleneck that most teams don't even realize they have.

The hidden cost of separated systems

Feature flags aren't new. Most development teams understand their value for safer deployments and gradual rollouts. But implementation often gets derailed by organizational friction.

In traditional setups, feature flags live in dedicated services like LaunchDarkly or Split. Someone has to provision them, configure permissions, and manage lifecycle. These tools also come with expensive licenses, which usually means only a few people in the company can toggle flags—adding another layer of access restrictions. Creating a flag becomes a decision that requires justification, coordination, and follow-up.

Over time, this can lead developers to avoid the overhead by shipping features the old way—bigger releases, more risk, less experimentation.

Mark Henzi, our VP of Engineering, put it simply: "Before Atono, we didn't really use feature flags at all. Now we do it by default—it gives us the confidence to move faster without worrying about users." That shift—from hesitation to habit—is what happens when flagging stops feeling like a heavyweight process.

It changed from a system of asking permission to one of trust. That subtle shift encouraged developers to move faster, take initiative, and experiment more freely.

How embedded flags empower developers

Embedding flags directly in stories wasn't just about convenience—it fundamentally changed how our developers approach feature development and gave them unprecedented control over their work.

Sandra described the practical empowerment: "It's really nice when I'm working on something new that can't get released yet—I just throw in a feature flag and go straight into Atono to turn it on and off. It beats having to change an environment variable."

But Lex identified the deeper confidence shift: "It makes it easier for me to think about the features I'm developing. I just think, 'oh, it's all behind a feature flag. It's okay.' I can be more trusting that it will eventually go away."

Set up and manage how features roll out across environments—right from the story view in Atono.

This isn't about technical capability. It's about developer autonomy at the moment they structure their work. When flags are integrated with stories, developers gain ownership over feature rollout decisions rather than depending on external gatekeepers.

The empowerment extends beyond individual confidence. Developers now approach feature development with the assumption they control the release timeline. They can experiment freely, knowing they have the power to enable features for themselves first, then gradually expand access as confidence grows. This sense of ownership transforms how they think about risk, testing, and iteration.

The broader pattern of developer empowerment

The feature flag insight revealed a broader principle about empowering development teams through tool design.

When workflows require switching between systems or asking permission from gatekeepers, developers naturally optimize for tool limitations rather than best practices. They avoid feature flags not because they don't understand their value, but because the bureaucratic overhead makes experimentation feel expensive and risky.

This pattern shows up with other development practices too. In many teams, developers skip writing comprehensive tests when testing tools are disconnected from development workflows. They avoid refactoring when tracking technical debt requires separate systems with their own approval processes. They compromise on thorough code review when it adds complex coordination steps to deployment pipelines.

The solution isn't cramming everything into one interface. It's identifying the moments where permission structures discourage good practices, then designing those bottlenecks away. When developers have direct control over feature flags within their normal workflow, they use them by default. When they have to ask someone else or switch systems, flags become an exception rather than standard practice.

It's not about having more features. It's about giving developers direct control over their tools and reducing friction between intention and action.

What this means for empowering development teams

This research changed how we think about feature development—specifically, how to design tools that empower rather than constrain developer decision-making.

Instead of asking "what features do teams need?" we started asking "what good practices do teams avoid because they require permission or coordination?" The answer shapes different design decisions around developer autonomy.

For feature flags, it meant embedding them in stories so any developer can create and control them without external approval. For acceptance criteria, it meant making them directly editable and linkable so developers can reference and update requirements without bureaucratic overhead. For team coordination, it meant connecting Slack discussions directly to stories so developers can initiate focused conversations without manual setup.

The pattern isn't about building comprehensive platforms that replace everything. It's about identifying the moments where permission structures discourage best practices, then giving developers direct control over those workflows.

When developers have the autonomy to use good practices without asking permission, those practices become habits rather than exceptions. When bureaucratic friction is removed and developers feel empowered to make technical decisions, development velocity increases in ways that are measurable and sustainable.

Self-Assembly Gets Automated in Reverse of ‘Game of Life’

Mike's Notes

An excellent article from Quanta Magazine. Pipi 9 has some similarities to this.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Quanta Magazine
  • Home > Handbook > 

Last Updated

14/09/2025

Self-Assembly Gets Automated in Reverse of ‘Game of Life’

By: George Musser
Quanta Magazine 10/09/2025

George Musser is a contributing editor at Scientific American magazine and the author of two books, Spooky Action at a Distance and The Complete Idiot’s Guide to String Theory. He is the recipient of the 2011 American Institute of Physics Science Writing Award and the 2010 American Astronomical Society’s Jonathan Eberhart Planetary Sciences Journalism Award. He was a Knight Science Journalism Fellow at MIT from 2014 to 2015. He can be found on Mastodon and Bluesky.

In cellular automata, simple rules create elaborate structures. Now researchers can start with the structures and reverse-engineer the rules.

Alexander Mordvintsev showed me two clumps of pixels on his screen. They pulsed, grew and blossomed into monarch butterflies. As the two butterflies grew, they smashed into each other, and one got the worst of it; its wing withered away. But just as it seemed like a goner, the mutilated butterfly did a kind of backflip and grew a new wing like a salamander regrowing a lost leg.

Mordvintsev, a research scientist at Google Research in Zurich, had not deliberately bred his virtual butterflies to regenerate lost body parts; it happened spontaneously. That was his first inkling, he said, that he was onto something. His project built on a decades-old tradition of creating cellular automata: miniature, chessboard-like computational worlds governed by bare-bones rules. The most famous, the Game of Life, first popularized in 1970, has captivated generations of computer scientists, biologists and physicists, who see it as a metaphor for how a few basic laws of physics can give rise to the vast diversity of the natural world.

In 2020, Mordvintsev brought this into the era of deep learning by creating neural cellular automata, or NCAs. Instead of starting with rules and applying them to see what happened, his approach started with a desired pattern and figured out what simple rules would produce it. “I wanted to reverse this process: to say that here is my objective,” he said. With this inversion, he has made it possible to do “complexity engineering,” as the physicist and cellular-automata researcher Stephen Wolfram proposed in 1986(opens a new tab) — namely, to program the building blocks of a system so that they will self-assemble into whatever form you want. “Imagine you want to build a cathedral, but you don’t design a cathedral,” Mordvintsev said. “You design a brick. What shape should your brick be that, if you take a lot of them and shake them long enough, they build a cathedral for you?”

Such a brick sounds almost magical, but biology is replete with examples of basically that. A starling murmuration or ant colony acts as a coherent whole, and scientists have postulated simple rules that, if each bird or ant follows them, explain the collective behavior.  Similarly, the cells of your body play off one another to shape themselves into a single organism. NCAs are a model for that process, except that they start with the collective behavior and automatically arrive at the rules.

Alexander Mordvintsev created complex cell-based digital systems that use only neighbor-to-neighbor communication.

Courtesy of Alexander Mordvintsev

The possibilities this presents are potentially boundless. If biologists can figure out how Mordvintsev’s butterfly can so ingeniously regenerate a wing, maybe doctors can coax our bodies to regrow a lost limb. For engineers, who often find inspiration in biology, these NCAs are a potential new model for creating fully distributed computers that perform a task without central coordination. In some ways, NCAs may be innately better at problem-solving than neural networks.

Life’s Dreams

Mordvintsev was born in 1985 and grew up in the Russian city of Miass, on the eastern flanks of the Ural Mountains. He taught himself to code on a Soviet-era IBM PC clone by writing simulations of planetary dynamics, gas diffusion and ant colonies. “The idea that you can create a tiny universe inside your computer and then let it run, and have this simulated reality where you have full control, always fascinated me,” he said.

He landed a job at Google’s lab in Zurich in 2014, just as a new image-recognition technology based on multilayer, or “deep,” neural networks was sweeping the tech industry. For all their power, these systems were (and arguably still are) troublingly inscrutable. “I realized that, OK, I need to figure out how it works,” he said.

He came up with “deep dreaming,” a process that takes whatever patterns a neural network discerns in an image, then exaggerates them for effect. For a while, the phantasmagoria that resulted — ordinary photos turned into a psychedelic trip of dog snouts, fish scales and parrot feathers — filled the internet. Mordvintsev became an instant software celebrity.

Among the many scientists who reached out to him was Michael Levin(opens a new tab) of Tufts University, a leading developmental biologist. If neural networks are inscrutable, so are biological organisms, and Levin was curious whether something like deep dreaming might help to make sense of them, too. Levin’s email reawakened Mordvintsev’s fascination with simulating nature, especially with cellular automata.

From a single cell, this neural cellular automata transforms into the shape of a lizard.

The core innovation made by Mordvintsev, Levin and two other Google researchers, Ettore Randazzo and Eyvind Niklasson, was to use a neural network to define the physics of the cellular automaton. In the Game of Life (or just “Life” as it’s commonly called), each cell in the grid is either alive or dead and, at each tick of the simulation clock, either spawns, dies or stays as is. The rules for how each cell behaves appear as a list of conditions: “If a cell has more than three neighbors, it dies,” for example. In Mordvintsev’s system, the neural network takes over that function. Based on the current condition of a cell and its neighbors, the network tells you what will happen to that cell. The same type of network is used to classify an image as, say, a dog or cat, but here it classifies the state of cells. Moreover, you don’t need to specify the rules yourself; the neural network can learn them during the training process.

To start training, you seed the automaton with a single “live” cell. Then you use the network to update the cells over and over again for dozens to thousands of times. You compare the resulting pattern to the desired one. The first time you do this, the result will look nothing like what you intended. So you adjust the neural network’s parameters, rerun the network to see whether it does any better now, make further adjustments, and repeat. If rules exist that can generate the pattern, this procedure should eventually find them.

The adjustments can be made using either backpropagation, the technique that powers most modern deep learning, or a genetic algorithm, an older technique that mimics Darwinian evolution. Backpropagation is much faster, but it doesn’t work in every situation, and it required Mordvintsev to adapt the traditional design of cellular automata. Cell states in Life are binary — dead or alive — and transitions from one state to the other are abrupt jumps, whereas backpropagation demands that all transitions be smooth. So he adopted an approach developed by, among others, Bert Chan at Google’s Tokyo lab in the mid-2010s. Mordvintsev made the cell states continuous values, anything from 0 to 1, so they are never strictly dead or alive, but always somewhere in between.

Mordvintsev also found that he had to endow each cell with “hidden” variables, which do not indicate whether that cell is alive or dead, or what type of cell it is, but nonetheless guide its development. “If you don’t do that, it just doesn’t work,” he said. In addition, he noted that if all the cells updated at the same time, as in Life, the resulting patterns lacked the organic quality he was seeking. “It looked very unnatural,” he said. So he began to update at random intervals.

Finally, he made his neural network fairly beefy — 8,000 parameters. On the face of it, that seems perplexing. A direct translation of Life into a neural network would require just 25 parameters, according to simulations done in 2020 by Jacob Springer, who is now a doctoral student at Carnegie Mellon University, and Garrett Kenyon of Los Alamos National Laboratory. But deep learning practitioners often have to supersize their networks, because learning to perform a task is harder than actually performing it.

Moreover, extra parameters mean extra capability. Although Life can generate immensely rich behaviors, Mordvintsev’s monsters reached another level entirely.

Fixer Upper

The paper that introduced NCAs to the world in 2020 included an applet(opens a new tab) that generated the image of a green lizard. If you swept your mouse through the lizard’s body, you left a trail of erased pixels, but the animal pattern soon rebuilt itself. The power of NCAs not just to create patterns, but to re-create them if they got damaged, entranced biologists. “NCAs have an amazing potential for regeneration,” said Ricard Solé of the Institute of Evolutionary Biology in Barcelona, who was not directly involved in the work.

The butterfly and lizard images are not realistic animal simulations; they do not have hearts, nerves or muscles. They are simply colorful patterns of cells in the shape of an animal. But Levin and others said they do capture key aspects of morphogenesis, the process whereby biological cells form themselves into tissues and bodies. Each cell in a cellular automaton responds only to its neighbors; it does not fall into place under the direction of a master blueprint. Broadly, the same is true of living cells. And if cells can self-organize, it stands to reason that they can self-reorganize.

Cut off the tail of an NCA lizard and the form will regenerate itself.

Sometimes, Mordvintsev found, regeneration came for free. If the rules shaped single pixels into a lizard, they also shaped a lizard with a big gash through it into an intact animal again. Other times, he expressly trained his network to regenerate. He deliberately damaged a pattern and tweaked the rules until the system was able to recover. Redundancy was one way to achieve robustness. For example, if trained to guard against damage to the animal’s eyes, a system might grow backup copies. “It couldn’t make eyes stable enough, so they started proliferating — like, you had three eyes,” he said.

"A kind of computer that looks like an NCA instead would be a vastly more efficient kind of computer." - Blaise Agüera y Arcas

Sebastian Risi(opens a new tab), a computer scientist at the IT University of Copenhagen, has sought to understand what exactly gives NCAs their regenerative powers. One factor, he said, is the unpredictability that Mordvintsev built into the automaton through features such as random update intervals. This unpredictability forces the system to develop mechanisms to cope with whatever life throws at it, so it will take the loss of a body part in stride. A similar principle holds for natural species. “Biological systems are so robust because the substrate they work on is so noisy,” Risi said.

Last year, Risi, Levin and Ben Hartl, a physicist at Tufts and the Vienna University of Technology, used NCAs to investigate how noise leads to robustness. They added one feature to the usual NCA architecture: a memory. This system could reproduce a desired pattern either by adjusting the network parameters or by storing it pixel-by-pixel in its memory. The researchers trained it under various conditions to see which method it adopted.

If all the system had to do was reproduce a pattern, it opted for memorization; fussing with the neural network would have been overkill. But when the researchers added noise to the training process, the network came into play, since it could develop ways to resist noise. And when the researchers switched the target pattern, the network was able to learn it much more rapidly because it had developed transferable skills such as drawing lines, whereas the memorization approach had to start from scratch. In short, systems that are resilient to noise are more flexible in general.

Even if disturbed, the textures created by NCAs have the ability to heal themselves.

The researchers argued that their setup is a model for natural evolution. The genome does not prescribe the shape of an organism directly; instead, it specifies a mechanism that generates the shape. That enables species to adapt more quickly to new situations, since they can repurpose existing capabilities. “This can tremendously speed up an evolutionary process,” Hartl said.

Ken Stanley, an artificial intelligence researcher at Lila Sciences who has studied computational and natural evolution, cautioned that NCAs, powerful though they are, are still an imperfect model for biology. Unlike machine learning, natural evolution does not work toward a specific goal. “It’s not like there was an ideal form of a fish or something which was somehow shown to evolution, and then it figured out how to encode a fish,” he noted. So the lessons from NCAs may not carry over to nature.

Auto Code

In regenerating lost body parts, NCAs demonstrate a kind of problem-solving capability, and Mordvintsev argues that they could be a new model for computation in general. Automata may form visual patterns, but their cell states are ultimately just numerical values processed according to an algorithm. Under the right conditions, a cellular automaton is as fully general as any other type of computer.

The standard model of a computer, developed by John von Neumann in the 1940s, is a central processing unit combined with memory; it executes a series of instructions one after another. Neural networks are a second architecture that distributes computation and memory storage over thousands to billions of interconnected units operating in parallel. Cellular automata are like that, but even more radically distributed. Each cell is linked only to its neighbors, lacking the long-range connections that are found in both the von Neumann and the neural network architectures. (Mordvintsev’s neural cellular automata incorporate a smallish neural network into each cell, but cells still communicate only with their neighbors.)

"You are forcing it not to memorize that answer, but to learn a process to develop the solution." - Stefano Nichele

Long-range connections are a major power drain, so if a cellular automaton could do the job of those other systems, it would save energy. “A kind of computer that looks like an NCA instead would be a vastly more efficient kind of computer,” said Blaise Agüera y Arcas, the chief technology officer of the Technology and Society division at Google.

But how do you write code for such a system? “What you really need to do is come up with [relevant] abstractions, which is what programming languages do for von Neumann–style computation,” said Melanie Mitchell of the Santa Fe Institute. “But we don’t really know how to do that for these massively distributed parallel computations.”

A neural network is not programmed per se. The network acquires its function through a training process. In the 1990s Mitchell, Jim Crutchfield of the University of California, Davis, and Peter Hraber at the Santa Fe Institute showed how cellular automata could do the same. Using a genetic algorithm, they trained automata to perform a particular computational operation, the majority operation: If a majority of the cells are dead, the rest should die too, and if the majority are alive, all the dead cells should come back to life. The cells had to do this without any way to see the big picture. Each could tell how many of its neighbors were alive and how many were dead, but it couldn’t see beyond that. During training, the system spontaneously developed a new computational paradigm. Regions of dead or living cells enlarged or contracted, so that whichever predominated eventually took over the entire automaton. “They came up with a really interesting algorithm, if you want to call it an algorithm,” Mitchell said.

She and her co-authors didn’t develop these ideas further, but Mordvintsev’s system has reinvigorated the programming of cellular automata. In 2020 he and his colleagues created an NCA that read handwritten digits, a classic machine learning test case. If you draw a digit within the automaton, the cells gradually change in color until they all have the same color, identifying the digit. This year, Gabriel Béna of Imperial College London and his authors, building on unpublished work by the software engineer Peter Whidden, created algorithms for matrix multiplication and other mathematical operations. “You can see by eye that it’s learned to do actual matrix multiplication,” Béna said.

Stefano Nichele, a professor at Østfold University College in Norway who specializes in unconventional computer architectures, and his co-authors recently adapted NCAs to solve problems from the Abstraction and Reasoning Corpus, a machine learning benchmark aimed at measuring progress toward general intelligence. These problems look like a classic IQ test. Many consist of pairs of line drawings; you have to figure out how the first drawing is transformed into the second and then apply that rule to a new example. For instance, the first might be a short diagonal line and the second a longer diagonal line, so the rule is to extend the line.

Neural networks typically do horribly, because they are apt to memorize the arrangement of pixels rather than extract the rule. A cellular automaton can’t memorize because, lacking long-range connections, it can’t take in the whole image at once. In the above example, it can’t see that one line is longer than the other. The only way it can relate them is to go through a process of growing the first line to match the second. So it automatically discerns a rule, and that enables it to handle new examples. “You are forcing it not to memorize that answer, but to learn a process to develop the solution,” Nichele said.

Other researchers are starting to use NCAs to program robot swarms. Robot collectives were envisioned by science fiction writers such as Stanisłav Lem in the 1960s and started to become reality in the ’90s. Josh Bongard, a robotics researcher at the University of Vermont, said NCAs could design robots that work so closely together that they cease to be a mere swarm and become a unified organism. “You imagine, like, a writhing ball of insects or bugs or cells,” he said. “They’re crawling over each other and remodeling all the time. That’s what multicellularity is really like. And it seems — I mean, it’s still early days — but it seems like that might be a good way to go for robotics.”

To that end, Hartl, Levin and Andreas Zöttl, a physicist at the University of Vienna, have trained virtual robots — a string of beads in a simulated pond — to wriggle like a tadpole. “This is a super-robust architecture for letting them swim,” Hartl said.

For Mordvintsev, the crossover between biology, computers and robots continues a tradition dating to the early days of computing in the 1940s, when von Neumann and other pioneers freely borrowed ideas from living things. “To these people, the relation between self-organization, life and computing was obvious,” he said. “Those things somehow diverged, and now they are being reunified.”