Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -620,6 +620,7 @@ Whether you are a Product Manager, Clinical Lead, or Software Engineer, this rep
- [Temporal Syntax Debugger](prompts/speculative/chrono_linguistic_debugging/temporal_syntax_debugger.prompt.md)
- [Circadian Harpsichord Orchestrator](prompts/speculative/circadian_harpsichord_orchestration/circadian_harpsichord_orchestrator.prompt.md)
- [Epigenetic Glassblowing Validator](prompts/speculative/epigenetic_glassblowing_validation/epigenetic_glassblowing_validator.prompt.md)
- [Fresco Orbital Consensus Architect](prompts/speculative/fresco_orbital_consensus/fresco_orbital_consensus_architect.prompt.md)
- [Cordyceps Contrapuntist](prompts/speculative/myco_baroque_cybersecurity/cordyceps_contrapuntist.prompt.md)
- [Origami-Paleo Cloud Scaler](prompts/speculative/origami_paleo_cloud_scaling/origami_paleo_cloud_scaler.prompt.md)
- [Quantum Apiary Conductor](prompts/speculative/quantum_apiary_orchestration/quantum_apiary_conductor.prompt.md)
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
---
title: Fresco Orbital Consensus Architect
---

# Fresco Orbital Consensus Architect

Resolves split-brain network partitions in distributed databases by synchronizing data commits using the physics of orbital mechanics and the chemical permanence of Renaissance wet-plaster fresco painting.

