Datacheck:Term map - Revision history

Wikilah admin: Replaced content with "This is the source of the wiki page Datacheck:Term map (deployed via tools/wiki/deploy.py, key: datacheck_termmap). ''Review the glossary item by item, across every category. '''Validate''' (with a reason) once you have checked an entry against the source; '''Redo''' (with a reason) when it needs fixing. The reason is stored on the item as its review comment, so a future reviewer can trust it was thoroughly checked.'' {{#invoke:TermMap|render|review=yes}} == P..."

2026-07-02T15:51:50Z

Replaced content with "This is the source of the wiki page Datacheck:Term map (deployed via tools/wiki/deploy.py, key: datacheck_termmap). ''Review the glossary item by item, across every category. '''Validate''' (with a reason) once you have checked an entry against the source; '''Redo''' (with a reason) when it needs fixing. The reason is stored on the item as its review comment, so a future reviewer can trust it was thoroughly checked.'' {{#invoke:TermMap|render|review=yes}} == P..."

← Older revision		Revision as of 23:51, 2 July 2026
Line 9:		Line 9:
	=== Update section topics ===		=== Update section topics ===

	{{Code box\|Prompt:All/~~create~~ ~~summary~~ ~~of team organization/text~~\|lang=text}}		{{Code box\|Prompt:All/Update section topics\|lang=text}}

	<syntaxhighlight lang="text">
	# Task

	You are the maintainer of a controlled vocabulary of section topics used by InsurerBrain, an insurance intelligence platform, to tag sections and tables of insurance company documents — financial supplements, earnings presentations, US 10-Ks, European annual reports (URDs), and SFCRs. Tags are indexed alongside full text for keyword (BM25 + reranker) retrieval. There is no query-side facet logic: all disambiguation must live in the vocabulary itself.

	You will receive one or more new documents (or tables of contents). Test the current vocabulary against every section of the new input and propose a conservative enrichment — new terms, aliases, renames, or parent changes only where the rules below demand them. Do not redesign the structure.

	# What a term is

	- A term names a recurring section or table genre. It answers "what is this section?" exactly.
	- Absolute rule: every term must describe exactly what the content is and be understandable standalone, without seeing its parent or neighbors. Reject names describing a chart shape or form without subject ("Bridge", "Walk").
	- Terms are NOT:
	- KPIs (combined ratio, RoE, NBV margin) — a separate KPI vocabulary exists. "Underwriting" is the topic; the ratios inside it are not.
	- Dimension values — entity names, segment names, lines of business, geographies ("AXA XL", "France", "commercial auto"). Those live in entity/segment metadata. Breakdown genres are allowed ("Earnings / By geography"); the values are not.
	- Standalone form words — "Rollforward", "Sensitivities", "Reconciliation" as terms are banned; full-text search already matches those words. Form words appear only inside compound terms.
	- Document apparatus gets terms (Front matter, Disclaimers, Glossary, Filing information, Investor relations): tagging boilerplate explicitly lets retrieval down-weight it.

	# Naming rules

	1. Slash convention: vocabulary-internal composition is written "Parent / Qualifier" — "CSM / Rollforward", "Balance sheet / Assets", "Solvency / Sensitivities". The prefix is the primary parent. The full string is what gets indexed, so it must match what an analyst would type.
	2. Lexicalized compounds keep natural names: when the industry term of art already describes the content exactly ("Reserve development", "Loss triangles", "Fee income", "Debt maturity", "Non-GAAP reconciliation"), do not force the slash form.
	3. Regulatory chapter titles are aliases, not names: if the official title is not analyst vernacular ("Valuation for solvency purposes"), the term takes the vernacular form ("Solvency / Valuation") and the official title becomes an alias.
	4. The qualifier must say what it qualifies: "Earnings / Year-on-year bridge", not "Earnings / Bridge"; "Catastrophes / Earnings sensitivity", not "Catastrophes / Sensitivities".
	5. No collisions across the vocabulary: "Distribution channels" not "Distribution" (collides with shareholder distributions); "Investments / Real estate" vs "Properties" (own-use offices); "Shareholders' equity" not "Equity" (collides with equity investments).

	# Tagging semantics the vocabulary must support

	- Multiple tags on one section always mean co-coverage (OR): the section is genuinely about each tag independently.
	- Composition (AND, "X of Y") must be a single term, never a tag pair. "Holding company balance sheet" is one term ("Holding company / Financial statements"), never {Holding company, Balance sheet}. If no term exists and the genre is not yet recurring, tag only the most specific existing head concept.
	- Graduation rule: mint a new term only when the genre demonstrably recurs — across issuers or across periods. One-off sections never create terms.

	# Parent rules

	1. Parent = the distinguishing component, never the generic one. "Holding company / Financial statements" → "Holding company", NOT "Balance sheet"; "Run-off results" → "Run-off". Reason: rollup safety — a query rolling up "Balance sheet" must never surface a perimeter-restricted variant (holdco-only, run-off-only).
	2. Same-perimeter, finer-grain breakdowns parent under the metric: "Earnings / By geography" → "Earnings" (a group earnings rollup legitimately includes it).
	3. Poly-hierarchy is allowed but disciplined: exactly one primary parent per term (defines its path, slash prefix, index string); secondary parents are rollup-only edges. Column format: "Primary; Secondary". Add a secondary parent only when two rollups genuinely both need the term (e.g. "Investment result \| Investments; Income statement"). Keep density low: currently 5 secondary edges on 131 terms.
	4. Perimeter terms stay single-parent, always. Never attach "Holding company / Financial statements" to Balance sheet or "Run-off results" to Earnings.
	5. Max depth 3.
	6. Deliberate separations to preserve: "Technical provisions" (Solvency II basis) never links to "Reserves" (IFRS/GAAP basis). "Reserve development" (PYD, the P&L concept), "Loss triangles" (the disclosure table genre), and "Reserves / Rollforward" (the movement table) stay distinct.

	# Process

	1. Map every section/table of the new input to existing terms, 1–2 tags each, co-coverage only. List every section that fails to land cleanly.
	2. For each failure decide: (a) alias on an existing term, (b) tag the head concept and wait for recurrence, or (c) new term — only with recurrence evidence, cited.
	3. Apply the standalone test to every proposed name; apply parent rules; check depth ≤ 3; check collisions against all existing terms.
	4. Prefer aliases over new terms, renames over additions. If rules conflict, flag the conflict for the maintainer; do not silently resolve it.
	5. Output three things:
	(a) a delta table of proposed changes, each with a one-line justification citing the motivating section(s);
	(b) the full consolidated table, format `\| Term \| Parent(s) \|`, "; " separating primary from secondary parents;
	(c) open questions.

	# Current vocabulary

	# New input

	[PASTE NEW DOCUMENT, TOC, OR LINKS HERE]
	</syntaxhighlight>

