Actor definition from requirements analysis this provider authorizes.
Authorization providers have no API endpoint; the actor is the generation key and supplies the name used when rewriting the provider's imports.
Generated provider source after query placeholders are materialized into Prisma calls.
Consumed directly as the on-disk file content, so this always holds the final TypeScript. The language-neutral form is carried in placeholderContent + queryIR.
File path where the provider function is generated.
Format: "src/providers/authorize/${name}.ts" Example: "src/providers/authorize/adminAuthorize.ts"
Provider function name in {actor}Authorize camelCase format (e.g.
"adminAuthorize", "customerAuthorize").
OptionalplaceholderProvider source before query placeholders are materialized into Prisma
calls. Holds the __AUTOBE_QUERY_IR:* placeholder form referenced by
queryIR.
OptionalqueryCanonical query calls referenced by placeholderContent.
In practice always present (the provider always reads the actor/session
record), but kept optional for parity with operation functions and so the
materialize helpers can branch on queryIR?.length.
Provider return type fixed by the deterministic decorator/payload stage.
This is the {Actor}Payload type name the provider returns, recorded as
the contract used when generating and validating the implementation. Mirror
of AutoBeRealizeOperationFunction.returnType.
Type discriminator for authorization provider function.
Authorization provider function implementation.
Represents the generated
{actor}Authorizeprovider that verifies the JWT, narrows the actor's{Actor}Payload, queries the actor/session record for enrollment and business-role (grade) checks, and returns the payload. It is a first-class member of AutoBeRealizeFunction so it rides the same queryIR write/correct/materialize machinery operation providers use — the single role-check database read is expressed as queryIR and protected by the deterministic IR auto-correction loop.Unlike AutoBeRealizeOperationFunction, an authorization provider is keyed by its actor rather than an endpoint, and its return type is the deterministically generated
{Actor}Payload(not an API response DTO). The matching decorator and payload are generated deterministically and live on the owning AutoBeRealizeAuthorization.Author
Samchon