Explore

Follow the approach. Inspect the work.

Bring us a real problem
01 / ORIENTATION

What matters, and who decides?

Start with what is already yours.

THE PRINCIPLE

From policy to a validated rule.

Interpretation becomes executable only after accountable owner validation.

Illustrative workflow · Synthetic example

Policy → Interpretation → Validated rule
  1. 01PolicyInspect

    The written clause is the authority. Keep its source, scope and version attached.

  2. 02InterpretationInspect

    Define issuer exposure, required inputs and the meaning of a missing assessment. Return ambiguity to the policy owner.

  3. 03Validated ruleInspect

    The owner approves the interpretation; boundary and missing-input tests validate its implementation before use.

Select a stage to inspect its detail.

Explore the principle in depth
4.0%Illustrative issuer ceiling
Assessment required before permission
Read the illustrative policy clause
“Exposure to a single issuer must not exceed 4.0%. An assessment is required before automated permission.”Constructed policy clause · Illustrative mandate §4.1–4.2

In this example, an exposure above 4.0% is refused. A missing assessment inside that limit requires human review. Only a complete case within approved authority may proceed.

01

The institution comes first.

Start with the work, knowledge and authority already in place.

Read the technical detail

We begin with the rules, records, systems and judgments your institution already relies upon. Written policy remains authoritative; interpretations are explicit; accountable owners decide what may become executable.

Start from the institution
  1. 01MandateInspect

    Identify the obligations and decisions the institution exists to carry out.

  2. 02PeopleInspect

    Find the policy owners, operators and reviewers who understand where judgment belongs.

  3. 03Operating realityInspect

    Map current systems, records, handoffs and constraints before specifying a change.

A bounded scope

Select a stage to inspect its detail.

02

Authority has a source.

A rule must retain the policy it came from and the person responsible for its meaning.

Authority travels with the source.
Written policySource of authority
Source
Clause + custody
Owner
Accountable person
Version
Effective edition
Scope
Authority + limits

Ambiguity returns to the policy owner.

Inspect the source requirements
Authoritative source
Record the mandate, policy clause or approved procedure and its custody location.
Owner and version
Identify the accountable policy owner, effective version and review date.
Interpretation
Make assumptions and ambiguities visible. Unresolved language is a question for its owner.
Scope
Specify where authority applies, where it ends and which cases require escalation.
04

Establish the boundaries.

Assess the decision terrain, then agree what authority the system may receive.

Discovery before authority
  1. 01AssessInspect

    Which decisions repeat? Which sources do people trust? Where do handoffs lose context? What does the current stack already do well?

  2. 02GovernInspect

    Who approves interpretation? Which failures must stop action? Who owns exceptions, evidence and future changes?

Select a stage to inspect its detail.

Read the technical detail

Discovery produces an explicit scope: a bounded workflow, its authoritative sources, accountable owners, input requirements and acceptance criteria. Unresolved policy questions and actions outside that authority stay out of deployment.

Browse all 15 systems & tools
05

Inspect the foundations.

The working papers remain available in full, with their original versions and source files.

Browse all 15 systems & tools