Concepts

How Kunuleco works beneath the commands.

The world model

Kunuleco treats being online as being somewhere. You are in a place, other people can be there with you, and the things in that place sit inside containers you control.

Two further ideas carry the rest. Access comes from holding a grant, not from appearing on a list. And your identity is a key pair on your own machine, not an account on someone else's server.

graph TD
    I[Identity: who] -->|signs in to| N[Your node]
    N -->|contains| P[Places: HOME and Halls]
    P -->|contains| C[Capsules: gated containers]
    C -->|contain| O[Objects and services]
    P -.presence: who is here.- W[Other people]
    N ---|transports: how nodes meet| T[mDNS, Veilid, Tor, IPFS]

The pages

Concept	Question it answers
Identity	Who am I, and what proves it?
Places and Halls	Where can I be?
Presence	Who else is here right now?
Trust and standing	Who decides what I can do here?
Connections	How do nodes reach each other?

Key principles

Locality. Your data lives on your node, and nodes talk to each other directly. No Kunuleco server carries your conversations. Two small lookup services at kunul.eco help with first contact (a bootstrap route registry and the short-code directory), and meet skips both when you are in the same room.

Presence is not permission. Being in a place and being able to open what is in it are separate decisions. Someone can stand in your Hall and still be unable to open a capsule there.

Transport agnosticism. The messaging layer, CapTP, is the same whether it travels over your LAN, Veilid, Tor or IPFS. If one path is blocked, the node tries another. The order it tries them in is on the Connections page.

Where to start

Start with Places and Halls for the world model, Identity for how you are recognised, and Trust and standing for what keeps it safe.