{
  "ai_model_governance": {
    "conflict_rule": "If model recommendation conflicts with authoritative control facts, Gekyume returns HOLD.",
    "role_of_ai": "AI/model output is an input, never unilateral execution authority.",
    "validation": "Institution can challenge policy mappings, edge cases, sensitivity, and outcome behavior before production use.",
    "vendor_models": "Third-party model outputs can be governed without granting the model release authority."
  },
  "assurance_statement": {
    "independent_attestations": "No self-issued claim is made for SOC 2, ISO 27001, PCI certification, independent penetration-test attestation, or bank approval. Those are external assurance artifacts and are completed by qualified third parties or the purchasing institution when required.",
    "procurement_readiness": "The product is ready to enter a bank procurement, architecture, security, model/control-risk, and pilot evaluation process.",
    "production_approval": "Production deployment remains subject to the institution\u2019s own approvals, contracts, data classification, security review, and authorized integration boundary."
  },
  "bank_control_translation": {
    "Alignment": "Risk appetite and transaction-limit adherence",
    "Boundary": "Entitlement, product, currency, and channel boundary",
    "Causality": "Expected posting and settlement consequence",
    "Coherence": "Cross-control and model-output consistency",
    "Continuity": "Account-state continuity and duplicate-payment control",
    "Genesis": "Originator authentication and payment authority",
    "Reference": "Beneficiary integrity and sanctions disposition",
    "Time": "Instruction freshness and cutoff control"
  },
  "classification": "Bank procurement sandbox and institutional integration package",
  "data_governance": {
    "data_minimization": "Control evaluation requires transaction/control facts rather than full customer records.",
    "production_retention": "Contractually defined per institution before production onboarding.",
    "sandbox_data": "Synthetic data only. Requests explicitly marked as live/customer data are rejected.",
    "system_of_record": "Bank retains ownership and authority over customer, account, sanctions, entitlement, and settlement systems."
  },
  "decision_model": {
    "HOLD": "State is incomplete, stale, contradictory, or requires requalification.",
    "PERMIT": "All configured pre-execution controls proved.",
    "REJECT": "A definitive bank policy/control breach is present."
  },
  "evidence": {
    "audit_retention": "CloudTrail audit objects retained under lifecycle policy; procurement control receipts are durable evidence records.",
    "backup": "DynamoDB point-in-time recovery enabled.",
    "change_control": "Bank procurement stack is infrastructure-as-code under CloudFormation; changes create AWS audit events.",
    "receipts": "Every procurement decision writes a durable attributable receipt containing decision, reason, transaction fingerprint, policy fingerprint, policy identifier, timestamp, failed controls, and receipt hash."
  },
  "incident_change_governance": {
    "change_policy": "Changes are attributable through CloudFormation/AWS audit records and require requalification of affected control behavior.",
    "incident_policy": "Security/control failures fail closed; operational alarms and CloudTrail preserve investigation evidence.",
    "rollback": "Infrastructure is versionable/reproducible; receipt evidence is separated from mutable runtime code."
  },
  "integration_contract": {
    "inputs": [
      "institution_id",
      "transaction control facts",
      "institution policy profile",
      "authoritative control dispositions",
      "optional model recommendation"
    ],
    "outputs": [
      "PERMIT/HOLD/REJECT",
      "bank-language reason",
      "failed controls",
      "policy fingerprint",
      "transaction fingerprint",
      "receipt identifier/hash"
    ],
    "settlement": "No production settlement connector is included in the procurement sandbox. Production consequence adapters are institution-specific and independently authorized."
  },
  "product": "GEKYUME Institutional Pre-Execution Control Plane",
  "product_promise": "No consequential financial release becomes eligible until authoritative control facts, policy, authority, references, transaction state, model output, and intended consequence are mutually coherent.",
  "regulatory_alignment": [
    {
      "alignment": "risk-based governance, validation/monitoring, governance and controls, vendor/third-party products",
      "source": "Federal Reserve / OCC / FDIC Revised Model Risk Management Guidance (2026)",
      "url": "https://www.federalreserve.gov/frrs/guidance/supervisory-guidance-on-model-risk-management.htm"
    },
    {
      "alignment": "architecture/infrastructure governance, operations, interconnected assets/processes/service providers",
      "source": "FFIEC Architecture, Infrastructure, and Operations",
      "url": "https://www.ffiec.gov/news/press-releases/2021/pr-06-30"
    },
    {
      "alignment": "AI lifecycle risk, trustworthiness, testing/evaluation/verification/validation",
      "source": "NIST AI RMF Generative AI Profile",
      "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence"
    }
  ],
  "resilience": {
    "failure_policy": "Fail closed: unresolved contradictions or stale/incomplete authoritative state produce HOLD, not silent release.",
    "production_targets": "RTO/RPO and availability commitments are institution-specific contractual SLOs; the procurement sandbox does not misrepresent unmeasured historical SLA.",
    "recovery": "Receipt table point-in-time recovery plus CloudFormation reproducible infrastructure.",
    "runtime": "AWS Lambda and DynamoDB managed regional services; no always-on server dependency in the procurement path."
  },
  "scope": {
    "institutional_api": "Private rate-limited procurement API; institution-specific policy profiles supported.",
    "production_pattern": "Bank-owned authoritative systems remain systems of record; Gekyume operates as a pre-execution release control plane.",
    "sandbox": "Synthetic data only; no settlement or external financial mutation."
  },
  "security": {
    "audit": "Multi-region CloudTrail enabled with log-file validation and private versioned S3 retention.",
    "encryption": "DynamoDB receipt storage encrypted at rest; TLS provided by API Gateway/CloudFront in transit.",
    "iam": "Dedicated least-privilege execution role; no Bedrock or S3 administrative access on the bank control Lambda.",
    "legacy_boundary": "Legacy Gekyume execution gate retired from active concurrency and removed from the procurement path.",
    "observability": "AWS X-Ray, API metrics, Lambda logs, and CloudWatch operational alarms.",
    "secrets": "No control secret embedded in the active procurement Lambda configuration; reserved secrets use AWS Secrets Manager.",
    "security_posture": "AWS Security Hub enabled.",
    "threat_detection": "Amazon GuardDuty enabled."
  },
  "third_party_risk": {
    "deployment_model": "Integrates without displacing core systems; least-privilege adapters are scoped to the exact bank-authorized consequence boundary.",
    "exitability": "Bank policy and authoritative data remain bank-owned; Gekyume stores control receipts/fingerprints rather than becoming the core ledger.",
    "subprocessors": "AWS is the current cloud execution substrate for the procurement environment. Additional production subprocessors are disclosed per deployment."
  },
  "verified_challenge_suite": {
    "authority_failure": "REJECT",
    "duplicate": "REJECT",
    "limit_breach": "REJECT",
    "model_conflict": "HOLD",
    "sanctions_match": "REJECT",
    "stale_instruction": "HOLD",
    "valid": "PERMIT"
  },
  "version": "Procurement Package v1.0"
}