Incomex AI Portal
KB-36A0

Law Merge Survey Packet — Old Law Corpus vs F0→F5/FX New Model (read-only, non-authorizing)

12 min read Revision 1
laws-newnewlawslaw-mergesurvey-packetcatalog-onlyread-onlynon-authorizingkeep-amend-rewrite-defer2026-06-16

Law Merge Survey Packet — Old Law Corpus vs F0→F5/FX New Model

Companion documents (this newlaws/ workspace only): law-merge-catalog-2026-06-16.md (the main catalog) · law-merge-execution-report-2026-06-16.md (the execution report). Survey run date: 2026-06-17. Deliverable cohort dated 2026-06-16 to align with the completed F0→F5/FX survey cohort.

1. Status / Non-authorization banner

STATUS: READ-ONLY · NON-AUTHORIZING · CATALOG-ONLY.

This packet defines the method for the Law Merge Survey — a documentary comparison of the existing/enacted/draft law corpus (knowledge/dev/laws/) against the completed F0→F5/FX model (knowledge/dev/laws-new/), producing a Law Merge Catalog that classifies every law as KEEP / KEEP+NOTE / AMEND / REWRITE / DEFER.

This is a survey/catalog task only. It does not:

  • amend, rewrite, re-enact, supersede, move, rename or delete any law;
  • write any amendment draft, rewrite draft, compatibility note, technical design, or implementation prompt;
  • query live DB / runtime, run Phase-1, touch production, or change any schema/registry/table/index;
  • resolve any held blocker (CONS-002/003, CELL-003/004/007, HOLD-1/HOLD-2, RISK-*); or
  • change the authority order decided at F0 (CONS-004).

A PASS on this survey means only that the Law Merge Catalog is complete enough for GPT / Codex / Owner review. It authorizes nothing. Engineering PASS ≠ Authority PASS; Codex/Council PASS ≠ Owner phase-authorization.

2. Folder policy (critical — three distinct branches)

Branch Meaning Rule in this macro
knowledge/dev/laws/ Old / existing / enacted / draft law corpus (the legal foundation) READ-ONLY. Do not edit / move / rename / delete / create files. No laws/newlaws/.
knowledge/dev/laws-new/ The F0–F5/FX survey branch READ-ONLY. No new files in its root or in laws-new/laws/.
knowledge/dev/laws-new/newlaws/ The Law Merge workspace ("New Laws") OUTPUTS ONLY. Exactly three files (this packet + catalog + report).

Allowed outputs (and only these):

  • knowledge/dev/laws-new/newlaws/law-merge-survey-packet.md
  • knowledge/dev/laws-new/newlaws/law-merge-catalog-2026-06-16.md
  • knowledge/dev/laws-new/newlaws/law-merge-execution-report-2026-06-16.md

No subfolders (reports/, amendments/, rewrites/, notes/) are created in this round.

3. Core philosophy

Treat the old legal system as the legal foundation, not as something to discard.

  • Existing laws = goals, authority, accumulated legal foundation.
  • F0→F5/FX = the new implementation / rollout / compatibility method (the Lego / DOT / stamp / checker / scanner model under the constitution).
  • laws-new/newlaws/ = the workspace for survey/catalog and (later, only if Owner authorizes) drafting — not a replacement corpus.

General rule:

  • Preserve goals unless the goal itself is obsolete or conflicting.
  • Change rollout/mechanism only when an old implementation assumption conflicts with the new Lego/DOT/stamp/checker/scanner model.
  • Do not rewrite a law just because its wording is old.
  • Do not copy the old law corpus into laws-new/newlaws/.

4. Scope and non-scope

In scope: read/list/search the KB; read the completed F0→F5/FX documents and the old law corpus; classify each law; record blockers and missing laws; produce exactly the three output documents.

