Architecture & Privacy Pipeline
Yearning v4 runs as a stateless Go modular monolith backed by PostgreSQL for shared state, execution leases, scheduled jobs, transactional outbox notifications, and multi-replica realtime SSE fan-out, with zero RPC dependencies.
Technology Stack
End-to-End Governance Dataflow
Core Security Invariants
- No Admin Business Override (
admin_is_not_business_override): Platform admins govern/admin/*configuration, datasources, flows, and SQL diagnostics, but cannot modify frozen orders, approve/execute on behalf of frozen actors, or reveal unauthorized SQL. - Six-Purpose AEAD Keyring & AAD Binding:
keyring.jsonisolates six cryptographic domains (payload,sql_fingerprint,identifier_token,settings_impact_token,oidc_state,cursor_affinity). Every ciphertext bindsdeployment_id + table + primary_key + column + purposeinto AES-256-GCM AAD to block cross-row ciphertext substitution. - Dual-Track AI Profile Isolation: Mixed primary/fallback provider chains build payloads per endpoint from raw source and isolate
PrivacyContractHashDefaultvsPrivacyContractHashSAN, guaranteeing raw payloads prepared for localsanmodels never fall back to public cloud endpoints. - Transactional Outbox & Metadata-Only SSE: State changes commit outbox records atomically with domain state.
GET /api/v4/events/streamstreams participant-scoped metadata frames (io.yearning.v4.*) with 25-second: keepaliveheartbeats and never emits plaintext SQL or free-text comments.