Deliver references to eligible runtime targets
This commit is contained in:
@@ -60,10 +60,11 @@ Reference flags are resolved against selected chunk, extractor, and normalizer
|
||||
targets before the run starts. Flat slot names are accepted only when exactly
|
||||
one selected target declares that slot. Bound reference files are read before
|
||||
pipeline work starts, validated as UTF-8 text, and recorded as provenance for
|
||||
the target that declares the slot. Runtime reference content is currently passed
|
||||
only to lane extractors. Notarius infers reference media types from file
|
||||
extensions for provenance and for optional slot checks. Reference content is not
|
||||
written to diagnostics, logs, errors, or manifests.
|
||||
the target that declares the slot. Runtime reference content is passed to the
|
||||
chunker, extractor, or normalizer target that declares the slot. Notarius infers
|
||||
reference media types from file extensions for provenance and for optional slot
|
||||
checks. Reference content is not written to diagnostics, logs, errors, or
|
||||
manifests.
|
||||
|
||||
Reference binding precedence is:
|
||||
|
||||
|
||||
@@ -149,10 +149,10 @@ compatibility bindings, and run-time `--reference` or `--without-reference`
|
||||
overrides are applied. Config-relative paths are resolved relative to the config
|
||||
file; CLI reference paths are resolved relative to the current working
|
||||
directory. Materialized bound files must be UTF-8 text. Materialized reference
|
||||
provenance is recorded for chunk, extractor, and normalizer targets; runtime
|
||||
reference content is currently passed only to lane extractors that declare the
|
||||
slot. Reference media types are inferred from file extensions, recorded as
|
||||
canonical base media types, and checked only when a module declares
|
||||
provenance is recorded for chunk, extractor, and normalizer targets, and runtime
|
||||
reference content is passed to the target that declares the slot. Reference
|
||||
media types are inferred from file extensions, recorded as canonical base media
|
||||
types, and checked only when a module declares
|
||||
`AcceptedMediaTypes`; unknown extensions are recorded as
|
||||
`application/octet-stream`. Reference content is not written to diagnostics,
|
||||
logs, errors, or manifests.
|
||||
|
||||
@@ -32,14 +32,15 @@ compares the canonical base media type inferred from the file extension,
|
||||
case-insensitively and without parameters.
|
||||
|
||||
The resolver materializes reference content for chunk, extractor, and
|
||||
normalizer targets. Runtime delivery is currently implemented only for lane
|
||||
extractors through `contracts.ExtractionRequest.References`. Reference material
|
||||
is not source evidence and must not be converted into `SourceRef` values. If a
|
||||
module prompt uses references, load the prompt bundle with the same declared
|
||||
slots and render with `RenderUserSystemWithReferences`. Prompt templates may use
|
||||
the `reference` function for content and the `hasreference` function for
|
||||
conditional sections. Prompt metadata hashes remain based on template source,
|
||||
not rendered reference bytes.
|
||||
normalizer targets. Runtime delivery uses `contracts.ChunkRequest.References`,
|
||||
`contracts.ExtractionRequest.References`, and
|
||||
`contracts.NormalizeRequest.References`. Reference material is not source
|
||||
evidence and must not be converted into `SourceRef` values. If a module prompt
|
||||
uses references, load the prompt bundle with the same declared slots and render
|
||||
with `RenderUserSystemWithReferences`. Prompt templates may use the `reference`
|
||||
function for content and the `hasreference` function for conditional sections.
|
||||
Prompt metadata hashes remain based on template source, not rendered reference
|
||||
bytes.
|
||||
|
||||
Chunk modules receive the structured LLM client through `contracts.ChunkRequest`
|
||||
when they need model-backed chunking. The pipeline runner validates generic
|
||||
|
||||
@@ -53,8 +53,8 @@ empty bound files. Media-type acceptance is checked only when a slot declares
|
||||
`application/octet-stream`. Reference content is omitted from diagnostics and
|
||||
manifests. The CLI writes provenance-only resolved reference diagnostics, and
|
||||
the run manifest records target-stage reference provenance separately from
|
||||
source digests. Runtime reference content is currently passed only to the
|
||||
matching lane extractor through `ExtractionRequest`.
|
||||
source digests. Runtime reference content is passed to the matching chunker,
|
||||
extractor, or normalizer request.
|
||||
|
||||
Prompt bundles can declare reference slots and use `reference` and
|
||||
`hasreference` template functions. Bundle loading validates string-literal slot
|
||||
|
||||
Reference in New Issue
Block a user