Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M MTSA
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lafhis
  • MTSA
  • Wiki
    • Enduser
  • Discrete Event Controller Synthesis

Discrete Event Controller Synthesis · Changes

Page history
Document permissive keyword in GR1 section of DECS page authored Sep 26, 2026 by Sebastian Uchitel's avatar Sebastian Uchitel

Co-Authored-By: default avatarClaude Opus 4.8 <noreply@anthropic.com>
Hide whitespace changes
Inline Side-by-side
Showing with 23 additions and 1 deletion
+23 -1
  • enduser/Discrete-Event-Controller-Synthesis.md enduser/Discrete-Event-Controller-Synthesis.md +23 -1
  • No files found.
enduser/Discrete-Event-Controller-Synthesis.md
View page @ 750d1508
......@@ -61,6 +61,29 @@ This keyword may be useful for debugging a non-realizable specification (i.e., o
plant ||Plant = (System)~{Spec}.
```
## `permissive` keyword
By default GR1 synthesis commits to a single strategy, keeping only the controllable
moves that make progress towards the goal. Adding `permissive` to the `controllerSpec`
instead produces the *maximally permissive* controller: it keeps **every** controllable
move that still guarantees the goal, not just the progress-making ones. The result is
the largest sub-behaviour of the plant that satisfies the specification — useful when
you want to preserve all valid behaviours for later refinement or analysis — at the
cost of a larger, non-deterministic controller.
```
controllerSpec Spec = {
safety = {NoB}
assumption = {G}
liveness = {E, D}
controllable = {a, c, e}
permissive
}
controller ||C = (System)~{Spec}.
```
(This feature is lightly maintained.)
# Non-Blocking
......@@ -135,7 +158,6 @@ experimental and may not be fully functional.
## To be checked
* `permissive` — permissive controller mode
* `controlled_det` — controlled determinism
* `lazyness` — controller laziness parameter
* `non_transient` — non-transient constraint
......
Clone repository
  • Developer
  • End User
  • devs
    • outputmessages
  • enduser
    • DCS
    • Discrete Event Controller Synthesis
    • Hello World
    • MTSA Syntax
    • Modal Transition Systems
  • Home