1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at https://mozilla.org/MPL/2.0/. */
//! The moot object — declare it, join it, share into its fauna.
//!
//! The tessera lane ([`crate::tessera`]) carries a moot's trust receipts;
//! this lane carries the moot *itself*: the founding declaration (name +
//! charter), visible membership, and the **fauna** — engram references
//! shared into the community (the hand-off eidetic's deferred consume half
//! picks up from). Same proven recipe, third lap: signed operations on the
//! event-DAG ([`wire`]), a deterministic order-independent fold
//! ([`roster`]), and one muniment-backed transactional write path ([`store`])
//! with a sign-and-store [`author`](store::MootStore::author) helper. Retention
//! checkpoints preserve a compact roster while authorized prune events remove
//! superseded event prefixes. The LogSync
//! catch-up + live session is currently host-composed over
//! [`murm_replication::SyncedSpace`]:
//! after the sibling-posture purity split moot owns no p2panda-net, so the host
//! builds the pump (endpoint injected) and publishes authored ops.
//!
//! M1 trust is the ring rule: holding the moot id is membership
//! eligibility (the kith ring's definition). Invitations, capability
//! gating, and fauna blob transfer are later milestones — the plan names
//! them rather than half-building them.
//!
//! External identity providers author through raw protocol-scoped Ed25519
//! seeds. The folded roster exposes a membership revision committed only to the
//! winning signed join operations, so unrelated fauna does not invalidate
//! recognition contexts.
pub use ;
pub use MootId;
pub use ;
pub use ;
pub use ;
pub use ;
pub use ;