Source in. Component out.

PitFast standardizes microservice outputs using the WebAssembly Component Model. Regardless of whether your code is written in Rust, Go, or TypeScript, the compiler produces a deterministic, content-addressed artifact.

Build Pipeline Output Directory

project/

├── src/main.go

├── pit.toml

├── pit build

└── .pit/

├── artifact.json — Manifest, schema, WIT world

└── build/service.wasm — Content-addressed binary

The 4 Artifact Primitives

ArtifactManifest

A declarative JSON descriptor specifying component version, WIT world target (wasi:http/proxy), exported functions, and execution constraints.

ArtifactDigest

The cryptographic SHA-256 hash calculated over the exact bytes of the compiled .wasm binary. This anchor ensures zero runtime drift.

Component World

The WebAssembly Interface Types (WIT) boundary defining what system calls the Component can import (such as HTTP client) and export (such as HTTP handler).

Build Fingerprint

A composite hash of the source code, compiler toolchain, and build flags. If the fingerprint matches an existing entry, compilation completes instantaneously.

Build and Verify

Run the build command and inspect the generated artifact manifest:

bash

# Compile the local project
pit build

# Inspect the generated manifest and SHA-256 digest
cat .pit/artifact.json

Next: Learn about the underlying component architecture:WASI Components Overview →