AIAAIC Repository governance
This page sets out how the AIAAIC Repository is managed, and how additions to the repository are assessed and processed.
Definitions and classifications (aka taxonomy) are set out here.
For further details, contact the Managing editor.
Governance
The AIAAIC Repository is managed as follows:
Editorial team selection. The AIAAIC editorial team, including additions and other personnel changes, is managed by Charlie Pownall, the Managing editor. The selection and approval of the editorial team members ('Contributors') takes into account an individual’s background, interests, employment, affiliations, and other criteria.
Access permissions
Google Sheets, on which AIAAIC Repository data is primarily stored, provides the four permission levels below. Access to each permission level is granted by the Managing editor.
Owner: Allowed to view, modify, add, and delete data and comments on visible and hidden sheets. Also able to add new Contributors and Premium Members, and to delete the spreadsheet. Only the Managing editor has this level of permission.
Editor: Allowed to view, modify, add, and delete data on visible and hidden sheets. Also allowed to add and reply to comments, and to download, share, and print the file. Active AIAAIC Contributors are granted Editor permissions.
Moderator: Allowed to view and add comments, as well as download, share, and print the file. Premium Members are granted Moderator permissions.
Viewer: Allowed to view, download, share and print but not edit or comment on the file.
Google Sites. Active AIAAIC Contributors are granted Editor permissions for the aiaaic.org website; inactive and former Contributors are provided with ‘Published Viewer’ status.
Content/data licensing. All AIAAIC content and data is available under a CC-BY-SA-4.0 Creative Commons license. This means that all users can use, copy, adapt, and redistribute content and data provided ‘AIAAIC’ is properly attributed and that any remixes or adaptations published or distributed by third parties (of any kind) must also be done under the same license.
Complaints. AIAAIC is committed to handling complaints of all kinds in a fair and timely manner. Complaints should be submitted here and will be assessed by the Managing editor.
Report verification
Additions to the AIAAIC Repository are considered and processed using a six-step process.
Detect. The detection of an incident or controversy. The following technologies are excluded:
Cryptography
NFTs, DAOs, DeSci/Fi, etc
CRISPR
Genetic algorithms
Quantum computing
Artificial general intelligence (AGI)
Artificial super intelligence/singularity.
Assess. A variety of predominantly qualitative criteria are used to determine whether an incident report should be listed in the AIAAIC Repository. Not all these criteria (eg. volume) need to be satisfied for an incident report to qualify.
Relevance. Entries must be ‘driven by’ or ‘relating to’ AI, algorithms, and automation. See definitions.
Impact(s). Entries to the repository should have resulted in – or be seen to have resulted in – clear harm (see definitions) to a) individuals/end users, society, and/or the environment (ie. external impacts), and/or b) to the governance and technological system of those operating, commissioning, or developing it in the form of strategic/reputational, operational, financial, and legal harms (ie. internal impacts). Equally, the potential impact(s)/harm(s) of a system may have been highlighted by a third-party or by an employee or whistleblower, in which case the report is listed under ‘Issue’.
Credibility. An incident should have been covered by the mainstream media (international, national, business, science, technology, etc) as opposed to running solely on social media, unless the individual(s) or organisation(s) involved in social media-based discussions are known to be credible and trustworthy.
Volume. The more an incident or issue is covered by the media, the more likely it is to be included in the AIAAIC Repository. However, this need not always be the case: an incident may have been widely covered but have little substance; equally, an incident may draw little attention but have a significant impact on the system under scrutiny.
Classify. The classification of the entry in line with AIAAIC's Classifications and Definitions.
Summarise. A short, written summary (example) of the entry.
Approve. The assessment of the entry for accuracy, fairness, and balance, and its approval by the Managing editor.
Publish. The publication of the entry on the AIAAIC Repository website and Google sheet.
Last updated: June 13, 2023