Ployz

Ployz is a Rust container orchestrator with deliberately weak operational semantics and its own product identity.

Language

Ployz: The product, CLI, and daemon reconstructed in this repository. Avoid: Uncloud, Ployz2

Cluster: The product-level mesh as observed from one entry machine. A Cluster is not a globally authoritative entity or complete view. Avoid: Cluster truth, authoritative cluster state

Machine: A durable participant identity in a Cluster. Its local lifecycle and its membership as observed by another Machine are separate facts. Avoid: Node, host, member

Machine ID: The durable opaque identity of one Machine. It is distinct from its mutable Machine Name. Avoid: Machine Name, hostname

Machine Name: A human-facing selector for a Machine that may be ambiguous. It is not an identity or a globally unique value. Avoid: Machine ID, unique hostname

Machine Target: The unresolved name-or-ID text used to target one Machine. It is not a wildcard and is not a unique identity. Avoid: Fan-out Selector, unique hostname

Fan-out Selector: A selection of every visible Machine or one Machine Target. * is the only wildcard spelling. Avoid: Machine Target, all

Local Machine Phase: A Machine's own lifecycle phase: uninitialized, joining, participating, or resetting. Joining includes catching up unless a concrete behavior requires that stage to be distinguished. Avoid: Machine state, membership state, readiness

Membership Observation: One Machine's potentially incomplete or stale judgment that another Machine is unknown, up, suspect, or down. It is not the observed Machine's lifecycle or an authoritative liveness fact. Avoid: Machine status, cluster membership truth

Service: An observer-derived grouping of Service Containers. It is not an independently persisted entity and has no canonical current specification or state. Avoid: Workload, application, desired service

Service ID: The durable opaque identity used to group Service Containers into a Service. Avoid: Service Name

Service Name: A human-facing selector for a Service that may resolve to several Service IDs. Avoid: Service ID, unique service name

Service Selector: The unresolved name-or-ID text used to select a Service. Avoid: Service Name as identity

Service Attempt: One Service Name this Deploy will apply from the target. Attempts are implicitly required until a requirement distinction exists. Avoid: selected-service list as a prune flag

Service Container: A managed Docker container carrying the Resolved Service Spec from its creation. It is one observed instance of a Service, not a replica identity or the canonical Service definition. Avoid: Replica, service record

Healthcheck: A present probe declaration on a Service Container. It is Disabled or Configured. Absence means the image's probe is inherited or that no probe is available, not a third kind of Healthcheck. Avoid: health check flag, disabled boolean plus command

Disabled Healthcheck: An explicit Healthcheck that turns probing off. It is not an absent Healthcheck. Avoid: inherited healthcheck, missing healthcheck

Configured Healthcheck: A Healthcheck with a non-empty command that probes the container. Avoid: enabled healthcheck

Hook Container: A managed Docker container that executes a pre-deploy hook rather than serving as an instance of the Service. Its identity and runtime observation remain distinct from those of Service Containers. Avoid: Service Container, sidecar

Container ID: The durable runtime identity of one managed Docker container. Generated container names are display values, not identities. Avoid: Container name, replica identity

Container Selector: The unresolved Container ID, display name, or ID prefix used to select one Container. Avoid: Container name as identity, replica identity

Container Runtime Observation: A point-in-time Docker lifecycle observation such as created, running with health, paused, restarting, exited, removing, dead, or an unknown external state. Container observations do not combine into an authoritative Service state. Avoid: Service state, desired state

Requested Service Spec: The normalized service configuration supplied to a Deploy before placement and container-specific resolution. Avoid: Current service spec, desired state

Resolved Service Spec: The exact service configuration attached to a Service Container when it is created. Different observed containers in one Service may legitimately carry different Resolved Service Specs. Avoid: Current service spec, canonical service spec

Deploy: A bounded command attempt that calculates and executes work against an observer-relative snapshot. It is not a persistent resource or durable workflow. Avoid: Deployment resource, reconciliation loop

Deploy Intent: The complete desired Services for one Deploy together with which of those Services this command applies. Services in the target that are not applied are unchanged. Avoid: leftover filtered Compose project, Cloud Attempt Target, Full/Partial/Adhoc as kinds of Deploy

Deploy Snapshot: The observer-relative Machine, Service Container, and Docker Volume observations gathered for one Deploy. It is Live Observation for a bounded command, not Cluster truth. Avoid: current cluster state, desired state, cluster snapshot

Deploy Plan: The ephemeral sequence of operations calculated for one Deploy. It may complete only a prefix and is neither persisted nor generally rolled back. Avoid: Desired state, workflow

Deploy Preview: The observer-relative plan-plus-warnings offered for confirmation before one Deploy executes. It is Live Observation shaped for a decision, not persisted state. Avoid: persisted plan, cluster decision record

Deploy Outcome: The evidence produced by executing a Deploy Plan: its completed prefix, any failed operation, its unexecuted suffix, and any narrow replacement compensation attempted. It does not imply atomicity or general rollback. Avoid: Bare deployment error, transaction result

Docker Volume: A machine-local Docker storage resource and possible placement anchor. Its name is meaningful only together with its Machine. Avoid: Cluster volume, replicated volume, CSI volume

Machine Pool: A ZFS storage budget on one Machine, chosen when that Machine joins and not addable afterwards. Provisioned Volumes live on it. Docker's data-root, image layers, and build cache do not. Avoid: Cluster pool, auto-created pool, dedicated disk, Machine ZFS Pool, ZFS-enabled cluster

