<!-- ephemeral -->

# Python Assist — List page `System Platform`

Use the exact generated entry point and APIs below. The result is a typed page
with exact filtered `total_count`; generated client code cannot override the
runtime's fixed 10,000-row materialization ceiling.

```python
from Q import Q
from models.platform import Platform
from teaql.core.list import TeaQLPage

async def list_active_platform_page(
    context, offset: int, limit: int
) -> TeaQLPage[Platform]:
    return await (
        Q.platforms_minimal()
        .select_name()
        .select_create_time()
        .select_last_update_time()
        .select_merchant_list()
        .order_by_id_ascending()
        .comment("what: list the active System Platform page")
        .purpose("why: serve the authorized System Platform directory")
        .execute_for_page(context, offset, limit)
    )
```

Compile and execute this source unchanged. Rows and count share the exact
generated and trusted-policy filters. Count excludes projection, relations,
ordering, offset, and limit. Reject negative offsets, limits outside
`1...10000`, unknown filters/sorts, missing intent, raw query dictionaries, and
every generated-client attempt to call `hard_limit`.

---

## TeaQL seven-language assist contract

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

- Validate offset, page size, filters, deep paths, IN-list size, and sort against
  explicit allow-lists. Reject invalid input instead of widening the query.
- Use a stable unique ordering and retain the runtime hard limit. Continuous-page
  optimization is opt-in, browsing-only, local runtime policy and cannot cross TFP.
- Run count only when explicitly requested; otherwise use the returned list length.