From 20286ce0d8867eb9c57a71ae62e4830df33311ab831c16298106436e89ac0b79 Mon Sep 17 00:00:00 2001 From: Tyler J King Date: Sun, 12 Apr 2026 22:21:55 -0400 Subject: [PATCH] docs: add architecture boundary comment to chronicle_client.rs Signed-off-by: Tyler King --- org-ops-core/src/chronicle_client.rs | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/org-ops-core/src/chronicle_client.rs b/org-ops-core/src/chronicle_client.rs index 9322675..e6b4bcd 100644 --- a/org-ops-core/src/chronicle_client.rs +++ b/org-ops-core/src/chronicle_client.rs @@ -1,11 +1,20 @@ // Copyright 2026 Guildhouse Dev // SPDX-License-Identifier: Apache-2.0 -//! CloudEvents 1.0 Chronicle emitter. +//! Chronicle CloudEvents Emitter +//! +//! Emits governance events to the Chronicle ingestion bridge as +//! CloudEvents 1.0 payloads. Events enter the Chronicle persistence +//! pipeline (Pulsar -> ClickHouse) via the bridge. +//! +//! This is NOT a direct Chronicle write — the in-memory Private +//! Ledger is maintained by substrate-chronicle-core. Userspace +//! emitters always go through the ingestion bridge. //! -//! Replaces the fake Forgejo push webhook pattern used previously. //! Git-originated events use the commit SHA as the CloudEvent `id`. //! Non-git events use a UUID v4. +//! +//! See: ARCHITECTURE-CHRONICLE.md use std::time::Duration;