Conduct

How a resolved composition may move — into custody, between compositions, and out into the world.

A resolved composition does not move on its own.

It moves only through an explicit, deliberate action you take. Nothing about receiving, holding, or being near a composition creates authority over it beyond what that one action grants. Permissions are specific to the crossing that created them — a crossing never grants more than it states.

Save

Save is a custody crossing: it asks Composium to hold your resolved composition in your account.

Save requires you to be signed in. It does not, by itself, happen merely because you're signed in — you have to choose it, every time.

Custody does not create ambient authority over anything beyond what you saved. It does not reopen the composition for further work. A new composition always requires a new, separate entry into the instrument.

Remove from Vault

Removing a composition from your Vault takes it out of your visible custody. This is a different, narrower act than deleting it: removal changes what you see; it does not by itself erase the composition's content. See Delete composition, below, for the act that does.

Delete composition

Deleting a composition asks Composium to erase its content, not just stop showing it to you. This is a separate, further action from Remove from Vault, and is treated as one.

Deletion reaches everything about that composition Composium can lawfully erase. Where something must still be kept — such as a payment record required for accounting — its content is stripped from that record rather than left in place, and the record itself is kept only to the extent the law requires it.

Reference

A new composition may hold an explicit, stated relationship to one you already hold. A reference is created only through an explicit, authorized action — it is never inferred, assumed, or created as a side effect of proximity or prior activity. Creating one does not merge the two compositions and does not reopen the earlier one.

Send

Send moves your Card outward, through a channel you choose, to a destination you choose. It is a deliberate, one-time push, not a standing connection.

Once a Card leaves through Send, what happens to that copy is between you, the recipient, and whatever platform carried it. Composium's authority over the composition remains what it always was; it does not follow the Card outward. Sending a Card never transfers ownership of the composition by itself.

The public Card

A released Card is reachable at its own address, so it can be shared and viewed without needing an account. Anyone who receives that address can view the Card. They cannot act on it, alter it, or gain any authority over your account through it.

Sharing a Card, in any form, never transfers ownership of the composition by itself.

Offering to Composium

You may choose to offer a resolved composition to Composium for possible further work. This creates only the specific possibility you asked for — never an automatic session, project, or ongoing relationship.

Exit

Exit closes the active runtime. It ends the composing session and whatever authority that session held.

Exit does not undo a crossing you already made. A Card you saved stays saved. A Card you sent stays sent. Exit closes what is still open; it does not reach backward.

What does not travel with a Card

A Card carries its Tone, Composition, Conduct, and the minimum provenance needed to recognize it as genuinely Composium's. It does not carry your account, your runtime, your other compositions, or any authority over Composium's systems. Receiving a Card never grants any of these, no matter how it was received. The Card may leave; the runtime does not.

The principle

A resolved composition moves only through an explicit crossing.
Nothing moves by proximity, by inference, or by default.
Custody does not create ambient authority.
Sharing does not itself transfer ownership.
What a crossing grants is exactly what it states — no more.