Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard#38

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-warren merged 3 commits into from
Sep 1, 2026
+557 −4
Merged

Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard #38

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2c69e9e
Correct the AGENTS.md predicate rule and add a stopgap flow-predicate…
claude Sep 1, 2026
6752ca7
Correct a comment that implied a platform gap where none exists
claude Sep 1, 2026
d03dcea
Split AGENTS.md rule 4 by expression scope, not by surface name
claude Sep 1, 2026
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
74 changes: 70 additions & 4 deletions AGENTS.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,11 @@ assignee field says.

## Verify after every metadata change

Metadata mistakes fail **silently at runtime**. A bare field reference in a
predicate (`done` instead of `record.done`) evaluates to `null` and hides the
action on every record; a dangling widget binding renders an empty chart.
Metadata mistakes fail **silently at runtime**: a dangling widget binding
renders an empty chart, a flow left out of its barrel never fires, an
unregistered hook never runs. `pnpm validate` catches most of them — including
a bare field reference on every predicate surface but one. Rule 4 below says
which one, and why it is the exception.

```bash
pnpm validate # same gates as build, no artifact — the fast inner loop
Expand DownExpand Up@@ -81,7 +83,57 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
optional and fails the assignment.
3. **Hooks are registered in `defineStack({ hooks })`**, not collected from the
objects barrel. An unregistered `*.hook.ts` never runs.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`, on every
surface: object validation rules, field `requiredWhen` / conditional rules,
action `visible` / `disabled`, sharing rules, hook conditions, and flow node
and edge conditions.

*What decides whether the gate catches you is SCOPE, not which surface you
are on.* An expression is evaluated either with the record bound as the
`record` namespace and nothing at top level (**record scope**), or with the
record's fields additionally flattened into top-level variables
(**flattened scope**). `validate` judges a bare identifier only in the first.

**Record-scoped surfaces — `validate` enforces this, and the failure really
is `null`.** Object validation rules, field conditional rules, action
`visible` / `disabled`, sharing rules and hook conditions all bind the record
as a namespace only, so a bare name binds nothing, the expression evaluates
to null, and the rule or action silently never fires. `validate` catches it
before it ships. Measured on `@objectstack/cli` 17.2.0, mutating
`duly_task`'s `skip_needs_reason` rule to `status == "skipped" && …` exits 1
with:

> object 'duly_task' · validation 'skip_needs_reason': bare reference
> `status` — a formula/validation expression binds the record as the
> `record` namespace, not at top level, so `status` resolves to nothing and
> the expression silently evaluates to null. Write `record.status`.

A misspelt **qualified** read is caught everywhere, flows included:
`record.needs_colection` in a flow condition gives ``unknown field
`needs_colection` on `duly_assignment` — did you mean `needs_collection`?``.

**Flow node and edge conditions are the one exception — no gate at all.**
They run in flattened scope, where a bare name may genuinely be a flow
variable (a loop iterator, a `get_record` output, an assignment target), so
the platform's `collectBoundRecordReads` deliberately never reads a bare
identifier as a record reference. The same predicate written
`status == "dispatched"` in a flow start condition passes `validate` with
**exit 0**.

*And in a flow the failure is not `null` either.* A bare `status` there
**resolves** — to the flattened field, or to a same-named flow variable that
was seeded first and **shadows** it. That shadowing case is the subtler bug:
the predicate reads correctly and silently means something else. When a name
resolves to nothing the engine **throws** (ADR-0032 §1c: no silent fallback —
a non-`ok` result is a real fault, not a false condition). So on this one
surface the outcomes are "silently means something else" and "loud runtime
fault", never the quiet null of the record-scoped surfaces above.

Filed upstream as **objectstack-ai/objectstack#14089**. Until it lands,
`test/flow-predicates.test.ts` is a repo-local **stopgap** covering exactly
the unguarded surfaces — flow node and edge conditions, walked over
`dulyFlows`, with `dulyJobs` walked as a tripwire — and it is written to be
deleted when #14089 ships, not maintained.
5. **Never store what you can filter.** No `is_late`, no `is_overdue`, no
`is_open`. A stored flag needs a writer that runs every midnight; a formula
field is virtual and a filter naming one silently matches nothing. Ask
Expand All@@ -98,6 +150,20 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
expected here, and not a bug to chase.
8. **English is the source language.** Every authored label gets an `en` entry;
`zh-CN` is hand-translated. Do not hard-code display text in a hook or flow.
9. **Metadata first — a handler is the last resort, not the first.** This is an
ObjectStack application. Objects, views, flows, jobs, datasets, permission
sets and actions are the primary tools; a hand-written handler is what you
reach for when none of them can express the thing.
**Before writing a handler, check whether the platform already has a
declarative way to do it.** The spec is on disk — `@objectstack/spec` ships
its Zod sources — and the answer is usually a key you have not read yet.
**If the platform genuinely cannot express it, file an issue against
`objectstack-ai/objectstack` and say so on the card.** Do not quietly write
around the gap. A workaround in application code is how a platform gap
becomes permanent and invisible: it works, nobody upstream ever hears about
it, and the next application writes the same workaround from scratch.
`test/flow-predicates.test.ts` is what a *declared* workaround looks like —
labelled a stopgap, pointing at objectstack#14089, and built to be deleted.

## Landing your work

Expand Down
Loading
Loading
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard#38

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-warren
merged 3 commits into

from

Sep 1, 2026

+557

−4

 Merged


Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard
#38
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


3 commits


Select commit
Hold shift + click to select a range
2c69e9e

