Welcome to the internal ClearSanction product and company documentation.
This documentation provides the central reference for how ClearSanction works, how the platform is designed, how features behave and how the product evolves.
Internal Documentation
This wiki contains internal ClearSanction product, technical, operational and commercial information. It should not be treated as public or customer-facing documentation unless a page is explicitly classified as public.
ClearSanction is a modern compliance platform designed to make sanctions screening simpler, faster and more explainable.
Our product philosophy is built around creating compliance software that is:
The platform should reduce compliance effort while increasing transparency and trust.
Detailed documentation covering the ClearSanction platform and its capabilities.
Technical documentation for integrating with the ClearSanction API.
Topics include:
API documentation should clearly distinguish between Sandbox and Production behaviour.
Documentation explaining the data and compliance foundations behind ClearSanction.
Topics include:
This section should help explain not only what data ClearSanction uses, but how that data contributes to screening and compliance decisions.
Internal technical documentation describing how ClearSanction is built and operated.
Topics include:
Architecture documentation should describe the current production architecture rather than planned or experimental designs.
Operational documentation for maintaining and supporting ClearSanction.
Topics include:
Documentation covering the development and evolution of ClearSanction.
Detailed specifications for capabilities being designed or developed.
Specifications must clearly state their status.
For example:
Proposed → Approved → In Development → Released
Planned functionality must never be represented as currently available functionality.
Product priorities and planned development.
Significant customer requirements and recurring product themes.
A chronological record of released product improvements.
The ClearSanction Product & Company Handbook is the authoritative source of truth for the current state of ClearSanction.
It answers:
What is true today?
It covers the company, product, strategy, capabilities and guiding principles.
Detailed product documentation in this wiki should remain consistent with the Handbook.
The ClearSanction Decision Log records significant product, technical, commercial and operational decisions.
It answers:
Why was this decision made?
The Decision Log preserves the reasoning behind important decisions and provides historical context as ClearSanction evolves.
Historical decisions should not be rewritten when circumstances change. A new decision should supersede the previous decision while preserving the original reasoning.
The ClearSanction Brand Guidelines define the approved visual identity, design principles and tone of voice.
They apply across:
ClearSanction should consistently feel:
Trusted · Professional · Modern · Enterprise · Intelligent · Practical · Transparent
Documentation supporting the customer lifecycle.
Topics include:
ClearSanction documentation follows a simple principle:
| Documentation | Question it answers |
|---|---|
| Product & Company Handbook | What is true today? |
| Product Documentation | How does it work? |
| Product Specifications | What are we building? |
| Decision Log | Why did we make this decision? |
| Release Notes | What changed? |
| Architecture Documentation | How is it built? |
| Operational Runbooks | How do we operate it? |
These documents should complement each other rather than duplicate each other.
Product documentation should clearly indicate its status.
Recommended statuses:
| Status | Meaning |
|---|---|
| 🟢 Released | Available in production |
| 🟡 In Development | Currently being implemented |
| 🔵 Planned | Approved for future development |
| ⚪ Proposed | Under consideration |
| 🔴 Deprecated | Being removed or no longer recommended |
| ⚫ Archived | Historical documentation |
Planned, proposed and in-development functionality must not be described as released functionality.
Pages should also identify their intended audience where appropriate.
| Classification | Description |
|---|---|
| Public | Suitable for public documentation |
| Customer | Suitable for authenticated customers |
| Internal | ClearSanction internal use |
| Confidential | Restricted business or security information |
Unless explicitly stated otherwise, documentation within this wiki should be considered Internal.
When creating or updating documentation:
Someone joining ClearSanction should be able to understand the product, how it works, why important decisions were made and how to operate it by starting here.
The documentation should grow alongside the platform while remaining clear, trustworthy and maintainable.