From 18225bc2334a8340d809001aaab547b2289d25b6 Mon Sep 17 00:00:00 2001 From: Pavan Dev Singh Charak Date: Wed, 4 Nov 2026 07:55:42 +0530 Subject: [PATCH 1/3] Update README.md --- integrations/parmana-server/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/integrations/parmana-server/README.md b/integrations/parmana-server/README.md index 7c1c49f9..51da8170 100644 --- a/integrations/parmana-server/README.md +++ b/integrations/parmana-server/README.md @@ -1,6 +1,7 @@ # Parmana -[Parmana](https://github.com/pavancharak/parmana) decides whether an agent's action may run under a versioned policy, + +[Parmana](https://github.com/pavancharak/parmana-core) decides whether an agent's action may run under a versioned policy, requires a signed human approval where the policy says so, and signs a record of every decision, refusals included. This integration treats those records as TRACE external evidence. Parmana issues no TRACE Trust Record. An agent @@ -15,8 +16,7 @@ One Parmana record per decision. Each entry's `digest` is `sha256:` over the RFC object as the resolver retains it. The `approval-outcome` entry points at the signed approval inside the Trust Record (`#/transaction/signals/approvalArtifact`), because Parmana retains it there, under the Trust Record's own signature. -Parmana signs in its own canonical form, not RFC 8785, and TRACE does not re-sign its records: `parmana_evidence.py` -checks those signatures offline, with Parmana's public key and nothing else. +Parmana's canonical form is JSON with recursively sorted keys. For plain JSON values it matches RFC 8785, and `parmana-core` pins this with conformance tests. Two non-JSON inputs differ: `undefined` values are dropped and `Date` values become ISO strings. TRACE does not re-sign its records: `parmana_evidence.py` checks those signatures offline, with Parmana's public key and nothing else. ## Fixtures From 7b6a96651c26f610a1ade341cf18a48f8740b9ba Mon Sep 17 00:00:00 2001 From: Pavan Dev Singh Charak Date: Wed, 4 Nov 2026 07:59:13 +0530 Subject: [PATCH 2/3] Update README.md docs(parmana-server): fix Parmana link and correct RFC 8785 wording --- integrations/parmana-server/README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/integrations/parmana-server/README.md b/integrations/parmana-server/README.md index 51da8170..e0e02696 100644 --- a/integrations/parmana-server/README.md +++ b/integrations/parmana-server/README.md @@ -1,6 +1,5 @@ # Parmana - [Parmana](https://github.com/pavancharak/parmana-core) decides whether an agent's action may run under a versioned policy, requires a signed human approval where the policy says so, and signs a record of every decision, refusals included. From c7626d676e9d281900f0233e43ed2aa46516c46a Mon Sep 17 00:00:00 2001 From: Pavan Dev Singh Charak Date: Wed, 4 Nov 2026 08:46:52 +0530 Subject: [PATCH 3/3] Update README.md --- integrations/parmana-server/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integrations/parmana-server/README.md b/integrations/parmana-server/README.md index e0e02696..8dd1017b 100644 --- a/integrations/parmana-server/README.md +++ b/integrations/parmana-server/README.md @@ -4,7 +4,7 @@ requires a signed human approval where the policy says so, and signs a record of every decision, refusals included. This integration treats those records as TRACE external evidence. Parmana issues no TRACE Trust Record. An agent -runtime that does points at the Parmana record for its step through `references` (trace-spec §3.1.2): +runtime that points at the Parmana record for its step through `references` (trace-spec §3.1.2): | Parmana decision | Parmana record | `references` entries | | ---------------- | -------------------------- | ---------------------------------------------------------------------- |