Documentation — the Target Market door

get_target_market serves the target market statement a product's manufacturer has filed for its International Securities Identification Number (ISIN): who the product is for and who it is not for, in each market's own category words; how it may be distributed; what the product is; which documents and assessments stand behind it. The manufacturer's agent files it with file_target_market, signed and versioned; it is stored at the node of the product's home market, signed again under that node's key, and receipted. A distributor's agent reads it in one call, and get_orderability reads it in the same call that clears the product — so the conditions a regime places on a distributor that the manufacturer's statement discharges are shown discharged, with the statement's version and signature on the outcome.

serving

The statement — fields

AIO-10060 v1.2 §6 (aio-10060.org).

field	meaning
`subject`	the ISIN; resolved through the apex index to the record and its home node
`manufacturer`	the manufacturer's Legal Entity Identifier (LEI) and name as on the LEI record
`version · filed_at · supersedes`	integer version, filing time (UTC), the version it replaces
`markets`	the markets the statement speaks for, each by its chapter; a statement may name one or many
`positive_target_market`	per market, in the regime's own category words: the client categories; knowledge and experience; ability to bear loss; risk tolerance; objectives and needs — the European MiFID Template (EMT) field groups, carried as the manufacturer states them
`negative_target_market`	per market, the categories and profiles the product is not for, in the regime's words
`distribution_strategy`	execution-only · with appropriateness · advised · portfolio management — as the regime names them
`product_scope_statement`	the manufacturer's statement of what the product is, by instrument class, mapped to the scope bridge term
`documentation`	the product documents the regime requires (key information document, prospectus, factsheet) — URL, document date, hash at filing
`assessments`	the assessments the manufacturer states it performed (product approval, scenario analysis, charging structure review) — named, dated, not attached
`source`	where the statement came from: an EMT file (its version and hash) or a direct filing
`sig · kid`	the manufacturer's signature over the canonical statement and the key id it was made with
`node_sig`	the home node's signature over the stored statement, under its record key, as for any record

1 The statement

1.1: Unit: one ISIN, one manufacturer (by Legal Entity Identifier), one version → one signed statement. A change is a new version with a supersedes link; every version stays published.
1.2: Target market: for each market the statement names, the positive target market — client categories, knowledge and experience, ability to bear loss, risk tolerance, objectives and needs — and the negative target market, each in the regime's own words, as the manufacturer states them.
1.3: Distribution: the distribution strategy the manufacturer sets — execution-only, with appropriateness, advised, portfolio management — as the regime names them.
1.4: Product: the manufacturer's product scope statement, mapped to the term the market's rule uses through the same scope bridge get_orderability uses.
1.5: Documents and assessments: the key information document, prospectus or factsheet by URL, date and hash at filing; the assessments the manufacturer states it performed, named and dated.
1.6: Source: the European MiFID Template (EMT) file the statement was derived from, by version and hash, where there is one; otherwise a direct filing.
1.7: Two signatures: the manufacturer's, under its filer identity or its own published key; the home node's, under its record key. Both verify offline.
1.8: Nothing judged: the door stores and serves the manufacturer's representation. It does not assess whether the statement is adequate; that duty stays with the firm.

2 Two calls

call	who	what comes back
`file_target_market`	the manufacturer's agent, under its filer identity	the version number, the node's signature, the filing receipt id
`get_target_market`	any agent	the statement at its current version (or the version or as-of time asked for), both signatures, the chapter sections it speaks to, the read receipt id
`list_target_market_versions`	any agent	every version for the ISIN with filed_at and supersedes
`verify_target_market`	anyone, offline	whether both signatures verify against the published keys

2.1

One read:

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_target_market","arguments":{"subject":"DE0007164600"}}}

at https://mcp.gettargetmarket.ai/mcp .

2.2

One filing:

{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"file_target_market","arguments":{"subject":"<ISIN>","manufacturer":"<LEI>","statement":{…}}}}

with the filer identity in the authorization header.

2.3

The vocabulary is the open standard at aio-10060.org (the statement object, the signature rule and the discharge rule); the clearance signals are at acm-68000.org; the chapter is the market's Book of Markets page at sm-eco-10060.org/market/<market>/.

5 Provenance

5.1: Every statement is signed by the manufacturer under its filer identity or its own published key, and by the home node under its record key (EdDSA); verify against the key ids named in the statement.
5.2: Every filing and every read is receipted at https://mcp.rco-records.ai/mcp with the door as writer and the filer or reader as caller; the receipt's answer_hash binds it to the exact signed statement; verify_receipt is public and works offline against rco-records.ai/.well-known/jwks.json.
5.3: Every version ever filed stays published, unchanged, for as long as a receipt cites it. An outcome that cited version 3 resolves to version 3.
5.4: The documents a statement names are re-fetched nightly; a document that no longer resolves or whose hash has changed is marked drifted on the statement, never removed, and the manufacturer is the one to file again.
5.5: Whether a regime accepts the manufacturer's statement as the evidence a distributor may rely on is a sourced field of the Book of Markets, read from the regulator's own text; where the regime is silent, the condition stays with the firm even when a statement is on file.

gettargetmarket.ai