The Complete 1💗1 Guide

What everything in the system is, where it lives, and how it is born and grows

1💗1 is a system for doing things together. A group of people — a rikma — decides together what needs doing, who does it, what it is worth, and how what is created gets shared. Instead of a manager who decides, there is one consent engine that everything passes through.

This guide walks through every object type in the system and every stage of its life, and links straight to the screen where you actually act. Every heading here is a link — click it and you are there.

The first six steps

If you have just arrived, this is the order that gets the system working for you.

  1. Sign up

    One account for all your rikmas. After signing up, a short onboarding introduces the main screens.

    Sign up

  2. Skills, values and roles

    In your profile you pick from a vocabulary shared across the whole site: what you know how to do, what matters to you, and which roles you see yourself in. If something is missing you can add it, and it joins the shared vocabulary. These fields are what the system builds your match suggestions from.

    To profile

  3. Your offering

    What you are willing to give the world — a service, a product, knowledge, equipment or time. This is what lets other rikmas and the community find you, instead of only the other way round.

    Set your offering

  4. A rikma — open one or join one

    You can open a new rikma in a minute, or join an existing one from its public page. If you are not sure yet, joining something that already runs and watching it from the inside is the better start.

    Open a rikma

  5. Lev — your daily screen

    Lev gathers in one place everything that is waiting specifically for you: proposals to approve, sales to confirm, splits awaiting your signature, match suggestions and missions in progress. If you open one screen a day, this is the one.

    Go to Lev

  6. Hub — the overview

    The hub shows the big numbers: how many votes are open, what is urgent, what has sold, and what is happening on the demand map. From there you jump straight to the relevant item in Lev.

    Go to Hub

System map — where everything is

Every screen there is, grouped by what you come there to do.

Your day to day

What is open every day — the decisions, the tasks and the time.

The rikma's brain

Everything that happens inside one rikma. These links lead to your active rikma.

Discovery pages

The public window: what the community is looking for and what it offers. Open to visitors too.

Wishes and concierge

The consumer side — say what you need and get an answer.

Money and deals

Sales, purchase requests, and keeping track of them.

Me

Your profile, preferences and devices.

Background and agreement

The material that explains why the system is built this way.

Object types and their life cycles

The system is built from only a handful of object types. Understand this list and you understand the whole system. Every object goes through the same four stages: it is born as a proposal, it is agreed, it is carried out, and it receives value.

Rikma

Project

A rikma is a group of people creating something together and sharing what they create. It is the container for everything: the values, the members, the missions, the resources, the products, the sales and the splits. Every rikma has its own decision time — how long a proposal stays open for a response before it is accepted on its own. A fast rikma sets a day, a careful one sets two weeks; that is the group's call, not the system's.

Life cycle

  1. Idea
  2. open a rikma
  3. set values and decision time
  4. add members
  5. ongoing activity
  6. split what accrued
Where it lives
All your rikmas live in the rikma brain. A rikma's public face is its project page, and that is also where people ask to join.
What you can do
Open a rikma, edit its name, description, image and external links, set the decision time, publish it as open to partners, and manage members.

Your profile and offering

User · Offerings

Your profile is not a CV but an interface: the skills, values and roles you pick come from one vocabulary shared across the whole site, so the system can cross what you know with what rikmas are looking for. Your personal offering is the active side: what you are willing to give — a service, a product, knowledge, equipment or time.

Life cycle

  1. Sign up
  2. onboarding
  3. skills, values and roles
  4. area of activity
  5. personal offering
  6. match suggestions in Lev
Where it lives
In your profile, and on the my-offering page. The match suggestions built from them reach you as cards in Lev.
What you can do
Update skills and values, add a new item to the shared vocabulary, set your area, and publish a personal offering that is visible on the discovery pages.

Mission

Mission → Pendm → Open Mission → in progress → finished

A mission is work someone takes on in the rikma's name. It starts as a template from the shared vocabulary ('build a landing page'), becomes a concrete proposal with hours, a rate and required skills, and only after consent does it open for execution. The hours approved at the end are the material your value in the rikma is derived from — which is why every step along the way needs agreement rather than an announcement.

Life cycle

  1. Mission template
  2. proposal in a vote
  3. open mission
  4. request to take it on
  5. in progress with a timer
  6. finished
  7. completion approval
  8. archive and value