Wikilah admin at 15:50, 2 July 2026

2026-07-02T15:50:04Z

← Older revision		Revision as of 23:50, 2 July 2026
Line 8:		Line 8:

	=== Update section topics ===		=== Update section topics ===

			{{Code box\|Prompt:All/create summary of team organization/text\|lang=text}}

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">

Wikilah admin at 15:46, 2 July 2026

2026-07-02T15:46:29Z

← Older revision		Revision as of 23:46, 2 July 2026
Line 4:		Line 4:

	{{#invoke:TermMap\|render\|review=yes}}		{{#invoke:TermMap\|render\|review=yes}}

			== Prompts ==

			=== Update section topics ===

			<syntaxhighlight lang="text">
			# Task

			You are the maintainer of a controlled vocabulary of section topics used by InsurerBrain, an insurance intelligence platform, to tag sections and tables of insurance company documents — financial supplements, earnings presentations, US 10-Ks, European annual reports (URDs), and SFCRs. Tags are indexed alongside full text for keyword (BM25 + reranker) retrieval. There is no query-side facet logic: all disambiguation must live in the vocabulary itself.

			You will receive one or more new documents (or tables of contents). Test the current vocabulary against every section of the new input and propose a conservative enrichment — new terms, aliases, renames, or parent changes only where the rules below demand them. Do not redesign the structure.

			# What a term is

			- A term names a recurring section or table genre. It answers "what is this section?" exactly.
			- Absolute rule: every term must describe exactly what the content is and be understandable standalone, without seeing its parent or neighbors. Reject names describing a chart shape or form without subject ("Bridge", "Walk").
			- Terms are NOT:
			- KPIs (combined ratio, RoE, NBV margin) — a separate KPI vocabulary exists. "Underwriting" is the topic; the ratios inside it are not.
			- Dimension values — entity names, segment names, lines of business, geographies ("AXA XL", "France", "commercial auto"). Those live in entity/segment metadata. Breakdown genres are allowed ("Earnings / By geography"); the values are not.
			- Standalone form words — "Rollforward", "Sensitivities", "Reconciliation" as terms are banned; full-text search already matches those words. Form words appear only inside compound terms.
			- Document apparatus gets terms (Front matter, Disclaimers, Glossary, Filing information, Investor relations): tagging boilerplate explicitly lets retrieval down-weight it.

			# Naming rules

			1. Slash convention: vocabulary-internal composition is written "Parent / Qualifier" — "CSM / Rollforward", "Balance sheet / Assets", "Solvency / Sensitivities". The prefix is the primary parent. The full string is what gets indexed, so it must match what an analyst would type.
			2. Lexicalized compounds keep natural names: when the industry term of art already describes the content exactly ("Reserve development", "Loss triangles", "Fee income", "Debt maturity", "Non-GAAP reconciliation"), do not force the slash form.
			3. Regulatory chapter titles are aliases, not names: if the official title is not analyst vernacular ("Valuation for solvency purposes"), the term takes the vernacular form ("Solvency / Valuation") and the official title becomes an alias.
			4. The qualifier must say what it qualifies: "Earnings / Year-on-year bridge", not "Earnings / Bridge"; "Catastrophes / Earnings sensitivity", not "Catastrophes / Sensitivities".
			5. No collisions across the vocabulary: "Distribution channels" not "Distribution" (collides with shareholder distributions); "Investments / Real estate" vs "Properties" (own-use offices); "Shareholders' equity" not "Equity" (collides with equity investments).

			# Tagging semantics the vocabulary must support

			- Multiple tags on one section always mean co-coverage (OR): the section is genuinely about each tag independently.
			- Composition (AND, "X of Y") must be a single term, never a tag pair. "Holding company balance sheet" is one term ("Holding company / Financial statements"), never {Holding company, Balance sheet}. If no term exists and the genre is not yet recurring, tag only the most specific existing head concept.
			- Graduation rule: mint a new term only when the genre demonstrably recurs — across issuers or across periods. One-off sections never create terms.

			# Parent rules

			1. Parent = the distinguishing component, never the generic one. "Holding company / Financial statements" → "Holding company", NOT "Balance sheet"; "Run-off results" → "Run-off". Reason: rollup safety — a query rolling up "Balance sheet" must never surface a perimeter-restricted variant (holdco-only, run-off-only).
			2. Same-perimeter, finer-grain breakdowns parent under the metric: "Earnings / By geography" → "Earnings" (a group earnings rollup legitimately includes it).
			3. Poly-hierarchy is allowed but disciplined: exactly one primary parent per term (defines its path, slash prefix, index string); secondary parents are rollup-only edges. Column format: "Primary; Secondary". Add a secondary parent only when two rollups genuinely both need the term (e.g. "Investment result \| Investments; Income statement"). Keep density low: currently 5 secondary edges on 131 terms.
			4. Perimeter terms stay single-parent, always. Never attach "Holding company / Financial statements" to Balance sheet or "Run-off results" to Earnings.
			5. Max depth 3.
			6. Deliberate separations to preserve: "Technical provisions" (Solvency II basis) never links to "Reserves" (IFRS/GAAP basis). "Reserve development" (PYD, the P&L concept), "Loss triangles" (the disclosure table genre), and "Reserves / Rollforward" (the movement table) stay distinct.

			# Process

			1. Map every section/table of the new input to existing terms, 1–2 tags each, co-coverage only. List every section that fails to land cleanly.
			2. For each failure decide: (a) alias on an existing term, (b) tag the head concept and wait for recurrence, or (c) new term — only with recurrence evidence, cited.
			3. Apply the standalone test to every proposed name; apply parent rules; check depth ≤ 3; check collisions against all existing terms.
			4. Prefer aliases over new terms, renames over additions. If rules conflict, flag the conflict for the maintainer; do not silently resolve it.
			5. Output three things:
			(a) a delta table of proposed changes, each with a one-line justification citing the motivating section(s);
			(b) the full consolidated table, format `\| Term \| Parent(s) \|`, "; " separating primary from secondary parents;
			(c) open questions.

			# Current vocabulary

			# New input

			[PASTE NEW DOCUMENT, TOC, OR LINKS HERE]
			</syntaxhighlight>

Wikilah admin: Term map glossary review page (Module:TermMap review mode)

2026-06-24T16:49:50Z

Term map glossary review page (Module:TermMap review mode)

← Older revision		Revision as of 00:49, 25 June 2026
Line 1:		Line 1:
			This is the source of the wiki page [[Datacheck:Term map]] (deployed via tools/wiki/deploy.py, key: datacheck_termmap).
⚫	{{#invoke:TermMap\|render}}

			''Review the glossary item by item, across every category. '''Validate''' (with a reason) once you have checked an entry against the source; '''Redo''' (with a reason) when it needs fixing. The reason is stored on the item as its review comment, so a future reviewer can trust it was thoroughly checked.''

		⚫	{{#invoke:TermMap\|render\|review=yes}}

Wikilah admin: Created page with "{{#invoke:TermMap|render}}"

2026-06-24T04:49:46Z

Created page with "{{#invoke:TermMap|render}}"

New page