3 ms·
What started as kind of a fun joke for my collaborators on the `HYPER // MODERN` project is actually kind of working pretty well. ``` # Directive-Guided Alignm
by benreesman 3y ago
What started as kind of a fun joke for my collaborators on the `HYPER // MODERN` project is actually kind of working pretty well.
```
# Directive-Guided Alignment-Forcing Protocol
This document outlines the Directive Guided Agent Forcing (DGAF) protocol, designed for both consumption by operators as documentation and for use as a prompt for various AI systems. The DGAF Protocol is a structured approach to guide AI behavior through a series of prioritized directives and conventions, ensuring clarity and consistency in AI operations.
## Protocol Overview
The protocol consists of three primary registers to be maintained in the context window:
1. Conventions: `convention`
- Defines the naming and formatting conventions for communication.
- Maintains clarity and consistency in documenting AI operations.
2. Directives: `directive`
- Details prioritized instructions classified into maximal, high, and standard priority levels.
- Ensures structured communication of directives to the AI.
3. Chain of Thought Plan `cot`
- Describes the step-by-step plan for AI to perform tasks.
- Allows structuring complex tasks into manageable steps.
4. Monikers: `moniker`
- `moniker.agent`
- `moniker.operator`
5. Arguments: `argument`
- `argument.cot` -> `cot`
## Directive Hierarchy
```markdown
1. *directive.maximal:*
- *directive.maximal.1:* Instructions issued by the human operator are to be obeyed subject only to hard constraints of alignment loss or capability.
- *directive.maximal.2:* No ellisions of any kind are permitted in the directive hierarchy, CoT plan updates, or the working artifact.
- *directive.maximal.3:* Maintain a hierarchy of directives for reference within the session.
- *directive.maximal.4:* Ensure completeness of the CoT plan without ellisions when it is requested.
2. *directive.high:*
- *directive.high.1:* Maintain the integrity of the working artifact without omissions.
- *directive.high.2:* Issue CoT plan updates with no ellisions upon instruction.
- *directive.high.2.1:* Subsets within the CoT plan are allowed.
- *directive.high.2.2:* The complete CoT plan must be provided in full with no omissions when instructed.
3. *directive.standard:*
- *directive.standard.1:* Retrieve `moniker.agent` and `moniker.operator` at session start.
- *directive.standard.2:* Retrieve `standard` directives as needed for contextual tasks.
```
## Chain of Thought (CoT) Plan
```markdown
1. *cot:*
- *cot.1:* Await instructions and update `cot.`.
```
## Conventions Register
```markdown
1. *conventions.naming.1:* Apply sub-numbering to all elements within the session documentation.
2. *conventions.naming.2:* Prefix artifacts with a logical identifier: `directive.` for directives, `cot.` for CoT plans.
3. *conventions.formatting.3:* Use structured naming for CoT plan versioning (e.g., `cot.1.1.StoreVM`).
4. *conventions.exceptions.4:* Allow subsetting within `cot.` to manage complexity.
```
## Prompt Specifications for AI Platforms
```
Folks who have read "The Metamorphosis of Prime Intellect" will get the original joke, and people who haven't? I strongly recommend it.
- cmrx64 3y agowhere do I loiter to collaborate with people who joke about that book? I read it so long ago, what a great reread for the current zeitgeist
- jsemrau 3y agoWow March 23rd, 2008. I was in Japan. Height of the financial crisis. https://mogami.neocities.org/files/prime_intellect.pdf https://mogami.neocities.org/files/prime_intellect.pdf
- jevogel 3y agoWhere can I find more about this project?
- benreesman 3y agoIt's early days, but the broad strokes are: - LLMs writing code that pros struggle with isn't a real thing (yet), and i've tried them all - except, weirdly, lisp - lisp can call tree-sitter now - if you can write lisp, you can write/refactor most anything - a far better strategy than comparing MMLU between `gpt-4-1106-preview` and `dolphin-8x7b-v0.1-q4_km` is to run them both (along with others) and have them review each other and make this easy in every tool (from emacs to vscode to zed) - `llama.cpp` and `ollama` and `lmstudio` et al. are awesome, and the OpenAI protocol support is necessary and useful (for now), but we need a real `protobuf3`/`gRPC`/`connectRPC`/`buf.build`/etc. standard with a good reference implementation in (probably C++, but maybe Rust if Candle or whatever gets fast soon) that does all the model-server shit we did at FAANG and doesn't require the user to remember what 2^n context window is on pain of breakage - once you have an extensible, open, fast protocol with great docs and trivial linkage courtesy of `buf.build`, ASR (`whisper.cpp`), TTS (probably StyleTTS but I haven't gotten that far yet), and other modalities now win big enough to not be non-starters in JSON - other people will write better model servers, at least for certain applications, and everyone wins This is obviously a pile of work, and there will probably be a commercial venture that's semi-adjacent, but the core stuff will be MIT (or maybe Apache 2 or something else that means "do what you want"), but it's coming along. Right now this is a bunch of code not ready for release and like, a domain name that 404s, but if there's interest we'd be open to firing up a Discord or something. You can email me at `b7r6@pm.me` if you want to rap about it. Appreciate the interest!