This repository has been archived on 2026-05-24. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
AgrarianGameArchive/Docs/KnowledgeAndSkillFoundation.md
T

2.1 KiB

Knowledge And Skill Foundation

Version 0.1.R defines how Agrarian treats knowledge, practice, body condition, tools, and infrastructure before those systems become heavy gameplay code.

MVP Separation Model

Agrarian should not collapse every form of progress into one generic skill number. The MVP separates five related but distinct drivers.

Knowledge:

  • Represents what a character understands.
  • Comes from observation, teaching, notes, mistakes, questions, and practice reflection.
  • Affects judgment, recognition, safety, sequencing, and when warnings appear.
  • Should help players understand why something worked or failed.

Practical experience:

  • Represents practiced execution under real conditions.
  • Comes from repeated action, variation, failed attempts, recovery, and doing the work in different weather, light, terrain, and tool conditions.
  • Affects speed, consistency, yield, precision, and waste.
  • Should grow slowly from use and should not replace core understanding.

Physical stats:

  • Represent the body in the moment: health, stamina, hunger, thirst, body temperature, exhaustion, injury, sickness, age, carry load, and care history.
  • Affect what a character can safely do right now.
  • Should create readable pressure without becoming a hidden knowledge system.

Tools:

  • Represent external capability the player can hold, equip, place, or maintain.
  • Affect what actions are possible, how safe they are, how much effort they require, and how good the result can be.
  • Should still require knowledge and practice for best outcomes.

Infrastructure:

  • Represents durable world improvements such as shelter, storage, paths, wells, fields, workshops, firebreaks, and community systems.
  • Affects baseline safety, efficiency, capacity, and resilience.
  • Should reduce routine survival pressure without removing consequences from poor choices.

MVP rule: basic survival actions must remain possible with low knowledge and poor tools, but outcomes should be riskier, slower, lower quality, or more wasteful until knowledge, practice, tools, and infrastructure improve.