Finalize domain prompt profile roadmap
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Domain-Specific Prompt Profiles Roadmap
|
||||
|
||||
Status: Accepted; implementation plan ready.
|
||||
Status: Implemented.
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -10,9 +10,9 @@ These logical profiles should give each report an appropriate default while
|
||||
allowing operators to replace any definition through the existing configured
|
||||
profile source.
|
||||
|
||||
This roadmap defines the scope, policy, and intended end state. The companion
|
||||
[implementation plan](domain-profiles-implementation.md) owns the ordered work
|
||||
needed to reach that state.
|
||||
This roadmap records the scope, policy, and implemented end state. The
|
||||
companion [implementation plan](implementation.md) records the ordered work
|
||||
and verification used to reach it.
|
||||
|
||||
## User Intent
|
||||
|
||||
@@ -29,22 +29,22 @@ The feature is intended to provide three related benefits:
|
||||
guarantee. A locally hosted lightweight model may still generate slowly on the
|
||||
available hardware.
|
||||
|
||||
## Current State
|
||||
## Pre-Implementation Baseline
|
||||
|
||||
Daily, Today, Tomorrow, and Hourly each declare Promptkit's
|
||||
`gemini-flash-latest` profile as their prompt default. The optional
|
||||
`promptkit.profile` setting overrides that default for every selected report in
|
||||
Before implementation, Daily, Today, Tomorrow, and Hourly each declared
|
||||
Promptkit's `gemini-flash-latest` profile as their prompt default. The optional
|
||||
`promptkit.profile` setting overrode that default for every selected report in
|
||||
an invocation.
|
||||
|
||||
Weatherreporter accepts either `promptkit.profile_file` or
|
||||
`promptkit.profile_dir` and passes that source to Promptkit. A matching external
|
||||
profile can override a Promptkit built-in profile, and the configured local
|
||||
backend can support profiles that select `backend: local`. Endpoint-only
|
||||
OpenAI-compatible profiles can also provide their own endpoint.
|
||||
Weatherreporter accepted either `promptkit.profile_file` or
|
||||
`promptkit.profile_dir` and passed that source to Promptkit. A matching external
|
||||
profile could override a Promptkit built-in profile, and the configured local
|
||||
backend could support profiles that select `backend: local`. Endpoint-only
|
||||
OpenAI-compatible profiles could also provide their own endpoint.
|
||||
|
||||
Weatherreporter does not currently own or embed execution profiles. Promptkit
|
||||
v0.5.0 now provides the fallback-profile layer needed to add them without
|
||||
changing the existing operator-source precedence.
|
||||
Weatherreporter did not own or embed execution profiles. Promptkit v0.5.0
|
||||
provided the fallback-profile layer used to add them without changing the
|
||||
existing operator-source precedence.
|
||||
|
||||
## Prerequisite
|
||||
|
||||
@@ -56,7 +56,7 @@ passed the repository test suite and an operator smoke test. Weatherreporter
|
||||
must continue to use only Promptkit's public API rather than depending on its
|
||||
internal packages or reproducing its profile repository behavior.
|
||||
|
||||
## Desired End State
|
||||
## Implemented End State
|
||||
|
||||
Weatherreporter embeds usable definitions for these exact logical profile IDs:
|
||||
|
||||
@@ -204,7 +204,7 @@ The purpose is to choose an appropriate default for each tier, not to add a
|
||||
permanent benchmark framework or live-provider requirement to the ordinary
|
||||
test suite. Repository tests remain offline and deterministic.
|
||||
|
||||
## Scope
|
||||
## Implemented Scope
|
||||
|
||||
The completed feature includes:
|
||||
|
||||
@@ -260,9 +260,9 @@ An external same-ID override is an operator-owned compatibility commitment.
|
||||
Weatherreporter may evolve its embedded definitions, but it must not rewrite or
|
||||
silently merge an operator file.
|
||||
|
||||
## Completion Criteria
|
||||
## Completion Record
|
||||
|
||||
The roadmap is complete when:
|
||||
The following conditions are satisfied:
|
||||
|
||||
- a tagged Promptkit dependency supports the required fallback layer;
|
||||
- every operational prompt selects its assigned logical profile at exact
|
||||
|
||||
@@ -1,19 +1,14 @@
|
||||
# Domain-Specific Prompt Profiles Implementation Plan
|
||||
|
||||
Status: Ready for implementation.
|
||||
Status: Completed.
|
||||
|
||||
## Purpose And Authority
|
||||
|
||||
This document gives a coding agent the ordered work needed to implement the
|
||||
This document records the completed implementation of the
|
||||
[domain-specific prompt profiles roadmap](domain-profiles.md). The roadmap is
|
||||
authoritative for scope, user intent, policy choices, and the desired end
|
||||
state. This plan is authoritative for implementation sequence, verification,
|
||||
and stage exit gates.
|
||||
|
||||
The target implementer is a `gpt-5.6-terra` coding agent using high reasoning.
|
||||
Complete the stages in order. Each stage is scoped for one implementation
|
||||
prompt and must leave the repository coherent, tested, and reviewable before
|
||||
the next stage begins.
|
||||
authoritative for scope, user intent, policy choices, and the implemented end
|
||||
state. This plan records the implementation sequence, verification, and exit
|
||||
gates used to reach it.
|
||||
|
||||
This plan follows the repository's
|
||||
[architecture](../policy/architecture.md),
|
||||
|
||||
Reference in New Issue
Block a user