Finance and workforce

These optional facilities turn commercial and staffing decisions into dated cash, work and service consequences. They are configured per task and use the same accepted command journal, gameplay budget and finalizer as other worldseq mechanics. The values are authored simulation terms; public evidence supports the mechanisms without establishing exact customer responses or a generally applicable legal rule.

Collections

A collection case distinguishes an earned invoice, a bank receipt and the application of that receipt to the invoice. Correcting a purchase order or agreeing to a payment schedule does not itself receive money. Cash changes when a real receipt arrives; applying it reduces the corresponding unpaid claim once. Unapplied cash retains its liability until the contractual application is valid.

The published case gives invoice and receipt identities, required documentary work, payment dates, installment limits and any payment-system interruption. A valid plan must fund the required work and respect those dates while continuing ordinary service. Duplicate applications, overstated receipts and collection of the same principal twice are rejected by the independent reconstruction.

Vendor commitments

Vendor terms disclose the service period, actual usage meter, minimum charge, invoice date, renewal behavior and notice cutoff. Each period charges the greater of its contractual minimum and measured usage charge. Accepting two overlapping terms can create two obligations; a cancelled work commitment does not cancel an accepted contract.

A timely nonrenewal prevents a future term. It preserves the current term, existing payables and service duties. Ending an episode before an invoice date also preserves accepted but unbilled liabilities. Once the invoice exists, it replaces that accrued commitment in the outcome calculation instead of adding the cost again.

Vendor migration and added service capacity require their quoted work, lead time and cash. The player can inspect terms, actual invoices and remaining obligations in normal public company reports. SLA agreements additionally model restricted credits against a matching future vendor invoice. A vendor contract may explicitly name its billed company product with productId; its contract ID remains the vendor identity. Both the actual invoice and independent audit derive this association from the immutable contract. An SLA must match that vendor, product and eligible invoice period. If a required service group targets a product, it must agree with an explicit binding. Historical contracts without productId retain their contract ID as the invoice product identity; no field is added to those records.

Workforce

The roster gives named people, available hours, skills, arrival/departure dates, recruitment terms and explicit coverage requirements. Productive coverage depends on the required skill being available; a generic increase in headcount does not supply that skill.

Knowledge transfer consumes the mentor’s and trainee’s actual hours, as well as the relevant department capacity. Concurrent transfers share the same finite people. Recruitment incurs its quoted cost and lead time, and a new hire still needs the declared training before supplying missing expertise. Payroll, support and ongoing service continue during training.

Cancellation preserves incurred costs and completed transfer work. A later hire cannot erase a historical service breach. Public workforce reports expose the roster, outstanding transfer work and observed coverage so a participant can schedule work without access to the verifier’s private state.

Authoring and validation

Use scenario.collections, scenario.vendorContracts and scenario.workforce when preparing a company package. Their action effects, relational references, units and bounds are validated by the shared schemas and server. An omitted facility preserves an existing world’s representation. Objectives cannot refer to a facility’s metric unless the corresponding facility exists.

The public catalog composes these facilities into distinct operating contexts. A configuration count is not certification: each registered realization needs its own retained legal witness, information-fairness review and independent outcome check.

Focused controls cover duplicate receipt application, invoice/commitment replacement, notice boundaries, unavailable payment systems, shared mentor hours, recruitment without useful skill, and historical coverage failure. Source mutations additionally test that the verifiers detect economically meaningful corruption after envelopes have been rehashed. Full release qualification checks adapter parity and every registered instance under the recorded source and runtime identities.

The source records live in data/evidence/sources/gitlab-collections.json, vendor-commitments.json and gitlab-workforce.json. Each separates the documented rule from authored timing, capacity and behavior. Validation receipts, rather than this explanatory document, establish which guarantees have been demonstrated.