sdg:hookKind
sdg:hookKind says where in the transaction lifecycle a hook fires. It is authored on sdg:HookDefinition documents alongside sdg:hookTransport (how the implementation is invoked) and sdg:matchesEvent (which transactions trigger it).
Known values
sdg:PostCommit— the hook runs after the atomic commit. It observes; it cannot retroactively decline the transaction. Both Phase 1 hooks (demo log, dependent-doc-changed) are post-commit.
The value set is small because Phase 1 ships post-commit observers only. A pre-commit kind arrives in Phase 4 when gate 4 (Pre-commit hooks) is wired: hooks run inside that gate and can veto, but they are still hooks — they observe and react rather than replacing the four admission gates (`Authz → Core invariants → Schema → Pre-commit hooks`).
Usage
- Domain:
sdg:HookDefinition. Range: a hook-kind individual. One per hook.