<!-- ephemeral -->

# TypeScript Assist — Update `System Platform`

Load the current row and its original optimistic version. Never reconstruct an
entity from an ID/version supplied by a client. Trusted runtime and policy state
comes only from `UserContext`.

An entity update is not a partial DTO patch. Load every scalar field before
modification so checker rules can validate the complete business state. Never
use `WithMinimalFields()` or a reduced projection for an entity that will be saved.

```typescript
import { UserContext } from '../teaql-ts';
import { Q } from './Q';
import { Platform } from './models/Platform';

export interface UpdatePlatformInput {
    name: string;
    createTime: string;
    lastUpdateTime: string;

}

export async function updatePlatform(
    id: string,
    input: UpdatePlatformInput,
    context: UserContext,
    throwIfMissing = false,
): Promise<Platform | undefined> {
    const entity = await Q.platforms()
        .withIdIs(id)

        .comment('what: load current System Platform for update')
        .purpose('why: preserve original version for optimistic locking')
        .executeForOne(context);
    if (!entity) {
        if (throwIfMissing) throw new Error('System Platform not found: ' + id);
        return undefined;
    }

    entity.updateName(input.name);
    entity.updateCreateTime(input.createTime);
    entity.updateLastUpdateTime(input.lastUpdateTime);

    await entity
        .auditAs('Update System Platform for the requested business operation')
        .save(context);
    return entity;
}
```

Compile the source unchanged. Prove persistence and query-back, a conflict from
an independently loaded stale copy, undefined and throwing not-found behavior,
missing/blank audit rejection, and compilation failure for unknown or trusted
fields. Constant and relation updates require an explicitly selected generated
method; do not invent a generic setter.


---

## TeaQL seven-language assist contract

Apply the verified Rust semantic ceiling while using only the exact TYPESCRIPT generated and
runtime APIs. Discover APIs through the generated application AGENTS.md and progressive
model-aware Assist. Do not inspect generated domain-library source.

- Do not create plurals by appending `s` or `es`; use the centralized generated plural.
- Human and non-human entities use different generated predicate vocabularies. Preserve
  forms such as “who are active” and “whose email is”; never infer them from English.
- Configure filters, projection, paging, and other query options before `purpose(...)`.
  Comment may appear anywhere in the chain. Purpose enters the executable stage; execution
  requires both values, but comment does not have to immediately precede purpose.
- Every execute/list/stream and every save accepts exactly one context argument:
  `UserContext`. Name that argument `context`, never `runtime`; data services and global
  policy are injected when the context is built. Reserve `runtime` for process-level
  runtime ownership, provider/pool setup, and module assembly.
- Tenant, merchant, identity, permissions, request policy, purpose policy, hard limit,
  and continuous-page cursor policy come only from trusted context, never dynamic JSON or TFP.
- If the required operation is absent after current entity/action and required field
  Assist, stop that path and report MISSING_ASSIST. Do not guess an API or search the
  generated library as a fallback.
- Create each application-owned source file once. After its first compile attempt,
  repair only the smallest block identified by the exact compiler or test diagnostic.
  Preserve unrelated code; do not rewrite the complete file as an error-recovery loop.
- Before a repair that would replace more than 25% of an existing application file,
  stop and report LARGE_REWRITE_REQUEST with the file, exact diagnostic, reason, and
  estimated scope. Initial creation and model-driven regeneration are not repairs.

Capability: `update`.

- Load the tenant-scoped current entity first so its original version participates
  in optimistic locking; do not reconstruct versioned state from untrusted JSON.
- Allow-list writable fields, attach the generated audit-reason API, and save with
  the same UserContext. Add a stale-version rejection test.