eric/audita
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

Prototype ConfigKit and PromptKit adoption and record the findings

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-23 18:48:18 +00:00
parent f70bb27636
commit 228087dec8
25 changed files with 1688 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/roadmap/library-adoption.md
View File

@@ -2,7 +2,8 @@
**Last updated:** 2026-09-23
**Status:** Agreed high-level direction; provisional roadmap. Detailed design,
**Status:** Shared boundary and offline prototype completed; production migrations
remain planned. See the [findings](library-boundary-findings.md). Detailed design,
implementation tasks, dependency versions, and acceptance criteria must be revisited
before migration begins. This document authorizes neither implementation nor release
publication and sets no schedule.
@@ -42,8 +43,9 @@ changes, especially changes to module or pipeline configuration.
## Proposed Sequence
The [shared-boundary and prototype roadmap](library-boundary.md) details the next
unit of work, covering stages 1 and 2 below before production migration.
The [shared-boundary and prototype roadmap](library-boundary.md) records the completed
unit covering stages 1 and 2 below. The [findings](library-boundary-findings.md)
select its target contract and identify the next ConfigKit implementation work.
### 1. Design the Shared Configuration Boundary
@@ -159,12 +161,11 @@ than quietly recreate shared library functionality as permanent Audita infrastru
## Coordination and Open Decisions
- Finalize the configuration/profile boundary, defaults, credential ownership, and
retry/repair budgets and deadline policy before committing to the new file schema
and CLI design. Structural repair is enabled by the agreed direction; its positive
default count remains to be selected.
- Define how exhausted repair, failed validation, exhausted retries, and partial
execution observations map to Audita warnings, rejected work, and failed runs.
- Use the selected configuration/profile boundary, defaults, credential flow, and
retry/repair/deadline contract in the [findings](library-boundary-findings.md)
when detailing the ConfigKit production migration.
- Implement the outcome and observation mapping recorded in the findings, retaining
Audita domain validation and diagnostic redaction.
- Resolve the [runtime retry-count follow-up](runtime-behavior.md) through this migration.
Retention and transcript timestamp questions are not automatically included.
- Revisit ordering when other major changes are defined. Prefer designing shared