Rempla Docs

Three-tier catalog (Product → Variant → VendorOffer), late-bound vendor resolution for long-horizon plans, frozen promised prices, and domain boundaries. Version 1.

How person-to-person relationships, chain computation, and family grouping work in the Planning Tree. Version 2.

The person-centric model: structural relationships, plan roles, and estate designations.

All 42 tables with every key and foreign key, generated from the EF model. Large — zoom and pan.

The five contexts, patterns the schema repeats, known drift, and when to regenerate.

The product, vendor, offer, and order tables at full column detail — the zoom on the map above.

What the diagram encodes, enums vs lookup tables, known drift, and when to regenerate it.

Living reference of all entities, relationships, and business rules.

Tech stack, infrastructure, and system architecture.

Executive strategy, market opportunity, and revenue model.

Detailed relationship types, grouping rules, and tree rendering logic.

Rempla composes and sends nothing itself, and nothing it causes to be sent goes through the outbox. Replaces Notification.DeliveryId with a polymorphic subject so a protector invitation has somewhere to point, makes a message per-party per-channel so partial failure is visible, and adds inbound as its own table — a bounce, an opt-out and a protector's answer are not states of the message we sent. Draining becomes an explicit job, and the drain, not the customer's click, is what may report a message as sent. Amended 2026-09-10: §1 and §2 are built and migrated; the sending identity is notify.rempla.com, chosen because the root domain's SPF is a hard fail authorizing Outlook alone; and the drain job has no host, because nothing in the solution runs in the background and IIS recycles what would.

Promoting the protector from a bare role edge to a designation with a status, its own snapshotted contact, an annual clock, and event-scoped confirmation rows. ADR-004's account-level edge was right and is kept as a projection. Unresponsive is derived from the clock, never set by hand; removal is a transition, not a delete. The verification engine that consumes a confirmation is named and deferred. Amended 2026-08-31: the stored status drops Unresponsive to a derived standing, and the backfill is Pending-never-invited rather than Accepted.

Replacing the constant VendorProduct.Availability with a Delisted state our own catalog sync infers when a product leaves the feed — and only from a provably complete read. "Not offered" bubbles up to the product as a derived state that never rewrites operator-owned Status. Vendor capabilities split into operator-recorded, observed-and-cached, and per-order questions stored nowhere.

Splitting VendorOfferStatus into a sync-owned availability and an explicit Product.ActiveVendorOfferId selection that replaces Priority. Routing fails closed rather than silently substituting a vendor and its price. Amended 2026-08-12: the per-offer disabled flag is removed — vendor status and selection already covered it.

VendorProduct as a staging tier outside the catalog, joined to VendorOffer by an explicit human bind act. Amended 2026-07-30: bind is a product-side act searching the whole vendor catalog by vendor and category; bulk-create deferred.

Images in a Rempla-owned root outside the web roots, the database holding only a category-relative path, with ICatalogImageResolver as the single seam to the delivered URL.

The Scheduled Gift plan-domain aggregate (CustomerScheduledGift + ScheduledGiftTransaction), mirroring the Vault flow; recurrence, anchors, and the Rempla Gift Reserve. Amended 2026-08-12: the gift is always paid in full at signup, designing out the instalment under-funding risk.

Turning a scheduled occurrence into a Delivery — vendor routing, the fulfillment port, and Reserve accounting. Amended 2026-07-21 with the layered vendor-integration model: config for transport, code for meaning. Amended 2026-08-17: a purchase-time vendor snapshot on the transaction, so processing becomes a best-match comparison — the customer is never charged more, which is exactly why the underwritten cost must be recorded. Records why an offer is not frozen once ordered against: mutable catalog, immutable documents that copy what they need.

Canonical Rempla style guide — logo system, mark, color palette (navy, gold, slate), typography (Arno Pro + Futura), pattern library, logo-use rules, and application mockups.

Transparent logo mark — gold tulip icon for use as favicon and brand identifier.

Early BSG brand ideation — logo concepts, palette explorations, and visual direction that preceded the 2026 style guide.

Full website mockup — landing page, hero, features, and marketing copy.

Remembrance Planning explainer — what Rempla does and what Remembrance Planning means.

Multi-step flow mockup for adding a scheduled gift — person, occasion, product selection, and scheduling. Latest design handoff.

Multi-step flow mockup for adding a vault box — box selection, contents, and delivery configuration.

Matt Kelly's original HTML prototype — onboarding, planning tree, dashboard, and AI assistant concepts.

Original PowerPoint process flow for scheduled gift delivery.

Original PowerPoint process flow for the vault box concept.

Development application environment — latest in-progress features and changes.