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.

[Unreleased]

[1.2.3] - 2026-07-29

Added

• Added explicit normative-pattern, illustrative-reference, and project-adoption semantics.
• Added normative attribute declaration, immutable value commitment, parent-graybox-to-child-blackbox, analysis placement, and whitebox observation rules.
• Added machine-readable evidence classification, source kind, project acceptance eligibility, and tailoring requirements.
• Added a publishable project adoption and tailoring checklist plus a guided learning path to README.
• Added automated RAWP conformance checks and continuous validation workflow.
• Added reusable requirements-traceability concern, viewpoint, and view definitions plus level-specific SEIT roles at L0/L1, PIT roles at L2, and PDT roles at L3. Each role holds a framed traceability concern; it does not own requirements or architecture elements.
• Added complete textual trace-chain exposure to each L0-L3 requirements-traceability view, including received needs, transformed and derived requirements, contextual satisfaction usages, and verification cases.
• Added README guidance for reading the trace chain without introducing redundant dependency relationships.

Changed

• Renamed MyStandard::myStandardComplyingPart to MyStandard::myStandardConstrainedPart so subsetting denotes contractual applicability and an obligation awaiting verification, rather than compliance proven by type.
• Clarified the standard-responsibility pattern: the SuperSystem integration organization frames the applicability concern in each provider need and inspects the contractual handoff, while each provider's system SEIT transforms the need, analyzes the inherited blackbox obligation, derives realization requirements, and analyzes the original boundary claim at whitebox.
• Corrected the L1 and decomposed L2 requirement chains so each graybox-derived requirement subsets its own transformed blackbox requirement rather than remaining a sibling that independently subsets the parent need.
• Added explicit contextual L0 satisfaction claims for both provider needs so the contractual-handoff inspection has a machine-readable verification target.
• Separated the standard contractual-handoff requirement from numerical payload-performance needs; the performance needs inherit the dedicated provider-contract needs, so inspection does not imply performance verification.
• Renamed the remaining standard requirement terminology from “complying element” to “constrained element.”
• Added an explicit L1 requirement transformation and terminal boundary-analysis template for the InteractingSystem provider branch.
• Reframed the L0 MyStandard verification as a contractual-handoff inspection and made the System-of-Interest compliance case an analysis of the inherited standard satisfaction claim on systemOfInterest_wb.
• Changed reusable verification and inspection verdicts from unconditional pass to safe reference-mode inconclusive.
• Classified synthetic analysis records as illustrative and removed claims to an unretained result artifact.
• Bound standard compliance qualityGain to each L1 operational element's realized qualityContribution.
• Aligned all decomposed levels on constraint-based allocation closure without rebinding realized contribution.
• Moved design-dependent capability assignments from decomposed blackboxes to their grayboxes, where decomposition analysis makes those values available.
• Replaced terminal capability values copied from normative needs with independent illustrative supplier or component-design seeds.
• Removed analysis-only strain and adjusted-contribution values from canonical configurations and kept scenario-dependent values in analysis cases.
• Standardized the product name as Recursive Architecture Wave Pattern and reconciled the guide, verification baseline, and benchmark matrix.
• Prepared the corrective release as version 1.2.3; publication remains a separately gated action.

[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.