hara-stage3b

Stage 3B SEC ratings are generated by transforming Stage 3A scenarios into isolated S/E/C/FTTI batch files and merging them into a contract-compliant sec.json. This process enforces isolation of S/E/C/FTTI responsibilities while keeping Stage 3A content unchanged.

The JSON output contract for SEC ratings requires producing an output sec.json file with only permitted top-level keys and scenario-aligned sec_records. It enforces deterministic merging and structural validation against Stage3A alignment requirements.

Batch orchestration isolates S/E/C/FTTI responsibilities in safety ASIL workflows by splitting them into separate batch workers. Each sub-task only reads its allowed knowledge base, ensuring strict separation before merging into the final SEC rating output.

Yes, you need Stage 3A scenarios as input before generating SEC rating batch files. The Stage 3B pipeline transforms existing Stage 3A scenarios into S/E/C/FTTI batches, enforces alignment requirements, and ensures Stage 3A content remains unchanged.

Deterministic merging for derived ASIL fields is limited to scenario-based safety engineering workflows where only SEC incremental outputs are needed. It strictly enforces structural validation against Stage3A alignment requirements and does not modify original Stage 3A content.