prompt_engine/templates.py

Rama main · réplica de lectura del repositorio original.

# SPDX-License-Identifier: BUSL-1.1
# Copyright (c) 2024-2026 Ali Sadeghi Aghili
#: Static, byte-identical prefix built once per system-prompt version by
#: ``prompt_engine.static_prefix.build_static_prefix`` and reused across every
#: request — see ``docs/api-contract-v2.md`` §8. Section order matters: it is
#: what preserves KV-cache reuse, and must not be changed casually.
STATIC_PREFIX_TEMPLATE = """
{system_prompt}

==================================================
BUSINESS RULES
==================================================

{business_rules}

==================================================
METRICS
==================================================

{metrics}

==================================================
DATABASE SCHEMA
==================================================

{schema}

==================================================
RELATIONSHIPS
==================================================

{relationships}

==================================================
EXAMPLES
==================================================

{examples}
"""

#: Variable suffix appended after :data:`STATIC_PREFIX_TEMPLATE`. Only this
#: part changes between requests: detected value filters, resolved
#: warehouse values, prior-turn session context (empty until sessions
#: land), and the question itself. Never put per-request content anywhere
#: in the prefix above — see the module-level warning in
#: ``prompt_engine.static_prefix``.
#:
#: ``{resolved_values}`` (Finding 19, 2026 audit) is deliberately its own
#: section, separate from ``{filters}`` just above it: ``filters`` mixes
#: values pulled straight from the question's own text with values
#: matched against the live warehouse (``retrieval/context_retriever.py``
#: merges both into one dict with no way to tell them apart afterwards),
#: while ``resolved_values`` -- rendered by
#: ``prompt_engine.builder.PromptBuilder`` via
#: ``prompt_engine.untrusted.fence_untrusted`` -- carries ONLY the
#: warehouse-sourced ones, fenced and explicitly labelled as data rather
#: than instructions. See ``prompt_engine/untrusted.py``'s module
#: docstring for the full reasoning.
#:
#: ``{access_notes}`` carries the calling principal's column restrictions that
#: the model can comply with up front (join-only columns). It is empty --
#: and the template renders byte-for-byte as it did before the field existed
#: -- for a principal with none; when present it brings its own
#: ``COLUMN ACCESS`` heading, which is why it sits flush against the blank
#: line on either side instead of having one of its own.
SUFFIX_TEMPLATE = """
==================================================
DETECTED FILTERS
==================================================

{filters}

IMPORTANT:

The detected filters are canonical business values.

When generating SQL:

- Use filter values exactly as provided.
- Do not rewrite filter values.
- Do not shorten filter values.
- Do not replace filter values with aliases.
- If Ring = "تالار پتروشیمی" then SQL must use:

r.Name = N'تالار پتروشیمی'

NOT:

r.Name = N'پتروشیمی'

==================================================
RESOLVED WAREHOUSE VALUES
==================================================

{resolved_values}

==================================================
SESSION CONTEXT
==================================================

{session_context}
{access_notes}
==================================================
USER QUESTION
==================================================

{question}

SQL:
"""

#: Legacy per-question template — kept for the retrieval fallback path (used
#: when ``prompt_engine.static_prefix.should_use_static_prefix`` is False,
#: i.e. a knowledge base too large for ``STATIC_PREFIX_TEMPLATE`` to be
#: economical). See ``prompt_engine.builder.PromptBuilder._build_retrieval``.
PROMPT_TEMPLATE = """
{system_prompt}

==================================================
BUSINESS RULES
==================================================

{business_rules}

==================================================
DATABASE SCHEMA
==================================================

{schema}

==================================================
RELATIONSHIPS
==================================================

{relationships}

==================================================
DETECTED FILTERS
==================================================

{filters}

IMPORTANT:

The detected filters are canonical business values.

When generating SQL:

- Use filter values exactly as provided.
- Do not rewrite filter values.
- Do not shorten filter values.
- Do not replace filter values with aliases.
- If Ring = "تالار پتروشیمی" then SQL must use:

r.Name = N'تالار پتروشیمی'

NOT:

r.Name = N'پتروشیمی'

==================================================
RESOLVED WAREHOUSE VALUES
==================================================

{resolved_values}
{access_notes}
==================================================
EXAMPLES
==================================================

{examples}

==================================================
USER QUESTION
==================================================

{question}

SQL:
"""