1. 

   tawasuyu · wawa

   An operating system that boots with no Linux underneath

   wawa (“little one” in Quechua) is a kernel of its own that powers on the machine and runs every program in its own cage. A program doesn’t ask for permissions: if nobody signed the capability it needs, the door doesn’t even exist for it. And every piece is stored by its fingerprint, so if something gets corrupted it shows at once.

   ~24,700 kernel lines · boots end to end · 23 applications isolated from one another

   read the project →
2. 

   takana

   A Linux that rebuilds itself, and that you run by talking to it

   takana builds every program from its source code, isolated and offline, and stores the result by its fingerprint: building twice gives the same binary, byte for byte. On top runs a channel through which an AI understands the system, proposes changes and applies them, with a safety net: tested on the side, confirmed by hand, and every change undone with one command.

   869 programs built and sealed · the Rust compiler and Linux 6.16.12 kernel rebuilt from scratch

   read the project →
3. 

   hifas

   When work can go on without coordinating, with a proof

   hifas (the threads a fungus grows with) decides, with a proof rather than by eye, when several copies of the same data can work without talking to each other. When the answer is yes within limits, it hands over the mechanism: a certificate that tells each copy how much it may spend alone. And its lab notebook keeps, dated, every promise that had to be withdrawn.

   89 tests · frozen API in production: tawasuyu consumes it

   read the project →
4. 

   tawasuyu · Llimphi

   A graphics engine from scratch, entirely in Rust

   Llimphi (“colour, shine” in Quechua) draws every pixel of the suite: the desktop, the editor, the media player, and also the screen of the in-house operating system, where no known engine can paint. The journal tells what is its own and what it borrows.

   79 interface components · in-house 3D engine · the same code already runs on Android

   read the project →
5. 

   tawasuyu · mirada

   A whole desktop, written from scratch

   mirada is the program that draws the windows, shares out the screen and listens to keyboard and mouse. It isn’t a theme on someone else’s desktop: it is the desktop, and it’s the one used every day to write the rest of the suite.

   Multiple monitors · sessions that resume · shortcuts and looks to taste

   read the project →
6. 

   tawasuyu · pluma

   A text that lives in several languages at once

   In pluma, a document lives alongside its translations, summaries and changes of tone. When the original changes, the versions derived from it mark themselves stale and regenerate with one button. AI is one more thread, not the driver, and the provider can be swapped without touching the document.

   Translate, summarise, change tone and compare two documents as if they were layers

   read the project →
7. 

   tawasuyu · puriy

   A browser with no Chromium underneath

   puriy (“to walk” in Quechua) reads the HTML, applies the CSS and runs the JavaScript of real sites with an engine written from scratch; the picture is this very page, as it sees it. Third-party scripts run in a cage you authorise.

   In-house style and JavaScript engines · third-party scripts, caged

   read the project →
8. 

   tawasuyu · nakui

   Accounting with no monthly rent

   nakui does real double-entry accounting, brings its own spreadsheet and invoices by each country’s rules, written in a file rather than in a different build of the program. It runs on your server: the books don’t live in anyone’s cloud, and they leave in open formats the day you want to go.

   Journal, ledger and balance sheets · round-trip with Excel, verified

   read the project →
9. 

   tawasuyu · agora

   An identity nobody lends you

   With agora your identity isn’t kept by Google or Microsoft: you keep it, proven with cryptography and portable between machines. With it you sign concrete, revocable permissions: who may run what, and until when.

   Keys already issued and in use inside the operating system

   read the project →
10. 

    tawasuyu · khipu

    A notebook that thinks with you, not for you

    khipu is named after the knotted cords the Andes used to keep their records. It’s the lab where language models, one’s own notes and daily practice talk to each other: the open experiment of how an AI can accompany thinking without replacing it.

    Notes that sync between machines with no central server

    read the project →
11. 

    humanoid

    A phone that answers to no one

    Nine native Android apps —the launcher, the keyboard, the terminal, notes, weather, the recorder— written for a phone of your own: no store in between, no account to open, no telemetry. Download, install, use; and like everything else, read line by line.

    9 apps in Kotlin and Compose · direct APK download, with its fingerprint to verify it

    read the project →

