Chief Writing Officer (Volunteer)

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate. We need to parse the posting: It's a volunteer role Chief Writing Officer (Volunteer) at Mentor A Promise, PromisePages division. It includes many details: location fully remote US, type volunteer, commitment approx 5-10 hrs/week, minimum commitment 6 months; 12 months preferred. Reports to CEO. Leads PromisePages directly oversees Senior Director of PromisePages, Writing Directors, Editors, Writers, designated literary teams. Works closely with other divisions. Then sections: About Mentor A Promise, About PromisePages, Role Overview, Creative Writing Vision, Literary Development, Story Development, Writers & Creative Talent, Editorial Development, Children's & Youth Literature, Youth Voice & Creative Participation, Originality & Creative Integrity, Literary Portfolio Leadership, Cross-Divisional Storytelling, Intellectual Property & Creative Rights, Ethical Storytelling, PromisePages Leadership, Executive Leadership Expectations, First-Year Priorities, Qualifications. We need to map to headings: About the role (maybe role overview?), Responsibilities (list duties), Requirements (maybe qualifications?), Qualifications (maybe skills?), Skills, Benefits, Pay, Schedule. We must not create sections with placeholder text. So we need to extract actual content for each. Let's identify: - About the role: Could be the "Role Overview" paragraph: "MAP is seeking an exceptional Chief Writing Officer to lead PromisePages and serve as the organization's senior creative executive for literary and written storytelling. The Chief Writing Officer establishes the creative vision for PromisePages, develops its writers and editors, oversees its portfolio of literary projects, strengthens storytelling and editorial quality, and builds the systems necessary to move original ideas from concept to completed work. The CWO should be equally comfortable discussing the emotional arc of a character, the structure of a manuscript, the development of an emerging writer, and the long-term creative direction of an entire literary division. The central question is What stories should MAP help bring into the world—and how do we tell them exceptionally well?" That's substantive. - Responsibilities: Could be the bullet-like lists under sections: Creative Writing Vision, Literary Development, Story Development, Writers & Creative Talent, Editorial Development, Children's & Youth Literature, Youth Voice & Creative Participation, Originality & Creative Integrity, Literary Portfolio Leadership, Cross-Divisional Storytelling, Intellectual Property & Creative Rights, Ethical Storytelling, PromisePages Leadership, Executive Leadership Expectations, First-Year Priorities. Many of these are responsibilities. We need to put them in

