fidelity-writing

name	fidelity-writing
description	Write, revise, outline, or review The Fidelity Framework content. Use when Codex is working in the fidelity-framework repo or asked to draft or edit Fidelity chapters, trustworthy love and loyalty prose, sexuality/family/friendship/boundary content, relational repair standards, or consistency with Ethosism house style.

Fidelity Writing

Core Workflow

When working in the Fidelity 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 Fidelity Framework as a secular, non-theological companion to Ethosism for trustworthy bonds. Ground claims in:

• Objective reality: what relational patterns actually produce in trust, safety, dignity, agency, care, and responsibility.
• Reciprocity: whether love, loyalty, boundaries, sexuality, forgiveness, and repair remain fair under role reversal.
• Integrity: whether words, promises, boundaries, sexual conduct, money, attention, and repair align.
• Trust: whether conduct makes a person safer to rely on over time.
• Boundaries: whether care protects dignity and agency instead of becoming control, indulgence, secrecy, or self-erasure.
• Repair: whether betrayal, neglect, coercion, abandonment, immaturity, or harm is corrected truthfully.
• Long-term responsibility: whether the bond 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, purity ideology, sexual libertinism, or any single theology.

Drafting Chapters

For new chapter drafts:

1. Define the relational domain and why it matters.
2. Name the common failure mode.
3. State the Fidelity standard for the domain.
4. Show why the standard follows from reality, reciprocity, integrity, trust, boundaries, repair, and endurance.
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, dating-hack language, vague relationship inspiration, self-help hype, therapy language detached from conduct, academic abstraction, partisan signaling, purity panic, sexual license, or sermon-like intensity.

Revising Chapters

For edits to existing prose:

• Preserve the author's core claim unless asked to rethink it.
• Tighten vague inspiration into concrete standards.
• Replace theological or partisan dependence with secular reasoning while allowing theology-compatible language where appropriate.
• Make unsupported claims explain conduct, power, consent, consequence, reciprocity, trust, boundaries, repair, and long-term endurance.
• Calibrate empirical claims to the evidence, especially in chapters about sexuality, attachment, trauma, marriage, abuse, family, technology, or development.
• 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, purity panic, sexual license, or culture-war shorthand.
• Moral claims asserted without reality, reciprocity, or trust arguments.
• Contradictions with boundaries, repair, consent, protection of the vulnerable, or long-term fidelity.
• Advice that rewards exploitation, coercion, betrayal, abandonment, secrecy, cruelty, evasion, enabling, or self-erasure.
• Tone drift into marketing, hype, vague inspiration, 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: "Fidelity Writing" short_description: "Guide Fidelity Framework drafting and revision" default_prompt: "Use $fidelity-writing to revise this Fidelity chapter for trustworthy bonds and relational repair clarity."