For Vision-Statement see: Vision.md
- Understand the motivation
-
Branching Strategy:
- Each developer should work on their own development branch (e.g. feature-... development branch).
- The
main
branch should only be updated through pull requests. - Pull requests to the
main
branch require a review before being merged. - Delete feature branches once they are merged into
main
.
-
Commit Messages:
- Write clear and concise commit messages describing the changes made.
- Use the imperative mood, e.g., "Add feature" not "Added feature" or "Adds feature".
-
Conflict Resolution:
- Resolve merge conflicts in your development branch before submitting a pull request.
- Keep your branch updated with the latest changes from
main
to minimize conflicts.
-
Code Review:
- Actively participate in code review processes.
- Reviewers should ensure code quality, functionality, and adherence to design principles.
- Status: MVP
- Architecture:
- Involved Platforms:
- GCP
- Stack:
- Cloud Run (europe-west3-docker.pkg.dev/...)
- BQ
- Stack:
- GCP
- Involved Platforms:
- .env
NUM_STEPS=10 (todo :: UI :: DFS search of user input)
MODEL=gpt-3.5-turbo-16k-0613 (todo :: UI :: Dropdown of models)
BQ_CLIENT_SECRETS={*****}
OPENAI_API_KEY=****
OPENAI_BASE_URL=https://api.openai.com/v1/chat/completions
ADJACENCY_MATRIX_DATASET_ID=graph_to_agent_adjacency_matrices MULTI_LAYERED_MATRIX_DATASET_ID=graph_to_agent_multi_layered_metrices ANSWER_CURATED_CHAT_COMPLETIONS=graph_to_agent_answer_curated_chat_completions CURATED_CHAT_COMPLETIONS=graph_to_agent_chat_completions RAW_CHAT_COMPLETIONS=graph_to_agent_raw_chat_completions GRAPH_DATASET_ID=graph_to_agent EDGES_TABLE=edges_table NODES_TABLE=nodes_table
TEMP_RAW_CHAT_COMPLETIONS_DIR=temp_raw_chat_completions TEMP_MULTI_LAYERED_MATRIX_DIR=temp_multi_layered_matrix TEMP_CHECKPOINTS_GPT_CALLS=temp_checkpoints_gpt_calls LOG_DIR_LOCAL=./temp_log
- control + shift --> default :D
- control c + v
- explain multi select difference between custom function, agent and assistant
- modi msg passing
- how to read proposal
- explain roadmap
- explain interest in simulation
- law of physics connected with msg. passing weights/ the more msgs/ the more info one msg carries, the higher the gravity of a node
- conways game of life
- llama-index --> language corpus via edges
- explain different dimensions if somebody uses a pre-trained/ fine tuned model
- Explain the sheer infinite statistical possibilities, starting with the two layers
- explain the difference between the two layers
- distance matrix
- social interaction simulation by msg. protocols
- Agent behaviour with dynamic environment