Skip to content

docs(deployment): reconcile the gate section with the four doors, the real rule count and the retired alias rule (#7465) #7483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-help merged 1 commit into from
Aug 10, 2026
+4 −5
Merged

docs(deployment): reconcile the gate section with the four doors, the real rule count and the retired alias rule (#7465) #7483

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions content/docs/deployment/cli.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -455,7 +455,7 @@ os validate path/to/config # Validate specific file
name/action/filter references, page sources, approval approvers, security
posture, the autonumber and view-reference lints. All of them come from one
registry, so the list is the same on `os build` and `os lint`; see
[The one gate, three entry points](/docs/deployment/validating-metadata#the-one-gate-three-entry-points)
[The one gate, four doors](/docs/deployment/validating-metadata#the-one-gate-four-doors)
for the full matrix. Every failing rule is reported in a single run rather than
stopping at the first, so one pass shows the whole hole.

Expand All @@ -469,8 +469,7 @@ stopping at the first, so one pass shows the whole hole.
- No objects defined
- No apps or plugins defined
- Every advisory the rule registry raised (dangling `stageField` /
`highlightFields` pointers, replay-unsafe seeds, ambiguous flow status,
deprecated visibility aliases, …)
`highlightFields` pointers, replay-unsafe seeds, ambiguous flow status, …)

<Callout type="tip">
`os validate`, `os build` and `os lint` share one rule registry, so a config that
Expand Down
4 changes: 2 additions & 2 deletions content/docs/deployment/validating-metadata.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -346,7 +346,7 @@ Skipped, to keep false positives at zero: the same set as §8 — non-static
values, `{...spread}` usages, relationship paths, system fields, and objects
another package defines.

## The one gate, three entry points
## The one gate, four doors

`os validate`, `os build` (alias of `os compile`) and `os lint` run the **same**
author-time rules, from one table — `AUTHORING_RULES` in
Expand Down Expand Up @@ -479,7 +479,7 @@ A clean run walks the registry and reports timing:
Config: /path/to/support-desk/objectstack.config.ts
Load time: 21ms
→ Validating against ObjectStack Protocol...
→ Running author-time rules (26)...
→ Running author-time rules (38)...
→ Checking capability providers (#3366)...
→ Checking package docs (ADR-0046)...

Expand Down
Loading