Loading...
Designed to refresh governed portfolio metrics from current operating records rather than relying solely on quarterly reporting cycles. The target-state capital layer would preserve the operator-authorized definition, governing source, reconciliation state, alternate valid values, and lineage for each consequential capital decision. It is pre-production architecture, not current operating performance.
When systems disagree, the operator governs.
Seven enterprise buyer contexts — each designed to read the governed value, definition, authority, and lineage the operator authorized for that decision.
Institutional trust markers
Multi-community operators, REITs, private equity, lenders, and multi-state portfolios evaluate the same nine markers before they sign. Each one is documented, enforced in the platform, and reviewable in the Trust-by-Design procurement package.
HIPAA-safeguarded controls; no SOC 2 certification or report claimed. No completed independent penetration-test report claimed.
HIPAA-safeguarded controls today: encryption at rest and in transit, BAA execution, PHI segregation, and signed-URL access to PHI buckets.
Operator-controlled definitions, source authority, reconciliation, and lineage across clinical, financial, workforce, compliance, and capital surfaces. Multi-tenant with database-enforced isolation.
A documented ingestion path for operator-supplied clinical, property, and accounting exports. Named-vendor connectors are ROADMAP; no third-party integration is live in operator production today. AI reads only the fields the operator declared readable.
SOC 2 in progress (underlying AWS infrastructure maintains its own SOC 2 reports), MFA required, session timeout, concurrent-session limits, continuous automated vulnerability scanning.
Immutable, append-only logs with UTC-millisecond timestamps, full user/session context, and 7-year retention.
33-role RBAC hierarchy. Property-level tenant and role gates enforced at the API layer (Fastify + tRPC on AWS) with WorkOS-authenticated sessions and defense-in-depth checks in PostgreSQL.
Holding Co → Operator → Region → Property → Unit hierarchy. Portfolio rollups computed from the Operator-Controlled Operating Record at request time. Designed for multi-state, multi-payer, multi-entity ownership.
Full detail on each marker, evidence inventory, and the Trust-by-Design procurement package live on the Trust Center.
A nurse closes a shift. A biller posts a payer. A med-tech reconciles a CoC count. The covenant rollup, the DSCR, the §856 income test, the predictive NOI, and the lease-coverage memo all read the same governed record, computed from the Operator-Controlled Operating Record at request time.
Status: designed target state — not operator production
This page describes intended capital-side architecture. No operator-production debt record, continuous lender view, predictive NOI result, filing, or assurance outcome is claimed. Evidence Record verified September 29, 2026.
It is a pre-production target-state architecture for authorized capital views. The operator determines which trusted definition governs each decision; the capital view preserves that authority decision, reconciliation state, alternate valid values, and lineage.
Governed entities the capital layer would read from after authority is declared.
IRC §856 income tests, covenant rollups, ESG metrics.
NOI bridges, hold-period thesis, exit-readiness diligence.
Operators have always been the day-one user of senior housing & care software. The enterprise buyer is changing. REITs and private equity own a growing share of the stock. Institutional allocators are setting hold-period and exit-readiness theses. Lenders require evidence between draw cycles, not at them. Regional and multi-state operators are professionalizing the spine that ties properties together.
What every one of these buyers asks for is the same thing: can I reconstruct why this definition and source possessed authority for this decision? Connected context helps, but it does not answer that authority question by itself.
Capital reads the value the operator authorized for the decision.
Epic organized healthcare around the patient record. SeniorCRE organizes senior housing & care around the operating record.
Covenant rollups, IRC §856 income tests, lease-coverage thresholds, ESG metrics across the portfolio.
NOI trend, agency-labor exposure, census movement, and portfolio standardization, each computed from the definition the operator declared for the hold-period thesis.
Audit-grade survey readiness, cross-property variance, capital-allocation decision support, exit-readiness diligence.
Property-by-property comparison, regional director visibility, shared-services rollups, multi-state licensing.
State-by-state regulatory variance, payer-mix shifts, MDS/PDPM accuracy across markets, surveyor-ready evidence.
Target-state covenant evidence, lease coverage, DSCR continuity, NOI bridges, and asset-level transparency under operator-approved definitions.
NOI-driver scenarios, governed risk signals, ESG reporting support, and traceable source lineage.
Target state: capital receives an authorized view of governed values, alternate valid values, definitions, and lineage for the decision at hand.
Shared governance policy across properties while independently authoritative clinical, labor, census, and financial systems may remain in place.
Target state: authorized capital views carry the applicable definition, authority, reconciliation status, and lineage. Freshness depends on the source and configuration.
Validation architecture demonstrates threshold signals and escalation paths; no operator-production alert performance is claimed.
Target state: governed workforce signals can be evaluated beside census and billing values without erasing each system’s appropriate authority.
Target state: NOI-driver analysis preserves the applicable occupancy, payer, labor, denial, and length-of-stay definitions with their source lineage.
Equity ownership is only half of the capital stack. Senior, mezzanine, bridge, agency, HUD 232/223(f), and construction debt all read from — and write back to — operator-governed capital decisions. The Debt object is a target-state governed entity in the capital-layer architecture.
The design can represent covenants, debt service, draw and reserve mechanics, reporting requirements, and maturity structure. Production use would require operator-approved definitions, authoritative sources, access policy, reconciliation rules, and acceptance testing.
| Field on the Debt object | What it carries |
|---|---|
| Loan record | Target-state fields: lender, instrument type, close date, maturity, balance, and accrual basis. Availability depends on operator-approved sources and acceptance gates. |
| Rate & pricing | Fixed / floating, index (SOFR, Prime), spread, all-in coupon, rate-cap or swap reference, reset cadence, current and forward effective rate. |
| Covenants | Target-state fields: DSCR, debt yield, LTV, occupancy floor, liquidity, leverage caps, headroom, and cure period under operator-approved definitions. |
| Debt service schedule | Amortization, interest-only window, balloon, principal paydown — projected forward and reconciled against the ledger at every period close. |
| Draw & reserve mechanics | Target-state fields for draws, reserves, escrows, and lockbox triggers, subject to source authority and human attestation. |
| Originator & servicer reporting | Target-state outputs include compliance certificates, rent rolls, operating statements, NOI bridges, and IRC §856 support, each subject to operator review. |
| Maturity ladder | Portfolio-wide maturity stack with extension options, refinance windows, prepayment penalties, defeasance, and yield maintenance computed against forward curves. |
| Guaranty & recourse | Sponsor guarantees, bad-boy carve-outs, completion guarantees, payment guarantees — scoped to entity and surfaced when a covenant approaches breach. |
In the target state, covenant evidence carries the applicable definition, source authority, reconciliation status, and lineage. No operator-production debt record or lender-reporting outcome is claimed.
| Layer | Reads | Writes |
|---|---|---|
| Operator layer | Target-state authorized resident, care-plan, ledger, shift, bed, and eMAR records | Target-state clinical and financial events under operator authorization |
| Asset management layer | Target-state governed property NOI, lease coverage, capex, and occupancy values | Target-state asset memos and hold/sell decision records |
| REIT / institutional layer | Target-state authorized portfolio, IRC §856, ESG, and covenant views | Target-state board, audit, and investor packets |
| Lender layer | Target-state authorized DSCR, debt yield, LTV, lease coverage, AR, and NOI views | Target-state draw-cycle and covenant attestations |
| Debt object | Target-state governed loan terms, covenant headroom, debt service, maturity, reserves, and guaranty scope | Target-state compliance certificates, draw requests, covenant cures, and refinance memos |
| Allocator layer | Target-state governed risk signals, NOI scenarios, and source lineage | Target-state capital deployment decision records |
In the target-state design, each layer would read through operator-approved roles and property boundaries, with access lineage preserved. Production isolation, logging, revocation, and export controls remain subject to operator acceptance.
Capital increasingly evaluates the quality of operating evidence. The thesis is that an asset whose consequential decisions can be reconstructed from governed definitions, authority, reconciliation, and lineage should be easier to diligence than one assembled only from periodic packets. SeniorCRE has not measured a value premium or operator-production capital outcome.
In the designed target state, the capital layer is an authorized view of the operator-governed record for a specific decision, not a second source that silently declares enterprise truth.
Status as of September 29, 2026 (last modified 2026-09-29)
| Claim | Evidence step | What is true today | Proof to inspect |
|---|---|---|---|
| Operator and portfolio workspace foundation built (roles, hierarchy, entity tree). | Validated | Provisioning controls have been exercised repeatedly in controlled SeniorCRE conditions, including the operator onboarding wizard. Not yet performed for an operator in production; no standard duration is published. | Control test record; synthetic or de-identified data; no operator PHI. |
| Single-community acceptance boundary. | Architecture designed | A gate sequence derived from the migration and acceptance model. No community has gone live for an operator, so no observed duration exists. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Portfolio-wide rollout acceptance across multi-community scope. | Architecture designed | A wave-cadence model from the deployment plan. Sequencing depends on community count, system count, data condition, source access, and operator authority decisions. Not a completed rollout. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Connectors to PointClickCare®, MatrixCare®, Yardi®, and QuickBooks®. | Validated | Ingestion and normalization exercised against synthetic and de-identified extracts in controlled SeniorCRE conditions. No third-party integration is live in operator production. | Control test record; synthetic or de-identified data; no operator PHI. |
| Operator-Controlled Operating Record: source authority, reconciliation, field-level lineage. | Architecture designed | The Operator-Controlled Operating Record is designed and not yet implemented in any community. Authority rules, reconciliation, and field-level lineage are design intent; synthetic examples do not establish working governance. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Clinical configuration: SeniorCRE as clinical system of record, or alongside an incumbent eMAR read one direction only. | Architecture designed | Designed, not built for operator use. SeniorCRE's native medication administration and eMAR are roadmap and not built; the read-only configuration alongside an incumbent eMAR depends on the Operator-Controlled Operating Record, which is designed and not yet implemented in any community. One authoritative medication record at all times is a design rule. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Barcode-verified administration with an automated five-rights check at the point of medication pass. | Architecture designed | Not built. Corrected September 7, 2026: earlier pages, operator training guides, and generated answers described this control as running, which was false. Implementation boundary: four of the five medication scan surfaces open a camera preview with no decoder and match only a manually typed NDC; one mobile surface decodes frames through the browser-native BarcodeDetector API where the browser supports it (Chromium/Android; not iOS Safari, not most desktops) and compares the NDC alone. No decoding library is bundled, no surface verifies resident, dose, route, or time, and no scan result blocks an administration. The five rights are verified by the administering clinician, not by SeniorCRE. | Build-queue entry with scope and dependencies. No implementation exists. |
| Live write-back into operator payroll and scheduling systems. | Architecture designed | Specified and in the build queue. Read-side ingestion only today. | Build-queue entry with scope and dependencies. No implementation exists. |
| Implementation effort required from the operator. | Architecture designed | Deployment is staged, not effortless: platform access, source access, authority rules, reconciliation, security review, and any history migration are scoped work with operator-side effort. Any claim of zero implementation would be false. | Written deployment plan and acceptance-gate model. No execution record exists. |
Status and evidence class as of September 29, 2026. SeniorCRE has no operator-production deployment. Public timing is gate-based and operator-specific; no standard go-live duration is published. Maintained and reviewed by John Hauber, Founder, SeniorCRE, LLC. A medication-safety control was described on earlier pages as running when it was not; that correction is published in full at /medication-safety-claim.
| Capability | SeniorCRE Capital Layer | Investor Portal (separate DB) | Operator-assembled packets |
|---|---|---|---|
| Source of capital-side metrics | Target-state authorized view | Copy on a schedule | Manual assembly |
| Metric latency | Target state; freshness disclosed by source and configuration | Hours to days | Monthly / quarterly |
| Covenant evidence between cycles | Target-state governed view | Snapshot | On request |
| Cross-property comparability | Governed definitions by decision context | Vendor-dependent | Spreadsheet-dependent |
| Audit-grade evidence | Designed access and decision lineage | Limited | No |
| Operator data sovereignty | Full export, revocable access | Vendor-held | N/A |
The operator chooses SeniorCRE for selected systems of record or supplies records from retained systems through supported ingestion. Named-vendor connectors are roadmap and not live in operator production.
Target-state roles would be scoped at the property level, with access and decision lineage subject to operator acceptance testing.
Target-state views carry definitions, source authority, reconciliation state, and lineage. Freshness depends on each source and configuration.
Validation architecture demonstrates threshold signals and escalation paths; production performance remains unproven.
The target state preserves operator authority and lineage in lender, board, audit, and capital-decision materials.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.