Looptimal v2.0.0 — from objective to verified outcome

Looptimal v2.0.0 — from objective to verified outcome

Versions 1.x shipped under the name LoopPrint. As of 2.0.0 the project is Looptimal: the
loop-design wizard is now one mode inside a larger objective→outcome orchestrator. The repository
Renn-Labs/LoopPrint → Renn-Labs/Looptimal was renamed (old links redirect). Install slug
loopprint@renn-labs → looptimal@renn-labs.

Changed

• Rebranded LoopPrint → Looptimal and absorbed the previously-private orchestrator into this repo
  as a single product. The loop-design wizard is preserved unchanged and is now Looptimal's
  Stage-2 "Design-loop" mode (also a direct design / blueprint fast-path).

Added

• Outcome orchestration pipeline — 0 Frame (hash-pinned sealed acceptance suite) → 1 Analyze →
  2 Design-loop → 3 Plan → 4 Simulate (roll forward + pre-mortem + harden) → [human GO] →
  5 Execute (domain-expert sub-agents, maker ≠ checker) → 6 Verify-outcome (a separate checker
  re-runs the sealed suite against live state, ignoring self-reported GREEN) → 7 Persist.
• looptimal-lint.py — plan-time gate for the outcome contract (sealed inputs, outcome-not-symptom
  criteria, maker ≠ checker at the outcome altitude).
• verify-outcome.py — Stage-6 sealed-suite re-runner with tamper→RED selftests, oracle-integrity
  checks, and interpreter env-injection stripping.
• Agent Foundry (references/agent-foundry.md, personas/) — two-tier dynamic domain-expert resolution.
• Worked example (examples/issue-to-pr-bugfix/) that round-trips Frame → … → Verify-outcome.

Security

• Honest, disclosed residual in the sealing model (SECURITY.md): anti-gaming rests on the checker
  controlling --workdir and the framer owning sealed/ via OS permissions; a cryptographic framer
  hash-pin is planned for a later release. Not marketed as fully tamper-proof.

Full changelog: CHANGELOG.md · scope ratified in release-boundary.md.