AGENTS.md — Public SIE contributor guide

Scope

This repository is the source of truth for the open-source SIE server, SDKs, gateway, sidecar, configuration service, MCP service, Helm chart, and public release automation. Keep changes self-contained: a clean clone must build and test without access to another repository, private registry, or secret.

Commands

• Use ordinary shell tools for read-only inspection.
• Run project tasks with mise run <task> and pass task arguments after --.
• Run version-managed executables that are not tasks with mise exec --.
• Bootstrap a clean checkout with ./tools/init.sh.
• Run mise tasks before assuming a task exists.

Every pull request runs the public lint, typecheck, unit, integration, and package/container checks; these are not selected by changed paths. Benchmark and quality-evaluation jobs are not part of this CI. The separate Real models workflow serves pinned public checkpoints on CPU nightly, on manual dispatch, and for pull requests that change model-serving, SDK, or integration paths. It is advisory and not part of CI / Required.

The main tasks are mise run lint, mise run typecheck, mise run test, mise run test-integrations, mise run ts -- build, mise run ts -- lint, mise run rust-check, mise run rust-test, and mise run helm -- lint. Build the TypeScript workspace before checking dependent packages in isolation. The standalone Candle worker uses mise exec -- cargo <command> --manifest-path packages/sie_server_rust/Cargo.toml --locked.

Development boundaries

• Keep the root Python and pnpm locks authoritative; standalone Rust crates keep their checked-in locks.
• Use sie_sdk.SIEClient for SIE API examples. Use current gateway terminology; legacy wire names remain only where compatibility requires it.
• Keep __init__.py files empty and imports at module scope except for optional dependencies.
• Do not commit secrets, credentials, generated Helm dependencies, staged chart model/bundle files, build output, or package archives.
• Trust-boundary changes to ingress, authentication, identity handling, billing, or wire protocols require an adversarial security review.
• Use Conventional Commits.

Releases

Read RELEASE.md before authoring, publishing, or recovering a release. Terraform modules have independent release lifecycles: a new SIE version alone does not require module documentation updates or module releases. Follow Terraform module follow-up only when a release changes an infrastructure requirement or exposes a real compatibility issue. Documentation-only changes use non-releasing commits; reserve module versions for actual module changes. An explicitly authorized one-time Registry documentation refresh follows the exception in that guide; never retag an existing module version to change its documentation.

Release automation is intentionally fail-closed. Package, image, and chart builds may run without publication authority; external publication additionally requires the protected workflow inputs and repository publishing latch described in RELEASE.md. Never bypass version, tag, source-revision, or full-set verification.

Release-PR authoring is independently default-off and requires the repository variable PUBLIC_RELEASE_AUTOMATION_ENABLED to be exactly true. Configure the release App and protected release-automation environment before enabling it; do not confuse this authoring gate with artifact publication enablement.

The release-please baseline is 0.7.3 at exact public commit 60996d9c30168e0f8e85b680295f147fdee87f61. Keep that full SHA as the checked-in bootstrap boundary; do not create a substitute baseline tag or move the boundary to a later commit. Publication retries reuse the original release run and artifacts, not a newer-main rebuild.