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
//! # spacedb-access — SpaceDB Layer 5 (identity & access)
//!
//! The consent layer, and the AI-age differentiator: **inaccessible by default,
//! accessible by mID-gated consent**. Every read / write / compute is authorized
//! by a signed, scoped, expiring, (S2) revocable [`Capability`] issued by an
//! owner's identity to a bearer — a human or an AI agent with its *own* identity.
//!
//! M5-S1 ships the core: [`Identity`] (ECDSA P-256 / ES256), the [`Capability`] +
//! [`SignedCapability`] model, the [`KeyDirectory`] seam (DID → published key),
//! and [`authorize`] — the single chokepoint enforcing signature · bearer · scope
//! · ops · expiry. Revocation + delegation (S2) and the audit log + human-vs-AI
//! policy (S3) build on this.
//!
//! Open-core (MIT): no MATA dependency. Identities are P-256 keys behind the
//! `KeyDirectory` seam; MATA resolves `did:mata` via IAMHUMAN, a self-hoster uses
//! [`MemKeyDirectory`]. ES256 matches mID, so MATA's real mIDs verify identically.
pub use ;
pub use ;
pub use ;
pub use ;
pub use RevocationSet;
pub use ;
pub use ;
pub use ;
pub use ;
/// Compiles the README's examples as doctests, so the documented API can never
/// drift from the real one. Not part of the public API, and not rendered into
/// the crate docs — it exists only under `cargo test --doc`.
;