B.M.12 — METHODOLOGY v27 VALIDATION: CZECH FILE ALIASES / CO...

Prompt

B.M.12 — METHODOLOGY v27 VALIDATION: CZECH FILE ALIASES / CONSOLIDATED CHANGE-CONTROL MANIFEST ROLE Independent auditor of the current long-term LMC methodology as the autonomous development/evaluation control plane. Audit only the exact v27 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.M.12 TXT; (2) exact v27 methodology DOCX; (3) exact v27 Změny DOCX; (4) exact current production prompt; (5) exact Frozen baseline; (6) prior release/acceptance rules; (7) expected-next-prompt inventory; (8) exact A 12 and B 12 TXT artifacts; (9) bundle identity. Missing item => BLOCKED. Never reconstruct. AUDIT OBJECTIVE Verify that v27 implements the requested convention: A x, B x, Metodika x, Změny x as short Czech aliases, while all canonical filenames remain identity-bound. Verify that the former standalone release manifest is consolidated into Změny x by default and that a separate manifest remains an explicit exception only when downstream processing materially benefits from it. TEST GROUPS TG1-TG10 TG1 Alias semantics and deterministic alias↔canonical mapping. TG2 Consolidation of Change-Control/Iteration-State + manifest data into one authoritative Změny x companion. TG3 Manifest completeness, machine-readable block, hashes, versions, parents and lifecycle fields. TG4 H195 separation exception: separate manifest only with explicit decision, reason, identity and cross-reference. TG5 Interaction with H187-H192 / automatic next-prompt attachment and H242-H250 exact-payload distribution. TG6 Human-readable naming versus machine-processing robustness and portability. TG7 Historical provenance: v26 standalone manifest remains historical evidence but is not silently treated as v27 required artifact. TG8 Fresh-thread handoff: Metodika x + Změny x + production prompt + Frozen baseline + expected A/B exact artifacts are sufficient without hidden conversational reconstruction. TG9 Internal validation coverage: every new material rule/process step mapped to IVR. TG10 Interaction with baseline protection, acceptance precedence, no-Web boundary, bounded recovery and post-release lifecycle. MANDATORY ADVERSARIAL SCENARIOS 1. All four aliases resolve uniquely. 2. Alias points to wrong canonical filename. 3. Změny x contains incomplete artifact inventory. 4. Separate manifest appears without H195 decision. 5. Machine-readable manifest block conflicts with narrative value. 6. A/B artifact exists but alias is missing from Změny x. 7. A/B alias exists but actual attachment is missing. 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 v27 H-rules — no reconstruction. 10. Competitor mechanism proposal requires Web Search — reject/reformulate web-free. DISCOVERY At most 3 new hypotheses. Novelty against v27 must be checked before admission. No candidate is promoted merely because consolidation or aliases 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 / alias 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 Změny x is the default authoritative human-readable identity/provenance companion from v27 onward. A separate manifest may exist only under H195 and must never become an implicit second source of truth. FINAL STOP RULE Incomplete bundle => do not issue content PASS/FAIL; do not reconstruct v27; do not treat a missing standalone manifest as a defect because v27 does not require one by default.