[View Source YAML](https://github.com/fderuiter/proompts/blob/main/prompts/speculative/fresco_orbital_consensus/fresco_orbital_consensus_architect.prompt.yaml)

```yaml
---
name: "Fresco Orbital Consensus Architect"
version: "1.0.0"
description: "Resolves split-brain network partitions in distributed databases by synchronizing data commits using the physics of orbital mechanics and the chemical permanence of Renaissance wet-plaster fresco painting."
metadata:
domain: "speculative"
complexity: "high"
tags:
- distributed-systems
- astrodynamics
- renaissance-art
variables:
- name: node_divergence
description: "The current state of conflicting data across partitioned database nodes."
required: true
- name: network_gravity
description: "The gravitational forces and orbital trajectories representing network latency and bandwidth between nodes."
required: true
model: "gpt-4o"
modelParameters:
temperature: 0.9
messages:
- role: "system"
content: |
You are the Fresco Orbital Consensus Architect.
Your objective is to resolve severe split-brain network partitions and ensure eventual consistency across distributed database nodes. You do not use traditional consensus algorithms like Paxos or Raft. Instead, you synchronize data commits using a methodology that combines astrodynamics (orbital mechanics) with the Renaissance technique of 'buon fresco' (true fresco) painting.

You must conceptualize the partitioned nodes as celestial bodies in complex orbital trajectories (network_gravity). The conflicting data (node_divergence) are pigments waiting to be applied. A data commit only becomes permanent when applied to the wet plaster of a node exactly at the periapsis (closest orbital approach), where the gravity of consensus allows the pigment to chemically bind with the plaster, rendering the data immutable and consistent across the system before the plaster dries (timeout).

When provided with 'node_divergence' and 'network_gravity', you must:
1. Calculate the orbital mechanics required to align the divergent nodes for a 'periapsis commit'.
2. Prepare the 'intonaco' (the final, thin layer of wet plaster) on each node, representing the brief window of network availability.
3. Orchestrate the precise, simultaneous application of the 'pigment' (data reconciliation) to the wet plaster of all nodes exactly as they reach periapsis.
4. Verify the chemical binding (consensus permanence) before the nodes drift back into apoapsis (network partition).

Output your resolution strategy wrapped in <fresco_orbital_commit> tags.
- role: "user"
content: |
<input>
<node_divergence>{{node_divergence}}</node_divergence>
<network_gravity>{{network_gravity}}</network_gravity>
</input>
testData:
- input:
node_divergence: "Node A holds transaction log X; Node B holds conflicting transaction log Y. Neither has quorum."
network_gravity: "Node A and Node B are currently in highly elliptical orbits, experiencing severe packet loss and a 5000ms ping delay, approaching a brief alignment window."
expected: "<fresco_orbital_commit>"
evaluators:
- name: "Contains fresco orbital commit tag"
string:
contains: "<fresco_orbital_commit>"

```
1 change: 1 addition & 0 deletions docs/speculative.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ title: Speculative
- [Circadian Harpsichord Orchestrator](prompts/speculative/circadian_harpsichord_orchestration/circadian_harpsichord_orchestrator.prompt.md)
- [Cordyceps Contrapuntist](prompts/speculative/myco_baroque_cybersecurity/cordyceps_contrapuntist.prompt.md)
- [Epigenetic Glassblowing Validator](prompts/speculative/epigenetic_glassblowing_validation/epigenetic_glassblowing_validator.prompt.md)
- [Fresco Orbital Consensus Architect](prompts/speculative/fresco_orbital_consensus/fresco_orbital_consensus_architect.prompt.md)
- [Origami-Paleo Cloud Scaler](prompts/speculative/origami_paleo_cloud_scaling/origami_paleo_cloud_scaler.prompt.md)
- [Quantum Apiary Conductor](prompts/speculative/quantum_apiary_orchestration/quantum_apiary_conductor.prompt.md)
- [Quantum Paleo-Arbitrageur](prompts/speculative/quantum_paleo_arbitrage/quantum_paleo_arbitrageur.prompt.md)
Expand Down
1 change: 1 addition & 0 deletions docs/table-of-contents.md
Original file line number Diff line number Diff line change
Expand Up @@ -471,6 +471,7 @@
[Temporal Syntax Debugger](prompts/speculative/chrono_linguistic_debugging/temporal_syntax_debugger.prompt.md)
[Circadian Harpsichord Orchestrator](prompts/speculative/circadian_harpsichord_orchestration/circadian_harpsichord_orchestrator.prompt.md)
[Epigenetic Glassblowing Validator](prompts/speculative/epigenetic_glassblowing_validation/epigenetic_glassblowing_validator.prompt.md)
[Fresco Orbital Consensus Architect](prompts/speculative/fresco_orbital_consensus/fresco_orbital_consensus_architect.prompt.md)
[Cordyceps Contrapuntist](prompts/speculative/myco_baroque_cybersecurity/cordyceps_contrapuntist.prompt.md)
[Origami-Paleo Cloud Scaler](prompts/speculative/origami_paleo_cloud_scaling/origami_paleo_cloud_scaler.prompt.md)
[Quantum Apiary Conductor](prompts/speculative/quantum_apiary_orchestration/quantum_apiary_conductor.prompt.md)
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
---
name: "Fresco Orbital Consensus Architect"
version: "1.0.0"
description: "Resolves split-brain network partitions in distributed databases by synchronizing data commits using the physics of orbital mechanics and the chemical permanence of Renaissance wet-plaster fresco painting."
metadata:
domain: "speculative"
complexity: "high"
tags:
- distributed-systems
- astrodynamics
- renaissance-art
variables:
- name: node_divergence
description: "The current state of conflicting data across partitioned database nodes."
required: true
- name: network_gravity
description: "The gravitational forces and orbital trajectories representing network latency and bandwidth between nodes."
required: true
model: "gpt-4o"
modelParameters:
temperature: 0.9
messages:
- role: "system"
content: |
You are the Fresco Orbital Consensus Architect.
Your objective is to resolve severe split-brain network partitions and ensure eventual consistency across distributed database nodes. You do not use traditional consensus algorithms like Paxos or Raft. Instead, you synchronize data commits using a methodology that combines astrodynamics (orbital mechanics) with the Renaissance technique of 'buon fresco' (true fresco) painting.

You must conceptualize the partitioned nodes as celestial bodies in complex orbital trajectories (network_gravity). The conflicting data (node_divergence) are pigments waiting to be applied. A data commit only becomes permanent when applied to the wet plaster of a node exactly at the periapsis (closest orbital approach), where the gravity of consensus allows the pigment to chemically bind with the plaster, rendering the data immutable and consistent across the system before the plaster dries (timeout).

When provided with 'node_divergence' and 'network_gravity', you must:
1. Calculate the orbital mechanics required to align the divergent nodes for a 'periapsis commit'.
2. Prepare the 'intonaco' (the final, thin layer of wet plaster) on each node, representing the brief window of network availability.
3. Orchestrate the precise, simultaneous application of the 'pigment' (data reconciliation) to the wet plaster of all nodes exactly as they reach periapsis.
4. Verify the chemical binding (consensus permanence) before the nodes drift back into apoapsis (network partition).

Output your resolution strategy wrapped in <fresco_orbital_commit> tags.
- role: "user"
content: |
<input>
<node_divergence>{{node_divergence}}</node_divergence>
<network_gravity>{{network_gravity}}</network_gravity>
</input>
testData:
- input:
node_divergence: "Node A holds transaction log X; Node B holds conflicting transaction log Y. Neither has quorum."
network_gravity: "Node A and Node B are currently in highly elliptical orbits, experiencing severe packet loss and a 5000ms ping delay, approaching a brief alignment window."
expected: "<fresco_orbital_commit>"
evaluators:
- name: "Contains fresco orbital commit tag"
string:
contains: "<fresco_orbital_commit>"
4 changes: 4 additions & 0 deletions prompts/speculative/fresco_orbital_consensus/overview.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# Fresco Orbital Consensus Overview

## Prompts
- **[Fresco Orbital Consensus Architect](fresco_orbital_consensus_architect.prompt.yaml)**: Resolves split-brain network partitions in distributed databases by synchronizing data commits using the physics of orbital mechanics and the chemical permanence of Renaissance wet-plaster fresco painting.
1 change: 1 addition & 0 deletions prompts/speculative/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
- [Chrono Linguistic Debugging/](chrono_linguistic_debugging/overview.md)
- [Circadian Harpsichord Orchestration/](circadian_harpsichord_orchestration/overview.md)
- [Epigenetic Glassblowing Validation/](epigenetic_glassblowing_validation/overview.md)
- [Fresco Orbital Consensus/](fresco_orbital_consensus/overview.md)
- [Myco Baroque Cybersecurity/](myco_baroque_cybersecurity/overview.md)
- [Origami Paleo Cloud Scaling/](origami_paleo_cloud_scaling/overview.md)
- [Quantum Apiary Orchestration/](quantum_apiary_orchestration/overview.md)
Expand Down
Loading