Community Purpose and Personal Agency
Policy brief
Core proposition
Mainstay begins with a community's ability to conduct its own affairs under accountable local governance. That purpose includes the agency of the people who participate: their ability to express privacy requirements, understand commitments, retain evidence, and seek correction or remedy.
Community purpose leads. Members retain agency. Cooperation rests on clear commitments and accountable practice.
IEEE 7012-2025, Standard for Machine Readable Personal Privacy Terms, offers a relevant agreement model. Known as MyTerms, it enables an individual to propose standard privacy terms to an organization and, when accepted, retain the same signed agreement as the organization. Its contribution to Mainstay's philosophy is practical: people should be able to bring requirements to a relationship and keep evidence of the commitments made to them.
Community benefit includes personal agency
Mainstay's Clarity of Priority establishes community benefit as the primary purpose of its infrastructure, with applicable obligations shaping responsible operation. This priority applies within the community as well as in its relationships with outside authorities.
A locally operated service should make membership and participation more useful, understandable, and dependable. Members should know who can access their information, for what purposes, and under which rules. They should be able to distinguish information needed to provide a service from optional uses such as publicity, research, or service improvement.
Community stewardship carries responsibilities toward each member. Shared governance should give people ways to influence rules, challenge mistakes, and obtain help. Local administration alone does not establish that those responsibilities have been met.
What IEEE 7012 contributes
The standard defines an interaction between an individual as the first party and an organization as the second party. The individual selects an agreement from a public roster maintained by a neutral entity. The agreement has plain-language, legal, and machine-readable representations. Upon acceptance, both parties sign and keep identical records (clauses 1, 4, and 5).
This makes a useful distinction between publishing a privacy policy and making a mutual commitment. The member should be able to establish which terms were proposed, whether they were accepted, and what agreement applies. An unanswered request should remain visibly unanswered.
For Mainstay, the philosophical connection is reciprocity. People provide information and participate in community activity; the responsible service should provide clear commitments and accessible evidence in return. The member's ability to inspect the relationship should endure beyond the screen on which it began.
Representation must have a clear mandate
Clause 5.2 requires agents to be controlled by and responsible exclusively to the party they represent. An agent in this context can be ordinary software or a service; it need not be an AI system.
Mainstay should apply the same clarity of responsibility when designing member assistance. A community may recommend privacy settings, explain agreements, or help a person use a service. The person should understand what authority has been delegated and how to change or withdraw that delegation for future actions.
If an operator hosts both the member's tools and the community service, their respective authority must remain distinguishable. The operator should have no unexplained ability to alter the member's preferences or accept new terms on the member's behalf. Convenience should come with a visible mandate and a record of consequential actions.
Agreements should remain usable evidence
IEEE 7012 requires identical, immutable agreement copies in each party's data store and requires substitutable storage with data portability (clause 5.4.4). It also provides for recording refusals and sharing disputed agreements for review (clauses 5.2.4–5.2.5).
These requirements fit Mainstay's emphasis on records that remain available and verifiable through changes in software, staff, and providers. Members should be able to retrieve the exact agreement they accepted, identify its version and parties, and present it to an appropriate reviewer.
Later changes should preserve a clear history of which commitments applied when. A new agreement should be distinguishable from the one it replaces. Agreement records themselves require confidentiality, controlled disclosure, and a considered retention policy because they can reveal sensitive relationships.
Mainstay's community-led recordkeeping principles provide a complementary approach to preserving exact artifacts and evidence. Preserving a signature establishes evidence about an agreement; operational review is still needed to determine whether the parties fulfilled it.
Put commitments into ordinary practice
Consider a member supplying a training record to a cooperative workshop. The cooperative needs to determine which equipment the member may use. The member wants the information used for that purpose under clear limits on access, retention, and further disclosure.
An agreement process inspired by MyTerms would make the proposed terms and the cooperative's response explicit, then give each side the accepted record. The cooperative would translate its commitments into staff permissions, handling procedures, and review practices. If a proposed use falls outside the agreement, the service should identify the additional authority or new agreement needed before proceeding.
This example illustrates Mainstay's desired behavior. A conforming IEEE 7012 implementation would also need an appropriate roster agreement and all applicable requirements of the standard.
Respect the boundaries of each authority
IEEE 7012 is specifically a two-party model between an individual and an organization (clause 5.4.3). Collective community decisions and agreements between organizations need their own governance arrangements. An individual agreement cannot establish a mandate to speak for other members or decide the treatment of collectively governed information.
Mainstay should keep personal choices, community rules, provider commitments, and applicable external obligations understandable and distinct. Where an activity carries requirements that a provider cannot vary, the provider should explain those limits before accepting terms. Claims about legal effect require assessment in the relevant context; standards conformance alone does not establish legal compliance.
This supports cooperative independence. Communities can work with external institutions through defined relationships while remaining accountable to the people whose information and participation make those relationships possible.
Principles for development and evaluation
Mainstay should use the following criteria when evaluating privacy agreement workflows:
- Understandable participation. Present a small set of meaningful choices in accessible language, with assistance appropriate to the community.
- Explicit commitments. Distinguish proposed, accepted, rejected, and superseded agreements, and identify the responsible parties.
- Proportionate information use. Connect collection, access, disclosure, and retention to a stated purpose and applicable authority.
- Accountable representation. Make delegated powers visible and keep member preferences under the member's control.
- Portable evidence. Let both parties retain and retrieve the accepted agreement through provider and infrastructure changes.
- Practical remedy. Provide a usable route for questions, correction, disputes, and review, with people responsible for responding.
These are Mainstay design principles informed by IEEE 7012. They do not assert that Mainstay currently implements or conforms to the standard. A conformance assessment would need to address the full requirements, including roster governance, representations, signing, agent behavior, and recorded metadata. The annex examples are informative rather than normative (clause 6).
The guiding position is that a community's independence and its members' agency should reinforce each other. Mainstay should give communities the capability to act responsibly and give people the means to understand, verify, and question the commitments made in their name.
References
- IEEE, IEEE Std 7012-2025: Standard for Machine Readable Personal Privacy Terms, published 20 January 2026. Core references: clauses 1, 4, 5.2, 5.4.3–5.4.5, and 6. See the MyTerms standard overview and IEEE access links.
- Mainstay, Clarity of Priority.
- Mainstay, Data Sovereignty, Authority, and Capability.
- Mainstay, Project Status, for implementation maturity.