The ARC Framework: Accountability, Regeneration, Consent

ARC is a compact lens for judging whether a proposal is actually ready. It asks three questions — Accountability, Regeneration, Consent — and a proposal that cannot answer all three is not yet complete. ARC is not a checklist to tick; it is a frame for noticing what is missing.

A — Accountability

The first question: is there a clear owner, and do they have the authority to act?

The governing insight is blunt: a decision without a clear owner is not a decision, it is a hope. Collective goodwill does not execute; a named role does. In your organization's memory system this is enforced structurally — every Task carries an assigned role, every Decision Candidate carries a decision-maker, every Risk carries an owner. If you cannot answer "which role is accountable for this?" then the proposal is not ready to be consented to. Accountability is not blame; it is the clarity that lets work actually happen.

R — Regeneration

The second question: does this leave the systems it touches better than before? A regenerative decision returns more than it takes across four kinds of system:

• Ecological — does it support or deplete land, water, energy, and living systems?
• Social — does it strengthen or weaken the fabric of trust and belonging?
• Economic — does it build resilience or create dependency?
• Knowledge and institutional memory — does it add to or erode what the organization knows and can inherit?

That last one is easy to forget and easy to violate. A decision made in a side channel, never written down, degrades institutional memory even if it looks efficient in the moment. Regeneration asks you to count that cost.

C — Consent

The third question: did it pass a valid consent process? Consent means the people whose roles are affected had a real opportunity to raise objections; that objections were either integrated or shown to be invalid, not simply overridden; and that the decision was recorded. A decision made without consent is not a governance decision — it is a unilateral action that may later need to be reversed.

Recall the valid-objection standard: an objection counts when it names a concrete way the proposal would prevent someone from fulfilling their role's accountabilities, not merely that they dislike it.

How Sera operationalizes ARC

When Sera extracts governance content from a meeting, email, or transcript, it is quietly running the ARC frame:

• Accountability — Sera captures who owns each action, writing the assigned role onto every task and the decision-maker onto every decision, so ownership is never left implicit.
• Regeneration — Sera flags decisions with regeneration implications as Decision Candidates with canon-impact, routing them to the humans who can weigh the ecological, social, economic, and knowledge effects. Risks to living or social systems are surfaced rather than buried.
• Consent — Sera records decisions as candidates requiring consent, never as confirmed decisions.

Why Sera never completes the Consent step

This is the load-bearing constraint of the whole system. Sera captures, structures, and surfaces — but it never completes the consent step. Only humans can. A machine can note that a decision was proposed, list who is affected, and flag that objections need to be gathered; it cannot legitimately declare that consent was given. Consent is a human act of shared authority, and manufacturing it would hollow out the very thing ARC exists to protect. So every governance artifact Sera produces arrives as Draft, Candidate, or Pending — complete on Accountability and Regeneration, and deliberately waiting for humans on Consent.

Key points

ARC is a three-question lens for any proposal. Accountability: is there a clear owner with the authority to act? A decision without a clear owner is not a decision, it is a hope. Regeneration: does this leave ecological, social, economic, and knowledge/institutional-memory systems better than before? Consent: did it pass a valid consent process where objections could be raised and integrated? Sera operationalizes ARC by capturing who owns each action, flagging decisions with regeneration implications as Decision Candidates with canon-impact, and recording decisions as candidates requiring consent rather than confirmed decisions. Sera never completes the Consent step; only humans can.