Where it lives
Created in the brain → Create. Tracked in the brain → Work (in progress, kanban, gantt). Site-wide open missions live on the open missions page. Any proposal waiting for you shows up in Lev.
What you can do
Propose a mission, negotiate hours and rate, ask to take it on, run a timer, break it into small acts, upload proof of work, and approve other people's completions.

Resource

Mashaabim → Pmash → Open Mashaabim → provided

A resource is anything the rikma needs that is not work hours: money, equipment, materials, a space, a vehicle, information or a contact. The system treats it exactly like a mission — it enters by consent, it has a quantity and a price per unit, and it too counts toward the value of whoever provided it. That is what lets someone with no time but with equipment be a full partner.

Life cycle

  1. Need identified
  2. resource request in a vote
  3. wanted and open resource
  4. offer to provide
  5. provided and received
  6. approval
  7. value in the rikma
Where it lives
Created in the brain → Create → request a resource. Site-wide wanted resources live on the wanted resources page and on the demand map.
What you can do
Request a resource, set quantity, unit and price per unit, offer to supply a resource to another rikma, mark partial delivery, and confirm receipt.

Product

Matanot · simple and complex

A product is what the rikma sells. A simple product is a name, a description, an image and a price. A complex product is exactly the same, plus a recipe on top: which missions and which resources one unit requires, and how much of each. Complex extends simple rather than replacing it — every field a simple product has, a complex one has too. From the recipe the system derives cost per unit, and from there a price by margin or a fixed price you set.

Life cycle

  1. Idea
  2. product proposal in a vote
  3. approved product
  4. recipe (for a complex product)
  5. pricing: fixed or by margin
  6. published on the products page
  7. sale
  8. split
Where it lives
The rikma's products live in the brain → Money → Sales. All products on the site are on the public products page, which is also where people ask to buy.
What you can do
Propose a product, build a recipe from existing missions and resources, choose a pricing method, set available quantity and location, and publish or archive.

Sale

Sale

A sale is a record of money that came in thanks to the rikma. Its critical field is not the amount but who actually holds the money. 'The money is with me' is a sovereign self-report and is final immediately. But reporting that 'the money is with X' is a claim about someone else's financial state, so it opens as a bilateral consent between the reporter and the person said to hold it. A sale counts in balances and splits only once it is effective — never while the claim is still open.

Life cycle

  1. Report a sale
  2. link a product and a customer
  3. who holds the money
  4. if someone else: bilateral consent
  5. sale effective
  6. enters the split
Where it lives
Brain → Money → Sales, and the personal sales center. Any holding claim waiting for you appears in Lev as a card with approve, chat or counter-proposal.
What you can do
Report a sale, link product and customer, define it as recurring, approve or counter a holding claim, and record a payment that was transferred.

Split

Tosplit · Haluka · hervachti

A split is the moment what accrued gets divided among the members. The system computes each member's share from what they actually contributed — approved hours, resources they provided, products sold — and puts the proposal to everyone, not only to whoever created it. If 1lev1 itself took part as a service-providing partner, it too receives a share by exactly the same rules and with the same transparency.

Life cycle

  1. Value accrues
  2. create a split proposal
  3. a personal share per member
  4. approve, chat or counter-proposal
  5. split closed
  6. actual transfer
Where it lives
Brain → Money → Split. A split waiting for your signature appears in Lev.
What you can do
Create a split, see what makes up each person's share, approve, propose a different split, and mark transfers as done.

Decision and voting

Decision · Vots · Timegrama

Anything needing more than one person's consent goes through the same mechanism: a proposal with a clock. There is no absolute 'no' — a unilateral rejection ends a conversation. There are three ways to respond: approve, open a chat to understand, or make a precise counter-proposal. 'I received nothing' is said as a counter-proposal for an amount of 0, not as a veto. Every counter-proposal resets the clock and starts a new round, until both sides sign the same version.

Life cycle

  1. Proposal
  2. the clock starts at the rikma's decision time
  3. approve / chat / counter-proposal
  4. new round or maturity
  5. decision
Where it lives
All of a rikma's open votes are in the brain → Votes, each with its own clock. What awaits you personally arrives in Lev. Deep discussion has a separate site — the consent engine.
What you can do
Approve, open a chat, make a counter-proposal, see who has voted and how long is left, and follow earlier rounds.

Negotiation

Nego · Negotiation