Correct the AGENTS.md predicate rule and add a stopgap flow-predicate…


claude Sep 1, 2026
6752ca7

Correct a comment that implied a platform gap where none exists


claude Sep 1, 2026
d03dcea

Split AGENTS.md rule 4 by expression scope, not by surface name


claude Sep 1, 2026

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


74 changes: 70 additions & 4 deletions
AGENTS.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,11 @@ assignee field says.

## Verify after every metadata change

Metadata mistakes fail **silently at runtime**. A bare field reference in a
predicate (`done` instead of `record.done`) evaluates to `null` and hides the
action on every record; a dangling widget binding renders an empty chart.
Metadata mistakes fail **silently at runtime**: a dangling widget binding
renders an empty chart, a flow left out of its barrel never fires, an
unregistered hook never runs. `pnpm validate` catches most of them — including
a bare field reference on every predicate surface but one. Rule 4 below says
which one, and why it is the exception.

```bash
pnpm validate # same gates as build, no artifact — the fast inner loop
Expand DownExpand Up@@ -81,7 +83,57 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 optional and fails the assignment.
3. **Hooks are registered in `defineStack({ hooks })`**, not collected from the
 objects barrel. An unregistered `*.hook.ts` never runs.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`, on every
 surface: object validation rules, field `requiredWhen` / conditional rules,
 action `visible` / `disabled`, sharing rules, hook conditions, and flow node
 and edge conditions.

 *What decides whether the gate catches you is SCOPE, not which surface you
 are on.* An expression is evaluated either with the record bound as the
 `record` namespace and nothing at top level (**record scope**), or with the
 record's fields additionally flattened into top-level variables
 (**flattened scope**). `validate` judges a bare identifier only in the first.

 **Record-scoped surfaces — `validate` enforces this, and the failure really
 is `null`.** Object validation rules, field conditional rules, action
 `visible` / `disabled`, sharing rules and hook conditions all bind the record
 as a namespace only, so a bare name binds nothing, the expression evaluates
 to null, and the rule or action silently never fires. `validate` catches it
 before it ships. Measured on `@objectstack/cli` 17.2.0, mutating
 `duly_task`'s `skip_needs_reason` rule to `status == "skipped" && …` exits 1
 with:

 > object 'duly_task' · validation 'skip_needs_reason': bare reference
 > `status` — a formula/validation expression binds the record as the
 > `record` namespace, not at top level, so `status` resolves to nothing and
 > the expression silently evaluates to null. Write `record.status`.

 A misspelt **qualified** read is caught everywhere, flows included:
 `record.needs_colection` in a flow condition gives ``unknown field
 `needs_colection` on `duly_assignment` — did you mean `needs_collection`?``.

 **Flow node and edge conditions are the one exception — no gate at all.**
 They run in flattened scope, where a bare name may genuinely be a flow
 variable (a loop iterator, a `get_record` output, an assignment target), so
 the platform's `collectBoundRecordReads` deliberately never reads a bare
 identifier as a record reference. The same predicate written
 `status == "dispatched"` in a flow start condition passes `validate` with
 **exit 0**.

 *And in a flow the failure is not `null` either.* A bare `status` there
 **resolves** — to the flattened field, or to a same-named flow variable that
 was seeded first and **shadows** it. That shadowing case is the subtler bug:
 the predicate reads correctly and silently means something else. When a name
 resolves to nothing the engine **throws** (ADR-0032 §1c: no silent fallback —
 a non-`ok` result is a real fault, not a false condition). So on this one
 surface the outcomes are "silently means something else" and "loud runtime
 fault", never the quiet null of the record-scoped surfaces above.

 Filed upstream as **objectstack-ai/objectstack#14089**. Until it lands,
 `test/flow-predicates.test.ts` is a repo-local **stopgap** covering exactly
 the unguarded surfaces — flow node and edge conditions, walked over
 `dulyFlows`, with `dulyJobs` walked as a tripwire — and it is written to be
 deleted when #14089 ships, not maintained.
5. **Never store what you can filter.** No `is_late`, no `is_overdue`, no
 `is_open`. A stored flag needs a writer that runs every midnight; a formula
 field is virtual and a filter naming one silently matches nothing. Ask
Expand All@@ -98,6 +150,20 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 expected here, and not a bug to chase.
8. **English is the source language.** Every authored label gets an `en` entry;
 `zh-CN` is hand-translated. Do not hard-code display text in a hook or flow.
9. **Metadata first — a handler is the last resort, not the first.** This is an
 ObjectStack application. Objects, views, flows, jobs, datasets, permission
 sets and actions are the primary tools; a hand-written handler is what you
 reach for when none of them can express the thing.
 **Before writing a handler, check whether the platform already has a
 declarative way to do it.** The spec is on disk — `@objectstack/spec` ships
 its Zod sources — and the answer is usually a key you have not read yet.
 **If the platform genuinely cannot express it, file an issue against
 `objectstack-ai/objectstack` and say so on the card.** Do not quietly write
 around the gap. A workaround in application code is how a platform gap
 becomes permanent and invisible: it works, nobody upstream ever hears about
 it, and the next application writes the same workaround from scratch.
 `test/flow-predicates.test.ts` is what a *declared* workaround looks like —
 labelled a stopgap, pointing at objectstack#14089, and built to be deleted.

## Landing your work

Expand Down
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard#38

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-warren
merged 3 commits into

from

Sep 1, 2026

+557

−4

 Merged


Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard
#38
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


3 commits


Select commit
Hold shift + click to select a range
2c69e9e

