triad-deliberation-protocol

Coordinate provisional decisions in SQLite when triad quorum is unavailable.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Heretek-AI/heretek-skills --skill triad-deliberation-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triad-deliberation-protocol
Source: https://github.com/Heretek-AI/heretek-skills/tree/main/skills/triad-deliberation-protocol
Command: npx skills add https://github.com/Heretek-AI/heretek-skills --skill triad-deliberation-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

In degraded triad situations, only TM-1 is operational; this skill defines a virtual subagent deliberation workflow, provisional decision logging, and a ratification path to maintain momentum while preserving consensus integrity.

Core Features & Use Cases

  • Virtual subagent deliberation to simulate TM-2 and TM-3 perspectives during degraded mode.
  • Provisional decision logging and ratification workflow to ensure eventual consensus restoration.
  • Integration with triad signal filter, quorum enforcement, and cron-based unity checks to manage mode transitions.

Quick Start

Activate the degraded-mode triad deliberation protocol when quorum is unavailable and begin logging provisional decisions for later ratification.

Frequently Asked Questions about triad-deliberation-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain consensus when triad quorum is unavailable in degraded mode?

To maintain consensus during degraded mode when triad quorum is unavailable, you coordinate provisional decisions through single-node operation while logging them in SQLite for later ratification. This preserves consensus integrity by deferring final agreement until quorum is restored.

What is provisional decision ratification in a degraded triad?

Provisional decision ratification is the workflow that finalizes temporary choices made during degraded triad operation. Once quorum is restored, provisional decisions logged in the SQLite database are reviewed and ratified by the full triad to ensure eventual consensus.

How do I simulate missing triad members during single-node operation?

You simulate missing triad members using virtual subagent deliberation. This workflow emulates the perspectives of unavailable nodes like TM-2 and TM-3, allowing the operational node to evaluate decisions comprehensively before logging them as provisional.

How does degraded-mode quorum enforcement integrate with signal filters and cron?

Degraded-mode quorum enforcement integrates with signal filters and cron manager to automate mode transitions. Cron-based unity checks monitor node reachability, triggering the deliberation protocol when quorum drops and initiating ratification workflows upon restoration.

Does the triad deliberation protocol require SQLite for tracking provisional decisions?

Yes, the protocol uses a SQLite-based triad_state and provisional_decisions tracking system. This local database ensures that all decisions made during degraded mode are persistently logged and retrievable for the ratification workflow once full quorum is reestablished.

When should I avoid using a degraded-mode consensus protocol?

You should avoid using degraded-mode consensus protocols when strict, immediate consensus is legally or operationally required without exception. Provisional decisions carry inherent risks until ratified, making this approach unsuitable for irreversible or highly sensitive actions.