spec-controller 0.1.213 → 0.1.214
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/dist/cli.js +1 -1
- package/package.json +2 -2
package/dist/cli.js
CHANGED
|
@@ -28478,7 +28478,7 @@ var init_messages4 = __esm({
|
|
|
28478
28478
|
[CoreMessage.EvidenceReconciliationHeading]: "### Evidence reconciliation",
|
|
28479
28479
|
[CoreMessage.EvidenceReconciliationClaimReconciliationTerm]: "A Claim Reconciliation is one row of the ledger: one claim, reconciled in its Quality Check Reconciliations. A Quality Check Reconciliation reconciles the evidence of one kind of quality check within the claim: the claim's Evidence Obligation of that kind, when it has one, against its Evidence Observations of that kind. A claim is a scenario, a phantom claim (a code that evidence cites and no scenario carries, which the table below calls an unknown Scenario) or the unnamed claim (the one row for the evidence that no scenario or phantom claim takes).",
|
|
28480
28480
|
[CoreMessage.EvidenceReconciliationReconciliationLineTerm]: "A Reconciliation line is one line of a Quality Check Reconciliation, with its own outcome: each Evidence Observation it holds is one line, and its Evidence Obligation is one more when no Evidence Observation that ran answers it. A scenario with no Evidence Obligation, no Pending Item and no Evidence Observation still has one Quality Check Reconciliation, holding neither, and it is a single line. No line stands in for another: a scenario whose one Evidence Obligation two passing tests answer adds one to the Claim Reconciliation total and two to the Reconciliation line total.",
|
|
28481
|
-
[CoreMessage.EvidenceReconciliationEvidenceObligationTerm]:
|
|
28481
|
+
[CoreMessage.EvidenceReconciliationEvidenceObligationTerm]: `An Evidence Obligation is the evidence a scenario asks for, by the tags it carries, to be met by Evidence Observations. A pending tag such as \`@unitpending\` defers the evidence of its kind of quality check, and a deferral tag such as \`@wip\` defers all of the scenario's: what a tag defers raises no Evidence Obligation and is a Pending Item instead, tallied after the table, apart from balanced and out-of-balance, when there is one. On a scenario that shares its \`@SCN\` code with another, no tag defers anything: it reads "${DUPLICATE_SCN_CODE}" at each kind of quality check it raises, or once when it raises none.`,
|
|
28482
28482
|
[CoreMessage.EvidenceReconciliationEvidenceObservationTerm]: "An Evidence Observation is one reported result of a test or a fitness function, attributed by the codes it cites: to the one scenario that carries its one code, to a phantom claim when no scenario carries its one code, and otherwise to the unnamed claim, because no one scenario can take it. One that never reached its assertions is broken: it was reported, but did not run to a result.",
|
|
28483
28483
|
[CoreMessage.SubjectColumn]: "Subject",
|
|
28484
28484
|
[CoreMessage.TotalColumn]: "Total",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "spec-controller",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.214",
|
|
4
4
|
"description": "Reconcile the behaviour your scenarios name against the evidence that actually ran — the deterministic `balance` CLI.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"reconciliation",
|
|
@@ -26,7 +26,7 @@
|
|
|
26
26
|
"fast-xml-parser": "^5.11.2",
|
|
27
27
|
"ts-json-schema-generator": "^2.9.0",
|
|
28
28
|
"yaml": "^2.9.0",
|
|
29
|
-
"@3f-consulting/spec-controller-core": "0.1.
|
|
29
|
+
"@3f-consulting/spec-controller-core": "0.1.214"
|
|
30
30
|
},
|
|
31
31
|
"publishConfig": {
|
|
32
32
|
"access": "public"
|