From useful assistant
to governed operator.
Sophia is becoming a private daily-driver agent that can research, build, coordinate, and operate recurring business workflows. Sophia owns the interaction harness; the Pleroma Agent Platform owns governed services; Data Profusion owns product, risk, and operations.
Gateway authority
Pleroma mediated
Fail closed
Evidence first
Human take-over
Responsibility contract
Three owners. One hard boundary.
Sophia requests and presents. The Pleroma Agent Platform authorizes, executes, and persists. Data Profusion governs and operates. Repository location never transfers authority.
Calendar recovery
Founder-visible release spine.
Only complete capability rows change the MVP feature percentage.
Implementation sequence
Six bounded phases
Phase percentages estimate bounded contract work. The stricter 4-of-36 ledger and release-spine exits determine MVP completion; a planned connector is never reported as live.
Canonical MVP ledger
What remains.
This is the complete non-accepted feature inventory. “In progress” means a bounded slice exists; it does not mean that production wiring or live authority has been granted.
Capability tracks
What moves in parallel
Current S5 durable-proposal lineage, approval, recovery, and settlement delivery
One governed layer for business operations.
Pleroma will expose normalized, policy-aware business operations inspired by four major systems. Sophia will use those capabilities through reviewed Hands and exact Gateway grants—not through direct vendor or database credentials.
Delivery gates
Read first. Propose next. Mutate last.
Each gate must close with conformance, denial, recovery, audit, and private-canary evidence.
Explicitly outside MVP
No silent shortcuts.
Operating contract