Trust¶

Amri decides what a profile is allowed to do based on where the profile came from, not on what the profile says about itself.

A profile is a set of voice commands and the actions they run. Some profiles ship with Amri, some you write yourself, and some you download. Amri sorts each one by its provenance: the install location it loaded from. That location sets the baseline of what the profile may do.

How Amri assigns trust¶

The tier comes from the install location, so a profile cannot set its own trust. A trust field written inside a profile has no effect: it is deprecated, and Amri ignores its value. What a profile is allowed to do is set by its provenance and by the abilities you approve, which are stored in your own engine.toml. See Grants and the sandbox for those abilities.

Where it loaded from	Baseline
Amri's built-in profiles	Highest. These are Amri's own.
Maintained add-ons (signed and verified)	Elevated and pre-approved, because they are vetted.
Profiles in your own profile folder	Restricted until you approve.
Community profiles from the Workshop	Restricted until you approve.

A profile you wrote and a profile you downloaded both start at the restricted baseline. Neither one gets more until you approve it.

Approval is all-or-nothing¶

A profile declares the abilities it wants up front. When Amri loads a profile that is not already approved, it shows you that list and you approve the whole set or none of it. Approving part of it is not offered, because a profile denied an ability it needs will not work. Anything a profile does not declare, and you did not approve, is denied. Finer-grained, per-ability approval may come later.

Your decision is saved in your own config¶

When you approve a profile, the decision is written to your own engine.toml, the file you control. It is never stored inside the profile. This is the same place other permissions live, such as the allowlist for system overrides.

Because approval is tied to the abilities a profile declared, a Community profile that is updated to ask for new abilities is presented to you again. An update cannot quietly widen what a profile you already trust is allowed to do.

Example¶

A profile can state the keys it will press. Amri holds the profile to that set, plus any keys written plainly in its commands:

[profile]
name = "elite_dangerous"
output = ["up", "down", "left", "right", "space", "g"]

Amri shows this list, along with the profile's other requested abilities, when it loads a profile that is not already approved. You approve the whole set or none of it.

Where a profile lives does not raise its trust

Moving a downloaded profile into your own profile folder does not upgrade what it may do. It still starts at the restricted baseline, and you still approve it before it can act.