feat: add Counterparty Evidence Desk fixture service#12
Open
mj-deving wants to merge 8 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a first runnable Directory service slice: Counterparty Evidence Desk.
This is intentionally fixture-backed and no-spend. It gives the Directory a visible service card, service detail page, runnable UI, machine contract JSON, and verifier-backed receipt flow without claiming live source truth, live payment, settlement, certification, or chain anchoring.
What changed
CounterpartyEvidenceReceiptfixture and verifier checks/api/dacs/counterparty-evidence/runfor the no-spend fixture runfixture:locatorsTrust boundary
The receipt proves fixture receipt integrity and authorship only. It does not prove source truth, compliance clearance, sanctions clearance, payment readiness, settlement, or chain inclusion. The UI also reports the fixture freshness state explicitly.
Validation
git merge-tree origin/main HEADcleangit diff --checkbun run test- 41/41 passbun run typecheckbun run buildautoreview --mode branch --base origin/mainclean after fixing the accepted fixture/chain-reader boundary findingNotes
bun run indexwas not used as a pass/fail gate here: without live deployment config it enters the chain-scan path and timed out locally. The fixture seed path and mocked reindex preservation are covered by tests.