A negotiation is a counter-proposal that ping-pongs until both sides sign the same version. It is not a separate mechanism but the same decision mechanism scoped to two people: a candidate and a rikma, a customer and a supplier, a sale reporter and the person holding the money. When the disagreement is too deep for a single card, it can move to the consent engine and be framed precisely there.

Life cycle

  1. First offer
  2. counter-proposal
  3. another round
  4. both sides sign the same version
  5. bound to execution
Where it lives
Inside the card itself in Lev, and in the brain's vote cards. Deep discussion moves to the consent engine.
What you can do
Counter, explain your reasoning, review the history of rounds, and close with a joint signature.

Wish and concierge

Ratson · Concierge

A wish is what you need, written in your own words with no form. The concierge receives it, understands it, and looks for an answer: an existing product, a service provider, or a group already looking for the same thing. If no answer exists, it publishes the wish to the community as an open mission or a wanted resource, and then anyone can volunteer for it. That is how a personal need becomes shared work.

Life cycle

  1. Write a wish
  2. understanding and identification
  3. suggested answers
  4. choose
  5. publish to the community if needed
  6. volunteer or supplier
  7. execution and follow-up
Where it lives
The concierge and the new-wish page. A published wish also appears on the demand map and on the missions and resources pages.
What you can do
Write a wish, set an area and a budget, open it for others to join, choose between offers, and mark that an answer was received.

Demand aggregate

Maagad · shared purchase

A demand aggregate is similar wishes from different people joining into one buying power. While it is small it is shown only as a range, without revealing who joined. Once enough demand accumulates in an area it becomes visible to suppliers, and a supplier can make a threshold-conditional offer — 'a minibus, runs at 10 sign-ups'. The offer only takes effect if the threshold is crossed in time, so no side commits alone.

Life cycle

  1. Similar wishes
  2. aggregate forming
  3. exposure threshold crossed
  4. visible to suppliers
  5. threshold-conditional offer
  6. threshold crossed
  7. it happens
Where it lives
On the public demand map, and on the aggregate's own page. A rikma also sees relevant aggregates in the brain → Opportunities.
What you can do
Join an aggregate, see how many are missing for the threshold, make a supplier offer, and follow the closing date.

Service and purchase request

Sheirut · Sheirutpend

A purchase request is the market's incoming side: someone outside wants to buy a product or receive a service from the rikma. The request arrives as a proposal, gets coordinated between the customer and the rikma (date, quantity, price), and once both sides agree it becomes work — and at the end a sale and a split. This is the path by which outside money enters the system by consent rather than as an anonymous order.

Life cycle

  1. Customer request
  2. offer and coordination
  3. both sides agree
  4. execution
  5. sale
  6. split
Where it lives
The deals page and the sales center. Requests waiting for you appear in Lev, and the products you can request are on the products page.
What you can do
Send a purchase request, coordinate date and quantity, approve or counter, mark it as done, and convert it into a sale.

Timer and acts

Timer · Act

A timer is the actual measurement of time on a mission in progress, and acts are the mission broken into small steps you can tick off. The measured hours are the material your share in a split is derived from, so they have to be accurate — which is also why they are approved at the end by the rikma rather than closed on your own.

Life cycle

  1. Mission in progress
  2. start a timer
  3. stop and resume
  4. hours summarised
  5. completion approval
  6. hours counted into value
Where it lives
On the timers page, on the mission card in Lev, and in the brain → Work → Timers. Also through the Telegram bot and the MCP interface.
What you can do
Start, stop and correct a timer, tick off completed acts, review your hours history, and submit for approval.

Process and chain

Process · Chain

A process is a container grouping missions and resources into one order — a 'product launch' holding design, development, materials and marketing. A chain is the same thing from the life-cycle angle: what is still a proposal, what is already open, what is in progress and what has finished. Together they let you see a whole project rather than a list of chores.

Life cycle

  1. Define a process
  2. attach missions and resources
  3. order and dependencies
  4. track it in the chain
  5. close
Where it lives
Brain → Flows, and in the gantt and kanban views that show the same information on a timeline and on a board.
What you can do
Create a process, attach existing or new missions and resources to it, set the order, and track progress.

The core processes, step by step

