☰ Contents
AISA v2.0 / Technical documentation / Challenges Register (appendix)

Challenges Register (appendix)

F verified factP decided planC open challenge

Generated by pwsh scripts/wiki_challenges.ps1 from every C statement in the wiki; the triage columns come from challenges_triage.csv. Edit the challenge where it is made and the triage in the CSV — never this page.

Every row carries the investigation or proposed solution of 02.09.2026 where one exists — the measured evidence is in Measurements 2026-09-02 and the two challenge rounds in Challenge Rounds 2026-09-02 — matched by page and text, so the pointer survives renumbering. The CH-nn ids are assigned at generation time, in document order: they renumber whenever a C is added or removed, so cite a challenge by its page and subject, never by its id. Classes follow the decision register: A needs evidence that exists (a query, a file, a repo); B needs a decision by the owner; C is deferred by design — it needs data that does not exist yet and names the event that will produce it; D is a build item — settled by building it. ? means not yet triaged.

Class Count
A — evidence 4
B — decision 1
C — deferred by design 21
D — build item 1
Total 27

A — evidence

Id Page · section Challenge Owner Closes when Investigation / proposed solution
CH-09 Rating Files · Challenges Cache invalidation across replicas is asserted here but the invalidation call has not been exercised from the platform. First deployment to a multi-replica environment settles what the deployer must send. platform team first deployment to a multi-replica environment the invalidation call has not been exercised from the platform
CH-11 Stage Abacus · Challenges Confirm the QT obsoletion state on the target branch before a production-bound product whose process carries a quotation step (Stage IPAL remark); UI evidence so far is from serdica-ui master, backend from bulstrad-staging (KI-054 documents drift). Vladimir QT obsoletion landed on the target branch (Source work item) Challenge Rounds § CS: production simulation criteria (B — Vladimir + Bulstrad)
CH-16 Stage Application and Verification · UI-driven application LDAP provisioning of aisa.ui. (Bulstrad IT); whether „Enable login" runs under a non-administrator role. Vladimir + Bulstrad IT the aisa.ui.<env> accounts exist on QA (password in the directory; roles from the platform - D134) no platform identity exists in PROD IPAL today (Challenge Rounds § R2 § 3: seven EMPL accounts)
CH-20 Agents Memory · 7.3 The past-case entries P Past cases are not articles; their entry shape is § 5. Retrieval mechanics — title/grep index versus vector search (the estate retains Qdrant as a rebuildable index [F: docs/architecture/health-ai/00-program.md, inspected 31.08.2026]) — are decided by m… support author measure both retrieval mechanics on the migrated corpus (Agents Memory § 7.2) Repo evidence: retrieval mechanics and the two-independent-uses rule

B — decision

Id Page · section Challenge Owner Closes when Investigation / proposed solution
CH-17 Support Module · 0. The agents P Waiting is a route, not a gap (D147). A request that can wait moves to a waiting state that names three things. Its trigger: a step only the customer can perform — the customer-question step type of Stage Solution Take § 1; a step only an external owner… Vladimir a decision whether a deferred wish pauses the contract clocks (clocks.pause_states) D147 defined the waiting state and left the deferred-wish pause state open

C — deferred by design

