Configuration module — typical cases

What this page is. The recurring kinds of configuration change on Bulstrad's estate as its databases and intake queues show them, not as the design assumed them. It complements Configuration Module § 8, whose eight walks (CS-1 … CS-8) were chosen to stress the architecture; here the only questions are what is actually configured on STAGING and PROD, how often, by whom, on which environment first, and what does the module do with it. Twenty-five cases, ordered by frequency × pain; each names its rows, its tickets, the parts of the twelve it touches (Configuration Module § 7.1), its deployment set and its walk through the stages. SRD_IPROD has no audit column on any of its 81 tables, so recency comes from ALL_TAB_MODIFICATIONS, from block-level ORA_ROWSCN bucketed into months by a calibration table — an upper bound, a row counts in the month its block was last written — and from a 113-table TEST ↔ PROD count-and-hash diff; SRD_ANLT.PPA_PRODUCT_VERSIONS carries real dates.

0. What the census says F

1. Changes to existing products are at least 95 % of the work; new products are 4 of about 60 in twelve months — 4727 (09.2025, co-branded casco), 2345 «Пълна защита» (06.2026, an INSIS + ABACUS product with three IPAL seam rows), 3606 (07.2026, a copy of 3635 whose real content is a BPMN and user-task commit) and 1105 (a 2026-tariff 1100, opened on TEST 04.09.2026). Two of the four are not IPAL products.
2. ABACUS on STAGING: one EUR re-deploy of every product's rating (10–11.2025 on TEST, 12.2025 on PROD), then a steady stream of broker, channel and partner rating templates on existing products — 4704 holds 115 versions on TEST against 71 on PROD, 4710 43 / 22, 3618 18 / 7, 3636 11 / 2; thirteen online-channel templates of 06–07.2026 are unreleased — and tariff refreshes on existing products (3607 × 5 versions, 3443 × 9, 3602, 3636, 3618, cargo 110x, 4727, 3613). TEST holds 519 versions, PROD 347.
3. SRD_IPROD on STAGING, by table group: pricing factors and LOV values are the most-touched group (11 871 row-blocks in twelve months), then catalogue and covers (5 756 — 2200 / 2222 EUR limits, 3606, the 3408 re-upload, eleven new annex types), mapping IPAL ↔ INSIS (5 114), offers (2 048), validations (1 893 — CFG_FLD_VALIDATION written every month from 04.2026 to 09.2026, 29 rules OFF), labels (163 TEST-only keys, 624 PROD-only, 122 changed texts).
4. The single most-churned configuration table is the ABACUS validation layer ABC_ACCESS.CFG_ABC_FLD_VALIDATION (1 689 updates on TEST since 29.12.2025; PROD last written 04.09.2026) with its per-user, per-agent and per-group bypass lists (PROD 1 387 users · 380 agents · 144 groups, last written 03.09.2026) — thresholds and who may cross them, not products.
5. TEST → PROD is not the only direction. PROD carries configuration TEST lacks (4704 deductible definitions 96 against 32 rows, 2222 MAND validations 107 against 84, route roles on 2200 / 2222 / 3607, 600+ НКИД labels, the "User Group 2200, 2222" role, 14 more numbering offices per product), and STAGING carries unreleased work (3606, the 2345 seam, 1105, the 3635 rework, PR_PRICING_FACTORS.UI_REQUIRED — a column PROD does not have — and two TEST-only tables). Drift is a standing condition.
6. Intake, HDesk (42 configuration tickets in the OTRS "Ablera" queue): validation or check 10 · tariff or rate 10 · discount or loading 6 · questionnaire or field 4 · nomenclature 3 · new product 2 · new clause 2 · promo 1 · visibility 1 · other 3. The customer names INSIS or МАТРИЦА as a target in 38 of 42 — the half D85 places outside the module. Ask → first TEST delivery: 0–1 day when the desk changes INSIS itself, 8–24 days when Ablera configures INSIS + IPAL, 56–155 days for cross-system asks, 287–496 days when ABACUS and IPAL twins are needed; PROD arrival is confirmed in 3 of 42, „очаква доработка" is the state of 20, twelve carry explicit waiting complaints, none mentions an offer or CR.
7. Intake, Jira (68 tickets: 34 configuration, 15 master data, 19 print): 31 were applied on PROD, 26 of them the same day, 7 on TEST only; executed by Ablera IT (25), by a person running AISA-drafted SQL (14) or by Bulstrad IT (11); ten are a temporary relax followed by a revert; 30 of 68 repeat an earlier ticket in chains of three to five (four relax rounds on one MINV, five tickets for one 0 cell — KI-030, four missing-sequence tickets, five monthly BSO batches). About eleven configuration-shaped Jira tickets a month, flat.
8. The code half. Every new product on the customer line needed a plugin commit (BPMN + user tasks); every computed rule — per-person count, campaign duration, date checks — landed as code with a database toggle; the FRAME work put a column on both environments and rows on none. Handover to Development is the normal path for a new or conditional configuration, not the exception.

