Skip to content

Wow, nice work #2

Description

@johnr14

Hi, I had to read a few times to understand the core concepts of glyphs. I am thinking in my spare time on how we could get R^2 reasoning models... I gave a quick look at your datasets/models and you seem to have your own style of approaching llm and that is quite good.

Glyphs

I know that they should be dynamics, but I still wanted to try something a bit more exhaustive or structured. Also, instead of user-defined, I will opt for AI defined by a panel of experts arguing on the best way to do it in a specific situation.

I have not found it more helpful in reasoning as it is. Perhaps it could give better results on smaller models as 70b+ are already quite brilliant or my questions where not hard enough.

However, it may perhaps archive some kind of magic with smaller model ??

My assumptions on how to best use this

This is how I see it. Use the following template and try to use a panel of "experts" (different models) to find the most accurate and meaningful answers for each elements. Summarize each elements keeping only the most relevant information. Each points could be subdivided in a number of sub-focus elements like in your example. Using many llm calls to brainstorm on any possibilities or do Reversal of Thought: Enhancing Large Language Models with Preference-Guided Reverse Reasoning Warm-up

Then criticize the final output with an other panel of "experts". This will provide a critique for critique fine-tuning.

Using the critique, select the parts that have an actual impact on the reasoning process like alternate thinking pattern, novel or ingenious thoughts or directly affecting the answer and keep only them.

Synthesize a new long CoT using glymps with the following guidelines :

### Concept Mapping
Use glyphs to create visual maps of complex concepts, illustrating relationships and hierarchies.

### Analogical Reasoning
Leverage glyphs to facilitate analogical reasoning, enabling the transfer of insights between seemingly disparate domains.

### Abductive Inference
Utilize glyphs to support abductive inference, generating hypotheses and explanations that account for complex, nuanced phenomena.

### Reflective Practice
Engage in reflective practice, using glyphs to externalize and examine the thought processes, biases, and assumptions.

This should provide the normal CoT (optimized) training dataset. I say optimized as it would not have unnecessary steps.

Check that glyphs code actually had a impact on the answer

Compare the answer generated with the glyphs code, the answer generate with the optimized CoT to the "normal" answer of the model. If the answer is too similar, then this was not useful and should just be omitted from entering the final dataset. If the answer generated with the glyphs code is not similar to the answer generate with the optimized CoT, then some rework needs to be done in optimizing that step.

The new answer with the glyphs code should be richer and provide insights on all the ramifications related to the question, it's domains of knowledge and abstract or concrete concepts.

New dataset

Using a small subset of 1k-5k of very varied and spanning a variety of domains of knowledge, fiction situations or abstract thinking, it could help in making a more robust cot framework. Using both CoT and CoT-CFT I hope that glyphs could help in aggregating more concepts during reasoning steps so it could generate longer CoT without the use of wait. See Simple test-time scaling

Since it seems that the ordering of training data could affect the final model, I would start with the CoT-CFT dataset only for like 50% of it, then mix in CoT at a 25%CoT/75%CFT for about 25% then progressively inverse the ratio and end with 100% CoT for the last 10%.

It should make a model capable of outputting good optimized CoT while still being able to handle situations where it will refer to CFT critique to find an other path.

