vellis

Design, create, review, revise, split, merge, or validate reusable software components and application compositions as textual SysML v2 black-box models. Use when Codex needs to define public actions and values, collaborator roles, abstract owned state, action effects, invariants, lifecycle, verification objectives, component boundaries, or system composition.

Keep human documentation synchronized with canonical SysML v2 models, generated component and application views, implementation realizations, repository tooling, skills, and workflow rules. Use after model, code, generated-view, README, AGENTS, skill, command, or public behavior changes.

Audit accepted SysML v2 component or application models against implementations, protocols, consumers, tests, generated evidence, predecessor contracts, and git history before proposing remediation. Use for periodic model hygiene, suspected model/implementation drift, migration-loss reviews, verification-closure audits, realization-codec review, or possible SysML-native modeling misuse.

Implement, review, or revise Python realizations of components from accepted textual SysML v2 contracts and generated views. Use when creating or aligning Python protocols, component classes, reference implementations, implementation bindings, or black-box contract tests.

Operate the Vellis RTG Knowledge Graph MCP server for agent-driven graph work. Use when an agent has RTG MCP tools such as rtg_validate_graph, rtg_apply_live_graph_changes, rtg_stage_knowledge_changes, rtg_apply_migration_cutover, rtg_execute_query, snapshots, or ledger replay, especially for schema evolution, validation recovery, and query authoring.

Design or evolve language-neutral RTG graph schemas from user and system needs. Use when choosing anchors, associated data, links, required properties, type keys, migration boundaries, or compatibility rules; when reviewing an RTG schema for clarity and extensibility; or before making consequential schema changes to a live RTG graph.

Ground textual SysML v2 and KerML authoring, review, language-semantics decisions, construct selection, and official-validator diagnosis in the repository's checksum-pinned specification corpus. Use for questions or changes involving parts, references, features, actions, bindings, successions, flows, ports, interfaces, states, constraints, requirements, views, imports, multiplicities, specialization, or other SysML/KerML syntax and semantics.