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
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
//! The blob family's three seams, each in BOTH modes: [`AsyncBlobEngine`] / [`BlobEngine`] (the per-slot
//! handle), [`AsyncLocate`] / [`Locate`] (its optional address capability) and [`AsyncBlobStore`] /
//! [`BlobStore`] (the construction layer that mints the handle).
//!
//! # Why this family is twinned, when most are not
//!
//! The dual-mode law's criterion is not *is the trait async* — it is *can the underlying act happen
//! NATIVELY BLOCKING*. Most seams fail it and are refused a twin on purpose: serving GraphQL,
//! waiting on a doorbell, sqlx's own socket. Twinning one of those manufactures the reverse fiction.
//!
//! Blob I/O passes it outright, and it is the record world's one member that does. A file read IS a
//! blocking syscall; `std::fs` is the direct spelling and `tokio::fs` is `spawn_blocking` wearing a
//! coat. So the blocking face here is not a convenience over the async one — it is the act, and the
//! async face is what BRIDGES to it. The shipped filesystem citizens below are written that way and
//! say so: [`BlobEngine`] holds the body, [`AsyncBlobEngine`] delegates to it and resolves immediately.
//!
//! # The two faces are SIBLINGS, and a backend implements what it can honestly answer
//!
//! Neither trait is a supertrait of the other, and the choice is load-bearing in both directions. A
//! supertrait `BlobEngine<R>: AsyncBlobEngine<R>` would tax a blocking-only store with an async face
//! nobody asked it for; the reverse would make every remote store implement a blocking one it cannot
//! honestly write. What a store CAN answer is what it implements, and a caller's bound is what says
//! which face it needs — a sync body over an async-only backend is `E0277` at the bound, naming the
//! two roads, rather than a runtime block-on nobody chose.
//!
//! The cost of siblings is that a store answering BOTH has two `put`s, two `get`s, two `read`s and
//! two `locate`s reachable by one name. It was MEASURED here rather than assumed: every call site in
//! this tree already spells the trait — `AsyncBlobEngine::<Frame>::put(&handle, …)`,
//! `AsyncLocate::<Frame>::locate(…)` — because `R` is otherwise uninferable from the arguments. The
//! disambiguation the collision would cost is therefore already written, and the shipped filesystem
//! handle implements all four faces with no suffix anywhere.
//!
//! # Which verbs the criterion actually twins, one seat finer
//!
//! The mode split is per ACT and not per trait, so the family is not uniformly twinned inside:
//!
//! | verb | mode | why |
//! |---|---|---|
//! | `put` / `get` / [`read`](AsyncBlobEngine::read) | async here, sync on the twin | file I/O, natively blocking |
//! | [`locate`](AsyncLocate::locate) / [`location`](AsyncLocate::location) | SYNC on both faces | a LOCAL render — no round trip, so no mode to differ in |
//!
//! [`AsyncLocate`] and [`Locate`] are therefore method-identical, and they still both exist: the
//! sibling law is about which face a store REACHES ITS SEATS THROUGH, not about which verbs differ.
use ;
use Infallible;
use Utf8Bytes;
use Connected;
use crateTransformer;
/// A blob store (local filesystem, S3, …), **generic over the record `R`** it stores: UNBOUNDED
/// over `R`, with only [`get`](Self::get) — whose signature projects `R::Key` — carrying the
/// method-level `where R: Transformer`. [`put`](Self::put) takes a bare `&R`.
///
/// `put` writes `R::bytes()` at the address derived from `R::key()` — a keyed replace,
/// last-write-wins — and returns nothing: a blob is a DERIVED artifact, so its corruption detector
/// is the consumer and its recovery is regenerate, not a stored-hash verify. `get` reads by
/// `R::Key`, resolving the same address, into the backend's [`Payload`](Self::Payload).
///
/// The write side carries the bytes IN MEMORY, through the record (`R::bytes()`); a streaming /
/// multipart upload is future ADDITIVE surface — a distinct method — and is neither implied by this
/// trait nor foreclosed by it.
/// Resolve a blob's ADDRESS without reading it — the wire-facing ref.
///
/// An OPTIONAL capability and a SUPERTRAIT of the [`AsyncBlobEngine`] face it extends. Standalone it could
/// not spell its own `Connected<…>` parameter — it has no `Connection` / `ReadContext` to project —
/// and a handle typically holds only its slot, the root living on the
/// [`Connection`](AsyncBlobEngine::Connection), so a handle-only `locate` could not even render an address.
///
/// [`locate`](Self::locate) is a PURE address render — NO existence check, and NO ROUND TRIP: the
/// store renders the address out of what it already holds, which is what lets a caller hand out a
/// reference having touched nothing, and what keeps this from being a `get` that throws its bytes
/// away.
///
/// # SYNCHRONOUS on both faces, and the pin is what says so
///
/// Neither verb here returns a future, on this face or on [`Locate`], and the pin above is
/// the reason rather than a mode judgement: a render out of what the store already holds cannot be
/// waiting for anything. A filesystem joins its root to the key's segments; an object store
/// concatenates a prefix, or signs a URL out of credentials it is already carrying. Both are LOCAL
/// rendering, so an `async fn` here would be an `async fn` in name only — which is precisely the
/// fiction the dual-mode law refuses in the other direction.
///
/// That leaves this capability with NO mode difference at all, and the twin below exists anyway for
/// the sibling law's own reason: a blocking-only store must reach its `Connection` and its scopes
/// through a face it implements, and [`AsyncBlobEngine`] is not that face.
///
/// # THE LOCATION IS THE BACKEND'S, and the seat that says so is BARE
///
/// [`Location`](Self::Location) carries NO bound naming a wire library, a serializer or a shape.
/// The backend defines it — `FsLocation { path, size }`, `S3Location { url, etag, size }`, whatever
/// a store actually knows about where its bytes are — exactly as `type Score` is the ENGINE's on the
/// two search seams. A bound here would make every location the property of whichever library the
/// bound named, and a second backend could not answer without that library compiled.
///
/// Where the form is SPENT is where it is demanded: a wire face returning a location asks it for
/// [`ToGraphqlOutput`](crate::ToGraphqlOutput) structurally, and a location no binding can render
/// fails at that face rather than at this seat. It is [`ToGraphqlOutput::Output`]'s own law, one
/// layer down, and it is what keeps the ORPHAN RULE out of a backend's way: the location is the
/// backend's LOCAL type, so its crossing row is an ordinary local impl.
///
/// [`BlobLocation`](super::BlobLocation) is A citizen of that seat and never THE law — the
/// convenience shape a backend with nothing more to say elects, and the one this crate's own
/// filesystem store takes.
///
/// # TWO members, because a bare seat has no producer the framework could write
///
/// Nothing generic can build a `Self::Location` — no bound means no constructor, no `From`, no
/// conversion this crate could call. So the backend that DEFINES the type is the one that MINTS it,
/// and [`location`](Self::location) is where. The alternative — a bound supplying the conversion —
/// is the law this seat exists to refuse.