remove stubs

This commit is contained in:
Evgeny Poberezkin
2026-06-01 18:21:24 +01:00
parent 6793369950
commit 0d7a8440e4
13 changed files with 1 additions and 116 deletions
+1 -1
View File
@@ -41,7 +41,7 @@ Routers are the network infrastructure — they accept, buffer, and deliver pack
Initialize: `smp-server init -n <fqdn>` (or `--ip <ip>`). This generates TLS certificates. The CA certificate fingerprint becomes part of the server address: `smp://<fingerprint>@<hostname>[:5223]`.
The server uses in-memory persistence with an optional append-only store log for queue persistence across restarts. Enable with `smp-server init -l` or in `smp-server.ini`. The log is compacted on every restart.
By default, the server uses in-memory persistence with an optional append-only store log for queue persistence across restarts. Enable with `smp-server init -l` or in `smp-server.ini`. The log is compacted on every restart.
When store log is enabled, undelivered messages are saved on exit (SIGINT only, not SIGTERM) and restored on start. Control this independently with the `restore_messages` setting.
-22
View File
@@ -1,22 +0,0 @@
# SimpleX Network — Product Layer
> What does this do? Who uses it? What must never break?
## Vision
<!-- Extracted from protocol specs and philosophy -->
## Components
| Component | Description | Spec | Protocol |
|-----------|-------------|------|----------|
| SMP | Simplex messaging queues | spec/smp-protocol.md | protocol/simplex-messaging.md |
| Agent | Duplex connections over simplex queues | spec/agent.md | protocol/agent-protocol.md |
| XFTP | File transfer via encrypted chunks | spec/xftp-protocol.md | protocol/xftp.md |
| XRCP | Remote control of mobile clients | spec/remote-control.md | protocol/xrcp.md |
| NTF | Push notifications with privacy | spec/ntf-protocol.md | protocol/push-notifications.md |
| Servers | SMP, XFTP, NTF server operation | spec/smp-server.md | — |
## Capability Map
<!-- Per-component: what users can do, what the system guarantees -->
-9
View File
@@ -1,9 +0,0 @@
# Agent — Duplex Connections
> Bidirectional connections built over pairs of simplex queues.
## Users
## Connection Lifecycle
## Guarantees
-7
View File
@@ -1,7 +0,0 @@
# Push Notifications
> Push notifications with metadata privacy.
## Users
## Privacy Trade-offs
-9
View File
@@ -1,9 +0,0 @@
# Server Operation
> SMP, XFTP, and NTF server deployment and operation.
## Deployment
## Configuration
## Monitoring
-9
View File
@@ -1,9 +0,0 @@
# SMP — Simplex Messaging Protocol
> Unidirectional messaging queues with sender/receiver separation.
## Users
## Guarantees
## Privacy Properties
-9
View File
@@ -1,9 +0,0 @@
# XFTP — File Transfer
> Encrypted file transfer via content-addressed chunks.
## Users
## Guarantees
## Privacy Properties
-7
View File
@@ -1,7 +0,0 @@
# XRCP — Remote Control
> Remote control of mobile clients from desktop.
## Users
## Trust Model
-5
View File
@@ -1,5 +0,0 @@
# Concepts & Entity Index
> Domain concepts with cross-references to spec/ and src/.
<!-- Each concept: name, definition, where it appears in spec/ and src/ -->
-5
View File
@@ -1,5 +0,0 @@
# Glossary
> Domain terminology used across simplexmq.
<!-- Each term: name, definition, where used -->
-5
View File
@@ -1,5 +0,0 @@
# Design Goals
> Verified against protocol specs and code.
<!-- Each goal: statement, source (which protocol spec), verification status -->
-5
View File
@@ -1,5 +0,0 @@
# Invariant Rules
> Invariants users depend on: privacy, delivery, ordering, security.
<!-- Each rule: ID (PR-XX), statement, rationale, enforcement (qualified function name), test coverage -->
-23
View File
@@ -1,23 +0,0 @@
# Threat Model
> Comprehensive threat model across all protocols.
Consistent with threat models in:
- `protocol/overview-tjr.md` (cross-protocol)
- `protocol/simplex-messaging.md` (SMP)
- `protocol/agent-protocol.md` (Agent: duplex connections, ratchet, queue rotation)
- `protocol/xftp.md` (XFTP)
- `protocol/xrcp.md` (XRCP)
- `protocol/push-notifications.md` (notifications)
## Actors
<!-- Threat actors and their capabilities -->
## Trust Boundaries
<!-- Per-protocol trust boundaries -->
## Security Properties
<!-- Properties the system must maintain -->