Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions activity/14_jun_2026.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# 14 th June 2026

## What we did ?
1. bank of india hackathon presentation final touch.
2. hackathon registration.

## 13th JUNE 2026
1. problem and solution discussed.
2. pdf and architecture developed
Comment on lines +3 to +9

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Add the objective/conclusion section expected by the log format.

This entry only covers the task checklist and the 13 June recap; it still misses the “that day’s objective and conclusions” section called for in activity/README.md. Per the documented activity-log contract, please add that block here.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@activity/14_jun_2026.md` around lines 3 - 9, The activity log entry in
activity/14_jun_2026.md is missing required sections per the documented format
in activity/README.md. Add an "objective" section at the beginning (describing
what was planned to be accomplished on that day) and a "conclusion" section at
the end (summarizing what was achieved and any key takeaways), following the
contract specified in the README file. These sections should frame the existing
"What we did" checklist and the 13th June recap content.

15 changes: 15 additions & 0 deletions bank_of_india/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# BOI CyberSecurity Hackathon

## Problem Statement
```txt
Developing a solution having AI/ML capabilities for detecting suspicious transactions
and mule accounts by ingesting financial transactions
and/or fraud monitoring solution alerts
and/or Transaction monitoring system alerts
and govt cyber fraud alerts/tickets
and preventing circulation of fraudulent proceeds
through mule accounts.
This solution should consume real-time regulatory inputs/ feeds and cross-channel bank data.
```


Loading