The trust engine. New `verif` schema (5 tables) + a data-driven verification
pipeline: steps are rows (6 seeded step-types), not a code enum.
- nurse_verifications.status is the single source of verification truth;
nurse_profiles.is_verified is flipped ONLY inside the finalize transaction
(VerificationAggregator: tracked verification + tracked profile -> one commit)
and reversed on suspension/expiry — no in-between state.
- is_automated snapshotted onto each step at submit; steps seeded from active
required step-types; automated runs (identity-KYC, Shahkar, IBAN ownership)
find their step by code.
- users.national_id populated only on identity-KYC pass; Shahkar + IBAN owner
compare against it (money-mule guard); shared-SIM -> shared_sim support alert.
- Documents are metadata-only behind signed URLs; credential_number encrypted
and never serialized; public trust badge exposes credential TYPES, not numbers;
holder-name cross-checked against the verified identity before recording.
- Admin-triggered credential-expiry scan reverts lapsed steps, re-gates
bookability, raises a verification_expired alert + verification_expiry_prompt
notification (scheduled cron deferred; config key
verification_expiry_scan_cadence_hours).
Three new mock vendor seams (IShahkarVerifier / IIdentityKycProvider /
ICredentialVerifier) behind DI; reuses b3 IBankAccountOwnershipVerifier and
b0 IObjectStorage/IFieldEncryptor. 15 endpoints across 4 controllers.
Two migrations (tables + step-type seed). 154 tests pass, zero new warnings.
Contract dev/contracts/domains/verification.md + swagger snapshot refreshed;
handoff/report/mocks-registry updated.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds the province -> city -> district reference hierarchy (geo schema,
seeded with 31 provinces + capital cities + Tehran's 22 districts),
nurse service areas (district_id NULL = whole city, filtered-index-pair
uniqueness -> 409), and encrypted, geocoded customer addresses with a
single-primary invariant. Introduces the IGeocoder seam (mocked) and
409 Conflict on the result envelope. Public cascading lookups are cached
behind a generation-token scheme with invalidate-on-admin-write.
One EF migration (GeographyAddressesServiceAreas, applied). Contract +
swagger snapshot + handoff/report/registry updated. 103 tests pass.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Lay the cross-cutting platform backbone every later phase reads from. Adds
the first marketplace EF migration baseline (new `ops` schema) and the
mechanisms b2..b15 reuse: typed runtime config, an append-only audit trail,
an analytics event log, the holiday/bank-closure calendar, in-app
notifications, and the internal support-alert worklist.
Schema & migration
- New `ops` schema + migration InitialMarketplaceBaseline with 6 tables:
PlatformConfigs (IAuditable), AuditLogs (append-only), SystemEvents,
IranianHolidays, Notifications, SupportAlerts — with indexes/uniques and
FKs to usr.Users. Seeded 12 config keys + 7 sample holidays via HasData.
Domain / Application
- IAuditable marker + [AuditRedacted] attribute; entities + string-code
constant holders (config data_type, holiday type, alert type/severity/status).
- Facade contracts: IPlatformConfig, IHolidayCalendar, IAnalyticsSink,
IAuditLogger, INotificationService, ISupportAlertService; DTOs +
PagedResult<T>; evolved the INotificationDispatcher.Notification record to
carry Type + DataJson; Pagination helper.
- 14 CQRS commands/queries (+ validators) wiring the endpoints to the facades.
Infrastructure
- DB-backed facade implementations in Persistence/Services/; real in-app
INotificationDispatcher (removes the b0 log stub); notification-retention
hosted service (purge is_read=1 AND age>90d).
- Extended AuditFieldInterceptor to also append an old/new-diff audit_logs row
for every IAuditable change in the same transaction (PII redacted).
- Registered all facades + hosted service in AddPersistenceServices; removed
the dispatcher registration from AddCrossCuttingSeams.
API
- 5 controllers: admin PlatformConfig/Holidays/Audit/SupportAlerts
([Authorize(DynamicPermission)]) + current-user Notifications ([Authorize]),
all tenant-scoped and paginated. 16 Swagger paths total.
Money-correctness & safety rules honoured
- Config read at compute time (cached, parsed by data_type), never hardcoded;
every config change is audited in the same transaction; audit_logs is
append-only (no update/delete path); support alerts are admin-only;
notifications are tenant-scoped; analytics is fire-and-forget.
Tests & docs
- 18 new foundation tests over in-memory SQLite (config typing + audit,
holidays, notifications + tenancy + retention, support alerts, analytics);
build clean (0 new code warnings), 22 tests green; migration applied to the
dev DB and swagger.v1.json refreshed.
- Updated server Project map + CONVENTIONS, product data-model doc 12 (seeded
config defaults), config-reference contract, mock registry, backend handoff/
STATUS/report.
Follow-ups: add FK constraints for SupportAlerts.BookingId (b9) and ReviewId
(b14) when those tables land.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
hamid