opname

Documentation

Overview

Package opname is the single source of truth for what a stack name and an operation (rule) name may contain. Names are persisted contract identifiers — they become DB keys, `stage = stack/scope` path components, trace directory names, and continuation `opDir` segments — so they are validated (rejected) at the write boundary rather than silently transformed. The filesystem sanitizers in the *store backends remain as belt-and-suspenders; this is the loud upstream gate.

Pure: no FS/DB/deps, so both the admin API and the opstack loader can import it without a cycle. Tenant-reservation policy (e.g. boot/* is _sys-owned) is NOT here — that stays with the admin layer that knows the acting tenant.

Index

• Variables
• func Valid(name string) error
• func ValidStack(name string) error

Variables

var ErrName = errors.New("invalid name")

ErrName is the sentinel for any invalid name (wrapped with detail).

Functions

func Valid

func Valid(name string) error

Valid reports whether name is a usable operation/rule name.

func ValidStack

func ValidStack(name string) error

ValidStack reports whether name is a usable stack name. A stack name is one or more "/"-joined segments (e.g. "hello-world", "_sys/boot"); every segment obeys the same charset as an operation name, so there is no empty/'.'/'..'/'%'/leading-or-trailing-slash/double-slash form.