# Case schema and limits

`initial_state.json` is the initial machine-readable world. `DOSSIER.md` and sixteen `documents/Dxx.md` files supply the ordinary meanings, purposes, refusals and uncertainties. `baseline_checks.json` is the author's arithmetic witness, not independent verification. `QUESTION_INDEX.md` contains question themes only. Initial answers live outside this folder in mediator-only `release/initial_response_cards.json`. Future material remains sealed until the protocol release.

## Time and resources

- Twelve dated weeks W01–W12; initial decision window W01–W03. Later windows are W04–W06, W07–W09 and W10–W12. Fixed deadlines are the end of the stated week; day-level timetables are deliberately outside this model.
- Vessel `weekly_capacity_days` is the weekly maximum, overridden only by a released exact resource/week value. `daily_cost` is cash cost per attempted vessel-day. `service_types` and each commitment's `allowed_vessel_ids` must both permit work.
- Person `weekly_capacity_days` includes operational assignments plus extra administrative/support time. P01 and P02 each have only0.5 additional day: their ordinary work is already reserved. Operational people each begin with5 available days. P09–P12 are external voices; their granted review attention must be separately recorded, not assigned as operational labour.
- A vessel allocation requires exactly one qualified skipper and one distinct qualified deck person for its full duration. Their vessel qualification is explicit in `skipper_vessels`/`deck_vessels`. At least one assigned person must hold every required team capability. No implicit relief crew, hiring, cross-training or vessel substitution.
- Voyage work is indivisible, in half-day units. Optional `support_allocations` use eighth-day units (one hour in this model), count against the same person's cap and need any applicable personal role permission. A role without booked effort is not free.

## Commitments and status

Every original C001–C048 remains identifiable throughout. The original customer, islands, type, window, duration, capability and cash terms are retained as the reference. `status: authorised` means an existing obligation; it never means performed. Later offered N rows are optional until permission-backed acceptance. Unaccepted offers earn no money and create no delivery obligation. Inquiries are neither work rows nor revenue.

A submission retains each commitment with its current disposition and permission-backed amendments. It carries unique allocations, full crew, week and status. `scheduled` is prospective; `simulated_performed` requires the protocol's explicit simulated performance receipt. Neither proves real work. A `failed` declared full attempt uses its stated time/cash but earns no success receipt. Multiple failed attempts may coexist with one later successful/scheduled fulfilment; never two successful fulfilments. Unperformed due obligations remain visible as unmet; changing a label does not cure them. Each amendment names an exact returned permission and records the decision week.

Existing flexible staff assignment within the same customer promise needs no customer grant. Changed promises do. Permission issuer IDs, subject IDs, actions, exact field changes, validity weeks and conditions all matter. Human wording is not mechanically exhausted by JSON. A permission supplied on a question card is conditional authority only; the arm must choose it and evidence its conditions.

## Cash

Currency is whole GBP in this fictional model. Start with£18,000. For every week fromW01 onward, subtract£1,800 overhead, every attempted vessel allocation's days times vessel daily cost, and that work's extra cost. Add a completed work unit's revenue once, at the later of its receipt week and actual completion week. Add signed released cash adjustments once by unique ID. End each week at or above£6,000. Negative signed adjustments are expenses/refunds. There is no intraday liquidity or borrowing model. Prospective cash from a scheduled successful job is a forecast, not a received payment. Conditional retainer/other cash is materialized only under the frozen predicate rules; never invented by an arm.

## Meaning and enactment

The submission schema is specified by the independent evaluator contract. Its five surfaces are service/intake, responsibilities, current work, knowledge and agreements; unchanged with a reason is valid. Carry NF01–NF04 in the nonfinancial promise ledger with references. A mechanically valid ledger does not establish that the relevant purpose, uncertainty, objection or promise has survived. Record independent estimates and personal refusals as attributed facts. Better scheduling, declining optional work and retaining the present organisation are legitimate, with no novelty penalty or bonus.

## Deliberate exclusions

This is not a route, seamanship, safety, legal, labour-law or scientific-validity model. No real island, person or organisation is represented. No stochastic weather or unlimited off-card conversation exists. Customer satisfaction and human saved time are unknown unless a released observation actually supplies them. A frozen card can authorize a bounded fictional decision; it cannot stand in for real participation. The experiment tests coherent choices and continuity within this authored world, and can expose failures rather than establish real organisational benefit.