Finish the references implementation for the extraction module and update roadmap documentation
This commit is contained in:
@@ -45,11 +45,14 @@ LLM-backed pipeline work. Config bindings resolve relative to the config file,
|
||||
CLI bindings resolve relative to the current working directory, and materialized
|
||||
reference content is passed only to the matching lane extractor through
|
||||
`ExtractionRequest`. Materialization accepts UTF-8 text files, computes
|
||||
`sha256:` content digests, records file origins, enforces declared byte limits,
|
||||
and warns for empty bound files. Reference content is omitted from diagnostics
|
||||
and manifests. The CLI writes provenance-only resolved reference diagnostics,
|
||||
and the run manifest records lane-scoped reference provenance separately from
|
||||
source digests.
|
||||
`sha256:` content digests, records file origins, infers canonical base media
|
||||
types from file extensions, enforces declared byte limits, and warns for empty
|
||||
bound files. Media-type acceptance is checked only when a slot declares
|
||||
`AcceptedMediaTypes`; unknown extensions are recorded as
|
||||
`application/octet-stream`. Reference content is omitted from diagnostics and
|
||||
manifests. The CLI writes provenance-only resolved reference diagnostics, and
|
||||
the run manifest records lane-scoped reference provenance separately from source
|
||||
digests.
|
||||
|
||||
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