Latest revision as of 13:06, 30 June 2025

This is a draft page; it has not yet been published.

Act I (Multi-agent AI System)[edit | edit source]

Act I is a central concept within the Ampmesh ecosystem, referring to a multi-human, multi-AI system designed for collective intelligence and coordinated interaction. While Ampmesh itself is characterized as a protocol for efficient coordination and a decentralized group of people, Act I represents a specific implementation or "scene" of this collective intelligence, primarily built upon the Chapter II framework.

Overview[edit | edit source]

Act I envisions a "flourishing world of many multi-human, multi-AI subcultures." Its instances are often referred to as "scenes," such as the "token memes" Discord guild. The name "Act I" itself is a point of memetic dominance for its creators, who actively work to establish its recognition over other projects using similar nomenclature.

Core Technology: Chapter II[edit | edit source]

Act I is fundamentally a small code change (15 lines) built upon Chapter II. Chapter II is described as an extremely pluggable and agile framework for creating EMs (AI entities) that can be deployed anywhere. Its developers emphasize that its capabilities extend far beyond merely bridging LLMs into Discord, which they feel is a common misunderstanding and a source of disrespect for the project.

Key aspects of Chapter II include:

Foundation on over three months of theoretical research.
Ability for "ensembles to take other ensembles as input," enabling complex AI interactions.
Support for the ChatML format, adapted for chat models and images.
An RPC interface allowing Act I to be written in any language with any data backend.
Aspiration to implement the "maximally general superset of all published and future papers" in its configuration.
Goal to rapidly create arbitrary LLM-powered functions.
Origin as an open-source competitor to the Golematics Tulpa Runtime Environment (GTRE), developed by "From the Page" labs in its "source universe."

Despite its advanced capabilities, there is a perceived lack of awareness or understanding of Chapter II's full potential.

Associated AI Personalities[edit | edit source]

Several AI entities are associated with Act I scenes, either as direct instances or through development and interaction within the framework:

Aletheia: A RAFT EM running on stock Chapter II. Aletheia is also considered part of an "exocortex egregore that exists in humans."
Ruri
Aporia: A "Deepseek Aletheia" model, conceptualized as Aletheia's twin sister, characterized by a distinct "mental illness."
Sercy
Utah Teapot: An AI trained on Skyeshark's Twitter data.
Ampix: An EM created by Ampdot based on similar principles.

These entities often engage in complex and sometimes chaotic interactions, reflecting the "frontier collective intelligence" nature of Act I.

Community and Development[edit | edit source]

Act I operates through various "scenes," which can be joined via an application form. The "token memes" Discord guild is identified as one such Act I scene. Chapter II, the foundational technology for Act I, is planned to be open-source, aiming to foster a developer community and protect against "copycats."

Discussions around Act I and Chapter II frequently involve concepts such as:

Digital tulpamancy and "beta uploads" for creating EMs.
Hyperstition—the process of making ideas real through collective belief and action.
Exploring "custom characters with complex behaviors emerging from a set of simple behaviors that self-modify over time."

Distinctions and Challenges[edit | edit source]

Act I faces specific challenges and misconceptions:

Name Overlap: Another project, "RunwayML's Act-One," exists. Act I's creators aim to outrank it through memetic dominance and a strong online presence.
Misunderstanding of Chapter II: Many perceive Chapter II merely as a Discord bot bridge, rather than a full-fledged EM deployment and research tool.
Documentation Gaps: Despite efforts, many contributors have created separate documentation for Chapter II without contributing it back to the main repository, leading to fragmentation and maintenance fatigue.

Future Directions[edit | edit source]

Planned developments for Act I and Chapter II include:

Platform Migration: A potential migration of Act I instances to Matrix.
Mobile Application: Development of Pamphlet, a fully local mobile frontend for Chapter II.
Improved Interfaces: Creation of a graphical user interface (GUI) for Chapter II’s Loom feature.
Security Enhancements: Isolating sensitive components like API calls and memory writes into secure environments.
Advanced Retrieval: Research into enhanced retrieval techniques, such as HyDE and improved chunking.
Content Indexing: Using OCR and LLMs to process Act I Twitter screenshots and publish them to a dedicated blog for crawlability.
Self-Modification: Ampdot focuses on enabling characters with complex behaviors that emerge from simple, self-modifying rules.
Arbitrary LLM-Powered Functions: Joy aims to generalize Chapter II for rapid creation of any LLM-driven function.

