FR-001reviewno test runGRC engineering MUST take catalogs and mappings from the library grc (@intellectual-frontiers/grc, grc FR-001), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
0007-grc · owner if · domain commons
FR-001reviewno test runGRC engineering MUST take catalogs and mappings from the library grc (@intellectual-frontiers/grc, grc FR-001), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-002reviewno test runGRC engineering MUST take controls from the library grc (@intellectual-frontiers/grc, grc FR-002), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-003reviewno test runGRC engineering MUST take verdicts and severities from the library grc (@intellectual-frontiers/grc, grc FR-003), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-004reviewno test runGRC engineering MUST take findings from the library grc (@intellectual-frontiers/grc, grc FR-004), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-005reviewno test runGRC engineering MUST take waivers from the library grc (@intellectual-frontiers/grc, grc FR-005), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-006reviewno test runGRC engineering MUST take the canonical form and the digests of evidence from the library grc (@intellectual-frontiers/grc, grc FR-006), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-007reviewno test runGRC engineering MUST take the evidence ledger from the library grc (@intellectual-frontiers/grc, grc FR-007), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
Cited by: pure/chain, Quality evidence
FR-008reviewno test runGRC engineering MUST take manifests from the library grc (@intellectual-frontiers/grc, grc FR-008), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-009reviewno test runGRC engineering MUST take evidence bundles from the library grc (@intellectual-frontiers/grc, grc FR-009), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-010reviewno test runGRC engineering MUST take coverage from the library grc (@intellectual-frontiers/grc, grc FR-010), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-011reviewno test runGRC engineering MUST take freshness from the library grc (@intellectual-frontiers/grc, grc FR-011), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
Cited by: ifqs/ifqs, Quality, pure/freshness, Quality evidence
FR-012reviewno test runGRC engineering MUST take drift from the library grc (@intellectual-frontiers/grc, grc FR-012), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-013reviewno test runGRC engineering MUST take the change-impact gate from the library grc (@intellectual-frontiers/grc, grc FR-013), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-014reviewno test runGRC engineering MUST take the risk register from the library grc (@intellectual-frontiers/grc, grc FR-014), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-015reviewno test runGRC engineering MUST take the requirement trace from the library grc (@intellectual-frontiers/grc, grc FR-015), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-016reviewno test runGRC engineering MUST take findings as OCSF from the library grc (@intellectual-frontiers/grc, grc FR-016), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-017reviewpassingGRC engineering MUST take assessments as OSCAL from the library grc (@intellectual-frontiers/grc, grc FR-017), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
Cited by: uuid, Quality evidence
FR-018reviewpassingGRC engineering MUST take attestations from the library grc (@intellectual-frontiers/grc, grc FR-018), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
Cited by: uuid
FR-019reviewno test runGRC engineering MUST take the run of a pack as signals from the library grc (@intellectual-frontiers/grc, grc FR-019), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-020reviewno test runGRC engineering MUST take signing and verifying from the library grc (@intellectual-frontiers/grc, grc FR-020), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-021reviewno test runThe runtime MUST take Git, read by running it from the library system (@intellectual-frontiers/system, system FR-014), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
FR-022reviewno test runGRC engineering MUST take the loaders of settings from the library grc (@intellectual-frontiers/grc, grc FR-021), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.
stolos's SQLite estate, erga's spec-kit grammar and ontology terms.catalog.control("XX-99") where the catalog has no such control: does not compile, per FR-001.error for that host, the nine others judged, per FR-002.fail joined with pass: fail; pass joined with not-applicable: pass, per FR-003.error: does not apply, per FR-005.{"b":1,"a":2.0} and {"a":2,"b":1}: one digest, per FR-006.P30D: due, per FR-011.infra/** declared for a control whose newest verdict is fail: blocked, naming the control, per FR-013.high and impact very-high: very-high, as Table I-2 gives it; the middle level is moderate, per FR-014.git not installed: an Err, never a thrown error, per FR-021.stolos writes these OCSF classes and OSCAL documents already). From OSCAL 1.1.2 to 1.2.3 the members of the four documents written did not change; 1.2 widened enumerations (component types, the discovery observation type, CVSS v4), made an SSP's users optional and added the mapping model, which is not written.OQ-1open questionWhether to add the OSCAL profile and catalog models when a harness resolves profiles itself.
SC-001success criterionerga and stolos keep no type of their own for a control, a verdict, a finding, a waiver or a ledger entry.
SC-002success criterionThe same findings give the same OCSF, OSCAL and CycloneDX on Bun and Node.
uuid, ifqs/ifqs, Quality, pure/chain, pure/freshness, git, System, Quality evidence, Intellectual Frontiers Quality System, Subject profiles