---
name: iso19650-naming-check
description: Check file and information container names against the project's ISO 19650-style naming standard (field order, delimiter, code lists such as project, originator, volume/system, level/location, type, role, number) plus status and revision codes in the register; report what fails and propose corrected names. Use when the user audits a common data environment (CDE) folder, a drawing register or a model exchange, mentions ISO 19650, "nomenclatura de archivos", "codificación de planos", information standard, file naming convention, or before a milestone delivery.
---

# Information container naming check

## Inputs
- The names: a folder export, the document register (CSV/Excel with name, status, revision) or a list pasted by the user.
- The project's information standard or BEP section with the field order and the code lists. ISO 19650-2 requires a project naming convention but the codes are the project's (the UK National Annex gives a widely used field order). Without the project's codes the check is only structural.

## Procedure
1. Get the standard: transcribe the fields, patterns and code lists into `standard.json` (see the script header). Ask for missing code lists rather than inventing them.
2. Run `python scripts/naming_check.py names.txt --standard standard.json`, or for a register `python scripts/naming_check.py register.csv --column "File name" --status-col Status --revision-col Revision --standard standard.json`, or `--folder <path>`.
3. Read the failures by field: usually one originator or one field causes most errors - a conversation with that team fixes more than renaming files one by one.
4. Propose corrected names only when the right value is unambiguous (e.g. level "1" -> "01"); otherwise list the question for the author.
5. Check the metadata too: status codes (S0-S7 work in progress/shared, A/B published, CR as-built per the UK annex, or the project's own) and revision format (P01.01 preliminary, C01 contractual, or the project's own).
6. Give each originator their list of names to fix.

## Output
- `naming.md` (summary, failures by field, names to fix), `naming.csv`, proposed corrections, messages per originator.

## Never
- Never rename files in the CDE yourself; propose, the information manager approves.
- Never treat the example layout as the project standard.
- Never invent a code that is not in the project's code list.