feat: CR-BP-73 A&O Retire admission tranche (Regulated Workforce Wind-Down) - #114
Merged
Merged
Conversation
|
|
…-Down)
Governed admission of the CR-BP-72 escape-clause recommendation at the
AgencyAndOrganization x Retire coordinate, landing the canonical
PC + PG + BP stack:
- dea:pc-ao-retire (Process Context)
- dea:group-regulated-workforce-wind-down (Process Group, cross-cutting)
- dea:process-conduct-regulated-workforce-wind-down (Business Process)
The register v2 cell's verbatim escape condition ("defer until a
regulated wind-down (e.g. mass layoff) requires a dedicated L1
group") is activated by CR-BP-72 discovery evidence:
WARN (29 USC 2101 et seq.; 20 CFR Part 639) +
EU Directive 98/59/EC + ILO Conventions 158 (1982) and 135 (1971) +
OECD Employment Outlook + UK TULRCA s.188 + German BetrVG section 17.
Register v9 -> v10: A&O x Retire flips from backlog-deferred to
ratified-accepted/landed; v9_to_v10_note documents the activation.
Counts 41/8 -> 42/7.
ADM-001 admission-authority regex extended to include CR-BP-73.
Disposition register: RETAIN entry appended (132 -> 133 dispositions).
Tranche plan: ao-ret.73 appended; total 71/132 -> 72/133;
pr-act.71 applied_pr updated null -> '112' to reflect the merged #112.
BP-ARC-ID-001 satisfied: name "Conduct Regulated Workforce Wind-Down"
is verb + object form; id preserved unchanged from the CR-BP-72
discovery recommendation. Process Identity gate verifies 0 errors
on the new BP.
Repository:
- contexts/v1-alpha/dea-pc-ao-retire.yaml (NEW; cell_charter
block satisfies PC-006 charter completeness)
- entities/v1-alpha/dea:group-regulated-workforce-wind-down/... (NEW)
- entities/v1-alpha/dea:process-conduct-regulated-workforce-wind-down/...
(NEW; identity, evidence_links in schema-compliant vocabulary,
relationships, ECF conformance, full metadata and links)
- entities/v1-alpha/dea:process-conduct-regulated-workforce-wind-down/research/README.md
(NEW; research subtree README required by catalog-index gate)
- entities/v1-alpha/dea:process-conduct-regulated-workforce-wind-down/research/l2-admission-deposition.yaml
(NEW)
- discovery/v1-alpha/agency-and-organization-retire-escape.yaml (MOD:
admission block appended to close the recommendation loop,
satisfying DISC-007 admission-resolution)
- entities/v1-alpha/dea:group-customer-lifecycle-management/research/l1-register.yaml
(MOD: v9 -> v10; cell flipped; v9_to_v10_note added; carry-forward
candidates retained in l2_candidates for traceability)
- scripts/check_admission_gate.py (MOD: ADM-001 regex extended)
- reconciliation/dispositions/register.yaml (MOD: 133 dispositions)
- reconciliation/tranches/plan.yaml (MOD: 72 tranches, 133 records,
ao-ret.73 entries; pr-act.71 applied_pr updated to '112')
- reconciliation/baseline/v1.yaml (REGEN: sha256 regenerated for
the new PC file)
- tests/* count assertions updated (BP 132 -> 133; PG/PC 41 -> 42;
EXE 694 -> 696; report 735 -> 738; dispositions 71 -> 72; ADM
candidate_count 132 -> 133; Records-checked 132 -> 133 across
4 validator tests)
- change-requests/CR-BP-73-ao-retire-admission.md (NEW)
- change-requests/README.md (MOD: index row)
- CATALOG.yaml regenerated (open_change_requests 83 -> 84)
Verified:
- check_process_context.py PASS (PC-001..PC-008)
- check_process_group.py PASS (PG-001..PG-008)
- check_process_semantics.py CONFORMANT (BP-SEM-008 fixed by
restricting context ref to PC only; BP-SEM-012 is permissible
cross-context warning)
- check_process_identity.py 0 errors on the new BP
- check_process_specialization.py PASS
- check_architectural_regression.py CONFORMANT (BP-AR-001..007)
- check_admission_gate.py CR-BP-73 registered
- check_dispositions.py DISP-OK
- check_lifecycle_discovery.py CONFORMANT (16 records, 0 findings;
admission block resolves DISC-007 duplicate-name face)
- check_ecf_conformance.py 696 entries conform (PC + BP enter
the EXE ledger; PG does not)
- check_activity_model.py CONFORMANT (Activity 521, BP 133)
- check_execution_boundary.py CONFORMANT (Records 696)
- check_process_context_relationships.py PASS (evidence_links
schema-compliant: documentation/governance/interview/artifact/
standard/regulation vocabulary)
- check_catalog_index.py --strict PASS (696 entities)
- regenerate_catalog.py --check PASS
- build_conformance_report.py: 738 records (all L4); CR-BP-73 PG/PC/BP
all at L4 with change_history_admission evidence
- 24-gate suite CONFORMANT (0 blocking, 0 advisory)
- CR-META 0 new findings
- pytest 383/0
- reconciliation/baseline/v1.yaml sha256 matches live catalog
Branch cut from origin/main post-#113; not stacked on open PRs.
emmanuel-a-otchere
force-pushed
the
feature/cr-bp-73-ao-retire-admission
branch
from
September 15, 2026 09:41
ac5be57 to
b013e1c
Compare
emmanuel-a-otchere
added a commit
that referenced
this pull request
Sep 15, 2026
Escape-clause re-evaluation of the F&A x Retire register cell,
re-opening the verbatim escape condition from the register v2
ratification (CR-BP-19, 2026-09-07):
'defer until a regulated unwind (e.g. mutual insurer run-off)
requires a standalone group'
The 2024-2026 regulatory landscape satisfies the escape clause:
- PRA PS20/24 (UK): Solvent Exit Planning for Insurers, in
force 30 June 2026. 28-day run-off plan once supervised.
- FSB Final Guidance on Insurance Resolution Strategies (2025):
categorises run-off as solvent, insolvent, payout/transfer,
and liquidation.
- NAIC Model Regulation Service of Legal Process (Model 901):
record retention during run-off; service-of-process;
claims-handling.
- IFRS 17 Insurance Contracts (effective 2023): current
fulfillment value with contractual service margin; the General
Model, the Variable Fee Approach, and the Premium Allocation
Approach each define how policies in run-off are measured.
- IFRS 5 Non-current Assets Held for Sale and Discontinued
Operations.
- ASC 205-30 Liquidation Basis of Accounting (FASB ASU 2013-07);
ASC 944 Financial Services - Insurance.
- APQC PCF 8.8 Perform financial wind-down (entity-level
solvent exit).
- TM Forum eTOM GB921 Level 3: 1.1.3.4 Manage Financial
Liquidity; 1.4.5 Perform Wind-down; 1.4.6 Perform Disposal
of Investments.
- Insurance Run-off Association (IRO) Best Practice Guidance
(2024): governance, communications, claims handling, asset
management during run-off, reserving adequacy, capital
adequacy during wind-down.
- dea-metaframework/framework/domain-grounding.md section 3.7.
Outcome (4 candidates evaluated):
- Conclude a Regulated Run-Off: 9/10 ADMIT-CANONICAL
- Operate Financial Wind-Down: 5/10 DEFER
- Dispose of Investments: 3/10 RECLASSIFY
- Recognize Impairment and Exit Liabilities: 3/10 RECLASSIFY
Candidate 1 is the L1 Process to admit at F&A x Retire via
CR-BP-75. It satisfies BP-LIFE-009 (verb + object), BP-ARC-ID-001
(process_type: management), DISC-002 (post-IFRS-17 evidence
basis), DISC-003 (authority-anchored trigger), and DISC-005
(audit completeness). Score 9/10; one-point reduction for the
F&A-domain scope question (insurance-led vs broader financial-
stewardship wind-down), deferred to a future CR.
Candidate 2 fails the BP-LIFE-009 semantic-identity test
(Operate is a state verb, not a transformation verb). Defer
until a future CR re-evaluates the cell charter to include a
non-insurance regulated wind-down L1 candidate (banks under
PRA BRRD / FDIC OLA, pension funds under PBGC termination).
Candidates 3 and 4 are Activity-shaped (bounded to a single
disposal or recognition event under the broader run-off
Process). Reclassify as Activity-level decomposition
candidates for CR-BP-7x+ once candidate 1 is admitted.
Schema notes:
- context_evaluation uses boolean concern-was-identified flags
(concerns_identified, candidates_considered, etc.); the
A&O escape record at CR-BP-72 uses the same pattern.
- rationale.{included,excluded,unresolved} are multi-line
string scalars (schema requires type=string, not array).
- scoring.total is an integer 0-10 (schema constraint),
decomposed into the 5 required sub-scores
(process_reality, semantic_stability,
cross_domain_applicability, boundary_clarity,
evidence_strength).
- disposition.canonical_process_ref is type=string (not
nullable); field is omitted entirely for DEFER / RECLASSIFY
dispositions.
- evaluation has 14 required fields; process_identity and
registry_alignment are removed (they were content, not
schema fields).
Repository:
- discovery/v1-alpha/finance-and-accounting-retire-escape.yaml
(NEW; escape-clause re-evaluation per CR-BP-62 method)
- tests/test_check_lifecycle_discovery.py (MOD: 16 -> 17
across 3 sites: record_count, docstring 'Discovery
records checked: 16' -> 17, len(_stage_pairs))
- change-requests/CR-BP-74-fa-retire-escape-discovery.md (NEW)
- change-requests/README.md (MOD: index row)
Verified:
- check_lifecycle_discovery.py CONFORMANT, 17 records, 0
findings
- pytest 383/0 (15/15 in test_check_lifecycle_discovery.py)
- 0 schema errors against
schemas/discovery/lifecycle-discovery.schema.json
- 0 em-dash on new lines (memory directive 2026-09-11)
- No admission; ADMIT-CANONICAL is recommendation-only per
CR-BP-62 section 20; admission is CR-BP-75
- No PC, PG, BP, or activity files created
- No register cell flip (carried to CR-BP-75)
- No ADM-001 regex extension
- No disposition register append
- No tranche plan update
- No PG, BP, or activity count-assertion bump
- No CATALOG.yaml regeneration
- No CR-META changes
Branch cut from origin/main post-#114; not stacked on open PRs.
emmanuel-a-otchere
added a commit
that referenced
this pull request
Sep 15, 2026
…#115) Escape-clause re-evaluation of the F&A x Retire register cell, re-opening the verbatim escape condition from the register v2 ratification (CR-BP-19, 2026-09-07): 'defer until a regulated unwind (e.g. mutual insurer run-off) requires a standalone group' The 2024-2026 regulatory landscape satisfies the escape clause: - PRA PS20/24 (UK): Solvent Exit Planning for Insurers, in force 30 June 2026. 28-day run-off plan once supervised. - FSB Final Guidance on Insurance Resolution Strategies (2025): categorises run-off as solvent, insolvent, payout/transfer, and liquidation. - NAIC Model Regulation Service of Legal Process (Model 901): record retention during run-off; service-of-process; claims-handling. - IFRS 17 Insurance Contracts (effective 2023): current fulfillment value with contractual service margin; the General Model, the Variable Fee Approach, and the Premium Allocation Approach each define how policies in run-off are measured. - IFRS 5 Non-current Assets Held for Sale and Discontinued Operations. - ASC 205-30 Liquidation Basis of Accounting (FASB ASU 2013-07); ASC 944 Financial Services - Insurance. - APQC PCF 8.8 Perform financial wind-down (entity-level solvent exit). - TM Forum eTOM GB921 Level 3: 1.1.3.4 Manage Financial Liquidity; 1.4.5 Perform Wind-down; 1.4.6 Perform Disposal of Investments. - Insurance Run-off Association (IRO) Best Practice Guidance (2024): governance, communications, claims handling, asset management during run-off, reserving adequacy, capital adequacy during wind-down. - dea-metaframework/framework/domain-grounding.md section 3.7. Outcome (4 candidates evaluated): - Conclude a Regulated Run-Off: 9/10 ADMIT-CANONICAL - Operate Financial Wind-Down: 5/10 DEFER - Dispose of Investments: 3/10 RECLASSIFY - Recognize Impairment and Exit Liabilities: 3/10 RECLASSIFY Candidate 1 is the L1 Process to admit at F&A x Retire via CR-BP-75. It satisfies BP-LIFE-009 (verb + object), BP-ARC-ID-001 (process_type: management), DISC-002 (post-IFRS-17 evidence basis), DISC-003 (authority-anchored trigger), and DISC-005 (audit completeness). Score 9/10; one-point reduction for the F&A-domain scope question (insurance-led vs broader financial- stewardship wind-down), deferred to a future CR. Candidate 2 fails the BP-LIFE-009 semantic-identity test (Operate is a state verb, not a transformation verb). Defer until a future CR re-evaluates the cell charter to include a non-insurance regulated wind-down L1 candidate (banks under PRA BRRD / FDIC OLA, pension funds under PBGC termination). Candidates 3 and 4 are Activity-shaped (bounded to a single disposal or recognition event under the broader run-off Process). Reclassify as Activity-level decomposition candidates for CR-BP-7x+ once candidate 1 is admitted. Schema notes: - context_evaluation uses boolean concern-was-identified flags (concerns_identified, candidates_considered, etc.); the A&O escape record at CR-BP-72 uses the same pattern. - rationale.{included,excluded,unresolved} are multi-line string scalars (schema requires type=string, not array). - scoring.total is an integer 0-10 (schema constraint), decomposed into the 5 required sub-scores (process_reality, semantic_stability, cross_domain_applicability, boundary_clarity, evidence_strength). - disposition.canonical_process_ref is type=string (not nullable); field is omitted entirely for DEFER / RECLASSIFY dispositions. - evaluation has 14 required fields; process_identity and registry_alignment are removed (they were content, not schema fields). Repository: - discovery/v1-alpha/finance-and-accounting-retire-escape.yaml (NEW; escape-clause re-evaluation per CR-BP-62 method) - tests/test_check_lifecycle_discovery.py (MOD: 16 -> 17 across 3 sites: record_count, docstring 'Discovery records checked: 16' -> 17, len(_stage_pairs)) - change-requests/CR-BP-74-fa-retire-escape-discovery.md (NEW) - change-requests/README.md (MOD: index row) Verified: - check_lifecycle_discovery.py CONFORMANT, 17 records, 0 findings - pytest 383/0 (15/15 in test_check_lifecycle_discovery.py) - 0 schema errors against schemas/discovery/lifecycle-discovery.schema.json - 0 em-dash on new lines (memory directive 2026-09-11) - No admission; ADMIT-CANONICAL is recommendation-only per CR-BP-62 section 20; admission is CR-BP-75 - No PC, PG, BP, or activity files created - No register cell flip (carried to CR-BP-75) - No ADM-001 regex extension - No disposition register append - No tranche plan update - No PG, BP, or activity count-assertion bump - No CATALOG.yaml regeneration - No CR-META changes Branch cut from origin/main post-#114; not stacked on open PRs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Governed admission of the CR-BP-72 escape-clause recommendation at the AgencyAndOrganization x Retire coordinate. Lands the canonical PC + PG + BP stack. Third slice of the Option B backlog-deferred sequence.
Scope
Escape clause activation (register v2 verbatim)
Activated by CR-BP-72 evidence: U.S. WARN Act (29 U.S.C. 2101 et seq.; 20 CFR Part 639), EU Council Directive 98/59/EC, ILO Conventions 158 (1982) and 135 (1971), OECD Employment Outlook, UK TULRCA s.188, German BetrVG section 17. Cell flips from backlog-deferred to ratified-accepted/landed in register v10; v9_to_v10_note documents the activation.
Mechanics
Verified
NOT-list: no L3 Activities (separate slice); no other register cell flips; no specialization, cross-stage, or new-domain admission; not stacked on open PRs (branch cut from origin/main post-#113).
Next step (separate slice): F&A x Retire (mutual insurer run-off), the third item in the Option B backlog-deferred sequence.