Skip to main content
The ownership model and truth-state doctrine on this page are durable architecture. Every branch, commit, environment, configuration, runtime result, and UI observation below is a historical 2026-06-19 Development snapshot, not proof of current behavior. The current contract (declared STRIPE_MODE, the per-obligation truth function, the real doors, the step that closes on confirmed_paid) is on Payment truth — current. See Current System State for present runtime identity and the dated Release Log checkpoint for the canonical historical record.

Canon Doctrine

Payment truth must preserve Lucia’s broader truth-state doctrine:
The 2026-06-19 snapshot did not claim production readiness, staging promotion, a full billing system, durable policy persistence, or Admin payment writes.

Purpose

Lucia payment truth separates:
The architecture chain is:
Property policy truthcalendar/booking temporal truthStripe movement truthLucia Core durable ledgerLIEA financial judgmentAdmin payment truth rendering
Definitions:
Boundary recorded at the 2026-06-19 checkpoint:

Historical Development snapshot — 2026-06-19

Evidence metadata:
Engine Development at the checkpoint:
Implemented at the checkpoint:
Engine capabilities recorded at the checkpoint:
Admin Development at the checkpoint:
Implemented at the checkpoint:
Durable Admin ownership boundary:
UI state recorded at the checkpoint:

Historical Lucia Core durable-storage snapshot

Public-safe configuration summary for the 2026-06-19 checkpoint:
Durable-storage contract:
Security posture:
Exact project identifiers, table names, row-security configuration, credential names, and runtime storage modes are intentionally omitted from public documentation. Checkpoint status:

Historical Development evidence — 2026-06-19

The example below is an explicitly synthetic fixture. Its original person-like label and numeric booking identifier are not part of the public record; this substitution does not change the recorded contract states or verification sequence. Synthetic-booking proof:
Admin Development UI evidence recorded at the checkpoint:
Property Payment Policy Baseline visible fields:

LIEA Attention Behavior

Implemented at the 2026-06-19 checkpoint:
Deferred at the checkpoint:

Property Payment Policy v0

At the 2026-06-19 checkpoint, Property Payment Policy v0 was visible in Admin as a draft-safe baseline only. Implemented at the checkpoint:
Not implemented at the checkpoint:

Checkpoint commits

Engine:
Admin:

Deferred at the checkpoint

Deferred on 2026-06-19:
Not claimed by the snapshot:

Next target recorded at the checkpoint

The next architecture target recorded on 2026-06-19 was:
That checkpoint proposed making policy truth durable before LIEA was asked to reason about deposit timing, final balance due dates, overdue state, partial payments, or property-specific verification rules. Verify present implementation and priorities through Current System State and owning source rather than carrying this historical next step forward.

See Also