KB-50DC

tool-kiem-thu — Central Folder README (Implementation Package DOT initiative)

3 min read Revision 1
tool-kiem-thureadmecentral-folderimplementation-package-dotindex2026-06-09

tool-kiem-thu — Central Folder

Purpose: the single human-readable home for the testing / implementation-package verification initiative ("Implementation Package DOT"). Everything related to this tooling work lives here so the User has one folder to review. Created: 2026-06-09 · Status: planning · Production mutation: none.

What this initiative is

A reusable, machine-checkable verifier family that checks implementation packages / construction dossiers before dry-run, Codex review, or production execution — so that the FIX7-class failure (prose claims an executable that does not actually run) is caught by a machine, not by a wasted review round.

It is built Assembly-First on top of existing foundations and creates no parallel authority:

  • Đ38 Text-as-Code — packages are Text-as-Code artifacts (consumed).
  • Điều 23 DOT Scanning — the verifier is a DOT; "Không có DOT = không deploy"; findings → system_issues (consumed + registered into).
  • Đ43 Context Pack — active context / SSOT resolution (consumed).
  • P11E checker-proofchecker_run_status readiness contract (reused verbatim).
  • dot-iu-cutter dryrun.py — the runnable, fail-closed Python verifier template.

Authority stays in the approved laws/designs/profiles. Tools only execute and report.

Folder structure (mandatory — keep everything here)

knowledge/dev/laws/tool-kiem-thu/
  README.md          ← this file
  00-index.md        ← index of all docs in this folder
  planning/          ← plans (feasibility plan lives here)
  designs/           ← specs / schemas / verifier design (Phase 2+)
  reviews/           ← GPT / Codex reviews
  reports/           ← run reports / verdicts / evidence
  checkpoints/       ← session checkpoints
  references/        ← pointers to consumed foundations (Đ23/Đ38/Đ43/P6/P11E/P9-G6)

In the KB, folders materialize when a document is written under their path. planning/ and checkpoints/ are populated; the others are reserved and will fill as the work proceeds.

Current contents

  • planning/implementation-package-dot-v0-1-feasibility-plan-2026-06-09.mdthe plan (PLAN_DRAFT_READY).
  • checkpoints/checkpoint-implementation-package-dot-v0-1-feasibility-plan-2026-06-09.md — session checkpoint.

Status

PLAN_DRAFT_READY — awaiting review by User / GPT / Codex / T1. No implementation, no install, no production mutation, no law authored, no FIX7 recheck resumed.