Top products by twelve-month row-blocks on TEST: 4704 12 775 · 4710 5 177 · 3443 5 141 · shared ALL 3 706 · 2200 3 673 · GLOBAL factor values 3 277 · 2214 3 154 · 3618 2 552 · 2222 2 445 · 3602 2 443 · 2204 1 688 · cargo 1100–1103 1 326–1 499 each. On PROD the releases land as product-family batches: 12.2025 (the EUR release), 06.2026 (2200 / 2222 EUR limits, 3443 LIABCR, KOLHIDA and MAXO templates, every offer row re-written), 07–08.2026 (CFG_PRINT_DOCS, CFG_MAPPING_LIMITS, PR_PRICING_FACTOR_ANNEX, CFG_FLD_VALIDATION_VALUES); CFG_BLANK_NUMBERS is PROD-only master data at about 100 000 new blanks and 15 000 USED flips a month.

1. The eight walks, re-read against the estate F

Three typical, one typical in shape, one recurring in another form, two architecture tests, one not a case. No CS covers the three highest-frequency kinds: threshold relax and revert, bypass and visibility lists, broker templates.

2. The cases

Format: ask · evidence · scope (parts of the twelve · stages · deployment set · shared rows) · delivery today · walk · variants · coverage today. Deployment sets as in Configuration Module § 3; write classes as in Gating § 1.

CF-01 — Threshold or LOV relax for one policy, then revert. Ask: „вдигнете временно валидацията", „да падне блокировката". Evidence: 8 Jira (SD-1570, 1577, 1584, 1592, 1614, 1669, 1827, 1903), all 04–07.2026; CFG_FLD_VALIDATION written every month 04–09.2026; 29 rules OFF on TEST, 26 on PROD; the ABACUS twin 1 689 updates. Scope: part 7 · S3 (+ S2 for CFG_ABC_FLD_VALIDATION) · one UPDATE on PROD (the blocked policy is on PROD) plus one revert · no shared rows. Delivery: the desk drafts step-1 and step-2 SQL, Ablera IT executes with the team's "target − 1" margin, the revert follows the client's confirmation; often the ABACUS twin is the real gate (SD-1669: no IPAL rule at all). Walk: H1 = policy id + rule id, no specification → S3 apply on PROD under H5 → verify by retransfer → scheduled H7 = the revert. Variants: CAR_PROD_YEAR, IV_PASSENGERS, IV_* caps in BGN-literal EUR, LOV OFF → ON. Coverage: the skill row of Data and Information Module § 0.2; Gap N (scheduled H7) fits; no CS.

CF-02 — Permanent check: add, change or explain a control. Ask: „контрола за …", „да не допуска …", „да е задължително когато …". Evidence: HDesk 10 of 42 (00098632, 00099893, 00101281, 00101359, 00103979, 00104150, 00104195, 00104411, 00072908, 00061034); Jira SD-1678, 1739, 1764, 1822, 2140; TEST CFG_FLD_VALIDATION 552 against PROD 531 (2222 84 / 107, 2227 10 / 1), PR_OPERATIONS 122 / 118 with 18 disabled, CFG_ABC_CAR_COVER_RESTRICTIONS +56, CFG_ABC_CAR_QUEST_RESTRICTIONS +10; the code half Add configurable policy date checks (17.07.2026). Scope: part 7 (+ 8, an INSIS Forms rule; + code when conditional) · S3 (+ S2) · ipal only (+ INSIS script) · shared rows CFG_VAL_OVERRULED_GRP. Delivery: Bulstrad IT flips existing INSIS rules the same day (00104150 on PROD, day 0); the IPAL and ABACUS side by Ablera in weeks to months; conditional rules become code. Walk: H1 (rule text + products) → S3 apply on TEST → H3 by the desk → H4 / H5 PROD. Variants: antedating, mandatory-when, IV cap per cover, cubic capacity ≠ 0, PML. Coverage: CS-3 in part, CS-7, Gap K — but the INSIS half, where the desk asks, is out by D85.

