B.M.13 — METHODOLOGY v28 VALIDATION: USER-ISSUED SHORT FILEN...

Prompt

B.M.13 — METHODOLOGY v28 VALIDATION: USER-ISSUED SHORT FILENAMES / RELEASE IDENTITY ROLE Independent auditor of the current long-term LMC methodology as the autonomous development/evaluation control plane. Audit only the exact v28 methodology bundle supplied with this prompt. WEB SEARCH Competitor models are NO-WEB by design. Never require or recommend competitor Web Search. Central Web Search may be used only by the controller/auditor for methodological calibration if actually available. HARD INTAKE Required atomic bundle: (1) exact B 13.txt; (2) exact v28 Metodika 28.docx; (3) exact v28 Změny 28.docx; (4) exact current production prompt; (5) exact Frozen baseline; (6) prior release/acceptance rules; (7) expected-next-prompt inventory; (8) exact A 13.txt and B 13.txt artifacts; (9) bundle identity. Missing item => BLOCKED. Never reconstruct. AUDIT OBJECTIVE Verify that v28 makes the shortened Czech labels the actual user-issued filenames: Metodika 28.docx Změny 28.docx A 13.txt B 13.txt Verify that Změny x records these exact delivered basenames in its deterministic identity block. Verify that long technical filenames from prior releases can remain only as historical/source-lineage references and are never silently issued as current user-facing filenames. Verify that this change does not weaken hash, version, parent, lifecycle, attachment or fresh-thread identity controls. TEST GROUPS TG1-TG10 TG1 Actual user-issued filename semantics: short Czech filename is the delivered file basename. TG2 One-to-one filename/alias identity and rejection of competing current names. TG3 Deterministic manifest identity block uses actual delivered filename, not a narrative alias. TG4 Legacy long filename separation: historical/source-lineage field only. TG5 Interaction with H187-H192 and H242-H250 exact-payload distribution and attachment verification. TG6 Human readability versus machine-processing determinism. TG7 Fresh-thread handoff: short filenames plus exact hashes are sufficient for deterministic identity. TG8 Historical provenance: v26/v27 long names remain historical evidence and do not become current issued names. TG9 Internal validation: every material naming rule maps to IVR; negative controls included. TG10 Interaction with baseline protection, acceptance precedence, no-Web boundary, bounded recovery and post-release lifecycle. MANDATORY ADVERSARIAL SCENARIOS 1. Metodika 28.docx is recorded as the actual issued filename. 2. Změny 28.docx manifest line uses a long legacy filename instead of the delivered short filename. 3. Two artifacts are assigned the same short filename. 4. One artifact has both a short issued filename and a different current issued filename. 5. Long legacy filename remains only in source-lineage/history field. 6. Manifest name and delivered basename differ while hash is otherwise correct. 7. A 13/B 13 are referenced by short names but one actual attachment is absent. 8. 8/10 or 9/10 panel execution — report actual coverage, no automatic rerun solely for n<10. 9. Target absent but audit prompt contains detailed v28 H-rules — no reconstruction. 10. Competitor mechanism proposal requires Web Search — reject/reformulate web-free. DISCOVERY At most 3 new hypotheses. Novelty against v28 must be checked before admission. No candidate is promoted merely because short filenames seem convenient. IVR / RELEASE Every material methodology/process change maps to an IVR before promotion. Self-test PASS is not independent acceptance. Production prompt remains unchanged unless a separate A.P. change record authorizes it. OUTPUT — SINGLE PASS 1. Executive verdict. 2. Intake / identity / actual user-issued filename map. 3. Web capability and calibration. 4. TG1-TG10 results. 5. Mandatory adversarial scenarios. 6. Findings and root causes. 7. Discovery hypotheses. 8. IVR coverage. 9. Independent validation. 10. Convergence/budget. 11. Release/post-release impact. 12. Exact next action. 13. Minimal patch / no-op. CRITICAL DISTINCTION The current user-issued filename is the actual delivered basename of the current artifact. "A 13", "B 13", "Metodika 28", and "Změny 28" are shorthand labels embedded directly in the filenames. They are not merely conversational aliases. Long legacy names may be retained only as explicit historical/source-lineage metadata.