-
✓ RSR template with full CI/CD (17 workflows)
-
✓ CLI with subcommands (init, validate, generate, build, run, info)
-
✓ Manifest parser for
ponyiser.toml -
✓ Codegen stubs
-
✓ ABI module stubs (Idris2 + Zig FFI)
-
✓ README with Pony reference capability architecture
-
❏ Parse concurrent code to identify shared state and message patterns
-
❏ Implement capability inference: assign iso/val/ref/box/trn/tag to each data reference
-
❏ Model the Pony capability subtyping lattice (iso <: trn <: ref <: box, iso <: val <: box, tag is bottom)
-
❏ Detect sendability violations (ref/trn/box cannot cross actor boundaries unless consumed)
-
❏ Idris2 ABI proofs for RefCapability subtyping and CapabilitySubtyping relation
-
❏ Emit capability assignment report for user review
-
❏ Generate Pony actor declarations from manifest component descriptions
-
❏ Generate behaviour (async handler) signatures with capability-correct parameters
-
❏ Generate
isoownership transfer for message-passing between actors -
❏ Generate
valpublish patterns (trn → val transition for shared immutable data) -
❏ Generate causal message types with correct capability annotations
-
❏ First working end-to-end example: concurrent producer/consumer pipeline
-
❏ Build Zig FFI bridge for Pony runtime interop
-
❏ C-ABI-compatible actor handle types
-
❏ Mailbox layout matching Idris2 Layout.idr proofs
-
❏ Callback registration for cross-language actor communication
-
❏ Integration tests verifying capability safety across the FFI boundary
-
❏ Idris2 proofs for actor mailbox memory layout
-
❏ Idris2 proofs for causal message ordering guarantees
-
❏ Compile-time capability violation errors with actionable diagnostics
-
❏ Capability audit mode: show all inferred capabilities and why
-
❏ Shell completions (bash, zsh, fish)
-
❏ Concurrent HTTP server pattern (iso requests, val config, tag logger)
-
❏ Pipeline pattern (chain of actors with iso handoff)
-
❏ Fan-out/fan-in pattern (val broadcast, iso collect)
-
❏ Supervisor pattern (tag references for health monitoring)
-
❏ Performance benchmarks vs. lock-based equivalents
-
❏ Additional examples and documentation