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

Resolve backend concurrency ownership and plan redundant code removal

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-08 01:48:50 +00:00
parent ac86c77cfe
commit d4d510a520
2 changed files with 47 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -58,6 +58,10 @@ They do not select unrelated work in [future.md](future.md).
dual formats, transition modes, or legacy-behavior tests merely to ease adoption.
Release guidance may require a hard cutover. Domain requirements still guide
the target, but existing implementations and contracts are open to redesign.
- **Remove redundant code:** reducing Audita's maintenance burden is an explicit
adoption goal. Retire local mechanisms, settings, wrappers, and tests superseded
by supported upstream behavior. Keep the domain logic and integration code that
Audita needs; retaining existing code is not a success criterion.
- Audita continues to own transcript formats, correction ordering, domain
validation, structured-response contracts, and truthful partial-success
behavior. Inspect each other restriction against a concrete domain need.
@@ -109,8 +113,10 @@ for Audita's complete release workflow.
concrete upstream requests early; do not postpone CommandKit design until the
runtime is done.
Reconcile planned changes with the current architecture policy, especially
application-only credential rules, finite admission, and preference for
standard-library CLI parsing. Update policies with adopted behavior; do not
application-only credential rules and preference for standard-library CLI
parsing. Backend concurrency ownership is resolved in the PromptKit outline:
adopt native behavior and retire Audita's duplicate policy. Update the finite-
admission requirement and other policies with adopted behavior; do not
silently treat old integration choices as permanent requirements.
Keep stage-specific glossary inputs in view when choosing configuration and
CLI contracts; detailed feature design and implementation follow adoption.
@@ -124,6 +130,8 @@ for Audita's complete release workflow.
identities and their exchanged types together, then implement native resource
formats, configuration semantics, runtime checks, and standard inspection
providers. Avoid a permanent replacement or dual configuration engine.
Identify and remove local code made redundant by the adopted facilities as
part of each migration, rather than leaving cleanup as an unspecified follow-up.
4. **Integrate CommandKit and both standard integrations.** Complete the
previously designed operator interface, adapting Audita domain handlers and
resolving upstream issues. This is required target scope, not an optional
@@ -201,6 +209,11 @@ preserving superseded behavior. Upstream requests need an explicit disposition
before calling the dependent behavior complete. Any temporary workaround must
name its reason and removal condition; it is not architecture by default.
Completion also includes retiring superseded local machinery and its obsolete
configuration, documentation, and tests. Preserve evidence for the selected
domain behavior and real integration boundaries without duplicating upstream
implementation tests. Code removal is a desired result, with no deletion quota.
Refresh [attribution](../oss/attribution.md) for the exact selected dependencies
and toolchain under [OSS policy](../policy/oss.md). The reviewed library grants
remain LGPL-3.0-or-later; remove old catalog entries when no longer incorporated