Governing Standard
BRSA Behavioral Readiness Standards Authority
Established 2026 · Deterministic · Auditable · Consent-Based · Permanent Record
01
Readiness Philosophy
Readiness is not a feeling. It is not a reputation. It is not a credential issued by proximity to the right institution. Readiness is a pattern — observable, documentable, and computable.
The BRSA readiness model rejects subjective assessment entirely. Every readiness determination is produced by applying a versioned ruleset to a structured evidence record. The same evidence, evaluated by the same ruleset, produces the same result every time. This is the foundation of a credible standard.
"Readiness is deterministic. If your method produces different results under the same conditions, you do not have a method — you have an opinion."
02
FRARI Ruleset
FRARI Individual v1.0.0 — Active
FRARI — the Foundational Readiness and Accreditation Ruleset for Individuals — is the scoring engine at the core of every BRSA assessment. It is versioned, published, and applied consistently. Every assessment record contains the exact ruleset version used to compute the score.
Version 1.0.0 implements a weighted composite model — four independently scored sub-dimensions are combined into a single readiness score between 0 and 100. This replaces the point-accumulation model of v0.1.0 with a structured, domain-aligned evaluation framework governed by certified BRSA evaluators operating within the Legacyline platform.
Each version is permanently archived. No assessment may be recomputed under a different ruleset version than the one active at the time of evaluation.
03
Composite Scoring Model
The FRARI v1.0.0 composite score is computed from four weighted sub-scores. Each sub-score is derived from structured evidence collected by a certified BRSA evaluator and processed deterministically by the Legacyline readiness engine.
Sub-Score 01
Evidence Engagement
30%
Volume and recency of evidence events submitted across all active assessment domains. Caps at 10 events; decays with inactivity.
SOURCE: evidence_events table · all domains
Sub-Score 02
Lifecycle Progression
25%
Advancement through the six-state readiness lifecycle. Velocity bonus applied for participants who progress through stages consistently and without delay.
SOURCE: state_history table · lifecycle velocity
Sub-Score 03
Consent Compliance
20%
Active, maintained consent to the assessment process. Granted consent scores 100. Pending scores 40. Revoked or absent scores 0.
SOURCE: consents table · status field
Sub-Score 04
Intake Completeness
25%
Completeness of the structured intake record including identity, housing, employment, income, and required documentation uploads.
SOURCE: intake_submissions table · 12 fields
The composite score is computed by the Legacyline readiness engine — never by the evaluator. Evaluators record evidence. The engine computes scores. This separation is a foundational design principle of the BRSA standard.
04
Five Canonical Indicators
Five indicators structure the BRSA assessment framework. Each maps directly to one or more composite sub-scores. Evaluators assess evidence within these indicator boundaries — they do not assign indicator ratings directly.
01
Documentation Discipline
→ Intake Completeness (25%)
The consistency, completeness, and timeliness of the participant's own record-keeping — intake fields, identity documents, financial records, and housing documentation.
02
Consent Compliance
→ Consent Compliance (20%)
Adherence to consent protocols — granting, maintaining, and not revoking consent without cause. Consent is the gateway to the governed assessment process.
03
Evidence Completeness
→ Evidence Engagement (30%)
The degree to which the submitted evidence record addresses all required assessment domains. Measured by volume of evidence events and recency of last submission.
04
Pattern Consistency
→ Lifecycle Progression (25%)
Observable regularity in behavior across time — measured through lifecycle state advancement and velocity through the six-stage readiness pipeline.
05
Escalation Integrity
→ Evaluator Workflow · Module 5
The appropriate and timely escalation of evaluation findings to the BRSA Standards Authority for review and approval. Governs the two-tier sign-off structure — evaluator submits, Standards Authority approves.
05
Readiness States
Every registry record carries one of three canonical readiness states. States are computed, not assigned. They reflect evidence, not opinion. A state may only change through a new governed assessment cycle.
Green
Verified Ready
Score 70–100
Sufficient evidence of behavioral discipline, documentation integrity, and consistent pattern compliance across all assessed dimensions.
Yellow
Developing
Score 40–69
Evidence collection underway. Readiness trajectory is being established. Active engagement with the assessment process is confirmed.
Red
Unverified
Score 0–39
Insufficient evidence or assessment not yet completed. Default state at registration. Does not indicate disqualification — only incomplete data.
Trajectory is tracked independently of state. A participant may hold a Yellow state with an improving trajectory — signaling readiness for state advancement at the next assessment cycle.
06
Assessment Lifecycle
Every BRSA assessment passes through a defined six-stage lifecycle. No stage may be skipped. Each stage is logged to the immutable ledger with a timestamp and actor identifier.
1
Registration
Participant enters the registry. Consent is recorded. Registry ID is issued. State defaults to Red (Unverified).
2
Data Collection
Intake submission completed. Evidence events recorded by certified evaluator across active assessment domains.
3
Under Review
File submitted for evaluator review. Domain scores, document verification, and narrative assessment recorded in the evaluation record.
4
Score Computed
FRARI v1.0.0 ruleset applied to the evidence record. Composite score and trajectory generated deterministically by the Legacyline readiness engine.
5
Standards Authority Approval
Evaluation submitted to the BRSA Standards Authority for review. Two-tier sign-off required before certification is issued.
6
Certified & Published
Public readiness state updated. Internal snapshot sealed. Ledger entry permanent. Registry ID reflects verified standing.
07
Publication Rules
BRSA applies strict data minimalism to every public record. What is published is fixed by doctrine — not by organizational preference or individual request.
✓
Public Fields
Registry ID, readiness state (RED / YELLOW / GREEN), certification status, last updated timestamp. These fields are always public for any verified registry record.
~
Internal Only
Raw composite score, trajectory label, individual sub-score ratings, domain scores, evidence record, ledger audit trail, subject number, participant ID, evaluator identity.
✕
Never Published
PII of any kind, contact information, financial data, legal documents, intake submissions, narrative assessments, or any field not explicitly listed as public.
∞
Immutability
Once a readiness snapshot is written to the ledger, it cannot be modified or deleted. Only a new governed assessment cycle can change the public readiness state. The record of presence is permanent.
08
SHA-256 Measurement Integrity
Every assessment record produced by the Legacyline readiness engine is cryptographically sealed at the time of computation. This is not an optional feature — it is a foundational requirement of the BRSA standard.
The SHA-256 hash is computed over a canonical input string composed of the participant ID, ruleset version, composite score, each sub-score value, and the UTC timestamp of computation. The resulting hash is stored alongside the assessment record and cannot be altered without detection.
"A score without a hash is an opinion. A score with a hash is a fact."
H1
Input Canonicalization
SHA-256 INPUT FIELDS
participant_id + ruleset_version + composite_score + evidence_engagement_score + lifecycle_score + consent_score + intake_score + computed_at (UTC ISO 8601)
H2
Hash Storage
readiness_snapshots.score_hash
The SHA-256 digest is stored in the readiness_snapshots table alongside the score record. It is written once and never updated. Any modification to the score values would produce a different hash — making tampering immediately detectable.
H3
Reproduction Protocol
ReproduceAssessment() — legacyline-core
Any assessment can be independently reproduced using the archived ruleset version and original evidence record. The ReproduceAssessment() function in the Legacyline core engine recomputes the score and validates the hash against the stored value. Matching hashes confirm the record has not been altered.
H4
Version Locking
frari_rulesets.ruleset_id
The ruleset version used for every assessment is stored in the record. Future ruleset updates do not affect existing assessments. An assessment may only be recomputed under the same ruleset version used at the time of original evaluation.