<!-- ephemeral -->

# Create `Platform` with the generated .NET API

Read `Generated/Requests/PlatformRequest.cs` and
`Generated/Models/Platform.cs` before implementing business input
mapping. Allow-list writable fields; never mass-assign untrusted JSON.

```csharp
using System.Threading.Tasks;
using Generated;
using Generated.Models;
using TeaQL.Core;

public static class PlatformCreateService
{
    public static async Task<Platform> CreateAsync(UserContext context)
    {
        var entity = Q.Platforms()
            .Comment("initialize an authorized System Platform")
            .Purpose("create System Platform")
            .NewEntity(context);

        // entity.UpdateName(value); // allow-listed business input
        // entity.UpdateCreateTime(value); // allow-listed business input
        // entity.UpdateLastUpdateTime(value); // allow-listed business input

        await entity
            .AuditAs("business reason for creating System Platform")
            .SaveAsync(context);
        return entity;
    }
}
```

`Purpose(...)` enters the executable stage and `NewEntity` accepts exactly one
context argument, `UserContext`. Add a negative test proving an empty audit
reason cannot write. Output C# that uses the exact generated updater names.


---

## TeaQL seven-language assist contract

Apply the verified Rust semantic ceiling while using only the exact DOTNET 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: `create`.

- Validate and allow-list writable business fields; never mass-assign dynamic JSON.
- Create through the generated request/entity API, attach a non-empty audit reason,
  save with the same UserContext, and return the runtime's native save result.
- Add a negative test proving a missing audit reason cannot write.