Operating Record Technical Spec
This excerpt shows how SeniorCRE® represents governed entities and lineage in a validation environment. The operator establishes the definition, source authority, decision context, reconciliation, adjudication, lineage, and preservation rules. The tables do not declare enterprise truth on the operator's behalf.
1. Data dictionary (canonical entities)
The eight rows below are representative technical entities. They become governed only when the operator declares what each means, which source has authority for the decision, how disagreement is reconciled, and how the decision is preserved with lineage.
2. Event model
These representative events show the intended lineage envelope: what changed, who or what produced it, which decision context consumed it, and what alternate valid value was preserved. They are demonstrable architecture, not operator-production throughput evidence.
3. RBAC matrix — 33 roles
The matrix documents role and scope design built; not validated. Authorization sits between decision and execution; role membership alone does not authorize a consequential action. Operator policy, data scope, and acceptance testing govern production access.
4. Tenant isolation pattern
Operator/tenant isolation policies are version-controlled in migrations and the application connects under a non-owner database role, so Row-Level Security fails closed — a missed application check returns zero rows, never another operator's data. Per-facility isolation is enforced in the application layer today, with extension to database RLS under active evaluation alongside automated cross-facility isolation tests. The pgTAP suites ( 001-rls-enabled.sql , 002-auth-tenant-isolation.sql , 003-compliance-audit.sql ) were authored against the prior Supabase schema and are being ported to…
5. Audit log
The validation design uses append-only lineage events carrying actor, operator, entity, operation, change, and timestamp. This is demonstrable architecture, not a completed operator-production audit trail. SeniorCRE does not claim SOC 2 certification or its own SOC 2 report.
Frequently asked questions
- Who is this spec for?
- Engineering, data, security, and operations leaders evaluating how definitions, source authority, reconciliation, adjudication, lineage, and preservation are represented.
- Is this the full schema?
- No. It is a pre-production excerpt showing representative governed entities and events. It is not an operator-production data dictionary or a claim that every domain shares one physical model.
- How is access represented?
- The validation architecture exercises role and scope controls. Production acceptance requires operator-specific policy review and security testing.
- How is tenant isolation evidenced?
- Tenant-isolation controls are demonstrable. The prior pgTAP suite is being ported; no completed operator-production isolation validation or independent penetration-test report is claimed.
- Is the event model production-proven?
- No. The table documents demonstrable architecture and design intent. No completed operator-production deployment exists.
https://seniorcre.com/operating-system-spec