Track KYC document reuploads and preserve audit history for replaced files

[grantfox-oss]

Context

The KYC upload flow in src/controllers/upload.controller.ts replaces the existing document URL for a submission, but the system does not clearly preserve the history of what was previously uploaded. This creates ambiguity for compliance review and manual moderation.

Problem statement

Implement a simple audit trail for KYC document reuploads so moderators and operators can see when a document was replaced and which file versions were previously associated with the submission.

Current behavior

• The controller updates the KYC submission document URL directly when a new file is uploaded.
• Previous document URLs are not preserved in a structured way for later review.

Required behavior

• Each document reupload should create a traceable history entry that records the replaced file reference and timestamp.
• The system should expose the history in a way that can be consumed by a future moderation view or API endpoint.
• The implementation should not break the current upload flow.

Constraints

• The change should avoid introducing a new storage backend or major schema redesign.
• Existing KYC upload behavior should remain compatible.

Acceptance criteria

• Replacing a KYC document creates a stored history record.
• The history retains enough information to identify the replaced file and when it was replaced.
• Unit tests cover successful history creation and missing-data cases.

Out of scope

• Building a full moderation dashboard.
• Changing the KYC submission schema beyond what is necessary for history tracking.

Hints and references

• Review the KYC submission model and the upload controller logic for where the replacement should be recorded.

[keljoshX]

Hi maintainer, can i please be assigned to this?

[felixakintoyese]

I have the necessary experience to execute this task perfectly within a good time frame.

[OluRemiFour]

I've reviewed the issue and understand the requirements. I'd love to work on this and submit a clean PR that meets the acceptance criteria.

[felixakintoyese]

I have the necessary experience to execute this task perfectly within a good time frame.

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[jaynomyaro]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[adesuwa-tech]

Hi maintener, i would love to work one this issue, i already reviewed the description and will submit a clean PR, please kindly assign

[nurudeenheroic]

Hello! I'd appreciate the opportunity to work on this issue.I've gone through the issue and am ready to get started.

[grantfox-oss]

🦊 GrantFox — @felixakintoyese has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #147)
2. Your PR will be reviewed by the aid-linkk maintainers

Good luck! Track your progress on GrantFox.