> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rotascale.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Market profiles

> Which law applies is a governed configuration resolved per decision and sealed into the record, not a setting somebody reads later.

Four market profiles ship today: **EU**, **US**, **Singapore** and
**Australia**. India is served by [Rotavision](https://rotavision.com), a
separate company that encodes the Indian instruments properly.

A profile does two things: it selects which clause maps are scored, and it
activates the identifier detection relevant to that jurisdiction.

## The profile is resolved per decision

This is the part that matters in an audit. The applicable profile is sealed into
each record **at the moment the decision was made**, so an evidence pack states
which laws applied then rather than which are configured today.

A system that reads current configuration when producing evidence is
reconstructing. Configuration drifts, and the drift is discovered in the room
where it costs the most.

## A profile that selects nothing says so

Singapore selects no clause map, because MAS FEAT is principles-based and asks a
firm to define its own objective. There is nothing enumerable to score against.

The readiness screen reports that rather than inventing a percentage. A number
against an instrument nobody encoded is a number with no denominator, and
producing one would be the single most tempting dishonest thing this platform
could do.

## Instruments mapped clause by clause

| Instrument                            | Profile |
| ------------------------------------- | ------- |
| EU AI Act (Regulation (EU) 2024/1689) | EU      |
| GDPR (Regulation (EU) 2016/679)       | EU      |
| SR 11-7                               | US      |
| NIST AI RMF 1.0                       | US      |

Instruments that are **not** mapped say so on their own pages, and there are two
different reasons which are never collapsed. DORA and ISO/IEC 42001 have
numbered articles and are unmapped because the maps are not written yet. MAS
FEAT and the UK approach have nothing enumerable to map. See
[the regulatory mapping](https://rotascale.com/regulatory/).

## Clause maps are data

Maps are YAML, validated against the evidence registry at load. A regulatory
analyst can author one without a release, and each carries a `provenance` field:
`platform`, `customer` or `hybrid`, so a reader knows whose interpretation they
are looking at.

## Identifier detection

Each profile activates the identifier families relevant to it, and every family
is a **checksum rather than a shape**. The claim is "this is a valid IBAN and
the check digits agree", not "this looks like one".

Eleven families ship: IBAN, EU VAT, three national identifier schemes (Poland,
Belgium, Norway), US SSN, ABA and EIN, Singapore NRIC and UEN, Australian TFN,
ABN and Medicare.

<Warning>
  What is **not** looked for matters as much. Names, addresses and dates of birth
  in free text carry no checksum and finding them needs a model this deployment
  does not run. Neither are card numbers or medical record numbers. A clean screen
  means no verified identifier was found, never that the payload holds no personal
  data.
</Warning>