On this page we transcribe and summarise the audio below.
http://transcript.thought.garden/assets/perspective-and-authorship/Perspective And Authorship.wav Perspective And Authorship
# Summary
The audio note titled "Perspective and Authorship" describes the Collective Intelligence platform, which has been largely built to illustrate the structure and function of partner projects. It explains the importance of perspective and authorship in creating and managing knowledge graphs, which are vital to the governance and incentive structures of these projects. It also highlights the use of dynamic equity to distribute value among contributors, emphasizing the importance of forking and merging to accommodate different perspectives and foster dialogue. The note further expands on the concept of perspective, likening it to viewing the same object from different angles and sharing the resulting insights to enrich the collective understanding. The note delves into the technicalities of implementing these concepts using version control language like Git, which allows for forking and merging of knowledge archives. The emphasis is on maintaining the integrity of authorship even as the original content is modified and added upon by others in the Collective Intelligence hypergraph. It also underscores the importance of creating a common language, and the value and power harnessed from doing so. The note concludes by highlighting the critical role that perspective and authorship play in creating a lifelike system that grows and evolves with continuous feedback and improvement.
# Tidied Transcript
This audio note, titled "Perspective and Authorship," is essentially a detailed technical description of how audio notes will be used within the Collective Intelligence platform that I have largely built to date. This platform utilizes the structure of partner projects it was built with and upon, and maps to governance relationships and incentive structures, such as dynamic equity. The audio note relates to the initial perspective of an audio note in the Astral Stories channel. Schick created a note, number 36, titled "Astral Ship" and I wanted to add to that concept. So, I created another audio note, number 36B, titled "Relationship," indicating that I considered them to be the same node in the Collective Intelligence hypergraph or knowledge graph. This different perspective is technically what we would call a perspective. This model enables us to look at a node from different angles or perspectives. It was initially viewed from Schick's position, and then someone else comes along and views it from a different spatial orientation or perspective. The technical implementation involves a tree of forks in version control language. For example, in Git, I can take a particular organization of knowledge, which includes the document that Schick added, called "Astral Ship," and I can fork it. I can then add new content above, below, or into the folder that the document is in. I now have a slightly different version of that knowledge archive than Schick has. Schick can pull that forked version from my personal storage and merge that back into his structure, thus incorporating both his and my contributions to that node. This process of forking and merging promotes a dialogue between the minds, resulting in knowledge nodes that are composed of numerous perspectives. The structure of these forks can become complex as we move into the future. We require enough structure now to make a pragmatic start, which we get from replicating the structure of federation built into federated wiki. Each node has a name with certain complex attributes. Technically, it should have an immutable ID and there are various ways of thinking about that ID. However, our name is more web-orientated, which is a title, a short title, ideally a memorable phrase. This title is canonicalized to lowercase and hyphenated for consistency. The title of the wiki page is the link that holds the pages together, and it also resides under a domain. This naming structure allows us to keep these different forks of the same object and infinitely fork them to your own domain or space. This structure is important because it allows us to assign value to each contribution. In the future, if a contributor feels that their contribution has been undervalued, there needs to be a process where they can raise their concern. This process can be creative and can contribute to improving the system. The system is lifelike and is based on perspective, authorship, and accreditation. The structure of perspective and authorship needs to process not just text and code, but also videos and audios. We're doing that by transcribing these audios, summarizing them, and then editing them. We're also writing code to do this automatically and improving that code, choosing which AI model to use. This code is useful because it's got all sorts of functions you can call to do things. We start by transcribing these audios, which means creating AI to do that and summarizing the audios. We put them in their own perspective space, their own author-owned perspective space. We then have AI to take these three perspectives and generate a summary of all the different texts. An editorial process then looks at that AI-based summary and tidies it, improves it, or discards it and rewrites it. Then that becomes the outside of this folder or DAO. In closing, the important thing is we can start by transcribing these audios, which means creating AI to do that, summarizing the audios and then editing them. We put them in their own perspective space, their own author-owned perspective space. Then we have AI to take these three perspectives and generate a summary of all the different texts. An editorial process then looks at that AI-based summary and tidies it, improves it, or discards it and rewrites it. Then that becomes the outside of this folder or DAO.
# Keywords Collective Intelligence platform, perspective, authorship, knowledge graphs, governance structures, dynamic equity, forking, merging, Git, version control language, common language, lifelike system, continuous feedback
# Graph
digraph { layout=fdp; "Collective Intelligence platform" -> "perspective"; "Collective Intelligence platform" -> "authorship"; "Collective Intelligence platform" -> "knowledge graphs"; "perspective" -> "knowledge graphs"; "perspective" -> "dynamic equity"; "authorship" -> "dynamic equity"; "authorship" -> "forking"; "knowledge graphs" -> "forking"; "knowledge graphs" -> "merging"; "forking" -> "Git"; "merging" -> "Git"; "forking" -> "common language"; "merging" -> "common language"; "Git" -> "lifelike system"; "common language" -> "lifelike system"; "lifelike system" -> "continuous feedback"; }
# Assets
perspective-and-authorship
# See also - Voice Notes
# Tools
The tools below will use generative AI to edit the contents of the page displayed above.
Tidy the raw transcript with generative AI: