Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:l:legal_and_regulatory_defensibility [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:l:legal_and_regulatory_defensibility [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Legal and Regulatory Defensibility ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Legal and regulatory defensibility concerns the ability to support an outcome, decision, interpretation, | ||
| + | |||
| + | In regulated data interpretation environments, | ||
| + | |||
| + | * What information entered the system | ||
| + | * What the system observed or extracted | ||
| + | * Which semantic definitions applied | ||
| + | * Which rules, parameters, and versions governed the processing | ||
| + | * Which components or actors performed relevant actions | ||
| + | * How the system produced the result | ||
| + | * Which authority governed the interpretation or assessment | ||
| + | * How the organization preserved the evidence and processing history | ||
| + | |||
| + | Legal and regulatory defensibility depends on architectural qualities such as: | ||
| + | |||
| + | * Traceability | ||
| + | * Auditability | ||
| + | * Reproducibility | ||
| + | * Evidentiary continuity | ||
| + | * Provenance | ||
| + | * Version control | ||
| + | * Explicit interpretive authority | ||
| + | |||
| + | The architecture supports defensibility by preserving the evidence, context, reasoning, and governance relationships necessary for authorized review. It does not determine whether a court, regulator, supervisory authority, or other decision-maker accepts a particular result. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //quality of a system, process, interpretation, | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * Federated Data Interpretation Systems Reference Architecture (FDIS-RA) | ||
| + | * ISO 19011, Guidelines for auditing management systems | ||
| + | * ISO/IEC 27001, Information security management systems | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Legal and regulatory defensibility does not mean legal validity, regulatory approval, or guaranteed acceptance by an authorized decision-maker. | ||
| + | |||
| + | The architecture provides evidence and explanatory support for examination. Appropriate legal, regulatory, supervisory, | ||
| + | |||
| + | Legal and regulatory defensibility differs from auditability. Auditability concerns the ability to inspect and reconstruct activity. Defensibility concerns whether the resulting evidence, reasoning, authority, and outcome provide a supportable basis during authorized examination or challenge. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | An interpretation is legally and regulatorily defensible when an authorized reviewer can identify the source evidence, applicable definitions, | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||