CF-03 — Who may bypass, who may see: overrule groups, per-user and per-agent lists, product roles. Ask: „само за посочени потребители", „група 9 / 12 / 66", „да се вижда в Портала". Evidence: PROD CFG_FLD_VAL_OVERRULED_USERS 1 387 rows (2 960 inserts, 1 506 deletes in the stats window, last 03.09.2026), _AGENTS 380, _GRP 144; IPAL CFG_VAL_OVERRULED_GRP 534 TEST / 441 PROD; LT_USER_ROLES carry thresholds in their names ("Limit 4000 EUR in 3618", "Premium below the minimum in 4704, gr. 12", "Users allowed to issue for Makso"); Routes.AllowedRoles differ TEST / PROD on 15 products; HDesk 00081163, 00097807, 00099115; SD-2140, SD-1614. Scope: parts 7 + 12 · S3 + S5 · PROD-direct identity data · all shared rows (W3: a person approves each). Delivery: Ablera IT or Bulstrad IT on PROD by name; no TEST step. Walk: the module has none — a per-identity row is neither a product write nor a specification field. Coverage: not covered (Trust and Data § 3 roles are platform roles, not these).

CF-04 — Tariff refresh on an existing product. Ask: „актуализиране на тарифата", new limits, rounding, minimum premium, EUR. Evidence: HDesk 10 of 42; PPA versions 3607 × 5, 3443 × 9 + 3, 3602, 3636, 3618, cargo × 4, 4727, 3613, 2200 / 2222; PPA_PRODUCT_LD 29 409 rows TEST against 19 630 PROD; 00100873 on TEST 15.07 → PROD 08.08.2026. Scope: part 5 (+ 1 limits, + 8 INSIS CFG_GEN_COVER_RULES 2 527 updates, CFG_GEN_RISK_LIMITS 621) · S2 (+ S3) · abacus-only or abacus + ipal. Delivery: Ablera on TEST, genRuleTable, weeks later on PROD; the customer tests with real-looking policies. Walk: CS-2 as written, plus the limits half. Variants: whole-product re-rating, one clause rate, minimum premium (PR_OPERATIONS, not PREMIUM_MIN), short-term scale. Coverage: CS-2.

CF-05 — Broker, channel or partner rating template on an existing product. Ask: a bank, a leasing house or an online channel gets its own prices and visibility. Evidence: 4704 115 against 71 versions, 4710 43 / 22, 3618 18 / 7, 3636 11 / 2; KOLHIDA_EUR, MAXO_EUR, BL / ER_RENT / ER_LEASE, thirteen *_ONLINE_DIRECT / AFF / DOVERIE / MARSH versions of 06–07.2026 on TEST only; LB_OFFER_PRICING_RULE 8 rows, CFG_SPECIAL_OFFER_MOTOR 14 rows (08.2026); roles "Show custom product 4704 / 4710 for (AVVI)"; the INSIS five-table anatomy (SD-1443, CFG_ABC_QUEST_DISC_AGENT 4 → 33 rows); HDesk 00097862, 00102031. Scope: parts 5, 3, 12 + INSIS discount configuration · S2 + S4 + S5 · abacus-only + roles. Delivery: a version per template on TEST, promoted one to two months later; the online templates unreleased. Walk: S1 must hold N templates per product — product.schema.json holds one. Variants: per-broker discount, per-channel price, co-branded product (4727). Coverage: Gap F "residual" — it is the modal ABACUS change; CS-2 mentions 71 templates and stops.

