# Cobalt Operations Team

A fictional staff directory, paid-shift schedule and leave register with base-pay reconciliation.

All entities and transactions are fictional. Snapshot: 2026-09-08.

## Start with the linked model

1. Open operations.xlsx and review the Summary sheet. Source tables contain stable primary keys and declared references.
2. Change source values in the workbook to explore the calculated totals and editable chart.
3. Compare output values with expected-results.json. The JSON Schema checks types; primary-key uniqueness and joins also require the listed semantic checks.
4. Use invalid-records.json only in a local validation harness. Its three cases exercise duplicate keys, wrong types and an orphan reference.

## Included tables

| Table | Records | Primary key |
| --- | ---: | --- |
| employees | 8 | employee_id |
| shifts | 48 | shift_id |
| leave_requests | 4 | request_id |
| service_slots | 24 | slot_id |
| service_bookings | 18 | booking_id |

## Expected totals

- Paid hours: 336.00 hours. Sum shifts.paid_hours over the included records.
- Base pay: 9,072.00 USD. Sum shifts.base_pay over the included records.
- Employees: 8.00 records. Count unique employee_id values in employees.

## Platform mapping

primary-records.csv is a generic example table. It is not a native platform export. Where this kit includes a named profile, use that profile’s separate CSV and schema and review its compatibility level before uploading.

## Scope and assumptions

- Base pay excludes statutory overtime, payroll tax, benefits and deductions. This is a scheduling/import example, not a payroll compliance engine.