Current phase: Release Preparation
This repository is a public-facing research archive for Rune Factory 4 Special / Rune Factory 5 observation-based mechanics research.
The current task is repository synchronization and navigation documentation, not redesign.
README.md
ROADMAP.md
articles/
csv/
images/
mermaid/
pdf/
research/
ルンファク（全部入り文字列検索可）/
The physical structure is intentionally relatively flat.
Logical relationships are expressed through Markdown links and navigation documents.
For this staging migration, the current observation labels are Equipment-Body Candidateization and Internal Arrangement Reference. Self-Contamination.md and Recursive-Processing.md remain physical historical filenames. The former labels “Self Contamination,” “Performance-Source Contamination,” and “Recursive Processing” describe historical terminology or models; no recursive expansion sequence is confirmed by these observations. “First Same-Category Internal-Arrangement Reference” is a current observed conditional behavioral rule under tested multiple-same-category and input-order conditions, nested under the broader observation. Its internal cause remains unknown; first-match scanning, category traversal, and base selection are not confirmed. Unknown transitions remain unknown rather than being replaced with a new mechanism. Candidate Count Model remains the research framework; the affected candidate-generation account is the part being corrected.
Candidate Count Model
├── Auto Arrange
├── Equipment-Body Candidateization (current observation; historical article filename)
├── Internal Arrangement Reference (broad current observation; historical article filename)
│ └── First Same-Category Internal-Arrangement Reference (observed conditional rule)
├── Success Probability
└── Light Ore Inheritance
Efficient Friendship Farming Strategy
├── RF5 Daily Friendship Farming Guide
├── RF4SP Daily Friendship Farming Guide
├── Triple Gift Mechanics
└── The Hidden Cost of Shipping Everything
The primary purpose of the repository is preservation and transmission of knowledge.
Architecture exists to support knowledge, not to replace it.
Once publication quality has been achieved, preserving repository stability takes precedence over pursuing structural perfection.
A stable repository that readers can reliably access and reproduce is more valuable than a perfectly organized repository that remains unpublished.
Preserve first.
Release second.
Refactor in the next cycle.