Id Page · section Challenge Owner Closes when Investigation / proposed solution
CH-01 Delivery · 5. Work streams Open, from the component inventory: platform team the first plug-in's build the lead-in to the component-count row below, not a challenge of its own
CH-02 Delivery · 5. Work streams The component counts of § 2.1–§ 2.4 are what this wiki names today. The first plug-in's build finds what was still assumed; the inventory is amended in the same change, like the Whitelabel Catalogue. platform team the first plug-in's build amends the inventory in the same change D94 - the inventory is Delivery 1.4; amended like the Whitelabel Catalogue
CH-03 Source Details · DG-3 — Environment = branch set across the source's repositories Its internals are therefore sourced from the branch's retirement dossiers, not from reading its code; the source/intentgpt domain is built on the first case that touches it. source author first Source case touching intentgpt Challenge Rounds § CS: the source/intentgpt domain
CH-04 Value and ROI · 5. How the ROI number is produced P P The protocol for the two missing inputs (Challenge Rounds § R2 § 10): ten consecutive real interruptions across at least three developers and both channels, four timestamps each written as they happen — T0 noticed · T1 ticket work starts · T2 ends · T3 … development manager the ten-interruption CSV exists (two calendar weeks) Challenge Rounds § R2: § 10 switch-cost protocol + 25 % rule per type
CH-05 Components · Challenges The acceptance bar for a configured tariff — one reconciling quote, or a set across a factor matrix — is undecided and defines what verified means; settle it on the first slice (Product design § 11 DEC-6). S2 author the first abacus-only slice fixes the number of worked examples reconciliation 3 DEC-6; same question as Quote Verification
CH-06 Factor Sources · Challenges Whether the locality probe runs once per environment at connection time or per factor at plan time is open; the three queries are cheap enough for either, and the first case with a remote-sourced factor decides. S3 author the first case with a remote-sourced factor either shape is affordable; the case decides
CH-07 Quote Verification · Challenges How many worked examples make an acceptance — one reconciling quote or a factor matrix — is DEC-6 of the reconciliation, still open, and is fixed by the first slice. S2 author the first abacus-only slice reconciliation 3 DEC-6; same question as the Components acceptance bar
CH-08 Rating Files · Challenges The applyAlways and vocabulary checks above are assertions the estate has no tooling for. Whether they belong in the abacus configure skill or in a standing configuration.verifier check is decided with the first abacus-only slice. S2 author the first abacus-only slice decides skill or standing check the assertions are the same either way
CH-10 Shared Vocabulary · Challenges Whether the tier distribution is measured once per customer at plug-in time or re-measured per case is open — it is the same question as the dated conventions of Product Configurator § A-19. S1 author the second customer plug-in reconciliation 1 A-19 - conventions are measured per estate, each count carrying its date
CH-12 Stage Normalization · The protocol here P Existing products: mapping to live codes is an S1 step (Configuration Module § 8 E). When the material changes a selling product, the normalizer — not the tariff analyst, which has no database — reads the live catalogue through a read connector and fill… S1 author the first existing-product case through S1 the mapping step is defined (Configuration Module § 8 E); its cost is measured on the first case
CH-13 Components · Challenges A source that is not in the workspace has unmapped seams; its node is built on the first case that touches it. source author the first Source case touching that source Challenge Rounds § CS-2.1: the source/intentgpt domain - stub now, summarizer on first case
CH-14 Source Module · 0.1 Its branch of the memory tree built on first case — repo absent here; known: Beth+AI components, health path being replaced source author first intentgpt case Challenge Rounds § CS: the source/intentgpt domain
CH-15 Data and Information Module · Challenges The HDesk and mail streams — counted 02.09.2026 (Challenge Rounds § R2 § 1) F: hdesk/ is the OTRS queue "Ablera", the customer's product-change and CR queue — 39 of its 52 tickets are Configuration-module intake, not support; the OTRS support stream rea… support author re-count on a full read-only export of the OTRS queue Challenge Rounds § R2: § 1 HDesk and mail streams
CH-18 Agent Framework · Challenges Eval-set budget: a full re-run on every memory write is unaffordable; batching by domain, on a schedule and before publish, is the proposal — measured against the spend envelope (Metrics) once real numbers exist. platform team first eval cost measurement in the T1 experiment batching by domain and on a schedule; a full re-run only before publish (Agent Framework § 6.5)
CH-19 Agent Runtime · Challenges Compaction quality — what a summary must keep so that a resumed agent does not re-derive settled facts; measured on the T1 experiment's resumed cases. platform team resumed cases in the T1 experiment Challenge Rounds § CS: compaction quality
CH-21 Agents · 0.6 Auto-learning a missing domain How deep a summarizer goes on first creation, and what triggers a refresh of a node that already exists — a staleness signal, a schedule, or the next case that finds it wrong. platform team first auto-created source/serdica-backend/ node Challenge Rounds § CS: summarizer depth and refresh
CH-22 Contracts · Challenges The drafts have been exercised against the eight Configuration, ten Support and eight Development written cases, not against a running stage. The first real case of each module either confirms a core field or moves it to the open body; the count of fields m… platform architect the first running stage produces and validates a draft instance (T2 slice) the drafts stay x-status: draft until then (D139)
CH-24 Gating · Challenges The first shape catalogue: which write shapes the five largest support families and the five configuration stages need, and how many of them a single template covers. Built on the first ten cases of each module. platform team + module authors the first ten cases of each module D72 - a shape is earned from observed instances, so the catalogue cannot precede the cases
CH-25 Gating · Challenges Whether check 2 can always re-derive the affected set cheaply — for a statement over a large table the re-derivation is a count query, but for a multi-statement block it is a set of them; the budget for the auditor is a per-profile ceiling (Agents § 0.1). write auditor author the first HW-approve on a shape over a large table a count query for the affected set; a sampled re-derivation where the count is not cheap
CH-26 Measurements 2026-09-02 · RE-8 Retrieval mechanics and the two-independent-uses rule — the measurement and the v1 baseline — CH-50, CH-66, CH-69 The two-independent-uses promotion rule still cannot be measured: the corpus has no "use" events (which article an analysis actually relied on, versus merely linked). The held-out set above is the right sample; the missing data is a per-case "relied-on" mar… support author the ledger produces per-case relied-on marks the held-out set of the same page (section TB) is the right sample; the missing datum is which article a case relied on, not which it linked
CH-27 Product Configurator · Q. What the documents leave open, and the wiki already answers The configurator's seven open questions DEC-1 … DEC-7 (Product design § 11): DEC-1 (file output first) is the abacus-only slice in files mode (A-20); DEC-2 (single- or multi-tenant) is the plug-in model; DEC-3 (documents leaving the region) is C-9; DEC-4 an… S2 author the first slice fixes the number of worked examples (DEC-6) DEC-1 to DEC-5 and DEC-7 are answered by the wiki; only DEC-6 is open

D — build item

Id Page · section Challenge Owner Closes when Investigation / proposed solution
CH-23 Data Model · Challenges The scripts have not run: SRD_SUPPORT is not created (DB-7) and the QA backup path must be restored first (D45/D131). Closed by the first acceptance-install-clean.sql run on QA, whose output is pasted here. Vladimir + Bulstrad DBA SRD_SUPPORT created on QA after the backup path is restored (D45, D47, D131) install-clean and the acceptance scripts are the entry points; lint_ddl.py passes offline
PreviousRequirements Register (appendix)NextGlossary