AI entity
Every one of those 1 sits in a single category, regulation. Of the tracked stories, 1 of 1 also mention Artificial Intelligence, the most common co-covered peer. Each story carries 2 original sources on average, compared with 2.9 for the broader beat in this window.
Last mentioned: Mar 7, 2026
Entity pulse
Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.
Every one of those 1 sits in a single category, regulation. Of the tracked stories, 1 of 1 also mention Artificial Intelligence, the most common co-covered peer. Each story carries 2 original sources on average, compared with 2.9 for the broader beat in this window. Their average consequence score of 6 runs below the beat's 6.6 for that window. ICTlogy appears in 1 tracked AI story from March 7, 2026.
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 29 AI stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Other entities that clear the same relevance threshold in stories also covering ICTlogy. Shared-story counts are live from our verified record — not editorial picks.
Expected Policy Influence
Anticipated adoption of playbook principles in regional public procurement guidelines.
Bibliographic Integration
The playbook is formally indexed in the ICT4D research bibliography for global policy use.
Report Publication
Initial release of the Mission-Oriented Playbook for AI procurement.
A new framework from ICTlogy introduces a mission-oriented approach to public AI procurement, prioritizing meaningful stakeholder engagement over traditional technical checklists. The playbook aims to bridge the gap between algorithmic deployment and social accountability in the public sector.
ICTlogy is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.
