You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Epic / tracking issue for the depth-axis goal: make mimetic capable of replacing a bespoke multi-actor, shared-state product simulation with mimetic core + a thin, declared in-repo extension — with decision-equivalent evidence (docs/goals/proof-roadmap/goal.md). This is the hardest of the three depth targets because it stacks two capabilities mimetic does not yet have: a multi-persona swarm and a shared mutable service plane.
We have shipped the enabling layers (subject provider + subject.state seed/migrate, the scripted-browser actor, the terminal-product real-agent lane with command-scoped credentials + cost/no-spend ledger + the extension seam). We have not yet completed a single end-to-end bespoke-sim deletion proof. This epic tracks the remaining generic capabilities; the domain-specific adapter that consumes them is intentionally downstream / out of this repo (it is product-specific and stays in the adopter's own repo as the thin extension — that split is the extension-budget thesis).
Tracked capabilities (generic mimetic core)
In dependency order:
Multi-lane fan-out (layer 2) — Multi-lane fan-out for the computer-use lab (proof-roadmap layer 2) #163. The prerequisite: N differentiated persona lanes (per-lane persona/device/starting-surface), bounded concurrency, per-lane-worlds default. Was designed + judged previously; lands as its own goal-packeted phase.
Multi-actor shared-world topology (layer 7) — Multi-actor shared-world (shared-service) topology (proof-roadmap layer 7) #164. The deep one: N actor roles against one provisioned mutable service plane; a declared override of per-lane-worlds whose open question is decision-grade attribution in a shared world (design-first).
Recommended path (build the bridge, not a rip-out)
Prove the "delete-for-mimetic + thin adapter" thesis end-to-end on an easier single-actor target first, so the pattern is proven before betting it on a multi-actor shared-state target.
Build the generic capabilities above in order (fan-out → shared-world design+build → scorer hook → PII/PHI tier).
Keep any bespoke harness as the acceptance baseline until per-capability parity is demonstrated against kept mimetic run-bundle receipts.
Each capability ships as its own ratified goal packet + proof ladder (deterministic merge gate, one kept live rung). Do not rip out a working bespoke harness before parity.
Public-safety stance
Generic roadmap; no product names, domains, paths, or values. The domain adapter that consumes these capabilities is downstream and not tracked here.
Summary
Epic / tracking issue for the depth-axis goal: make mimetic capable of replacing a bespoke multi-actor, shared-state product simulation with mimetic core + a thin, declared in-repo extension — with decision-equivalent evidence (
docs/goals/proof-roadmap/goal.md). This is the hardest of the three depth targets because it stacks two capabilities mimetic does not yet have: a multi-persona swarm and a shared mutable service plane.We have shipped the enabling layers (subject provider +
subject.stateseed/migrate, the scripted-browser actor, the terminal-product real-agent lane with command-scoped credentials + cost/no-spend ledger + the extension seam). We have not yet completed a single end-to-end bespoke-sim deletion proof. This epic tracks the remaining generic capabilities; the domain-specific adapter that consumes them is intentionally downstream / out of this repo (it is product-specific and stays in the adopter's own repo as the thin extension — that split is the extension-budget thesis).Tracked capabilities (generic mimetic core)
In dependency order:
Recommended path (build the bridge, not a rip-out)
Each capability ships as its own ratified goal packet + proof ladder (deterministic merge gate, one kept live rung). Do not rip out a working bespoke harness before parity.
Public-safety stance
Generic roadmap; no product names, domains, paths, or values. The domain adapter that consumes these capabilities is downstream and not tracked here.