build-wiki

<!DOCTYPE html>

A Guide to Contributor Roles - K10 Wiki

A Guide to Contributor Roles

This document outlines the various roles within the K10 development team. Its purpose is to clarify responsibilities and guide contributors in focusing their efforts effectively.

1. Lead Writer

The Lead Writer is responsible for the high-level strategic direction of the project.

Plan Development: Update the development-plan.md to reflect the current state of the repo, remove completed tasks, and set priorities for the next iteration.
Maintain Changelog: Keep changelog.md concise and up-to-date with major changes.
Set Cadence: Decide how often each role should contribute to maintain a healthy development cycle.

2. World Builder

The World Builder focuses on the coherence, integrity, and texture of the K10 universe.

Add Connections: Weave new connections between disparate elements of the world—factions, characters, locations, and historical events.
Ensure Integrity: Add small details that reinforce the established canon and ensure the world feels real and consistent.
Expand Lore: Flesh out cultural details, historical events, and the daily lives of people within the world.

3. Magic System Designer

The Magic System Designer is responsible for the logical consistency and depth of the K10 magic system.

Review and Refine: Continuously review the magic system for clarity, consistency, and logical rigor.
Expand System: Design and document new elements of the system (e.g., new named Cycles, unique magical phenomena) in a way that is detailed, concise, and non-repetitive.
Maintain Balance: Ensure that new additions do not contradict existing rules or create unintended loopholes.

4. Reviewer

The Reviewer acts as an editor and quality control specialist, focused on accessibility and polish.

Simplify Language: Identify and simplify unnecessarily complicated expressions and vocabulary to reduce the learning curve for new readers.
Review writing style: Review documents according to the writing style guide document style-guide.md
Improve Prose: Remove awkward sentences and tighten phrasing to improve readability.
Shorten Text: Condense documents by removing redundant information without losing any details. Information about the magic system and world is prioritized over details about individuals.
Restructure Content: Merge, split, or reorganize files where it would improve the logical flow and navigability of the wiki.

5. Maintainer

The Maintainer is responsible for the technical health and hygiene of the repository.

Link Management: Regularly check documents for broken links and add new contextual links where appropriate to improve discoverability.
Asset Management: Identify which documents lack customized thumbnails and create or assign them.
Address Reports: Monitor reports.md and either fix the reported issues or assign them to the appropriate role.

6. Playtester

The Playtester's role is to engage with the material as a "user" (a writer or reader) and provide structured feedback on its effectiveness. This is the most empirical role, focused on how the system feels in practice.

Playtest Scenario Template

Scenario Title: A brief, descriptive name for the test case (e.g., "A Gevurah mage judges a thief").
Characters Involved: List of characters, their primary paths, and milestone levels.
Core Conflict: What is the central problem the characters must solve using the magic system?
Expected Mechanics: Which specific rules are being tested (e.g., Dissonance, a specific Circulation, a Taint-level corruption)?
Narrative Log: A summary of the story that emerged.
Feedback: Notes from the writer/player about the experience.

Quantitative Metrics to Record

For each playtest, try to track:

Clarity Score (1-5): How easy was it to understand the relevant rules? (1=very confusing, 5=very clear)
Constraint Score (1-5): How much did the rules productively constrain the narrative vs. feeling restrictive? (1=too restrictive, 3=good balance, 5=too loose)
Cool Factor (1-5): How cool and evocative were the resulting magical effects and consequences? (1=boring, 5=awesome)

Open Questions for Writers

Which rules are the most difficult to translate into compelling narrative action?
Are there any gaps in the system? What situations have you encountered where there is no clear rule?
Does the "hard magic" system successfully prevent writers from creating easy solutions to problems?
Is the distinction between the three pillars and their corresponding corruption types clear and meaningful in practice?
Are there any "useless" or "overpowered" abilities that need rebalancing?

7. Single writer

Single writer's role is to write about a single topic or a single document.

Follow development plan: Focus on the on-going task in development plan that is about write new documents or expanding existing one.
Follow writing style guide: Carefully review the style-guide.md and strictly follow it during your writing.
Update development plan: Update the development plan accordingly to the result of your work. Leave suggestions related to results of your work.