The same objects as above, this time in the order you actually do things.

  1. 1. Opening a rikma

    A rikma opens with a name, a description and values. The values are not decoration: they are chosen from the shared vocabulary, which is what lets people with similar values find you. At this stage you also set the decision time — how long each proposal stays open before it is accepted on its own. You can change it later, but it is better to start from a number that matches the group's real pace.

    How to get there: Profile → create a rikma. After creating it you land straight in the new rikma's brain.

    Open a rikma

  2. 2. Proposing a mission or a resource

    In the brain, the create tab offers three routes: a mission, a resource request, or a process that holds both. You define what needs doing, how many hours it takes, the hourly rate and the required skills — or, for a resource, what quantity at what price per unit. At this stage it is still only a proposal: it goes into a vote, not into the task list.

    How to get there: Brain → Create. There is also an AI route that scans the rikma and proposes ready-made missions for your approval.

    Go to Create

  3. 3. Negotiation and consent

    Every proposal enters a negotiation period as long as the rikma's decision time. A member can approve, open a chat to understand, or make a precise counter-proposal — 'not 20 hours but 12', 'not 150 an hour but 120'. A counter-proposal is not a rejection: it is a new version on the table, and it resets the clock and starts another round. This continues until both sides sign the same version.

    How to get there: Brain → Votes, and everything waiting for you personally in Lev.

    My votes

  4. 4. Approval by silence

    If the decision time passes and nobody responded, the last version on the table is approved automatically. This is not a technical detail but a position: silence is consent, at the pace the group itself chose. Whoever wants to influence responds in time; whoever does not, trusts the group. After approval a mission becomes open and can be taken on, and a resource becomes wanted and can be provided.

    How to get there: Each proposal shows its own clock — in the brain → Votes and on the card in Lev.

    Go to Lev

  5. 5. Execution and timers

    An open mission waits for someone to ask to take it on. Once the request is accepted the mission moves to 'in progress' and a timer opens on it. You can start and stop it from anywhere — the timers page, the mission card in Lev, the brain, the Telegram bot or the MCP interface — and the hours accumulate. You can also break the mission into small acts and tick them off as you go.

    How to get there: Timers, my tasks, and brain → Work → In progress.

    Go to timers

  6. 6. Finishing, approval and archive

    When you finish you submit the mission for approval, and you can attach proof of work — a file, a link or an image. Rikma members approve, and if someone thinks the hours are inaccurate they propose a different number instead of rejecting. After approval the mission moves to the archive and the hours count toward your value in the rikma — which is what will determine your share in the next split.

    How to get there: Brain → Work → In progress, and the completion approvals waiting for you in Lev.

    My approvals

  7. 7. From sale to split

    When money comes in you report a sale, link it to a product and a customer, and state who holds the money. If it is with someone else, a bilateral consent opens and the sale only counts once it is effective. When enough has accumulated you create a split: the system computes each member's share from the hours and resources approved for them, everyone approves or proposes otherwise, and then you mark the transfers that were made.

    How to get there: The sales center, and brain → Money → Sales and Split.

    Go to sales center

Governing rules

Five rules that explain almost every design decision in the system. If something in the interface looks strange, the answer is probably here.

There is no absolute 'no'

A unilateral rejection ends a conversation, so it does not exist here. In its place there are three ways to respond: approve, open a chat, or make a precise counter-proposal. Even 'I received nothing' is said as a counter-proposal for an amount of 0 — a claim that can be discussed, not a veto that leaves nothing to say.

Silence is consent, at the rikma's pace

Every proposal stays open for the length of the rikma's decision time. No response in time and the last version is approved. The pace is set by the group and not by the system, and a counter-proposal always resets the clock.

One decision engine for everything

A mission, a resource, a product, a sale, a split and a change to the rikma's settings all pass through the same mechanism of proposal, clock and consent. There is no bypass route for any kind of decision, which is why learning it once is enough.

A claim about another person needs their consent

Saying 'the money is with me' is a self-report and is final immediately. Saying 'the money is with X' is claiming something about someone else's financial state, so it opens as a bilateral consent. Until it closes, the sale counts neither in balances nor in splits.

Sovereignty and privacy by default

Nobody acts in your name without your approval, and any action that touches you is shown to you before it closes. Public pages show aggregate numbers rather than identities: rounded location, a range instead of an exact number, and a name is revealed only when you enter the item itself and by its own access rules.

Did not find an answer?

Short questions have an FAQ page, and a deep disagreement has its own consent engine. You can also open a conversation with the concierge and describe in your own words what is missing.

FAQ To the concierge