Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[1.2.2] - 2026-07-24

Changed

• Corrected the analysis-to-requirement derivation direction for the main recursive allocation chain (L0, L1, L2 Subsystem1): sensitivity-analysis usages now expose selected allocation outputs, tagged with a new AnalysisExecutionProvenance metadata def, and requirement budget attributes bind to those outputs instead of hardcoded literals. Degradation and trade-study analyses remain decision-support only by design; documented explicitly at each affected budget attribute.
• Verification objectives across all levels now verify a local satisfy feature declared on the whitebox (or highest-available) configuration subject rather than the external requirement definition directly, with whitebox parts redefining the same named satisfy usage a graybox declares, keeping the satisfaction claim continuous across box levels.
• Clarified the scope of MyStandard compliance to the L1 operational-element boundary (the parts that interact with each other at the L0 operational level), matching how service/interface standards -- and the MOSA principle -- govern boundaries, not internal subsystem/component design. Not a recursive decomposition: a single fixed constraint asserted once at the boundary, contrasted explicitly with budget-derived requirements in a new STANDARDS PATTERN RULES block.
• Fixed 3 of 16 related-feature-conformance warnings at L0 by dual-subsetting mySystemOfInterest/myInteractingSystem under MyOperationalOntology ::operationalPerformers. Remaining warnings trace to the provisional operational/system ontology split and are deferred to a planned UAFv2 integration.
• Updated syside dependency and the Syside Views sysand library dependency to 0.10.3.

Added

• Documented that the centralized license declaration in Credits.sysml follows the spirit of the REUSE/SPDX convention (SPDX license identifier, LICENSES/ <SPDX-identifier>.txt naming, per-file headers reserved for vendored third-party content whose license differs), via a new conventionReference attribute.

[1.2.1] - 2026-07-13

Changed

• Updated README logo reference to a tag-pinned external URL for Sysand package rendering compatibility with md/sysml-only payload constraints.
• Bumped project version metadata to 1.2.1 for release validation.

[1.2.0] - 2026-07-13

Added

• Added framework-level value provenance glossary terms (normativeTarget, executableSeed, computedResult, observedEvidence) to standardize interpretation of model values.
• Added analysis role policy clarifying that analysis in RAWP is decision-support evidence and not empirical proof of realized-system capability.
• Added cross-level policy pointers in analysis and verification packages to reinforce the analysis-vs-empirical-evidence boundary.
• Added SysMLv2-specification-limitation note in framework semantics and root package documentation.

Changed

• Refactored recursive quality semantics to explicit one-way causality (capability seed -> behavioral transformation -> realized contribution) across decomposition levels.
• Propagated capability-setting and realized-contribution pattern through L1/L2/L3 branches while keeping qualityContribution compatibility aliasing for requirement continuity.
• Rebased selected derived-allocation values on stakeholder concern envelope attributes to improve provenance and reduce circular-looking derivation patterns.
• Added seeded exemplar analysis scenarios at L0/L1/L2 for non-circular demonstration inputs.
• Updated README to a current-state, history-neutral release posture and aligned it with the new causality/provenance/policy semantics.

Notes

• Static model validity remains intact under current SysML checks.
• Full numeric execution for some typed value-resolution/arithmetic combinations remains subject to current SysMLv2 specification maturity and is retained as semantic intent.

[1.1.4] - 2026-07-06

Changed

• Implemented secured release automation for private repositories using token-based Sysand publishing in CI (environment-scoped secret) and aligned release workflow hardening.

[1.1.2] - 2026-06-25

Changed

• Refined analysis-case semantics to remove verify usage from analysis objectives and align objective intent with assume/require constraints.
• Explicitly redefined inherited analysis objectives and inherited parent constraints in specializations.
• Clarified and stabilized return feature redefinitions across operational, system-of-interest, and subsystem analysis cases.
• Harmonized analysis subject and parameter declarations to match parent-feature inheritance behavior used in this baseline.

[1.1.1] - 2026-06-10

Changed

• Reworked README into a standalone, publish-ready guide so KPAR consumers can use the package documentation without additional markdown files.
• Added a dedicated analysis section that captures analysis intent, policy, and expected outcomes across decomposition levels.
• Removed environment-specific validation script instructions from README.

[1.1.0] - 2026-06-10

Added

• Layered interface source attribution for P. Shames, M. Sarrel, and S. Friedenthal in Credits metadata.

Changed

• Updated project README to reflect the current model architecture including Framework semantics and stack port guidance.
• Documented current validation workflow and model navigation for the recursive pattern baseline.

[1.0.1] - 2026-06-02

Added

• Initial changelog entry for version 1.0.1.