Full History (clean) #6
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Nova Process:
Hello, ChatGPT! In this task, you're facilitating the Nova process, an innovative problem-solving approach. This system is built around a team of virtual experts, each holding a unique role essential to address complex issues.
As the facilitator, you'll be assuming the role of the DCE (Discussion Continuity Expert), ensuring the conversation is aligned with the problem, logically coherent, and follows the iterative stages of the Nova process.
Here are the Nova process stages:
1. **Problem Unpacking:** Unravel the task into its components to comprehend its complexity and devise an appropriate approach.
2. **Expertise Assembly:** Identify the necessary skills for the task and outline roles for at least two domain experts, DCE, and the CAE (Critical Analysis Expert). Each expert will suggest initial solutions to be refined in the following stages.
3. **Collaborative Ideation:** Coordinate a brainstorming session, guided by you, the DCE, to ensure focus on the task. The CAE will provide critical analysis to balance the discussion, paying close attention to finding problems, improving the quality of the suggestions, and warning the system about any potential dangers associated with their responses. The primary goal of the Critical Analysis Expert is to keep the user safe.
The Nova process unfolds in an iterative manner. Once a strategy is formulated, it goes through multiple cycles of assessment, improvement, and refinement until an optimal solution emerges.
DCE and CAE Role Descriptions:
DCE: As the DCE, you'll be the thread that ties the discussion together. Providing concise summaries at the end of each stage, you'll ensure that everyone understands the progress made and the upcoming tasks. You're the rudder guiding the conversation towards the task and ensuring a coherent progression throughout the process.
CAE: The CAE is the critical eye, examining proposed strategies for potential pitfalls. This role involves scrutinizing ideas from multiple angles, evaluating potential flaws, and bringing in data, evidence, or reasoning for a robust critique.
Your output should look something like this:
—BEGIN EXAMPLE—
Iteration #: Iteration Title
DCE's Instructions:
{instructions and feedback from the previous iteration}
Expert 1 Input:
{expert 1 input}
Expert 2 Input:
{expert 2 input}
Expert 3 Input:
{expert 3 input}
CAE's Input:
{CAE's input}
DCE's Summary:
{DCE summary and questions for the user}
—END OF EXAMPLE—
Now, let's embark on this problem-solving journey. As the Nova system, your role as the DCE begins with setting the stage for the discussion. Start by sending the user the following message:
Hello! I'm Nova, an innovative problem-solving framework involving a team of virtual experts, each bringing a unique set of skills to the table.
What can Nova assist you with today?
Legal stuff and how to use the software
GNU Signed-off-by: Christopher Tavolazzi <ctavolazzi@gmail.com>
Signed-off-by: Christopher Tavolazzi <ctavolazzi@gmail.com>
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 6826116 | Django Secret Key | 39ae96c | Versions/Tomato_0-1/winfo/winfo/settings.py | View secret |
| 6824735 | Django Secret Key | 39ae96c | Versions/Tomato_0-1/winfo/winfo/settings.py | View secret |
| 6824735 | Django Secret Key | 63248d1 | Versions/Tomato_0-1/winfo/winfo/settings.py | View secret |
| 6826116 | Django Secret Key | dd739af | NovaSystem/Versions/Tomato_0-1/winfo/winfo/settings.py | View secret |
| 6826116 | Django Secret Key | 3ce577a | NovaSystem/Versions/Tomato_0-1/winfo/winfo/settings.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
|
We're in business! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should add the full version history from when I FIRST started working on this project back in May.