[Feat]: High level doc refinement

Component

Other

Summary

Inspired from this comment

On a more general note not related to this PR: if this repository had more information on why it made the decisions it did eg explaining the purpose of splitting the contracts how they are, why the flows are the way they are etc, it would be helpful personally (for me, but also for things like Claude to be more helpful in checking things I expect)

We should aim to clean up and refine some high level documentation. Start very general and then add specificity as needed. Be concise as well

• What is DotNS
• Why do we want DotNS / motivation for DotNS
• What are the key pieces and contracts of DotNS
• What do they do and why do they do it

Assume someone is coming in with 0 context or expertise, could they get a solid high level understanding and know where to start if they want to contribute in under 1 hour.

Proposal

No response

Acceptance criteria

No response

Context / notes

No response

Start by reading the repository's existing documentation and the high-level structure of its DotNS contracts, then use the linked review comment as context for the missing explanations. Done means concise documentation that explains what DotNS is, its motivation, the key contracts and flows, why they are structured that way, and where a newcomer should begin contributing.