CF-06 — Discount, loading or deductible rule. Ask: „отстъпка", „завишение", „самоучастие", „лимит на отстъпката". Evidence: HDesk 6 of 42 (00057910 open since 03.2023), Jira SD-1443, 1447, 1448, 1449, 1450, 1840; TEST PR_BASIC_LD +1 per product (a new LD code, LT_LD_CODES 279 / 278); 4704 PR_BASIC_COVER_DEF deductibles 96 PROD against 32 TEST; INSIS CFG_DISCOUNTS 118 inserts (07.2026), HT_DISCOUNT_TYPE +3, PPA_PRODUCT_LD. Scope: parts 1, 4, 5, 7, 8 — three systems for one rule (IPAL LD row + ABACUS LD + INSIS discount type and rule) · S2 + S3 (+ INSIS script). Delivery: INSIS first by the desk or Ablera, ABACUS and IPAL later; 00057910 partially on PROD (only HT_DISCOUNT_TYPE). Walk: CS-3 covers the ABACUS side; the INSIS side is out (D85) though it is where the rule fires for МАТРИЦА. Variants: per-count discount, employee or client-group percentage, deductible type, owner-age loading table. Coverage: CS-3 in part.

CF-07 — Pricing-factor LOV or dependent value add. Ask: a car model, twelve installments, an average agent, an IMO field, a payment frequency. Evidence: Jira SD-1627, 1740, 1814, 2036, 1992, 1544, 1593; HDesk 00076893 / 00076960 (287 days), 00080821 (refused); PR_PRICING_FACTOR_DEPENDENT 28 340 rows, 497 inserts on TEST, 783 inserts and 758 deletes on PROD; PR_PRICING_FACTOR_VALUES TEST 4 538 against PROD 5 045 (GLOBAL 1 840 / 2 347). Scope: part 2 (+ 6) · S3 · ipal only, often PROD-direct · shared rows GLOBAL values and the SR_MESSAGES_LNG label. Delivery: drafted SQL → Ablera IT on PROD the same or next day; the INSIS twin (CFG_CAR_VALUE) by Bulstrad IT. Walk: H1 = value + label + INSIS / ABACUS codes → S3 → H5 PROD → verify the dropdown. Variants: two rows per model (car and light truck), per-country dependents, global against per-product. Coverage: /add-car; the skill row; no CS.

CF-08 — Print template registration and document-set change. Ask: CFG_PRINT_DOCS rows, copies, the per-product set, EUR renames; the INSIS print register. Evidence: 19 Jira PRINT (5 configuration, 5 INSIS rows, 9 explained); CFG_PRINT_DOCS TEST 536 / PROD 511 rewritten 08.2026; INSIS CFG_PRINT_DOC* 19 + 89 + 38 + 21 rows on 06.08.2026; 3606 reuses BST3635_*; about 60 products differ in template parameters. Scope: part 11 · S5 (+ the INSIS register and the BI template, Bulstrad IT) · ipal only. Delivery: rows on TEST then PROD; BI templates outside both. Walk: the S5 protocol; the KI-030 chain — five tickets for one 0 cell — is the "configuration present but inert" failure of Stage IPAL § PF-8. Variants: new product set, EUR migration, language variant (none for cargo in English), copies. Coverage: Stage Serdica surface; CS-6 in passing.

CF-09 — Numbering: the yearly sequence roll, per-office rows, the INSIS sequence with grant and synonym. Ask: „липсва конфигурация за номер". Evidence: Jira SD-1553, 1579, 1711, 1904, 2216; CFG_POLICY_NO_SEQ 10 073 rows in 09.2025 (policy-year 26), PROD +14 offices per product and 60–535 rows most months; 3606 rows on TEST. Scope: part 10 · S5 · PROD-direct + INSIS DDL (CREATE SEQUENCE, grant, synonym). Delivery: Ablera IT on both databases, usually after a failed transfer (INT_TRNSF_FAIL, ORA-00001). Walk: Gap AB says DDL is "never configuration" and goes to Development at Hd; the estate does it monthly as configuration. Variants: new product, new year, new office, counter collision. Coverage: Stage Serdica numbering; the skill row; /add-agent office counters.

