straymark-charter-new

To create a scope charter, you provide a one-line title and an XS|S|M|L effort estimate, optionally linking an AILOG or SpecKit origin. The CLI then generates a sequentially numbered charter file at .straymark/charters/NN-slug.md to establish a bounded scope contract.

A multi-session scope contract declares a stable, bounded scope for implementation blocks lasting longer than one day. You need one to prevent accidental scope drift across phases and to enable ex-post telemetry aggregation when the work closes.

You link a charter scaffold to a SpecKit spec or AILOG entry by passing the --from-spec or --from-ailog flag during creation. This wires the origin metadata into the charter file for traceable audits.

Charter scaffolding is designed for implementation blocks longer than one day or work spanning multiple tasks across phases. For shorter, single-session tasks, a full scope contract is unnecessary and adds overhead.

Telemetry tracking works by capturing the charter's declared scope and origin up front, then aggregating ex-post telemetry data at close. This relies on explicit operator actions for lifecycle transitions from declared to in-progress to closed.

The best way to manage scope drift is to scaffold a charter early that defines bounded multi-session scope. This establishes a stable scope contract before implementation, ensuring ex-post telemetry can be aggregated to audit deviations.