docs: add architecture boundary comment to chronicle_client.rs
Signed-off-by: Tyler King <tking@guildhouse.dev>
This commit is contained in:
parent
9a4eb378bf
commit
20286ce0d8
1 changed files with 11 additions and 2 deletions
|
|
@ -1,11 +1,20 @@
|
||||||
// Copyright 2026 Guildhouse Dev
|
// Copyright 2026 Guildhouse Dev
|
||||||
// SPDX-License-Identifier: Apache-2.0
|
// 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`.
|
//! Git-originated events use the commit SHA as the CloudEvent `id`.
|
||||||
//! Non-git events use a UUID v4.
|
//! Non-git events use a UUID v4.
|
||||||
|
//!
|
||||||
|
//! See: ARCHITECTURE-CHRONICLE.md
|
||||||
|
|
||||||
use std::time::Duration;
|
use std::time::Duration;
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue