@agent-ix/quoin 0.23.1 → 0.26.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -258
- package/bin/launcher.js +138 -0
- package/package.json +22 -123
- package/.agents/plugins/marketplace.json +0 -14
- package/.claude-plugin/marketplace.json +0 -16
- package/.claude-plugin/plugin.json +0 -8
- package/.codex-plugin/plugin.json +0 -27
- package/.github/plugin/marketplace.json +0 -16
- package/bin/quoin.js +0 -21
- package/default-modules.yaml +0 -107
- package/dist/advisor/advise.d.ts +0 -199
- package/dist/advisor/advise.d.ts.map +0 -1
- package/dist/advisor/index.d.ts +0 -10
- package/dist/advisor/index.d.ts.map +0 -1
- package/dist/advisor/methods.d.ts +0 -60
- package/dist/advisor/methods.d.ts.map +0 -1
- package/dist/advisor-B0rESCx1.js +0 -63
- package/dist/assurance/graph.d.ts +0 -87
- package/dist/assurance/graph.d.ts.map +0 -1
- package/dist/assurance/index.d.ts +0 -9
- package/dist/assurance/index.d.ts.map +0 -1
- package/dist/assurance/render.d.ts +0 -3
- package/dist/assurance/render.d.ts.map +0 -1
- package/dist/auditor/audit.d.ts +0 -146
- package/dist/auditor/audit.d.ts.map +0 -1
- package/dist/auditor/combinatorial.d.ts +0 -53
- package/dist/auditor/combinatorial.d.ts.map +0 -1
- package/dist/auditor/index.d.ts +0 -9
- package/dist/auditor/index.d.ts.map +0 -1
- package/dist/auditor-Dd3i9Aqx.js +0 -340
- package/dist/base-gAClyCNd.js +0 -137
- package/dist/base.d.ts +0 -23
- package/dist/base.d.ts.map +0 -1
- package/dist/catalog.d.ts +0 -33
- package/dist/catalog.d.ts.map +0 -1
- package/dist/change-assurance/attestations.d.ts +0 -7
- package/dist/change-assurance/attestations.d.ts.map +0 -1
- package/dist/change-assurance/index.d.ts +0 -14
- package/dist/change-assurance/index.d.ts.map +0 -1
- package/dist/change-assurance/integrity.d.ts +0 -11
- package/dist/change-assurance/integrity.d.ts.map +0 -1
- package/dist/change-assurance/records.d.ts +0 -22
- package/dist/change-assurance/records.d.ts.map +0 -1
- package/dist/change-assurance/schema-assets.d.ts +0 -8
- package/dist/change-assurance/schema-assets.d.ts.map +0 -1
- package/dist/change-assurance/store.d.ts +0 -18
- package/dist/change-assurance/store.d.ts.map +0 -1
- package/dist/change-assurance/types.d.ts +0 -180
- package/dist/change-assurance/types.d.ts.map +0 -1
- package/dist/change-assurance/verify.d.ts +0 -4
- package/dist/change-assurance/verify.d.ts.map +0 -1
- package/dist/change-assurance-CyKLPeKa.js +0 -1236
- package/dist/cli.d.ts +0 -61
- package/dist/cli.d.ts.map +0 -1
- package/dist/cli.js +0 -34
- package/dist/commands/advise.d.ts +0 -16
- package/dist/commands/advise.d.ts.map +0 -1
- package/dist/commands/advise.js +0 -234
- package/dist/commands/assurance.d.ts +0 -14
- package/dist/commands/assurance.d.ts.map +0 -1
- package/dist/commands/assurance.js +0 -204
- package/dist/commands/catalog/index.d.ts +0 -2
- package/dist/commands/catalog/index.d.ts.map +0 -1
- package/dist/commands/catalog/index.js +0 -2
- package/dist/commands/catalog/list.d.ts +0 -11
- package/dist/commands/catalog/list.d.ts.map +0 -1
- package/dist/commands/catalog/list.js +0 -22
- package/dist/commands/catalog/methods.d.ts +0 -12
- package/dist/commands/catalog/methods.d.ts.map +0 -1
- package/dist/commands/catalog/methods.js +0 -43
- package/dist/commands/catalog/show.d.ts +0 -13
- package/dist/commands/catalog/show.d.ts.map +0 -1
- package/dist/commands/catalog/show.js +0 -25
- package/dist/commands/catalog/validate.d.ts +0 -10
- package/dist/commands/catalog/validate.d.ts.map +0 -1
- package/dist/commands/catalog/validate.js +0 -27
- package/dist/commands/change-assurance/common.d.ts +0 -37
- package/dist/commands/change-assurance/common.d.ts.map +0 -1
- package/dist/commands/change-assurance/index.d.ts +0 -8
- package/dist/commands/change-assurance/index.d.ts.map +0 -1
- package/dist/commands/change-assurance/index.js +0 -12
- package/dist/commands/change-assurance/intake.d.ts +0 -15
- package/dist/commands/change-assurance/intake.d.ts.map +0 -1
- package/dist/commands/change-assurance/intake.js +0 -53
- package/dist/commands/change-assurance/receipt.d.ts +0 -21
- package/dist/commands/change-assurance/receipt.d.ts.map +0 -1
- package/dist/commands/change-assurance/receipt.js +0 -99
- package/dist/commands/change-assurance/recover.d.ts +0 -13
- package/dist/commands/change-assurance/recover.d.ts.map +0 -1
- package/dist/commands/change-assurance/recover.js +0 -29
- package/dist/commands/change-assurance/schema.d.ts +0 -13
- package/dist/commands/change-assurance/schema.d.ts.map +0 -1
- package/dist/commands/change-assurance/schema.js +0 -40
- package/dist/commands/change-assurance/seal-attestation.d.ts +0 -15
- package/dist/commands/change-assurance/seal-attestation.d.ts.map +0 -1
- package/dist/commands/change-assurance/seal-attestation.js +0 -58
- package/dist/commands/change-assurance/seal-record.d.ts +0 -14
- package/dist/commands/change-assurance/seal-record.d.ts.map +0 -1
- package/dist/commands/change-assurance/seal-record.js +0 -53
- package/dist/commands/change-assurance/verify-receipt.d.ts +0 -13
- package/dist/commands/change-assurance/verify-receipt.d.ts.map +0 -1
- package/dist/commands/change-assurance/verify-receipt.js +0 -41
- package/dist/commands/completeness.d.ts +0 -16
- package/dist/commands/completeness.d.ts.map +0 -1
- package/dist/commands/completeness.js +0 -49
- package/dist/commands/config/doctor.d.ts +0 -7
- package/dist/commands/config/doctor.d.ts.map +0 -1
- package/dist/commands/config/doctor.js +0 -15
- package/dist/commands/config/edit.d.ts +0 -7
- package/dist/commands/config/edit.d.ts.map +0 -1
- package/dist/commands/config/edit.js +0 -13
- package/dist/commands/config/get.d.ts +0 -11
- package/dist/commands/config/get.d.ts.map +0 -1
- package/dist/commands/config/get.js +0 -20
- package/dist/commands/config/index.d.ts +0 -2
- package/dist/commands/config/index.d.ts.map +0 -1
- package/dist/commands/config/index.js +0 -2
- package/dist/commands/config/set.d.ts +0 -12
- package/dist/commands/config/set.d.ts.map +0 -1
- package/dist/commands/config/set.js +0 -26
- package/dist/commands/evidence/affirm.d.ts +0 -17
- package/dist/commands/evidence/affirm.d.ts.map +0 -1
- package/dist/commands/evidence/affirm.js +0 -65
- package/dist/commands/evidence/audit.d.ts +0 -34
- package/dist/commands/evidence/audit.d.ts.map +0 -1
- package/dist/commands/evidence/audit.js +0 -107
- package/dist/commands/evidence/baseline.d.ts +0 -14
- package/dist/commands/evidence/baseline.d.ts.map +0 -1
- package/dist/commands/evidence/baseline.js +0 -89
- package/dist/commands/evidence/gc.d.ts +0 -13
- package/dist/commands/evidence/gc.d.ts.map +0 -1
- package/dist/commands/evidence/gc.js +0 -35
- package/dist/commands/evidence/index.d.ts +0 -8
- package/dist/commands/evidence/index.d.ts.map +0 -1
- package/dist/commands/evidence/index.js +0 -18
- package/dist/commands/evidence/inspect-mocks.d.ts +0 -16
- package/dist/commands/evidence/inspect-mocks.d.ts.map +0 -1
- package/dist/commands/evidence/inspect-mocks.js +0 -49
- package/dist/commands/evidence/record.d.ts +0 -22
- package/dist/commands/evidence/record.d.ts.map +0 -1
- package/dist/commands/evidence/record.js +0 -144
- package/dist/commands/graph/change-impact.d.ts +0 -16
- package/dist/commands/graph/change-impact.d.ts.map +0 -1
- package/dist/commands/graph/change-impact.js +0 -29
- package/dist/commands/graph/churn.d.ts +0 -14
- package/dist/commands/graph/churn.d.ts.map +0 -1
- package/dist/commands/graph/churn.js +0 -15
- package/dist/commands/graph/common.d.ts +0 -16
- package/dist/commands/graph/common.d.ts.map +0 -1
- package/dist/commands/graph/fan-out.d.ts +0 -14
- package/dist/commands/graph/fan-out.d.ts.map +0 -1
- package/dist/commands/graph/fan-out.js +0 -15
- package/dist/commands/graph/index.d.ts +0 -8
- package/dist/commands/graph/index.d.ts.map +0 -1
- package/dist/commands/graph/index.js +0 -12
- package/dist/commands/matrix.d.ts +0 -14
- package/dist/commands/matrix.d.ts.map +0 -1
- package/dist/commands/matrix.js +0 -15
- package/dist/commands/measurement/index.d.ts +0 -7
- package/dist/commands/measurement/index.d.ts.map +0 -1
- package/dist/commands/measurement/index.js +0 -11
- package/dist/commands/measurement/intervention.d.ts +0 -11
- package/dist/commands/measurement/intervention.d.ts.map +0 -1
- package/dist/commands/measurement/intervention.js +0 -31
- package/dist/commands/measurement/operational-release.d.ts +0 -11
- package/dist/commands/measurement/operational-release.d.ts.map +0 -1
- package/dist/commands/measurement/operational-release.js +0 -31
- package/dist/commands/measurement/record.d.ts +0 -10
- package/dist/commands/measurement/record.d.ts.map +0 -1
- package/dist/commands/measurement/record.js +0 -36
- package/dist/commands/module/ensure-defaults.d.ts +0 -8
- package/dist/commands/module/ensure-defaults.d.ts.map +0 -1
- package/dist/commands/module/ensure-defaults.js +0 -17
- package/dist/commands/module/index.d.ts +0 -2
- package/dist/commands/module/index.d.ts.map +0 -1
- package/dist/commands/module/index.js +0 -2
- package/dist/commands/module/install.d.ts +0 -11
- package/dist/commands/module/install.d.ts.map +0 -1
- package/dist/commands/module/install.js +0 -22
- package/dist/commands/module/list.d.ts +0 -8
- package/dist/commands/module/list.d.ts.map +0 -1
- package/dist/commands/module/list.js +0 -13
- package/dist/commands/module/remove.d.ts +0 -10
- package/dist/commands/module/remove.d.ts.map +0 -1
- package/dist/commands/module/remove.js +0 -16
- package/dist/commands/plugin/deprecation.d.ts +0 -10
- package/dist/commands/plugin/deprecation.d.ts.map +0 -1
- package/dist/commands/plugin/ensure-defaults.d.ts +0 -8
- package/dist/commands/plugin/ensure-defaults.d.ts.map +0 -1
- package/dist/commands/plugin/ensure-defaults.js +0 -12
- package/dist/commands/plugin/index.d.ts +0 -2
- package/dist/commands/plugin/index.d.ts.map +0 -1
- package/dist/commands/plugin/index.js +0 -2
- package/dist/commands/plugin/install.d.ts +0 -8
- package/dist/commands/plugin/install.d.ts.map +0 -1
- package/dist/commands/plugin/install.js +0 -12
- package/dist/commands/plugin/list.d.ts +0 -8
- package/dist/commands/plugin/list.d.ts.map +0 -1
- package/dist/commands/plugin/list.js +0 -12
- package/dist/commands/plugin/remove.d.ts +0 -8
- package/dist/commands/plugin/remove.d.ts.map +0 -1
- package/dist/commands/plugin/remove.js +0 -12
- package/dist/commands/report.d.ts +0 -19
- package/dist/commands/report.d.ts.map +0 -1
- package/dist/commands/report.js +0 -96
- package/dist/commands/review.d.ts +0 -14
- package/dist/commands/review.d.ts.map +0 -1
- package/dist/commands/review.js +0 -15
- package/dist/commands/to-plan.d.ts +0 -14
- package/dist/commands/to-plan.d.ts.map +0 -1
- package/dist/commands/to-plan.js +0 -15
- package/dist/commands/update.d.ts +0 -13
- package/dist/commands/update.d.ts.map +0 -1
- package/dist/commands/update.js +0 -34
- package/dist/commands/validate.d.ts +0 -13
- package/dist/commands/validate.d.ts.map +0 -1
- package/dist/commands/validate.js +0 -123
- package/dist/commands/write.d.ts +0 -16
- package/dist/commands/write.d.ts.map +0 -1
- package/dist/commands/write.js +0 -33
- package/dist/common-B1ZJ8CSO.js +0 -36
- package/dist/common-DTrmnvL-.js +0 -35
- package/dist/completeness/assess.d.ts +0 -82
- package/dist/completeness/assess.d.ts.map +0 -1
- package/dist/completeness/bundle.d.ts +0 -52
- package/dist/completeness/bundle.d.ts.map +0 -1
- package/dist/completeness/declarations.d.ts +0 -46
- package/dist/completeness/declarations.d.ts.map +0 -1
- package/dist/completeness/index.d.ts +0 -11
- package/dist/completeness/index.d.ts.map +0 -1
- package/dist/completeness/run.d.ts +0 -35
- package/dist/completeness/run.d.ts.map +0 -1
- package/dist/completeness-BzBuNq6w.js +0 -228
- package/dist/config-schema-Dp-vlxuR.js +0 -13
- package/dist/config-schema.d.ts +0 -52
- package/dist/config-schema.d.ts.map +0 -1
- package/dist/deprecation-fRxUHoxv.js +0 -4
- package/dist/evidence/adapters/agent-eval.d.ts +0 -26
- package/dist/evidence/adapters/agent-eval.d.ts.map +0 -1
- package/dist/evidence/adapters/audit-script.d.ts +0 -25
- package/dist/evidence/adapters/audit-script.d.ts.map +0 -1
- package/dist/evidence/adapters/cargo-mutants.d.ts +0 -3
- package/dist/evidence/adapters/cargo-mutants.d.ts.map +0 -1
- package/dist/evidence/adapters/contract-conformance.d.ts +0 -16
- package/dist/evidence/adapters/contract-conformance.d.ts.map +0 -1
- package/dist/evidence/adapters/differential-report.d.ts +0 -18
- package/dist/evidence/adapters/differential-report.d.ts.map +0 -1
- package/dist/evidence/adapters/junit.d.ts +0 -17
- package/dist/evidence/adapters/junit.d.ts.map +0 -1
- package/dist/evidence/adapters/registry.d.ts +0 -63
- package/dist/evidence/adapters/registry.d.ts.map +0 -1
- package/dist/evidence/adapters/sarif.d.ts +0 -35
- package/dist/evidence/adapters/sarif.d.ts.map +0 -1
- package/dist/evidence/adapters/sbom.d.ts +0 -35
- package/dist/evidence/adapters/sbom.d.ts.map +0 -1
- package/dist/evidence/adapters/types.d.ts +0 -86
- package/dist/evidence/adapters/types.d.ts.map +0 -1
- package/dist/evidence/index.d.ts +0 -27
- package/dist/evidence/index.d.ts.map +0 -1
- package/dist/evidence/mock-inspection.d.ts +0 -16
- package/dist/evidence/mock-inspection.d.ts.map +0 -1
- package/dist/evidence/record.d.ts +0 -58
- package/dist/evidence/record.d.ts.map +0 -1
- package/dist/evidence/store.d.ts +0 -215
- package/dist/evidence/store.d.ts.map +0 -1
- package/dist/evidence/types.d.ts +0 -281
- package/dist/evidence/types.d.ts.map +0 -1
- package/dist/evidence-OyqpqHLS.js +0 -614
- package/dist/flow-command-CCRTE5Oe.js +0 -88
- package/dist/flow-command.d.ts +0 -25
- package/dist/flow-command.d.ts.map +0 -1
- package/dist/flows.d.ts +0 -7
- package/dist/flows.d.ts.map +0 -1
- package/dist/graph-analysis/analysis.d.ts +0 -106
- package/dist/graph-analysis/analysis.d.ts.map +0 -1
- package/dist/graph-analysis/index.d.ts +0 -6
- package/dist/graph-analysis/index.d.ts.map +0 -1
- package/dist/graph-analysis/input.d.ts +0 -33
- package/dist/graph-analysis/input.d.ts.map +0 -1
- package/dist/graph-analysis/load.d.ts +0 -21
- package/dist/graph-analysis/load.d.ts.map +0 -1
- package/dist/graph-analysis/render.d.ts +0 -4
- package/dist/graph-analysis/render.d.ts.map +0 -1
- package/dist/graph-analysis-IWaoJJSN.js +0 -657
- package/dist/hooks/command-not-found.d.ts +0 -23
- package/dist/hooks/command-not-found.d.ts.map +0 -1
- package/dist/hooks/command-not-found.js +0 -8
- package/dist/index.d.ts +0 -13
- package/dist/index.d.ts.map +0 -1
- package/dist/index.js +0 -12
- package/dist/measurement/agent-eval-intervention.d.ts +0 -6
- package/dist/measurement/agent-eval-intervention.d.ts.map +0 -1
- package/dist/measurement/atomic-file.d.ts +0 -5
- package/dist/measurement/atomic-file.d.ts.map +0 -1
- package/dist/measurement/compare.d.ts +0 -4
- package/dist/measurement/compare.d.ts.map +0 -1
- package/dist/measurement/date-time.d.ts +0 -3
- package/dist/measurement/date-time.d.ts.map +0 -1
- package/dist/measurement/github-release-operational.d.ts +0 -7
- package/dist/measurement/github-release-operational.d.ts.map +0 -1
- package/dist/measurement/graph-adapters.d.ts +0 -304
- package/dist/measurement/graph-adapters.d.ts.map +0 -1
- package/dist/measurement/graph-portfolio-load.d.ts +0 -3
- package/dist/measurement/graph-portfolio-load.d.ts.map +0 -1
- package/dist/measurement/graph-portfolio.d.ts +0 -158
- package/dist/measurement/graph-portfolio.d.ts.map +0 -1
- package/dist/measurement/index.d.ts +0 -22
- package/dist/measurement/index.d.ts.map +0 -1
- package/dist/measurement/intervention-report.d.ts +0 -24
- package/dist/measurement/intervention-report.d.ts.map +0 -1
- package/dist/measurement/intervention-schema.d.ts +0 -144
- package/dist/measurement/intervention-schema.d.ts.map +0 -1
- package/dist/measurement/intervention-types.d.ts +0 -105
- package/dist/measurement/intervention-types.d.ts.map +0 -1
- package/dist/measurement/intervention.d.ts +0 -16
- package/dist/measurement/intervention.d.ts.map +0 -1
- package/dist/measurement/operational-report.d.ts +0 -17
- package/dist/measurement/operational-report.d.ts.map +0 -1
- package/dist/measurement/operational-schema.d.ts +0 -461
- package/dist/measurement/operational-schema.d.ts.map +0 -1
- package/dist/measurement/operational-types.d.ts +0 -121
- package/dist/measurement/operational-types.d.ts.map +0 -1
- package/dist/measurement/operational.d.ts +0 -13
- package/dist/measurement/operational.d.ts.map +0 -1
- package/dist/measurement/plans.d.ts +0 -6
- package/dist/measurement/plans.d.ts.map +0 -1
- package/dist/measurement/portfolio.d.ts +0 -54
- package/dist/measurement/portfolio.d.ts.map +0 -1
- package/dist/measurement/profiles.d.ts +0 -9
- package/dist/measurement/profiles.d.ts.map +0 -1
- package/dist/measurement/report.d.ts +0 -48
- package/dist/measurement/report.d.ts.map +0 -1
- package/dist/measurement/schemas/operational-evidence-v1.schema.json.d.ts +0 -384
- package/dist/measurement/store.d.ts +0 -14
- package/dist/measurement/store.d.ts.map +0 -1
- package/dist/measurement/types.d.ts +0 -85
- package/dist/measurement/types.d.ts.map +0 -1
- package/dist/measurement/validate.d.ts +0 -9
- package/dist/measurement/validate.d.ts.map +0 -1
- package/dist/measurement-j8sDSqx5.js +0 -2980
- package/dist/modules-DDQkKC4l.js +0 -23
- package/dist/modules.d.ts +0 -10
- package/dist/modules.d.ts.map +0 -1
- package/dist/org.d.ts +0 -61
- package/dist/org.d.ts.map +0 -1
- package/dist/plugins-CHpYhpEI.js +0 -77
- package/dist/plugins.d.ts +0 -13
- package/dist/plugins.d.ts.map +0 -1
- package/dist/quire/assurance.d.ts +0 -109
- package/dist/quire/assurance.d.ts.map +0 -1
- package/dist/quire/contract.d.ts +0 -88
- package/dist/quire/contract.d.ts.map +0 -1
- package/dist/quire/exec.d.ts +0 -66
- package/dist/quire/exec.d.ts.map +0 -1
- package/dist/quire/index.d.ts +0 -13
- package/dist/quire/index.d.ts.map +0 -1
- package/dist/quire/types.d.ts +0 -415
- package/dist/quire/types.d.ts.map +0 -1
- package/dist/quire/validate.d.ts +0 -39
- package/dist/quire/validate.d.ts.map +0 -1
- package/dist/quire-BsVj1xIR.js +0 -4968
- package/dist/schema-assets-HZWo_iFN.js +0 -233
- package/dist/schemas/assurance-v1.schema.json +0 -225
- package/dist/schemas/change-assurance-record-v1.schema.json +0 -234
- package/dist/schemas/coverage-v1.schema.json +0 -1111
- package/dist/schemas/operational-evidence-v1.schema.json +0 -381
- package/dist/schemas/proof-attestation-v1.schema.json +0 -96
- package/dist/schemas/properties-v1.schema.json +0 -159
- package/dist/schemas/verification-receipt-v1.schema.json +0 -208
- package/dist/validators/gates.d.ts +0 -18
- package/dist/validators/gates.d.ts.map +0 -1
- package/dist/validators/index.d.ts +0 -2
- package/dist/validators/index.d.ts.map +0 -1
- package/dist/version-CMxMIh5g.js +0 -17
- package/dist/version.d.ts +0 -3
- package/dist/version.d.ts.map +0 -1
- package/dist/write-CGTI0dRO.js +0 -157
- package/dist/write.d.ts +0 -28
- package/dist/write.d.ts.map +0 -1
- package/skills/assurance-status-report/SKILL.md +0 -135
- package/skills/assurance-status-report/references/report-contract.md +0 -110
- package/skills/gap-analysis/SKILL.md +0 -111
- package/skills/gap-analysis/references/step-1-target-selection.md +0 -53
- package/skills/gap-analysis/references/step-2-plan-completion.md +0 -49
- package/skills/gap-analysis/references/step-3-matrix-verification.md +0 -147
- package/skills/gap-analysis/references/step-4-underspecified-code.md +0 -92
- package/skills/gap-analysis/references/step-5-semantic-review.md +0 -51
- package/skills/gap-analysis/references/step-6-specreview-artifact.md +0 -108
- package/skills/spec-app-review/SKILL.md +0 -51
- package/skills/spec-app-review/references/checklist.md +0 -197
- package/skills/spec-architecture-evaluation/SKILL.md +0 -30
- package/skills/spec-correctness/SKILL.md +0 -96
- package/skills/spec-correctness/assets/strategy-table.md +0 -101
- package/skills/spec-correctness/assets/templates/fast-check.ts.md +0 -169
- package/skills/spec-correctness/assets/templates/hypothesis.py.md +0 -156
- package/skills/spec-correctness/assets/templates/proptest.rs.md +0 -147
- package/skills/spec-correctness/references/step-0-scope-and-harness.md +0 -94
- package/skills/spec-correctness/references/step-1-census.md +0 -53
- package/skills/spec-correctness/references/step-2-clause-grounding.md +0 -159
- package/skills/spec-correctness/references/step-3-strategy-selection.md +0 -85
- package/skills/spec-correctness/references/step-4-generate-tests.md +0 -117
- package/skills/spec-correctness/references/step-5-second-pass.md +0 -81
- package/skills/spec-correctness/references/step-6-review-artifact.md +0 -134
- package/skills/spec-correctness/references/step-7-report-and-handoff.md +0 -102
- package/skills/spec-dependency-analysis/SKILL.md +0 -90
- package/skills/spec-ears-analysis/SKILL.md +0 -102
- package/skills/spec-evidence-analysis/SKILL.md +0 -156
- package/skills/spec-failure-domain-analysis/SKILL.md +0 -59
- package/skills/spec-fuzz/SKILL.md +0 -133
- package/skills/spec-fuzz/assets/templates/atheris.py.md +0 -74
- package/skills/spec-fuzz/assets/templates/cargo-fuzz.rs.md +0 -83
- package/skills/spec-fuzz/assets/templates/fast-check.ts.md +0 -76
- package/skills/spec-fuzz/references/step-0-scope-and-harness.md +0 -51
- package/skills/spec-fuzz/references/step-1-select-obligations.md +0 -47
- package/skills/spec-fuzz/references/step-2-ground-entry-point.md +0 -55
- package/skills/spec-fuzz/references/step-3-emit-targets.md +0 -65
- package/skills/spec-fuzz/references/step-4-report.md +0 -56
- package/skills/spec-ideation/SKILL.md +0 -46
- package/skills/spec-integrity-analysis/SKILL.md +0 -62
- package/skills/spec-matrix/SKILL.md +0 -186
- package/skills/spec-matrix/assets/test-cases/TC-001.md +0 -35
- package/skills/spec-matrix/assets/test-cases/TC-002.md +0 -37
- package/skills/spec-matrix/assets/test-cases/TC-006.md +0 -50
- package/skills/spec-matrix/assets/test-matrix-example.md +0 -104
- package/skills/spec-matrix/assets/test-matrix-template.md +0 -123
- package/skills/spec-matrix/workflow-assets/dist/index.d.ts +0 -146
- package/skills/spec-matrix/workflow-assets/dist/index.d.ts.map +0 -1
- package/skills/spec-matrix/workflow-assets/dist/index.js +0 -7525
- package/skills/spec-matrix/workflow-assets/dist/invariants.d.ts +0 -6
- package/skills/spec-matrix/workflow-assets/dist/invariants.d.ts.map +0 -1
- package/skills/spec-matrix/workflow-assets/skills/matrix/SKILL.md +0 -35
- package/skills/spec-matrix/workflow-assets/skills/matrix/scripts/invariants.js +0 -1
- package/skills/spec-matrix/workflow-assets/skills/matrix/templates/report/default.md +0 -30
- package/skills/spec-matrix/workflow-assets/skills/matrix/workflows/matrix/def.yaml +0 -82
- package/skills/spec-object-review/SKILL.md +0 -125
- package/skills/spec-object-review/references/object-type-guide.md +0 -118
- package/skills/spec-review/SKILL.md +0 -92
- package/skills/spec-review/references/checklist.md +0 -50
- package/skills/spec-review/workflow-assets/dist/index.d.ts +0 -146
- package/skills/spec-review/workflow-assets/dist/index.d.ts.map +0 -1
- package/skills/spec-review/workflow-assets/dist/index.js +0 -7525
- package/skills/spec-review/workflow-assets/dist/invariants.d.ts +0 -6
- package/skills/spec-review/workflow-assets/dist/invariants.d.ts.map +0 -1
- package/skills/spec-review/workflow-assets/skills/review/SKILL.md +0 -96
- package/skills/spec-review/workflow-assets/skills/review/scripts/invariants.js +0 -61
- package/skills/spec-review/workflow-assets/skills/review/workflows/review/def.yaml +0 -68
- package/skills/spec-risk-complexity-analysis/SKILL.md +0 -92
- package/skills/spec-scope-boundary-analysis/SKILL.md +0 -101
- package/skills/spec-security-analysis/SKILL.md +0 -84
- package/skills/spec-security-analysis/assets/security-analysis-example.md +0 -89
- package/skills/spec-security-analysis/assets/security-analysis-template.md +0 -73
- package/skills/spec-security-analysis/references/component-type-mapping.md +0 -161
- package/skills/spec-security-analysis/references/gdpr/ChII-Principles.md +0 -58
- package/skills/spec-security-analysis/references/gdpr/ChIII-DataSubjectRights.md +0 -84
- package/skills/spec-security-analysis/references/gdpr/ChIV-ControllerProcessor.md +0 -83
- package/skills/spec-security-analysis/references/gdpr/ChV-DataTransfers.md +0 -62
- package/skills/spec-security-analysis/references/gdpr/index.md +0 -54
- package/skills/spec-security-analysis/references/iso27001/A5-OrganizationalControls.md +0 -64
- package/skills/spec-security-analysis/references/iso27001/A6-PeopleControls.md +0 -30
- package/skills/spec-security-analysis/references/iso27001/A7-PhysicalControls.md +0 -35
- package/skills/spec-security-analysis/references/iso27001/A8-TechnologicalControls.md +0 -66
- package/skills/spec-security-analysis/references/iso27001/index.md +0 -43
- package/skills/spec-security-analysis/references/nist-800-53/AC-AccessControl.md +0 -57
- package/skills/spec-security-analysis/references/nist-800-53/AU-AuditAccountability.md +0 -49
- package/skills/spec-security-analysis/references/nist-800-53/CM-ConfigurationManagement.md +0 -36
- package/skills/spec-security-analysis/references/nist-800-53/IA-IdentificationAuthentication.md +0 -44
- package/skills/spec-security-analysis/references/nist-800-53/SA-SystemServicesAcquisition.md +0 -50
- package/skills/spec-security-analysis/references/nist-800-53/SC-SystemCommunications.md +0 -53
- package/skills/spec-security-analysis/references/nist-800-53/SI-SystemInformationIntegrity.md +0 -52
- package/skills/spec-security-analysis/references/nist-800-53/index.md +0 -58
- package/skills/spec-security-analysis/references/owasp-asvs/V1-Architecture.md +0 -33
- package/skills/spec-security-analysis/references/owasp-asvs/V10-MaliciousCode.md +0 -33
- package/skills/spec-security-analysis/references/owasp-asvs/V11-BusinessLogic.md +0 -32
- package/skills/spec-security-analysis/references/owasp-asvs/V12-Files.md +0 -34
- package/skills/spec-security-analysis/references/owasp-asvs/V13-API.md +0 -34
- package/skills/spec-security-analysis/references/owasp-asvs/V14-Configuration.md +0 -35
- package/skills/spec-security-analysis/references/owasp-asvs/V2-Authentication.md +0 -36
- package/skills/spec-security-analysis/references/owasp-asvs/V3-SessionManagement.md +0 -35
- package/skills/spec-security-analysis/references/owasp-asvs/V4-AccessControl.md +0 -39
- package/skills/spec-security-analysis/references/owasp-asvs/V5-Validation.md +0 -37
- package/skills/spec-security-analysis/references/owasp-asvs/V6-Cryptography.md +0 -34
- package/skills/spec-security-analysis/references/owasp-asvs/V7-ErrorLogging.md +0 -37
- package/skills/spec-security-analysis/references/owasp-asvs/V8-DataProtection.md +0 -34
- package/skills/spec-security-analysis/references/owasp-asvs/V9-Communication.md +0 -32
- package/skills/spec-security-analysis/references/owasp-asvs/index.md +0 -59
- package/skills/spec-security-analysis/references/soc2/CC1-ControlEnvironment.md +0 -31
- package/skills/spec-security-analysis/references/soc2/CC2-CommunicationInformation.md +0 -27
- package/skills/spec-security-analysis/references/soc2/CC3-RiskAssessment.md +0 -29
- package/skills/spec-security-analysis/references/soc2/CC4-MonitoringActivities.md +0 -27
- package/skills/spec-security-analysis/references/soc2/CC5-ControlActivities.md +0 -28
- package/skills/spec-security-analysis/references/soc2/CC6-LogicalPhysicalAccess.md +0 -45
- package/skills/spec-security-analysis/references/soc2/CC7-SystemOperations.md +0 -42
- package/skills/spec-security-analysis/references/soc2/CC8-ChangeManagement.md +0 -32
- package/skills/spec-security-analysis/references/soc2/CC9-RiskMitigation.md +0 -34
- package/skills/spec-security-analysis/references/soc2/index.md +0 -46
- package/skills/spec-security-analysis/references/standards-index.md +0 -46
- package/skills/spec-to-plan/SKILL.md +0 -88
- package/skills/spec-to-plan/references/step-0-plan-selection.md +0 -121
- package/skills/spec-to-plan/references/step-1-analysis.md +0 -88
- package/skills/spec-to-plan/references/step-2-test-plan.md +0 -43
- package/skills/spec-to-plan/references/step-3-execution-plan.md +0 -218
- package/skills/spec-to-plan/workflow-assets/dist/index.d.ts +0 -146
- package/skills/spec-to-plan/workflow-assets/dist/index.d.ts.map +0 -1
- package/skills/spec-to-plan/workflow-assets/dist/index.js +0 -7525
- package/skills/spec-to-plan/workflow-assets/dist/invariants.d.ts +0 -6
- package/skills/spec-to-plan/workflow-assets/dist/invariants.d.ts.map +0 -1
- package/skills/spec-to-plan/workflow-assets/skills/to-plan/SKILL.md +0 -35
- package/skills/spec-to-plan/workflow-assets/skills/to-plan/scripts/invariants.js +0 -1
- package/skills/spec-to-plan/workflow-assets/skills/to-plan/templates/implementation-plan/default.md +0 -44
- package/skills/spec-to-plan/workflow-assets/skills/to-plan/workflows/to-plan/def.yaml +0 -85
- package/skills/specify/SKILL.md +0 -154
- package/skills/specify/assets/app-spec-template.md +0 -143
- package/skills/specify/assets/spec-template.md +0 -299
- package/skills/specify/references/integration-tests.md +0 -72
- package/skills/specify/references/us-to-fr.md +0 -40
- package/skills/specify/references/writing-good-requirements.md +0 -61
|
@@ -1,102 +0,0 @@
|
|
|
1
|
-
# Step 7: Report and Handoff
|
|
2
|
-
|
|
3
|
-
**Goal**: close the loop — the matrix knows about the new tests, and `gap-analysis` can
|
|
4
|
-
reconcile every tag this run emitted.
|
|
5
|
-
|
|
6
|
-
## The run report
|
|
7
|
-
|
|
8
|
-
The `## Census` section of the review artifact (step 6), and the same counts to the user.
|
|
9
|
-
Counts only:
|
|
10
|
-
|
|
11
|
-
```
|
|
12
|
-
spec-correctness — <repo> — <YYYY-MM-DD>
|
|
13
|
-
quire-cli <version> · harness <name> · <N> criteria
|
|
14
|
-
|
|
15
|
-
emitted 37 extractable, grounded, no finding
|
|
16
|
-
emitted + finding 22 candidate 0 · second-pass 18 · downgraded 1 · dep-missing 3
|
|
17
|
-
not settled 14 symbol-not-found 6 · oracle-is-adjectival 5 · unimplemented 3
|
|
18
|
-
already covered 9 hand-written tests already carry the row_id
|
|
19
|
-
witnesses 5 Unit tests, not property coverage
|
|
20
|
-
```
|
|
21
|
-
|
|
22
|
-
`emitted + emitted-with-finding + not-settled + already-covered` must equal the number of
|
|
23
|
-
records with a `row_id`. If it does not, a record was dropped — find it before reporting.
|
|
24
|
-
|
|
25
|
-
No thresholds, no grades, no rewording suggestions. Same rule as step 1.
|
|
26
|
-
|
|
27
|
-
## Handoff to `spec-matrix`
|
|
28
|
-
|
|
29
|
-
Emit rows for the `spec-matrix` Test Case Summary — do not write them yourself if the repo
|
|
30
|
-
already runs the matrix workflow; hand them over.
|
|
31
|
-
|
|
32
|
-
`Test ID | Title | Type | Priority | Traces To | Status`
|
|
33
|
-
|
|
34
|
-
- `Type` — `Property` for the 8 generatable families; `Unit` for witnesses, whether they
|
|
35
|
-
came from the second pass or from a `singleton-domain` grounding result.
|
|
36
|
-
The vocabulary is owned by `spec_artifacts_process/manifest.yaml`, not by this skill; if
|
|
37
|
-
it disagrees with what you write, the manifest wins.
|
|
38
|
-
- `Traces To` — the `row_id`, exactly (`FR-027-AC-1`). Never a range you invented, never
|
|
39
|
-
another TC.
|
|
40
|
-
- `Status` — `✅` only for a test that actually passed in this run. A criterion with no
|
|
41
|
-
test gets **no row**; it is a finding in the review artifact, not a claim in the matrix.
|
|
42
|
-
|
|
43
|
-
## Binding check
|
|
44
|
-
|
|
45
|
-
Before finishing, prove every emitted tag actually **binds** — not that it exists.
|
|
46
|
-
|
|
47
|
-
```
|
|
48
|
-
quire coverage --scope <repo> --json
|
|
49
|
-
```
|
|
50
|
-
|
|
51
|
-
`--scope` is the repository root. Since quire-cli v0.16.0 (quire-rs CR-045) the command
|
|
52
|
-
derives two roots from it: documents from `<repo>/spec` only, trace tags from the source
|
|
53
|
-
tree excluding `spec/`. A repo with no `spec/` directory exits with a diagnostic naming
|
|
54
|
-
the missing document root, and a matrix outside `spec/` mints nothing.
|
|
55
|
-
|
|
56
|
-
For each `row_id` this run emitted, confirm the id appears among the backed ids: its
|
|
57
|
-
minting document's group must count it, and it must not appear in `untracked_symbols`.
|
|
58
|
-
|
|
59
|
-
```
|
|
60
|
-
quire coverage --scope <repo> --json \
|
|
61
|
-
| jq -r '.untracked_symbols[] | "\(.trace_id)\t\(.path)\t\(.symbol)"'
|
|
62
|
-
```
|
|
63
|
-
|
|
64
|
-
An emitted `row_id` that is *not* backed means the tag is in the file but attached to no
|
|
65
|
-
test symbol — almost always TypeScript placement, a tag above `describe(` instead of above
|
|
66
|
-
`it(` (step 4). Fix the placement and re-run; do not report the criterion as covered.
|
|
67
|
-
|
|
68
|
-
**This check replaces a grep, deliberately.** The previous version of this step confirmed
|
|
69
|
-
the tags were greppable, and a grep matches a comment wherever it sits. Six generated files
|
|
70
|
-
passed that check with every tag bound to nothing (agent-ix/quoin#61). Only the engine that
|
|
71
|
-
consumes the tags can tell you a tag works.
|
|
72
|
-
|
|
73
|
-
Then confirm, as before:
|
|
74
|
-
|
|
75
|
-
- no matrix row this run added is `✅` while its test is skipped;
|
|
76
|
-
- no emitted tag names a `row_id` absent from the `quire properties` output.
|
|
77
|
-
|
|
78
|
-
Check `quire --version` ≥ 0.16.0 first: the two-root semantics this step assumes are
|
|
79
|
-
unenforced, and an older build silently walks the whole repository instead.
|
|
80
|
-
|
|
81
|
-
Two distinct states get conflated here; keep them apart (they have different causes and
|
|
82
|
-
different fixes — `gap-analysis` step 3 has the same reading):
|
|
83
|
-
|
|
84
|
-
- **A zero denominator.** Under the `--json` invocation this step prescribes the signal is
|
|
85
|
-
`"totals": {"total": 0}`. `no rows matched` is a **human-format-only** marker and never
|
|
86
|
-
appears in the JSON, so do not look for it there. It means the declared model matched
|
|
87
|
-
nothing in this scope — no minting document was found. Not full coverage, not a clean
|
|
88
|
-
run: report it as **no data**.
|
|
89
|
-
- **No model at all.** `quire coverage` exits **non-zero** with a distinct diagnostic when
|
|
90
|
-
no active module declares a `traceability:` model (quire-rs FR-050-AC-9). That is an
|
|
91
|
-
environment gap — the module set, not the repo's rows.
|
|
92
|
-
|
|
93
|
-
Say which one happened rather than reporting the run as reconciled.
|
|
94
|
-
|
|
95
|
-
A mismatch here is a bug in this run, not in `gap-analysis`.
|
|
96
|
-
|
|
97
|
-
## Finish by saying
|
|
98
|
-
|
|
99
|
-
- What now has tests, in concrete terms: which FRs, how many criteria.
|
|
100
|
-
- How many findings are waiting and roughly how long reading them would take.
|
|
101
|
-
- The one next action — usually "read `reviews/<date>-<slug>.md`" or "add `<lib>` to
|
|
102
|
-
dev-dependencies, then re-run to emit the tests it blocked".
|
|
@@ -1,90 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-dependency-analysis
|
|
3
|
-
description: Analyze dependencies and separate enablement from feature work.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Dependency & Ordering Analysis
|
|
7
|
-
|
|
8
|
-
Identify prerequisite relationships between requirements so work can be sequenced. The deliverable is a directed acyclic graph (DAG) of FRs/StRs/NFRs in **logical order**, not a schedule.
|
|
9
|
-
|
|
10
|
-
## When to use
|
|
11
|
-
|
|
12
|
-
- Before `spec-to-plan` — `spec-to-plan` consumes the DAG.
|
|
13
|
-
- After all FRs have been written and reviewed.
|
|
14
|
-
- Whenever new FRs are added that may unblock or block existing work.
|
|
15
|
-
|
|
16
|
-
## Process
|
|
17
|
-
|
|
18
|
-
1. **Identify prerequisite edges.** For each FR/StR/NFR, list every other requirement that MUST be satisfied before this one can be implemented. Express each as `A → B` (A is prerequisite to B).
|
|
19
|
-
|
|
20
|
-
2. **Classify each requirement.**
|
|
21
|
-
- **Enablement** — frameworks, abstractions, scaffolding, schema/migration, shared libs. Has no business-visible behavior on its own.
|
|
22
|
-
- **Feature** — business or user-visible behavior.
|
|
23
|
-
|
|
24
|
-
**Rule**: Enablement requirements MUST be tasked before any feature that depends on them.
|
|
25
|
-
|
|
26
|
-
3. **Verify acyclicity.** If any cycle is found, the spec is malformed — break the cycle by introducing a separation FR or merging the cyclic requirements.
|
|
27
|
-
|
|
28
|
-
4. **Produce the deliverable.** Use the template below.
|
|
29
|
-
|
|
30
|
-
## Deliverable template
|
|
31
|
-
|
|
32
|
-
Record output in `spec/analysis/dependency.md` (or as a section in `spec/spec.md` § 7 if your project keeps analysis inline).
|
|
33
|
-
|
|
34
|
-
```markdown
|
|
35
|
-
# Dependency Analysis
|
|
36
|
-
|
|
37
|
-
## Classification
|
|
38
|
-
|
|
39
|
-
| Requirement | Class | Rationale |
|
|
40
|
-
|-------------|-------|-----------|
|
|
41
|
-
| FR-001 | Enablement | Defines the auth middleware all feature FRs use |
|
|
42
|
-
| FR-002 | Enablement | Database schema for user records |
|
|
43
|
-
| FR-003 | Feature | Login flow — depends on FR-001, FR-002 |
|
|
44
|
-
| FR-004 | Feature | Password reset — depends on FR-001, FR-002 |
|
|
45
|
-
|
|
46
|
-
## Dependency Graph
|
|
47
|
-
|
|
48
|
-
```mermaid
|
|
49
|
-
graph TD
|
|
50
|
-
FR-001[FR-001: Auth middleware]
|
|
51
|
-
FR-002[FR-002: User schema]
|
|
52
|
-
FR-003[FR-003: Login flow]
|
|
53
|
-
FR-004[FR-004: Password reset]
|
|
54
|
-
FR-001 --> FR-003
|
|
55
|
-
FR-002 --> FR-003
|
|
56
|
-
FR-001 --> FR-004
|
|
57
|
-
FR-002 --> FR-004
|
|
58
|
-
```
|
|
59
|
-
|
|
60
|
-
## Topological Order (suggested implementation sequence)
|
|
61
|
-
|
|
62
|
-
1. FR-001, FR-002 (enablement, parallelizable)
|
|
63
|
-
2. FR-003, FR-004 (features, parallelizable after enablement)
|
|
64
|
-
|
|
65
|
-
## Cycles
|
|
66
|
-
|
|
67
|
-
None detected.
|
|
68
|
-
```
|
|
69
|
-
|
|
70
|
-
## Acceptance Criteria
|
|
71
|
-
|
|
72
|
-
- Every FR/StR/NFR appears in the classification table exactly once.
|
|
73
|
-
- Every edge in the graph corresponds to an explicit prerequisite — no "soft" dependencies.
|
|
74
|
-
- No cycles.
|
|
75
|
-
- Topological order respects: all enablement before any feature that depends on it.
|
|
76
|
-
|
|
77
|
-
## Output contract
|
|
78
|
-
|
|
79
|
-
This skill emits one **`SpecReview`** under `reviews/YY-MM-DD-<slug>.md` with
|
|
80
|
-
`analysis: dependency` in its frontmatter.
|
|
81
|
-
|
|
82
|
-
Stated here because nothing checked it. The module declares an `analysis`
|
|
83
|
-
vocabulary of eleven values; five of them named a skill that never said it
|
|
84
|
-
emitted under them, so a skill and its declared output were unlinked and drift
|
|
85
|
-
between the two was invisible. `tests/skill-contracts.test.ts` now asserts the
|
|
86
|
-
pairing in both directions.
|
|
87
|
-
|
|
88
|
-
The document must carry a `## Summary` and a `## Findings` table — the two
|
|
89
|
-
sections `SpecReview`'s `body_extraction` requires — and must pass
|
|
90
|
-
`quire validate`.
|
|
@@ -1,102 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-ears-analysis
|
|
3
|
-
description: Analyze requirement statements (FR/NFR/StR) for EARS requirement-grammar conformance and author a SpecReview of the findings.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# EARS Requirement-Grammar Analysis
|
|
7
|
-
|
|
8
|
-
This skill analyzes the natural-language **requirement statements** in a spec
|
|
9
|
-
(FR Description/Behavior/Constraints, NFR Statement, StR Stakeholder Need)
|
|
10
|
-
against **EARS** (Easy Approach to Requirements Syntax), and authors one
|
|
11
|
-
`SpecReview` document recording the findings.
|
|
12
|
-
|
|
13
|
-
It pairs the **deterministic engine check** (quire-rs FR-042, the `iso-spec-core`
|
|
14
|
-
grammar) with the **semantic judgment the engine cannot make** — together they
|
|
15
|
-
form the lens.
|
|
16
|
-
|
|
17
|
-
## Process
|
|
18
|
-
|
|
19
|
-
1. **Run the engine check.** From the repo root:
|
|
20
|
-
|
|
21
|
-
```bash
|
|
22
|
-
quire validate --scope . "spec/**/*.md" --summary
|
|
23
|
-
```
|
|
24
|
-
|
|
25
|
-
> **`--scope` is the repository root, and must be passed explicitly.** Since quire-cli
|
|
26
|
-
> v0.16.0 (quire-rs CR-045) the command derives **two roots** from it and never
|
|
27
|
-
> interchanges them: spec documents are read from `<repo>/spec` only, trace tags from
|
|
28
|
-
> the source tree at `<repo>` excluding `spec/`. A repo with no `spec/` exits with a
|
|
29
|
-
> diagnostic naming the missing document root rather than scanning the whole tree, and a
|
|
30
|
-
> matrix outside `spec/` (a fixture, a `plan/` copy) mints nothing. A relative glob
|
|
31
|
-
> resolves under `--scope` only in scoped mode (no `--module`); with `--module` it
|
|
32
|
-
> resolves against the process working directory, and an omitted `--scope` defaults to
|
|
33
|
-
> `.` — so a run launched from a parent directory validates the **wrong tree** and exits
|
|
34
|
-
> 0 for whatever it matched. Check `quire --version` ≥ 0.16.0 before relying on any of
|
|
35
|
-
> this; ≤ 0.15.0 has the pre-split traversal semantics.
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
Read the `[ears:<check>]` warnings and the `GrammarSummary` line. The engine
|
|
39
|
-
flags, per statement:
|
|
40
|
-
- `non-singular` — more than one `shall` (can't map cleanly to one AC).
|
|
41
|
-
- `vague-response` — `support`/`handle`/`manage`/`process`/`provide`/
|
|
42
|
-
`enable`/`be able to` (unverifiable).
|
|
43
|
-
- `missing-subject` — no named system/actor before `shall`.
|
|
44
|
-
- `non-canonical-trigger` — `On …`/`Upon`/`After`/`During` instead of
|
|
45
|
-
`When …`/`While …`.
|
|
46
|
-
- `unclassifiable` — has `shall` but matches no EARS pattern.
|
|
47
|
-
|
|
48
|
-
These are advisory (they never fail `quire validate`); this lens records
|
|
49
|
-
them as review findings.
|
|
50
|
-
|
|
51
|
-
2. **Add the semantic judgment** (what the engine cannot check deterministically):
|
|
52
|
-
- **Keyword-vs-intent** — does a `When …` statement describe a momentary
|
|
53
|
-
*event*, or is it really a continuous `While …` *state* (or vice-versa)?
|
|
54
|
-
- **Genuinely concrete response** — a statement can pass the vague-verb
|
|
55
|
-
lexicon yet still be unmeasurable ("shall be fast", "shall be robust").
|
|
56
|
-
- **Right pattern for the obligation** — an unwanted condition stated as
|
|
57
|
-
`When …` instead of `If … then …`.
|
|
58
|
-
|
|
59
|
-
3. **Author the SpecReview.** Fetch the template once:
|
|
60
|
-
|
|
61
|
-
```bash
|
|
62
|
-
quoin write --types SpecReview
|
|
63
|
-
```
|
|
64
|
-
|
|
65
|
-
Write one document to `spec/reviews/ears-conformance.md` with
|
|
66
|
-
`analysis: ears-conformance` in the frontmatter, a `## Summary` (one or two
|
|
67
|
-
sentences: how many statements, how many clean, the dominant defect), and a
|
|
68
|
-
validated `## Findings` table:
|
|
69
|
-
|
|
70
|
-
| ID | Severity | Summary | Refs |
|
|
71
|
-
| --- | --- | --- | --- |
|
|
72
|
-
| FND-001 | medium | FR-001 Description packs two `shall` into one statement — split into atomic requirements | FR-001 |
|
|
73
|
-
| FND-002 | low | FR-003 leads with `On startup, …`; use `When the service starts, …` | FR-003 |
|
|
74
|
-
|
|
75
|
-
- `Severity` ∈ `low`/`medium`/`high`. Suggested mapping: `non-singular`
|
|
76
|
-
and `missing-subject` → **medium** (they degrade traceability);
|
|
77
|
-
`vague-response`/`unclassifiable` → **medium** when the response is truly
|
|
78
|
-
unverifiable, else **low**; `non-canonical-trigger` → **low** (cosmetic).
|
|
79
|
-
Raise to **high** any statement whose ambiguity changes what gets built.
|
|
80
|
-
- `Refs` names the offending FR/NFR/StR id.
|
|
81
|
-
- Combine the engine findings with your step-2 semantic findings into one
|
|
82
|
-
table; attribute each row to its statement.
|
|
83
|
-
|
|
84
|
-
4. **Validate + record.**
|
|
85
|
-
|
|
86
|
-
```bash
|
|
87
|
-
quire validate --scope . "spec/reviews/ears-conformance.md"
|
|
88
|
-
```
|
|
89
|
-
|
|
90
|
-
Fix any structural errors in the review doc. The doc syncs into filament-core
|
|
91
|
-
as a `SpecReview` artifact like every other analysis lens.
|
|
92
|
-
|
|
93
|
-
## Notes
|
|
94
|
-
|
|
95
|
-
- Scope is **requirement-bearing** artifacts only: FR, NFR, StR. US stories
|
|
96
|
-
(`As a / I want / So that`) and tests are out of scope.
|
|
97
|
-
- This lens is advisory by default. To make EARS a **gate** for a converted
|
|
98
|
-
repo, run `quire validate --strict` in that repo's CI — `--strict` escalates
|
|
99
|
-
the EARS warnings to a failing exit.
|
|
100
|
-
- Per-archetype dialects the engine already applies (don't re-flag them): an
|
|
101
|
-
enumerated `The X SHALL:` + numbered list is one statement; StR may use a
|
|
102
|
-
stakeholder subject; an NFR with no trigger is fine.
|
|
@@ -1,156 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-evidence-analysis
|
|
3
|
-
description: Recommend verification methods per obligation from the declared catalog, and flag mismatches with what was authored.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Verification & Evidence Strategy
|
|
7
|
-
|
|
8
|
-
Every requirement needs a defined verification method and a concrete artifact
|
|
9
|
-
that proves it was verified. This skill recommends the method **from the
|
|
10
|
-
declared catalog**, and flags where the authored choice disagrees.
|
|
11
|
-
|
|
12
|
-
> **This skill no longer carries its own method table.** It used to: a
|
|
13
|
-
> skill-local list of `test | analysis | inspection | demonstration` plus a few
|
|
14
|
-
> evidence kinds, declared in no manifest and read by no code. The result was
|
|
15
|
-
> `Verification` columns defaulting to `Test` by habit, with nothing ever
|
|
16
|
-
> advising DAST for an attack surface, monitors for a temporal property, or
|
|
17
|
-
> fault injection for a reliability NFR. The methods now live in module data
|
|
18
|
-
> (quire-rs FR-054, `spec-artifacts-process` FR-007) and are read from there.
|
|
19
|
-
|
|
20
|
-
## When to use
|
|
21
|
-
|
|
22
|
-
- At **Spec Review**, to confirm each obligation's method before the matrix is built.
|
|
23
|
-
- At **Matrix** time, to plan which suites the chosen methods imply.
|
|
24
|
-
- Whenever a new NFR is added — NFRs are the ones most prone to a defaulted method.
|
|
25
|
-
|
|
26
|
-
## Run the advisor, do not recall the table
|
|
27
|
-
|
|
28
|
-
```bash
|
|
29
|
-
quoin advise # every obligation, with its recommendations
|
|
30
|
-
quoin advise --mismatch-only # only where the authored method disagrees
|
|
31
|
-
quoin advise --inconclusive-only # only where no rule matched — your work list
|
|
32
|
-
quoin advise --json # for scripting
|
|
33
|
-
```
|
|
34
|
-
|
|
35
|
-
`quoin advise` derives the obligations from `quire coverage --json`, reads each
|
|
36
|
-
criterion's FR-052 property shape from `quire properties --json`, and matches
|
|
37
|
-
both against the catalog's `applicability` rules. **This is the deterministic
|
|
38
|
-
half of the analysis and it is not optional** — a method you recalled is a
|
|
39
|
-
method nobody can check.
|
|
40
|
-
|
|
41
|
-
The catalog behind it:
|
|
42
|
-
|
|
43
|
-
```bash
|
|
44
|
-
quoin catalog methods # human-readable, grouped by class
|
|
45
|
-
quoin catalog methods --json # the merged catalog, for scripting
|
|
46
|
-
quoin catalog methods --class Analysis
|
|
47
|
-
```
|
|
48
|
-
|
|
49
|
-
Merged first-wins across active modules, exactly as quire-rs merges it — so the
|
|
50
|
-
method you are advised is the method the auditor will later check conformance
|
|
51
|
-
against.
|
|
52
|
-
|
|
53
|
-
## Process
|
|
54
|
-
|
|
55
|
-
1. **Run `quoin advise`.** It carries the obligations (quire-rs FR-053: id,
|
|
56
|
-
statement, hash, authored method, criticality) *and* the recommendations.
|
|
57
|
-
Do not restate either by hand.
|
|
58
|
-
|
|
59
|
-
2. **Take the deterministic recommendations first.** They come from the
|
|
60
|
-
catalog's `applicability` rules matched against facts about the obligation:
|
|
61
|
-
its statement's characteristics, its FR-052 property shape, its archetype,
|
|
62
|
-
its declared criticality, and what the evidence store already records.
|
|
63
|
-
Rules match or they do not. Each recommendation names the rule and the value
|
|
64
|
-
that matched, so you can check the reasoning rather than trust it.
|
|
65
|
-
|
|
66
|
-
**Read what matched, not just what was recommended.** A recommendation
|
|
67
|
-
matched *only* on an evidence characteristic is telling you about the tests,
|
|
68
|
-
not about the requirement — see below.
|
|
69
|
-
|
|
70
|
-
3. **Judge only the residue, and label it.** Where the rules are inconclusive
|
|
71
|
-
the advisor says so and stops rather than guessing. That is where your
|
|
72
|
-
judgement belongs — and it must be recorded *as* judgement. Never present an
|
|
73
|
-
LLM conclusion as a verdict (the ADR-0010 discipline).
|
|
74
|
-
|
|
75
|
-
4. **Confirm or correct the authored method.** A mismatch (`⚠` in the human
|
|
76
|
-
output, `mismatch: true` in JSON) is advisory: the human decides. The confirmed method lands in the spec, becomes the
|
|
77
|
-
obligation's method, and is what `quoin evidence` records discharge against.
|
|
78
|
-
|
|
79
|
-
5. **Plan the suite.** A method implies an evidence kind; a suite in
|
|
80
|
-
`spec/evidence/suites.md` produces that kind. A recommended method with no
|
|
81
|
-
suite that can produce its evidence is a gap in the plan, not a gap in the
|
|
82
|
-
spec.
|
|
83
|
-
|
|
84
|
-
## Recommendations that come from the evidence, not from the requirement
|
|
85
|
-
|
|
86
|
-
`quoin advise` reads the evidence store. Two characteristics come from there
|
|
87
|
-
rather than from the statement, and they mean something different from the rest.
|
|
88
|
-
|
|
89
|
-
| Matched value | What it says |
|
|
90
|
-
|---|---|
|
|
91
|
-
| `fault-detection-unmeasured` | the obligation **is** exercised by a bound run, and nothing measures whether that exercise would catch a fault |
|
|
92
|
-
| `fault-detection-failed` | something **did** measure it, and a seeded fault survived |
|
|
93
|
-
|
|
94
|
-
**Both mean "escalate the existing suite", not "the requirement is unverified".**
|
|
95
|
-
An obligation nothing is bound to is `undischarged`, which the auditor reports
|
|
96
|
-
separately — and neither of these mints for it, deliberately, because
|
|
97
|
-
recommending a solver for code nobody has tested yet is advice nobody can act
|
|
98
|
-
on.
|
|
99
|
-
|
|
100
|
-
So when the only reason a method was recommended is one of these two, the
|
|
101
|
-
finding you write is about the tests. "This is tested and nothing says the tests
|
|
102
|
-
discriminate" is a different sentence from "this requirement has no method", and
|
|
103
|
-
they lead to different work.
|
|
104
|
-
|
|
105
|
-
## Cost is not in the catalog yet, so it has to be here
|
|
106
|
-
|
|
107
|
-
The advisor ranks by **how many rules matched**. It has no way to say what a
|
|
108
|
-
method costs, so an escalation of last resort ties with a unit test and the
|
|
109
|
-
output gives no hint. Filed as `agent-ix/quire-rs#190`; until it lands, this
|
|
110
|
-
paragraph is the only place the ordering is written down.
|
|
111
|
-
|
|
112
|
-
**`concolic-execution` is the case to watch.** Concrete + symbolic execution
|
|
113
|
-
runs the code while recording the constraints on each branch, then negates one
|
|
114
|
-
and asks a solver for an input that flips it — `if x * 3 == 51` is a
|
|
115
|
-
1-in-4-billion coin flip for a fuzzer and one line of algebra for a solver. It
|
|
116
|
-
also path-explodes and is slow. **Nobody reaches for it first.** The industrial
|
|
117
|
-
pattern is hybrid fuzzing: fuzz until the coverage curve flattens, then hand the
|
|
118
|
-
stuck branches to a solver (Driller, QSYM, SymCC).
|
|
119
|
-
|
|
120
|
-
When it is recommended alongside a cheaper method keyed on the same evidence —
|
|
121
|
-
`mutation-testing` on `fault-detection-unmeasured`, for instance — **take the
|
|
122
|
-
cheaper one first.** Measuring is what tells you whether the escalation is
|
|
123
|
-
warranted.
|
|
124
|
-
|
|
125
|
-
This is the skill-local-prose arrangement ADR-0011 moved away from, and it is
|
|
126
|
-
recorded as a debt rather than a design. When `quire-rs#190` lands, this section
|
|
127
|
-
should shrink to a pointer at the catalog.
|
|
128
|
-
|
|
129
|
-
## What "inconclusive" means, and why it is not a failure
|
|
130
|
-
|
|
131
|
-
An obligation the rules cannot place is a normal outcome — the catalog's
|
|
132
|
-
applicability rules are deliberately narrow, because a rule that matches
|
|
133
|
-
everything advises nothing. Report it as inconclusive and choose a method
|
|
134
|
-
yourself. **Do not default to `Test` to make the report look complete**: that is
|
|
135
|
-
precisely the habit this skill was rebuilt to end.
|
|
136
|
-
|
|
137
|
-
## Deliverable
|
|
138
|
-
|
|
139
|
-
A `SpecReview` with `analysis: evidence`, under `reviews/YY-MM-DD-<slug>.md`.
|
|
140
|
-
|
|
141
|
-
The `Findings` table carries one row per obligation whose method needs
|
|
142
|
-
attention — a mismatch, or an inconclusive recommendation the author must
|
|
143
|
-
settle. An obligation whose authored method matches the recommendation needs no
|
|
144
|
-
row; a review listing every passing obligation is a review nobody reads to the
|
|
145
|
-
end.
|
|
146
|
-
|
|
147
|
-
```markdown
|
|
148
|
-
| ID | Severity | Summary | Refs |
|
|
149
|
-
|----|----------|---------|------|
|
|
150
|
-
| FND-001 | medium | NFR-009-AC-1 is authored `Inspection`; the statement's `reliability` characteristic recommends `fault-injection` (Test). | NFR-009-AC-1 |
|
|
151
|
-
| FND-002 | low | FR-001-AC-9 matched no applicability rule; method chosen by judgement, not by the catalog. | FR-001-AC-9 |
|
|
152
|
-
```
|
|
153
|
-
|
|
154
|
-
Record the per-requirement outcome in the requirement's own `Verification`
|
|
155
|
-
cell — that cell **is** the obligation's method (quire-rs FR-053), so editing it
|
|
156
|
-
is what changes the plan. There is no separate evidence file to keep in sync.
|
|
@@ -1,59 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-failure-domain-analysis
|
|
3
|
-
description: Identify unstated failure modes, identity confusion, purity gaps, and topological edge cases in ISO-style specifications.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Spec Failure Domain Analysis
|
|
7
|
-
|
|
8
|
-
Run this skill during spec review to catch common omissions before implementation.
|
|
9
|
-
|
|
10
|
-
## When to Use
|
|
11
|
-
- After drafting FR/NFR/StR requirements
|
|
12
|
-
- Before `spec-to-plan` (part of its readiness gate)
|
|
13
|
-
- During peer review of specifications
|
|
14
|
-
|
|
15
|
-
## Checklist
|
|
16
|
-
|
|
17
|
-
### 1. Extension Points (Trust Boundaries)
|
|
18
|
-
For each callback, hook, observer, or plugin interface:
|
|
19
|
-
- [ ] Is failure behavior defined? Options:
|
|
20
|
-
- **Strict**: Failure aborts operation (data integrity)
|
|
21
|
-
- **Resilient**: Failure is logged/suppressed (availability)
|
|
22
|
-
- **Configurable**: User chooses policy
|
|
23
|
-
|
|
24
|
-
### 2. Entity Identity
|
|
25
|
-
For each core domain entity (State, Event, User, etc.):
|
|
26
|
-
- [ ] Is the uniqueness key explicit?
|
|
27
|
-
- Bad: "A set of states"
|
|
28
|
-
- Good: "States unique by `name` property"
|
|
29
|
-
|
|
30
|
-
### 3. Evaluation Purity
|
|
31
|
-
For each user-supplied logic (guards, filters, validators):
|
|
32
|
-
- [ ] Are side-effects constrained?
|
|
33
|
-
- Document if read-only is required for simulation/reasoning
|
|
34
|
-
|
|
35
|
-
### 4. Topological Robustness
|
|
36
|
-
For each graph/tree algorithm (search, path-finding):
|
|
37
|
-
- [ ] Is termination guaranteed on cycles?
|
|
38
|
-
- [ ] Are worst-case structures considered? (deep nesting, disconnected nodes)
|
|
39
|
-
|
|
40
|
-
## Output
|
|
41
|
-
Document any missing constraints as proposed additions:
|
|
42
|
-
- **NFR**: Non-functional (resilience, performance)
|
|
43
|
-
- **StR**: Structural (integrity, purity)
|
|
44
|
-
- **FR**: Functional (if behavior is undefined)
|
|
45
|
-
|
|
46
|
-
## Output contract
|
|
47
|
-
|
|
48
|
-
This skill emits one **`SpecReview`** under `reviews/YY-MM-DD-<slug>.md` with
|
|
49
|
-
`analysis: failure-domain` in its frontmatter.
|
|
50
|
-
|
|
51
|
-
Stated here because nothing checked it. The module declares an `analysis`
|
|
52
|
-
vocabulary of eleven values; five of them named a skill that never said it
|
|
53
|
-
emitted under them, so a skill and its declared output were unlinked and drift
|
|
54
|
-
between the two was invisible. `tests/skill-contracts.test.ts` now asserts the
|
|
55
|
-
pairing in both directions.
|
|
56
|
-
|
|
57
|
-
The document must carry a `## Summary` and a `## Findings` table — the two
|
|
58
|
-
sections `SpecReview`'s `body_extraction` requires — and must pass
|
|
59
|
-
`quire validate`.
|
|
@@ -1,133 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: spec-fuzz
|
|
3
|
-
description: >-
|
|
4
|
-
Turn Fuzz-kind obligations into runnable fuzz targets. Consumes `quoin advise --json`,
|
|
5
|
-
selects the obligations whose verification method carries `evidence_kind: Fuzz`, grounds
|
|
6
|
-
each one's entry-point symbol in the repository's source, and emits targets in the repo's
|
|
7
|
-
own harness (cargo-fuzz / atheris / fast-check) keyed on the obligation id. Writes nothing
|
|
8
|
-
where the tooling is absent or the entry point cannot be grounded — a finding instead.
|
|
9
|
-
Emits a validated SpecReview recording every obligation it could not serve.
|
|
10
|
-
---
|
|
11
|
-
|
|
12
|
-
# Spec Fuzz
|
|
13
|
-
|
|
14
|
-
Use this skill to **generate fuzz targets from robustness requirements you already wrote**.
|
|
15
|
-
|
|
16
|
-
*"Never panic on arbitrary input"* and *"reject malformed frontmatter"* are property-shaped
|
|
17
|
-
over an input surface. `spec-correctness` generates example and property tests, not fuzz
|
|
18
|
-
targets, so a consumer that parses anything gets nothing from its spec toward a harness —
|
|
19
|
-
the method can be advised from the catalog and materializing it is entirely manual.
|
|
20
|
-
|
|
21
|
-
Specified by [FR-038](../../spec/functional/FR-038-generate-fuzz-harnesses.md).
|
|
22
|
-
|
|
23
|
-
## The rule that is not negotiable
|
|
24
|
-
|
|
25
|
-
**Writing a target discharges nothing.**
|
|
26
|
-
|
|
27
|
-
This is where fuzz differs from every other generator in this family. A property test that
|
|
28
|
-
exists and passes is evidence. A fuzz target that exists has proved nothing — fuzzing is a
|
|
29
|
-
search, and an unrun target is a search never started.
|
|
30
|
-
|
|
31
|
-
The obligation is discharged by a **recorded run** (FR-030), in its own suite with
|
|
32
|
-
`Evidence Kind: Fuzz`. A generated target that has never run is precisely the
|
|
33
|
-
`vacuous-evidence` shape FR-034 exists to name. Report generated targets as **undischarged**,
|
|
34
|
-
always, and never imply otherwise in the handoff.
|
|
35
|
-
|
|
36
|
-
Three more:
|
|
37
|
-
|
|
38
|
-
- **Never install anything.** No `cargo install`, no dependency added, no fuzz workspace
|
|
39
|
-
scaffolded. Absent tooling is a finding. (CON-2.)
|
|
40
|
-
- **Never decide which methods are fuzz methods.** That is the catalog's, read at run time.
|
|
41
|
-
(CON-1.)
|
|
42
|
-
- **Never write a framework name into `spec/**`.** Inherited from FR-028-CON-2.
|
|
43
|
-
|
|
44
|
-
## When to use
|
|
45
|
-
|
|
46
|
-
- After `quoin advise` recommends `fuzzing` for an obligation and nothing implements it.
|
|
47
|
-
- On a repository that parses untrusted or structured input and has no fuzz suite.
|
|
48
|
-
- To extend an existing fuzz suite to surfaces the spec names and the suite misses.
|
|
49
|
-
|
|
50
|
-
Not for: authoring the requirement (`specify`), choosing the method (`quoin advise`), or
|
|
51
|
-
running the fuzzer. Running is the consumer's CI — quoin transcribes, it does not execute.
|
|
52
|
-
|
|
53
|
-
## When fuzzing stops being the answer
|
|
54
|
-
|
|
55
|
-
A fuzz campaign has a shape: coverage climbs, then flattens. **The plateau is
|
|
56
|
-
the documented signal to escalate**, not to fuzz harder. Random input cannot
|
|
57
|
-
satisfy a checksum, a CRC or a magic number — `if x * 3 == 51` is roughly a
|
|
58
|
-
1-in-4-billion coin flip for a fuzzer and one line of algebra for a solver.
|
|
59
|
-
|
|
60
|
-
The industrial pattern is **hybrid fuzzing**: fuzz until the curve flattens,
|
|
61
|
-
hand the stuck branches to a solver, feed the solved inputs back to the fuzzer
|
|
62
|
-
as fresh seeds. Driller (2016) did it with AFL + angr; QSYM, SymCC and Fuzzolic
|
|
63
|
-
followed.
|
|
64
|
-
|
|
65
|
-
The concrete hop in Rust:
|
|
66
|
-
|
|
67
|
-
```
|
|
68
|
-
cargo-fuzz ──plateau──▶ Kani bounded model checking over MIR (AWS)
|
|
69
|
-
haybale symbolic execution of LLVM IR, in Rust
|
|
70
|
-
```
|
|
71
|
-
|
|
72
|
-
`quoin advise` will point there on its own once the evidence says so — the
|
|
73
|
-
catalog keys `concolic-execution` on `fault-detection-unmeasured` (exercised,
|
|
74
|
-
and nothing measures whether the tests discriminate) and
|
|
75
|
-
`fault-detection-failed` (measured, and a seeded fault survived). Record the
|
|
76
|
-
fuzz and mutation runs and the recommendation follows.
|
|
77
|
-
|
|
78
|
-
**Do not escalate before that.** Concolic execution path-explodes and is slow;
|
|
79
|
-
it earns its cost only where the cheap search has demonstrably stalled. The
|
|
80
|
-
catalog cannot yet express that ordering (`agent-ix/quire-rs#190`), so it is
|
|
81
|
-
written here.
|
|
82
|
-
|
|
83
|
-
## Inputs
|
|
84
|
-
|
|
85
|
-
- The target repository.
|
|
86
|
-
- `quoin advise --repo <repo> --json` — obligations with their authored method and
|
|
87
|
-
recommendations.
|
|
88
|
-
- The active `verification_catalog` — which methods are Fuzz-kind, and the `tooling` each
|
|
89
|
-
names. **Read it; do not carry a list here.**
|
|
90
|
-
|
|
91
|
-
## Steps
|
|
92
|
-
|
|
93
|
-
0. **[Scope and harness](references/step-0-scope-and-harness.md)** — detect the repository's
|
|
94
|
-
language and fuzz tooling from its manifest. Absent tooling stops the run here, with
|
|
95
|
-
findings.
|
|
96
|
-
1. **[Select the obligations](references/step-1-select-obligations.md)** — those whose
|
|
97
|
-
method has `evidence_kind: Fuzz`, from the catalog rather than by name.
|
|
98
|
-
2. **[Ground the entry point](references/step-2-ground-entry-point.md)** — find the symbol
|
|
99
|
-
the target will call, in the source. Ungrounded means a finding, not a guess.
|
|
100
|
-
3. **[Emit the targets](references/step-3-emit-targets.md)** — harness-native, two trace
|
|
101
|
-
carriers, one provenance line.
|
|
102
|
-
4. **[Report](references/step-4-report.md)** — a validated `SpecReview` naming every
|
|
103
|
-
obligation not served and why, and the handoff that says the targets are undischarged.
|
|
104
|
-
|
|
105
|
-
## What "could not be served" looks like
|
|
106
|
-
|
|
107
|
-
Three distinct outcomes, and they are not interchangeable:
|
|
108
|
-
|
|
109
|
-
| Outcome | Meaning | What to write |
|
|
110
|
-
|---|---|---|
|
|
111
|
-
| **no tooling** | the repo has no fuzz harness | finding per obligation; **no files** |
|
|
112
|
-
| **ungrounded** | no entry-point symbol found in the source | finding naming the obligation; **no file for it** |
|
|
113
|
-
| **already covered** | an existing target already claims the id | nothing; record as covered |
|
|
114
|
-
|
|
115
|
-
Never collapse these into "skipped". The first is a decision for the repository owner, the
|
|
116
|
-
second is a gap in the spec or the code, and the third is success.
|
|
117
|
-
|
|
118
|
-
## Why there is no `quoin fuzz` command
|
|
119
|
-
|
|
120
|
-
The selection is mechanical and the emission is not. Choosing the entry point for
|
|
121
|
-
*"the parser SHALL NOT panic on arbitrary input"* means reading the parser, and a command
|
|
122
|
-
that guessed would produce targets that do not compile.
|
|
123
|
-
|
|
124
|
-
`quoin advise` supplies the mechanical half as JSON. This skill is the judgement half, and
|
|
125
|
-
it records which is which in the provenance line so a reviewer can tell them apart.
|
|
126
|
-
|
|
127
|
-
## Output contract
|
|
128
|
-
|
|
129
|
-
The `SpecReview` this skill emits carries `analysis: evidence` — the fuzz report records what a harness could and could not serve, which is an evidence claim.
|
|
130
|
-
|
|
131
|
-
Stated here because nothing checked it (quoin#202): a skill and its declared
|
|
132
|
-
output were unlinked, so drift between them was invisible until a document
|
|
133
|
-
failed validation in an unrelated session.
|