The Scrum Guide only identifies three artifacts - product backlog, sprint backlog and product increment. Both the product & sprint backlogs would capture requirements, but these might be at a high-level if the team is capable of delivering a quality, customer satisfactory solution without getting into greater details.
However, the Scrum Guide does not prevent teams from adding additional artifacts or repositories if those add value to their delivery work.
For example, a team who is using a work management solution like Jira in conjunction with a wiki-like tool such as Confluence might capture user story summaries in Jira and link those to detailed descriptions of the underlying requirements in Confluence.
I hope if dogs ever take over the world, and they choose a king, they don't just go by size, because I bet there are some Chihuahuas with some good ideas.