From d158585216e94c4953f8d1b9ec5775cfec2a57a2 Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Fri, 15 May 2026 10:17:57 +0100 Subject: [PATCH 01/11] Add agience-flare-dkg-integration --- .../agience-flare-dkg-integration.json | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 integrations/agience-flare-dkg-integration.json diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json new file mode 100644 index 0000000..d238975 --- /dev/null +++ b/integrations/agience-flare-dkg-integration.json @@ -0,0 +1,42 @@ +{ + "$schema": "../schema/integration.schema.json", + "schemaVersion": "0.1.0", + "slug": "agience-flare-dkg-integration", + "name": "Agience FLARE × DKG v10 Integration", + "description": "Governance layer above DKG v10. Projects only commit-gated Agience artifacts into Working Memory and Shared Memory as typed agience: RDF Knowledge Assets, with policy-controlled SHARE, optional FLARE confidential retrieval, and provenance receipts. Complementary to dkg mcp setup.", + "category": ["agent-memory", "governance", "research-workflow", "mcp", "working-memory", "shared-memory"], + "maintainer": { + "github": "@Muffinman75", + "name": "Manoj Modhwadia", + "contact": "manojmodhwadia@outlook.com" + }, + "repo": "https://github.com/Muffinman75/agience-flare-dkg-integration", + "commit": "09bf331ae13b9ba1ddbec07957e49e0bce358a92", + "license": "MIT", + "requiresDkgNodeVersion": ">=10.0.0-rc.1", + "memoryLayers": ["WM", "SWM"], + "v10PrimitivesUsed": ["UAL", "KnowledgeAsset", "ContextGraph", "Curator"], + "publicInterfacesUsed": ["mcp"], + "targetAgents": ["generic-MCP", "generic-CLI", "generic-HTTP"], + "install": { + "kind": "manual", + "docsUrl": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/README.md", + "oneLiner": "Python package on PyPI: `pip install agience-flare-dkg-integration==0.3.0`. Provides a CLI (`agience-dkg wm-write`, `promote`, `search`) and a `DkgHttpClient` library that drive the local DKG node's MCP Streamable HTTP transport (POST /mcp). Configure DKG_BASE_URL, DKG_TOKEN, DKG_CONTEXT_GRAPH; for governed-mode also set AGIENCE_BASE_URL and AGIENCE_TOKEN." + }, + "security": { + "networkEgress": [], + "writeAuthority": [ + "POST /mcp -> tools/call dkg-create (privacy=private) — Working Memory write", + "POST /mcp -> tools/call dkg-create (privacy=public) — Shared Memory promotion (SHARE, Curator-authority)", + "POST /mcp -> tools/call dkg-sparql-query — read-only memory search", + "GET /health" + ], + "credentialsHandled": ["AGIENCE_TOKEN"], + "notes": "Distribution: published to PyPI (not npm) at https://pypi.org/project/agience-flare-dkg-integration/0.3.0/ via GitHub Actions with build provenance (pypa/gh-action-pypi-publish, attestations: true). The npm-registry lookup in CI will warn 'package not yet published' — expected, this is a Python package. Registered MIT in package metadata. No postinstall/preinstall hooks (Python packaging does not use those). Egress: only the local DKG node (DKG_BASE_URL, default http://localhost:8081) and, if governed-mode is enabled, an Agience platform endpoint (AGIENCE_BASE_URL) the operator explicitly configures; FLARE service endpoint is opt-in and disabled by default. Curator-authority surface: SHARE (privacy=public dkg-create) is invoked only when an operator explicitly runs the `promote` CLI command or calls DkgHttpClient.promote_to_swm; PUBLISH/VM is out of scope for Round 1 and not invoked. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for downstream auditability. No dynamic code loading; no eval on remote input. pip-audit --production is clean. 60 unit tests + 5 integration tests in this repo; 6 DKG service tests in the parent Agience Core repo; 101 tests in the FLARE Index repo (172 total). Maintainer commits to a 6-month support window from acceptance — see docs/maintainer-statement.md." + }, + "trustTier": "community", + "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", + "demo": "https://youtu.be/0Zm8R3vQzgU", + "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. The integration deliberately stops at SWM in Round 1 and does not call PUBLISH/endorse/verify.", + "fitNotes": "Round-1 fit: a platform-level governance layer that turns committed artifacts from any upstream tool (chat clients, IDEs, research notebooks) into provenance-bearing Working/Shared Memory entries — the substrate Karpathy's LLM-Wiki / autoresearch direction depends on. Complementary to single-tool plugins (ChatGPT, Slack, GitHub, Obsidian) and to the first-party `cursor-mcp-dkg`: those clients can author into a governed Agience workspace; this integration governs which artifacts reach DKG WM/SWM, with what typing, and under whose authority. Engineered for forward-compatibility with Round 2 (Verified Memory, oracles): typed agience: predicates and stable UALs make PUBLISH a one-line extension, and FLARE provides the cryptographic retrieval boundary needed for confidential oracle inputs." +} From a87c57df9f3eb5dbfec809da2599f34274f7bd08 Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Wed, 20 May 2026 08:56:07 +0100 Subject: [PATCH 02/11] Bump pinned SHA to 9f4a095 (typed-artifact substrate doc + screenshots) --- integrations/agience-flare-dkg-integration.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index d238975..b009fdc 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -11,7 +11,7 @@ "contact": "manojmodhwadia@outlook.com" }, "repo": "https://github.com/Muffinman75/agience-flare-dkg-integration", - "commit": "09bf331ae13b9ba1ddbec07957e49e0bce358a92", + "commit": "9f4a095b94bfdf1a9e7d1b46ed0cc0e8a1c8165f", "license": "MIT", "requiresDkgNodeVersion": ">=10.0.0-rc.1", "memoryLayers": ["WM", "SWM"], From a495cb38871f33bd2af3c4e24905d99a81476652 Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Wed, 20 May 2026 10:09:18 +0100 Subject: [PATCH 03/11] Switch install.kind to cli with npm pin (0.3.1, dual PyPI+npm publish with provenance) --- integrations/agience-flare-dkg-integration.json | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index b009fdc..bc469f0 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -11,7 +11,7 @@ "contact": "manojmodhwadia@outlook.com" }, "repo": "https://github.com/Muffinman75/agience-flare-dkg-integration", - "commit": "9f4a095b94bfdf1a9e7d1b46ed0cc0e8a1c8165f", + "commit": "a278898d462622d16ad81c17dd87b800f25cecdc", "license": "MIT", "requiresDkgNodeVersion": ">=10.0.0-rc.1", "memoryLayers": ["WM", "SWM"], @@ -19,9 +19,12 @@ "publicInterfacesUsed": ["mcp"], "targetAgents": ["generic-MCP", "generic-CLI", "generic-HTTP"], "install": { - "kind": "manual", - "docsUrl": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/README.md", - "oneLiner": "Python package on PyPI: `pip install agience-flare-dkg-integration==0.3.0`. Provides a CLI (`agience-dkg wm-write`, `promote`, `search`) and a `DkgHttpClient` library that drive the local DKG node's MCP Streamable HTTP transport (POST /mcp). Configure DKG_BASE_URL, DKG_TOKEN, DKG_CONTEXT_GRAPH; for governed-mode also set AGIENCE_BASE_URL and AGIENCE_TOKEN." + "kind": "cli", + "package": "agience-flare-dkg-integration", + "version": "0.3.1", + "binary": "agience-dkg", + "envRequired": ["DKG_BASE_URL", "DKG_TOKEN"], + "usageHint": "The npm package is a thin Node wrapper around the Python CLI on PyPI. Install both: `npm i -g agience-flare-dkg-integration && pipx install agience-flare-dkg-integration==0.3.1`. Run `agience-dkg wm-write|promote|search`. Required env: DKG_BASE_URL, DKG_TOKEN, DKG_CONTEXT_GRAPH. Governed-mode also reads AGIENCE_BASE_URL and AGIENCE_TOKEN." }, "security": { "networkEgress": [], @@ -32,7 +35,7 @@ "GET /health" ], "credentialsHandled": ["AGIENCE_TOKEN"], - "notes": "Distribution: published to PyPI (not npm) at https://pypi.org/project/agience-flare-dkg-integration/0.3.0/ via GitHub Actions with build provenance (pypa/gh-action-pypi-publish, attestations: true). The npm-registry lookup in CI will warn 'package not yet published' — expected, this is a Python package. Registered MIT in package metadata. No postinstall/preinstall hooks (Python packaging does not use those). Egress: only the local DKG node (DKG_BASE_URL, default http://localhost:8081) and, if governed-mode is enabled, an Agience platform endpoint (AGIENCE_BASE_URL) the operator explicitly configures; FLARE service endpoint is opt-in and disabled by default. Curator-authority surface: SHARE (privacy=public dkg-create) is invoked only when an operator explicitly runs the `promote` CLI command or calls DkgHttpClient.promote_to_swm; PUBLISH/VM is out of scope for Round 1 and not invoked. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for downstream auditability. No dynamic code loading; no eval on remote input. pip-audit --production is clean. 60 unit tests + 5 integration tests in this repo; 6 DKG service tests in the parent Agience Core repo; 101 tests in the FLARE Index repo (172 total). Maintainer commits to a 6-month support window from acceptance — see docs/maintainer-statement.md." + "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.3.1/), both via GitHub Actions tag-triggered workflows. The npm package (3.8 kB tarball, 5 files, zero runtime dependencies) is a thin wrapper that delegates to the Python CLI shipped on PyPI; all integration logic lives in the Python package. npm publish uses `--provenance --access public` against id-token: write, producing a SLSA v1 attestation signed by the GitHub Actions runner and recorded in the public sigstore transparency log. PyPI publish uses pypa/gh-action-pypi-publish with attestations: true. No `preinstall`, `install`, or `postinstall` scripts in either package — Section 8a compliant. No dynamic code loading, no eval on remote input. Egress: only the local DKG node (DKG_BASE_URL, default http://localhost:8081) and, if governed-mode is enabled, an Agience platform endpoint (AGIENCE_BASE_URL) the operator explicitly configures; FLARE service endpoint is opt-in and disabled by default. Curator-authority surface: SHARE (privacy=public dkg-create) is invoked only when an operator explicitly runs the `promote` CLI command or calls DkgHttpClient.promote_to_swm; PUBLISH/VM is out of scope for Round 1 and not invoked. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for downstream auditability. pip-audit --production is clean. 60 unit tests + 5 integration tests in this repo; 6 DKG service tests in the parent Agience Core repo; 101 tests in the FLARE Index repo (172 total). Maintainer commits to a 6-month support window from acceptance — see docs/maintainer-statement.md." }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", From c18d24eea4d97e6d80b4d7f2a89c07f680bd3a14 Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Sun, 24 May 2026 11:07:51 +0100 Subject: [PATCH 04/11] Bump agience-flare-dkg-integration to v0.4.0 (daemon transport default) --- .../agience-flare-dkg-integration.json | 24 +++++++++++-------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index bc469f0..f474f11 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -11,31 +11,35 @@ "contact": "manojmodhwadia@outlook.com" }, "repo": "https://github.com/Muffinman75/agience-flare-dkg-integration", - "commit": "a278898d462622d16ad81c17dd87b800f25cecdc", + "commit": "6e3a7676fa4ef76bccf9ae47e6b3974a71c036f8", "license": "MIT", "requiresDkgNodeVersion": ">=10.0.0-rc.1", "memoryLayers": ["WM", "SWM"], "v10PrimitivesUsed": ["UAL", "KnowledgeAsset", "ContextGraph", "Curator"], - "publicInterfacesUsed": ["mcp"], + "publicInterfacesUsed": ["http-api", "mcp"], "targetAgents": ["generic-MCP", "generic-CLI", "generic-HTTP"], "install": { "kind": "cli", "package": "agience-flare-dkg-integration", - "version": "0.3.1", + "version": "0.4.0", "binary": "agience-dkg", - "envRequired": ["DKG_BASE_URL", "DKG_TOKEN"], - "usageHint": "The npm package is a thin Node wrapper around the Python CLI on PyPI. Install both: `npm i -g agience-flare-dkg-integration && pipx install agience-flare-dkg-integration==0.3.1`. Run `agience-dkg wm-write|promote|search`. Required env: DKG_BASE_URL, DKG_TOKEN, DKG_CONTEXT_GRAPH. Governed-mode also reads AGIENCE_BASE_URL and AGIENCE_TOKEN." + "envRequired": ["DKG_BASE_URL"], + "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.0`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN). Governed-mode (`--from-agience-artifact`) also reads AGIENCE_BASE_URL and AGIENCE_TOKEN. npm wrapper published as alternative." }, "security": { "networkEgress": [], "writeAuthority": [ - "POST /mcp -> tools/call dkg-create (privacy=private) — Working Memory write", - "POST /mcp -> tools/call dkg-create (privacy=public) — Shared Memory promotion (SHARE, Curator-authority)", - "POST /mcp -> tools/call dkg-sparql-query — read-only memory search", - "GET /health" + "daemon transport (default) — POST /api/assertion/create + POST /api/assertion/{name}/write — Working Memory assertion creation and quad append", + "daemon transport — POST /api/shared-memory/write — direct Shared Memory write (layer=swm)", + "daemon transport — POST /api/assertion/{name}/promote — Shared Memory promotion (SHARE, Curator-authority)", + "daemon transport — POST /api/query — read-only SPARQL SELECT for memory search", + "daemon transport — GET /api/status — health probe", + "MCP transport (alternative) — POST /mcp -> tools/call dkg-create (privacy=private) — Working Memory write", + "MCP transport — POST /mcp -> tools/call dkg-create (privacy=public) — Shared Memory promotion (SHARE, Curator-authority)", + "MCP transport — POST /mcp -> tools/call dkg-sparql-query — read-only memory search" ], "credentialsHandled": ["AGIENCE_TOKEN"], - "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.3.1/), both via GitHub Actions tag-triggered workflows. The npm package (3.8 kB tarball, 5 files, zero runtime dependencies) is a thin wrapper that delegates to the Python CLI shipped on PyPI; all integration logic lives in the Python package. npm publish uses `--provenance --access public` against id-token: write, producing a SLSA v1 attestation signed by the GitHub Actions runner and recorded in the public sigstore transparency log. PyPI publish uses pypa/gh-action-pypi-publish with attestations: true. No `preinstall`, `install`, or `postinstall` scripts in either package — Section 8a compliant. No dynamic code loading, no eval on remote input. Egress: only the local DKG node (DKG_BASE_URL, default http://localhost:8081) and, if governed-mode is enabled, an Agience platform endpoint (AGIENCE_BASE_URL) the operator explicitly configures; FLARE service endpoint is opt-in and disabled by default. Curator-authority surface: SHARE (privacy=public dkg-create) is invoked only when an operator explicitly runs the `promote` CLI command or calls DkgHttpClient.promote_to_swm; PUBLISH/VM is out of scope for Round 1 and not invoked. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for downstream auditability. pip-audit --production is clean. 60 unit tests + 5 integration tests in this repo; 6 DKG service tests in the parent Agience Core repo; 101 tests in the FLARE Index repo (172 total). Maintainer commits to a 6-month support window from acceptance — see docs/maintainer-statement.md." + "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.0/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `promote` CLI command or the equivalent Python API; PUBLISH/VM is out of scope for Round 1 and not invoked. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. 75 unit + 5 integration tests in this repo (governance-flow tests transport-agnostic); 6 DKG service tests in Agience Core; 101 in FLARE Index (187 total). 6-month maintenance commitment — see docs/maintainer-statement.md." }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", From 1d49fcd99396fb443d4c821fc01c886d3efb29cb Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Mon, 25 May 2026 17:16:09 +0100 Subject: [PATCH 05/11] Refresh demo URL to v0.4.0 recording (daemon transport default) --- integrations/agience-flare-dkg-integration.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index f474f11..fdf6cf4 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -43,7 +43,7 @@ }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", - "demo": "https://youtu.be/0Zm8R3vQzgU", + "demo": "https://youtu.be/GToqbekFdPc", "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. The integration deliberately stops at SWM in Round 1 and does not call PUBLISH/endorse/verify.", "fitNotes": "Round-1 fit: a platform-level governance layer that turns committed artifacts from any upstream tool (chat clients, IDEs, research notebooks) into provenance-bearing Working/Shared Memory entries — the substrate Karpathy's LLM-Wiki / autoresearch direction depends on. Complementary to single-tool plugins (ChatGPT, Slack, GitHub, Obsidian) and to the first-party `cursor-mcp-dkg`: those clients can author into a governed Agience workspace; this integration governs which artifacts reach DKG WM/SWM, with what typing, and under whose authority. Engineered for forward-compatibility with Round 2 (Verified Memory, oracles): typed agience: predicates and stable UALs make PUBLISH a one-line extension, and FLARE provides the cryptographic retrieval boundary needed for confidential oracle inputs." } From 7057378fd903f342ce575b20dd4221d33cea9cf4 Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Thu, 18 Jun 2026 09:09:52 +0100 Subject: [PATCH 06/11] registry: v0.4.1 - Verifiable Memory layer, hosted SaaS egress, rc.17 write authority --- .../agience-flare-dkg-integration.json | 20 +++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index fdf6cf4..11a57cf 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -14,24 +14,28 @@ "commit": "6e3a7676fa4ef76bccf9ae47e6b3974a71c036f8", "license": "MIT", "requiresDkgNodeVersion": ">=10.0.0-rc.1", - "memoryLayers": ["WM", "SWM"], + "memoryLayers": ["WM", "SWM", "VM"], "v10PrimitivesUsed": ["UAL", "KnowledgeAsset", "ContextGraph", "Curator"], "publicInterfacesUsed": ["http-api", "mcp"], "targetAgents": ["generic-MCP", "generic-CLI", "generic-HTTP"], "install": { "kind": "cli", "package": "agience-flare-dkg-integration", - "version": "0.4.0", + "version": "0.4.1", "binary": "agience-dkg", "envRequired": ["DKG_BASE_URL"], - "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.0`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN). Governed-mode (`--from-agience-artifact`) also reads AGIENCE_BASE_URL and AGIENCE_TOKEN. npm wrapper published as alternative." + "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.1`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN). Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." }, "security": { - "networkEgress": [], + "networkEgress": [ + "my.agience.ai — governed mode only (--from-agience-artifact); operator-configurable via AGIENCE_BASE_URL; optional", + "operator-configured FLARE service host — protected-search mode only; opt-in, disabled by default" + ], "writeAuthority": [ - "daemon transport (default) — POST /api/assertion/create + POST /api/assertion/{name}/write — Working Memory assertion creation and quad append", + "daemon (rc.17) — POST /api/knowledge-assets (+ /{name}/wm/write) — WM KA create + quad append (finalize:false); legacy fallback /api/assertion/create on 404", "daemon transport — POST /api/shared-memory/write — direct Shared Memory write (layer=swm)", - "daemon transport — POST /api/assertion/{name}/promote — Shared Memory promotion (SHARE, Curator-authority)", + "daemon (rc.17) — POST /api/knowledge-assets/{name}/swm/share — Shared Memory promotion (SHARE, Curator-authority); legacy fallback /api/assertion/{name}/promote on 404", + "daemon (rc.17) — POST /api/knowledge-assets/{name}/vm/publish — Verifiable Memory publish (PUBLISH, Curator-authority, on-chain); operator-initiated via vm-publish only", "daemon transport — POST /api/query — read-only SPARQL SELECT for memory search", "daemon transport — GET /api/status — health probe", "MCP transport (alternative) — POST /mcp -> tools/call dkg-create (privacy=private) — Working Memory write", @@ -39,11 +43,11 @@ "MCP transport — POST /mcp -> tools/call dkg-sparql-query — read-only memory search" ], "credentialsHandled": ["AGIENCE_TOKEN"], - "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.0/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `promote` CLI command or the equivalent Python API; PUBLISH/VM is out of scope for Round 1 and not invoked. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. 75 unit + 5 integration tests in this repo (governance-flow tests transport-agnostic); 6 DKG service tests in Agience Core; 101 in FLARE Index (187 total). 6-month maintenance commitment — see docs/maintainer-statement.md." + "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.1/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `promote` CLI command or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", "demo": "https://youtu.be/GToqbekFdPc", - "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. The integration deliberately stops at SWM in Round 1 and does not call PUBLISH/endorse/verify.", + "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. VM is reachable today via the operator-initiated `vm-publish` command (rc.17 `POST /api/knowledge-assets/{name}/vm/publish`); PUBLISH is always explicit, never automatic, and the integration never calls endorse/verify.", "fitNotes": "Round-1 fit: a platform-level governance layer that turns committed artifacts from any upstream tool (chat clients, IDEs, research notebooks) into provenance-bearing Working/Shared Memory entries — the substrate Karpathy's LLM-Wiki / autoresearch direction depends on. Complementary to single-tool plugins (ChatGPT, Slack, GitHub, Obsidian) and to the first-party `cursor-mcp-dkg`: those clients can author into a governed Agience workspace; this integration governs which artifacts reach DKG WM/SWM, with what typing, and under whose authority. Engineered for forward-compatibility with Round 2 (Verified Memory, oracles): typed agience: predicates and stable UALs make PUBLISH a one-line extension, and FLARE provides the cryptographic retrieval boundary needed for confidential oracle inputs." } From ddeb9ea230ca7397e9bccadca3bf248a1353e49b Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Sun, 28 Jun 2026 12:54:45 +0100 Subject: [PATCH 07/11] registry: bump agience-flare-dkg-integration to v0.4.2, DKG v10.0.1, new demo URL --- .../agience-flare-dkg-integration.json | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index 11a57cf..6790806 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -11,9 +11,9 @@ "contact": "manojmodhwadia@outlook.com" }, "repo": "https://github.com/Muffinman75/agience-flare-dkg-integration", - "commit": "6e3a7676fa4ef76bccf9ae47e6b3974a71c036f8", + "commit": "482d081cae60bfe2b2e8fcc4896a1484c1ca1647", "license": "MIT", - "requiresDkgNodeVersion": ">=10.0.0-rc.1", + "requiresDkgNodeVersion": ">=10.0.1", "memoryLayers": ["WM", "SWM", "VM"], "v10PrimitivesUsed": ["UAL", "KnowledgeAsset", "ContextGraph", "Curator"], "publicInterfacesUsed": ["http-api", "mcp"], @@ -21,10 +21,10 @@ "install": { "kind": "cli", "package": "agience-flare-dkg-integration", - "version": "0.4.1", + "version": "0.4.2", "binary": "agience-dkg", "envRequired": ["DKG_BASE_URL"], - "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.1`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN). Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." + "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.2`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN). Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." }, "security": { "networkEgress": [ @@ -32,10 +32,10 @@ "operator-configured FLARE service host — protected-search mode only; opt-in, disabled by default" ], "writeAuthority": [ - "daemon (rc.17) — POST /api/knowledge-assets (+ /{name}/wm/write) — WM KA create + quad append (finalize:false); legacy fallback /api/assertion/create on 404", + "daemon (v10.0.1) — POST /api/knowledge-assets (+ /{name}/wm/write) — WM KA create + quad append (finalize:false); legacy fallback /api/assertion/create on 404", "daemon transport — POST /api/shared-memory/write — direct Shared Memory write (layer=swm)", - "daemon (rc.17) — POST /api/knowledge-assets/{name}/swm/share — Shared Memory promotion (SHARE, Curator-authority); legacy fallback /api/assertion/{name}/promote on 404", - "daemon (rc.17) — POST /api/knowledge-assets/{name}/vm/publish — Verifiable Memory publish (PUBLISH, Curator-authority, on-chain); operator-initiated via vm-publish only", + "daemon (v10.0.1) — POST /api/knowledge-assets/{name}/swm/share — Shared Memory promotion (SHARE, Curator-authority); legacy fallback /api/assertion/{name}/promote on 404", + "daemon (v10.0.1) — POST /api/knowledge-assets/{name}/vm/publish — Verifiable Memory publish (PUBLISH, Curator-authority, on-chain); operator-initiated via vm-publish only", "daemon transport — POST /api/query — read-only SPARQL SELECT for memory search", "daemon transport — GET /api/status — health probe", "MCP transport (alternative) — POST /mcp -> tools/call dkg-create (privacy=private) — Working Memory write", @@ -43,11 +43,11 @@ "MCP transport — POST /mcp -> tools/call dkg-sparql-query — read-only memory search" ], "credentialsHandled": ["AGIENCE_TOKEN"], - "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.1/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `promote` CLI command or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." + "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.2/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `promote` CLI command or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", - "demo": "https://youtu.be/GToqbekFdPc", - "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. VM is reachable today via the operator-initiated `vm-publish` command (rc.17 `POST /api/knowledge-assets/{name}/vm/publish`); PUBLISH is always explicit, never automatic, and the integration never calls endorse/verify.", + "demo": "https://youtu.be/IvDyedXPqwU", + "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. VM is reachable today via the operator-initiated `vm-publish` command (v10.0.1 `POST /api/knowledge-assets/{name}/vm/publish`); PUBLISH is always explicit, never automatic, and the integration never calls endorse/verify.", "fitNotes": "Round-1 fit: a platform-level governance layer that turns committed artifacts from any upstream tool (chat clients, IDEs, research notebooks) into provenance-bearing Working/Shared Memory entries — the substrate Karpathy's LLM-Wiki / autoresearch direction depends on. Complementary to single-tool plugins (ChatGPT, Slack, GitHub, Obsidian) and to the first-party `cursor-mcp-dkg`: those clients can author into a governed Agience workspace; this integration governs which artifacts reach DKG WM/SWM, with what typing, and under whose authority. Engineered for forward-compatibility with Round 2 (Verified Memory, oracles): typed agience: predicates and stable UALs make PUBLISH a one-line extension, and FLARE provides the cryptographic retrieval boundary needed for confidential oracle inputs." } From 0c7b486287f7785e86882cb7f2793212708a671f Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Sun, 28 Jun 2026 18:31:46 +0100 Subject: [PATCH 08/11] registry: bump agience-flare-dkg-integration to v0.4.3, new demo URL, pinned commit --- integrations/agience-flare-dkg-integration.json | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index 6790806..7aeba79 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -11,7 +11,7 @@ "contact": "manojmodhwadia@outlook.com" }, "repo": "https://github.com/Muffinman75/agience-flare-dkg-integration", - "commit": "482d081cae60bfe2b2e8fcc4896a1484c1ca1647", + "commit": "f63641905ac135b3caf39d0e76ab97d06f0e431a", "license": "MIT", "requiresDkgNodeVersion": ">=10.0.1", "memoryLayers": ["WM", "SWM", "VM"], @@ -21,10 +21,10 @@ "install": { "kind": "cli", "package": "agience-flare-dkg-integration", - "version": "0.4.2", + "version": "0.4.3", "binary": "agience-dkg", "envRequired": ["DKG_BASE_URL"], - "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.2`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN). Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." + "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.3`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN). Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." }, "security": { "networkEgress": [ @@ -43,11 +43,11 @@ "MCP transport — POST /mcp -> tools/call dkg-sparql-query — read-only memory search" ], "credentialsHandled": ["AGIENCE_TOKEN"], - "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.2/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `promote` CLI command or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." + "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.3/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `promote` CLI command or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", - "demo": "https://youtu.be/IvDyedXPqwU", + "demo": "https://youtu.be/g3OtdM0DKtE", "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. VM is reachable today via the operator-initiated `vm-publish` command (v10.0.1 `POST /api/knowledge-assets/{name}/vm/publish`); PUBLISH is always explicit, never automatic, and the integration never calls endorse/verify.", "fitNotes": "Round-1 fit: a platform-level governance layer that turns committed artifacts from any upstream tool (chat clients, IDEs, research notebooks) into provenance-bearing Working/Shared Memory entries — the substrate Karpathy's LLM-Wiki / autoresearch direction depends on. Complementary to single-tool plugins (ChatGPT, Slack, GitHub, Obsidian) and to the first-party `cursor-mcp-dkg`: those clients can author into a governed Agience workspace; this integration governs which artifacts reach DKG WM/SWM, with what typing, and under whose authority. Engineered for forward-compatibility with Round 2 (Verified Memory, oracles): typed agience: predicates and stable UALs make PUBLISH a one-line extension, and FLARE provides the cryptographic retrieval boundary needed for confidential oracle inputs." } From 70e0abeec593b7cf888c81bb147df670c4b8b4ca Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Sun, 28 Jun 2026 20:15:28 +0100 Subject: [PATCH 09/11] Update agience-flare-dkg-integration to v0.4.4 (08a0081) --- integrations/agience-flare-dkg-integration.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index 7aeba79..276071a 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -11,7 +11,7 @@ "contact": "manojmodhwadia@outlook.com" }, "repo": "https://github.com/Muffinman75/agience-flare-dkg-integration", - "commit": "f63641905ac135b3caf39d0e76ab97d06f0e431a", + "commit": "08a00810092dc5fd2d5b32b289ee139d72fc9d13", "license": "MIT", "requiresDkgNodeVersion": ">=10.0.1", "memoryLayers": ["WM", "SWM", "VM"], @@ -21,10 +21,10 @@ "install": { "kind": "cli", "package": "agience-flare-dkg-integration", - "version": "0.4.3", + "version": "0.4.4", "binary": "agience-dkg", "envRequired": ["DKG_BASE_URL"], - "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.3`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN). Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." + "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.4`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN); default port 8083 matches the reference `dkg-node/apps/agent` setup, use 8081 for the DKG Edge Node Agent Web UI/API. CLI: `agience-dkg share` (v10.0.1 SHARE), `promote` is a backward-compatible alias. Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." }, "security": { "networkEgress": [ @@ -34,16 +34,16 @@ "writeAuthority": [ "daemon (v10.0.1) — POST /api/knowledge-assets (+ /{name}/wm/write) — WM KA create + quad append (finalize:false); legacy fallback /api/assertion/create on 404", "daemon transport — POST /api/shared-memory/write — direct Shared Memory write (layer=swm)", - "daemon (v10.0.1) — POST /api/knowledge-assets/{name}/swm/share — Shared Memory promotion (SHARE, Curator-authority); legacy fallback /api/assertion/{name}/promote on 404", + "daemon (v10.0.1) — POST /api/knowledge-assets/{name}/swm/share — Shared Memory SHARE (historically called promote); legacy fallback /api/assertion/{name}/promote on 404", "daemon (v10.0.1) — POST /api/knowledge-assets/{name}/vm/publish — Verifiable Memory publish (PUBLISH, Curator-authority, on-chain); operator-initiated via vm-publish only", "daemon transport — POST /api/query — read-only SPARQL SELECT for memory search", "daemon transport — GET /api/status — health probe", "MCP transport (alternative) — POST /mcp -> tools/call dkg-create (privacy=private) — Working Memory write", - "MCP transport — POST /mcp -> tools/call dkg-create (privacy=public) — Shared Memory promotion (SHARE, Curator-authority)", + "MCP transport — POST /mcp -> tools/call dkg-create (privacy=public) — Shared Memory SHARE (Curator-authority)", "MCP transport — POST /mcp -> tools/call dkg-sparql-query — read-only memory search" ], "credentialsHandled": ["AGIENCE_TOKEN"], - "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.3/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `promote` CLI command or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." + "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.4/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `share` CLI command (or the backward-compatible `promote` alias) or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", From ce79ba49a80f355aa1377b6cd1fadcdde5e08b0d Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Mon, 29 Jun 2026 11:05:24 +0100 Subject: [PATCH 10/11] update agience-flare-dkg-integration to v0.4.5 --- integrations/agience-flare-dkg-integration.json | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index 276071a..29c0863 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -11,7 +11,7 @@ "contact": "manojmodhwadia@outlook.com" }, "repo": "https://github.com/Muffinman75/agience-flare-dkg-integration", - "commit": "08a00810092dc5fd2d5b32b289ee139d72fc9d13", + "commit": "542bfdf699f787026a60af1133168c6244ccb43a", "license": "MIT", "requiresDkgNodeVersion": ">=10.0.1", "memoryLayers": ["WM", "SWM", "VM"], @@ -21,10 +21,10 @@ "install": { "kind": "cli", "package": "agience-flare-dkg-integration", - "version": "0.4.4", + "version": "0.4.5", "binary": "agience-dkg", "envRequired": ["DKG_BASE_URL"], - "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.4`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN); default port 8083 matches the reference `dkg-node/apps/agent` setup, use 8081 for the DKG Edge Node Agent Web UI/API. CLI: `agience-dkg share` (v10.0.1 SHARE), `promote` is a backward-compatible alias. Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." + "usageHint": "Install: `pipx install agience-flare-dkg-integration==0.4.5`. Default transport is the local DKG v10 daemon (DKG_BASE_URL=http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token). MCP transport supported via `--transport mcp` (requires DKG_TOKEN); default port 8083 matches the reference `dkg-node/apps/agent` setup, use 8081 for the DKG Edge Node Agent Web UI/API. CLI: `agience-dkg share` (v10.0.1 SHARE), `promote` is a backward-compatible alias. Governed-mode (`--from-agience-artifact`) reads AGIENCE_BASE_URL + AGIENCE_TOKEN — point these at the hosted Agience SaaS (https://my.agience.ai) so no local Agience stack is needed. npm wrapper published as alternative." }, "security": { "networkEgress": [ @@ -43,11 +43,12 @@ "MCP transport — POST /mcp -> tools/call dkg-sparql-query — read-only memory search" ], "credentialsHandled": ["AGIENCE_TOKEN"], - "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.4/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `share` CLI command (or the backward-compatible `promote` alias) or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." + "notes": "Distribution: dual-published with build provenance to npm (https://www.npmjs.com/package/agience-flare-dkg-integration) and PyPI (https://pypi.org/project/agience-flare-dkg-integration/0.4.5/) via tag-triggered GitHub Actions. The npm package is a thin wrapper (zero runtime deps) that delegates to the Python CLI on PyPI. npm publish uses `--provenance --access public` (SLSA v1, sigstore log); PyPI uses pypa/gh-action-pypi-publish with attestations: true. No preinstall/install/postinstall scripts — Section 8a compliant. No dynamic code loading, no eval on remote input. Transport: default is the local OriginTrail DKG v10 daemon over HTTP (DKG_BASE_URL=http://127.0.0.1:9201, bearer token auto-read from ~/.dkg/auth.token); MCP Streamable HTTP remains a fully-supported alternative (`--transport mcp`, requires DKG_TOKEN). Both are stable v10 public interfaces per bounty Section 5. Egress: only the local DKG daemon (or MCP node) by default; governed-mode optionally calls an operator-configured Agience endpoint (AGIENCE_BASE_URL; hosted default https://my.agience.ai); FLARE service is opt-in and disabled by default. Curator-authority surface: SHARE is invoked only when an operator explicitly runs the `share` CLI command (or the backward-compatible `promote` alias) or the equivalent Python API; PUBLISH/VM is exposed via the operator-initiated `vm-publish` command (daemon-only, never automatic); endorse/verify remain out of scope for Round 1. Governed-mode (`--from-agience-artifact`) refuses to project unless the upstream Agience artifact's state is `committed`, attaching the commit_receipt_id to the Knowledge Asset for auditability. pip-audit --production is clean. This integration repo: 87 tests (82 unit + 5 integration; governance-flow tests transport-agnostic). For context (not summed): Agience Core adds 11 DKG-projection-service tests, and FLARE — now part of Agience Core — carries 101 cryptographic-search tests. 6-month maintenance commitment — see docs/maintainer-statement.md." }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", - "demo": "https://youtu.be/g3OtdM0DKtE", + "demo": "https://youtu.be/bFzoqER60is", "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. VM is reachable today via the operator-initiated `vm-publish` command (v10.0.1 `POST /api/knowledge-assets/{name}/vm/publish`); PUBLISH is always explicit, never automatic, and the integration never calls endorse/verify.", "fitNotes": "Round-1 fit: a platform-level governance layer that turns committed artifacts from any upstream tool (chat clients, IDEs, research notebooks) into provenance-bearing Working/Shared Memory entries — the substrate Karpathy's LLM-Wiki / autoresearch direction depends on. Complementary to single-tool plugins (ChatGPT, Slack, GitHub, Obsidian) and to the first-party `cursor-mcp-dkg`: those clients can author into a governed Agience workspace; this integration governs which artifacts reach DKG WM/SWM, with what typing, and under whose authority. Engineered for forward-compatibility with Round 2 (Verified Memory, oracles): typed agience: predicates and stable UALs make PUBLISH a one-line extension, and FLARE provides the cryptographic retrieval boundary needed for confidential oracle inputs." } + From 5b99b390456b78e388774e8d9537148209e227c9 Mon Sep 17 00:00:00 2001 From: Manoj Modhwadia Date: Mon, 29 Jun 2026 15:06:39 +0100 Subject: [PATCH 11/11] update agience-flare-dkg-integration demo link --- integrations/agience-flare-dkg-integration.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/integrations/agience-flare-dkg-integration.json b/integrations/agience-flare-dkg-integration.json index 29c0863..65f3940 100644 --- a/integrations/agience-flare-dkg-integration.json +++ b/integrations/agience-flare-dkg-integration.json @@ -47,7 +47,7 @@ }, "trustTier": "community", "designBrief": "https://github.com/Muffinman75/agience-flare-dkg-integration/blob/main/DESIGN_BRIEF.md", - "demo": "https://youtu.be/bFzoqER60is", + "demo": "https://youtu.be/gduMkwpigkg", "promotionPath": "Artifacts originate as draft → committed inside Agience (governance gate). Committed artifacts project into DKG Working Memory as typed agience: RDF Knowledge Assets with provenance (author, commit_receipt_id, source_artifact UAL). Curator-authorized promotion (SHARE) elevates them to Shared Memory for team-gossiped collaboration. UAL stability and the agience: predicate set are designed so Round-2 promotion to Verified Memory is a small, additive step (PUBLISH against the existing UAL with the same JSON-LD shape), and downstream context oracles can consume matured Knowledge Assets without re-typing. VM is reachable today via the operator-initiated `vm-publish` command (v10.0.1 `POST /api/knowledge-assets/{name}/vm/publish`); PUBLISH is always explicit, never automatic, and the integration never calls endorse/verify.", "fitNotes": "Round-1 fit: a platform-level governance layer that turns committed artifacts from any upstream tool (chat clients, IDEs, research notebooks) into provenance-bearing Working/Shared Memory entries — the substrate Karpathy's LLM-Wiki / autoresearch direction depends on. Complementary to single-tool plugins (ChatGPT, Slack, GitHub, Obsidian) and to the first-party `cursor-mcp-dkg`: those clients can author into a governed Agience workspace; this integration governs which artifacts reach DKG WM/SWM, with what typing, and under whose authority. Engineered for forward-compatibility with Round 2 (Verified Memory, oracles): typed agience: predicates and stable UALs make PUBLISH a one-line extension, and FLARE provides the cryptographic retrieval boundary needed for confidential oracle inputs." }