1. 

   tawasuyu · Making · October 24, 2026

   Your WordPress, without WordPress: the same site to the pixel, with its store, without a single line of PHP

   A WordPress site is a program that runs every time someone visits, with its database, its plugins and its admin doors open to the internet. qhatu takes it whole, identical to the pixel —and with its store, if it has one—, and leaves nothing to execute: the same site, faster, and without a single line of PHP.

   read the article →
2. 

   tawasuyu · Root · October 23, 2026

   Arje: the init that remembers — your whole system as a signed commit

   The first program that runs on your computer decides everything that follows, and on almost every Linux that program is systemd: a giant governed by a corporation's calendar. Arje replaces it with 48 thousand lines of Rust that do what systemd cannot: remember every state of the system, explain every death, and resurrect the whole machine over the wire.

   read the article →
3. 

   tawasuyu · Sovereignty · October 16, 2026

   Tawasuyu: a sovereign system end to end, built on the Andean chakana

   Boot, screen, browser, files and identity: on an ordinary computer, every layer has an owner who isn’t the person using it. tawasuyu replaces each one with a piece of its own written in Rust, and takes its blueprint from the Andean tradition, where sovereignty belonged to the community.

   read the article →
4. 

   tawasuyu · Llimphi · October 12, 2026

   Qt, GTK, Flutter, Electron? No: a graphics engine from scratch, entirely in Rust

   Llimphi draws every pixel of tawasuyu, even inside an operating system that boots with no Linux underneath. Why it exists, how it works and how true that “from scratch” really is.

   read the article →

The whole journal →

1. 

   i · architecture

   A whole system, one person to talk to

   I design the complete system: domain, data, interface and deployment. One person from the first sketch to the first real invoice, for problems that no longer fit an off-the-shelf product.

   In production from day one · legacy integration without surprises · documentation your team can run

2. 

   ii · artificial intelligence

   AI that works instead of posing

   Language models, search by meaning and agents built into the workflow, measured in cost, latency and quality like any other component. No flashy demos that don’t survive a Monday.

   Internal assistants that unclog whole teams · search over your own documents · no lock-in to one provider

3. 

   iii · infrastructure

   Infrastructure that is yours

   Platforms that rebuild the same every time, that can be audited and that run in your cloud or on your servers. Delivered with the source, the binaries, the keys and the manifests: if tomorrow you need to move, you move.

   Deployments that rebuild themselves after a failure · security and performance audit · zero lock-in

4. 

   iv · method

   Model first, code after

   Diagnosis comes before implementation. Every architecture decision is a decision about priorities in another language, and it’s made with the business at the table, not afterwards.

5. 

   v · method

   What’s delivered can be touched

   Short cycles and concrete pieces: a demo, a deployment, a load test. No roadmaps you can’t touch, no slide-deck milestones.

6. 

   vi · method

   A fixed price per phase

   A fixed cost per stage, with no open-ended hours and no drift. The estimate is a contract, not a hope.

1. 

   front i

   Instruments for the old questions

   The deep disciplines —clinical psychology, contemplation, fine neurophysiology— don’t need more slogans: they need instruments. Recording devices, reproducible archives, falsifiable models. Building that base so the old questions find their experimental counterpart, without dissolving into self-help or surrendering to reductionism.

2. 

   front ii

   Science with instruments of its own

   Hypotheses that don’t depend on foreign licences or on platforms that change their terms tomorrow. Sensors, simulators and scientific databases run at home, reproducible. If the experiment depends on the vendor, so does the conclusion, and nobody is going to audit the vendor.

3. 

   front iii

   The extraordinary, in ordinary hands

   Graphics engines, verifiable operating systems, robust cryptography, natural synthetic voice: frontier technology deployed where it’s needed most, not where it pays best. A cooperative should be able to run what a bank runs; a rural school, what a university lab runs.

4. 

   front iv

   Street-level infrastructure

   A farmer with their archive. A doctor with the medical record that travels with the patient. A private network for whoever needs one. A neighbourhood council with its own cloud. Sovereignty not as a flag or a speech: as everyday infrastructure, small, that comes on when the lights come on.

5. 

   front v

   Code that carries a world

   The words code is named with aren’t neutral: a variable called khipu arranges memory differently from one called record. Building from categories of one’s own —from the south, the countryside, the deep traditions— is an act of engineering. What goes through the repository decides what survives.