• module.json — Agentic module schema role assignments

🪝 Hooks — Canonical Event & Trigger Layer

The hooks directory contains the event‑driven trigger layer for TriadicFrameworks.
Hooks define how modules respond to actions, state changes, or resonance events across the canon.

This directory provides:

• canonical hook definitions
• event → action mappings
• automation triggers
• cross‑module integration points
• lightweight HTML index for browsing

Hooks are part of the automation substrate, enabling modules to react to internal or external signals.

📄 Included Hook Files#

index.html#

A lightweight HTML index for browsing available hooks.
Used by internal tooling, documentation viewers, and module‑level automation systems.

data/hooks.json#

The canonical hook registry.
Defines:

• hook names
• trigger conditions
• event categories
• associated actions
• metadata for automation engines

This file is consumed by RTT automation layers, module builders, and integration tools.

🧩 How to Reference Hooks#

Inside any module:

See: `docs/hooks/data/hooks.json`

Or include directly:

{{#include ../hooks/index.html}}

Hooks keep your documentation reactive, automated, and integration‑ready.