All workflows in this folder follow the same validation/release discipline established in AUTHORIZED_REPAIR_WORKFLOW.md (intake → acquisition → development → validation → release). That file remains the generic, module-agnostic baseline. The module/operation-specific workflows below add prerequisites, adapters, wiring, safety notes, common failures, and recovery procedures particular to that operation type.

Workflow	File
Generic validation and release (baseline)	AUTHORIZED_REPAIR_WORKFLOW.md
EEPROM Read/Write	EEPROM_READ_WRITE_WORKFLOW.md
MCU Read/Write	MCU_READ_WRITE_WORKFLOW.md
ECU Clone / TCU Clone	ECU_TCU_CLONE_WORKFLOW.md
VIN Migration	VIN_MIGRATION_WORKFLOW.md
ISN Operations	ISN_OPERATIONS_WORKFLOW.md
Bench Reading / Boot Reading	BENCH_AND_BOOT_READING_WORKFLOW.md
Immobilizer Backup / Restore	IMMOBILIZER_BACKUP_RESTORE_WORKFLOW.md
Authorized Key Learning	AUTHORIZED_KEY_LEARNING_WORKFLOW.md

Scope and evidence note

These workflows separate the following acquisition paths clearly:

CAN communication analysis
Module-level bench mode
Direct MCU debug or programming interface
External EEPROM access
File and memory reconstruction

The repository's memory concepts page captures the terminology normalization and includes the Ducati Monster 696 S12X case study as CASE-STUDY-SPECIFIC material. That case study is not a generic Multi-PROG workflow and is not to be treated as an official procedure for all S12X families.

Scope note

These workflows are procedural and adapter-agnostic. They describe what to verify and record, not exact security algorithms, real memory offsets, or bypass techniques — that boundary is intentional (see CONTRIBUTING.md and 07_Authorized_Key_Immobilizer_Work/README.md). Real, platform-specific security data belongs only in the governance-boundaried 07_Authorized_Key_Immobilizer_Work/ scope, never in this general-purpose folder.