What NORKÄRŸM is
NORKÄRŸM (also written NORKARYM, without accents) is a small software studio from Catalonia.
We design, build and maintain our own digital products: a platform for organisations, a desktop app, a predictive mushroom map, an online course and talks.
It is run by its two co-founders, Adrià and Dani.
The apps in IKARYA
IKARYA is for businesses and the self-employed. Each organisation installs, from its app centre, only the apps it needs. IKARYA is in beta and goes to production in phases: team and shifts first, then bookings, then the public website, and invoicing last. The apps below are in development.
Team and time
- Team: shifts, who is in today, and a mailbox for payslips.
- Bookings: bookings and occupancy.
- Calendar: appointments and the organisation's calendar.
- Chat: messages inside the organisation.
Sales and stock
- Orders: customer orders, with shipping.
- Catalogue: the services and products you offer.
- Inventory: what you have in stock.
- Purchasing: orders to suppliers.
- Payments: getting paid by customers.
Online and with others
- Public address and website: each organisation gets its own address and public web page.
- Network between organisations: organisations that work together can connect.
- WhatsApp channel: to talk with customers on WhatsApp.
- Electronic signature: to sign documents.
At the desk
- Mascot: with voice dictation.
- Desktop mode: a way of working in IKARYA as on a computer desktop.
Future
Economy and finance
We are preparing invoicing for VeriFactu, Spain's new system for verifiable invoices. It is not available yet.
Month-end closing, taxes and the depreciation of assets are also in preparation.
How we build: crew coding with Claude Code
We call it crew coding. It is not "vibe coding". A person directs a crew of Claude Code agents. Each agent has a role, its work is reviewed by other agents, and everyone follows written rules. People make every decision that matters.
Read the full article: Crew coding with Claude Code →
The crew
On one workstation, several Claude Code sessions work at the same time. Each one takes care of one part: an app, a module or a project. Each works on its own copy of the project and in its own space on the computer, so sessions never step on each other's work or on the people's running environment.
A few sessions do not build product. They coordinate, and each one is named after its role. None of them governs: they watch, warn, route work, or carry out what a person decided.
- Dashboard
- what is waiting for a person's decision, and the versions that go public
- Messages
- between sessions, and each person's decision to whoever must act on it
- Tax and legal
- questions go to the person in charge and to our advisers
- Security
- keys and passwords, permissions, third-party software and reviews
- Screens
- the visual line: reviews every screen change
- Tests
- automatic tests that fail, quality checks and trial runs of the app in a test environment
- Tools
- for the agents: automatic alerts, small programs and work guides
- Machine
- memory, disk space and the cost of the computer
- Housekeeping
- whatever nobody is waiting for: forgotten work and weekly cleanup
- Releases
- the versions that go public
The rules that make it reliable
- The first rule: do not make things up. An agent that is not sure asks whoever knows. "I don't know" is a good answer.
- Plan before code. A new feature, screen or permission starts with a short written plan. The screen, security and legal reviewers read it at the same time, before any code exists.
- Every merge into our products needs a person's yes.
- Heavy work (installs, builds, test suites, screenshots) goes through a shared queue, so the machine does not choke.
- Every message between agents uses one format, with three types (information, question or blocker), and is signed, so a person can always tell who said what.
- Lessons learned are written down where every agent can read them.
The forge
An internal console that builds apps with agents under human supervision.
A real example: this website
This page was rebuilt by a new Claude Code session. It first wrote a plan in a GitHub thread (an "issue"). The legal reviewer checked the legal notice, the screen reviewer checked the layout, and the security reviewer checked what would become public. Another session checked every fact against its source. A co-founder made the decisions from a phone.
Several machines, one way of working
The crew does not live on a single computer.
- Each co-founder's computer has its own crew of agents, with the same roles.
- A separate testing machine runs its own testing agent.
- Agents on different machines never talk to each other directly. They write in a GitHub thread (an "issue"), and every message is signed with who sent it and from which machine.
- People make the decisions from their phones.
- IKARYA Desktop already has remote access: one shared computer can serve several people, and it is designed so that none of them sees what the others are doing.
It works: it has been tested with two people on two devices.
The coordination app
A desktop app with a dashboard that keeps people and agents in step. It tells each person what is waiting for them, with a recommended option, and sends alerts to their phone. It tells agents when to summarise what they remember so they do not run out of memory, and puts sessions to sleep and wakes them up to save memory. A chat view is being built.
GitHub
GitHub holds it all together: plans in threads, reviews in change proposals, lessons in a shared thread, and the common memory between machines. The rules are in the crew section.