Memact is evolving: Organization-wide architecture migration

[keepsloading]

Hi everyone,

Over the past few weeks, Memact's vision has evolved significantly.

What started as a project around portable user context is now evolving into an open identity infrastructure where users own an identity address and applications exchange user-approved context through open protocols.

To support this direction, we are beginning an organization-wide architecture migration.

What to expect

Over the coming days, you may notice:

• Repository renames
• New repositories
• Documentation updates
• New milestones and issues
• Updated contributor guides
• Protocol specifications
• Existing issues being rewritten, transferred, or closed if they no longer align with the current architecture

This is not just a cleanup. It is a complete realignment of the organization around the new vision.

For contributors

If you have an open issue or pull request, there is nothing you need to do right now.

We will review every contribution individually and preserve as much valuable work as possible. Where appropriate, we will help migrate contributions into the new architecture instead of asking contributors to start over.

If an issue or pull request no longer fits the project, we will explain why before closing it and point to the new direction whenever possible.

Why now?

As Memact grows, having a clear and consistent architecture becomes increasingly important.

Making these changes now helps establish a stronger foundation before the project reaches a larger contributor base.

Thank you

Thank you to everyone who has contributed so far.

Your ideas, discussions, issues, and pull requests have all helped shape Memact into what it is becoming today. We are excited to build this next chapter together.