Provisioned Volume: A Docker Volume backed by a dataset on a Machine Pool, with a maximum size declared in Compose under x-volumes. A name declared only under volumes: is not one and is unaffected. Avoid: Managed Volume, Managed ZFS Volume, cluster volume, storage class, CSI volume

Service Volume Reference: A name used within one Service specification to refer to storage. It is not the Docker Volume name or a machine-independent storage identity. Avoid: Docker Volume name, cluster volume ID

Bind Mount: A container mount whose source is a path on its Machine. It is distinct from a Docker Volume, a Provisioned Volume, and tmpfs. Avoid: Docker Volume, Provisioned Volume, cluster storage

Tmpfs Mount: An ephemeral memory-backed container mount. It is distinct from a Bind Mount, Docker Volume, and Provisioned Volume. Avoid: Docker Volume, Provisioned Volume, persistent volume

Machine Subnet: The IPv4 /24 subnet locally selected for one Machine's containers. It is an optimistic allocation candidate and may overlap another Machine Subnet after concurrent changes. Avoid: Reserved subnet, globally allocated subnet

Management Address: The address used to reach a Machine's management plane over the mesh. It is distinct from container, gateway, and endpoint addresses. Avoid: Container address, public endpoint

Machine Gateway: The Machine-local gateway address for its container network. Avoid: Management Address, ingress gateway

Container Address: The address assigned to one container within its Machine Subnet. Its apparent cluster-wide uniqueness depends on optimistic Machine Subnet allocation. Avoid: Management Address, globally unique container address

Serving Container: A Service Container that is healthy and has a Container Address. It is observer-derived eligibility to receive traffic, not a replica identity. Avoid: replica, endpoint, upstream

Internal DNS Answer: An observer-local, TTL-zero A answer derived from replicated healthy Service Container observations. It is not persisted and is not authoritative Cluster state even though the DNS response is authoritative for the .internal zone. Avoid: Service registry record, membership-filtered endpoint set

Ingress Hostname: The HTTP hostname a Service publishes through ingress: assignment from the reserved hosted DNS domain, or an explicit validated hostname. An empty string is not an assignment signal. Avoid: empty hostname sentinel

Certificate Material: The certificate and private key held in cluster state for one Ingress Hostname. It is served as given; it is not an issuance request and not a local proxy store. Avoid: Caddy certificate, ACME certificate, cert secret

Certificate Policy: The cluster-state values that steer certificate issuance: authority directory, external account binding, key type, renewal fraction, backoff bounds, and probe timeout. Absence means the daemon's built-in defaults. A challenge kind the daemon cannot perform is a refusal, not a default. Avoid: ACME config, daemon certificate constants, CA settings

Cluster DNS Verdict: Whether an Ingress Hostname's resolved addresses intersect this Cluster's Machine public addresses. It is not Caddy health, certificate readiness, or a Deploy failure. Avoid: DNS health, certificate gate, reachability

Nearest DNS Selector: An Internal DNS selector that orders addresses from the observing Machine's subnet before other addresses. It expresses subnet locality, not measured reachability or latency. Avoid: closest Machine, available endpoint

Machine-Service DNS Selector: An Internal DNS selector that names one Machine ID together with one Service Name. It is not a Service identity. Avoid: machine-qualified service name, replica address

Advertised Endpoint: An endpoint a target Machine publishes as a way peers might reach it. Avoid: Selected Endpoint, current endpoint

Selected Endpoint: The endpoint one observing Machine currently selects for reaching a target Machine. Different observers may select different endpoints for the same target. Avoid: Advertised Endpoint, globally current endpoint

Cloud Relay: The hosted byte pipe a Machine dials out to and holds open so Cloud can reach it without an inbound route. It carries opaque streams and interprets none of them. It is not a Machine, not a mesh peer, and holds no Cluster observation. Avoid: Machine Proxy, tunnel binary, control plane

Cloud Pairing: The cluster-scoped grant of a Cloud Relay endpoint and Pairing Credential that makes a Cluster's Machines dial out. Absence means no Machine dials. It authenticates a Cluster to the relay and is not a per-Machine credential, not daemon-side authorization, and not proof any Machine is currently connected. Avoid: per-Machine credential, login, daemon authn

Pairing Credential: The bearer Cloud Pairing grants a Machine to authenticate Register. It is rejected on Dial. Avoid: Dial Credential, per-Machine JWT

Dial Credential: The bearer Cloud presents on Dial. It is not the Pairing Credential and does not authenticate Register. Avoid: Pairing Credential, cluster credential

Tunnel ID: The Relay-issued identity of one opaque splice, carried on Open and Attach. It is not a Machine ID. Avoid: session id, connection id, stream id

Live Observation: Data obtained by directly querying a Machine at a point in time. It may still be incomplete, entry-relative, or obsolete immediately after collection. Avoid: Current truth, complete state, authoritative state

Replicated Observation: Data read from the local eventually convergent store. It may be stale, incomplete, or contradictory even after storage convergence. Avoid: Live state, desired state, cluster truth

Partial Result: A command or fan-out result containing both successful values and target-specific failures or omissions. It is an expected outcome, not an atomic transaction failure. Avoid: Complete result, rollback signal

Name Ambiguity: The expected condition in which one Machine or Service name matches multiple durable identities. Ployz preserves every match and does not choose or repair a winner in the domain model. Avoid: Duplicate error, canonical winner