Architectural Constraint Analysis and Boundary Spec

Wrote docs/architecture/tasks/fedwire-const-001/constraint-analysis/constraint-register-spec.md. Complete architectural constraint analysis specification establishing mutability classifications, regulatory compliance boundaries, cost-of-compliance evaluations, and relaxation pathways.

---

skill: constraint-analysis

Constraint Register & Boundary Spec: Fedwire Modernization [CONST-FED-001]

Summary

This specification establishes the architectural constraint analysis, mutability taxonomy, regulatory compliance boundaries, and relaxation triggers for fedwire-clearing-engine v2.0 under run ID fedwire-const-001. It governs high-value wholesale wire transfers up to $500M across 12 participant financial institutions processing $85B in daily clearing liquidity. It decisively halts the project paralysis and budget inflation demonstrated in incident CST-4919 (where engineering squads treated legacy mainframe EBCDIC batch file formatting as an immutable constraint, producing an unviable $44M architecture estimate that triggered an aborted $12M re-platforming). The analysis systematically examines eight candidate constraints, classifies them across

four mutability tiers (Statutory Invariant, Enterprise Boundary, Negotiable Requirement, Aspirational Goal), establishes the

Cost of Compliance for each constraint, protects non-negotiable Federal Reserve Operating Circular 6 (OC-6) legal invariants, and unlocks

$26M in capital savings by negotiating legacy mainframe interface conversions.

Detailed Description

Architectural projects often stall or experience catastrophic cost explosions because design teams treat all constraints as equally immutable. When technical habits, legacy interfaces, or local preferences are labeled "hard constraints," the solution space shrinks until no viable architecture exists. Rigorous constraint analysis distinguishes between

Hard Invariants (laws of physics, criminal statutes, regulatory mandates like Fedwire OC-6 where violation means immediate revocation of banking charter) and

Negotiable Boundaries (internal policies, legacy file formats, network transit protocols that can be modified or waived with appropriate governance).

Candidate Constraints Ledger (8 Total Constraints)
                         │
                         ▼
[ Mutability Classification Gate ]
  ├── 1. Statutory / Regulatory Invariant (IMMUTABLE)
  │      └── Federal Reserve OC-6 & ISO 20022 Mandate (Non-Negotiable)
  ├── 2. Cryptographic Security Invariant (HARD)
  │      └── Dedicated On-Premise HSM Key Storage (FIPS 140-3 Level 4)
  ├── 3. Negotiable Architectural Boundary (NEGOTIABLE)
  │      └── Legacy Mainframe EBCDIC Transit (CST-4919: Waived via JSON/gRPC)
  └── 4. Sizing & Latency SLA Constraint (TUNABLE)
         └── p99 Clearing Latency <= 450 ms (Achievable via Cache Proxies)
                         │
                         ▼
[ Modernized Fedwire Engine Baseline: Cost Reduced from $44M to $18M Cap ]

Criteria and weights

Comparison

Result

Option C is selected. True statutory and cryptographic constraints (OC-6, FIPS HSM) are preserved as immutable; legacy mainframe EBCDIC constraints are reclassified as negotiable and replaced with containerized translation adapters, lowering project cost from $44M to $17.4M.

---

Required Mechanisms

1. Constraint Surface & Mutability Taxonomy [MC-MT-01]

2. Regulatory & Sovereignty Boundary Protection [MC-RB-01]

• Federal Reserve Operating Circular 6 (OC-6) Invariant:
  • Requires non-repudiable mutual TLS 1.3 encryption with dedicated hardware token authentication.
  • Wire payment processing data must remain within the continental United States (CONUS) under all operating conditions.
  • Software shortcuts bypassing Federal Reserve validation checksums are legally barred.

3. Legacy EBCDIC Relaxation & Adapter Negotiation [MC-RN-01]

• The CST-4919 Defect Resolution:
  • The legacy requirement stating "Core clearing engine must run natively in EBCDIC on IBM z/OS" is reclassified from Tier 1 to

Tier 3 (Negotiable).

Relaxation Agreement: The core clearing engine executes in UTF-8 on AWS EKS; a dedicated, stateless containerized adapter (EbcdicToIsoBridge) handles mainframe translation at the network perimeter, eliminating $16.6M in custom mainframe compiler re-writes.

4. Relaxation Triggers & Governance Playbook [MC-RP-01]

• If Fedwire clearing volume exceeds 50,000 wires/hour during peak market volatility:
  • Latency SLA relaxes from 450 ms to 750 ms under emergency surge protocol authorized by Elena Rostova.

---

Invariants and Contracts

Statutory Regulatory Non-Negotiability [INV-CONST-01]
  Constraints deriving from federal banking statutes or regulatory operating circulars (OC-6) are immutable.
  Architectural proposals attempting to relax or waive statutory compliance are rejected at intake.

FIPS 140-3 Cryptographic Integrity Invariant [INV-CONST-02]
  Wire signing private keys must never exist in plaintext in container memory or general storage.
  Key operations must execute exclusively within certified physical or dedicated cloud HSM enclaves.

Hard Financial Capital Expenditure Ceiling [INV-CONST-03]
  The total architectural implementation budget must not exceed $18,000,000.
  Architectural options whose estimated implementation cost exceeds $18M are disqualified.

Explicit Unknowns

• Federal Reserve certification schedule for cloud-connected dedicated HSM endpoints in AWS us-east-1 (G-1).
• Mainframe channel adapter latency overhead when converting 10,000 concurrent UTF-8 ISO payloads to EBCDIC (G-2).

Traceability

Verification

No validator was supplied, so no command was run.

Reviewer self-check against constraint analysis standards:

• Taxonomy Discipline: PASS. Constraints classified across Statutory, Security, Negotiable, and Financial tiers.
• Cost Realism: PASS. Negotiating EBCDIC legacy constraint drops cost from $44M to $17.4M, preserving budget cap.
• Regulatory Fidelity: PASS. Fedwire OC-6 and FIPS HSM keys preserved as immutable non-negotiable boundaries.
• Markdown Hygiene: PASS. Native Markdown syntax strictly adheres to rule_markdown.md.

Open Decisions

• DEC-CONST-01: David O'Reilly to finalize whether dedicated AWS CloudHSM or on-premise Thales Luna HSM via DirectConnect is selected for the Tier-2 cryptographic boundary (Owner: David O'Reilly).

Next steps

1. Elena Rostova submits the negotiated EBCDIC boundary relaxation addendum to the Mainframe Governance Board.
2. Payment Architecture squad drafts the technical specification for the stateless EbcdicToIsoBridge adapter.
3. Conduct staging performance test routing 1,000 concurrent ISO 20022 wires through the bridge adapter to confirm sub-450ms p99 latency.