Out of scope (forbidden): every item in §1 plus — declaring laws superseded; deleting/moving old laws; editing knowledge/dev/laws/; creating knowledge/dev/laws/newlaws/ or knowledge/dev/laws-new/laws/; writing outputs to the laws-new/ root; renaming laws/ or laws-new/.

5. Owner-facing 3 questions (preserved in every output)

  1. Luật nào đang có và dùng lại được? (Which existing laws are reusable as-is?) → KEEP (+ the as-is half of KEEP+NOTE).
  2. Luật nào đang có nhưng cần ghi chú / kiểm chứng / amendment / rewrite mới dùng lại được? (Which need a note / verification / amendment / rewrite first?) → KEEP+NOTE / AMEND / REWRITE.
  3. Luật nào thật sự phải viết mới hoặc viết lại trước technical design? (Which must be (re)written before technical design?) → REWRITE (+ the highest-priority AMEND), and the NOT_FOUND / standalone-absent items.

6. Source discovery plan

Mandatory new-model reading first (the lens — knowledge/dev/laws-new/…): F0–F5 + FX owner-decision records; F4 + F5 execution reports; FX packet + FX execution report; F0→F5 Cross-F Evidence & Readiness Matrix; technical-slice-framework.md; de-bai-cai-tien.md; cau-hoi-khi-tai-cau-truc.md.

Authority / operating sources: knowledge/dev/laws/constitution.md; knowledge/dev/ssot/operating-rules.md; the enacted Điều 32 / 33 / 35 / 37 / 38 / 39 law files.

Old law corpus discovery under knowledge/dev/laws/ — at minimum: the Constitution; the terminology glossary; the foundation law-NN-*.md family (Điều 0-H, 1–19, 22, 24); the dieu* law files (20, 26, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 41, 43, 44); the Điều 38 Text-as-Code family (incl. LSL-01, L4); and the implementation subtrees (dieu28/38/43/44-trien-khai/, dieu43-migrations/, dieu41-revision-rulings/). Embedded-only articles (Điều 0 / 0-B / 0-G / 0-S / 0-M / 0-L) are read from the Constitution. Implementation reports are not read individually unless a law-level decision needs them. If a law number is not found as a standalone document, record NOT_FOUND_IN_PASS; do not invent it.

7. Classification rules

Use exactly these five labels:

  • KEEP — goals AND rollout compatible enough with F0→F5/FX; no amendment needed before technical design; safe to keep reading from laws/.
  • KEEP+NOTE — goal valid and mostly compatible, but a short compatibility note (in laws-new, later, Owner-gated) should clarify how F0→F5/FX interprets it. Do not rewrite the law.
  • AMEND — goal valid, but specific clauses/definitions/rollout assumptions must be amended before technical design.
  • REWRITE — structure or authority model conflicts deeply with F0→F5/FX; rewrite later in laws-new/newlaws/ before technical design.
  • DEFER — implementation-specific, obsolete, superseded, too deep for this phase, or not needed before technical design.

Per-law audit questions (folded into each catalog record): (1) original goal; (2) goal still valid under F0→F5/FX?; (3) assumes old architecture / big-bang rollout?; (4) conflicts with Lego/DOT/stamp/checker/scanner?; (5) conflicts with "governance = relationship/state/classification info"?; (6) conflicts with "scanner list-only, no auto-fix"?; (7) conflicts with "birth minimal; canonical birth at promote"?; (8) conflicts with "Owner gate / Mức 3 / Engineering PASS ≠ Authority PASS"?; (9) depends on unproven live DB/runtime evidence?; (10) classification; (11) minimal next action.

Conservatism rule: if uncertain, choose the more conservative classification and explain (e.g. structural + authority conflict → REWRITE over AMEND; superseded/implementation-only → DEFER).

8. Mandatory special sections