Correct the AGENTS.md predicate rule and add a stopgap flow-predicate…


claude Sep 1, 2026
6752ca7

Correct a comment that implied a platform gap where none exists


claude Sep 1, 2026
d03dcea

Split AGENTS.md rule 4 by expression scope, not by surface name


claude Sep 1, 2026

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


74 changes: 70 additions & 4 deletions
AGENTS.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,11 @@ assignee field says.

## Verify after every metadata change

Metadata mistakes fail **silently at runtime**. A bare field reference in a
predicate (`done` instead of `record.done`) evaluates to `null` and hides the
action on every record; a dangling widget binding renders an empty chart.
Metadata mistakes fail **silently at runtime**: a dangling widget binding
renders an empty chart, a flow left out of its barrel never fires, an
unregistered hook never runs. `pnpm validate` catches most of them — including
a bare field reference on every predicate surface but one. Rule 4 below says
which one, and why it is the exception.

```bash
pnpm validate # same gates as build, no artifact — the fast inner loop
Expand DownExpand Up@@ -81,7 +83,57 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 optional and fails the assignment.
3. **Hooks are registered in `defineStack({ hooks })`**, not collected from the
 objects barrel. An unregistered `*.hook.ts` never runs.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`, on every
 surface: object validation rules, field `requiredWhen` / conditional rules,
 action `visible` / `disabled`, sharing rules, hook conditions, and flow node
 and edge conditions.

 *What decides whether the gate catches you is SCOPE, not which surface you
 are on.* An expression is evaluated either with the record bound as the
 `record` namespace and nothing at top level (**record scope**), or with the
 record's fields additionally flattened into top-level variables
 (**flattened scope**). `validate` judges a bare identifier only in the first.

 **Record-scoped surfaces — `validate` enforces this, and the failure really
 is `null`.** Object validation rules, field conditional rules, action
 `visible` / `disabled`, sharing rules and hook conditions all bind the record
 as a namespace only, so a bare name binds nothing, the expression evaluates
 to null, and the rule or action silently never fires. `validate` catches it
 before it ships. Measured on `@objectstack/cli` 17.2.0, mutating
 `duly_task`'s `skip_needs_reason` rule to `status == "skipped" && …` exits 1
 with:

 > object 'duly_task' · validation 'skip_needs_reason': bare reference
 > `status` — a formula/validation expression binds the record as the
 > `record` namespace, not at top level, so `status` resolves to nothing and
 > the expression silently evaluates to null. Write `record.status`.

 A misspelt **qualified** read is caught everywhere, flows included:
 `record.needs_colection` in a flow condition gives ``unknown field
 `needs_colection` on `duly_assignment` — did you mean `needs_collection`?``.

 **Flow node and edge conditions are the one exception — no gate at all.**
 They run in flattened scope, where a bare name may genuinely be a flow
 variable (a loop iterator, a `get_record` output, an assignment target), so
 the platform's `collectBoundRecordReads` deliberately never reads a bare
 identifier as a record reference. The same predicate written
 `status == "dispatched"` in a flow start condition passes `validate` with
 **exit 0**.

 *And in a flow the failure is not `null` either.* A bare `status` there
 **resolves** — to the flattened field, or to a same-named flow variable that
 was seeded first and **shadows** it. That shadowing case is the subtler bug:
 the predicate reads correctly and silently means something else. When a name
 resolves to nothing the engine **throws** (ADR-0032 §1c: no silent fallback —
 a non-`ok` result is a real fault, not a false condition). So on this one
 surface the outcomes are "silently means something else" and "loud runtime
 fault", never the quiet null of the record-scoped surfaces above.

 Filed upstream as **objectstack-ai/objectstack#14089**. Until it lands,
 `test/flow-predicates.test.ts` is a repo-local **stopgap** covering exactly
 the unguarded surfaces — flow node and edge conditions, walked over
 `dulyFlows`, with `dulyJobs` walked as a tripwire — and it is written to be
 deleted when #14089 ships, not maintained.
5. **Never store what you can filter.** No `is_late`, no `is_overdue`, no
 `is_open`. A stored flag needs a writer that runs every midnight; a formula
 field is virtual and a filter naming one silently matches nothing. Ask
Expand All@@ -98,6 +150,20 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 expected here, and not a bug to chase.
8. **English is the source language.** Every authored label gets an `en` entry;
 `zh-CN` is hand-translated. Do not hard-code display text in a hook or flow.
9. **Metadata first — a handler is the last resort, not the first.** This is an
 ObjectStack application. Objects, views, flows, jobs, datasets, permission
 sets and actions are the primary tools; a hand-written handler is what you
 reach for when none of them can express the thing.
 **Before writing a handler, check whether the platform already has a
 declarative way to do it.** The spec is on disk — `@objectstack/spec` ships
 its Zod sources — and the answer is usually a key you have not read yet.
 **If the platform genuinely cannot express it, file an issue against
 `objectstack-ai/objectstack` and say so on the card.** Do not quietly write
 around the gap. A workaround in application code is how a platform gap
 becomes permanent and invisible: it works, nobody upstream ever hears about
 it, and the next application writes the same workaround from scratch.
 `test/flow-predicates.test.ts` is what a *declared* workaround looks like —
 labelled a stopgap, pointing at objectstack#14089, and built to be deleted.

## Landing your work

Expand Down
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard#38

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-warren
merged 3 commits into

from

Sep 1, 2026

+557

−4

 Merged


Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard
#38
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


3 commits


Select commit
Hold shift + click to select a range
2c69e9e

