Core Systems · Long-Form Feature
Core modernisation is a sequence of risk decisions
A long-form feature connecting how architecture choices affect data lineage, change risk and service resilience to practical reading and decision discipline.
Article archive
Core Banking Modernisation, Data And Ai Governance
Three editorial formats, one source discipline. This archive is a dated collection rather than a live feed; each article records its desk, format, publication date and primary reading.
Data · Reported Explainer
Data lineage is the quiet dependency of banking AI
A close look at incremental migration, observable interfaces and accountable model use, with source-led questions for teams working in core banking modernisation, data and AI governance.
AI Governance · Annotated Guide
An architecture review for incremental migration
A structured way to decide which modernisation step removes structural risk without creating an untestable migration, without presenting a static article as live advice.
Coverage structure
Four desks, distinct questions
Our taxonomy is designed around decisions readers make, not around search-volume labels. The categories keep news, explanation and analysis legible while allowing a story to show cross-cutting dependencies.
Core Systems
This desk follows how architecture choices affect data lineage, change risk and service resilience from a architectural, sceptical and implementation-focused perspective. Coverage prioritises primary sources, decision context and clear limits.
Data
This desk follows how architecture choices affect data lineage, change risk and service resilience from a architectural, sceptical and implementation-focused perspective. Coverage prioritises primary sources, decision context and clear limits.
AI Governance
This desk follows how architecture choices affect data lineage, change risk and service resilience from a architectural, sceptical and implementation-focused perspective. Coverage prioritises primary sources, decision context and clear limits.
Migration
This desk follows how architecture choices affect data lineage, change risk and service resilience from a architectural, sceptical and implementation-focused perspective. Coverage prioritises primary sources, decision context and clear limits.
How to use this archive
Start with the format label. A reported explainer reconstructs a mechanism; policy analysis distinguishes authoritative text from our interpretation; a guide or timeline organises questions for later verification. None is a substitute for current professional advice. We do not silently update dates, present archived material as live or add a “breaking” label to create urgency.
Every article links to primary material where available. We record a verification date because source pages can change, documents can be superseded and implementation may vary by institution. If an article is materially corrected after launch, the correction should be dated and described rather than overwritten without notice.
Commercial material is not included in this archive grid. When campaign data is complete, the homepage may show a clearly labelled sponsored unit assembled from the fixed campaign files. The editorial desk does not create substitute copy when those files are absent or malformed.
The archive intentionally keeps three formats side by side. Read across them to compare the mechanism, governance question and implementation sequence; then return to the primary source for current text. Category anchors are a reading aid, not a claim that complex banking work belongs to only one desk.