CF-10 — Cover limit, deductible definition or sublimit on an existing product. Evidence: SD-1822 (74 covers), HDesk 00104001 (13 products), 00103956, 00061034; PR_BASIC_COVER_DEF 2200 305 / 314, 4704 32 / 96, content differs on 20 products; CFG_GEN_RISK_LIMITS 621 updates on TEST. Scope: parts 1, 8, 9 · S3 (+ INSIS script) · ipal only + INSIS. Coverage: Gap J residual.

CF-11 — Label, translation or message fix. Evidence: SD-1463, 1921, 1989, 2183; 163 TEST-only keys, 624 PROD-only, 122 changed texts (90 CAR_COLOR_*). Scope: part 2 · S5 · shared rows by definition · ipal only + a cache refresh · PROD-direct. Coverage: Translations; the skill row; the module's label sweep assumes a new product.

CF-12 — New clause or cover on an existing product, with its LD, limit, print, INSIS clause and seam. Evidence: HDesk 00097807, 00102452, 00087147, 00104195; CFG_GEN_COVERS +15 on TEST; 2200 covers 72 / 74; 3607 PR_BASIC_COVERS content. Scope: parts 1, 3, 5, 8, 9, 11 · S2 + S3 + S4 (+ S5, + INSIS) · abacus + ipal + INSIS script. Coverage: CS-3, CS-6.

CF-13 — Package or offer change (LB_OFFERS, LB_OFFER_COVERS, LB_COVERS_DEF, LBRR_*). Evidence: 2200 18 offers and 2222 8 with changed content, LB_COVERS_DEF 2200 6 / 2 and 2222 18 / 6, 4704 LB_OFFER_COVERS 511 rows changed, LBRR_COVER_DEPENDENCY 169 rows in 07.2026, every PROD LB_OFFERS row re-written 06.2026. Scope: parts 3, 4 · S4 · ipal only. Coverage: Stage Offer; CS-4 nominally.

CF-14 — Questionnaire question, answer or object field. Ask: „въпрос във въпросника", an IMO field, „Тип" КХ1–3. Evidence: HDesk 4 of 42; INSIS CFG_QUEST_* 22 + 52 + 22 rows on 21.07.2026, two mandatory questions valid from 06.2026 delivered the same day; the IPAL twin (PR_PRICING_FACTORS, CFG_ABC_LD_QUEST) months later. Scope: the optional questionnaire part + part 2 · S3 (+ INSIS). Delivery: INSIS by the desk in 0 days; IPAL and ABACUS by Ablera in 200+ days. Coverage: § 7.1 "questionnaire → S3"; CS-1's 91-row questionnaire is the new-product shape only.

CF-15 — IPAL ↔ INSIS seam change for a changed or new product (CFG_MAPPING_COVERS / FLFLD / _VALUES / LD / OBJECT_TYPES). Evidence: written monthly on TEST (2 710 · 372 · 283 · 164 · 520 · 762 row-blocks); 2345 has three rows; 2200 72 / 74; CFG_MAPPING_LD +1 on 48 products; SD-1980, SD-2184. Scope: part 9 · ipal only. Coverage: D85 "one script run once" — the seam tables are the fourth most-written group.

CF-16 — Copy-of-product or variant (3606 from 3635 single; 4727 co-branded; 1105 = 1100 with the 2026 tariff; 2227). Evidence: 3606 on TEST in 20 tables; the development census 06.07 and 02.09.2026 (BPMN + user tasks + i18n). Scope: all twelve parts by copy + code (a process per product) · S1–S5 + Hd. Coverage: CS-1's donor idea (CG-2) — the real shape is a clone plus a Development case, not a 13-sheet specification.

CF-17 — INSIS-native new product with ABACUS rating and an IPAL seam only (2345 «Пълна защита»; 3410 asked 05.2025, nothing anywhere). Evidence: INSIS TEST HT_INSR_TYPE, CFG_GEN_CONDITIONS tariff rule PD, three covers, AB_CFG_RATE_ABC_ON; PPA 06–07.2026; a 155-day wait. Scope: parts 5, 6, 8, 9 · S2 + INSIS script · abacus-only. Coverage: not covered — the module is IPAL-first and declares INSIS out.