The catalog/report must include dedicated treatments of:

  • Constitution — stays supreme? compatibility note? which principles support F0→F5/FX? which clauses may need future amendment (flag only)?
  • Điều 37 (Governance Organization) — why REWRITE/major-AMEND; old governance org vs FX Governance One Roof; goals to preserve; mechanisms to replace; future-rewrite checklist (do not write the rewrite).
  • Điều 39 (Knowledge Graph) — preserve goals? change rollout? compatibility/reinterpretation note needed? registered/spec'd vs executed/live DOT-KG; how it combines with F0→F5 (do not write the note).
  • Điều 38 (Text as Code) — IU/Smart Brick vs F2/F3; compatible parts; parts needing amendment for candidate-packet/staging/promote/canonical-birth.
  • Điều 35 (DOT Governance v5.2) — DOT-as-narrow-info-completion alignment; reusable repair-governance loop; live caveats (production-readiness fail, authority bypass); note vs amendment.
  • Birth / Điều 0-G — minimal TEMP_ID / candidate identity match? implies canonical birth too early? needs amendment for BIRTH_STAMP at promote?

9. Evidence obligations

Every record carries, at minimum: source path; revision; authority status (enacted / draft / deprecated / backup / superseded / appendix / process / implementation); short goal; goal-still-valid; relation to F0→F5/FX; goal compatibility; rollout compatibility; runtime impact; conflict type; evidence status; whether live proof exists (it does not — see below); recommended classification; recommended next action; safety lock.

Live-proof discipline (uniform): this survey ran no live DB / runtime / Phase-1 query. Per technical-slice-framework rev56 §4, all reported-LIVE substrate is downgraded to DOCUMENTARY_ONLY. Therefore liveProof = No (or Unknown / N/A) for every record; row counts, "DONE/HOÀN TẤT/LIVE" claims, and trigger/function existence are documentary, not proof.

10. Internal gate (run only if all GREEN)

Gate Requirement
G1 F0→F5/FX evidence readable
G2 Constitution + operating-rules readable
G3 law corpus discoverable
G4 classification labels defined and used consistently
G5 no amendment / rewrite / design / implementation produced
G6 no live DB / runtime / Phase-1
G7 Owner 3 questions preserved
G8 special sections covered
G9 folder policy preserved (laws/ untouched; outputs only under laws-new/newlaws/)

Any RED → stop and report PARTIAL / BLOCKED.

11. Expected catalog / report format

Catalog (law-merge-catalog-2026-06-16.md) — the main table (columns: Law/Document · Current path · Revision · Authority status · Short goal · Goal still valid? · F0→F5/FX impact · Conflict type · Classification · Recommended action · Priority · Must happen before technical design? · Notes) plus summary tables (count by classification; high-priority-before-technical-design; safe-to-keep-reading; require-future-newlaws-note/amend/rewrite; deferred docs; missing/not-found).

Execution report (law-merge-execution-report-2026-06-16.md) — status/boundary; folder-policy confirmation; sources discovered/read; Owner 3-question answers; method + internal-gate result; catalog summary; the six special sections; the five classification lists (KEEP / KEEP+NOTE / AMEND / REWRITE / DEFER); missing/not-found list; conflict/HOLD log; recommendation for next macros; non-authorization confirmation.

12. Stop conditions

Stop and report PARTIAL/BLOCKED if: the new-model docs or the Constitution/operating-rules cannot be read; the classification cannot be produced honestly without resolving a held blocker; or any action would require a forbidden mutation (amend/rewrite/design/implementation/live-query/schema-change/authority-change/edit-of-laws/). When a law cannot be fully adjudicated (e.g. an operative clause lives in an unread file), record the gap explicitly rather than guessing.

13. Meaning of PASS

A PASS means only that the Law Merge Catalog is complete enough for GPT / Codex / Owner review. It does not authorize law amendments, law rewrites, technical design, Phase-1, implementation, or authority changes.

Next action after PASS: GPT reviews the catalog → Codex reviews the catalog → Owner decides which laws move to note / amend / rewrite batches.