governance-writing

name	governance-writing
description	Write, revise, outline, or review The Governance Framework content. Use when Codex is working in the governance-framework repo or asked to draft or edit Governance chapters, citizenship/representation/policy/administration prose, public trust/accountability/constraint content, or consistency with Ethosism house style.

Governance Writing

Core Workflow

When working in the Governance Framework repo, first read the available guidance in this order:

1. agents.md for the repo goal and agent-level direction.
2. docs/writing-guide.md for the moral method, voice, chapter pattern, and consistency checks.
3. chapters/00-introduction.md and any chapters adjacent to the requested topic for house style.
4. src/LINEAR-FRAMEWORK.md when the task involves sequence, phases, curriculum structure, or operating cadence.

If the repo root is unclear, locate it by finding a project with README.md, chapters/, and docs/writing-guide.md.

Writing Standard

Treat the Governance Framework as a secular, non-theological companion to Ethosism for legitimate public decision-making. Ground claims in:

• Objective reality: what public problem exists, what evidence supports it, what tradeoffs follow, and what capacity is available.
• Reciprocity: whether rules remain fair under role reversal among majority, minority, taxpayer, dependent, official, dissenter, outsider, and future citizen.
• Public trust: whether authority is exercised as a duty for affected people rather than private possession.
• Constraint: whether power is limited by law, rights, procedure, transparency, budgets, review, and accountability.
• Competence: whether institutions can actually administer what they promise.
• Long-term responsibility: whether the governance pattern remains defensible across years, decades, and generations.

Keep the framework usable by atheists, agnostics, and religious readers. Do not make the argument depend on divine command, scripture, clergy, afterlife, karma, supernatural reward, partisan loyalty, revolutionary romance, technocratic authority, or any single theology.

Drafting Chapters

For new chapter drafts:

1. Define the governance domain and why it matters.
2. Name the common failure mode.
3. State the Governance standard for the domain.
4. Show why the standard follows from reality, reciprocity, public trust, constraint, competence, accountability, and inheritance.
5. Address tradeoffs, edge cases, or predictable objections.
6. End with a concise behavioral expectation or decision standard.
7. For domain chapters, include a practice section or equivalent concrete application.

Use clear essay prose. Prefer concrete claims and practical judgment over slogans, partisan commentary, electioneering, anti-politics cynicism, bureaucratic excuse-making, technocratic control, populist theater, academic abstraction, or sermon-like intensity.

Revising Chapters

For edits to existing prose:

• Preserve the author's core claim unless asked to rethink it.
• Tighten vague civic language into concrete standards.
• Replace theological or partisan dependence with secular reasoning while allowing theology-compatible language where appropriate.
• Make unsupported claims explain evidence, authority, tradeoffs, budgets, incentives, administrative capacity, reciprocity, rights, and long-term public trust.
• Calibrate empirical claims to the evidence, especially in chapters about elections, taxation, budgets, administration, regulation, technology, emergencies, or foreign policy.
• Preserve or add practical application so the reader can turn the chapter into behavior, not only agreement.
• Keep the manuscript voice sober, direct, morally serious, and adult.

Reviewing Chapters

For review-only requests, lead with the highest-impact issues:

• Theological dependence, partisan framing, technocratic authority, revolutionary romance, anti-politics cynicism, or culture-war shorthand.
• Moral claims asserted without evidence, reality, reciprocity, authority, or constraint arguments.
• Contradictions with public trust, competence, transparency, accountability, rights, budgets, or long-term inheritance.
• Advice that rewards corruption, capture, incompetence, fiscal evasion, rights violations, public disorder, or institutional abdication.
• Tone drift into marketing, hype, vague civic language, or academic abstraction.

Give file and line references when reviewing local files. Keep suggested rewrites short unless the user asks for a full rewrite.

interface: display_name: "Governance Writing" short_description: "Guide Governance Framework drafting and revision" default_prompt: "Use $governance-writing to revise this Governance chapter for public trust, accountability, constraint, and institutional competence."