← Rohas Legal AI: InvestigationsCONTENT HISTORY

Update to Rohas Legal AI: Investigations

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.2.1

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Reconstruct flows of funds across bank accounts, ledgers, entities, instruments, currencies, and blockchains. Use for asset tracing, fraud, insolvency, sanctions, AML, disputes, or source-linked transaction paths.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 283
    }
  ],
  "name": "transaction-tracer",
  "skill_md_contents": "---\nname: transaction-tracer\ndescription: >-\n  Reconstruct flows of funds across bank accounts, ledgers, entities,\n  instruments, currencies, and blockchains. Use for asset tracing, fraud,\n  insolvency, sanctions, AML, disputes, or source-linked transaction paths.\n---\n\n# Transaction Tracer\n\nMake each funds-flow edge traceable to a source. State the tracing convention and\ndo not imply ownership, knowledge, or misconduct from movement alone.\n\n## Inputs\n\nObtain the objective, jurisdiction, accounts, wallets, entities, period,\ncurrencies, native statements, ledger, invoices, contracts, blockchain hashes,\naddresses, networks, opening balances, FX sources, relationships, and limitations.\n\n## Tracing method\n\n1. Preserve raw records and build a normalised ledger with stable source IDs,\n   timestamps, time zones, currencies, signs, counterparties, networks, tokens,\n   and transaction identifiers.\n2. Test uniqueness and completeness, deduplicate, and reconcile opening balance\n   plus inflows less outflows to closing balance. List differences.\n3. Separate account ownership, beneficial ownership, authority, access, control,\n   and transaction purpose; source each relationship independently.\n4. Trace direct transfers, then layering, conversions, intermediaries, cash,\n   fees, refunds, reversals, chargebacks, and internal movements.\n5. Disclose a defensible convention such as FIFO, LIFO, proportional allocation,\n   or lowest intermediate balance; show alternatives where material.\n6. Apply dated, sourced FX rates; retain original amounts and isolate valuation.\n7. For blockchains, identify network, transaction model, token contract, fees,\n   change, bridges, swaps, mixers, and exchange touchpoints. Separate on-chain\n   observation from third-party attribution.\n8. Test loops, pass-through timing, aggregation, splitting, address reuse,\n   common counterparties, and off-chain explanations without overstating taint.\n9. Quantify direct, indirect, commingled, dissipated, and unresolved amounts as\n   separate scenarios and prevent double counting.\n10. Record reproducible queries, transformations, exclusions, assumptions, and\n    the source for every displayed node and edge.\n\n## Output\n\nProvide a source inventory, reconciliations, chronological ledger, funds-flow\ntable and map, relationship table, traced scenarios, gaps, and reproducibility\nappendix.\n\n## Guardrails\n\nDo not access accounts or wallets, move funds, obtain credentials, or evade legal\nprocess. Do not assume an address belongs to a person, attribution is certain, or\nexposure proves control or guilt. Protect financial data and exculpatory paths.\n"
}

SHA-256 of public snapshot: 329faac8224b24f7b15fca238f497eda0028972c928a528211932841466de53e