Skip to content

Clarity of Priority

Policy brief

Core proposition

Mainstay's first purpose is to enable a community to carry out its own work: maintain records, move value, administer shared resources, and sustain relationships under accountable local governance. Compliance with applicable requirements from authorities outside the community supports the responsible exercise of that capability.

Community purpose leads. Applicable obligations shape how that purpose is carried out.

This is a priority of purpose and design. Obligations must be understood from the outset and met when they apply. The community's needs determine what the infrastructure is for; compliance helps define the conditions under which it operates. Success requires both useful local capability and responsible operation.

This position gives practical meaning to Mainstay's cooperative independence: communities can govern and sustain their own activities while working constructively with governments, regulators, service providers, and other communities.

Begin with the work of the community

A community may be a cooperative, association, municipality, Indigenous community, or another body with shared responsibilities. Its authority and relationship with other institutions depend on its own circumstances. A community may itself govern through public institutions; local and government authority are not necessarily opposing categories.

The starting questions should be concrete. What do members need to accomplish? Who is responsible for decisions? What records must remain available? What must people be able to check, correct, transfer, or recover?

These questions establish the purpose of the system before a particular credential, reporting format, supplier, or outside integration becomes a design requirement. External requirements are then considered against the actual activity and the authority responsible for it.

A service can satisfy an external reporting requirement while remaining difficult for members to use. It can also be convenient locally while failing an applicable obligation. Clarity of priority requires the design to address both, with community benefit remaining the reason for providing the service.

Give external requirements a defined scope

Responsible compliance starts by identifying which requirements apply, to which activities, and under whose authority. Legal obligations, contractual conditions, recognition criteria, and provider preferences should be recorded distinctly so that each can be assessed on its own basis.

For each requirement, the responsible operator should be able to explain its source, the affected decision or service, the evidence needed, and any access or retention it entails. Changes should be reviewed through a documented process with an accountable decision-maker.

This supports proportionate implementation. A requirement associated with one regulated interaction should be applied to that interaction and extended to other activities only where there is a justified need. Wherever a choice is available, the design should preserve useful local operation and minimize unnecessary disclosure and dependence.

When an obligation constrains a community objective, the responsible authority should explain the constraint and consider lawful alternatives, changes to the service, or an appropriate review or appeal. Software should make the decision and its consequences visible to the people affected.

A practical example

Consider a cooperative that manages a shared workshop. Its ordinary work includes recognizing members, recording safety training, lending equipment, and resolving disputes. Its system should make those activities dependable under documented rules, with clear responsibilities and appropriate access to records.

An insurer or public authority may require particular evidence for a specified activity. The cooperative should be able to provide that evidence through a defined process. This additional relationship should not automatically make every booking, membership interaction, or internal record dependent on the same external service.

The design question is whether each dependency is necessary for the activity it governs. Where external verification is required, it must be completed. Where local evidence is sufficient, the community should retain the ability to act on it. An outside institution remains responsible for deciding what it recognizes for its own purposes.

Community accountability includes the member

Community purpose must be expressed through legitimate, accountable procedures. Members need understandable rules, appropriate privacy, accessible services, and ways to correct records and challenge decisions. Administrators need defined powers, reviewable actions, and procedures for succession and recovery.

Local control can concentrate power as readily as remote control. Community infrastructure should therefore protect people within the community as well as strengthen the community's ability to work with others. Portability and exit should preserve the records and rights a person is entitled to retain, while respecting the confidentiality and obligations of other participants.

What the wallet discussion contributes

In Is there money in the EU Digital Identity Wallet?, Jon Ølnes of Signicat describes an ecosystem organized around national identity, recognized providers, certification, and service-provider integration. He also emphasizes user control and the need for sustainable funding across the ecosystem (see the reference below).

The presentation illustrates a different starting point: how institutions can provide, recognize, integrate, and finance digital identity at scale. Mainstay begins with the capability a community needs to conduct its own affairs. These approaches can meet through explicit recognition and interoperability arrangements.

The funding question applies equally to community infrastructure. Local capability needs maintenance, support, recovery, and accountable operators. Funding arrangements should make these costs understandable and support continuity when a supplier or funding source changes. Any fee or external dependency attached to routine verification should be assessed for its effect on privacy, accessibility, and continued use.

Implications for Mainstay

This priority should guide Mainstay's product and deployment decisions:

  • Design around ordinary community work. Begin with the records, services, and exchanges members need, including accessible and assisted ways to use them.
  • Keep authority explicit. Identify who may make each decision and the scope within which it has effect. Software operation alone confers no mandate.
  • Bound external dependencies. Connect external identity, reporting, and verification services to the activities that require them, with clear behavior when those services are unavailable.
  • Preserve confidentiality, integrity, and availability together. Limit disclosure appropriately, retain verifiable evidence, and provide dependable authorized access and recovery.
  • Support continuity and replacement. Make portability, documented operation, sustainable funding, and tested recovery part of deployment planning.
  • Evaluate member outcomes. Measure whether people can complete useful work and obtain correction or remedy alongside evidence that applicable obligations are being met.

These are criteria for development and evaluation. Mainstay's project status describes current capabilities and work still underway.

A decision rule for partners and operators

Every significant requirement should answer two questions:

  1. What community purpose does this serve, or what applicable obligation does it fulfil?
  2. Can that purpose or obligation be met while preserving more member agency, privacy, accessibility, and local continuity?

The resulting policy position is straightforward:

Mainstay enables communities to govern and sustain their own activities, meet applicable obligations, and cooperate with others on clear terms. Community benefit remains the primary measure of success.

Reference

Jon Ølnes, Signicat, Is there money in the EU Digital Identity Wallet?, presentation to W3C CCG. The supplied presentation's title slide is dated 19 October 2026. See pp. 11–15 on user control and institutional roles, pp. 17–23 on funding and verification, and p. 24 on intermediaries. These passages describe the presenter's analysis of the wallet ecosystem.