Concepts/Concept

Start with plausible-looking success

An agent can draw a convincing diagram while leaving dangling relations, wrong ownership, duplicate objects, or an empty change set in the model repository. A post-write model critique arrives after the shared engineering state has already been changed.

Definition

A structural write-back gate sits between candidate plans and the formal engineering repository. Before side effects, it checks that:

1. the scope exists, is unique, and is writable;
2. element, relation, and diagram types are legal;
3. every relation endpoint resolves;
4. explicitly named items are complete;
5. the view is a subset of accepted model results;
6. the write produces an observable delta, otherwise it is NOOP;
7. repository and view updates use one write channel and produce a receipt and rollback handle.

The result is one of APPLIED, APPLIED_WITH_WARNINGS, BLOCKED, or NOOP.

Boundary

The gate checks programmatically decidable structure. Naming quality, modeling granularity, and design judgment may still require pre-write review, generation critique, or offline evaluation.

Provenance

• Initial research source: the AI4MBSE personal research project by Liangding Yuan; synthesized by ADPS from the published mechanism.
• Lineage: admission controllers, database constraints, preconditions, and transaction validation.
• ADPS contribution: applies those controls to agent-generated engineering structures and connects the decision to write-back receipts and user-visible outcomes.
• Definition status: ADPS restatement.