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
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
//! Shared capability traits for exact-support materialization.
//!
//! These traits make the released add-on relation surfaces line up around one
//! explicit question: what exact facts remain after forgetting provenance
//! witnesses, annotation values, or valid-time intervals?
use crate::;
use FiniteRelation;
/// Relation-level exact support for add-on relation surfaces.
///
/// `ExactSupport` makes explicit the deterministic relation-level boundary
/// already used by the released provenance, annotated, and valid-time
/// surfaces: forget the add-on payload and keep only the exact stored facts.
///
/// The forgotten payload differs by surface:
///
/// - provenance forgets the witness token set returned by
/// [`crate::provenance::ProvenanceRelation::why`];
/// - annotated relations forget the stored annotation returned by
/// [`crate::annotated::AnnotatedRelation::annotation_of`];
/// - valid-time relations forget the fact-level interval support returned by
/// [`crate::temporal::ValidTimeRelation::valid_time_of`].
///
/// Do not confuse this relation-level exact support with
/// [`crate::temporal::ValidTimeSupport`], which is the canonical interval
/// support for one stored fact rather than the exact support of the whole
/// relation.
///
/// # Examples
///
/// ```rust
/// use relmath::{
/// ExactSupport,
/// annotated::{AnnotatedRelation, BooleanSemiring},
/// provenance::ProvenanceRelation,
/// temporal::{Interval, ValidTimeRelation},
/// };
///
/// let evidence = ProvenanceRelation::from_facts([
/// (("alice", "review"), "directory"),
/// (("bob", "approve"), "policy"),
/// ]);
/// let permissions = AnnotatedRelation::from_facts([
/// (("alice", "review"), BooleanSemiring::TRUE),
/// (("bob", "approve"), BooleanSemiring::TRUE),
/// ]);
/// let schedule = ValidTimeRelation::from_facts([
/// (
/// ("alice", "review"),
/// Interval::new(1, 3).expect("expected valid interval"),
/// ),
/// (
/// ("bob", "approve"),
/// Interval::new(2, 4).expect("expected valid interval"),
/// ),
/// ]);
///
/// assert_eq!(
/// evidence.exact_support().to_vec(),
/// vec![("alice", "review"), ("bob", "approve")]
/// );
/// assert_eq!(permissions.exact_support().to_vec(), evidence.exact_support().to_vec());
/// assert_eq!(schedule.exact_support().to_vec(), evidence.exact_support().to_vec());
/// ```
/// Materializes exact scalar support as a unary relation.
///
/// This trait mirrors the existing `to_unary_relation` conversion methods on
/// released add-on surfaces and gives generic code one explicit unary
/// materialization boundary.
///
/// # Examples
///
/// ```rust
/// use relmath::{
/// ToExactUnaryRelation,
/// annotated::{AnnotatedRelation, BooleanSemiring},
/// };
///
/// fn exact_values<R>(relation: &R) -> Vec<&'static str>
/// where
/// R: ToExactUnaryRelation<&'static str>,
/// {
/// relation.to_unary_relation().to_vec()
/// }
///
/// let concepts = AnnotatedRelation::from_facts([
/// ("Closure", BooleanSemiring::TRUE),
/// ("Relations", BooleanSemiring::TRUE),
/// ("Zero", BooleanSemiring::FALSE),
/// ]);
///
/// assert_eq!(exact_values(&concepts), vec!["Closure", "Relations"]);
/// ```
/// Materializes exact pair support as a binary relation.
///
/// This trait mirrors the existing `to_binary_relation` conversion methods on
/// released add-on surfaces and keeps deterministic pair order inherited from
/// exact support materialization.
///
/// # Examples
///
/// ```rust
/// use relmath::{
/// BinaryRelation, ToExactBinaryRelation,
/// annotated::{AnnotatedRelation, BooleanSemiring},
/// };
///
/// fn exact_pairs<R>(relation: &R) -> BinaryRelation<&'static str, &'static str>
/// where
/// R: ToExactBinaryRelation<&'static str, &'static str>,
/// {
/// relation.to_binary_relation()
/// }
///
/// let permissions = AnnotatedRelation::from_facts([
/// (("alice", "read"), BooleanSemiring::TRUE),
/// (("bob", "approve"), BooleanSemiring::TRUE),
/// ]);
///
/// assert_eq!(
/// exact_pairs(&permissions).to_vec(),
/// vec![("alice", "read"), ("bob", "approve")]
/// );
/// ```
/// Materializes exact row support as an n-ary relation with an explicit schema.
///
/// This trait mirrors the existing `to_nary_relation` conversion methods on
/// released add-on surfaces. It preserves the current exact n-ary contract:
/// schema names remain explicit and `NaryRelation` validation rules still
/// apply during materialization.
///
/// # Examples
///
/// ```rust
/// use relmath::{NaryRelation, ToExactNaryRelation, provenance::ProvenanceRelation};
///
/// let rows = ProvenanceRelation::from_facts([
/// (vec!["Alice", "Math", "passed"], "gradebook"),
/// (vec!["Bob", "Physics", "passed"], "gradebook"),
/// ]);
///
/// assert_eq!(
/// rows.to_nary_relation(["student", "course", "status"])?,
/// NaryRelation::from_rows(
/// ["student", "course", "status"],
/// [["Alice", "Math", "passed"], ["Bob", "Physics", "passed"]],
/// )?
/// );
///
/// # Ok::<(), relmath::NaryRelationError>(())
/// ```