docs: design proposal for YAML-driven cost calculator#4
Draft
docs: design proposal for YAML-driven cost calculator#4
Conversation
Co-authored-by: gvegayon <893619+gvegayon@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add design proposal for YAML and report structure
docs: design proposal for YAML-driven cost calculator
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
docs/design-proposal.mdas the formal response to Discussion #2, establishing the architecture for the next development stage of the cost calculator.YAML model file spec
Four top-level sections per model file:
Key design choices:
parameters[].namedoubles as the Python identifier injected into equation expressionsequations[].equationis a plain Python expression string evaluated at runtime; equations may compose each other via theiridtable.scenarios[].variablesinjects free variables (e.g.n_cases) not covered by parameters, enabling multi-column outbreak-size comparisons from a single equation setReport structure spec
Standardises output as an ordered
sectionslist consumed by the existingrender_sectionsrenderer:output_type(integer/double)parameters[](name, current value, unit, description, references)parameters[].referencesWorkflows (Mermaid)
Two flowcharts covering the full lifecycle:
yaml.safe_load→ section extraction → sidebar widget construction + equation registry → session staterender_sections→ guardrail warnings for out-of-bounds values💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.