2.0 KiB
Audita Prompt Registry
internal/prompts embeds nine PromptKit YAML definitions under
assets/prompts. The IDs and selected version remain:
modules.glossary.proposal(v1)modules.homophones.proposal(v1)modules.spoken_word.proposal(v1)modules.grammar.proposal(v1)validators.spoken_form_plausibility(v1)validators.meaning_reversal_review(v1)validators.editorial_review(v1)validators.grammar_review(v1)validators.spoken_word_review(v1)
PromptKit reads the embedded definitions and renders their system and user
messages from named string variables. The role-bound adapter will supply
HardeningPolicy from the single embedded assets/shared/prompt_hardening.md
fragment after caller variables, so callers cannot replace that policy. Proposal prompts receive the
section JSON, glossary JSON where used, and transcript description block.
Validator prompts receive the correction payload and description block.
The prompt assets retain the prior task instructions and output-schema
association. The role-bound runtime will supply the complete JSON Schema output contract
and repair count; the definition does not own an operator-facing repair default.
internal/framework/responseschema remains the only embedded source for
correction_set.v1.json and validator_decision_set.v1.json. It exposes that
filesystem to PromptKit and retains Audita's schema-key lookup. PromptKit's
prepared execution supplies definition and rendered hashes; Audita does not
recompute or promise equality with hashes from the removed template renderer.
The small Audita registry records only prompt ID, version, source, and embedded
path. Prepared runtime metadata belongs in diagnostics rather than the registry.
The structured-call contract carries prompt ID/version, string variables, response-schema key, and logical-call attribution. Module and validator callers are being migrated in their respective work units. See the LLM runtime for runtime assembly and configuration for operator-selected profiles.