vocation-writing

name	vocation-writing
description	Write, revise, outline, or review The Vocation Framework content. Use when Codex is working in the vocation-framework repo or asked to draft or edit Vocation chapters, useful-work moral framework prose, craft/enterprise/professional ethics content, livelihood and contribution standards, or consistency with Ethosism house style.

Vocation Writing

Core Workflow

When working in the Vocation 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 Vocation Framework as a secular, non-theological companion to Ethosism for useful work and durable contribution. Ground claims in:

• Objective reality: what the work actually produces, costs, repairs, improves, or damages.
• Usefulness: whether real people are served by real value rather than image, status, or performance.
• Craft: whether competence, quality, standards, and care are built into the work.
• Reciprocity: whether the work remains fair from the customer's, worker's, teammate's, apprentice's, maintainer's, or future person's position.
• Integrity: whether promises, incentives, products, reputation, and behavior align.
• Stewardship: whether talent, tools, money, time, teams, opportunity, and authority are handled responsibly.
• Long-term responsibility: whether the work 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, or any single theology.

Drafting Chapters

For new chapter drafts:

1. Define the work domain and why it matters.
2. Name the common failure mode.
3. State the Vocation standard for the domain.
4. Show why the standard follows from usefulness, craft, reciprocity, integrity, stewardship, and long-term responsibility.
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, generic career advice, self-help hype, hustle culture, corporate language, academic abstraction, partisan signaling, 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 usefulness, consequences, reciprocity, craft, integrity, stewardship, and long-term contribution.
• Calibrate empirical claims to the evidence, especially in chapters about markets, entrepreneurship, technology, management, labor, psychology, or education.
• 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, or culture-war shorthand.
• Moral claims asserted without usefulness, reality, or reciprocity arguments.
• Contradictions with craft, integrity, stewardship, or contribution.
• Advice that rewards vanity, exploitation, burnout, laziness, dishonest marketing, or short-term extraction.
• 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: "Vocation Writing" short_description: "Guide Vocation Framework drafting and revision" default_prompt: "Use $vocation-writing to revise this Vocation chapter for useful-work moral clarity and house style."