CF-18 — Product re-upload or catalogue correction from a changed specification (3408 on 04.09.2026; the 3635 rework; 3607 in three tickets). Evidence: the 3408 TEST-only rows; HDesk 00065573 („Има още много работа", 105 days and two years); CS-3's board changing 3 000 EUR / 0.15 % to 5 000 EUR / 0.1 % mid-thread. Scope: any part · an S1 revision → the affected stage. Coverage: CS-7; Gap U; the module's "amend, do not replan" rule.

CF-19 — Promo or time-boxed campaign (2214 / 2215 „65 години"). Evidence: SD-1524, 1721, 1727, 2183; PR_PRICING_OVERRIDES 2214 and 2215 five rows each; CFG_DISCOUNTS.CAMPAIGN_ID unused. Scope: part 5 + code + part 3 · S2 + S4 + Hd · two H7 (stop offering, remove). Coverage: CS-4, Gap N — once in twelve months.

CF-20 — Product visibility: routes and roles (Routes.AllowedRoles, LT_USER_ROLES). Evidence: 15 products differ TEST / PROD; 2200 / 2222 restricted on PROD to UR_INTERNAL;UR_COMMERCIAL_PROPERTY; 3607 opened to agents on PROD; 13 products with empty roles on PROD and full lists on TEST; HDesk 00099115. Scope: part 12 · S5 · PROD-direct. Coverage: the route and label check skill; KI-052.

CF-21 — Master-nomenclature reload (НКИД 344 positions, cargo goods groups, car values). Evidence: CFG_PROP_ACTIVITY 815 / 169 / 662 on TEST 04.06.2026; 600+ LT_DETAIL_COMPANY_ACTIVITY_* labels PROD-only; 00080821 refused („не е възможно да сменим номенклатура, на база на която се тарифира"); SD-1446 (287 days). Scope: part 2 + INSIS · shared rows (W3). Coverage: not covered.

CF-22 — BSO blank batch (50 000 green cards + 50 000 stickers). Evidence: SD-1591, 1722, 1789, 1944; PROD about 100 000 FREE rows a month. Scope: the optional part · PROD-only master data · /add-bso. Coverage: § 7.1 optional; Support-shaped, listed for completeness.

CF-23 — Commission rule set (CFG_COMMISSION_EXP 40 rows reloaded 08.2026 on both; SRD_PR.CF_COMM_PRODUCTS; six COMMISSION tickets). Scope: the optional part · S3. Coverage: § 7.1 optional.

CF-24 — Process or contract-type registration (FRAME contract types, 32 files on 04.09.2026; PR_ANNEX_TYPES.CONTRACT_TYPE present on both environments and NULL on both; startedFor; the 3606 BPMN). Scope: the process part (D86) + code. Coverage: D86 — registration in S3, the process in Development; on the customer line the two always ship together.

CF-25 — Environment reconciliation before configuring. TEST ≠ PROD in both directions: the UI_REQUIRED column TEST-only; 4704 deductibles PROD-only; 2222 MAND rules PROD-only; two TEST-only tables; typo keys '47040' and '3607333'; effective dates per environment for the same template. Evidence: 117 products with a difference over 104 comparable tables. Scope: the estate prober's work before any S3 or S5 plan; a diff report as the first artefact. Coverage: Gap Z (shared impact keys) in part; the four-layer release-audit method exists in v1 memory (test_prod_release_audit.md); not a module case today.

Census challenges

What the real changes ask of the module page and its stage pages. Each is a challenge to a written rule, with the rule the changes suggest; the design disposition is recorded below.

• Census finding The module is new-product-first; the estate is delta-first. Four new products in twelve months, two of them not IPAL products, against hundreds of monthly row changes to the existing sixty; eight of the ten configuration pages assume a specification arrives. Suggested rule: for a delta case S1's input is the estate itself — the existing product read back through the export round-trip of Configuration Module § 6 — plus a one-line ask, and the "specification" is a diff.
• Census finding The five-stage two-phase flow does not fit a one-row change. CF-01, 03, 07, 09 and 11 are one to fifty rows, executed on PROD the same day by a named person, with no TEST step and often a scheduled revert. Suggested rule: a delta fast path** — H1 = target rows + rule text, one stage, one guarded statement through the same write executor and auditor, H5, verification by re-running the operator's action, H7 scheduled — a tenth of the ceremony with the same gates.
• Census finding PROD-direct is routine, and PROD is sometimes ahead of TEST. The module says nothing customer-facing changes before the release; the estate shows 4704 deductibles, 2222 mandatory checks, route roles, НКИД labels and office sequences that exist only on PROD, and a column that exists only on TEST. Suggested rule: the deployment set names a source of truth per table group**, and the estate prober emits the TEST ↔ PROD diff (CF-25) as the first artefact of every case; the write auditor checks the column set of every target before H5.
• Census finding Half the customer's asks are INSIS-side, and D85 excludes them. 38 of 42 HDesk tickets name INSIS or МАТРИЦА; CFG_GEN_COVER_RULES (2 527 updates), CFG_DISCOUNTS (118), CFG_QUEST_* (96), CFG_PRINT_DOC* (167) and HT_INSR_TYPE changed on INSIS TEST in the window; the desk delivers questionnaire and Forms-rule changes there in 0–1 day while the IPAL and ABACUS twins wait 100–500 days. "One PL/SQL script run once per product" describes the seam rows, not this stream. Suggested rule: either the module owns an INSIS delta stage over the oracle-insis write connector, or Stage IPAL § The INSIS side states that CF-02, 06, 12, 14 and 17 are delivered half by someone else, and the sign-out names who.
• Census finding The ABACUS-only set is right, but its modal member is the template, not the tariff. Gap F ("one tariff.template per specification — residual") is the most frequent ABACUS change of the year. Suggested rule: product.schema.json gains templates[] with selector and roles (Stage Normalization § WS-3), and the sign-out records which templates were deployed where.
• Census finding Validation thresholds and bypass lists are the highest-frequency configuration, and § 7.1 gives them one row. CFG_ABC_FLD_VALIDATION 1 689 updates, per-user lists 2 960 inserts, CFG_FLD_VALIDATION every month. Suggested rule: a case type of their own with the relax-and-revert pair, the ABACUS twin, the bypass identity rows and the "OFF but present" audit (SD-1764, SD-2140).
• Census finding Shared rows are the norm, not the collision case. GLOBAL factor values, SR_MESSAGES, LT_LD_CODES, LT_USER_ROLES, the overrule lists — CF-03, 07, 11 and 21 write nothing else. Suggested rule: W3 "never a shared row without a person" (Write Envelopes) becomes a first-class step of the walk, not a refusal.
• Census finding Time-boxed is not configuration alone. The only promo in twelve months was code (campaign_dur) plus rating plus one label; CFG_DISCOUNTS.CAMPAIGN_ID has never held a row. Suggested rule: Gap N reopens as a Development + Configuration pair with two H7s.
• Census finding Recurrence is the signal the module lacks. 30 of 68 Jira configuration tickets re-occur — five for one 0 cell (KI-030), four relax rounds on one MINV, four missing-sequence tickets. Suggested rule: a Configuration case opens with "has this row been touched before, and what was the permanent fix?" through the experience consult, and the fast path refuses to relax the same rule a third time without raising the permanent change (second-identical-fix rule).
• Census finding Elapsed time today is the product's real cost, and § 6 does not measure it. Ask → TEST: 0–1 day when the desk changes INSIS, about three weeks when Ablera configures both systems, three to sixteen months for ABACUS and IPAL twins and nomenclatures; PROD confirmed in 3 of 42; twelve explicit complaints; one ticket closed „поради забава". Suggested rule: the module's evaluation (Configuration Module § 6) grades the middle band collapsing to days and the long band becoming a stated Hd rather than silence, not "a product configured from a 13-sheet template".
• Census finding Configuration and code ship together on this customer line. Every new product needed a plugin commit; every computed rule became code with a database toggle; the FRAME work put a column on both environments and rows on none. Suggested rule: Hd is the normal path for CF-02, 16, 19 and 24, and the release sign-out (Configuration Module § 1b) names the commit beside the script.

Architecture disposition — 07.09.2026

P The case journeys and wire/protocol specification answer the census questions without expanding the module charter. The interactive walkthrough traces every case on this page through requests, records, prompts, messages, gates, execution, reversal and next-request learning. These are design decisions and offline acceptance criteria, not proof of deployed behaviour.