manifest/compute-manifest.toml

audience: ai

The ComputeManifest the coalition folds into the image pre-hash. Deriving blake3(canonicalized(this)) yields the pre-hash that appears in the provider’s card and in any ComputeRequest targeting this binary; the post-hash (MR_TD) is produced by the mosaik TDX builder at build time.

The [bridge_extensions] section is folded into the image pre-hash because it declares which backends the binary drives — different backend support is a materially different binary. Per-operator concrete backend credentials and regions live in the separate backends boot config (src/config.rs), not here.

# ComputeManifest for the compute-bridge provider
# binary itself. Deriving blake3(canonicalized(this))
# yields the image pre-hash the coalition will see in
# the provider card.
#
# The post-hash (MR_TD) is produced by the mosaik TDX
# builder after building the crate; it is printed by
# the builder and must be pasted into
# manifest/compute-manifest.post-hash.txt for the
# provider card publication step.
#
# See book/src/contributors/basic-services.md#compute
# for the ComputeManifest shape.

[crate_ref]
name        = "compute-bridge"
version     = "0.1.0-prototype"
commit_hash = "0x0000000000000000000000000000000000000000000000000000000000000000"
# commit_hash is the blake3 of the git tree the binary
# was built from; filled in by CI at build time.

# Minimum hardware the bridge binary itself needs to run
# its own loops and the AWS / GCP / Azure SDK clients
# plus any bare-metal SSH control sessions.
min_cpu_millicores = 2000
min_ram_mib        = 2048
min_storage_gib    = 8

# TDX is required: the bridge's honesty rests on the
# MR_TD the coalition verifies against this manifest.
tdx = "Required"

# The bridge's own mosaik traffic only; AWS / GCP / Azure
# control-plane calls plus bare-metal SSH go via per-
# backend allowlists enforced inside the guest.
network_policy = "Allowlist"

# Non-binding duration hint: the bridge runs indefinitely
# while the operator rotates credentials.
duration_hint_sec = 0

# --- Extensions beyond the base ComputeManifest ---
#
# The base spec in basic-services.md is deliberately
# narrow. compute-bridge additionally declares which
# backends its binary will drive. This is binary-specific
# (folded into the pre-hash); per-operator concrete
# regions and credentials live in the backends boot
# config, not the manifest.
[bridge_extensions]
backends_supported = ["aws", "gcp", "azure", "baremetal"]

# Each enabled backend contributes capacity telemetry
# and a region set to the provider card at runtime.
# Operators mix and match:
#
#   - A coalition member with AWS credits and nothing
#     else enables [backends.aws] only.
#   - A member with a rack of bare-TDX hosts enables
#     [backends.baremetal] only; every grant requiring
#     TDX automatically routes there.
#   - A member with all four can accept the widest
#     possible range of grants and let the fleet router
#     choose.
#
# The concrete operator configuration lives in a
# separate backends boot config; see src/config.rs.

Up: compute-bridge.