pandoraDescribe resources with OpenTofu.
Keep compute, networking and storage declarations in reusable modules. Separate environment inputs from module logic so a workspace can target existing infrastructure as well as newly provisioned resources.
Check before changing.
Compile a proposed state into a plan, check the encoded invariants, and review the result. The policy worker’s Terraform projection is read-only: a policy evaluation is not an infrastructure apply.
Carry the evidence forward.
Bind decisions to baseline, policy and model revisions. Recheck evidence at admission so a previously valid result cannot silently authorize a changed workspace.
A constrained probability space.
Pandora’s research direction treats possible infrastructure states as a distribution. Langevin dynamics and flow-matching methods provide a way to model movement through that space, guided by workload evidence and bounded by policy. A learned proposal is still a proposal.
Regularity needs an explicit boundary.
Z3 checks encoded constraints against a proposed plan. Satisfiability applies to the constraints we actually encode, not every property of a real deployment. Unknown, expired or stale evidence must not authorize work. The diffusion visualization is an illustrative channel simulation, not a live infrastructure optimizer.
REPOSITORY MAP
iac/ · pandora-policy/src/ · workspace.pd