-
Notifications
You must be signed in to change notification settings - Fork 0
ADR 019 Derived Binary View from Quantitative Metrics
Status: Accepted Date: 2026-05-16 Deciders: Michael Zargham Related: ADR-004 Quantitative Certification Outcome; ADR-007 Scope as First-Class RDF Resource; Quantitative Outcomes; Certification Predicate; Design Spec
The Zargham 2026 paper, in its TDD framing, characterizes the RTM certification predicate as binary — the RTM is complete or it is not. v0.1's primary certification outcome is quantitative (see ADR-004 Quantitative Certification Outcome) because institutional adoption requires the gradient. Yet some downstream consumers — CI pipelines, dashboards, contractual sign-offs — want a single pass/fail signal. The question is whether v0.1 produces the binary view as a separate first-class outcome or derives it from the quantitative metrics against a configurable threshold. See Design Spec §4.5 and Certification Predicate.
flexo-rtm v0.1's binary certification view is derived from the quantitative metrics against a configurable threshold (per scope, per claim type, per aspect). A cert run produces the quantitative coverage matrix; the binary view applies the configured thresholds and emits pass/fail. The thresholds are part of the cert run configuration (scope + profile + thresholds — see ADR-007 Scope as First-Class RDF Resource and ADR-016 Composable SHACL Profiles); a cert artifact records both the quantitative metrics and the threshold-evaluated binary outcome.
- Reconciles paper's TDD framing with industrial reality: institutions get the binary outcome the paper describes, but produced by an explicit, configurable threshold rather than implicit definition
- Threshold transparency: every cert artifact records the thresholds used; reviewers can see why a cert is binary-passing and what would have to change for it to fail
- Per-scope and per-aspect thresholds let safety-critical scopes set 100% while exploratory scopes set lower thresholds, without parallel binary-predicate definitions
- Forward-compatible with downstream-analysis paths (per ADR-032 Methodology Agnosticism as Foundational Axiom): an adopter who runs topological analysis as a downstream-analysis mode (see ADR-003 Topological Framework Documented as Future Work) can compose the closure predicate with the threshold-derived binary; adopters running SLSA, GSN, ARP4754A, or in-house analyses compose their own predicates on the same threshold-derived foundation
- Threshold-setting is a governance question per scope; institutions have to decide and document their thresholds
- The "TDD pass/fail" semantics of the paper is not literally what v0.1 implements — v0.1's binary is threshold-derived, which is more nuanced; bridging documentation required
- The binary view is always a projection of the quantitative model — never a parallel computation that could disagree
- Pure quantitative (no derived binary): Emit only coverage percentages and gap reports; let downstream consumers derive their own binary signals. Rejected: forces every consumer to define their own threshold mechanism, defeating the institutional-consistency story. A cert artifact should record a binary signal alongside the metrics so that contractual sign-offs and CI gates have a stable interpretation point.
- Cert run configuration declares thresholds as part of the run inputs (alongside scope and profile); thresholds are per claim type per aspect
- Analysis layer (
oracle/src/oracle/analysis/) computes the quantitative coverage matrix; the cert-artifact builder applies thresholds and emits the binary view - Cert artifact format records: (a) the quantitative coverage matrix, (b) the threshold configuration used, (c) the threshold-evaluated binary outcome per claim type per aspect, (d) the overall cert pass/fail (typically the AND of all threshold evaluations within the scope)
- See Certification Predicate for the canonical predicate semantics and threshold composition
- Design Spec §4.5 (Derived Binary View), §4.6 (Threshold Configuration)
- Certification Predicate — the canonical predicate semantics
- Quantitative Outcomes — the underlying quantitative model
- ADR-004 Quantitative Certification Outcome — the primary outcome this derives from
-
ADR-032 Methodology Agnosticism as Foundational Axiom — the threshold-derived binary is
flexo-rtm's; downstream-analysis paths compose their own predicates on top
- Flexo Git Coexistence
- ADCS Prototype Lessons
- MVC Pattern from RIME TRL ANT
- Human-AI Accountability
- Multi-Agent Discourse Graph Precedent
- OSLC RM and QM Review
- INCOSE V2 Review
- OMG SysMLv2
- PROV EARL GSN P-PLAN
- Dragon Architecture and Mission Enterprise
- Traditional Forward and Backward Analysis
- Attestation Infrastructure in v0.1
- Identity Boundaries and Policy Projections
- External URI References
- Signed Envelopes and Established Standards
- Aspect Coverage with Adequacy and Sufficiency
- Federated Audit and Composition
- Certification Predicate
- Gap Taxonomy
- Quantitative Outcomes
- Engineering Lifecycle Stages (v0.2)
- Topological Framework Future Work (research phase)
- Vertices Edges Faces (research phase)
- Three-Layer Architecture
- Operational Layer UX Discipline
- Storage Layer Flexo Conventions
- Analysis Layer Scope Algebra
- OSLC Roundtrip Acceptance
- Identity Adapter Contract
- Flexo REST Binding
- SysMLv2 Ingestion Contract
- External URI Rules
- Signed Envelope Shapes
- Parsimony Manifest
- Lossless Roundtrip Definition
- Vendor Extension Carry-Through
- OSLC RM Adapter Contract
- OSLC QM Adapter Contract
- ADR Template
- ADR-001 Foundations First Approach
- ADR-002 SysMLv2 Anchoring
- ADR-003 Topological Framework Documented as Future Work
- ADR-003a v0.1 Ships Traditional Analysis Only
- ADR-004 Quantitative Certification Outcome
- ADR-005 Adequacy and Sufficiency as Guidance Subtypes
- ADR-006 Three-Layer Architecture
- ADR-007 Scope as First-Class RDF Resource
- ADR-008 Repo Name and Org Transfer Plan
- ADR-009 Two-Repo Strategy
- ADR-010 OSLC-RM and OSLC-QM in v0.1
- ADR-011 Lossless Criterion A plus C
- ADR-012 Direct RDF Properties over Reified Edges
- ADR-013 Simplicial Complex as Derived View When Built
- ADR-014 Parsimony Layer Build-Time Extraction
- ADR-015 GSN Adoption for Adequacy and Sufficiency
- ADR-016 Composable SHACL Profiles
- ADR-017 knowledgecomplex as Optional Extras
- ADR-018 V minus F Invariant Deferred with Topological Framework
- ADR-019 Derived Binary View from Quantitative Metrics
- ADR-020 Vocabulary Alignment with Zargham 2026
- ADR-021 Three Attestation Subclasses Ship in v0.1
- ADR-022 External URI References as Open-Source Foundation
- ADR-023 Cryptography by Composition of Battle-Tested Standards
- ADR-024 Identity by Thin Projection of External Sources
- ADR-025 Reproducibility is Structural and Local
- ADR-026 Cryptographic Agility via Algorithm Profiles
- ADR-027 Bit-Exactness vs Numerical Tolerances Are Both First-Class
- ADR-028 Scope-Level Adequacy and Sufficiency for Federated Audit
- ADR-029 Engineering Lifecycle Stages as Scope Metadata
- ADR-030 Polycentric ASOT Authority Model
- ADR-031 Attestation Status Pass Fail Deferred Deprecated
- ADR-032 Methodology Agnosticism as Foundational Axiom
- ADR-033 Generalized ASOT Principle for All Identified Things