Tested foundations
The first-field foundation covers tenancy, access, audit history, definitions, lineage and a census adapter. Controlled tests are not operator-production evidence.
Loading...
Founding Operator Program
SeniorCRE® · First governed-field phase
First governed occupancy proof
One occupancy figure. Operator-defined authority. Evidence a reviewer can trace to source.
This is the proof specification for the $50,000 foundations and first-field phase—not a completed proof, live product demonstration or commitment to all Pilot One.
Acceptance requirements · No passed first-field acceptance or independent operator review is claimed.
Current readiness · October 16, 2026
Component status describes controlled-environment progress only. The Operator-Controlled Operating Record as a whole is designed and not yet implemented in any community as of October 16, 2026; no operator-production deployment or measured operator outcome is claimed.
Review the current maturity and security disclosuresWhat the first phase must produce
The public scope follows the program’s statement of work: foundations and the first governed-field segment through its calibration checkpoint. Confidential engineering documents are not published here, and an engineering scope is not a participant agreement.
One governed occupancy figure
A defined occupancy field with preserved source assertions, visible disagreement, an operator-defined authority rule and reconciliation. Not a portfolio-wide deployment.
Independently traceable evidence
A board-reviewable artifact whose governed figure can be walked back to its source rows by a reviewer outside the build team. The review is an acceptance requirement, not a completed review.
A deliberate checkpoint
Review the foundations and first-field exit tests, then calibrate the next segment on measured delivery pace. Nothing beyond this checkpoint is included or pre-committed.
The acceptance requirements
These are requirements to satisfy, not badges of completion. Detailed tests, responsibilities and the acceptance decision must be agreed before work begins.
- 01
Test the foundations
Confirm tenancy, access, audit history, definitions, lineage and the census adapter through the agreed first-phase exit tests.
Evidence required · Not yet accepted
A recorded test result for the agreed foundations and first-field scope, with unresolved exceptions retained.
- 02
Define the occupancy field
Agree what counts as occupied, the unit of measurement, the denominator, reporting cut-off and decision context before computing the figure.
Evidence required · Not yet accepted
The approved, versioned field definition and its accountable operator owner.
- 03
Declare source authority
Name which source governs this field for this decision context and who can approve the rule. A different context can legitimately require a different value.
Evidence required · Not yet accepted
An operator-approved authority rule, its effective version and the source assertions it governs.
- 04
Reconcile without erasing evidence
Preserve the original source assertions, identify disagreements and apply the agreed definition and authority rule. Keep unresolved exceptions visible.
Evidence required · Not yet accepted
The resulting determination, the applied rule and the explanation for each included or excluded source row.
- 05
Walk the figure back to source
A reviewer outside the build team must be able to independently trace the governed occupancy figure back to its source rows.
Evidence required · Not yet accepted
A board-reviewable evidence artifact with source references, definition and rule versions, reconciliation and decision lineage. Review is required, not completed.
- 06
Stop at the checkpoint
Review the first-phase exit tests and trace-back result, then calibrate any proposed next segment using measured delivery pace.
Evidence required · Not yet accepted
A recorded acceptance decision or an explicit list of unmet criteria. Later work requires separate scope, funding and approval.
What belongs in the evidence artifact
A board-reviewable figure is more than a dashboard total. A reviewer must be able to follow its definition, source rows, authority and reconciliation. The outline below is a required evidence structure, not an export from working software.
- Decision context
- The decision this occupancy figure is permitted to support.
- Field definition
- Numerator, denominator, counting unit and reporting cut-off, with definition version.
- Source assertions
- Original values and source-row references, preserved rather than overwritten.
- Operator authority
- Accountable owner, approved source rule, effective version and approval record.
- Reconciliation
- Disagreements, rule application, included/excluded rows and unresolved exceptions.
- Determination and lineage
- The governed value and a traceable path through source evidence, rules and approvals.
- Review outcome
- Independent trace-back result and the checkpoint decision, including unmet criteria.
Independent traceability means review outside the build team. It does not mean a named reviewer has approved the artifact, an audit opinion has been issued, or operator-production use has been demonstrated.
The first artifact and operator-use proof are different
Included: first-field evidence
Tested foundations, one defined occupancy field and an independently traceable source-row artifact, reviewed at the calibration checkpoint.
Subsequent: the operator’s recurring proof
Real-file operator proof, resolution of the operator’s contested number in recurring use, recurring-close acceptance and the later operator-use proof window require separate subsequent commitments.
Completing the first artifact does not establish the later proof. No savings, occupancy gains, clinical outcomes or deployment date are promised.
- The remainder of Pilot One, additional governed fields and portfolio expansion.
- Real-file operator proof, recurring close acceptance and the later operator-use proof window; these are separate, subsequent gates.
- Medication administration, eMAR, clinical workflows, write-back and money movement.
- A finished-platform subscription, replacement of incumbent systems or five simultaneous implementations.
- Support, on-call coverage, steward training and operator-success services unless separately owned, funded and agreed.
- Guaranteed savings, occupancy gains, clinical outcomes or a promised delivery date.
Before the first field begins
- An executive sponsor and an accountable owner for the disputed occupancy number.
- Agreement on the occupancy definition, purpose, reporting period and source authority.
- Authorized source access and data-handling arrangements before any real operator data is used.
- Written scope, acceptance criteria and participation terms before commitment.
This phase is read-only alongside incumbent systems. The broader deployment choice—keep current systems or choose SeniorCRE system-of-record functions after their own build, safety and acceptance gates—does not expand this phase’s scope. Delivery ownership, capacity, participation terms and remedies for unmet acceptance must be confirmed in writing.
Begin with the number and its accountable owner.
Use an Executive Briefing to establish fit, the decision context and what acceptance would require. A briefing is not enrollment, a payment request or a reserved place.
Request an Executive BriefingLast verified October 16, 2026 · the single status date used on every page
Component status describes controlled-environment progress only. The Operator-Controlled Operating Record as a whole is designed and not yet implemented in any community as of October 16, 2026; no operator-production deployment or measured operator outcome is claimed.
Current capability and deployment boundary
Operators may retain existing systems, or select future SeniorCRE system-of-record functions after their required gates clear. Neither replacement nor immediate production availability is implied.
- 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. Request implemented source authority, reconciliation and lineage, followed by operator-owned acceptance. Medication administration/eMAR remains not built.
- Built
- Clinical record surfaces are built; a built surface is not an accepted clinical system or a built operating record. Inspect the exact function and executable artifact; require function-specific safety, security and workflow gates before reliance.
- Validation-exercised
- 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. Request the controlled test record, data classification and limitations. Synthetic/de-identified tests are not operator acceptance or a live named-vendor connector.
- Operator deployment
- No workflow has been accepted end to end by a named operator owner against operator data. Require the named operator owner, scope, acceptance date and the accepted workflow record.
- Production evidence
- No operator-production deployment, 10+ community rollout or measured production result is established. Require named operator consent, scope, acceptance date, baseline and measured production evidence before treating a result as proven.
Prerequisites and acceptance gates
- Operator-approved scope, metric definitions, source authority and accountable approver.
- Authorized source access, vendor permissions, data readiness, entity mapping and security review.
- Function-specific build and end-to-end reconciliation, permission, failure and lineage tests.
- Recorded operator acceptance against agreed criteria before production reliance.
Evidence to inspect
- Versioned metric dictionary, source-authority matrix and entity map.
- Source-specific access record, mapping, test results and unresolved exception register.
- Authorized determination, preserved source-row lineage and signed acceptance record.
Clinical scope and explicit exclusions
Clinical record surfaces are built; medication administration and eMAR remain roadmap — not built, excluded from Road 2 starting scope and unavailable for production today. The future native clinical configuration requires function-specific build completion, clinical-safety review and clinical sign-off, end-to-end workflow validation, data readiness, operator acceptance before production entry. No community runs SeniorCRE as its clinical system of record.
No operator-production deployment, live named connector, measured portfolio rollout or standard go-live duration is claimed. Replacement of a fixed number of systems within hours is not an available offer or a measured result. Medication administration/eMAR and third-party write-back are excluded from starting scope. Synthetic examples, architecture documents and controlled tests are not operator acceptance.