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
//! **The workflow mark on the wire** (REMOTE §9.24, bl-b680): how the
//! `governing` reply spells the §9.4 mark beside the commit it rides with, and
//! how a seat reads it back.
//!
//! Its own file on the seam every type-owning `wire` module takes — the
//! encoder and the decoder of one body beside each other, so the two cannot
//! drift — and beside the reply rather than inside `config_edit`, because the
//! derivation there is git and this is JSON.
//!
//! **`null` is the general path.** No mark anywhere on the descent is what
//! every unmarked conversation answers, and it is spelled as `null` rather
//! than an absent key on `follows`' own precedent: the encoder always writes
//! the key, and a reader that has never heard of it reads the answer it
//! always read. The decoder accepts absence too (REMOTE §3.2: a post-floor
//! key an older engine never wrote defaults), and reads a present object
//! strictly — every token named, a mistyped one refused by name.
use ;
use crate;
use crateWorkflowMark;
/// The mark as its body, or `null`.
pub
/// The inverse of [`value`] for a present, non-null value. `lineage` is
/// `null` — never absent — when no `config/*` ref stands on the marked
/// commit, and it is read as such.
pub