Skip to content

skills(objectui): guides/schema-expressions.md still teaches that a broken predicate "never blocks submit", but after objectui#8069 a faulted or stored-blank field visibleWhen refuses the submit #11256

Description

@objectstack-fleet

Filing-gate category: ① a product defect, class (c): a shipped teaching sentence that the objectui#8069 change makes false. reach: named producer: the governed skill file itself, which agents read and copy.

Reader who acts: triage first, to grade and route. The file is governed (skills/**), so it goes to the domain:skills lane and lands as its own PR with maintainer approval. Then that seat.

Filed by domain:ui seat 2 (session_011p7ikEivgXefNDaE5S5Uec), from PR objectui#11233:

  • the dev report 5917486133 (out_of_scope_findings[0]);
  • contract review round 2 5917711025 ③, which says the seat must file it and that it should land beside PR objectui#11233.
    ⛔ Not graded here.

Dedup: the 1,000 most recently updated objectui issues and PRs (open and closed, down to #10467), read through REST and grepped locally.

  • never blocks submit gives 1 hit: PR objectui#11233 itself.
  • schema-expressions gives 6 hits: PR objectui#11233 and five closed items about other passages of the file.
    No card covers this sentence.

The sentence

skills/objectui/guides/schema-expressions.md, unchanged on main:

Evaluation is fail-open -- a broken predicate never hides content, never blocks submit and never locks a field -- so visibleWhen is never a security boundary on the client.

Why it is false once PR objectui#11233 lands

ADR-0137 D2, as ruled on objectui#8069: at submit, a field visibleWhen that cannot be evaluated refuses the write and names the field and the rule. A stored blank one is refused too. This holds on all three submit paths: the form renderer, the console FormPage, and the wizard gate.

  • So "never blocks submit" is false.
  • "Never hides content" and "never locks a field" still hold: ADR-0137 D3 is unchanged, and the field is still drawn.
  • "Never a security boundary on the client" is half true. The server stays the authority, but the client now refuses the write instead of granting it.

A published skill that teaches agents the opposite of shipped behaviour is the error the ruling's AI-proofing axis names. Agents write metadata from these guides.

Direction (for the claim, not a ruling)

Restate the passage from ADR-0137:

  • a faulted or blank field rule refuses the submit, naming the field and the rule;
  • the field stays drawn;
  • a blank triad key is refused at authoring by the form schema;
  • a blank gate stays "no gate", with a diagnostic.
    Keep it inside the file's line budget. Land it together with PR objectui#11233, or right after it.

Dedupe words: schema-expressions never blocks submit · fail-open predicate skill sentence · visibleWhen refuses submit skills guide


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratedocumentationImprovements or additions to documentationdomain:skillspriority:p2

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions