1 ῖon

* It’s still early days; this project is a pre-alpha minimum-viable-product – features are missing, the query system needs optimising, etc. This document describes both where ion is, and also what it’s been designed for – any features that are still upcoming have been marked with an asterisk.

ion is a universal media processing pipeline. ion’s core purpose in life is to take an input folder and produce an indexed and optimised version of that folder, optionally publishing it, while responding to changes in the input by rebuilding only what has changed. ion can act as an invisible content management system, or a generator for websites, apps, ebooks, audiobooks, and perhaps, one day, even realbooks.

1.1 Questions

If you want to know more, then one advantage of ion being entirely self-contained is that it (the source below) can be pasted to a language model to ask it questions about ion, like: was ion written by a human or by a machine, what is the purpose of ion, what is its aim, where is it in its development, is it quickly becoming one of the greatest content management systems currently in existence, etc, etc. This is useful because ion is currently basically undocumented.

1.2 Trajectory

1.3 History

This project began as the scaffolding for a nutrition calculator, with the goal of balancing the often conflicting ideals of health and resource usage. Initially, the goal was to be able to reverse engineer Huel (sorry Huel) by importing a large amount of nutrition data, particular the USDA FoodData, using a constraint solver to find the inputs, and then using the imported statistics to determine its health charistics as well as its costs economically and ecologically, particularly land use, for both individuals and for large groups of people.

This turns out to be an interesting challenge – the answer of how much land does something like Huel use depends on your personal requirements mixed with the capabilities of the land in question – the answer is different for an Indian woman that wants to eat organically than it is for a British man that wants to eat cheaply; the personal requirements, land yields, and ecological impacts vary significantly; the resource usage changes completely across supply chains (or trees, or graphs, properly speaking), and so the complexity of this question spirals out of control very quickly. A human diet can be modelled as a supply graph, but the statistics needed to answer these questions lie in many varied sources, from government nutrition databases, to information buried in the tables of messy and obscure documents. This was the crucible that designed ion. Achieving this goal ended up requiring a new approach to content management, and so ion was born.

With this as the foundation stone, ion became a fairly capable data hub, or node. This was the first stage. These nodes are designed to connect with others, to share information as a mesh network. This is to enable a broader goal – beyond consolidating the web and making it work offline, the ultimate goal of ion is to sit as the foundation for an open federation of interconnected franchises.

The view is that the world needs a safety net. As a thought experiment, imagine an empire, like a fast-food franchise, except it’s an open, decentralised network of non-profit, non-loss, nutritionally-balanced restaurants and hotels that receive and redistribute the fundamentals. This is the primary reference project.

At the heart of a restaurant is the menu, and the ticketing system; a menu is an inventory; a ticket is a subset of that inventory; a recipe, and even ingredients are inventories; porridge is a collection of oats; oats are collections of nutrients; proteins are collections of amino acids; blogs are collections of articles; invoices are collections of products and services; everything is an inventory.

A network of nutritionally-balanced kitchens seems then to be an accountancy problem, and this is where ion aims to sit, as the scaffolding that supports the inventory component; a node that indexes, balances, and connects inventory components together, so that they may form, in the real world, a decentralised safety net.

Until then, it also makes nice websites (coming soon), and you can watch its development from here.