CORE_LOGIC
Summary
Cassowary World systems must satisfy explicit causal dependencies: biology shapes behavior, behavior enables technology, technology requires infrastructure, and infrastructure can support institutions. Preservation implies containers and storage practices; surplus implies measurement and authority rules; trade implies maintained routes and exchange institutions; domestication requires a prior ecological or behavioral bridge; timeline claims must not introduce systems before their prerequisites exist.
Purpose
Use this file to test whether a claimed system implies other systems that must also exist, be deferred, or be marked as open questions.
Core Causal Rules
- Biology -> behavior -> technology -> infrastructure -> institutions
- Preservation capacity implies storage media, containers, and handling practices.
- Stored surplus at scale implies measurement, allocation, and ownership/authority rules.
- Long-distance trade implies transport routes, transport maintenance, and exchange institutions.
- Durable settlements imply recurring energy supply, risk management, and intergenerational knowledge transfer.
- Domestication claims must build on a preexisting ecological or behavioral bridge.
- Timeline claims must not introduce downstream institutions before enabling systems exist.
Document Authoring Implications
When a technical document introduces a system, contributors should check:
- What does this system depend on?
- What systems does this make possible?
- What timeline window is minimally plausible?
- Which implied systems are missing and need placeholders or open questions?
Current Gaps Flagged During Repository Restructure
- Orchard lineage management and propagation details
- Aphid domestication/stabilization as a distinct ecological system
- Storage container and ceramic standardization
- Tribute/taxation institutional mechanisms
- Transport network infrastructure and maintenance
Open Questions
- Which systems are required before a first coherent timeline pass can move beyond placeholders?
- How should preservation and storage milestones be placed relative to early tribute systems?
- Which generated validation warnings should become errors after existing docs are cleaned up?