Correct the AGENTS.md predicate rule and add a stopgap flow-predicate…


claude Sep 1, 2026
6752ca7

Correct a comment that implied a platform gap where none exists


claude Sep 1, 2026
d03dcea

Split AGENTS.md rule 4 by expression scope, not by surface name


claude Sep 1, 2026

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


74 changes: 70 additions & 4 deletions
AGENTS.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,11 @@ assignee field says.

## Verify after every metadata change

Metadata mistakes fail **silently at runtime**. A bare field reference in a
predicate (`done` instead of `record.done`) evaluates to `null` and hides the
action on every record; a dangling widget binding renders an empty chart.
Metadata mistakes fail **silently at runtime**: a dangling widget binding
renders an empty chart, a flow left out of its barrel never fires, an
unregistered hook never runs. `pnpm validate` catches most of them — including
a bare field reference on every predicate surface but one. Rule 4 below says
which one, and why it is the exception.

```bash
pnpm validate # same gates as build, no artifact — the fast inner loop
Expand DownExpand Up@@ -81,7 +83,57 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 optional and fails the assignment.
3. **Hooks are registered in `defineStack({ hooks })`**, not collected from the
 objects barrel. An unregistered `*.hook.ts` never runs.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`, on every
 surface: object validation rules, field `requiredWhen` / conditional rules,
 action `visible` / `disabled`, sharing rules, hook conditions, and flow node
 and edge conditions.

 *What decides whether the gate catches you is SCOPE, not which surface you
 are on.* An expression is evaluated either with the record bound as the
 `record` namespace and nothing at top level (**record scope**), or with the
 record's fields additionally flattened into top-level variables
 (**flattened scope**). `validate` judges a bare identifier only in the first.

 **Record-scoped surfaces — `validate` enforces this, and the failure really
 is `null`.** Object validation rules, field conditional rules, action
 `visible` / `disabled`, sharing rules and hook conditions all bind the record
 as a namespace only, so a bare name binds nothing, the expression evaluates
 to null, and the rule or action silently never fires. `validate` catches it
 before it ships. Measured on `@objectstack/cli` 17.2.0, mutating
 `duly_task`'s `skip_needs_reason` rule to `status == "skipped" && …` exits 1
 with:

 > object 'duly_task' · validation 'skip_needs_reason': bare reference
 > `status` — a formula/validation expression binds the record as the
 > `record` namespace, not at top level, so `status` resolves to nothing and
 > the expression silently evaluates to null. Write `record.status`.

 A misspelt **qualified** read is caught everywhere, flows included:
 `record.needs_colection` in a flow condition gives ``unknown field
 `needs_colection` on `duly_assignment` — did you mean `needs_collection`?``.

 **Flow node and edge conditions are the one exception — no gate at all.**
 They run in flattened scope, where a bare name may genuinely be a flow
 variable (a loop iterator, a `get_record` output, an assignment target), so
 the platform's `collectBoundRecordReads` deliberately never reads a bare
 identifier as a record reference. The same predicate written
 `status == "dispatched"` in a flow start condition passes `validate` with
 **exit 0**.

 *And in a flow the failure is not `null` either.* A bare `status` there
 **resolves** — to the flattened field, or to a same-named flow variable that
 was seeded first and **shadows** it. That shadowing case is the subtler bug:
 the predicate reads correctly and silently means something else. When a name
 resolves to nothing the engine **throws** (ADR-0032 §1c: no silent fallback —
 a non-`ok` result is a real fault, not a false condition). So on this one
 surface the outcomes are "silently means something else" and "loud runtime
 fault", never the quiet null of the record-scoped surfaces above.

 Filed upstream as **objectstack-ai/objectstack#14089**. Until it lands,
 `test/flow-predicates.test.ts` is a repo-local **stopgap** covering exactly
 the unguarded surfaces — flow node and edge conditions, walked over
 `dulyFlows`, with `dulyJobs` walked as a tripwire — and it is written to be
 deleted when #14089 ships, not maintained.
5. **Never store what you can filter.** No `is_late`, no `is_overdue`, no
 `is_open`. A stored flag needs a writer that runs every midnight; a formula
 field is virtual and a filter naming one silently matches nothing. Ask
Expand All@@ -98,6 +150,20 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 expected here, and not a bug to chase.
8. **English is the source language.** Every authored label gets an `en` entry;
 `zh-CN` is hand-translated. Do not hard-code display text in a hook or flow.
9. **Metadata first — a handler is the last resort, not the first.** This is an
 ObjectStack application. Objects, views, flows, jobs, datasets, permission
 sets and actions are the primary tools; a hand-written handler is what you
 reach for when none of them can express the thing.
 **Before writing a handler, check whether the platform already has a
 declarative way to do it.** The spec is on disk — `@objectstack/spec` ships
 its Zod sources — and the answer is usually a key you have not read yet.
 **If the platform genuinely cannot express it, file an issue against
 `objectstack-ai/objectstack` and say so on the card.** Do not quietly write
 around the gap. A workaround in application code is how a platform gap
 becomes permanent and invisible: it works, nobody upstream ever hears about
 it, and the next application writes the same workaround from scratch.
 `test/flow-predicates.test.ts` is what a *declared* workaround looks like —
 labelled a stopgap, pointing at objectstack#14089, and built to be deleted.

## Landing your work

Expand Down
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard#38

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-warren
merged 3 commits into

from

Sep 1, 2026

+557

−4

 Merged


Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard
#38
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


3 commits


Select commit
Hold shift + click to select a range
2c69e9e

