Rulvar

Appearance

Rulvar API reference

Rulvar API reference / @rulvar/rulvar / ExecutionScope

Interface: ExecutionScope ​

Defined in: packages/core/dist/index.d.ts

The bounded execution scope of one run (RV4007, the fifth comparison experiment's P0.4): WHO this run executes for, as the host names it. The library CARRIES the scope without loss (RunMeta, a genesis journal decision, the invoice header, the export bundle via its meta) and asserts identity on resume; it never interprets it. Tenancy semantics, entitlement, and isolation policy are host decisions: this is an attribution envelope, not IAM.

Properties ​

PropertyTypeDescriptionDefined in
account?stringThe billing account within the tenant.packages/core/dist/index.d.ts
legalDomain?stringThe governing legal domain (RV4205, the sixth comparison experiment's P0.2): host-defined vocabulary (a jurisdiction, a regulatory regime), the first of the three named dimensions the experiment's question bound to routing and audit.packages/core/dist/index.d.ts
project?stringThe project or workload name.packages/core/dist/index.d.ts
providerAccount?stringThe provider-side billing account identity, host-defined (RV4205).packages/core/dist/index.d.ts
region?stringThe deployment or data-residency region, host-defined (RV4205).packages/core/dist/index.d.ts
sponsor?stringThe sponsoring principal of the work (RV4408, the seventh comparison experiment's benchmark domain): the party on whose behalf and at whose expense the run executes, distinct from the OWNING tenant and the BILLING account. The Aster adjudication shape is the motivating example: a network operator (tenant) adjudicates a trial financed by a study sponsor, and the sponsor identity must ride attribution, the invoice header, and the regulated posture hash without being conflated with billing. Host-defined vocabulary, like every dimension here.packages/core/dist/index.d.ts
tenant?stringThe owning tenant or organization, host-defined.packages/core/dist/index.d.ts