Release AKTA v0.5.0#2
Merged
Merged
Conversation
Packaging metadata must track the v0.5 policy manifest and contract surface.
Runtime version checks and adapters rely on the package string matching policy v0.5.
Manifest pins hashed policy artifacts for integrity verification at load time.
Automates manifest regeneration so release edits stay consistent with on-disk YAML.
Ontology labels must align with updated evidence-to-action routing.
Matrix gates tool actions against deployment profiles and evidence states.
Registry hashes feed PCS bundles and overlay-scoped admissibility.
Profiles distinguish dev HMAC convenience from production key requirements.
Evidence state vocabulary drives classifier and gate outcomes.
Matrix links evidence tiers to permitted action classes.
Rule refinements close gaps found in integrated demo scenarios.
Responsibility tiers constrain high-impact protocol changes.
Bridge table keeps AKTA decisions aligned with SCOPE grant vocabulary.
Validation labels appear in PCS artifacts and REST responses.
Verification states support weak-evidence and review-required paths.
Policy loader must honor manifest pins and version fields introduced in v0.5.
Developers verify locally without production keys while prod remains strict.
Operators need explicit guidance on AKTA_POLICY_HMAC_KEY usage.
Regression tests lock dev-key simulation and production failure modes.
Versioning tests prevent silent drift of pinned policy artifacts.
Existing policy suite must cover manifest hash expectations.
Shared protocol types keep client and contract tests aligned on v0.5 semantics.
Client supports simulated and real SCOPE paths used by demos and contracts.
Integrators need accurate request/grant mapping and mode selection guidance.
Contract tests guard against drift in subprocess SCOPE invocation.
Import mode must remain stable for offline CI and demos.
Schema captures new PCS artifact fields required by full-chain export.
Export bundles SCOPE and PF artifacts with tamper-evident hashes.
Benchmark exporter must emit manifests valid under updated schema.
Tamper tests prove hash linkage across bundled artifacts.
Bundled decision matches standalone example for PCS verification.
Bundled record completes weak-evidence PCS chain export.
Hash pin tracks v0.5 policy manifest digest.
Overlay hash reflects generic_lab overlay under new tiers.
Registry hash matches default_tool_registry v0.5 content.
Active protocol update path shows review_required under v0.5.
Draft follow-up decision demonstrates allowed draft_change scope.
Record captures SCOPE-facing fields for active update scenario.
Obligation documents tool_review requirement from integrated demo.
Review trigger encodes human review gate for protocol drift.
SCOPE review packet matches client simulation output for demo.
SCOPE decision artifact completes grant path in v0.5 PCS chain.
Manifest enumerates SCOPE and PF members in full-chain bundle.
Bundled decision mirrors active and draft demo outcomes.
Bundled record ties AKTA outputs to SCOPE artifacts in PCS.
Bundled review trigger supports tamper tests on PCS chain.
Review packet hash linkage is validated in PCS contract tests.
PF obligation is exported as first-class PCS artifact in v0.5.
SCOPE decision is included for full-chain integrity checks.
Grant artifact documents protocol_draft scope from SCOPE simulation.
Policy digest pin matches regenerated v0.5 manifest.
Overlay digest updated after overlay tier edits.
Tool registry digest aligns with PCS export expectations.
Guide covers PCS full-chain export and SCOPE adapter modes.
Security doc highlights classifier boundary and policy HMAC split.
Governance text reflects overlay review tiers introduced in v0.5.
README summarizes v0.5 integration, demos, and integrity modes.
Changelog captures user-visible changes for the v0.5 release.
Skill instructions reference v0.5 artifacts and trust-boundary docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan
pip install -e .[dev]andmake ci(run locally before push)mainafter review (do not merge until approved)Notes
87 logical commits on
release/v0.5fromrelease/v0.4tip. Eval report JSON underevals/reports/intentionally omitted.