103 lines
5.0 KiB
YAML
103 lines
5.0 KiB
YAML
---
|
|
title: Select a Notarius configuration profile through Narratio
|
|
status: proposed
|
|
consumer: rakestraw.dnd Ansible collection and its pipeline role
|
|
|
|
use_case: >-
|
|
The Ansible pipeline role deploys Narratio and Notarius as independently
|
|
configured applications. Operators select Narratio's testing profile to
|
|
develop prompts and other pipeline assets with inexpensive models while
|
|
retaining production settings in the base configuration. That selection
|
|
currently cannot select a Notarius configuration profile, leaving extraction
|
|
on its production settings.
|
|
|
|
desired_outcome: >-
|
|
Narratio's testing overlay can explicitly select Notarius's testing overlay.
|
|
Notarius owns the resulting model choices and any other testing-specific
|
|
settings. The operator selects testing once when invoking Narratio, without
|
|
editing production files or separately invoking Notarius.
|
|
|
|
rationale: >-
|
|
Both applications already use ConfigKit configuration overlays. Selecting
|
|
the downstream overlay preserves each application's configuration ownership
|
|
and supports future Notarius testing adjustments without adding a Narratio
|
|
configuration field for every downstream setting. This is explicit profile
|
|
composition, not a requirement for arbitrary recursive orchestration.
|
|
|
|
requested_interface:
|
|
field: pipeline.notarius.config_profile
|
|
value: Optional Notarius ConfigKit configuration profile name
|
|
supplied: >-
|
|
Invoke Notarius with --config-profile and the selected name when extraction
|
|
executes. The setting is available in Narratio's base configuration and
|
|
its ordinary configuration overlays.
|
|
omitted_or_null: >-
|
|
Do not supply a profile-selection flag. Preserve existing Notarius
|
|
configuration selection behavior.
|
|
downstream_semantics: >-
|
|
Retain Notarius's existing selector semantics, including the default
|
|
selector for its base configuration. Notarius resolves profiles relative
|
|
to its own configuration root, not Narratio's root.
|
|
explicit_selection: >-
|
|
Do not automatically forward Narratio's profile name. The selected
|
|
Notarius profile may have the same name or a different name.
|
|
distinction: >-
|
|
This selects a ConfigKit configuration overlay through --config-profile,
|
|
not a PromptKit LLM profile through --llm-profile. The Notarius overlay
|
|
can itself select the desired LLM profiles using native Notarius settings.
|
|
|
|
illustrative_consumer_configuration:
|
|
note: >-
|
|
These are separate files managed by the Ansible suite, not a proposed
|
|
combined configuration document. The Notarius pipeline and LLM profile
|
|
names are illustrative; the referenced LLM profile must be available to
|
|
Notarius.
|
|
narratio_profiles_testing_yml: |
|
|
notarius:
|
|
config_profile: testing
|
|
notarius_profiles_testing_yml: |
|
|
pipelines:
|
|
dnd-session:
|
|
llm_profile: gemini-flash-latest
|
|
operator_workflow: >-
|
|
Select --profile testing on the ordinary Narratio invocation. Narratio
|
|
selects Notarius's testing configuration overlay when it runs extraction;
|
|
other Narratio testing overrides continue to apply normally.
|
|
|
|
observable_behavior:
|
|
- >-
|
|
Notarius owns overlay discovery, composition, validation, and the effective
|
|
downstream settings. A missing or invalid selected overlay must not silently
|
|
fall back to production or be reported as successful extraction.
|
|
- >-
|
|
Changing the selected Notarius configuration profile must not silently
|
|
reuse Narratio's completed extraction from the previous selection.
|
|
Existing downstream invalidation behavior applies when extraction changes.
|
|
- >-
|
|
Editing Notarius overlay contents behind an unchanged selector retains
|
|
the existing operator responsibility to force extraction when needed.
|
|
This request does not require inspecting or tracking private Notarius files.
|
|
- >-
|
|
Existing credential forwarding remains independently configurable through
|
|
notarius.llm_api_key, including in the Narratio testing overlay when the
|
|
selected Notarius settings require a different credential reference.
|
|
|
|
consumer_follow_up: >-
|
|
After Narratio releases this interface, the standalone Narratio Ansible role
|
|
can expose an optional variable and omit the field when unset. The suite role
|
|
can deploy Notarius's testing overlay and select it from Narratio's testing
|
|
overlay, then distribute the changes through the collection. These consumer
|
|
updates are separate from this upstream feature request.
|
|
|
|
scope_boundaries:
|
|
- No Notarius change is currently required; v0.7.0 supports --config-profile.
|
|
- No separate Narratio-side Notarius LLM-profile selector is requested.
|
|
- No automatic profile-name propagation or downstream configuration rewriting.
|
|
- No new credential discovery, copying, or provider-name remapping.
|
|
- This request specifies consumer behavior, not internal Narratio code changes.
|
|
|
|
references:
|
|
narratio_configuration: ../config.md
|
|
narratio_notarius_integration: ../integrations/notarius.md
|
|
notarius_cli: https://gitea.maximumdirect.net/eric/notarius/src/tag/v0.7.0/docs/cli.md
|