Worked example · 05
One session interrupted is still one occurrence
Should splitting time create extra state transitions?
Midday · shared learning with a break
A single synthetic learning occurrence is captured as two contiguous time slices around a break, with one source attestation and one impact decision.
This is a synthetic variation on the paper’s redacted public worked day. It teaches a branch of the model; it is not a private record, observed personal event or empirical finding.
World 03 / 03
Record Integrity Lab
Performance · two slices · one occurrence
Short answer
No. Duration can unite across slices while transition count remains one.
01 · Moment
Observed time slice
A bounded event with context and provenance.
02 · Economic question
Vcom 1000
Typed VC output: 700
03 · Human question
+0.021 WellbeingScore movement
Wbefore 700.000 → Wafter 700.021
Show the calculation
Four questions, in order.
- 01
Start with the prior state
The event reads Wbefore = 700.000.
- 02
Ask the economic question
Validated rate × duration produces Vcom = 1000 hypothetical credits.
- 03
Ask the human-state question
The reviewed input produces deltaW = 0.021, so Wafter = 700.021.
- 04
Keep the units honest
VCperformance = (Wbefore / 1000) × Vcom = 700 hypothetical credits.
What this means
The slices contribute to one non-overlapping duration union because they share the occurrence and source attestation.
What it does not mean
Separate activities cannot be merged merely because they happened near one another.
Scenario structure
Follow the integrity rule.
- 01
Slice one + slice two
- 02
One shared occurrence
- 03
One duration union and one transition
Technical layerAudit the calculationInspect statuses, intermediate values, provenance, uncertainty and raw scenario structure.
- Source settlement
- final
- Impact review
- applied
- Replay eligibility
- eligible
- Valuation
- valued
- Projection
- canonical
- Wbefore
- 700.000
- Component delta
- 0.07
- deltaW
- 0.021
- Wafter
- 700.021
- Vcom_event
- 1000
- VCperformance_event
- 700
Pinned implementation calculation
Complete component-transition trace
Every input and intermediate value is carried by the stable synthetic fixture or derived from its pinned issuer-policy snapshot.
- Components before
- { "Physiology": 700, "Emotion": 700, "Feeling": 700, "Thought": 700, "Habit": 700, "Performance": 700 }
- calculated_Wbefore
- 700
- Affected component
- Performance
- component_before
- 700
- Band
- (600,700]
- band_rate
- 0.03
- adjustment_factor
- 0.005
- Direction
- positive
- Intensity
- medium
- intensity_multiplier
- 2/3
- maximum_move
- 0.105
- calculated_component_delta
- 0.07
- component_after
- 700.07
- component_weight
- 0.3
- calculated_deltaW
- 0.021
- calculated_Wafter
- 700.021
- Typed Vcom_event
- 1000
- Typed VCperformance_event
- 700
maximum_move = 700 × 0.03 × 0.005 = 0.105
component_delta = 0.105 × 2/3 × 1 = 0.07
component_after = 700 + (0.07) = 700.07
deltaW = 0.07 × 0.3 = 0.021
Wafter = 700 + (0.021) = 700.021
Vcom_event = validated rate × validated duration = 1000
VCperformance_event = (700 / 1000) × 1000 = 700
Required case note
Impact justification
- Assumed synthetic evidence
- Two contiguous synthetic slices share one occurrence and one source attestation; a single reviewed positive-medium impact input belongs to the occurrence.
- Reviewed decision input
- positive · medium once per occurrence
- Calculation demonstrated
- The calculator applies the pinned HouseOfBros Founder Policy v0.1 transition matrix to the declared component state. It does not infer direction or intensity from the evidence narrative.
- Decision rationale
- Duration unions across slices, while transition cardinality remains one.
- Alternative interpretations
- Separate occurrences would require separate decisions.
- Uncertainty
- This synthetic case has not been calibrated against observed longitudinal evidence or independent reviewer agreement.
- Evidence-to-intensity rubric
- unvalidated. Direction and intensity are reviewed inputs; the calculator does not infer them from prose.
- Validation research required
- Occurrence-linkage and duplicate-transition conformance tests.
Raw scenario structure
Slice union and one occurrence
Two slices form one non-overlapping duration union. Their shared occurrence and source attestation permit one—and only one—wellbeing transition.
{
"occurrence_id": "occ-split-001",
"source_attestation_id": "att-synthetic-001",
"slices": [
{
"id": "slice-a",
"start_at": "2026-01-03T09:00:00Z",
"end_at": "2026-01-03T10:00:00Z"
},
{
"id": "slice-b",
"start_at": "2026-01-03T10:00:00Z",
"end_at": "2026-01-03T11:00:00Z"
}
],
"duration_hours": 2,
"transition_count": 1
}