service-foundation
Foundations for standalone runnable services and host-side companion processes.
Current Status
2026.10.17.2026 is released together with app-foundation, connection-hub and
project-board at one version (W322). It includes a generic
host-relay lifecycle under service_foundation.host_relay:
HostRelayAdapterdefines one asynchronouspoll_once()domain boundary;HostRelayRuntimeowns repeated execution, health, stop, and bounded retry;HostRelayPolicydefines poll and retry timing;- an adapter may return
next_poll_secondsand implementwait_for_wakeup(timeout_seconds, stop_event)so a live transport can start the next reconciliation cycle immediately; - entry-point discovery uses
service_foundation.host_relay.adaptersfor separately packaged adapters.
python -m pip install service-foundation
An adapter owns domain translation and returns bounded cycle metadata. The runtime emits lifecycle metadata and result-key names; it does not copy domain payloads into observer events.
Boundary
A standalone service needs a host layer around its application logic:
- composition and launcher contracts;
- browser-session and service-workload authentication surfaces;
- service-owned session issuance and verification;
- configuration, health, and readiness contracts;
- migration invocation, while the application owns its migrations;
- lifecycle for a local or remote companion process.
The host-relay runtime does not know MCP, Data Bus, credentials, agents, mail, journals, or any product vocabulary. A product composition root supplies an adapter, opens whatever governed transport that adapter needs, and translates transport events into wakeups. Poll timing remains reconciliation policy even when ordinary work is push-driven.
service-foundation does not import app-foundation, and app-foundation
does not import service-foundation. Products may depend on either or both.
The in-progress generic durable decision coordinator and PostgreSQL store live
under service_foundation.coordination. Their v2 canonical authority bytes
and frozen test vector are documented in
docs/service-foundation/durable-decision.md.
The package has not been released with this coordination feature yet.
License: MIT. Source: https://github.com/elenaviter/app-ecosystem
1 maintainer
Metadata
1 maintainer
Release files for service-foundation 2026.10.17.2026
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| service_foundation-2026.10.17.2026.tar.gz | 35.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| service_foundation-2026.10.17.2026-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 57.1 kB
Release files / service_foundation-2026.10.17.2026.tar.gz
| Download URL | service_foundation-2026.10.17.2026.tar.gz |
|---|---|
| Size | 35.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e24ee8f088ef40614e3bb15a5b597d137329de390051455d04e0e270a0b9b68
|
|
BLAKE2b-256 checksum How to use checksums |
4f6a99ae70f679678dfabbc5d0c59eccd8a057157d3dbd4c236228e6e1c0cddd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / service_foundation-2026.10.17.2026-py3-none-any.whl
| Download URL | service_foundation-2026.10.17.2026-py3-none-any.whl |
|---|---|
| Size | 21.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b55425512ecf1cacb5c615ac10c17d5932a1412a6df6c4e14a9496263f0d9ef3
|
|
BLAKE2b-256 checksum How to use checksums |
ea1e08e60b1b1641036289e717ad28c9b350c1570575594007f388617f6b4ac5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logSecurity for service-foundation 2026.10.17.2026
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for service_foundation-2026.10.17.2026.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
