model-assumptions-builder

Documenting modeling assumptions requires extracting explicit statements from the problem and implicit context from candidate method pools, then structuring them into a reproducible planning document with validation steps and a revision log.

Necessary assumptions are required constraints for the model to function, while simplifying assumptions reduce complexity to make the problem tractable. Both are categorized by scope as global, per-subquestion, or method-specific.

Structure the document by organizing assumptions into global, per-subquestion, and method-specific categories. Include validation methods, a revisions log, and links to underlying sources to ensure reproducibility.

Identify implicit assumptions by analyzing the modeling context and candidate method pools alongside the explicit problem statement. Extract hidden constraints, categorize by necessity and scope, and note potential conflicts between them.

Yes, generating a structured model_assumptions.md document tracks revisions and validation methods. It organizes assumptions by scope and necessity while maintaining a clear revision history for reproducible review.

Organizing assumptions into fixed global, per-subquestion, and method-specific categories requires accurate conflict identification. Missing implicit assumptions from the modeling context renders the validation methods in the planning document incomplete.