Correct the AGENTS.md predicate rule and add a stopgap flow-predicate…


claude Sep 1, 2026
6752ca7

Correct a comment that implied a platform gap where none exists


claude Sep 1, 2026
d03dcea

Split AGENTS.md rule 4 by expression scope, not by surface name


claude Sep 1, 2026

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


74 changes: 70 additions & 4 deletions
AGENTS.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,11 @@ assignee field says.

## Verify after every metadata change

Metadata mistakes fail **silently at runtime**. A bare field reference in a
predicate (`done` instead of `record.done`) evaluates to `null` and hides the
action on every record; a dangling widget binding renders an empty chart.
Metadata mistakes fail **silently at runtime**: a dangling widget binding
renders an empty chart, a flow left out of its barrel never fires, an
unregistered hook never runs. `pnpm validate` catches most of them — including
a bare field reference on every predicate surface but one. Rule 4 below says
which one, and why it is the exception.

```bash
pnpm validate # same gates as build, no artifact — the fast inner loop
Expand DownExpand Up@@ -81,7 +83,57 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 optional and fails the assignment.
3. **Hooks are registered in `defineStack({ hooks })`**, not collected from the
 objects barrel. An unregistered `*.hook.ts` never runs.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`, on every
 surface: object validation rules, field `requiredWhen` / conditional rules,
 action `visible` / `disabled`, sharing rules, hook conditions, and flow node
 and edge conditions.

 *What decides whether the gate catches you is SCOPE, not which surface you
 are on.* An expression is evaluated either with the record bound as the
 `record` namespace and nothing at top level (**record scope**), or with the
 record's fields additionally flattened into top-level variables
 (**flattened scope**). `validate` judges a bare identifier only in the first.

 **Record-scoped surfaces — `validate` enforces this, and the failure really
 is `null`.** Object validation rules, field conditional rules, action
 `visible` / `disabled`, sharing rules and hook conditions all bind the record
 as a namespace only, so a bare name binds nothing, the expression evaluates
 to null, and the rule or action silently never fires. `validate` catches it
 before it ships. Measured on `@objectstack/cli` 17.2.0, mutating
 `duly_task`'s `skip_needs_reason` rule to `status == "skipped" && …` exits 1
 with:

 > object 'duly_task' · validation 'skip_needs_reason': bare reference
 > `status` — a formula/validation expression binds the record as the
 > `record` namespace, not at top level, so `status` resolves to nothing and
 > the expression silently evaluates to null. Write `record.status`.

 A misspelt **qualified** read is caught everywhere, flows included:
 `record.needs_colection` in a flow condition gives ``unknown field
 `needs_colection` on `duly_assignment` — did you mean `needs_collection`?``.

 **Flow node and edge conditions are the one exception — no gate at all.**
 They run in flattened scope, where a bare name may genuinely be a flow
 variable (a loop iterator, a `get_record` output, an assignment target), so
 the platform's `collectBoundRecordReads` deliberately never reads a bare
 identifier as a record reference. The same predicate written
 `status == "dispatched"` in a flow start condition passes `validate` with
 **exit 0**.

 *And in a flow the failure is not `null` either.* A bare `status` there
 **resolves** — to the flattened field, or to a same-named flow variable that
 was seeded first and **shadows** it. That shadowing case is the subtler bug:
 the predicate reads correctly and silently means something else. When a name
 resolves to nothing the engine **throws** (ADR-0032 §1c: no silent fallback —
 a non-`ok` result is a real fault, not a false condition). So on this one
 surface the outcomes are "silently means something else" and "loud runtime
 fault", never the quiet null of the record-scoped surfaces above.

 Filed upstream as **objectstack-ai/objectstack#14089**. Until it lands,
 `test/flow-predicates.test.ts` is a repo-local **stopgap** covering exactly
 the unguarded surfaces — flow node and edge conditions, walked over
 `dulyFlows`, with `dulyJobs` walked as a tripwire — and it is written to be
 deleted when #14089 ships, not maintained.
5. **Never store what you can filter.** No `is_late`, no `is_overdue`, no
 `is_open`. A stored flag needs a writer that runs every midnight; a formula
 field is virtual and a filter naming one silently matches nothing. Ask
Expand All@@ -98,6 +150,20 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 expected here, and not a bug to chase.
8. **English is the source language.** Every authored label gets an `en` entry;
 `zh-CN` is hand-translated. Do not hard-code display text in a hook or flow.
9. **Metadata first — a handler is the last resort, not the first.** This is an
 ObjectStack application. Objects, views, flows, jobs, datasets, permission
 sets and actions are the primary tools; a hand-written handler is what you
 reach for when none of them can express the thing.
 **Before writing a handler, check whether the platform already has a
 declarative way to do it.** The spec is on disk — `@objectstack/spec` ships
 its Zod sources — and the answer is usually a key you have not read yet.
 **If the platform genuinely cannot express it, file an issue against
 `objectstack-ai/objectstack` and say so on the card.** Do not quietly write
 around the gap. A workaround in application code is how a platform gap
 becomes permanent and invisible: it works, nobody upstream ever hears about
 it, and the next application writes the same workaround from scratch.
 `test/flow-predicates.test.ts` is what a *declared* workaround looks like —
 labelled a stopgap, pointing at objectstack#14089, and built to be deleted.

## Landing your work

Expand Down
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard#38

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-warren
merged 3 commits into

from

Sep 1, 2026

+557

−4

 Merged


Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard
#38
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


3 commits


Select commit
Hold shift + click to select a range
2c69e9e

