Starters
No --template
memo-architect init copies the one skeleton the ontology's manifest names, and --example <id> starts from a copy of an example. --template and the template list in init --list are gone.
Commands
memo and memo-architect split
memo compiles, validates, packs and checks the toolchain; everything else, including init, is memo-architect. A retired command exits with an error naming its replacement. memo package is replaced by memo pack (a SysAnd KPAR) and memo-architect import kpar.
Commands
One verb to create a thing
memo-architect new package|requirement|rule|kind|plugin replaces create-package, req new, rules new, ontology add-kind and plugin create. The flags are unchanged except req new --template, which is new requirement --pattern. memo-architect sysand publish (a dry run) is memo publish. Each old name fails naming its replacement for one release.
Settings
The project names its compiler
A project names its compiler with toolchain.compiler. A person overrides it for themselves in their user settings; tool paths are found automatically and are rejected in a checked-in project file.
Rules
Rules read the new trace
The loader reads #EnforcesClause dependencies. Ontology 0.13.x and earlier, which use ref enforces, no longer show clause traces.
Rules
Filter by obligation
memo validate --rules --rules-obligation required lists the rules of one obligation; new rule --obligation and --enforces write the new forms.
Performance
Faster edits, a smaller handoff
Stage 1 converts only the documents an edit reached and stores them compressed. With OpenSysML 0.10.0 or later, the compact API JSON format is used where the service offers it.
Migration
Converting an old project
memo-architect convert also writes the memo.package.yaml a converted project needs to load, and its warning names the methodology the old memo.config.yaml pinned. The new guide Convert an Old Project documents what it changes and what it leaves to you.
Packaging
Real SysAnd packages
memo pack builds a KPAR from the declared sources only, not from examples or the ontology. A package's .project.json lists the packages its sources import as urn:kpar:<package> usages with a ^version constraint (an extension lists the ontology, and any other extension it imports). memo-architect sysand publish (a dry run) stages exactly what memo pack stages, so it reports the real version and the same file set; before, it reported every version as 0.0.0.