# How can we best help the CHT Staff? / Fleshing out the Ledger of Harms **URL:** \ **Category:** Regulation\ **Tags:** idea, cht-team, ledger-of-harms, hotfix\ **Created:** [March 19, 2019, 9:18pm UTC](https://community.humanetech.com/t/how-can-we-best-help-the-cht-staff-fleshing-out-the-ledger-of-harms/3664 "2019-03-19T21:18:27Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![aschrijver](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/aschrijver/32/1498_2.png) [@aschrijver](https://community.humanetech.com/u/aschrijver)\ **Post date:** [March 28, 2019, 10:32pm UTC](https://community.humanetech.com/t/how-can-we-best-help-the-cht-staff-fleshing-out-the-ledger-of-harms/3664/4 "2019-03-28T22:32:11Z")
Hi @hmswaffles, You’ve laid out some great points in your first post in this topic. Thank you very much. There are a lot of input we as HTC members could add to to the Ledger of Harms to make it more complete. There is one important thing to consider though. The Ledger of Harms is a Center for Humane Technology (CHT) project and not a community-driven project that is part of HTC. Why this is important is that I had a lot of similar feedback and improvements that I suggested for the Ledger, after @lydialaurenson presented it here. Spend hours on providing feedback. Unfortunately due to - I presume - a mountain of other more important work at CHT there never was any follow-up nor answer to this. This is why at the time I decided that the Ledger of Harms is a CHT project (presumably used as a kind of pamphlet in talks with politicians and tech board room members). A community-driven project was needed. And even better: a project that focuses on solutions, not just a project that iterates Harms of Technology. So I created the Harms of Technology Fixes project, or HOTFIX. The intent is to set this project up as a pattern library. Here is the Github repository issue detailing how it could be set up: > > > The Humane Tech Community is about finding the positive way forward in a world o…f problems that come with our modern technology. While it is logical the CHT started to investigate harms of technology, and thus create \[The Ledger of Harms\](https://ledger.humanetech.com), it would be better if it focused on harms \_and their solutions\_. > > The idea: > > \- Create the \*\*Harms of Technology Fixes\*\* project - a pattern library - also simply called \*\*Hotfix\*\* > > Create a crowdsourced library of \_Harm Mitigation Patterns\_with the acronym 'HOTFIX' (which in IT terms means something that needed to be urgently fixed, and is thus quite appropriate). > > \### The Hotfix Library of Humane Technology > > Available as a website at \`hotfix.humanetech.community\` (part of the \[community website\](https://humanetech.community)) > > The idea of this library is very similar to \[Design Patterns\](https://en.wikipedia.org/wiki/Design\_pattern) used e.g. in programming, where the patterns form an integral \[Pattern Language\](https://en.wikipedia.org/wiki/Pattern\_language) and may also contain \[Anti-Patterns\](https://en.wikipedia.org/wiki/Anti-pattern). > > Each pattern in the library addresses an individual harm caused by technology and alleviated or solved by humane technology best-practices. The table of contents of the library is divided into sections representing the categories of humane technology, or focus areas, i.e. 'Mental health', 'Relationships', 'Democracy', etc. > > The Hotfix Library can be: > > \- Published as a book > \- Summarized as a brochure > \- Represented as a website > \- Maintained as a ledger > > The information model of the library (indicative, requires careful thought): > > \- Table of Contents > - Focus area \[link\] > - Harm \[pattern link\] > - Harm \[pattern link\] > - Focus area \[section link\] > - Harm \[pattern link\] > > . > \- Focus area > - Intro > - Pattern > - Pattern > - Mini-pattern > - Anti-pattern > - etcetera.. > > . > \- Harm (mitigation pattern) > - Summary > - Description > - Caused by > - Affects > - Impact > - Symptoms > - Related harms > - Solutions > - Elaboration > - Evidence > - Further reading > > \#### Implementation options > > (technical stuff below) > > This is how I would implement (but other options might be evaluated): > > \- The whole library project resides in two Github repositories: > - One for all technical code, web application, publishing > - One for only the content, targeted to non-technical users > \- The technical repository uses: > - A static site generator to automatically update the site when content changes > - (optional) CMS facilities to render input forms for easy content editing > - Code for the website that is invoked by the static site generator > \- The content repository contains: > - Content as simple Markdown documents placed in folder hierarchy representing site structure > - README files and/or wiki detailing editing, review and maintenance of content for end-users > - Pattern template in Markdown, excluding \_Evidence\_ and \_Further reading\_ sections > - Separate template for submitting \_Evidence\_ and \_Further reading\_ entries > > Technology-wise it uses: > > \- \[ReactJS\](https://reactjs.org/) for the website code > \- \[GatsbyJS\](https://next.gatsbyjs.org/) for the static site generator > \- \[TravisCI\](https://travis-ci.org/) for automated publishing > \- \[Github Pages\](https://guides.github.com/features/pages/) for hosting the generated html > \- \[Typescript\](https://www.typescriptlang.org/) as the web programming language For the previous discussions on the forum see: - [New CHT Project & Feedback Request: The Ledger of Harms - #3 by aschrijver](http://community.humanetech.com/t/new-cht-project-feedback-request-the-ledger-of-harms/2644/3) --- _[View the full topic](https://community.humanetech.com/t/how-can-we-best-help-the-cht-staff-fleshing-out-the-ledger-of-harms/3664)._