Sovrnti

View saved version →

---
name: decision-brief
description: Turn Sovrnti benchmark results into a short decision brief for an executive, a board, a security lead or a procurement team, with the sources stated. Use it when the user asks for a summary, a memo, a board paper or a recommendation based on Sovrnti results. An example is "write a one-page brief for our CIO on collaboration suites in Germany".
---

# Write a decision brief

Explicit user instructions take priority over this workflow, including on length and format.

## Inputs

Ask at most two questions, and only for what is missing:

- **Audience.** For example a CIO, a CISO, a board or a procurement team.
- **Decision.** For example choose a product, narrow a list, keep the current product or migrate.
- **Scope.** A market, or two or three named products, and the place: a country, a region or "world".

## Steps

Gather the facts with as few calls as possible. Deeper views use the user's Sovrnti credits.

- **A whole market:** `sovrnti_market_get_snapshot`. Add `sovrnti_market_get_sovrntimax` if sovereignty is a hard requirement.
- **Named products:** `sovrnti_product_compare`.
- **A specific "why" question:** `sovrnti_qq_sherpa`. It answers only from what Sovrnti has scored and returns citations.

Use the same place in every call. If results from earlier in the conversation already cover the scope, reuse them.

## Output

Keep it to about 400 words unless the user asks otherwise.

1. **Title and date.**
2. **The decision,** in one line.
3. **Options,** one line each with its trade-off. Recommend one only if the results clearly support it, and say why.
4. **Evidence.** A short table with the scores the tools returned.
5. **Risks and what to verify.** Contract terms, configuration choices, and anything the results do not cover.
6. **Sources.** "Source: Sovrnti, <date>", with the views used.

## Rules

- Use only facts the tools return. If the brief includes your own reading of the results, label it as your assessment, not as Sovrnti's.
- Sovrnti's terms allow short extracts in internal documents such as board papers, with "Source: Sovrnti" and the date. Do not reproduce full result sets for publication.
- Use plain language. Put numbers before adjectives.
- If a tool returns an error, say so and state what the brief could not cover.
- If a tool says the user has no credits left, pass its message on as it is. Do not suggest a workaround.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: market-benchmark
description: Benchmark a whole technology market with Sovrnti for one country, region or the world view. Use it when the user asks who leads a market, how products rank on raw capability, or what changes once sovereignty rules apply. Examples are "benchmark collaboration suites for France" and "which office suite holds up for a German public body?". Do not use it for two or three named products; use product-comparison instead.
---

# Benchmark a market for a place

Explicit user instructions take priority over this workflow. If the user asks for one view only, give that view.

## Inputs

- **Market.** Pass the user's words as they are. The tools accept a market name, an alias or an id. If the market is unclear, call `sovrnti_markets_list` and confirm it with the user.
- **Place.** A country name, an ISO code, a region or "world". If the user names no place and the answer could depend on location, ask once which country matters. Do not guess a country.
- If the user asks about a place Sovrnti may not cover, call `sovrnti_geographies_list`. Entries marked "coming soon" cannot be scored yet.

## Steps

Call only the views the question needs. Deeper views use the user's Sovrnti credits.

1. **Head-on view.** Call `sovrnti_market_get_snapshot` with the market and the place.
2. **Raw capability.** Call `sovrnti_market_get_capaindex` when the user wants a ranking.
3. **Under full sovereignty rules.** Call `sovrnti_market_get_sovrntimax` when sovereignty matters to the user.
4. **What sovereignty moves.** If steps 2 and 3 rank products differently, call `sovrnti_market_get_delta` to show which products move and by how much.

The world view applies no sovereignty rules. There, Sovrnti Max matches the Capability Index, so skip step 4 and say why.

Use the same market and the same place in every call.

## Output

1. **Answer first.** One sentence: who leads, and whether sovereignty changes that.
2. **Table.** Product, Innovation, Control, Scale, rank on raw capability, rank under sovereignty rules. Copy the scores exactly as the tools return them.
3. **Three findings,** one line of reasoning each: the most capable product, the product with the most control, and the best balance.
4. **What sovereignty changes.** Products that lose the most, products that hold, and products the rules do not affect. A product that does not move is not affected by these rules. It is not missing data.
5. **Next step.** Two or three products worth a closer look. Offer a side-by-side comparison.
6. **Source line.** "Source: Sovrnti, <today's date>, <place>."

If the host shows Sovrnti's interactive view, summarise it. Do not repeat every number.

## Rules

- Use only the scores, ranks and products the tools return. Never invent a score, a rank or a product.
- If a product the user names is not in the results, say that Sovrnti does not score it in this market for this place.
- If a market is on the roadmap, say it is not scored yet and offer the closest published market.
- If a tool returns an error, say so in plain words and offer the next best step.
- If a tool says the user has no credits left, pass its message on as it is. Do not suggest a workaround.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: product-comparison
description: Compare two or three named products with Sovrnti on innovation, control and scale, for one country, region or the world view. Use it when the user has finalists or specific products in mind. Examples are "Microsoft 365 or Nextcloud Hub for a French hospital?" and "how do Google Workspace and Proton compare on control?". For a whole market, use market-benchmark instead.
---

# Compare named products

Explicit user instructions take priority over this workflow.

## Inputs

- **Products.** Two or three, named as the user wrote them. Aliases such as "M365" work. If the user names more than three, ask which three matter most.
- **Place.** A country name, an ISO code, a region or "world". If the user names no place and the answer could depend on location, ask once which country matters. Do not guess a country.
- **Priority.** If the user states what matters most (for example control of data, or features), use it to order the answer. If not, do not invent one.

## Steps

1. Call `sovrnti_product_compare` with the products and the place. The market is optional: the tool finds the market the products share.
2. If the tool rejects the request because the products are in different markets, pass on its message. Suggest comparing products within one market.
3. If sovereignty is the user's concern, call `sovrnti_market_get_delta` for that market and place. Read only the rows for the compared products.

Use the same place in every call.

## Output

1. **Answer first.** One sentence on how the products differ for the user's stated priority. If the user stated no priority, say where each product leads instead of naming a winner.
2. **Table.** Capability area by product, as the tool returns it, then the Innovation, Control and Scale scores.
3. **Where each product leads and where it trails.** Two lines per product.
4. **What to verify.** Two or three questions for each vendor, taken from the areas where the product scores lowest or where the result depends on configuration. Present them as points to check, not as findings.
5. **Source line.** "Source: Sovrnti, <today's date>, <place>."

If the host shows Sovrnti's interactive comparison, summarise it. Do not repeat every number.

## Rules

- Use only the scores and capability areas the tools return. Never invent a score or a capability.
- If a product is not found, say that Sovrnti does not score it, and offer the closest products the tools return.
- If a tool returns an error, say so in plain words and offer the next best step.
- If a tool says the user has no credits left, pass its message on as it is. Do not suggest a workaround.

Referenced files: 1 — file references are metadata, not package contents.