Correct the AGENTS.md predicate rule and add a stopgap flow-predicate…


claude Sep 1, 2026
6752ca7

Correct a comment that implied a platform gap where none exists


claude Sep 1, 2026
d03dcea

Split AGENTS.md rule 4 by expression scope, not by surface name


claude Sep 1, 2026

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


74 changes: 70 additions & 4 deletions
AGENTS.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,11 @@ assignee field says.

## Verify after every metadata change

Metadata mistakes fail **silently at runtime**. A bare field reference in a
predicate (`done` instead of `record.done`) evaluates to `null` and hides the
action on every record; a dangling widget binding renders an empty chart.
Metadata mistakes fail **silently at runtime**: a dangling widget binding
renders an empty chart, a flow left out of its barrel never fires, an
unregistered hook never runs. `pnpm validate` catches most of them — including
a bare field reference on every predicate surface but one. Rule 4 below says
which one, and why it is the exception.

```bash
pnpm validate # same gates as build, no artifact — the fast inner loop
Expand DownExpand Up@@ -81,7 +83,57 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 optional and fails the assignment.
3. **Hooks are registered in `defineStack({ hooks })`**, not collected from the
 objects barrel. An unregistered `*.hook.ts` never runs.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`, on every
 surface: object validation rules, field `requiredWhen` / conditional rules,
 action `visible` / `disabled`, sharing rules, hook conditions, and flow node
 and edge conditions.

 *What decides whether the gate catches you is SCOPE, not which surface you
 are on.* An expression is evaluated either with the record bound as the
 `record` namespace and nothing at top level (**record scope**), or with the
 record's fields additionally flattened into top-level variables
 (**flattened scope**). `validate` judges a bare identifier only in the first.

 **Record-scoped surfaces — `validate` enforces this, and the failure really
 is `null`.** Object validation rules, field conditional rules, action
 `visible` / `disabled`, sharing rules and hook conditions all bind the record
 as a namespace only, so a bare name binds nothing, the expression evaluates
 to null, and the rule or action silently never fires. `validate` catches it
 before it ships. Measured on `@objectstack/cli` 17.2.0, mutating
 `duly_task`'s `skip_needs_reason` rule to `status == "skipped" && …` exits 1
 with:

 > object 'duly_task' · validation 'skip_needs_reason': bare reference
 > `status` — a formula/validation expression binds the record as the
 > `record` namespace, not at top level, so `status` resolves to nothing and
 > the expression silently evaluates to null. Write `record.status`.

 A misspelt **qualified** read is caught everywhere, flows included:
 `record.needs_colection` in a flow condition gives ``unknown field
 `needs_colection` on `duly_assignment` — did you mean `needs_collection`?``.

 **Flow node and edge conditions are the one exception — no gate at all.**
 They run in flattened scope, where a bare name may genuinely be a flow
 variable (a loop iterator, a `get_record` output, an assignment target), so
 the platform's `collectBoundRecordReads` deliberately never reads a bare
 identifier as a record reference. The same predicate written
 `status == "dispatched"` in a flow start condition passes `validate` with
 **exit 0**.

 *And in a flow the failure is not `null` either.* A bare `status` there
 **resolves** — to the flattened field, or to a same-named flow variable that
 was seeded first and **shadows** it. That shadowing case is the subtler bug:
 the predicate reads correctly and silently means something else. When a name
 resolves to nothing the engine **throws** (ADR-0032 §1c: no silent fallback —
 a non-`ok` result is a real fault, not a false condition). So on this one
 surface the outcomes are "silently means something else" and "loud runtime
 fault", never the quiet null of the record-scoped surfaces above.

 Filed upstream as **objectstack-ai/objectstack#14089**. Until it lands,
 `test/flow-predicates.test.ts` is a repo-local **stopgap** covering exactly
 the unguarded surfaces — flow node and edge conditions, walked over
 `dulyFlows`, with `dulyJobs` walked as a tripwire — and it is written to be
 deleted when #14089 ships, not maintained.
5. **Never store what you can filter.** No `is_late`, no `is_overdue`, no
 `is_open`. A stored flag needs a writer that runs every midnight; a formula
 field is virtual and a filter naming one silently matches nothing. Ask
Expand All@@ -98,6 +150,20 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 expected here, and not a bug to chase.
8. **English is the source language.** Every authored label gets an `en` entry;
 `zh-CN` is hand-translated. Do not hard-code display text in a hook or flow.
9. **Metadata first — a handler is the last resort, not the first.** This is an
 ObjectStack application. Objects, views, flows, jobs, datasets, permission
 sets and actions are the primary tools; a hand-written handler is what you
 reach for when none of them can express the thing.
 **Before writing a handler, check whether the platform already has a
 declarative way to do it.** The spec is on disk — `@objectstack/spec` ships
 its Zod sources — and the answer is usually a key you have not read yet.
 **If the platform genuinely cannot express it, file an issue against
 `objectstack-ai/objectstack` and say so on the card.** Do not quietly write
 around the gap. A workaround in application code is how a platform gap
 becomes permanent and invisible: it works, nobody upstream ever hears about
 it, and the next application writes the same workaround from scratch.
 `test/flow-predicates.test.ts` is what a *declared* workaround looks like —
 labelled a stopgap, pointing at objectstack#14089, and built to be deleted.

## Landing your work

Expand Down
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard#38

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-warren
merged 3 commits into

from

Sep 1, 2026

+557

−4

 Merged


Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard
#38
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


3 commits


Select commit
Hold shift + click to select a range
2c69e9e

