tms gate¶
Print a PDLC stage's recorded gate result.
Synopsis¶
Description¶
tms gate is read-only: it reports a Gate already recorded in the model's gates array — written by tms analyze --apply — it does not compute one itself. There is no tms gate --compute or equivalent; gate computation only ever happens as part of an analyze --apply call.
Flags¶
| Flag | Description |
|---|---|
--stage |
PDLC stage to evaluate (required) |
--ci |
Exit non-zero if the gate has not passed |
--json |
Output as JSON |
--help, -h |
Show help |
--ci treats a pending gate result (no recorded result yet) the same as failed — not passing.
Examples¶
Default Output¶
Output:
Gate: stage=deployment result=passed
- has-invariant equals true
Evaluated by: evaluation.EvaluateStageGate
JSON Output¶
{
"id": "gate-deployment",
"stage": "deployment",
"criteria": [{"metric": "has-invariant", "operator": "equals", "value": "true"}],
"result": "passed",
"evaluatedBy": "evaluation.EvaluateStageGate",
"evaluatedAt": "2026-08-16T20:39:40Z"
}
CI Enforcement¶
Exits 1 (no output beyond the default text report) if the recorded gate's result is failed or pending.
No Gate Recorded¶
Exits 1. A stage only has a recorded gate after at least one tms analyze --apply call for it.
See Also¶
- analyze — the only command that computes and writes a gate
- status — every stage's gate result at a glance, alongside run and finding counts
- Lifecycle IR Objects — the
Gateobject's full field reference