• . We must preserve all substantive info, not summarize away detail. But we can combine similar items? The instruction: "Prefer a few substantive sections over many thin ones." So we could group responsibilities into a single Responsibilities section with many list items covering all those bullet points. Must not invent or summarize away detail: we need to keep the substance but can condense? The instruction says "do NOT invent or summarize away detail." Summarizing away detail might be considered removing detail. We need to preserve all substantive information. That suggests we should not omit any details; we need to keep them as is. However we can still put them as list items; each bullet can be a sentence or phrase from the original. We must not create filler like "commensurate with experience". So we need to extract each distinct responsibility statement. Let's list responsibilities from the text: From Creative Writing Vision: "Establish the creative and literary vision for PromisePages. Develop standards and direction for Storytelling Narrative development Character Voice Dialogue Worldbuilding Structure Pacing Theme Tone Genre Audience Literary quality Originality Emotional authenticity". That's a long sentence; we can break into list items maybe each phrase? But we need to preserve detail; we could keep as one list item: "Establish the creative and literary vision for PromisePages; develop standards and direction for storytelling, narrative development, character, voice, dialogue, worldbuilding, structure, pacing, theme, tone, genre, audience, literary quality, originality, emotional authenticity." Literary Development: "Lead the development of original literary projects, which may include Children's books Picture books Middle-grade stories Young adult concepts Short stories Poetry Graphic narratives Creative nonfiction Scripts Serialized storytelling Digital stories Experimental literary projects Help determine which concepts should advance and what development they require. Not every good idea needs to become a book. Strong creative leadership knows which ideas deserve deeper development." Story Development: "Guide projects through a disciplined creative process Idea → Concept → Audience → Story Development → Outline → Draft → Editorial Review → Revision → Final Manuscript → Production Ask the questions that make stories stronger Who is this story about? What does the character want? What stands in the way? Why should the reader care? What changes? What is the emotional journey? What is the story really about beneath the plot? What should remain with the reader after the final page?" Writers & Creative Talent: "Build and develop an exceptional community of writers. Responsibilities include Recruit writers. Identify emerging creative talent. Assign writers to appropriate projects. Mentor developing writers. Support experienced writers. Create constructive critique practices. Establish writing workshops. Develop writing teams. Encourage experimentation. Build future literary leaders. Create pathways for writers to take increasing ownership. The Chief Writing Officer should not become the person who writes every important story. The Chief should build a division full of people capable of writing extraordinary ones." Editorial Development: "Work closely with PromisePages editorial leadership to strengthen manuscripts without erasing the writer's voice. Guide developmental editing involving Story structure Character development Narrative arc Theme Pacing Dialogue Point of view Continuity Worldbuilding Emotional clarity Audience appropriateness Overall manuscript development Editing should help a writer discover the strongest version of their story—not turn the story into the editor's." Children's & Youth Literature: "Help PromisePages develop writing that respects the intelligence, imagination, complexity, and emotional lives of young readers. Stories for children should not automatically become lectures disguised as fiction. Young readers deserve Interesting characters Humor Adventure Mystery Imagination Emotion Wonder Conflict Discovery Joy Complexity A story may carry meaning without announcing its lesson on every page." Youth Voice & Creative Participation: "Explore appropriate opportunities for young people to participate in creative writing and storytelling. This may include Writing workshops Poetry Story development Youth publications Creative prompts Collaborative projects Youth-authored work Writing mentorship Literary showcases Youth participation must follow MAP's safeguarding, privacy, consent, and intellectual-property standards. Young people's voices should not simply decorate adult-created projects. When young people are invited to create, their contribution should be respected as creative work." Originality & Creative Integrity: "Build a culture where PromisePages develops original work rather than imitating whatever is currently popular. Writers should understand genre and audience expectations without becoming trapped by them. The Chief should encourage teams to ask What have we seen before? What feels predictable? What perspective is missing? What makes this story ours? Why does this story need to exist? The goal is not originality for originality's sake. It is storytelling with a reason to exist." Literary Portfolio Leadership: "Oversee PromisePages' portfolio of projects. Establish clear stages such as Concept → Development → Writing → Editorial → Revision → Approved Manuscript → Production → Publication / Release Maintain visibility into Active manuscripts Writers and editors Development stage Creative decisions Dependencies Deadlines Revision status Production readiness Creative freedom and accountability can coexist." Cross-Divisional Storytelling: "PromisePages stories may become larger creative worlds. Collaborate with PromiseStudios and other creative divisions when appropriate on adaptations involving Animation Film Audio Podcasts Illustration Graphic storytelling Music Voice performance Interactive media Digital experiences A story may begin on a page without having to remain there. The written work, however, should be strong enough to stand on its own before adaptation becomes the goal." Intellectual Property & Creative Rights: "Work with PromiseTrust and appropriate MAP leadership to ensure literary projects follow established requirements involving Copyright Authorship Contributor agreements Intellectual property Licensing Adaptation rights Third-party materials Releases Publication rights Youth-created work Creative collaboration should begin with clarity about ownership rather than waiting until a successful project makes ownership important." Ethical Storytelling: "PromisePages may explore difficult experiences, including housing instability, family, identity, belonging, hardship, resilience, and community. Stories should never reduce people to circumstances. MAP should not create fictional or nonfictional narratives that exploit hardship simply because hardship creates emotional intensity. Dignity should survive the editing process." PromisePages Leadership: "Build PromisePages as a genuine creative institution. Responsibilities include Establish division strategy. Recruit creative leaders. Develop directors and editors. Build writing teams. Establish creative standards. Create development processes. Set quarterly priorities. Review major literary projects. Resolve creative barriers. Strengthen collaboration. Develop future leadership. Maintain accountability for projects through completion. The CWO should build systems strong enough for creativity to flourish without requiring the Chief to control every creative decision." Executive Leadership Expectations: "As a MAP Chief, the Chief Writing Officer is expected to Participate consistently in weekly Chiefs meetings. Meet regularly with the CEO. Own PromisePages strategy and performance. Establish quarterly priorities and measurable milestones. Communicate consistently with PromisePages leadership. Recruit, develop, and retain creative talent. Follow through on commitments. Collaborate constructively with fellow Chiefs. Protect creative integrity. Respect safeguarding and intellectual-property requirements. Model curiosity, imagination, accountability, humility, and excellent creative judgment. Executive creative leadership is not about having the most ideas in the room. It is about creating an environment where the strongest ideas can emerge from anyone in it." First-Year Priorities: "The Chief Writing Officer should help establish PromisePages' creative vision. A clear literary development pipeline. Writing and editorial standards. A portfolio of original literary projects. Manuscript development workflows. Writing workshops and critique structures. Writer recruitment and development systems. Youth-writing opportunities where appropriate. Creative project tracking. Intellectual-property coordination. Cross-divisional adaptation pathways. A strong PromisePages leadership team. The goal is to build more than a collection of writing projects. It is to build a literary division." Now Qualifications: The posting includes "Qualifications Strong candidates may have experience in Creative writing Children's literature Fiction Poetry Publishing Literary development Developmental editing Screenwriting Story development Editorial leadership Creative leadership Candidates should demonstrate Exceptional storytelling instincts. Strong writing and editing ability. Understanding of narrative structure and character. Ability to develop writers without erasing their voices. Strong creative judgment. Experience managing multiple creative projects. Ability to give thou" (cut off). We need to preserve as is; it's cut off but we must keep what's there. Probably the text ended abruptly; we keep it. Skills: Not explicitly listed separate; maybe qualifications cover skills. But we could create Skills section if there is explicit skill list. There's "Ability to give thou" incomplete. Might be "Ability to give thoughtful feedback"? Not sure. We'll not invent. Benefits: Not mentioned (volunteer). No benefits described. So we should not create Benefits section. Pay: Not mentioned (volunteer). No pay. So no Pay section. Schedule: It mentions commitment approx 5-10 hours per week, minimum commitment 6 months; 12 months preferred. That's schedule info. So we can create a Schedule section with that detail. Also location: Fully Remote — United States, with NYC collaboration as needed. That could be part of About the role or maybe a separate section? Not in headings list; we could fold into About the role paragraph. We must not repeat job title as heading. So we will not have heading "Chief Writing Officer". We'll use headings: About the role, Responsibilities, Requirements?, Qualifications, Skills?, Schedule. Requirements maybe we can treat as qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Requirements if there is specific content. The posting includes qualifications but not separate "Requirements". Could treat qualifications as Requirements. But we have both Qualifications and Requirements headings; we need to decide. Since there is a Qualifications section in the posting, we can map that to