From ef66d60235a34a163993c43ae76b0895fb365843 Mon Sep 17 00:00:00 2001 From: Manfred Touron <94029+moul@users.noreply.github.com> Date: Fri, 28 Jul 2023 02:30:32 +0200 Subject: [PATCH 1/3] feat: create lighthouse.md I've been thinking a lot about whether Carmel should just stick to debates, or if it would make sense to merge Lighthouse into it. Or perhaps keeping Lighthouse as a standalone subproject, as it is now, is the best way to go. What I really feel though, is that both of these projects could benefit from a shared core framework and then become specialized pipelines on top of it. Even the name is giving me pause. But enough about what I think. I want to hear from you. What are your thoughts on all of this? --- lighthouse.md | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 lighthouse.md diff --git a/lighthouse.md b/lighthouse.md new file mode 100644 index 0000000..9559b00 --- /dev/null +++ b/lighthouse.md @@ -0,0 +1,65 @@ +"# Project Lighthouse (Alexandria?) + +Draft spec, please provide feedback in the form of pull requests and issues to github.com/allinbits/carmel. + +## Initial terms + + * All contributors agree on a curator or a panel of curators. + * All contributors commit to intellectual honesty, constructive debate, and the pursuit of truth. + * All contributors respect that this is an uncensored platform but are responsible for the veracity of their contributions. + +## Step 1. Determine the Discussion Points + + * Any contributor can suggest a complex or controversial topic for discussion. + * The curator(s) reviews these suggestions for relevance and interest. + * Topics that foster meaningful exploration of truth are approved. + * The curator(s) can propose new topics independently. + +## Step 2. Submission of Arguments and Evidence + + * For each approved topic, contributors can submit arguments, counter-arguments, and evidence. + * Contributors are expected to cite sources where applicable. + * The curator(s) organizes and categorizes the submitted information. + * All contributions remain uncensored, but the curator(s) may provide a framework for the information to promote understanding. + +## Step 3. Simplification and Correlation + + * Contributors can propose to split complex topics into smaller, easier-to-review subtopics. + * Contributors can suggest links to other related topics. + * Such contributions that facilitate comprehension and progress in discussions will be rewarded. + * The curator(s) review and implement these proposals. + +## Step 4. Debunking and Discussing + + * Contributors can refute existing arguments, provide new insights, and debate the evidence. + * All discussions are expected to be fact-based, respectful, and focused on debunking misconceptions. + * The curator(s) intervene if discussions go off-topic or become non-constructive. + * Curators provide summary statements to encapsulate progress and breakthroughs in understanding. + +## Step 5. Updating the Knowledge Base + + * As discussions evolve, contributors can update their arguments and evidence. + * The curator(s) review the updates for relevance and clarity. + * Approved updates are incorporated into the knowledge base. + * The curator(s) can suggest updates to streamline discussions. + +# Extra A. Intellectual Honesty and Rewards + + * Deliberate spreading of misinformation will not be tolerated and can lead to penalties. + * Any user can report suspected misinformation. + * The curator(s) review all reports and take necessary actions. + * Users making false reports can also face penalties. + * Both parties agree to indemnify reporters of misinformation to the full extent. + * Contributions that significantly aid in the quest for truth will be rewarded. + +# Extra B. IP Rights + + * All contributed arguments, evidence, and discussions belong to their respective original owners. + * Contributors grant a license for their contributions to be used within the knowledge base. + +--------------------------------- + +# Resources + + * https://twitter.com/jaekwon/status/1676530097308966912?s=20 +“ From c2924252f9df5a972a263aa73e29b0b0eef9bedc Mon Sep 17 00:00:00 2001 From: Manfred Touron <94029+moul@users.noreply.github.com> Date: Fri, 28 Jul 2023 03:06:31 +0200 Subject: [PATCH 2/3] Update lighthouse.md --- lighthouse.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/lighthouse.md b/lighthouse.md index 9559b00..3eb2b0b 100644 --- a/lighthouse.md +++ b/lighthouse.md @@ -1,4 +1,6 @@ -"# Project Lighthouse (Alexandria?) +# Project Lighthouse + +Project Lighthouse is conceptually linked to Project Carmel. They may appear as separate entities, but both projects can potentially share similar technical foundations. While Carmel is focused on debates, Lighthouse takes those principles and applies them to the management of a knowledge base. The underlying architecture can be similar, promoting synergies and allowing both projects to benefit from shared enhancements and updates. Draft spec, please provide feedback in the form of pull requests and issues to github.com/allinbits/carmel. @@ -17,7 +19,7 @@ Draft spec, please provide feedback in the form of pull requests and issues to g ## Step 2. Submission of Arguments and Evidence - * For each approved topic, contributors can submit arguments, counter-arguments, and evidence. + * contributors can submit arguments, counter-arguments, and evidence for each approved topic. * Contributors are expected to cite sources where applicable. * The curator(s) organizes and categorizes the submitted information. * All contributions remain uncensored, but the curator(s) may provide a framework for the information to promote understanding. @@ -32,7 +34,7 @@ Draft spec, please provide feedback in the form of pull requests and issues to g ## Step 4. Debunking and Discussing * Contributors can refute existing arguments, provide new insights, and debate the evidence. - * All discussions are expected to be fact-based, respectful, and focused on debunking misconceptions. + * All discussions must be fact-based, respectful, and focused on debunking misconceptions. * The curator(s) intervene if discussions go off-topic or become non-constructive. * Curators provide summary statements to encapsulate progress and breakthroughs in understanding. @@ -55,11 +57,10 @@ Draft spec, please provide feedback in the form of pull requests and issues to g # Extra B. IP Rights * All contributed arguments, evidence, and discussions belong to their respective original owners. - * Contributors grant a license for their contributions to be used within the knowledge base. + * Contributors grant a license to use their contributions within the knowledge base. --------------------------------- # Resources * https://twitter.com/jaekwon/status/1676530097308966912?s=20 -“ From bc25ba6d0654805b21043c635de1cbe4a89e0e90 Mon Sep 17 00:00:00 2001 From: Manfred Touron <94029+moul@users.noreply.github.com> Date: Fri, 28 Jul 2023 03:29:37 +0200 Subject: [PATCH 3/3] Update lighthouse.md --- lighthouse.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/lighthouse.md b/lighthouse.md index 3eb2b0b..7114bda 100644 --- a/lighthouse.md +++ b/lighthouse.md @@ -2,6 +2,8 @@ Project Lighthouse is conceptually linked to Project Carmel. They may appear as separate entities, but both projects can potentially share similar technical foundations. While Carmel is focused on debates, Lighthouse takes those principles and applies them to the management of a knowledge base. The underlying architecture can be similar, promoting synergies and allowing both projects to benefit from shared enhancements and updates. +A key aspect to underscore is that the backbone of our efforts in Carmel, Lighthouse (and Gno) hinges on both contribution and reputation. I posit that this reputation could be mutually recognized between Carmel and Lighthouse. This cross-recognition could be particularly beneficial in identifying trustworthy experts within specific fields. + Draft spec, please provide feedback in the form of pull requests and issues to github.com/allinbits/carmel. ## Initial terms