Skip to main content

Governed authoring layer above DKG v10: commit-gated Agience artifacts, policy-controlled projection, FLARE confidentiality, typed agience: RDF Knowledge Assets.

Project description

agience-flare-dkg-integration

The governance layer above dkg mcp setup. OriginTrail's official dkg mcp setup (shipped 7 May 2026) makes MCP-to-DKG a two-command commodity. This package is what sits upstream — committed Agience Core artifacts, optional FLARE confidentiality, and typed agience: RDF Knowledge Assets — so what reaches Working Memory is governed, attributable, and SPARQL-queryable, not raw LLM output.

See the head-to-head comparison and design brief.

Features

  • MCP stdio server (agience-dkg-mcp) — exposes agience_wm_write, agience_share (agience_promote alias), agience_search tools for Claude Desktop, Cursor, Claude Code, and any MCP host
  • Writes committed Agience artifacts to DKG v10 Working Memory as typed JSON-LD Knowledge Assets with the agience: RDF vocabulary — SPARQL-queryable by type, author, collection, and memory layer
  • Promotes eligible assets to Shared Memory (SHARE) via the daemon's POST /api/knowledge-assets/{name}/swm/share (or dkg-create with privacy=public on MCP transport)
  • Searches across memory layers via the daemon's POST /api/query (or dkg-sparql-query on MCP transport)
  • Default transport: direct HTTP to the local DKG v10 daemon at http://127.0.0.1:9201; bearer token auto-read from ~/.dkg/auth.token. Alternative transport: MCP Streamable HTTP at POST /mcp with SSE stream handling
  • Distinguishes transport success from blockchain anchoring state (status: anchored vs status: pending)
  • FLARE optional path: when policy_class = "internal-confidential", only derived projections reach DKG; raw content stays encrypted

Install

pip install agience-flare-dkg-integration

MCP Server (Claude Desktop, Cursor, etc.)

Default config uses the local DKG v10 daemon — no token is needed because the daemon transport auto-reads ~/.dkg/auth.token:

{
  "mcpServers": {
    "agience-dkg": {
      "command": "agience-dkg-mcp",
      "env": {
        "DKG_BASE_URL": "http://127.0.0.1:9201"
      }
    }
  }
}

Tools: agience_wm_write, agience_share (agience_promote alias), agience_search.

To target an MCP-fronted DKG node instead, add "DKG_TRANSPORT": "mcp", set "DKG_BASE_URL": "http://localhost:8083", and add "DKG_TOKEN": "<mcp-bearer>".

CLI

# Default: local DKG v10 daemon. Bearer token auto-read from ~/.dkg/auth.token.
# DKG_BASE_URL defaults to http://127.0.0.1:9201 if unset.

# Write to Working Memory
agience-dkg wm-write \
  --title "Architecture Decision: use DKG v10" \
  --artifact-type decision \
  --artifact-id art-001 \
  --content "We will use DKG v10 Working Memory as the shared knowledge substrate." \
  --context-graph-id agience-demo \
  --collection-id my-project

# Share to Shared Memory (SHARE)
# Pass the Knowledge Asset NAME from the wm-write output (e.g. "art-001-Architecture-Decision-..."),
# NOT the v10.0.1 turnUri (its trailing revision index does not contain the KA name).
agience-dkg share <ka-name> --context-graph-id agience-demo
# agience-dkg promote is still accepted as a backward-compatible alias.

# Search
agience-dkg search "architecture decisions" --context-graph-id agience-demo

Resolved invocation block. Every wm-write call prints a # agience-dkg wm-write — resolved invocation (copy to replay): block to stdout before the HTTP call fires, showing all fully-resolved flags with tokens truncated to 8 chars. Useful for testers and reviewers to copy and replay the exact command.

For MCP-fronted DKG nodes, add --transport mcp --base-url http://localhost:8083 --token <mcp-bearer>.

Python API

from agience_dkg_integration import DkgDaemonClient, MemoryTurnRequest
from agience_dkg_integration.formatter import artifact_to_markdown, session_uri_for_collection

# Default: local DKG v10 daemon. Bearer token auto-resolves from ~/.dkg/auth.token.
client = DkgDaemonClient(base_url="http://127.0.0.1:9201")

# Alternative: MCP-fronted DKG node
# from agience_dkg_integration import DkgHttpClient
# client = DkgHttpClient(base_url="http://localhost:8083", bearer_token="<mcp-bearer>")

result = client.memory_turn(MemoryTurnRequest(
    contextGraphId="agience-demo",
    markdown=artifact_to_markdown(title="My Note", content="...", artifact_type="research-note", artifact_id="art-001"),
    layer="wm",
    sessionUri=session_uri_for_collection("my-project"),
))
print(result.turn_uri)

Links

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

agience_flare_dkg_integration-0.4.4.tar.gz (27.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

agience_flare_dkg_integration-0.4.4-py3-none-any.whl (30.9 kB view details)

Uploaded Python 3

File details

Details for the file agience_flare_dkg_integration-0.4.4.tar.gz.

File metadata

File hashes

Hashes for agience_flare_dkg_integration-0.4.4.tar.gz
Algorithm Hash digest
SHA256 7d82b03a98a8f74d22492db8a432c36190712d4c03afe6824f7944c37b966920
MD5 7edf6b0460ad750bf70085e78e34decb
BLAKE2b-256 1af2a7a6d9db21d29d33a2a38b9d17b1957d260c31087ef5cccc67f49e42c62d

See more details on using hashes here.

Provenance

The following attestation bundles were made for agience_flare_dkg_integration-0.4.4.tar.gz:

Publisher: publish.yml on Muffinman75/agience-flare-dkg-integration

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file agience_flare_dkg_integration-0.4.4-py3-none-any.whl.

File metadata

File hashes

Hashes for agience_flare_dkg_integration-0.4.4-py3-none-any.whl
Algorithm Hash digest
SHA256 db75700f8417a55216b5f7f3dc958202926b12179b596d4e5186575eb6953a45
MD5 45d8f961f1dbb0b7065bf39d3a0f1282
BLAKE2b-256 cceef9d7e1c2151a2b007773862ea7514bc4b8f959ece3f2561554c9e0009a18

See more details on using hashes here.

Provenance

The following attestation bundles were made for agience_flare_dkg_integration-0.4.4-py3-none-any.whl:

Publisher: publish.yml on Muffinman75/agience-flare-dkg-integration

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page