Architecture Index — iSOAF Public References

Purpose

The iSOAF Public Architecture Index organizes the framework's four canonical public references into a single publication structure. Each reference has a distinct role: methodology, documented validation, evidentiary traceability, and conceptual reasoning architecture.

Publication rule: Doctrine, runtime values, historical validation metrics, research observations, and illustrative examples must be scoped distinctly so readers do not confuse enduring architectural principles with current or historical operational evidence.

Four Foundational Public References

1. Continuous Operational Assurance Methodology

Establishes the assurance principles and framework-agnostic methodology for continuously validating operational evidence.

Open Methodology PDF

v2.1 · 229 KB
SHA-256: 1cb1812380d443ec20ab5640fe4a7c8115ae62e55fb9a3a1291c7e6cbdee075c

2. Executive White Paper

Communicates the governance assurance gap, operational motivation, documented validation results, and public outcomes of iSOAF.

Open Executive White Paper

v1.2 · 109 KB
SHA-256: d525bce5386a0369e386a08fe15bec603ed83072047c09300aeff2ca84d482b6

3. Evidence Provenance

Explains evidentiary traceability, lineage, source integrity, and the role of provenance in supporting reliance.

Open Provenance Reference

Download PDF
v1.0 · 108 KB
SHA-256: 2e8e01bb8ed13f861efa559e0b5a606634e1edcd11ba005ed485de2e83e395f3

4. Reliance Assessment Model

Defines the conceptual reasoning model through which evidence is assessed, conclusions are evaluated, and reliance is validated while decisions remain under human authority.

Open RAM Reference

Download PDF
v1.1 · 103 KB
SHA-256: f486a634315d74028047443d5f5a9c0db75044b49526fd18f1790fb31378e448

Publication Claim Governance

Public-facing iSOAF statements are classified by claim type. This prevents historical proof-case values from being read as current runtime values and prevents design objectives from being interpreted as legal, operational, or technical guarantees.

Claim Class	Purpose	Publication Rule
Doctrine	Enduring architectural principles.	Use stable evidence-bounded and human-governed terminology.
Architectural Design Objective	What the framework is designed to preserve or prevent.	Use “is designed to” or “is intended to”; avoid guarantee language.
Methodology	Framework-agnostic assurance practice.	Scope to the Continuous Operational Assurance Methodology and its stated terms.
Current Runtime	Current published operational state.	Must align to the latest published runtime report.
Historical Validation	Completed validation period or proof case.	Label as historical operational validation or documented validation period.
Research	Analytical observations and future evaluation themes.	Use measured language and avoid claims of universal validity.
Illustrative Example	Education or scenario explanation.	Label as example and avoid presenting it as active runtime evidence.

Publication Boundaries

The public architecture set describes validated capabilities, governance boundaries, and operational outcomes without disclosing scoring logic, proprietary assurance methods, internal orchestration mechanics, or implementation-specific architecture. It also preserves the distinction between evidentiary reliance assessment and human decision-making authority.

Baseline Position

This Public Documentation Suite v2026.1 synchronizes the public terminology, claim-governance rules, and architectural boundaries for the current website package. Future changes should be treated as controlled revisions against this baseline rather than isolated wording changes.

The architecture index does not replace the individual references. It provides a navigation and governance layer that explains how the public documents relate to each other and how their claims should be interpreted.

Back to iSOAF