Skip to content

Honesty: modelbasedPrj-* MUST NOT use SysMLEdge as model SSOT - #178

Merged
chouswei merged 1 commit into
masterfrom
cursor/modelbasedprj-not-sysmledge-ssot-7a4d
Sep 22, 2026
Merged

chouswei merged 1 commit into
masterfrom
cursor/modelbasedprj-not-sysmledge-ssot-7a4d

Conversation

@chouswei

Copy link
Copy Markdown
Owner

Prefix is the model host. modelbasedPrj-* said it does not use SysMLEdge as SSOT; the playbook had over-taught operator README as a flip for that family.

What changed

  • modelbasedPrj-* (and this engine checkout): repo-based. git sysml-models/ is model SSOT. MUST NOT use SysMLEdge as model SSOT. MUST NOT copy a SysMLEdge host onto that tree.
  • SysMLEdgePrj-* and bound (working_ssot=graph): SysMLEdge-based. The SSOT graph is hosted by SysMLEdge. MemNet stays shared working memory. Operator README on that overlay states SysMLEdge-based — it does not flip a modelbasedPrj-* tree.
  • Two pin_map tools still MUST NOT substitute. tip≠face. No Hatch bump.

SysML honesty

CousinSysMLEdge now locks modelbasedPrjRepoBased=true and modelbasedPrjSysmlEdgeIsModelSsot=false. MN-REQ-11.17.1 and cousin verify constraints follow. Tests in tests/test_playbook_host_mode.py refuse the lumped “repo-based or SysMLEdge-based” README flip.

Proof

pytest tests/test_playbook_host_mode.py tests/test_sysml_ssot_to_code.py passes.

Open in Web Open in Cursor 

Prefix is the host. modelbasedPrj-* and this engine checkout stay
repo-based (git sysml-models/). SysMLEdgePrj-* bound desk remains
working model SSOT. CousinSysMLEdge locks modelbasedPrjRepoBased
and modelbasedPrjSysmlEdgeIsModelSsot=false. No Hatch bump.

Co-authored-by: chouswei <chouswei@users.noreply.github.com>
@chouswei
chouswei marked this pull request as ready for review September 22, 2026 16:33
@chouswei
chouswei merged commit c308771 into master Sep 22, 2026
2 checks passed
chouswei added a commit that referenced this pull request Sep 24, 2026
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: chouswei <chouswei@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants