qore-meta-log-decision

Log engineering decisions into a Merkle-chained meta-ledger with risk classifications.

Updated Aug 23, 2026

Search Tags:#governance #risk management #decision logging #traceability #audit trail #meta-ledger

Ready to run

npx skills add https://github.com/MythologIQ/Zo-Qore --skill qore-meta-log-decision

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qore-meta-log-decision
Source: https://github.com/MythologIQ/Zo-Qore/tree/main/.claude/commands/scripts/custom/qore-meta-log-decision
Command: npx skills add https://github.com/MythologIQ/Zo-Qore --skill qore-meta-log-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining an auditable and traceable record of significant development decisions, preventing knowledge loss and ensuring accountability.

Core Features & Use Cases

Decision Logging: Records key details of decisions including type, rationale, evidence, and risk.
Auditable Trail: Creates a Merkle-chained ledger for tamper-evident tracking.
Risk Management: Classifies decisions by risk (L1, L2, L3) and enforces approval workflows for critical choices.
Use Case: When deciding to switch from SQLite to PostgreSQL for scalability, log this decision with its justification, evidence, and risk assessment to ensure future reference and compliance.

Quick Start

Log an architecture decision to use SQLite for phases 1-2 with a clear rationale and L2 risk grade.

Frequently Asked Questions about qore-meta-log-decision

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

FAQPage Schema

How do I create an auditable trail for engineering decisions like architecture changes?▼

To create an auditable trail for engineering decisions, you log them into a Merkle-chained meta-ledger. This records the decision type, rationale, and evidence, ensuring tamper-evident traceability and preventing knowledge loss.

What is the best way to enforce approval workflows for high-risk technical stack changes?▼

To enforce approval workflows for high-risk technical stack changes, classify the decision using L1, L2, or L3 risk grades. The meta-ledger enforces these workflows for critical choices, ensuring accountability before implementation.

How do I log a database migration decision with its risk assessment and rationale?▼

To log a database migration decision with its risk assessment, record the event as a TECH_STACK or ARCHITECTURE type. Include the specific rationale, supporting evidence, and an L1, L2, or L3 risk grade in the meta-ledger.

Can I track scope changes and security decisions in a single tamper-evident ledger?▼

Yes, you can track scope changes and security decisions in a single tamper-evident ledger. The system manages multiple decision types, including SCOPE_CHANGE and SECURITY, linking them via a Merkle-chained meta-ledger.

When do I need to log decisions to a meta-ledger instead of just using standard documentation?▼

You need to log decisions to a meta-ledger when you require tamper-evident traceability and progressive formalization. It is essential for preventing knowledge loss and ensuring accountability for major engineering decisions.

Does decision logging integrate with SOA Ledger principles for governance and risk management?▼

Yes, decision logging integrates with SOA Ledger principles for governance and risk management. It enforces progressive formalization and accountability by chaining decision records with their rationale and risk classifications.