Correct the AGENTS.md predicate rule and add a stopgap flow-predicate…


claude Sep 1, 2026
6752ca7

Correct a comment that implied a platform gap where none exists


claude Sep 1, 2026
d03dcea

Split AGENTS.md rule 4 by expression scope, not by surface name


claude Sep 1, 2026

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


74 changes: 70 additions & 4 deletions
AGENTS.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,11 @@ assignee field says.

## Verify after every metadata change

Metadata mistakes fail **silently at runtime**. A bare field reference in a
predicate (`done` instead of `record.done`) evaluates to `null` and hides the
action on every record; a dangling widget binding renders an empty chart.
Metadata mistakes fail **silently at runtime**: a dangling widget binding
renders an empty chart, a flow left out of its barrel never fires, an
unregistered hook never runs. `pnpm validate` catches most of them — including
a bare field reference on every predicate surface but one. Rule 4 below says
which one, and why it is the exception.

```bash
pnpm validate # same gates as build, no artifact — the fast inner loop
Expand DownExpand Up@@ -81,7 +83,57 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 optional and fails the assignment.
3. **Hooks are registered in `defineStack({ hooks })`**, not collected from the
 objects barrel. An unregistered `*.hook.ts` never runs.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`, on every
 surface: object validation rules, field `requiredWhen` / conditional rules,
 action `visible` / `disabled`, sharing rules, hook conditions, and flow node
 and edge conditions.

 *What decides whether the gate catches you is SCOPE, not which surface you
 are on.* An expression is evaluated either with the record bound as the
 `record` namespace and nothing at top level (**record scope**), or with the
 record's fields additionally flattened into top-level variables
 (**flattened scope**). `validate` judges a bare identifier only in the first.

 **Record-scoped surfaces — `validate` enforces this, and the failure really
 is `null`.** Object validation rules, field conditional rules, action
 `visible` / `disabled`, sharing rules and hook conditions all bind the record
 as a namespace only, so a bare name binds nothing, the expression evaluates
 to null, and the rule or action silently never fires. `validate` catches it
 before it ships. Measured on `@objectstack/cli` 17.2.0, mutating
 `duly_task`'s `skip_needs_reason` rule to `status == "skipped" && …` exits 1
 with:

 > object 'duly_task' · validation 'skip_needs_reason': bare reference
 > `status` — a formula/validation expression binds the record as the
 > `record` namespace, not at top level, so `status` resolves to nothing and
 > the expression silently evaluates to null. Write `record.status`.

 A misspelt **qualified** read is caught everywhere, flows included:
 `record.needs_colection` in a flow condition gives ``unknown field
 `needs_colection` on `duly_assignment` — did you mean `needs_collection`?``.

 **Flow node and edge conditions are the one exception — no gate at all.**
 They run in flattened scope, where a bare name may genuinely be a flow
 variable (a loop iterator, a `get_record` output, an assignment target), so
 the platform's `collectBoundRecordReads` deliberately never reads a bare
 identifier as a record reference. The same predicate written
 `status == "dispatched"` in a flow start condition passes `validate` with
 **exit 0**.

 *And in a flow the failure is not `null` either.* A bare `status` there
 **resolves** — to the flattened field, or to a same-named flow variable that
 was seeded first and **shadows** it. That shadowing case is the subtler bug:
 the predicate reads correctly and silently means something else. When a name
 resolves to nothing the engine **throws** (ADR-0032 §1c: no silent fallback —
 a non-`ok` result is a real fault, not a false condition). So on this one
 surface the outcomes are "silently means something else" and "loud runtime
 fault", never the quiet null of the record-scoped surfaces above.

 Filed upstream as **objectstack-ai/objectstack#14089**. Until it lands,
 `test/flow-predicates.test.ts` is a repo-local **stopgap** covering exactly
 the unguarded surfaces — flow node and edge conditions, walked over
 `dulyFlows`, with `dulyJobs` walked as a tripwire — and it is written to be
 deleted when #14089 ships, not maintained.
5. **Never store what you can filter.** No `is_late`, no `is_overdue`, no
 `is_open`. A stored flag needs a writer that runs every midnight; a formula
 field is virtual and a filter naming one silently matches nothing. Ask
Expand All@@ -98,6 +150,20 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 expected here, and not a bug to chase.
8. **English is the source language.** Every authored label gets an `en` entry;
 `zh-CN` is hand-translated. Do not hard-code display text in a hook or flow.
9. **Metadata first — a handler is the last resort, not the first.** This is an
 ObjectStack application. Objects, views, flows, jobs, datasets, permission
 sets and actions are the primary tools; a hand-written handler is what you
 reach for when none of them can express the thing.
 **Before writing a handler, check whether the platform already has a
 declarative way to do it.** The spec is on disk — `@objectstack/spec` ships
 its Zod sources — and the answer is usually a key you have not read yet.
 **If the platform genuinely cannot express it, file an issue against
 `objectstack-ai/objectstack` and say so on the card.** Do not quietly write
 around the gap. A workaround in application code is how a platform gap
 becomes permanent and invisible: it works, nobody upstream ever hears about
 it, and the next application writes the same workaround from scratch.
 `test/flow-predicates.test.ts` is what a *declared* workaround looks like —
 labelled a stopgap, pointing at objectstack#14089, and built to be deleted.

## Landing your work

Expand Down
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard#38

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-warren
merged 3 commits into

from

Sep 1, 2026

+557

−4

 Merged


Correct the AGENTS.md predicate rule and add a stopgap flow-predicate guard
#38
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


3 commits


