Webservice Catalog
The canonical runtime inventory is the generated service inventory. It reconciles source deployables, the included development Compose estate and the release bundle. Use it to select a project or deployment target; this page is an ownership guide and does not maintain a second project census based on filename suffixes. Hosts named Engine, Api, WebApi or Service can also be deployables.
Verified against: 818afdc7523c57b24370f841d99a1ce622cfd9ee (2026-10-07). Re-verify with
python tools/scripts/generate/service-inventory.py --check. Host composition and checked-in Compose definitions support the owner mappings below; no live estate availability or release publication is asserted.
Consolidated owning hosts
| Owning host | Current source project | Carried capabilities | Docker discovery alias / Compose definition |
|---|---|---|---|
evidence-web | src/Evidence/StellaOps.Evidence.WebService | Attestation and evidence-locker APIs under /api/evidence/v1/*. | evidence.stella-ops.local; docker-compose.evidence.yml. |
vulnerabilities-web | src/Vulnerabilities/StellaOps.Vulnerabilities.WebService | Advisory/VEX and binary/symbol hub. | vulnerabilities.stella-ops.local; docker-compose.vulnerabilities.yml. |
offlinekit-web | src/OfflineKit/StellaOps.OfflineKit.WebService | Export-center and offline exchange APIs under /api/offlinekit/v1/*. | offlinekit.stella-ops.local; docker-compose.offlinekit-consolidated.yml. |
findings-web | src/Findings/StellaOps.Findings.WebService | Findings ledger, security and runtime projections under /api/findings/v1/*. | findings.stella-ops.local; docker-compose.findings.yml. |
jobengine-web | src/JobEngine/StellaOps.JobEngine.WebService | Scheduling, PacksRegistry and job execution. | jobengine.stella-ops.local; docker-compose.stella-services.yml. |
advisoryai-web | src/AdvisoryAI/StellaOps.AdvisoryAI.WebService | Advisory assistance, OpsMemory and remediation composition. | advisoryai.stella-ops.local; docker-compose.advisoryai.yml. |
authority | src/Authority/StellaOps.Authority/StellaOps.Authority | Identity and issuer-directory composition. | authority.stella-ops.local; docker-compose.stella-services.yml. |
platform | src/Platform/StellaOps.Platform.WebService | Platform operator read models and Doctor aggregation; service Doctor checks remain with each owning host. | platform.stella-ops.local; docker-compose.stella-services.yml. |
The family worker is a role of its owning service, not a second owner API. The generated inventory records each family’s database/role, worker project and deployment membership. Signer remains a separate host under src/Attestor/StellaOps.Signer/StellaOps.Signer.WebService.
Other deployables — Scanner, SbomService, Policy, Graph, Notify, Timeline, Router, ReleaseOrchestrator and its agent, Integrations, Registry, Replay, Signals, Unknowns, SmRemote and Workflow — are listed with their actual source projects in the generated inventory. That list also records opt-in Tester and infrastructure roles; it does not infer deployment membership from source-project existence.
Address and deployment selection
Docker discovery aliases describe traffic inside the attached network. They do not establish a host-accessible URL, TLS listener or running instance. In particular, the Evidence, Vulnerabilities, OfflineKit, Findings and AdvisoryAI family definitions do not declare host ports. Operator API traffic uses the configured gateway; inspect the selected overlay chain for any direct publication. See the port and host binding registry.
For deployment membership, use the inventory’s Compose, Bundle and Opt-in overlays outside the estate sections. Workflow has a publish key but no default-estate or bundle membership at the verified source revision. Tester is an opt-in QA harness and must not be selected for a production stack.
For runtime authorization and payloads, inspect the owning host’s Program.cs and mapped endpoint classes. Static gateway hints, old OpenAPI captures and a dated probe receipt do not substitute for a current owner contract.
Historical predecessor inventory withdrawn 2026-10-07
The previous manually maintained catalog mixed February 2026 host names with later consolidation notes. Its separate Attestor, EvidenceLocker, ExportCenter, Excititor, BinaryIndex, Symbols, Remediation and Findings Ledger host entries are historical. The generated inventory retains their frozen-project-to-successor mapping, along with the later Scheduler, PacksRegistry, Doctor, Notifier and TimelineIndexer retirements. These predecessor names are not current deployment targets; the freeze records remain unchanged.