RS-TKT-1-PATCH1C · 04 — Single Artifact Contract and Schema Supersession

NON_EXECUTABLE_DESIGN_DOC
DOT_BOUND_DRYRUN_READINESS_PROOF_ONLY
NOT_IMPLEMENTED
NOT_AUTHORIZED_FOR_RUNTIME

Lane: RS-TKT-1 — Phase 1 TKT Base · PATCH1C Date: 2026-06-22 Gate: REGISTRATION_HOLD · REGISTRATION_CAN_PROCEED = NO · 0 runtime mutations Authority: NON_AUTHORITY · may_gate=false · decision_effect=NONE Closes: Codex PATCH1B-DRYRUN-ARTIFACT-CARDINALITY-AMBIGUOUS (§14).

Exactly one artifact model is chosen. The JSON and Markdown shapes are not two files — they are two sections of one file.

---

1. The one chosen artifact model

artifact_model            = SINGLE_KB_MARKDOWN_REPORT
artifact_count            = 1
artifact_cardinality_ambiguous = 0
allowed_report_path       = knowledge/current-state/reports/tool-kiem-thu-lego/phase2-dryrun/rs-tkt-2-dryrun-read-report-inspector-YYYY-MM-DD.md
write_channel             = KB write (upload_document) under the allowed output prefix — the handbook §12 ALLOWED channel; NOT the DOT-only schema zone

2. The single report's required sections (all inside ONE markdown file)

1. metadata block            : lane, date, bound DOT code, mode, gate, authority/registration effect = NONE
2. machine-readable section  : exactly ONE fenced ```json block carrying the Phase-1 13 result schema (tkt_base_result{...}), EMBEDDED — not a separate result.json
3. human-readable summary    : the Phase-1 13 result.md shape, rendered as a markdown SECTION — not a separate result.md
4. per-fixture result table  : fixture_id · expected_check_status · observed(paper) · canonical_outcome_code  (oracle from patch1b 01/02)
5. aggregate stop-state table: aggregate_status (FAIL>HOLD>PASS) · review_readiness · stop_state
6. DOT binding table         : bound DOT code/mode/channel; authority_effect=NONE; registration_effect=NONE
7. non-authority disclaimer  : aggregate=PASS implies nothing about authority/registration/runtime/production

3. Cardinality rule (deterministic)

EXACTLY ONE persisted KB artifact per dry-run run. No result.json file. No result.md file. No multi-file output folder.
If a future implementation needs internal JSON, it MUST be transient (in-memory) or EMBEDDED in section 2 of the single report — NEVER a second persisted KB artifact.

4. Supersession map (additive — old files unchanged)

superseded clause	old text (paraphrase)	superseded by
Phase-1 13 §§1,2,5	"future result.json" + "future result.md" as two shapes/files; "an AUTHORIZED output folder ... and a KB summary"	§2 here: both shapes become sections of one markdown report; one file, one folder, one artifact
patch1b/05 §2	future_report_schema: phase1-design/13 (result.json / result.md ...)	§1/§2 here: SINGLE_KB_MARKDOWN_REPORT; schema embedded
patch1b/05 §6	"ONE result report ... result.json/result.md per schema 13. No other artifact."	reconciled: ONE report; the "result.json/result.md per schema 13" is the embedded JSON section + human section, not separate files
patch1b/05 §9 DR-5	"allowed OUTPUT KB path for result.json/md"	DR-5 output path retained; representation fixed to the single embedded-section report
Phase-1 21 §1	"An allowed OUTPUT folder is named (where result.json/result.md are written)"	output folder retained; artifact = one markdown report (JSON/MD embedded)

Method: ADDITIVE supersession. Files 13 / 05 / 21 are UNCHANGED (revision 1). The single-artifact contract governs from PATCH1C onward (recorded here + in 08).

5. Counts proven here (counted in 07)

artifact_models_count            = 1
artifact_cardinality_ambiguous   = 0
separate_result_json_required    = 0
separate_result_md_required      = 0