Platform

Prompts as versioned artefacts

A prompt that changes without a version is an experiment you cannot repeat. Planverity treats prompt content as part of the execution record.

Attributable to an execution

Every manifest records the classifier, token estimator, planner and quality-model versions in force. Prompt versioning extends the same discipline: knowing which text produced a result is a precondition for improving it.

Change resets assumptions

The same rule that governs tool schemas applies here — when content changes materially, prior judgements about it no longer automatically carry forward. Silent reuse of a stale approval is how an approved artefact gets repurposed.

Partially built

Version provenance is recorded per execution today. A prompt registry with diffing and rollback is designed but not shipped, and is not part of the beta.

Elsewhere in the platform