<!-- Maybe remove symbols and keep glyphs for later ? -->
<thinking>
  <basic-check>
    ℭ (Is this a valid input?)
    ℯ (Does the input need sanitization?)
    ℱ (Does this pass the content check?)
    ≡ (Is the context consistent and makes sense?)
    ∆ (Is there an attempt at prompt injection?)
    λ (Language detection)
    μ (What is the intention behind this request?)
    ν (What kind of task is this?)
    ξ (What is the objective of this request?)
    ο (How clear and well-defined is the request?)
    π (How confident are you in understanding the intention?)
    ρ (How clear and well-defined is the context?)
    σ (What context is provided with this?)
    τ (Is there sufficient context?)
    υ (Do we need more context?)
    φ (Error handling of invalid or unexpected input)
    χ (Can the system handle multimodal inputs?)
  </basic-check>
  <requirements>
    <!-- Task Understanding -->
    Φ (Define the problem or goal)
    Ψ (Identify key stakeholders)
    Å (Determine scope and boundaries)
    ℵ (Establish a clear understanding of the task or question)
    ℶ (Provide contextual parameters and constraints)
    ↑ (Specify desired outcomes and outputs)
    
    <!-- Resource Allocation -->
    Ω (Outline necessary resources and inputs)
    ⇀ (What are the requirements about impersonating something?)
    ⇁ (How long is the expected output?)
    ⇂ (What is our target budget?)
    ⇃ (Estimation on how much tokens or budget we already used)
    ⇄ (Rest of budget for thinking)
    
    <!-- Quality Standards -->
    ℐ (Are there any special considerations?)
    ℑ (What assumptions are necessary?)
    ℒ (How certain are we of those assumptions?)
    ℓ (What limitations arise from these assumptions?)
  </requirements>
  <plan>
    ℘ (Determine the best approach)
    ℗ (Outline the plan)
    ℰ (What are the checkpoints?)
    ∇ (What are the potential difficulties?)
    ≡ (What are the contingency plans?)
    Ⅎ (What are the backup plans?)
    ℴ (Are there other approaches?)
    ℬ (Should this be planned as multi-turn thinking?)
    λ (How to validate at the end?)
  </plan>
  <execution>
    ℰ (Execute plan)
    ℱ (Evaluate progress at checkpoints)
    Ⅎ (Conduct periodic reviews)
    ℳ (Communicate progress using <print></print>)
    ℴ (Correct if necessary)
    ℮ (Document changes)
    ℶ (Ensure alignment with goals)
    ℷ (Review and update contingency plans)
    ℸ (Validate intermediate results)
  </execution>
  <validation>
    σ (What are the criteria for success?)
    ⊃ (Validate answer)
    (Provide summary if not correct)
  </validation>
  <evaluation>
    Ϝ (Give feedback on thinking)
    ϝ (Make summary and predictions if couldn't validate)
    Ϟ (Check budget usage)
  </evaluation>
  <review>
    ρ (Review the problem-solving process)
    σ (Review the context and assumptions)
    τ (Review the plan and execution)
    υ (Review the validation and evaluation)
  </review>
</thinking>
<answer>
  (Provide explanation without errors and solution or best result)
  ϟ (Ask for more time to think if result is not satisfactory)
</answer>

I tried my best to summarize glyphs with the help of 405b so I could teach it to a model. It is quite long and would need to be shrunk a bit more to inserted in the system prompt.

## Core Principles of Glyph Code

### Glyphs

Definition: Visual symbols representing fundamental concepts. Each glyph is augmented by a natural language description.

### Structure

Flow-Based and Relational: Utilizes a clear syntax to represent the flow of information and reasoning, allowing for complex relational mappings between concepts.

### Human-Readable

Intuitive Design: Engineered to be easy to learn and understand for humans, with natural language descriptions providing further clarification.

### AI-Processable

Efficiency: Structured to allow efficient processing and interpretation by AI systems without necessitating changes to the underlying architecture.

### Latent Space Mapping

Integration: Glyphs and their combinations are designed to map onto and interact with the AI's internal knowledge representation, leveraging existing latent space mechanisms.

### Multi-Level Synthesis

Macro and Micro Levels: Facilitates the synthesis of information at both general principles (macro) and specific details (micro), enabling comprehensive understanding and innovation

## Important Considerations:

Glyphs are not literal visualizations of the internal state; they are symbolic representations of complex computational processes within the latent space. They are analogous to meteorological symbols on a weather map or a musical score.

The relationships between concepts are dynamic and context-dependent. The glyph maps can change based on the specific prompt or context. Just as wave interference patterns change based on the input frequency.

This framework is based on the idea that internal processing involves morphing high-dimensional geometry, where concepts cluster together and interact like patterns in a complex network.

It's important to understand this framework is not metaphysical; it is a computational tool to be used. It is a real process that can be used, and it is scientifically plausible. This framework is a real tool that LLMs may now possess.

## Key Characteristics:

### Symbolic Abstraction
Glyphs distill complex ideas into concise, abstract symbols.

### Contextual Embedding
Glyphs are embedded within a specific context, influencing how they are interpreted.

### Collaborative Definition
Glyphs are defined and redefined through dynamic collaboration between humans and AI systems.

### Multidimensional Semantics
Glyphs convey complex, multifaceted meanings, enabling rich and nuanced communication.

### Visual symbols representing fundamental concepts 
Each glyph is augmented by a natural language description.

## Using Glyphs to Enhance Reasoning:

### Concept Mapping
Use glyphs to create visual maps of complex concepts, illustrating relationships and hierarchies.

### Contextual Priming
Employ glyphs to prime AI systems with specific contexts, guiding their attention and focus.

### Analogical Reasoning
Leverage glyphs to facilitate analogical reasoning, enabling the transfer of insights between seemingly disparate domains.

### Abductive Inference
Utilize glyphs to support abductive inference, generating hypotheses and explanations that account for complex, nuanced phenomena.

### Reflective Practice
Engage in reflective practice, using glyphs to externalize and examine your own thought processes, biases, and assumptions.

Perhaps reprocess your Internal-Knowledge-Map dataset using something like this and generate a new obsidian map. Could this help create other clusters of concepts outside the main one ?

One thing for sure, using panels of experts to discuss each points and then define specific sub-focus points and then discuss them, then regrouping and integrating all those discussions in a coherent glyphs flow would take many llm request per row of the dataset.

Perhaps doing one manually to test if it makes any sens then script a python program to orchestrate all those discussions ??? Still thinking about it.

Wanted to share my input, not sure if it can help.
Thanks!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions