Observed since 21 Oct, 09:05 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
Governed authoring layer above DKG v10: commit-gated Agience artifacts, policy-controlled projection, FLARE confidentiality, typed agience: RDF Knowledge Assets.
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.
agience-dkg-mcp) — exposes agience_wm_write, agience_share (agience_promote alias), agience_search tools for Claude Desktop, Cursor, Claude Code, and any MCP hostagience: RDF vocabulary — SPARQL-queryable by type, author, collection, and memory layerPOST /api/knowledge-assets/{name}/swm/share (or dkg-create with privacy=public on MCP transport)POST /api/query (or dkg-sparql-query on MCP transport)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 handlingstatus: anchored vs status: pending)policy_class = "internal-confidential", only derived projections reach DKG; raw content stays encryptedpip install agience-flare-dkg-integration
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>".
# 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-writecall 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>.
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)
MIT
Download counts and popularity will appear here as the collector receives them.
| Version | Published | Direct dependencies | Open version |
|---|---|---|---|
| 0.4.5 | 29 Jun 2026 | 6 |
This describes our collected data; it is not a security assessment.
Shared repository data · GitHub
Observed since 21 Oct, 09:05 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
package:207c09de913917f8d7c9b1dcbb153fce71761ba4a3a3af9d158d7d15cc51596b