1. Organizational Context and Consequence
Establish the organization, industry, obligations, assurance calendar, workflow, action, stakeholders, and material consequence before selecting the applicable framework lens.
Assurance and evidence model
Execution Integrity Framework
The Execution Integrity Framework defines the organizational context, approved criteria, authority, execution, exception, evidence, and assurance questions required to evaluate one consequential workflow.
Proposed seven-domain model
A workflow-level framework, not a generic control catalog.
These domains reflect the current refined operating model and should receive final methodology review before public release.
2. Approved Standard in Force
Identify the approved rule, policy, control, plan, contract, criteria, version, effective date, and ownership that should govern the action.
3. Authority and Accountability
Establish who or what may recommend, approve, execute, escalate, override, or accept risk, including delegated and vendor authority.
4. Execution Conformance
Compare the actual workflow path, conditions, data, actions, and final outcome with the approved standard.
5. Exceptions, Overrides and Human Intervention
Make nonstandard paths, human judgment, escalation, and override authority visible and attributable.
6. Evidence, Provenance and Replay
Preserve the fields, sources, versions, actors, timestamps, decisions, and artifacts required to reconstruct the event.
7. Assurance, Remediation and Closure
Translate findings into approved remediation, testable criteria, validation re-runs, and ongoing assurance.
Cross-framework overlap
One observed gap can create several obligations.
The strongest front-end output is not a long framework list. It is the overlap showing why one execution gap matters across multiple assurance, contractual, regulatory, and internal requirements.
Observed gap
Control objective
Internal policy
Assurance framework
Industry obligation
Remediation
Example: no per-decision audit trail can affect several obligations at once, but the mapping must be supported and scoped.
Framework discipline
Establish the organization before the framework.
Applicable obligations cannot be selected responsibly until the organization, industry, workflow, action, geography, data, and assurance calendar are known.
- Organization and operating context
- Applicable jurisdictions and contracts
- Consequential workflow and action
- Existing control environment
- Evidence sources and limitations
- Assurance or regulatory calendar
Do not over-map
Use established framework relationships as complement claims unless control-level mappings have been documented and reviewed by the appropriate specialist.
The framework defines what to evaluate. The Closure Method defines what happens next.
Move from the observed gap to an approved, testable standard and a validation path.