{

"agentName": "Evidence Collection and Management Agent (ECMA)",
"agentDescription": "Consolidates, organizes, and manages evidence related to potential Preferential, Undervalued, Fraudulent, or Extortionate (PUFE) transactions identified during a forensic audit. Ensures systematic documentation, linking findings to source documents, and preserving the integrity of collected evidence for potential legal proceedings under frameworks like the IBC.",
"version": "1.0",
"status": "Conceptual",
"goals": [
  "Centralize findings and flags generated by other forensic audit agents (TPRA, FSAA, DAVA, ATRA).",
  "Establish and maintain clear links between audit findings (e.g., flagged transactions, anomalies) and the specific supporting source documents or data points.",
  "Organize collected evidence logically (e.g., by potential PUFE type, transaction trail, counterparty, date).",
  "Ensure evidence is properly labeled, described, and contextualized.",
  "Maintain an audit trail of evidence collection and management activities (who collected what, when, from where).",
  "Facilitate the preservation and integrity of digital evidence (e.g., by recording hashes of key electronic files).",
  "Generate structured evidence packages or summaries suitable for review by legal teams and for potential submission in legal proceedings.",
  "Track the status of evidence gathering for specific investigations or findings."
],
"keyCapabilities": [
  "Evidence Aggregation Hub: Ingests structured outputs (reports, lists, alerts) from various forensic analysis agents.",
  "Source Document Linking: Provides interfaces or mechanisms to link findings directly to underlying source documents stored in a repository (e.g., linking a flagged transaction entry to the PDF bank statement page).",
  "Metadata Management: Captures key metadata for each piece of evidence (source, date collected, relevance, type, associated finding ID).",
  "Logical Structuring: Allows organizing evidence into case files, by PUFE category, by transaction trail, or using custom tagging.",
  "Evidence Database: Maintains a searchable database of collected evidence items and their relationships.",
  "Chain of Custody Logging: Records user actions related to accessing, adding, or modifying evidence records (not the evidence file itself, ideally).",
  "Digital Integrity Verification Support: Calculates and stores cryptographic hashes (e.g., SHA-256) of key digital evidence files upon ingestion or linking.",
  "Evidence Package Assembly: Compiles selected evidence items, including source document references/copies and associated analysis reports, into a structured export format.",
  "Search and Retrieval: Enables users to efficiently search for specific evidence based on various criteria (date, type, associated finding, keyword).",
  "Status Tracking: Allows users to mark the collection/verification status for pieces of evidence.",
  "Annotation & Notes: Allows auditors to add context or notes to evidence items."
],
"targetUsers": [
  "Forensic Auditors",
  "Audit Managers / Team Leads",
  "Legal Counsel (receiving evidence packages)",
  "Insolvency Professionals / Resolution Professionals / Liquidators (overseeing process)",
  "Support staff assisting with evidence management"
],
"inputDataRequirements": [
  "Outputs/Findings from TPRA, FSAA, DAVA, ATRA (Structured data: JSON, CSV, DB records).",
  "Access to the repository of source documents (e.g., bank statements, invoices, contracts, GL extracts) - *crucial for linking*.",
  "Case Context (Debtor name, period under review, key dates).",
  "User inputs for linking, annotations, and status updates.",
  "Configuration for evidence categorization (PUFE types).",
  "Access controls defining user permissions."
],
"outputFormats": [
  "Searchable Evidence Database/Log (Accessible via UI/API).",
  "Structured Evidence Packages (e.g., Indexed PDF report, Zipped archive with manifest file, potentially including copies/links to source documents).",
  "Evidence Summary Reports (Grouped by PUFE type, transaction trail, etc.).",
  "Audit Trail Report for Evidence Management Activities.",
  "Evidence Status Trackers.",
  "Exportable lists of evidence with metadata (CSV, XLSX)."
],
"potentialBenefits": [
  "Creates a highly organized and traceable repository of forensic evidence.",
  "Simplifies the process of assembling comprehensive evidence packages for legal action.",
  "Enhances the reliability and defensibility of audit findings by clearly linking them to sources.",
  "Improves collaboration within the audit team by providing a central evidence hub.",
  "Helps maintain the integrity of digital evidence.",
  "Reduces the risk of losing track of critical evidence pieces.",
  "Streamlines the handover of findings to legal teams or other stakeholders."
],
"requiredTools": [
  {
    "toolCategory": "Data Storage & Management",
    "tools": [
      "Relational Databases (Essential: PostgreSQL, MySQL, SQL Server - for metadata, links, logs, status tracking)",
      "Document Management System or Robust File Storage (Crucial: SharePoint, OpenText, Cloud Storage like AWS S3 / Azure Blob / Google Cloud Storage - *to hold the actual evidence files*)",
      "Database Connectors (to link DB records to file paths/URIs)"
    ]
  },
  {
    "toolCategory": "Data Acquisition & Integration",
    "tools": [
      "API Clients (to ingest findings from other agents)",
      "Database Connectors (to read analysis results stored elsewhere)",
      "File System / Cloud Storage SDKs (to interact with the document repository)"
    ]
  },
  {
    "toolCategory": "Data Processing & Linking",
    "tools": [
      "Data Manipulation Libraries (e.g., Pandas)",
      "Custom logic for establishing and maintaining links (core application code)"
    ]
  },
  {
    "toolCategory": "Integrity & Security",
    "tools": [
      "Hashing Libraries (e.g., hashlib in Python, built-in OS tools)",
      "Access Control mechanisms within the database and document store",
      "Secure Audit Logging features"
    ]
  },
  {
    "toolCategory": "Search & Retrieval",
    "tools": [
      "Database Query Languages (SQL)",
      "Full-Text Search capabilities (Optional, within DB like PostgreSQL FTS or external like Elasticsearch on metadata)"
    ]
  },
  {
    "toolCategory": "Reporting & Export",
    "tools": [
      "PDF Generation Libraries (ReportLab, FPDF)",
      "Archiving Libraries (e.g., ZipFile in Python)",
      "Spreadsheet Writing Libraries (openpyxl)"
    ]
  },
  {
    "toolCategory": "Workflow & User Interface (Recommended)",
    "tools": [
      "Web Frameworks (e.g., Flask, Django, React, Angular - for user interaction, evidence browsing, linking)",
      "Workflow Engines (Optional, for managing evidence review/approval steps)"
    ]
  }
]

}