[cfi-dkgv10-r1] Add agience-flare-dkg-integration

integrations/agience-flare-dkg-integration.json

@@ -0,0 +1,54 @@
+{
+  "$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": "542bfdf699f787026a60af1133168c6244ccb43a",
+  "license": "MIT",
+  "requiresDkgNodeVersion": ">=10.0.1",
+  "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.5",
+    "binary": "agience-dkg",
+    "envRequired": ["DKG_BASE_URL"],
+    "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": [
+      "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 (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 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 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.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/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."
+}
+