Learn / Chapter 10
Governance and Assurance
Which claim does this evidence support, and who must decide what remains acceptable?
Learning objective: construct a bounded review argument, distinguish expectations from implemented checks, and identify evidence gaps and decision responsibility.
Prerequisite: Continuous Engineering.
Manual assurance review using V0 sources. No approval, compliance evaluation or certification is performed. Hypothetical cases are teaching examples.
From a passing calculation to a justified claim
The monitoring team proposes a larger sensor radius and obtains a geometric PASS. Someone asks whether the configuration can now be accepted for operational use. The calculation supports a narrower statement: under particular inputs, criterion and idealized assumptions, the sampled area estimate meets the threshold. It does not establish that a physical sensor will detect the objects the operator needs to monitor.
The gap is a reasoning problem before it is a tooling problem. We must say what is being claimed, why the available evidence bears on that claim and what remains unsupported. A longer list of successful checks cannot supply a missing relationship between geometric area and operational detection.
For this lesson, a claim is a statement under review; evidence is an actual observation from an identified execution or source; supporting reasoning explains their connection. A control is a defined measure intended to constrain or check work. Decision responsibility identifies who must resolve remaining questions within the real assignment. These are local teaching terms, not a claim of standards conformance.
Separate the expectation from its mechanism
The operational need motivates the work. The requirement defines a geometric criterion, currently 50%, for SCN-001. A review expectation such as “identify the evaluated revision” concerns how a proposal is assessed. It does not replace that behavioral criterion or provide its operational basis.
An expectation also differs from an implemented mechanism. The source validator checks contracts and relationships. The registered test assertions check specified behavior. Generated analyses record inputs and execution context. None of those mechanisms automatically decides whether the operational need is adequately addressed. Read their actual scope before describing them as controls over a broader decision.
The table maps selected review expectations to existing sources and observations. It is a manual teaching aid, not a canonical policy, a control evaluation result or an approval record. The responsible reviewers named here describe roles needed by the exercise; they do not identify appointed people or assert configured repository permissions.
| Expectation | Existing source/check | Observation needed | Limit and next responsibility |
|---|---|---|---|
| Definitions are interpretable | Source validation | Actual validation outcome and definitions at its revision | Contracts do not establish operational basis; requirement reviewer examines the criterion. |
| Implemented behavior matches assertions | TEST-COV-001 and model tests | Actual test command/log and checked revision | Successful assertions preserve the canonical geometric FAIL; model reviewer assesses omitted behavior. |
| Analysis is attributable | Proposal records and provenance | Definitions, differences, calculation and execution context | Attribution is not acceptance; proposal reviewer checks task scope and evidence applicability. |
| Decision is justified | Written task boundary | Explicit claim, gaps and responsible next review | No operational approval is recorded here; responsible engineering authority must resolve acceptance. |
Traceability is a route to review
A source link lets a reviewer inspect a definition; a stable identifier connects records across changes. Neither establishes that an execution used today's definition. Match source revision, working-tree state, inputs, criterion, method and model version before attaching a retained result to the claim being reviewed.
Then test the reasoning, not merely the links. An ideal circular footprint omits terrain, occlusion, uncertainty and sensor faults. Evidence of its sampled area supports a geometric statement under those omissions. If the claim concerns physical detection, name the missing observations or models instead of treating additional trace links as stronger physical evidence.
Counterarguments make that boundary inspectable. Ask whether the criterion has a justified operational basis, whether the scenario represents intended use and whether the method can observe the behavior claimed. An unanswered question is an explicit limitation. It is not automatically a measured failure, and it must not disappear because another check passed.
Keep the argument reviewable as the proposal evolves. If the evaluated input changes, revisit the associated observation. If the claim broadens, revisit whether the same method can support it. If only a document link changes, confirm that it still identifies the intended definition. These are different review questions; recording them explicitly helps the next engineer avoid carrying an unsupported conclusion into a later decision.
Build a bounded review argument
- Apply the radius-only task. Try the radius proposal and inspect its exact difference. Write the narrow geometric claim, including criterion and assumptions.
- Reset and try the threshold proposal. Compare changed fields and explain why calculation success does not justify the new criterion under that assignment.
- Break a reference, then restore/reset. Distinguish invalid definitions from valid definitions with insufficient operational support.
- Use the review table to name actual evidence needed, remaining gaps and the responsible next review. No decision is saved or approved by this page.
A definition change, not an approval
Temporary, unapproved browser proposal. This workspace changes a copy of the definitions. It does not edit YAML, execute TEST-COV-001, retain evidence or approve a requirement. Reset restores the baseline; leaving or reloading discards edits.
Canonical baseline from this site build
Requirement REQ-COV-001: 50%. Scenario SCN-001: radius 35, center (50, 50), area 100 × 100 model units.
Under reference scenario SCN-001 and the V0 model assumptions, the monitoring configuration shall cover at least 50 percent of the defined area geometrically.
FAIL — 38.52% estimated coverage. Margin: -11.48 percentage points.
This is a build-time calculation, not a displayed CI verification artifact. The baseline stays unchanged while you edit.
Enable JavaScript to validate and evaluate a temporary proposal.
Exact field differences
The requirement statement and basis change with the threshold so the proposed definition stays consistent. These differences describe the current trial, not a committed revision.
| Field | Baseline | Proposal |
|---|
Inspect the validated proposed definition
No proposal evaluated yet.
Both calculations use MODEL-COV-001 v0.1.0: a 100 × 100 cell-center area estimate. No physical sensor calibration, terrain, occlusion, directional effects, time, uncertainty, faults or communications are modeled. A PASS establishes neither operational suitability nor an optimal design.
A proposal can pass and still need a decision
Both existing proposal examples can produce a modeled PASS. The radius example changes geometry while retaining the criterion. The threshold example changes evaluation meaning while keeping the same coverage. Under the radius-only assignment, the latter is outside the agreed edit boundary even though its data validate and its arithmetic is correct.
A request to relax the criterion therefore needs a separately justified requirement decision and appropriate authority. The proposal author cannot derive that authority from the result they wish to obtain. Likewise, changing expected assertions to conceal a known outcome would remove useful feedback rather than resolve the engineering problem.
Keep the stages visible: propose, validate, analyze, interpret and decide. In this exercise the decision remains unresolved. A reviewer can identify the narrow supported claim and request missing evidence without either accepting the physical design or declaring every aspect of the proposal invalid. No automated approval system is needed to practice that distinction.
Review hypothetical evidence gaps
These designed cases do not report actual missing artifacts or failed controls. State what remains supportable before revealing the explanation.
A PASS has no provenance
The label alone cannot be attributed to the candidate. Request definitions and execution context; do not invent a revision or claim verified suitability.
The proposal is valid, but operational evidence is absent
The geometric claim may remain supported by its actual calculation. Physical acceptance remains open; the responsible engineering reviewer must identify required operational evidence.
Someone asks to lower the threshold
Identify the changed requirement and its missing justification. Refer it to the responsible requirement authority; a passing number cannot authorize the change.
The historical artifact has expired
State that the original record was unavailable. A local reproduction is a new execution with its own provenance; it does not reconstruct an original approval or observation.
Record what was actually inspected
Follow the repository assurance review to inspect actual definitions and generated records at an identified checkout. Reference generation evaluates canonical inputs; separate test logs establish assertion execution. Proposal analysis explicitly does not execute the registered reference test against changed inputs. Preserve those meanings in your written argument.
No historical CI artifact is loaded by this page. Browser proposals are temporary; the baseline is calculated at build time. Retained artifacts expire after 30 days and may require sign-in. Record what you actually inspected, what was unavailable and which claim remains unresolved. This review is an aid to accountable reasoning, not production-system assurance or certification.
Check your reasoning
1. Does traceability establish evidence sufficiency?
No. It enables inspection; reasoning must still connect the evidence's scope and limitations to the claim.
2. Is an unobserved operational behavior a measured failure?
No. Missing support and a measured failure are different findings. Name the gap without inventing a result.
3. Can a PASS authorize a changed criterion?
No. The criterion needs its own engineering basis and responsible decision; task authority does not follow from arithmetic.
4. Does this review table implement governance controls?
No. It maps expectations to existing checks and remaining decisions. It records no approval or compliance evaluation.
Next: preserve meaning through evolution
We can now state a bounded claim, inspect its support and identify unresolved responsibility. Continue with Chapter 11: Engineering Knowledge at Scale to preserve those meanings when definitions are configured, reused and changed across a growing body of engineering knowledge.