1. How to read the inventory
Each action belongs to a primitive family (Orchestration §4), and most are available to both surfaces with different renderings. Chat rendering: chips, buttons, cards, sheets, voice. Live rendering: approach, gesture, object, place. Role gates refer to Roles; “sovereign” means the member’s own hand is required (press-and-hold in Chat; the practice version teaches it in Kidunaversity).
2. The baseline actions
Converse (the relationship)
| Say / ask anything |
type or talk; the ally answers with contextual actions |
walk with your ally and talk |
the root action; everything below is reachable from it |
| Switch voice ↔︎ text mid-thought |
composer ↔︎ voice band; in-flight words stay peripheral |
voice is native in Live |
one conversation, two input modes |
| Set / edit the Contract |
pull down; edit prose; ally confirms its reading |
— |
quoted back wherever it binds |
| Correct a claim |
reply to any Account claim; artifact amends; correction prints |
— |
the accountability lever |
| Sign the weekly Seal |
press-and-hold; contest a line → card |
— |
sovereign |
| Inspect (the Vigil) |
“show me what you’re doing right now” from any citation |
watch your ally move; open its work |
leaves no residue |
| Add information (wisdom, files, notes) |
upload / paste / say it; metadata auto: author, name, handle, description |
hand an object to your ally |
defaults per your Contract; level set at add-time |
| Set access level |
one sentence or the grant sheet: public · private · secret · personal |
— |
changeable anytime; binds every persona instantly |
| Ask the record |
“what did I tell you about…” — the answer, expanded, cited |
— |
the record is asked, never browsed |
| Grant / request access |
grant card (sovereign for secret-tier); ask-permission flows to the author |
— |
private = ask or code; author can set terms, including paid |
Invite / Connect (people and trust)
| Connect with a member |
relationship card; each side sets grant levels |
meet and exchange |
grants live on the Relationship — between two people it is a relationship, never a “connection” |
| Extend a code |
sovereign: press-and-hold; code travels any channel |
hand the ember/ticket |
the one act never delegated |
| Demand / re-present a code |
ally handles at the gate; one line in the Account |
gate object |
Gatekeeper action |
| Invite a non-member |
ally checks: member? → connect/invite; not? → email invite |
— |
the ally routes the right invitation automatically |
| Form a Guild |
name it, say who’s in |
gather and name |
feather-light; no wallet; sharing scope only. When money-shaped activity appears around a guild, the ally offers promotion to an alliance in one sentence — guilds never grow wallet features of their own |
| Form an Alliance |
charter sentence + codes; Squads wallet created |
founding circle |
on-chain per Protocol |
| Enroll someone (Organizer work) |
Enroller carries the conversation; the code is still yours |
— |
lineage recorded off-chain; commissions attach only to Compute purchases, never to enrollment itself. Dunas may also run no codes at all — open door, or invite-first then open |
Decide (Forums)
| Propose |
say the intent; the proposal comes back with its duna commands shown as a receipt — members see exactly what will execute if it passes |
post at the Forum |
the receipt’s plain sentence is machine-generated from the command’s parameters, never hand-written (Protocol §3) |
| Discuss |
in the proposal sheet or by tagging through your ally |
the circle |
|
| Vote |
sovereign: set your pass/fail token (one per member, free, equal) |
place the stone |
never costs; never weighted by wealth; members enrolled with an Institution cannot vote on that Institution’s contracts (their enrollment is always visibly disclosed) |
| Watch execution |
command receipt → execution shown step by step as commands run atomically |
the built thing appears |
|
| See policies |
ask; the living rulebook, cited |
policy-stones |
passed proposals become policies |
Pay (money — always via the web surface)
| Check balances |
prose answer + meter chip |
— |
reads across bank/crypto/Compute |
| Send Compute / USDC |
say it → authorize on the cream web page (nothing but the act) → receipt line returns to Chat |
— |
R4 web money surface; mobile app never touches payments |
| Buy / reload Compute |
join (the duna’s initial purchase — $100 for Kinship Duna) and reload flows on web |
— |
Institutions: $1K, enroll ≤10, reload for members. A Compute purchase is the one event that pays lineage commissions where a duna runs lineage: immediate on USDC, pending until fiat bridges on-chain (Real Work, Real Money §3) |
| Alliance treasury actions |
proposal → vote → settlement (issue Compute · send to member · send to alliance) |
— |
the only three alliance vote types (Protocol §2) |
Make (creation)
| Make a thing (page, bot, agent, regimen) |
intent → shape card → strike (sovereign) |
build in place |
three conversational beats; Builders extend the palette |
| Adopt / use a made thing |
via claims or by asking; code policy governs |
encounter it in the world |
|
| Register a domain / page / artifact |
ally gives the TXT record (domain), embeds a code (page, content), or records a hash (photo, video); verification confirms; the artifact becomes registered — traceable to member, ally, alliance, organization |
— |
Protocol §4; renders as registered vs unregistered — never “trusted,” never “accountable” |
Enter (Live and its Moves)
| Enter a portal |
portal card, tap-to-enter, abortable crossing |
step through |
entering costs nothing; no hold-to-enter |
| Take a role |
offered inside a training; your ally may wear a role/name |
costume/mask |
sim flag only |
| Practice-sign |
inside Kidunaversity, over sim proposals with visible commands |
the teaching version of the gesture |
practice currency is named inside the fiction |
| Leave |
say so, or the exit |
walk out |
nothing inside affected the Kidunaverse |
3. Duna commands are actions too
The Forum-executable command families (treasury, Compute, membership, Programs, alliances, organizations, governance, economy, commerce, identity — Protocol §3) are the organizational half of this inventory: actions a duna takes when a proposal passes. Member actions above feed them (propose, vote); the receipt anatomy makes the join visible.
4. Extension rule
New actions register with: name · family · surfaces · role gate · level behavior · command(s) invoked. If a proposed action can’t fill that line, it isn’t an action yet. The total inventory lives in the graph and this page tracks the baseline; dunas’ custom actions appear in their variance rows (Organizations §3).
Changes in v4.6: lineage commission notes on Buy Compute and Enroll. v4.5: registration extended to pages, content, and media; “registered / unregistered” vocabulary. v4.4: receipt sentences machine-generated only. v4.3: Institution recusal on Vote; guild-to-alliance promotion offer. v4.2: track created. Full history: versions.