Select commit
Hold shift + click to select a range
2c69e9e

Correct the AGENTS.md predicate rule and add a stopgap flow-predicate…


claude Sep 1, 2026
6752ca7

Correct a comment that implied a platform gap where none exists


claude Sep 1, 2026
d03dcea

Split AGENTS.md rule 4 by expression scope, not by surface name


claude Sep 1, 2026

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


74 changes: 70 additions & 4 deletions
AGENTS.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,11 @@ assignee field says.

## Verify after every metadata change

Metadata mistakes fail **silently at runtime**. A bare field reference in a
predicate (`done` instead of `record.done`) evaluates to `null` and hides the
action on every record; a dangling widget binding renders an empty chart.
Metadata mistakes fail **silently at runtime**: a dangling widget binding
renders an empty chart, a flow left out of its barrel never fires, an
unregistered hook never runs. `pnpm validate` catches most of them — including
a bare field reference on every predicate surface but one. Rule 4 below says
which one, and why it is the exception.

```bash
pnpm validate # same gates as build, no artifact — the fast inner loop
Expand DownExpand Up@@ -81,7 +83,57 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 optional and fails the assignment.
3. **Hooks are registered in `defineStack({ hooks })`**, not collected from the
 objects barrel. An unregistered `*.hook.ts` never runs.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`.
4. **Predicates are CEL** — `record.<field>`, never bare `<field>`, on every
 surface: object validation rules, field `requiredWhen` / conditional rules,
 action `visible` / `disabled`, sharing rules, hook conditions, and flow node
 and edge conditions.

 *What decides whether the gate catches you is SCOPE, not which surface you
 are on.* An expression is evaluated either with the record bound as the
 `record` namespace and nothing at top level (**record scope**), or with the
 record's fields additionally flattened into top-level variables
 (**flattened scope**). `validate` judges a bare identifier only in the first.

 **Record-scoped surfaces — `validate` enforces this, and the failure really
 is `null`.** Object validation rules, field conditional rules, action
 `visible` / `disabled`, sharing rules and hook conditions all bind the record
 as a namespace only, so a bare name binds nothing, the expression evaluates
 to null, and the rule or action silently never fires. `validate` catches it
 before it ships. Measured on `@objectstack/cli` 17.2.0, mutating
 `duly_task`'s `skip_needs_reason` rule to `status == "skipped" && …` exits 1
 with:

 > object 'duly_task' · validation 'skip_needs_reason': bare reference
 > `status` — a formula/validation expression binds the record as the
 > `record` namespace, not at top level, so `status` resolves to nothing and
 > the expression silently evaluates to null. Write `record.status`.

 A misspelt **qualified** read is caught everywhere, flows included:
 `record.needs_colection` in a flow condition gives ``unknown field
 `needs_colection` on `duly_assignment` — did you mean `needs_collection`?``.

 **Flow node and edge conditions are the one exception — no gate at all.**
 They run in flattened scope, where a bare name may genuinely be a flow
 variable (a loop iterator, a `get_record` output, an assignment target), so
 the platform's `collectBoundRecordReads` deliberately never reads a bare
 identifier as a record reference. The same predicate written
 `status == "dispatched"` in a flow start condition passes `validate` with
 **exit 0**.

 *And in a flow the failure is not `null` either.* A bare `status` there
 **resolves** — to the flattened field, or to a same-named flow variable that
 was seeded first and **shadows** it. That shadowing case is the subtler bug:
 the predicate reads correctly and silently means something else. When a name
 resolves to nothing the engine **throws** (ADR-0032 §1c: no silent fallback —
 a non-`ok` result is a real fault, not a false condition). So on this one
 surface the outcomes are "silently means something else" and "loud runtime
 fault", never the quiet null of the record-scoped surfaces above.

 Filed upstream as **objectstack-ai/objectstack#14089**. Until it lands,
 `test/flow-predicates.test.ts` is a repo-local **stopgap** covering exactly
 the unguarded surfaces — flow node and edge conditions, walked over
 `dulyFlows`, with `dulyJobs` walked as a tripwire — and it is written to be
 deleted when #14089 ships, not maintained.
5. **Never store what you can filter.** No `is_late`, no `is_overdue`, no
 `is_open`. A stored flag needs a writer that runs every midnight; a formula
 field is virtual and a filter naming one silently matches nothing. Ask
Expand All@@ -98,6 +150,20 @@ rejects it. Use `position` (distribution), `permission_set` (capability),
 expected here, and not a bug to chase.
8. **English is the source language.** Every authored label gets an `en` entry;
 `zh-CN` is hand-translated. Do not hard-code display text in a hook or flow.
9. **Metadata first — a handler is the last resort, not the first.** This is an
 ObjectStack application. Objects, views, flows, jobs, datasets, permission
 sets and actions are the primary tools; a hand-written handler is what you
 reach for when none of them can express the thing.
 **Before writing a handler, check whether the platform already has a
 declarative way to do it.** The spec is on disk — `@objectstack/spec` ships
 its Zod sources — and the answer is usually a key you have not read yet.
 **If the platform genuinely cannot express it, file an issue against
 `objectstack-ai/objectstack` and say so on the card.** Do not quietly write
 around the gap. A workaround in application code is how a platform gap
 becomes permanent and invisible: it works, nobody upstream ever hears about
 it, and the next application writes the same workaround from scratch.
 `test/flow-predicates.test.ts` is what a *declared* workaround looks like —
 labelled a stopgap, pointing at objectstack#14089, and built to be deleted.

## Landing your work

Expand Down
Loading
Loading