From 1248c8dcf6252bad6b39e2ca1deeb8131d889486 Mon Sep 17 00:00:00 2001 From: PRAMOD B N Date: Tue, 11 Aug 2026 21:53:31 -0500 Subject: [PATCH 1/2] Refine roadmap for Semantica export support --- agenticlens-roadmap.md | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/agenticlens-roadmap.md b/agenticlens-roadmap.md index 598e434..24d6276 100644 --- a/agenticlens-roadmap.md +++ b/agenticlens-roadmap.md @@ -104,6 +104,14 @@ cross-project coordination before they should be marked complete. - `ai-operations-spec` Provides the normative artifact model and conformance rules for AIOS-aligned validation, schema references, and interoperability claims. +- `agentic-sidecar` + Coordinate with: both projects independently export to Semantica + (AgenticLens: trace/evidence; Sidecar: decision/governance) and must + agree on a shared correlation-ID contract linking a trace to the + decision(s) made against it before either export is considered + non-experimental. See the Provenance and Governance Export Guidance + section below and `agentic-sidecar`'s `ROADMAP.md` v0.6 deliverables for + the other half of this. - `agentic-chaos` Produces resilience/fault evidence that AgenticLens may analyze, summarize, or validate as part of cross-tool workflows. @@ -601,10 +609,35 @@ Planned targets include: - MCP-hosted agents - OpenInference - OpenTelemetry and OTLP +- Semantica, as a provenance- and audit-oriented export surface Integration packages must document coverage and any framework behavior that cannot be represented in the core schema. +### Provenance and Governance Export Guidance + +AgenticLens owns trace/evidence export — what ran, what it cost, why it +behaved that way. It does not own decision governance: `agentic-sidecar` +owns the decision/governance side of that same Semantica export (allow, +block, escalate, and why), so the two exports must agree on a shared +compatibility shape — a common ID/correlation convention linking a trace to +the decision(s) made against it — rather than each project inventing its +own. This is tracked as a real coordination item, not just prose intent: +see the `agentic-sidecar` entry under [Cross-Project +Dependencies](#cross-project-dependencies) near the top of this document, +and `agentic-sidecar`'s own `ROADMAP.md` (Cross-Project Dependencies and +v0.6 deliverables), where the correlation-ID contract is defined, +versioned, and tested before either project's Semantica export is +considered non-experimental. + +- do not turn AgenticLens into a knowledge-graph or policy-engine runtime +- do add provenance-aware evidence fields and lineage-friendly export shapes +- do consider optional PROV-O, RDF, or JSON-LD export targets once the trace + and evaluation schemas are stable enough, with Semantica as one such + target +- do keep any external audit or governance integration optional and + artifact-oriented rather than a runtime dependency + ## Success Measures ### Developer experience From 5cc4738558125cacdd9fccc0d3e923fc33891da7 Mon Sep 17 00:00:00 2001 From: PRAMOD B N Date: Tue, 11 Aug 2026 22:02:12 -0500 Subject: [PATCH 2/2] Pin hatchling for metadata compatibility --- pyproject.toml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index 65f14f4..f8a00c6 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,5 +1,8 @@ [build-system] -requires = ["hatchling"] +# Keep the isolated build backend on a metadata-2.4-compatible hatchling line. +# Newer hatchling releases can emit Core Metadata 2.5, which current CI's +# `twine check` rejects as an invalid distribution metadata version. +requires = ["hatchling<1.27"] build-backend = "hatchling.build" [project]