RPOS Operational Architecture

RPOS Operational Architecture An architecture diagram generated by Archify. Requester / Model · proposal source · Architecture component · proposal ≠ authority Requester / Model proposal source proposal ≠ authority RPOS Core · service + state machine · RPOS operational boundary · owns operation RPOS Core service + state machine owns operation Human Authority · approve / deny / resume · Architecture component · authority owner Human Authority approve / deny / resume authority owner SQLite Store · state + attempts + events · RPOS operational boundary · durable facts SQLite Store state + attempts + events durable facts Operation Adapter · external dispatch boundary · RPOS operational boundary · effect attempt Operation Adapter external dispatch boundary effect attempt External System · effect outside RPOS · External-effect domain · third party External System effect outside RPOS third party Reconciliation Observer · independent readback · External-effect domain · evidence only Reconciliation Observer independent readback evidence only Responsibility Observatory · read-only service facade · RPOS operational boundary · no mutation Responsibility Observatory read-only service facade no mutation Formal Assurance Surface · Lean theorem + test crosswalk · Architecture component · not runtime authority Formal Assurance Surface Lean theorem + test crosswalk not runtime authority proposal Human Gate / return decision / resume atomic state + event restart recovery authorized dispatch effect attempt transport receipt independent readback reconciliation evidence read-only inspect / history public structural assurance RPOS operational boundary External-effect domain Legend Backend Database Cloud Security External

Operation Ownership

  • • RPOS owns the operation pathway, not model intelligence
  • • Human Authority remains separate from proposal generation and execution
  • • SQLite persists responsibility before and after external dispatch boundaries

Receipt vs Effect

  • • Transport receipt is evidence about transport, not proof of external effect
  • • Required independent readback may reconcile EFFECT_UNKNOWN
  • • Observer failure stays unresolved rather than manufacturing success

Assurance Separation

  • • Lean checks bounded structural invariants
  • • Responsibility Observatory reads through RposService and exposes no mutation
  • • Neither formal assurance nor visualization creates Operational Authority