Home /Modules/server-edition/README.md

README.md

server-edition/moral/2/README.md · 151 line(s) · markdown

<img align="right" src="https://github.com/mearvk/SLeeLa/blob/master/images/debian/debian-logo.png" width="75" height="75" alt="SLeeLa">

<img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela/sleela-logo-004.jpg" alt="SLeeLa">

Discord-2™ — SLeeLa Server and Service — Service 2 — v2.0.2

Service 2 is the expanded Server and Service package. It separates the authoritative SLeeLa server program from configuration and lifecycle control.

Layout

Runtime state remains in server-edition/inbox and server-edition/state.

Configuration

The configuration is plain KEY=VALUE data. Unknown keys and invalid values are rejected. Configuration is never evaluated as shell code.

Supported keys are engine, inbox, state, server_source, log, mode, tick, foreground, sha256_manifest, and allow_network.

The default network policy is false. Service 2 does not itself create a public listening socket.

Server and Service

Server means the SLeeLa program that processes owned inputs. Service means the lifecycle/configuration boundary that starts, constrains, records, and stops that program. This follows the useful systems distinction that a service is a software component providing functionality or participating in a capability. NIST also recommends careful installation and configuration before external exposure of server software. citeturn0search2turn0search12

Integrity

The package prefers security/important-sha256-manifest.json and passes that location to the SLeeLa engine. Configuration changes are therefore part of the deployable baseline. NIST configuration-management guidance emphasizes identifying, controlling, recording, and reporting controlled components and configuration changes. citeturn0search9turn0search13

Design Activity

Service 2 uses the shared SLeeLa Design Activity model. Correctness, reproducibility, observability, safety, resource discipline, and interoperability are engineering dimensions. Variance is a comparison against a declared engineering reference profile; it is not scientific measurement uncertainty.

Installation

See INSTALL.md and the platform files under install/ and service/.

Example:

server-edition/moral/2/serverd --help server-edition/moral/2/serverd --design-activity physics 98 95 100 95 85 85

Programmatic theme

Discord-2™ is the programmatic name and implementation theme assigned to Service 2 in the SLeeLa Server Edition series. It is an implementation name only and does not indicate sponsorship, endorsement, ownership, or technical affiliation with Discord Inc.

Discord and related Discord marks are third-party trademarks. No Discord logo, trade dress, or proprietary Discord asset is included by this naming convention. Discord's published brand guidance states that permission is required for uses of its marks beyond permitted cases. citeturn0search3turn0search2

Module version

Service 2 module: 2.0.2

The port-awareness addition is a backward-compatible patch-level update to this implementation generation. Shared firewall lifecycle support is provided by port-awareness module 1.0.0.

Port awareness and firewall lifecycle

Service 2 declares port, port_protocol, firewall, and firewall_required. The default is TCP port 19866 with automatic host-firewall selection.

At startup Service 2 removes a stale Discord-2™ rule, opens the configured port, and only then starts Server.sleela. On normal completion or failure, the lifecycle cleanup closes that rule. The shared controller detects the host OS/version and uses UFW or firewalld on Linux, PF on macOS, or the Windows Defender Firewall PowerShell controller on Windows.

The firewall rule is owned by the Server Edition lifecycle and is not a replacement for socket binding, NAT, TLS, or application authentication.

HTTP multiplexing and large-file DOWNLOAD

Service 2 is wired to the shared api/http-multiplexing/ source through server-edition/http/httpctl. Its configuration now supports http_version, logical_port, download_size_bytes, and http_api. The logical PORT namespace is exactly 10^48 values and is independent of the native firewall port. HTTP 2.1 uses HTTP/2 stream multiplexing. Files over 50,000,000 bytes select resumable DOWNLOAD mode with SESSION-ID, DATETIME, FILE-ID, FILE-NAME, INDEX, OFFSET, and TOTAL-SIZE resume state.

Port lifecycle and service negotiation

Each Server Edition has a named basic scanning/service-discovery port (scan_port, default 22220). The port is opened by the firewall controller while the server is running and closed when the server stops. Multiplex-capable services may negotiate their logical service through this port; a Mature Service may then open its own native port only for the duration of that service. Logical SLeeLa HTTP ports remain distinct from native firewall ports. UFW, firewalld, PF, or Windows Defender Firewall is used according to the host OS. A shutdown cleanup path must remove both the scan-port rule and any service-specific rules.

Traffic and packet logging

The Server Edition maintains a traffic log for the named basic probe port (default TCP 2222), the basic scan/service-discovery port (default TCP 22220), the configured server port, and the International Strernary reference port 20000. When packet capture is available, the logger records timestamps, numeric source/destination IP addresses and ports, protocol information, and packet payload bytes in a diagnostic packet representation. HTTP traffic is therefore retained to the extent it is visible at the transport layer; encrypted HTTPS/HTTP/3 payloads remain encrypted rather than being decrypted by the logger. Packet capture is best-effort and requires the host's packet-capture privileges. Logging stops during server shutdown.

The port-20000 reference comes from mearvk/Java.Web.Server.Telnet.Front.Java.21, whose repository identifies Strernary on port 20000 and includes a Strernary liveness check. See the cited repository evidence in the project history.

Privacy-preserving network records

The Server Edition consumes its raw traffic log at least daily and when it reaches 50 MiB. The retained message.digest is redacted for IP addresses, national-data fields, contact data, MAC addresses, and packet payloads. Records are stored under a UTC dated hierarchy:

state/message-digest/DATE/TIME/message.digest

A separate known.connections record is created under:

state/known-connections/DATE/TIME/known.connections

Active port verification is disabled by default. If an operator explicitly enables it with SLEELA_ACTIVE_PROBING=true and supplies SLEELA_PROBE_ALLOWLIST, the shared verifier checks only the configured known ports (default 2222, 22220, 19866, and the external Strernary reference 20000). Retained records do not contain the probed IP/hostname. This prevents the Server Edition from becoming an unrestricted Internet scanner.

International probe, traffic records, and privacy

Service 2 treats activity arriving at the basic probe port (2222) and basic scan/service-discovery port (22220) as potentially international requests. This is an observation and routing classification; it does not itself grant legal, diplomatic, governmental, or network authority.

Raw traffic is consumed at least daily and when it reaches 50 MiB. The retained digest removes IP addresses, MAC addresses, national/citizen/bank/banker/Cromsmrus identity data, contact data, and packet payloads. Records are stored under state/message-digest/DATE/TIME/message.digest. Known-connection records are stored under state/known-connections/DATE/TIME/known.connections.

Active port verification is disabled by default. Explicit verification requires SLEELA_ACTIVE_PROBING=true and an operator-supplied SLEELA_PROBE_ALLOWLIST; retained records do not preserve the probed endpoint address.

These controls support the SLeeLa Kind Sternary Port Assistor model: controlled communications assistance toward a designated Master Sternary service without treating the relay itself as an international legal authority.

Dynamic resolver

Server Edition 2 can use the shared /resolver subsystem for event-scoped hostname-to-IP, IP-to-hostname, and canonical path resolution. Configure resolver_target and, when required, resolver_require_dynamic=true. The resolver is advisory and does not install operating-system routes or alter firewall policy.