Promote the experimental architecture to main

CONTRIBUTING.md

@@ -75,20 +75,23 @@ execution. The intended crate roles are:
 
  -  `feder-vocab`: Type-safe representations of Activity Vocabulary objects,
     such as actors, notes, and activities.
- -  `feder-core`: The portable ActivityPub protocol engine, responsible for
-    protocol decisions and state transitions.
- -  Runtime crates: Platform-specific execution layers for networking, storage,
-    clocks, timers, async runtimes, and operating system or hardware
-    integration.
+ -  `feder-core`: Portable ActivityPub protocol decisions and capability traits.
+    It derives transient outcomes from facts supplied by its caller and does
+    not retain protocol state.
+ -  `feder-server`: The standard operating system runtime for HTTP networking,
+    SQLite storage, actor resolution, request verification, and activity
+    delivery.
+ -  Future runtime crates: Platform-specific implementations for other async
+    runtimes, operating systems, or hardware environments.
 
 When contributing to `feder-core`, avoid adding direct dependencies on HTTP
 clients or servers, databases, filesystems, async runtimes, system clocks, or
 platform-specific crates. Runtime crates may use those dependencies when
 appropriate, but those choices should not leak into the portable core.
 
-Core behaviour should generally be tested by feeding an input into the core and
-asserting the returned actions. Core tests should not require real networking,
-storage, or async execution.
+Core behaviour should generally be tested by feeding stored facts and protocol
+input into a core function and asserting the returned transient outcome. Core
+tests should not require real networking, storage, or async execution.
 
 ### Git pre-commit hook
 

Cargo.toml

@@ -2,7 +2,7 @@
 members = [
   "crates/feder-core",
   "crates/feder-vocab",
-  "crates/feder-runtime-server",
+  "crates/feder-server",
   "examples/single-user-server",
 ]
 resolver = "3"
@@ -20,7 +20,7 @@ repository = "https://github.com/fedify-dev/feder"
 # Use `mise run bump-execute <version>` instead of editing these by hand.
 base64 = { version = "0.22.1", default-features = false, features = ["alloc"] }
 feder-core = { version = "0.1.0", path = "crates/feder-core" }
-feder-runtime-server = { version = "0.1.0", path = "crates/feder-runtime-server" }
+feder-server = { version = "0.1.0", path = "crates/feder-server" }
 feder-vocab = { version = "0.1.0", path = "crates/feder-vocab" }
 iri-string = { version = "0.7.12", default-features = false, features = ["alloc", "serde"] }
 rand_chacha = { version = "0.3.1", default-features = false }

README.md

@@ -23,10 +23,11 @@ software so different parts can run on machines with very different resources.
 Approach
 --------
 
-Feder separates ActivityPub protocol logic from platform execution. The core
-should contain federation behavior such as inbox/outbox state, delivery
-decisions, and protocol-level rules. Runtimes provide platform-specific pieces
-such as networking, storage, clocks, scheduling, and execution.
+Feder separates ActivityPub protocol decisions from platform execution.
+`feder-core` derives transient protocol outcomes from application-provided
+facts without retaining state. `feder-server` supplies a standard operating
+system runtime with HTTP networking, SQLite storage, actor resolution, request
+verification, and activity delivery.
 
 The first target is a Linux proof of concept for a small single-user
 ActivityPub server. Future runtimes may explore more constrained environments.

crates/feder-core/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "feder-core"
-description = "Portable ActivityPub core logic for Feder."
+description = "Portable ActivityPub protocol decisions and capability traits for Feder."
 version.workspace = true
 edition.workspace = true
 authors.workspace = true
@@ -17,8 +17,10 @@ feder-vocab.workspace = true
 rsa = { workspace = true, optional = true }
 zeroize = { workspace = true, optional = true }
 
-[dev-dependencies]
-rand_chacha.workspace = true
-
 [lints]
 workspace = true
+
+[[test]]
+name = "key"
+path = "tests/key.rs"
+required-features = ["http-signatures"]