Tag: AI

  • Artificial Intelligence: How Do We Use It Ethically?

    Artificial Intelligence: How Do We Use It Ethically?

    Let’s talk about Artificial Intelligence: How Do We Use It Ethically? There’s been a lot of interest in this topic recently, as well as quite a lot of emotion and misinformation.

    I wanted to set out how the Safety Artisan uses Artificial Intelligence, or AI, ethically. But to do that, we have to understand what the ethics are and the ethical questions around AI.

    Many of the arguments about AI centre around two questions:

    • First: are we infringing copyright, the intellectual property of other people, by using AI?  
    • Second: by using AI, are we putting people out of work?

    Copyright Law & AI Training

    So, let’s look at the first issue. Before we can make any judgment about what AI does we need to understand Copyright law and how AI is trained.

    First, we should note that not all published material is subject to copyright. Many US government publications are copyright-free on principle, because they were paid for by the American people and may be freely used by them. There is also lots of online material published under Creative Commons (CC) 3.0 or 4.0. CC 3.0 may be copied, changed and republished for non-commercial use, but CC 4.0 may be used in this way for commercial gain. Both usually require attribution to or acknowledgement of the original.

    Copyright law (or is it just convention?) says that we can quote copyright, provided that we attribute the information to our source. (Let’s skip the issue that when we quote somebody, we might be quoting a quote; the true originator might be somebody else entirely, but we might not know that.)

    If, however, we copied someone else’s work word for word without attribution, then that may be a civil offense. We have passed off somebody else’s work as ours, and we have infringed their copyright, their Intellectual Property (IP).

    Interestingly, it is not an offense to look at somebody else’s work and to write a précis or summary, or reword it – to use those ideas but to put them in our own words. That has always been legal. Indeed, this is the basis of reportage and criticism. Every time we write a book, an article, or a blog post, we are probably taking information from many sources and putting it together in a unique way, using our own unique words. That’s normal and ethical practice.

    What is curious is that different standards seem to be applied to AI. Perhaps it is because those who criticize it don’t understand how it works.

    How Does Artificial Intelligence Really Work?

    AIs, particularly Large Language Models (LLMs), are trained on vast data sets which are freely available online. The AI engine does not read and store or copy these sources, but learns from them. It is remarkably like the way humans learn, and sometimes deliberately so. AI adjusts itself depending on the information that it receives. Just as a brain is a complex neural net, AI is a complex set of algorithms; indeed, it may use an artificial neural net, deliberately aping the human brain.

    So, we can put aside the notion that AI is copying other people’s work. When an LLM is trained on billions of web pages, it would simply not be feasible to store all that information for the AI to refer to when we ask a question. Instead, the AI interprets the questions that we ask it and then it responds using the algorithms which have been trained on the real data.

    It looks like a reproduction because it is so lifelike, so incredibly realistic. We think it must be working from stored, i.e., copied, knowledge. But it isn’t.

    AI’s uncanny ability to process data does not come from real intelligence. Rather, it is Machine Learning, and it is a dumb machine. What it is really doing is using brute-force power to make up for its lack of intelligence. A single microprocessor can carry out hundreds of thousands of operations in a second. An AI model may be run on hundreds or even thousands of such microprocessors in a server farm.

    Using AI at The Safety Artisan

    So, let’s look at some practical examples. How do we use AI at The Safety Artisan?

    First, we use LLMs to help us generate some blog posts.

    A typical process is that I make a video where I’m talking live to camera, often without a script. I’ve got the knowledge of the subject to be able to do that, with structure from presentation slides that I’ve prepared. However, prose that works in spoken form – when you can see my face, hear my voice and interpret my words – doesn’t work so well when it’s text on a page.

    I use an AI to take my recorded video and extract my words into a raw transcript. I still use a tool called Pictory AI (https://pictory.ai) in order to edit my videos, which it does by manipulating the AI-generated transcript.

    I then used to pay my daughter, who is an English literature graduate, to edit this transcript. All through the COVID epidemic, she edited my work and then sent it back to me. I paid her to do this, and it supplemented her furlough payments while she was laid off.

    What I can do now is take that AI-extracted transcript and feed it to ChatGPT, an LLM (GPT stands for ‘General Purpose Transformer’). I ask it to improve the transcript and turn it into prose of whatever style I want (formal, conversational, whatever). It does an incredible job in seconds.

    Lately, I’ve been asking ChatGPT to turn my work into simplified English in accordance with an international standard, ASD-STE100 (Simplified Technical English). I know of this standard because it is used internationally in engineering and maintenance publications when parsing unambiguous user instructions for tasks, which may be safety-related. Of course, we want such instructions to be clear and easy to read!

    Another variation is to take an existing publication and to use ChatGPT to translate it. For example, I might take an excerpt from a safety standard or process guide, which may be written in dense and difficult language. I then ask ChatGPT to convert it into something more accessible and readable for a blog post article.

    This is legal and ethical on several levels:

    • First, the original source may be copyright-free, or it may be usable under CC 3.0 or 4.0. There is a huge amount of material online which is available in this way.
    • Second, the LLM is not copying the material; it is making a reworded precis or summary of the material, which is not an infringement of copyright.
    • Third, I give attribution to show where the information originally came from.

    The last point is not always strictly necessary, but I like to do it anyway. It shows that I am drawing on an authoritative source, which is important given that I’m teaching people how to do safety in accordance with legal requirements or standards.

    Another example is the use of Imagery

    When I started The Safety Artisan in 2018, I paid a graphic designer (https://www.linkedin.com/in/samjusaitis/) I knew to come up with a logo and colour scheme for the brand. I was very pleased with the result, and his advice on website design – thanks, Sam!

    Having done that, I might change that logo by feeding it again into ChatGPT and asking it to update the logo. Here’s the original and an example of ChatGPT content. I asked the LLM to come up with a ‘Millennial Minimalist’ version using Sam’s colour palette. (Why ‘Millennial Minimalist’? I asked Google what was popular with younger demographics, my target audience. How do I know what my target audience is? Because I did my homework.)

    Similarly, a former employer paid Iain Bond Photography to take headshots of me and my colleagues. The images belong to the photographer, but the firm bought the right to use the photos. Ownership is quite a complex issue in Australia – see this guidance from The National Library of Australia. (N.B. I haven’t researched the law in other jurisdictions – it may be different where you are.)

    I fed this original image into ChatGPT, which it manipulated. With mixed results, as you can see.

    The original photograph is on the left, and the obviously stylised version in the middle. So far, so good. The version on the right makes me look like someone else (my wife says Ewan McGregor, my daughter says Andy Burnham or Ronnie Corbett!) and I find it faintly unsettling. This is illuminating, isn’t it? Something that is obviously derivative and artificial looks fine. Conversely, something realistic, but not quite right, looks false and wrong. I guess it’s down to authenticity.   

    Another example is images I use in web pages and posts. I used to use pictures that I took myself, which were never very successful, as I’m not a very good photographer. Or I used to go to sites like Pexels.com and get free images there. I would then acknowledge the photographer who took the original pictures in the picture’s caption.

    Now I can use ChatGPT and just feed it the text that I’m going to use. The LLM will generate a suitable image for me to use with the material. Sure, I’m not paying any artist, but as a small business I couldn’t afford to pay a graphic designer or photographer for such images anyway. I would have done it myself in the free version of Canva, or some other online tool.

    Here are some examples of ChatGPT’s work.

    All I had to do was give it the address of a recent blog post, “Supporting a Vision Worth Sharing”, and it did the rest. First, I asked for a Millennial Minimalist version, then an art deco version, and, finally, one done in the style of a vintage British railway poster. Each one took only seconds to generate, and they are all quite lovely. (Incidentally, the LLM made up a new Safety Artisan logo, which I later asked it to replace.)

    Summary

    If we are going to use AI ethically, then I dare to suggest the following principles:

    • We need to understand copyright, Intellectual Property, Creative Commons Licences, and the conditions that the original creator imposes.
    • We need to understand how AI (Machine Learning) works and what it does and does not do.
    • Authenticity and openness about use of AI are key.
    • Successful use of AI requires skilful direction, which comes from knowing the subject and doing your research.
    • We still need to check the results from LLMs and other AIs.

    What do you think?

    Declaration: I dictated this article into my phone using Gmail voice recognition and edited it in Microsoft Word. I fed this article to ChatGPT asking it to suggest SEO hashtags for it. It did, but it also pointed out that I had incorrectly written “ASD-100STE”, whereas it is “ASD-STE100 (Simplified Technical English)”.

  • Updating Legal Presumptions for Computer Reliability

    Updating Legal Presumptions for Computer Reliability

    TL;DR Updating Legal Presumptions for Computer Reliability must happen if we are to have justice!

    Background

    The ‘Horizon’ Scandal in the UK was a major miscarriage of justice:

    Between 1999 and 2015, over 900 sub postmasters were convicted of theft, fraud and false accounting based on faulty Horizon data, with about 700 of these prosecutions carried out by the Post Office. Other sub postmasters were prosecuted but not convicted, forced to cover Horizon shortfalls with their own money, or had their contracts terminated. The court cases, criminal convictions, imprisonments, loss of livelihoods and homes, debts and bankruptcies, took a heavy toll on the victims and their families, leading to stress, illness, family breakdown, and at least four suicides.

    Wikipedia, British Post Office scandal

    ‘Horizon’ was a faulty computer system, produced by Fujitsu.  The Post Office had lobbied the British Government to reverse the burden of proof so that courts assumed that computer systems were reliable until proven otherwise.  This made it very difficult for sub-postmasters – small-business franchise owners – to defend themselves in court.

    A 1984 act of parliament ruled that computer evidence was only admissible if it could be shown that the computer was used and operating properly. But that act was repealed in 1999, just months before the first trials of the Horizon system began. When post office operators were accused of having stolen money, the hallucinatory evidence of the Horizon system was deemed sufficient proof. Without any evidence to the contrary, the defendants could not force the system to be tested in court and their loss was all but guaranteed.

    Alex Hern writing in The Guardian in January 2024.

    This shocking miscarriage of justice was based on an equally shocking presumption.  One that anyone with a background in software development would find ridiculous. 

    Introduction 

    Legal experts warn that failure to immediately update laws regarding computer reliability could lead to a recurrence of scandals like the Horizon case. Critics argue that the current presumption of computer reliability shifts the burden of proof in criminal cases, potentially compromising fair trials.

    The Presumption of Computer Reliability

    English and Welsh law assumes computers to be reliable unless proven otherwise, a principle criticized for its reversal of the burden of proof. Stephen Mason, a leading barrister in electronic evidence, emphasizes the unfairness of this presumption, stating that it impedes individuals from challenging computer-generated evidence.

    It is also patently unrealistic.  As I explain in my article on the Principles of Safe Software Assurance, there are numerous examples of computer systems going wrong:

    • Drug Infusion Pumps,
    • The NASA Mars Polar Lander,
    • The Airbus A320 accident at Warsaw,
    • Boeing 777 FADEC malfunction,
    • Patriot Missile Software Problem in Gulf War II, and many more…

    Making software dependable or safe requires enormous effort and care.

    Historical Context and the Horizon Scandal

    Dating back to an old common law principle, presuming the reliability of mechanical systems, the UK Post Office also lobbied to have the principle applied to digital systems. The implications of this change became evident during the Horizon scandal, where flawed computer evidence led to wrongful accusations against post office operators. Repealing the 1984 act further weakened safeguards against unreliable computer evidence, exacerbating the issue.

    International Influence and Legal Precedents

    The influence of English common law extends internationally, perpetuating the presumption of computer reliability in legal systems worldwide. Mason highlights cases from various countries supporting this standard, underscoring its global impact.

    “[The Law] says, for the person who’s saying ‘there’s something wrong with this computer’, that they have to prove it. Even if it’s the person accusing them who has the information.”

    Stephen Mason

    Modern Challenges and the Rise of AI

    Advancements in AI technology intensify the need to reevaluate legal presumptions. Noah Waisberg, CEO of Zuva, warns against assuming the infallibility of AI systems, which operate probabilistically and may lack consistency.

    With a traditional rules-based system, it’s generally fair to assume that a computer will do as instructed. Of course, bugs happen, meaning it would be risky to assume any computer program is error-free…Machine-learning-based systems don’t work that way. They are probabilistic … you shouldn’t count on them to behave consistently – only to work in line with their projected accuracy…It will be hard to say that they are reliable enough to support a criminal conviction.

    Noah Waisberg

    This poses significant challenges in relying on AI-generated evidence for criminal convictions.

    Section 5: Proposed Legal Reforms

    James Christie is a software consultant, who co-authored recommendations for an update to the UK law.  He proposes two-stage reforms to address the issue.

    The first would require providers of evidence to show the court that they have developed and managed their systems responsibly, and to disclose their record of known bugs … If they can’t … the onus would then be on the provider of evidence to show the court why none of these failings or problems affect the quality of evidence, and why it should still be considered reliable.

    James Christie

    First, evidence providers must demonstrate responsible development and management of their systems, including disclosure of known bugs. Second, if unable to do so, providers must justify why these shortcomings do not affect the evidence’s reliability.

    The Reality of Software Development

    First of all, we need to understand how mistakes made in software can lead to failures and ultimately accidents.

    Errors in Software Development

    This is illustrated well by this standard BS 5760. We see that during development people, either on their own or using tools make mistakes. That’s inevitable. And there will be many mistakes in the software – as we will see. These mistakes can lead to faults or defects being present in the software. Again, inevitably, some of them get through.

    BS 5760-8:1998. Reliability of systems, equipment and components. Guide to assessment of the reliability of systems containing software

    If we jump over the fence, the software is now in use. All these faults are in the software, but they lie hidden. Until that is, some revealing mechanism comes along and triggers them. That revealing mechanism might be a change in the environment and operator scenario, or changing inputs that maybe the software is seeing from sensors.

    That doesn’t mean that a failure is inevitable because lots of errors don’t lead to failures that matter. But some do. And that is how we get from mistakes to false or defects in the software to run time errors.

    What Happens to Errors in Software Products?

    A long time ago (1984!), a very well-known paper in the IBM Journal of Research looked at how long it took faults in IBM operating system software to become failures for the first time. We are not talking about cowboys producing software on the web that may or may not work okay, or people in their bedrooms producing apps. We’re talking about a very sophisticated product that has been in use all around the world.

    Yet, what Adams found was that lots of software faults took more than 5,000 operating years to be revealed. He found that more than 90% of faults in the software would take longer than 50 years to become failures.

    ‘Optimizing Preventive Service of Software Products’ Edward N. Adams, IBM Journal of Research and Development, 1984, Vol 28, Iss. 1

    There are two things that Adams’s work tells us.

    First, in any significant piece of software, there is a huge reservoir of faults waiting to be revealed. So if people start telling you that their software contains no defects or faults, either they’re dumb enough to believe that, or they think you are. What we see in reality is that even in a very high-quality software product, there are numerous latent defects.

    Second, many of them – the vast majority of them – will take a long, long time to reveal themselves. Testing will not reveal them. Using Beta versions will not reveal them. Fifty years of use will not reveal them. They’re still there.

    [This Section is a short extract from my course Principles of Safe Software Development.]

    Conclusion

    Legal experts stress the urgency of updating laws to reflect the fallibility of computers, crucial for ensuring fair trials and preventing miscarriages of justice. The UK Ministry of Justice acknowledges the need for scrutiny, pending the outcome of the Horizon inquiry, signaling a potential shift towards addressing issues of computer reliability in the legal framework.

    Hopefully, the legal people will come to realize what software engineers have known for a long time.  Software reliability is difficult to achieve and must be demonstrated.