Skip to main content
Glama
dongsheng123132

dsh-duty-separation-proof

dsh-duty-separation-proof

Offline, deterministic evidence that one supplied DSH workflow kept declared duties apart. It validates exact request/approval/execution/observation order, hash-bound object and workflow identity, receipt-chain continuity, disjoint principal sets, approval quorum, principal/observer diversity and freshness. It writes only a redacted, content-addressed JSON verdict.

This is not an authorization system. It does not grant roles, approve requests, execute changes, authenticate receipts, inspect live systems, or prove that the supplied ledger is exhaustive.

Why this is a separate layer

NIST distinguishes static, dynamic, object-based, operational and history-based separation of duties. This plugin implements a narrow post-hoc evidence layer for one supplied workflow object. It complements:

  • dsh-guarded-hcl, whose separation is specific to optimizer/evaluator/policy/commit-controller boundaries;

  • dsh-decision-effect-proof, which reconciles authorization decisions with effects;

  • dsh-artifact-promotion-proof, which verifies an artifact's promotion chain;

  • dsh-access-review-proof, which verifies entitlement recertification closure.

Here, the question is only: did the supplied hash-linked workflow receipts satisfy the declared duty-conflict policy?

Related MCP server: EVIDIQ Rubric MCP

Use

npm test
npm run check
node bin/dsh-duty-separation-proof.mjs inspect examples/settled.json
node bin/dsh-duty-separation-proof.mjs verify examples/settled.json

The DSH bundle exposes dsh_duty_separation_inspect and dsh_duty_separation_verify. The standalone MCP server exposes equivalent proof-only inline tools.

Manifest boundary

All workflow, object, revision, policy, principal, observer and receipt identities are lowercase SHA-256 values. The only public identifier is a bounded proofId, and reports contain only its hash. The required sequence starts with request, contains execute, ends with observe, and may contain multiple approve stages. disjointDutySets and quorum thresholds are explicit policy input.

Reports intentionally say authenticatesReceipts: false, provesLedgerExhaustive: false, and provesAbsenceOfUndeclaredActions: false.

References

MIT licensed.

A
license - permissive license
Not graded
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • Deterministic pre-execution audit for trading agents. PASS/WAIT/FAIL, reproducible verdict_hash.

  • Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402.

  • Free, no-account verification of KeyHalve-sealed documents. Read-only; never receives keys.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dongsheng123132/dsh-duty-separation-proof'

If you have feedback or need assistance with the MCP directory API, please join our Discord server