AetheriaLore/AGENTS.md
2026-04-18 15:57:19 +01:00

4.3 KiB

AGENTS.md

Purpose

This repository is an Obsidian vault for the Aetheria setting. Contributions should preserve it as a coherent worldbuilding knowledge base rather than treating it like generic prose storage.

Project Conventions

  • Prefer Markdown notes organized by setting domain, era, faction, technology, concept, species, or timeline event.
  • Keep files in the existing folder hierarchy unless there is a strong structural reason to introduce a new branch.
  • Name notes in Title Case, usually matching the in-universe proper noun or concept exactly.
  • Preserve Obsidian-style wiki links such as [[Aether]], [[Timeline]], and [[Pan-Solar Consortium]].
  • Favor creating or strengthening links between notes over repeating the same explanation in multiple places.
  • Avoid YAML frontmatter unless the repository begins using it consistently in the future.

Writing Style

  • Write in clear, polished Markdown prose.
  • Default to a serious, analytical, high-concept science-fantasy / science-fiction voice.
  • Treat the setting as materially grounded: economics, ideology, infrastructure, labor, warfare, governance, class power, and technological constraints should feel causally connected.
  • Keep speculative elements legible by anchoring them in social, political, or physical consequences.
  • Use vivid phrasing when appropriate, but avoid empty flourish that does not add setting information, mood, or ideological texture.
  • Maintain internal consistency with existing terminology, institutions, factions, and timeline beats.

Tone

  • The project's dominant tone is sober, reflective, and politically aware.
  • Many notes frame technology and institutions in terms of incentives, domination, exploitation, regulation, resistance, and material tradeoffs. Preserve that lens.
  • When expanding factions or concepts, avoid flattening them into pure heroes, villains, or aesthetic stereotypes. Emphasize tensions, contradictions, and historical pressures.
  • Keep the writing attentive to how systems shape lived experience, not just to spectacle or lore trivia.

Note Structure

  • Match the local structure of neighboring notes before introducing a new pattern.
  • Many notes begin with a short orienting paragraph, while others begin with a heading such as ### <Topic>. Either is acceptable if used intentionally.
  • Use short thematic sections with Markdown headings when a note benefits from subdivision.
  • Timeline and index notes should stay scannable, with compact summaries and linked entries.
  • Faction, technology, and concept notes should explain what the subject is, how it functions, who it affects, and why it matters in the broader setting.
  • Prefer concise paragraphs over oversized blocks when clarity would benefit.

Content Expectations

  • New material should deepen the setting rather than merely decorate it.
  • Ask of each addition: what pressures produced this, who benefits, who is constrained, what contradictions does it create, and how does it interact with other parts of the setting?
  • Be mindful of continuity across Pre-Elysium, Post-Elysium, politics, technology, and factional history.
  • When possible, connect abstract concepts to institutions, everyday life, and conflict.

Cultural And Historical Guidance

  • Always be mindful of the societal and cultural impact of technology.
  • Always be mindful of the historical dialectic: institutions, ideologies, and technologies should be understood as emerging from conflict, material conditions, and changing power relations.
  • Treat technological change as socially embedded, not neutral or autonomous.
  • Consider how class, labor, governance, identity, colonial dynamics, media, and infrastructure mediate the effects of any technology or social system added to the setting.
  • Prefer writing that reveals contradiction, contingency, and historical development over writing that treats the world as static.

Editing Guidance For Future Agents

  • Read adjacent notes before making substantial additions so new material matches local vocabulary and structure.
  • Preserve existing links and add new ones where they genuinely improve navigation.
  • Do not remove ambiguity or tension unless the note is clearly meant to resolve a question.
  • If you encounter malformed characters from prior encoding issues, fix them carefully and only where you can do so confidently without changing meaning.