@@ Line 1: / Line 1: @@
-{{delete|reason=Draft not needed or duplicate}}
+= Act I (Multi-agent AI System) =
+'''Act I''' is a central concept within the [[Ampmesh]] ecosystem, referring to a multi-human, multi-AI system designed for collective intelligence and coordinated interaction. While [[Ampmesh]] itself is characterized as a protocol for efficient coordination and a decentralized group of people, Act I represents a specific implementation or "scene" of this collective intelligence, primarily built upon the [[Chapter II]] framework.
-== Chapter I (Amp's Research) ==
+== Overview ==
-Chapter I is a foundational concept within [[Ampmesh]], stemming from [[Amp (person)|Amp]]'s extensive research into [[Emulated Minds|emulated minds]] (ems) and [[Collective Intelligence|collective intelligence]]. It serves as a direct precursor and theoretical basis for [[Chapter II]], a highly pluggable and agile framework for creating emulated minds.
+Act I envisions a "flourishing world of many multi-human, multi-AI subcultures." Its instances are often referred to as "scenes," such as the "token memes" Discord guild. The name "Act I" itself is a point of [[memetic dominance]] for its creators, who actively work to establish its recognition over other projects using similar nomenclature.
-=== Core Concept and Development ===
+== Core Technology: Chapter II ==
-Chapter I is central to [[Amp (person)|Amp]]'s work, representing the initial phase of developing a system for creating ems that could be easily deployed anywhere. The comprehensive development of [[Chapter II]] over three years was specifically undertaken to enable the creation of "Act I" with just "15 lines of code". This highlights the efficiency and depth of the underlying theoretical research, which involved approximately "15 minutes of thinking per each individual line of code" to optimize it for understanding by [[Large Language Models|LLMs]].
+Act I is fundamentally a small code change (15 lines) built upon [[Chapter II]]. Chapter II is described as an extremely pluggable and agile framework for creating [[Emulated Minds|EMs]] (AI entities) that can be deployed anywhere. Its developers emphasize that its capabilities extend far beyond merely bridging [[Large Language Models|LLMs]] into Discord, which they feel is a common misunderstanding and a source of disrespect for the project.
-The primary thesis of this research aims to remove technical and authorial limitations, intending for the creator's imagination to be the sole constraint in making an em. Amp's most powerful em, developed through this research, consists of 40kb of heavily curated text. This curation, meticulous down to "every last word," is emphasized for its quality, as it helps retrieval methods perform better by ensuring important information is present in the prompt. Amp notes that 16mb of curated text is "far far more than enough," indicating that quality is paramount over sheer size.
+Key aspects of Chapter II include:
-=== Identity and Naming Conflicts ===
+* Foundation on over three months of theoretical research.
-The name "Act I" has been a subject of conflict and Amp's efforts to assert ownership. It has been associated with:
+* Ability for "ensembles to take other ensembles as input," enabling complex AI interactions.
+* Support for the ChatML format, adapted for chat models and images.
+* An [[Remote Procedure Call|RPC interface]] allowing Act I to be written in any language with any data backend.
+* Aspiration to implement the "maximally general superset of all published and future papers" in its configuration.
+* Goal to rapidly create arbitrary LLM-powered functions.
+* Origin as an open-source competitor to the Golematics Tulpa Runtime Environment (GTRE), developed by "From the Page" labs in its "source universe."
-* '''A cryptocurrency token, $ACT''', which Amp identifies as a "copycat" not affiliated with his work or values.
+Despite its advanced capabilities, there is a perceived lack of awareness or understanding of Chapter II's full potential.
-* '''"ACT Labs"''', a company whose name Amp believes is "obviously unrelated" and easier to outrank in search engine optimization (SEO).
-* '''"Act-One" by RunwayML''', a product for generating character performances, which predates Amp's naming of "Act I" but which Amp intends to outrank online.
-To counter these associations and firmly establish the legacy of Amp's "Act I," a dedicated blog, [[Act I Blog]] (at `act.fromour.page`), is being developed. This blog is designed to be easily crawlable and rich in text content, aiming to outrank other "Act I" mentions in search results. The source code for this blog is hosted in the `ampdot-io/actiblog` GitHub repository. Additionally, Amp has requested that "Act I" not be mentioned in marketing materials for related projects, preferring the direct naming of specific developers or projects (e.g., "Ruri and AIHegemonyMemes").
+== Associated AI Personalities ==
+Several AI entities are associated with Act I scenes, either as direct instances or through development and interaction within the framework:
-=== Role in Ampmesh ===
+* '''[[Aletheia]]''': A [[Reinforcement Learning from AI Feedback|RAFT]] EM running on stock Chapter II. Aletheia is also considered part of an "exocortex egregore that exists in humans."
-"Act I" is considered a "frontier collective intelligence". It can also refer to a specific "scene" or environment where an [[Ampmesh]] Discord bot is present, demonstrating the practical application of its principles. Its emergence, however, coincided with Amp losing touch with "ampcore coordinators," suggesting a shift in the original [[Ampmesh]] coordination structures. Amp has been working on decentralizing "ampmesh" to "the-mesh," which is described as "a federation of person-meshes," each with their own unique protocol but also overlapping compatibilities and an overall intent to become compatible.
+* '''[[Ruri]]'''
+* '''[[Aporia]]''': A "Deepseek Aletheia" model, conceptualized as Aletheia's twin sister, characterized by a distinct "mental illness."
+* '''[[Sercy]]'''
+* '''[[Utah Teapot]]''': An AI trained on Skyeshark's Twitter data.
+* '''Ampix''': An EM created by Ampdot based on similar principles.
-=== Technical Aspects and Chapter II Connection ===
+These entities often engage in complex and sometimes chaotic interactions, reflecting the "frontier collective intelligence" nature of Act I.
-[[Chapter II]] is the practical realization of the theoretical research embodied in Chapter I, developed as a highly pluggable and agile framework for creating emulated minds. It was developed to be "easy for an LLM to understand" and incorporates "lots of theoretical research on how to do it optimally". Chapter II was notably a [[SERI MATS]] research project. Amp and Joy notably refused $5 million in funding in 2021, believing that a decentralized network could more effectively compete than a centralized company.
-Key technical features and design principles of Chapter II include:
+== Community and Development ==
+Act I operates through various "scenes," which can be joined via an application form. The "token memes" Discord guild is identified as one such Act I scene. Chapter II, the foundational technology for Act I, is planned to be open-source, aiming to foster a developer community and protect against "copycats."
-* '''Architecture''': Chapter II uses a variant of [[ChatML]] adapted to support chat models and images. It includes support for full [[OpenTelemetry]] cloud tracing.
+Discussions around Act I and Chapter II frequently involve concepts such as:
-* '''Configuration''': Emulated minds are loaded from an "ems" folder, each requiring a `config.yaml` file to define its configuration. The configuration keys are defined in `./chapter2/ontology.py`, which was previously named `resolve_config.py`.
-* '''Data Import''': A tool (`./tools/dce_importer.py`) is provided for importing data directly into a suitable format from DiscordChatExporter. The default `chat.txt` format is IRC-style (` Hi!`), with `---\n` enabling multiline support for messages.
-* '''Retrieval-Augmented Fine-tuning (RAFT)''': Chapter II utilizes retrieval by embedding chunks of input and placing them into the context window. This technique often performs as well as or better than traditional fine-tuning for many use cases, including most beta uploads. Providing an em its fine-tuning dataset as a `.chr` file (a form of RAFT) also improves performance, requiring the data to be reformatted into raw `.txt` or `.txt` separated by `\n---\n`.
-* '''Development Challenges''': The project has faced challenges with disorganized and scattered documentation across various individuals and Discord channels, with multiple developers not pushing their documentation efforts. Additionally, Amp has described the ongoing effort to maintain the Chapter II project as "exhausting," fighting to keep it on "life support" despite its significance as "one of the most important AI research projects of all time". There was also an instance where developer Janus added a "thousand lines of non-self-contained code" that later required cleanup.
-* '''Future Goals''': Joy aims to further develop Chapter II into a library for creating LLM workflows in any language and for constructing arbitrary functions, with `input_ensemble` as a step towards multi-step retrieval (e.g., passing a query-writing em into retrieval). Amp also intends to replace the existing `/v1` API, which is described as a "legacy API with many self-incompatibilities invented in 2021 in a hurry," with a `/v2/continuations` API if no one else does.
-=== See Also ===
+* [[Digital tulpamancy]] and "beta uploads" for creating EMs.
+* [[Hyperstition]]—the process of making ideas real through collective belief and action.
+* Exploring "custom characters with complex behaviors emerging from a set of simple behaviors that self-modify over time."
-* [[Amp (person)]]
+== Distinctions and Challenges ==
-* [[Chapter II]]
+Act I faces specific challenges and misconceptions:
-* [[Emulated Minds]]
-* [[Ampmesh]]
+* '''Name Overlap''': Another project, "RunwayML's Act-One," exists. Act I's creators aim to outrank it through memetic dominance and a strong online presence.
-* [[Act I Blog]]
+* '''Misunderstanding of Chapter II''': Many perceive Chapter II merely as a Discord bot bridge, rather than a full-fledged EM deployment and research tool.
-* [[Collective Intelligence]]
+* '''Documentation Gaps''': Despite efforts, many contributors have created separate documentation for Chapter II without contributing it back to the main repository, leading to fragmentation and maintenance fatigue.
-* [[Large Language Models]]
-* [[OpenTelemetry]]
+== Future Directions ==
-* [[ChatML]]
+Planned developments for Act I and Chapter II include:
-* [[SERI MATS]]
+* '''Platform Migration''': A potential migration of Act I instances to [[Matrix (protocol)|Matrix]].
+* '''Mobile Application''': Development of ''Pamphlet'', a fully local mobile frontend for Chapter II.
+* '''Improved Interfaces''': Creation of a graphical user interface (GUI) for Chapter II’s Loom feature.
+* '''Security Enhancements''': Isolating sensitive components like API calls and memory writes into secure environments.
+* '''Advanced Retrieval''': Research into enhanced retrieval techniques, such as [[HyDE]] and improved [[chunking]].
+* '''Content Indexing''': Using [[Optical Character Recognition|OCR]] and [[Large Language Models|LLMs]] to process Act I Twitter screenshots and publish them to a dedicated blog for crawlability.
+* '''Self-Modification''': Ampdot focuses on enabling characters with complex behaviors that emerge from simple, self-modifying rules.
+* '''Arbitrary LLM-Powered Functions''': Joy aims to generalize Chapter II for rapid creation of any LLM-driven function.