diff --git a/interviews/vault-cli/check_results_absolute_final.json b/interviews/vault-cli/check_results_absolute_final.json deleted file mode 100644 index f2197b2b3..000000000 --- a/interviews/vault-cli/check_results_absolute_final.json +++ /dev/null @@ -1 +0,0 @@ -{"ok": false, "exit_code": 1, "exit_symbol": "VALIDATION_FAILURE", "command": "vault check", "data": {"loaded": 10700, "load_errors": 1, "invariant_failures": 59}, "errors": [{"uri": "../vault/questions/edge/edge-0162.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "schema validation failed: 1 validation error for Question\ndetails.options.1\n Input should be a valid string [type=string_type, input_value={'~0.0007 Bytes/Op (Inver...'Bandwidth / Compute).'}, input_type=dict]\n For further information visit https://errors.pydantic.dev/2.13/v/string_type"}, {"uri": "", "severity": 1, "code": "chain-position-duplicate", "source": "vault-check-structural", "message": "chain 'cloud-chain-467' has duplicate positions among [0, 1, 0]"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-305' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-018' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-036' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-043' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-065' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-085' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-086' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-097' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-116' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-123' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-160' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-232' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-242' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-251' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-258' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-263' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-282' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-288' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-302' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-394' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-469' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-187' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-193' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-081' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-142' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-003' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-085' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-095' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-110' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-056' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-052' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-001' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-002' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-018' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-029' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-012' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-002' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-036' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-020' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-048' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-030' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-039' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-040' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-046' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-052' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-022' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-005' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-027' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-110' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-099' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-055' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-105' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-051' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-056' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-066' has only 1 member(s); min 2"}]} diff --git a/interviews/vault-cli/check_results_after_repair.json b/interviews/vault-cli/check_results_after_repair.json deleted file mode 100644 index 09077d57e..000000000 --- a/interviews/vault-cli/check_results_after_repair.json +++ /dev/null @@ -1 +0,0 @@ -{"ok": false, "exit_code": 1, "exit_symbol": "VALIDATION_FAILURE", "command": "vault check", "data": {"loaded": 10638, "load_errors": 63, "invariant_failures": 64}, "errors": [{"uri": "../vault/questions/cloud/cloud-0360.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 492"}, {"uri": "../vault/questions/cloud/cloud-0455.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 12, column 88"}, {"uri": "../vault/questions/cloud/cloud-0469.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "schema validation failed: 1 validation error for Question\nzone\n Value error, invalid zone 'tradeoff-analysis'; must be one of ['analyze', 'design', 'diagnosis', 'evaluation', 'fluency', 'implement', 'mastery', 'optimization', 'realization', 'recall', 'specification'] [type=value_error, input_value='tradeoff-analysis', input_type=str]\n For further information visit https://errors.pydantic.dev/2.13/v/value_error"}, {"uri": "../vault/questions/cloud/cloud-0654.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 389"}, {"uri": "../vault/questions/cloud/cloud-0733.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 252"}, {"uri": "../vault/questions/cloud/cloud-0777.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 263"}, {"uri": "../vault/questions/cloud/cloud-0798.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 559"}, {"uri": "../vault/questions/cloud/cloud-2178.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 138"}, {"uri": "../vault/questions/cloud/cloud-2394.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "schema validation failed: 1 validation error for Question\nhuman_reviewed.status\n Value error, invalid human_reviewed.status 'reviewed', must be one of ['flagged', 'needs-rework', 'not-reviewed', 'verified'] [type=value_error, input_value='reviewed', input_type=str]\n For further information visit https://errors.pydantic.dev/2.13/v/value_error"}, {"uri": "../vault/questions/cloud/cloud-2530.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 50"}, {"uri": "../vault/questions/cloud/cloud-2777.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 40"}, {"uri": "../vault/questions/cloud/cloud-3985.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "schema validation failed: 1 validation error for Question\nhuman_reviewed.status\n Value error, invalid human_reviewed.status 'reviewed', must be one of ['flagged', 'needs-rework', 'not-reviewed', 'verified'] [type=value_error, input_value='reviewed', input_type=str]\n For further information visit https://errors.pydantic.dev/2.13/v/value_error"}, {"uri": "../vault/questions/cloud/cloud-4093.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 10, column 17"}, {"uri": "../vault/questions/cloud/cloud-4286.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 10, column 32"}, {"uri": "../vault/questions/cloud/cloud-4299.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: while scanning a double-quoted scalar\n in \"\", line 14, column 23\nfound unknown escape character 'g'\n in \"\", line 14, column 234"}, {"uri": "../vault/questions/cloud/cloud-4451.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 10, column 43"}, {"uri": "../vault/questions/cloud/cloud-4539.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "schema validation failed: 1 validation error for Question\nhuman_reviewed.status\n Value error, invalid human_reviewed.status 'reviewed', must be one of ['flagged', 'needs-rework', 'not-reviewed', 'verified'] [type=value_error, input_value='reviewed', input_type=str]\n For further information visit https://errors.pydantic.dev/2.13/v/value_error"}, {"uri": "../vault/questions/edge/edge-0005.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 12, column 65"}, {"uri": "../vault/questions/edge/edge-0022.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 123"}, {"uri": "../vault/questions/edge/edge-0100.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 236"}, {"uri": "../vault/questions/edge/edge-0114.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 223"}, {"uri": "../vault/questions/edge/edge-0119.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 206"}, {"uri": "../vault/questions/edge/edge-0154.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "schema validation failed: 1 validation error for Question\n Value error, zone='analyze' and bloom_level='understand' are incompatible (zone='analyze' admits ['analyze', 'apply']). Run reclassify_zone_bloom_mismatch.py to repair, or correct one of the two fields manually. [type=value_error, input_value={'schema_version': '1.0',...': None, 'notes': None}}, input_type=dict]\n For further information visit https://errors.pydantic.dev/2.13/v/value_error"}, {"uri": "../vault/questions/edge/edge-0162.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: while parsing a block mapping\n in \"\", line 14, column 3\nexpected , but found ''\n in \"\", line 14, column 230"}, {"uri": "../vault/questions/edge/edge-0168.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 12, column 86"}, {"uri": "../vault/questions/edge/edge-0189.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 159"}, {"uri": "../vault/questions/edge/edge-0335.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 140"}, {"uri": "../vault/questions/edge/edge-0380.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 10, column 47"}, {"uri": "../vault/questions/edge/edge-0477.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: while parsing a block mapping\n in \"\", line 14, column 3\nexpected , but found ''\n in \"\", line 14, column 82"}, {"uri": "../vault/questions/edge/edge-1102.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "schema validation failed: 1 validation error for Question\n Value error, zone='evaluation' and bloom_level='create' are incompatible (zone='evaluation' admits ['analyze', 'evaluate']). Run reclassify_zone_bloom_mismatch.py to repair, or correct one of the two fields manually. [type=value_error, input_value={'schema_version': '1.0',...': None, 'notes': None}}, input_type=dict]\n For further information visit https://errors.pydantic.dev/2.13/v/value_error"}, {"uri": "../vault/questions/mobile/mobile-0250.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 10, column 32"}, {"uri": "../vault/questions/tinyml/tinyml-0616.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: while scanning for the next token\nfound character '`' that cannot start any token\n in \"\", line 34, column 5"}, {"uri": "../vault/questions/tinyml/tinyml-0699.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: while scanning a double-quoted scalar\n in \"\", line 14, column 23\nfound unknown escape character ','\n in \"\", line 14, column 523"}, {"uri": "../vault/questions/tinyml/tinyml-0904.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 209"}, {"uri": "../vault/questions/tinyml/tinyml-0907.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 53"}, {"uri": "../vault/questions/tinyml/tinyml-0911.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 109"}, {"uri": "../vault/questions/tinyml/tinyml-0912.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 127"}, {"uri": "../vault/questions/tinyml/tinyml-0913.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 91"}, {"uri": "../vault/questions/tinyml/tinyml-0920.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 132"}, {"uri": "../vault/questions/tinyml/tinyml-0928.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 237"}, {"uri": "../vault/questions/tinyml/tinyml-0940.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 199"}, {"uri": "../vault/questions/tinyml/tinyml-0942.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 259"}, {"uri": "../vault/questions/tinyml/tinyml-0945.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 119"}, {"uri": "../vault/questions/tinyml/tinyml-0961.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 122"}, {"uri": "../vault/questions/tinyml/tinyml-1018.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 12, column 71"}, {"uri": "../vault/questions/tinyml/tinyml-1022.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 366"}, {"uri": "../vault/questions/tinyml/tinyml-1024.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 194"}, {"uri": "../vault/questions/tinyml/tinyml-1028.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 340"}, {"uri": "../vault/questions/tinyml/tinyml-1032.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 216"}, {"uri": "../vault/questions/tinyml/tinyml-1124.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 351"}, {"uri": "../vault/questions/tinyml/tinyml-1125.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 391"}, {"uri": "../vault/questions/tinyml/tinyml-1127.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 221"}, {"uri": "../vault/questions/tinyml/tinyml-1133.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 324"}, {"uri": "../vault/questions/tinyml/tinyml-1136.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 194"}, {"uri": "../vault/questions/tinyml/tinyml-1138.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 331"}, {"uri": "../vault/questions/tinyml/tinyml-1143.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 370"}, {"uri": "../vault/questions/tinyml/tinyml-1161.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 203"}, {"uri": "../vault/questions/tinyml/tinyml-1291.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 195"}, {"uri": "../vault/questions/tinyml/tinyml-1330.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 305"}, {"uri": "../vault/questions/tinyml/tinyml-1339.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 71"}, {"uri": "../vault/questions/tinyml/tinyml-1344.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 150"}, {"uri": "../vault/questions/tinyml/tinyml-1356.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 11, column 317"}, {"uri": "../vault/questions/tinyml/tinyml-1395.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 12, column 57"}, {"uri": "", "severity": 1, "code": "chain-position-duplicate", "source": "vault-check-structural", "message": "chain 'cloud-chain-467' has duplicate positions among [0, 1, 0]"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-305' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-018' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-036' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-043' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-065' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-085' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-086' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-097' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-116' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-123' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-160' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-232' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-242' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-251' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-258' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-263' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-282' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-288' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-302' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-394' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-469' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-540' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-187' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-193' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-134' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-131' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-081' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-142' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-003' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-085' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-095' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-110' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-056' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-188' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-052' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-059' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-001' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-002' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-018' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-029' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-012' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-002' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-036' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-020' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-048' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-030' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-039' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-040' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-046' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-052' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-022' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-005' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-027' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-110' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-099' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-055' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-105' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-051' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-056' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-066' has only 1 member(s); min 2"}]} diff --git a/interviews/vault-cli/check_results_final.json b/interviews/vault-cli/check_results_final.json deleted file mode 100644 index 5d796c380..000000000 --- a/interviews/vault-cli/check_results_final.json +++ /dev/null @@ -1 +0,0 @@ -{"ok": false, "exit_code": 1, "exit_symbol": "VALIDATION_FAILURE", "command": "vault check", "data": {"loaded": 10695, "load_errors": 6, "invariant_failures": 60}, "errors": [{"uri": "../vault/questions/edge/edge-0022.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 123"}, {"uri": "../vault/questions/edge/edge-0100.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 236"}, {"uri": "../vault/questions/edge/edge-0162.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: while parsing a block mapping\n in \"\", line 14, column 3\nexpected , but found ''\n in \"\", line 14, column 230"}, {"uri": "../vault/questions/edge/edge-0335.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: mapping values are not allowed here\n in \"\", line 14, column 140"}, {"uri": "../vault/questions/edge/edge-0477.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: while parsing a block mapping\n in \"\", line 14, column 3\nexpected , but found ''\n in \"\", line 14, column 82"}, {"uri": "../vault/questions/tinyml/tinyml-0616.yaml", "severity": 1, "code": "yaml-load-or-schema", "source": "vault-check", "message": "YAML load failed: while scanning for the next token\nfound character '`' that cannot start any token\n in \"\", line 34, column 5"}, {"uri": "", "severity": 1, "code": "chain-position-duplicate", "source": "vault-check-structural", "message": "chain 'cloud-chain-467' has duplicate positions among [0, 1, 0]"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-305' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-018' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-036' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-043' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-065' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-085' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-086' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-097' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-116' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-123' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-160' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-232' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-242' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-251' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-258' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-263' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-282' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-288' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-302' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-394' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-469' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-187' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-193' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-081' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-142' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-003' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-085' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-095' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-110' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-056' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-052' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-059' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-001' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-002' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-018' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-029' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-012' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-002' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-036' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-020' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-048' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-030' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-039' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-040' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-046' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-052' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-022' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-005' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-027' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-110' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-099' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-055' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-105' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-051' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-056' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-066' has only 1 member(s); min 2"}]} diff --git a/interviews/vault-cli/check_results_total_final.json b/interviews/vault-cli/check_results_total_final.json deleted file mode 100644 index 3ebd79743..000000000 --- a/interviews/vault-cli/check_results_total_final.json +++ /dev/null @@ -1 +0,0 @@ -{"ok": false, "exit_code": 1, "exit_symbol": "VALIDATION_FAILURE", "command": "vault check", "data": {"loaded": 10701, "load_errors": 0, "invariant_failures": 59}, "errors": [{"uri": "", "severity": 1, "code": "chain-position-duplicate", "source": "vault-check-structural", "message": "chain 'cloud-chain-467' has duplicate positions among [0, 1, 0]"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-305' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-018' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-036' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-043' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-065' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-085' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-086' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-097' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-116' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-123' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-160' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-232' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-242' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-251' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-258' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-263' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-282' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-288' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-302' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-394' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'cloud-chain-469' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-187' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-193' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-081' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-142' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-003' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-085' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-095' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-110' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-056' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-052' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-001' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-002' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-018' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'edge-chain-029' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-012' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-002' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-036' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-020' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-048' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-030' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-039' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-040' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-046' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-052' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-022' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-005' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'global-chain-027' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-110' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-101' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-099' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-055' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'mobile-chain-105' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-051' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-056' has only 1 member(s); min 2"}, {"uri": "", "severity": 1, "code": "chain-min-members", "source": "vault-check-structural", "message": "chain 'tinyml-chain-066' has only 1 member(s); min 2"}]} diff --git a/interviews/vault-cli/docs/GEMINI_SELF_AUDIT_PROMPT.md b/interviews/vault-cli/docs/GEMINI_SELF_AUDIT_PROMPT.md deleted file mode 100644 index 829595443..000000000 --- a/interviews/vault-cli/docs/GEMINI_SELF_AUDIT_PROMPT.md +++ /dev/null @@ -1,143 +0,0 @@ -# Self-running Gemini audit prompt - -A single prompt that lets Gemini CLI walk the corpus and audit it directly, -without the Python `audit_corpus_batched.py` wrapper. Use when the wrapper is -flaky (rate limits, exit 55, etc.) or when you want Gemini to checkpoint -results to disk as it goes. - -## How to run - -```bash -cd /Users/VJ/GitHub/MLSysBook-yaml-audit -gemini -m gemini-3.1-pro-preview --yolo --skip-trust \ - -p "$(cat interviews/vault-cli/docs/GEMINI_SELF_AUDIT_PROMPT.md | sed -n '/^## PROMPT BEGIN/,/^## PROMPT END/p' | sed '1d;$d')" \ - < /dev/null -``` - -Or paste the prompt body interactively into a fresh `gemini` session. - -The audit results are written to `interviews/vault/_pipeline/runs/gemini-self-audit/01_audit.jsonl` (one JSON record per line, appended). Resumable: re-run picks up where it left off by skipping qids already in the file. - -## PROMPT BEGIN -You are auditing the StaffML ML-systems interview corpus. Each item is a YAML -file under `interviews/vault/questions///.yaml`. Audit only -files where `status: published`. - -OUTPUT TARGET (write here, append, one JSON object per line): - `interviews/vault/_pipeline/runs/gemini-self-audit/01_audit.jsonl` -Create the directory if it doesn't exist. If the file already exists, read it -first, collect the set of qids already audited, and SKIP those — this lets -the run resume after an interruption. - -WORK PLAN -1. List published YAML files under `interviews/vault/questions/`. Track them - in lexical order (sorted by track, then area, then qid). -2. For each unaudited published file: - a. Read the YAML. Extract: id, track, level, zone, topic, competency_area, - title, scenario, question (if present), and the entire `details` block - (realistic_solution, common_mistake, napkin_math, options, correct_index). - b. Run the five gates below. - c. Append a single JSON record to the output file (with a trailing newline). -3. Every 25 questions, print a one-line progress update to stdout: - `progress: / · pass=

fail= · current=`. -4. When done, print a summary block: per-gate pass/fail counts, per-track - totals, top 10 failure rationales by frequency. - -THE FIVE GATES - - Gate A — format_compliance - common_mistake (when non-empty) must contain in order: - "**The Pitfall:**" "**The Rationale:**" "**The Consequence:**" - napkin_math (when non-empty) must contain in order: - "**Assumptions" (or "**Assumptions & Constraints:**") - "**Calculations:**" - "**Conclusion" (or "**Conclusion & Interpretation:**") - Verdict: pass | fail · with `format_issues: []` on fail. - - Gate B — level_fit - The `level` field claims a Bloom-mapped depth (L1=Remember .. L6+=Create - Staff-level). Read the question + scenario + realistic_solution and judge - whether the claimed level matches what the question actually demands. - Verdict: pass | fail - On fail: `level_fit_rationale` (1-2 sentences), `suggested_level` (e.g. "L3"). - - Gate C — coherence - Reject (verdict=fail) on any of: - 1. PHYSICAL ABSURDITY: hardware/software numbers violate real-world - bounds (e.g., NPU wake-up >50ms, smartphone pulling 50W, latency - >5× off realistic for the named hardware). - 2. VENDOR-NAME FABRICATION: hardware/framework/benchmark names that - don't exist or are misattributed (e.g., "Coral Edge TPU XL" — no XL - variant). Treat ambiguous-but-plausible as ok; flag clearly invented. - 3. SCENARIO/QUESTION/SOLUTION MISMATCH: question doesn't follow from - scenario, realistic_solution doesn't actually answer the question, - or numbers contradict across fields. - 4. ARITHMETIC IN SCENARIO: scenario contains a stated calculation that - is wrong on its face (this is separate from gate D's napkin math). - Verdict: pass | fail · `coherence_failure_mode` (one of: physical-absurdity, - vendor-fabrication, mismatch, scenario-arithmetic, none) · `coherence_rationale`. - - Gate D — math_correct - Independently re-derive the napkin_math calculations. Are the assumptions - sound? Do the unit conversions check out? Does the conclusion follow? - Verdict: pass | fail · `math_errors: []` on fail. - - Gate E — title_quality - Title (≤120 chars, plaintext, no LaTeX, no markdown, no underscores). - Verdicts: - good — descriptive, concrete, names the operative concept - generic — too vague to retrieve ("Cloud Q1", "Memory Question") - placeholder — clearly an unfilled placeholder ("TODO", "draft", "x") - On non-good: `title_suggestion` if you can produce a short concrete one. - -OUTPUT JSON SHAPE (one per line in `01_audit.jsonl`) - - { - "qid": "cloud-2297", - "track": "cloud", - "format_compliance": "pass" | "fail", - "format_issues": [], - "level_fit": "pass" | "fail", - "level_fit_rationale": "...", - "suggested_level": "L4" | null, - "coherence": "pass" | "fail", - "coherence_failure_mode": "none" | "physical-absurdity" | ..., - "coherence_rationale": "...", - "math_correct": "pass" | "fail", - "math_errors": [], - "title_quality": "good" | "generic" | "placeholder", - "title_suggestion": null - } - -CRITICAL RULES - - - Append only. Do not rewrite the file. Each batch you complete should be - durable on disk so a kill-9 mid-run loses at most one item. - - Do not modify any YAML. This is read-only audit; corrections are a - downstream task. - - Skip non-published statuses. Do not audit drafts, flagged, deleted, - or archived. - - Process at least 200 items per session. Print progress every 25. - - If you encounter a YAML you can't parse, write a record with - `qid: ""` and all gates `error`, plus `_reason: "..."`. - - If you hit a tool / network error, write what you have so far, then - print `STOPPING: ` and exit cleanly. Do not crash. - -START NOW. First action: read the existing -`interviews/vault/_pipeline/runs/gemini-self-audit/01_audit.jsonl` (or note -that it doesn't exist), then list published YAMLs. -## PROMPT END - -## Notes - -- Gemini's `--yolo --skip-trust` are required: the first lets it use file - tools without prompting, the second bypasses the workspace-trust gate that - silently breaks `--yolo` in unfamiliar `cwd`s. -- Gemini's tool-use latency is ~1-3 seconds per file read on the local FS. - 9,446 published YAMLs × 5s = ~13 hours wall-clock if Gemini reads serially. - Recommend running on a slice (one track at a time) and concatenating - results. -- To slice by track, change the WORK PLAN line to: - `1. List published YAML files under interviews/vault/questions/cloud/.` -- To resume across sessions, the JSONL append + skip-already-audited - contract makes this safe: just re-run the same prompt. diff --git a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/cloud_audit_prompt.md b/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/cloud_audit_prompt.md deleted file mode 100644 index 76b91d411..000000000 --- a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/cloud_audit_prompt.md +++ /dev/null @@ -1,107 +0,0 @@ -You are auditing the StaffML ML-systems interview corpus. Each item is a YAML -file under `interviews/vault/questions///.yaml`. Audit only -files where `status: published`. - -OUTPUT TARGET (write here, append, one JSON object per line): - `audit_results.jsonl` -Create the directory if it doesn't exist. If the file already exists, read it -first, collect the set of qids already audited, and SKIP those — this lets -the run resume after an interruption. - -WORK PLAN -1. Read the list of published YAML files from `cloud_published.txt`. Track them - in lexical order (sorted by track, then area, then qid). -2. For each unaudited published file: - a. Read the YAML. Extract: id, track, level, zone, topic, competency_area, - title, scenario, question (if present), and the entire `details` block - (realistic_solution, common_mistake, napkin_math, options, correct_index). - b. Run the five gates below. - c. Append a single JSON record to the output file (with a trailing newline). -3. Every 25 questions, print a one-line progress update to stdout: - `progress: / · pass=

fail= · current=`. -4. When done, print a summary block: per-gate pass/fail counts, per-track - totals, top 10 failure rationales by frequency. - -THE FIVE GATES - - Gate A — format_compliance - common_mistake (when non-empty) must contain in order: - "**The Pitfall:**" "**The Rationale:**" "**The Consequence:**" - napkin_math (when non-empty) must contain in order: - "**Assumptions" (or "**Assumptions & Constraints:**") - "**Calculations:**" - "**Conclusion" (or "**Conclusion & Interpretation:**") - Verdict: pass | fail · with `format_issues: []` on fail. - - Gate B — level_fit - The `level` field claims a Bloom-mapped depth (L1=Remember .. L6+=Create - Staff-level). Read the question + scenario + realistic_solution and judge - whether the claimed level matches what the question actually demands. - Verdict: pass | fail - On fail: `level_fit_rationale` (1-2 sentences), `suggested_level` (e.g. "L3"). - - Gate C — coherence - Reject (verdict=fail) on any of: - 1. PHYSICAL ABSURDITY: hardware/software numbers violate real-world - bounds (e.g., NPU wake-up >50ms, smartphone pulling 50W, latency - >5× off realistic for the named hardware). - 2. VENDOR-NAME FABRICATION: hardware/framework/benchmark names that - don't exist or are misattributed (e.g., "Coral Edge TPU XL" — no XL - variant). Treat ambiguous-but-plausible as ok; flag clearly invented. - 3. SCENARIO/QUESTION/SOLUTION MISMATCH: question doesn't follow from - scenario, realistic_solution doesn't actually answer the question, - or numbers contradict across fields. - 4. ARITHMETIC IN SCENARIO: scenario contains a stated calculation that - is wrong on its face (this is separate from gate D's napkin math). - Verdict: pass | fail · `coherence_failure_mode` (one of: physical-absurdity, - vendor-fabrication, mismatch, scenario-arithmetic, none) · `coherence_rationale`. - - Gate D — math_correct - Independently re-derive the napkin_math calculations. Are the assumptions - sound? Do the unit conversions check out? Does the conclusion follow? - Verdict: pass | fail · `math_errors: []` on fail. - - Gate E — title_quality - Title (≤120 chars, plaintext, no LaTeX, no markdown, no underscores). - Verdicts: - good — descriptive, concrete, names the operative concept - generic — too vague to retrieve ("Cloud Q1", "Memory Question") - placeholder — clearly an unfilled placeholder ("TODO", "draft", "x") - On non-good: `title_suggestion` if you can produce a short concrete one. - -OUTPUT JSON SHAPE (one per line in `01_audit.jsonl`) - - { - "qid": "cloud-2297", - "track": "cloud", - "format_compliance": "pass" | "fail", - "format_issues": [], - "level_fit": "pass" | "fail", - "level_fit_rationale": "...", - "suggested_level": "L4" | null, - "coherence": "pass" | "fail", - "coherence_failure_mode": "none" | "physical-absurdity" | ..., - "coherence_rationale": "...", - "math_correct": "pass" | "fail", - "math_errors": [], - "title_quality": "good" | "generic" | "placeholder", - "title_suggestion": null - } - -CRITICAL RULES - - - Append only. Do not rewrite the file. Each batch you complete should be - durable on disk so a kill-9 mid-run loses at most one item. - - Do not modify any YAML. This is read-only audit; corrections are a - downstream task. - - Skip non-published statuses. Do not audit drafts, flagged, deleted, - or archived. - - Process at least 200 items per session. Print progress every 25. - - If you encounter a YAML you can't parse, write a record with - `qid: ""` and all gates `error`, plus `_reason: "..."`. - - If you hit a tool / network error, write what you have so far, then - print `STOPPING: ` and exit cleanly. Do not crash. - -START NOW. First action: read the existing -`audit_results.jsonl` (or note -that it doesn't exist), then list published YAMLs. diff --git a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/edge_audit_prompt.md b/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/edge_audit_prompt.md deleted file mode 100644 index 091c22e71..000000000 --- a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/edge_audit_prompt.md +++ /dev/null @@ -1,107 +0,0 @@ -You are auditing the StaffML ML-systems interview corpus. Each item is a YAML -file under `interviews/vault/questions///.yaml`. Audit only -files where `status: published`. - -OUTPUT TARGET (write here, append, one JSON object per line): - `audit_results.jsonl` -Create the directory if it doesn't exist. If the file already exists, read it -first, collect the set of qids already audited, and SKIP those — this lets -the run resume after an interruption. - -WORK PLAN -1. Read the list of published YAML files from `edge_published.txt`. Track them - in lexical order (sorted by track, then area, then qid). -2. For each unaudited published file: - a. Read the YAML. Extract: id, track, level, zone, topic, competency_area, - title, scenario, question (if present), and the entire `details` block - (realistic_solution, common_mistake, napkin_math, options, correct_index). - b. Run the five gates below. - c. Append a single JSON record to the output file (with a trailing newline). -3. Every 25 questions, print a one-line progress update to stdout: - `progress: / · pass=

fail= · current=`. -4. When done, print a summary block: per-gate pass/fail counts, per-track - totals, top 10 failure rationales by frequency. - -THE FIVE GATES - - Gate A — format_compliance - common_mistake (when non-empty) must contain in order: - "**The Pitfall:**" "**The Rationale:**" "**The Consequence:**" - napkin_math (when non-empty) must contain in order: - "**Assumptions" (or "**Assumptions & Constraints:**") - "**Calculations:**" - "**Conclusion" (or "**Conclusion & Interpretation:**") - Verdict: pass | fail · with `format_issues: []` on fail. - - Gate B — level_fit - The `level` field claims a Bloom-mapped depth (L1=Remember .. L6+=Create - Staff-level). Read the question + scenario + realistic_solution and judge - whether the claimed level matches what the question actually demands. - Verdict: pass | fail - On fail: `level_fit_rationale` (1-2 sentences), `suggested_level` (e.g. "L3"). - - Gate C — coherence - Reject (verdict=fail) on any of: - 1. PHYSICAL ABSURDITY: hardware/software numbers violate real-world - bounds (e.g., NPU wake-up >50ms, smartphone pulling 50W, latency - >5× off realistic for the named hardware). - 2. VENDOR-NAME FABRICATION: hardware/framework/benchmark names that - don't exist or are misattributed (e.g., "Coral Edge TPU XL" — no XL - variant). Treat ambiguous-but-plausible as ok; flag clearly invented. - 3. SCENARIO/QUESTION/SOLUTION MISMATCH: question doesn't follow from - scenario, realistic_solution doesn't actually answer the question, - or numbers contradict across fields. - 4. ARITHMETIC IN SCENARIO: scenario contains a stated calculation that - is wrong on its face (this is separate from gate D's napkin math). - Verdict: pass | fail · `coherence_failure_mode` (one of: physical-absurdity, - vendor-fabrication, mismatch, scenario-arithmetic, none) · `coherence_rationale`. - - Gate D — math_correct - Independently re-derive the napkin_math calculations. Are the assumptions - sound? Do the unit conversions check out? Does the conclusion follow? - Verdict: pass | fail · `math_errors: []` on fail. - - Gate E — title_quality - Title (≤120 chars, plaintext, no LaTeX, no markdown, no underscores). - Verdicts: - good — descriptive, concrete, names the operative concept - generic — too vague to retrieve ("Cloud Q1", "Memory Question") - placeholder — clearly an unfilled placeholder ("TODO", "draft", "x") - On non-good: `title_suggestion` if you can produce a short concrete one. - -OUTPUT JSON SHAPE (one per line in `01_audit.jsonl`) - - { - "qid": "cloud-2297", - "track": "cloud", - "format_compliance": "pass" | "fail", - "format_issues": [], - "level_fit": "pass" | "fail", - "level_fit_rationale": "...", - "suggested_level": "L4" | null, - "coherence": "pass" | "fail", - "coherence_failure_mode": "none" | "physical-absurdity" | ..., - "coherence_rationale": "...", - "math_correct": "pass" | "fail", - "math_errors": [], - "title_quality": "good" | "generic" | "placeholder", - "title_suggestion": null - } - -CRITICAL RULES - - - Append only. Do not rewrite the file. Each batch you complete should be - durable on disk so a kill-9 mid-run loses at most one item. - - Do not modify any YAML. This is read-only audit; corrections are a - downstream task. - - Skip non-published statuses. Do not audit drafts, flagged, deleted, - or archived. - - Process at least 200 items per session. Print progress every 25. - - If you encounter a YAML you can't parse, write a record with - `qid: ""` and all gates `error`, plus `_reason: "..."`. - - If you hit a tool / network error, write what you have so far, then - print `STOPPING: ` and exit cleanly. Do not crash. - -START NOW. First action: read the existing -`audit_results.jsonl` (or note -that it doesn't exist), then list published YAMLs. diff --git a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/global_audit_prompt.md b/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/global_audit_prompt.md deleted file mode 100644 index 868c8b585..000000000 --- a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/global_audit_prompt.md +++ /dev/null @@ -1,107 +0,0 @@ -You are auditing the StaffML ML-systems interview corpus. Each item is a YAML -file under `interviews/vault/questions///.yaml`. Audit only -files where `status: published`. - -OUTPUT TARGET (write here, append, one JSON object per line): - `global_test.jsonl` -Create the directory if it doesn't exist. If the file already exists, read it -first, collect the set of qids already audited, and SKIP those — this lets -the run resume after an interruption. - -WORK PLAN -1. Read the list of published YAML files from `global_published.txt`. Track them - in lexical order (sorted by track, then area, then qid). -2. For each unaudited published file: - a. Read the YAML. Extract: id, track, level, zone, topic, competency_area, - title, scenario, question (if present), and the entire `details` block - (realistic_solution, common_mistake, napkin_math, options, correct_index). - b. Run the five gates below. - c. Append a single JSON record to the output file (with a trailing newline). -3. Every 25 questions, print a one-line progress update to stdout: - `progress: / · pass=

fail= · current=`. -4. When done, print a summary block: per-gate pass/fail counts, per-track - totals, top 10 failure rationales by frequency. - -THE FIVE GATES - - Gate A — format_compliance - common_mistake (when non-empty) must contain in order: - "**The Pitfall:**" "**The Rationale:**" "**The Consequence:**" - napkin_math (when non-empty) must contain in order: - "**Assumptions" (or "**Assumptions & Constraints:**") - "**Calculations:**" - "**Conclusion" (or "**Conclusion & Interpretation:**") - Verdict: pass | fail · with `format_issues: []` on fail. - - Gate B — level_fit - The `level` field claims a Bloom-mapped depth (L1=Remember .. L6+=Create - Staff-level). Read the question + scenario + realistic_solution and judge - whether the claimed level matches what the question actually demands. - Verdict: pass | fail - On fail: `level_fit_rationale` (1-2 sentences), `suggested_level` (e.g. "L3"). - - Gate C — coherence - Reject (verdict=fail) on any of: - 1. PHYSICAL ABSURDITY: hardware/software numbers violate real-world - bounds (e.g., NPU wake-up >50ms, smartphone pulling 50W, latency - >5× off realistic for the named hardware). - 2. VENDOR-NAME FABRICATION: hardware/framework/benchmark names that - don't exist or are misattributed (e.g., "Coral Edge TPU XL" — no XL - variant). Treat ambiguous-but-plausible as ok; flag clearly invented. - 3. SCENARIO/QUESTION/SOLUTION MISMATCH: question doesn't follow from - scenario, realistic_solution doesn't actually answer the question, - or numbers contradict across fields. - 4. ARITHMETIC IN SCENARIO: scenario contains a stated calculation that - is wrong on its face (this is separate from gate D's napkin math). - Verdict: pass | fail · `coherence_failure_mode` (one of: physical-absurdity, - vendor-fabrication, mismatch, scenario-arithmetic, none) · `coherence_rationale`. - - Gate D — math_correct - Independently re-derive the napkin_math calculations. Are the assumptions - sound? Do the unit conversions check out? Does the conclusion follow? - Verdict: pass | fail · `math_errors: []` on fail. - - Gate E — title_quality - Title (≤120 chars, plaintext, no LaTeX, no markdown, no underscores). - Verdicts: - good — descriptive, concrete, names the operative concept - generic — too vague to retrieve ("Cloud Q1", "Memory Question") - placeholder — clearly an unfilled placeholder ("TODO", "draft", "x") - On non-good: `title_suggestion` if you can produce a short concrete one. - -OUTPUT JSON SHAPE (one per line in `01_audit.jsonl`) - - { - "qid": "cloud-2297", - "track": "cloud", - "format_compliance": "pass" | "fail", - "format_issues": [], - "level_fit": "pass" | "fail", - "level_fit_rationale": "...", - "suggested_level": "L4" | null, - "coherence": "pass" | "fail", - "coherence_failure_mode": "none" | "physical-absurdity" | ..., - "coherence_rationale": "...", - "math_correct": "pass" | "fail", - "math_errors": [], - "title_quality": "good" | "generic" | "placeholder", - "title_suggestion": null - } - -CRITICAL RULES - - - Append only. Do not rewrite the file. Each batch you complete should be - durable on disk so a kill-9 mid-run loses at most one item. - - Do not modify any YAML. This is read-only audit; corrections are a - downstream task. - - Skip non-published statuses. Do not audit drafts, flagged, deleted, - or archived. - - Process at least 200 items per session. Print progress every 25. - - If you encounter a YAML you can't parse, write a record with - `qid: ""` and all gates `error`, plus `_reason: "..."`. - - If you hit a tool / network error, write what you have so far, then - print `STOPPING: ` and exit cleanly. Do not crash. - -START NOW. First action: read the existing -`global_test.jsonl` (or note -that it doesn't exist), then list published YAMLs. diff --git a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/mobile_audit_prompt.md b/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/mobile_audit_prompt.md deleted file mode 100644 index 88e082381..000000000 --- a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/mobile_audit_prompt.md +++ /dev/null @@ -1,107 +0,0 @@ -You are auditing the StaffML ML-systems interview corpus. Each item is a YAML -file under `interviews/vault/questions///.yaml`. Audit only -files where `status: published`. - -OUTPUT TARGET (write here, append, one JSON object per line): - `audit_results.jsonl` -Create the directory if it doesn't exist. If the file already exists, read it -first, collect the set of qids already audited, and SKIP those — this lets -the run resume after an interruption. - -WORK PLAN -1. Read the list of published YAML files from `mobile_published.txt`. Track them - in lexical order (sorted by track, then area, then qid). -2. For each unaudited published file: - a. Read the YAML. Extract: id, track, level, zone, topic, competency_area, - title, scenario, question (if present), and the entire `details` block - (realistic_solution, common_mistake, napkin_math, options, correct_index). - b. Run the five gates below. - c. Append a single JSON record to the output file (with a trailing newline). -3. Every 25 questions, print a one-line progress update to stdout: - `progress: / · pass=

fail= · current=`. -4. When done, print a summary block: per-gate pass/fail counts, per-track - totals, top 10 failure rationales by frequency. - -THE FIVE GATES - - Gate A — format_compliance - common_mistake (when non-empty) must contain in order: - "**The Pitfall:**" "**The Rationale:**" "**The Consequence:**" - napkin_math (when non-empty) must contain in order: - "**Assumptions" (or "**Assumptions & Constraints:**") - "**Calculations:**" - "**Conclusion" (or "**Conclusion & Interpretation:**") - Verdict: pass | fail · with `format_issues: []` on fail. - - Gate B — level_fit - The `level` field claims a Bloom-mapped depth (L1=Remember .. L6+=Create - Staff-level). Read the question + scenario + realistic_solution and judge - whether the claimed level matches what the question actually demands. - Verdict: pass | fail - On fail: `level_fit_rationale` (1-2 sentences), `suggested_level` (e.g. "L3"). - - Gate C — coherence - Reject (verdict=fail) on any of: - 1. PHYSICAL ABSURDITY: hardware/software numbers violate real-world - bounds (e.g., NPU wake-up >50ms, smartphone pulling 50W, latency - >5× off realistic for the named hardware). - 2. VENDOR-NAME FABRICATION: hardware/framework/benchmark names that - don't exist or are misattributed (e.g., "Coral Edge TPU XL" — no XL - variant). Treat ambiguous-but-plausible as ok; flag clearly invented. - 3. SCENARIO/QUESTION/SOLUTION MISMATCH: question doesn't follow from - scenario, realistic_solution doesn't actually answer the question, - or numbers contradict across fields. - 4. ARITHMETIC IN SCENARIO: scenario contains a stated calculation that - is wrong on its face (this is separate from gate D's napkin math). - Verdict: pass | fail · `coherence_failure_mode` (one of: physical-absurdity, - vendor-fabrication, mismatch, scenario-arithmetic, none) · `coherence_rationale`. - - Gate D — math_correct - Independently re-derive the napkin_math calculations. Are the assumptions - sound? Do the unit conversions check out? Does the conclusion follow? - Verdict: pass | fail · `math_errors: []` on fail. - - Gate E — title_quality - Title (≤120 chars, plaintext, no LaTeX, no markdown, no underscores). - Verdicts: - good — descriptive, concrete, names the operative concept - generic — too vague to retrieve ("Cloud Q1", "Memory Question") - placeholder — clearly an unfilled placeholder ("TODO", "draft", "x") - On non-good: `title_suggestion` if you can produce a short concrete one. - -OUTPUT JSON SHAPE (one per line in `01_audit.jsonl`) - - { - "qid": "cloud-2297", - "track": "cloud", - "format_compliance": "pass" | "fail", - "format_issues": [], - "level_fit": "pass" | "fail", - "level_fit_rationale": "...", - "suggested_level": "L4" | null, - "coherence": "pass" | "fail", - "coherence_failure_mode": "none" | "physical-absurdity" | ..., - "coherence_rationale": "...", - "math_correct": "pass" | "fail", - "math_errors": [], - "title_quality": "good" | "generic" | "placeholder", - "title_suggestion": null - } - -CRITICAL RULES - - - Append only. Do not rewrite the file. Each batch you complete should be - durable on disk so a kill-9 mid-run loses at most one item. - - Do not modify any YAML. This is read-only audit; corrections are a - downstream task. - - Skip non-published statuses. Do not audit drafts, flagged, deleted, - or archived. - - Process at least 200 items per session. Print progress every 25. - - If you encounter a YAML you can't parse, write a record with - `qid: ""` and all gates `error`, plus `_reason: "..."`. - - If you hit a tool / network error, write what you have so far, then - print `STOPPING: ` and exit cleanly. Do not crash. - -START NOW. First action: read the existing -`audit_results.jsonl` (or note -that it doesn't exist), then list published YAMLs. diff --git a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/tinyml_audit_prompt.md b/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/tinyml_audit_prompt.md deleted file mode 100644 index edb3d67b2..000000000 --- a/interviews/vault/_pipeline/runs/gemini-self-audit/prompts/tinyml_audit_prompt.md +++ /dev/null @@ -1,107 +0,0 @@ -You are auditing the StaffML ML-systems interview corpus. Each item is a YAML -file under `interviews/vault/questions///.yaml`. Audit only -files where `status: published`. - -OUTPUT TARGET (write here, append, one JSON object per line): - `audit_results.jsonl` -Create the directory if it doesn't exist. If the file already exists, read it -first, collect the set of qids already audited, and SKIP those — this lets -the run resume after an interruption. - -WORK PLAN -1. Read the list of published YAML files from `tinyml_published.txt`. Track them - in lexical order (sorted by track, then area, then qid). -2. For each unaudited published file: - a. Read the YAML. Extract: id, track, level, zone, topic, competency_area, - title, scenario, question (if present), and the entire `details` block - (realistic_solution, common_mistake, napkin_math, options, correct_index). - b. Run the five gates below. - c. Append a single JSON record to the output file (with a trailing newline). -3. Every 25 questions, print a one-line progress update to stdout: - `progress: / · pass=

fail= · current=`. -4. When done, print a summary block: per-gate pass/fail counts, per-track - totals, top 10 failure rationales by frequency. - -THE FIVE GATES - - Gate A — format_compliance - common_mistake (when non-empty) must contain in order: - "**The Pitfall:**" "**The Rationale:**" "**The Consequence:**" - napkin_math (when non-empty) must contain in order: - "**Assumptions" (or "**Assumptions & Constraints:**") - "**Calculations:**" - "**Conclusion" (or "**Conclusion & Interpretation:**") - Verdict: pass | fail · with `format_issues: []` on fail. - - Gate B — level_fit - The `level` field claims a Bloom-mapped depth (L1=Remember .. L6+=Create - Staff-level). Read the question + scenario + realistic_solution and judge - whether the claimed level matches what the question actually demands. - Verdict: pass | fail - On fail: `level_fit_rationale` (1-2 sentences), `suggested_level` (e.g. "L3"). - - Gate C — coherence - Reject (verdict=fail) on any of: - 1. PHYSICAL ABSURDITY: hardware/software numbers violate real-world - bounds (e.g., NPU wake-up >50ms, smartphone pulling 50W, latency - >5× off realistic for the named hardware). - 2. VENDOR-NAME FABRICATION: hardware/framework/benchmark names that - don't exist or are misattributed (e.g., "Coral Edge TPU XL" — no XL - variant). Treat ambiguous-but-plausible as ok; flag clearly invented. - 3. SCENARIO/QUESTION/SOLUTION MISMATCH: question doesn't follow from - scenario, realistic_solution doesn't actually answer the question, - or numbers contradict across fields. - 4. ARITHMETIC IN SCENARIO: scenario contains a stated calculation that - is wrong on its face (this is separate from gate D's napkin math). - Verdict: pass | fail · `coherence_failure_mode` (one of: physical-absurdity, - vendor-fabrication, mismatch, scenario-arithmetic, none) · `coherence_rationale`. - - Gate D — math_correct - Independently re-derive the napkin_math calculations. Are the assumptions - sound? Do the unit conversions check out? Does the conclusion follow? - Verdict: pass | fail · `math_errors: []` on fail. - - Gate E — title_quality - Title (≤120 chars, plaintext, no LaTeX, no markdown, no underscores). - Verdicts: - good — descriptive, concrete, names the operative concept - generic — too vague to retrieve ("Cloud Q1", "Memory Question") - placeholder — clearly an unfilled placeholder ("TODO", "draft", "x") - On non-good: `title_suggestion` if you can produce a short concrete one. - -OUTPUT JSON SHAPE (one per line in `01_audit.jsonl`) - - { - "qid": "cloud-2297", - "track": "cloud", - "format_compliance": "pass" | "fail", - "format_issues": [], - "level_fit": "pass" | "fail", - "level_fit_rationale": "...", - "suggested_level": "L4" | null, - "coherence": "pass" | "fail", - "coherence_failure_mode": "none" | "physical-absurdity" | ..., - "coherence_rationale": "...", - "math_correct": "pass" | "fail", - "math_errors": [], - "title_quality": "good" | "generic" | "placeholder", - "title_suggestion": null - } - -CRITICAL RULES - - - Append only. Do not rewrite the file. Each batch you complete should be - durable on disk so a kill-9 mid-run loses at most one item. - - Do not modify any YAML. This is read-only audit; corrections are a - downstream task. - - Skip non-published statuses. Do not audit drafts, flagged, deleted, - or archived. - - Process at least 200 items per session. Print progress every 25. - - If you encounter a YAML you can't parse, write a record with - `qid: ""` and all gates `error`, plus `_reason: "..."`. - - If you hit a tool / network error, write what you have so far, then - print `STOPPING: ` and exit cleanly. Do not crash. - -START NOW. First action: read the existing -`audit_results.jsonl` (or note -that it doesn't exist), then list published YAMLs.