Three decisions and one build. That is the format. Nothing else.

Decision 1 — Three divisions, one company

Rocket Marketing & Consulting becomes a division of Rocket Technologies next to Legal Tech and Security Tech. Phoenix is the commercial family for the two technology divisions. The method (FORGE) and the control plane (Helion) are named publicly. The private orchestration layer is not.

Decision 2 — Prices carry their own risk

Marketing: $15,000 → $35,000 MXN a month, no setup fee, no tier above. Legal: Plan Basic at $75,000 MXN + VAT for an 8-week Discovery Pilot — priced to be a decision, not a procurement project. Security: site assessment at $120,000 MXN + VAT; site operations are not for sale until the multi-camera beta clears its gates. Hardware is a separate line with a 15–25% integration margin, and local inference hardware is built only when a client requires it.

Decision 3 — Legal first

Phoenix Legal can prove value with the least capital: a controlled corpus, auditable criteria and a synthetic matter. Two paid pilots with a scorecard are the next commercial objective. Security advances in parallel by gates, not by promises.

Build — Phoenix Legal, this week

  • History of the law, verified. Article versions were reconstructed from the decrees and checked against the text in force. For facts that predate a reform, the system uses the text in force at that date; where reliable history is missing it says so instead of assuming (15 CNPP articles this pass).
  • Defence against text that gives orders. Case context enters in a block with a per-call random marker declared as evidence. Text that tries to close the block cannot guess the marker. If a document contains instructions, it is not deleted — it is evidence — it is flagged, and the prompt says so.
  • Access log with brute-force brake. Attempts are recorded centrally (reason, origin, agent — never the password). Five attempts per user or twenty per origin in fifteen minutes stops the door.
  • Tests: consistency 48/48, web layer 52/52, with and without the law corpus connected. 10/10 failure categories gated.
  • FORGE F1 and F2 shipped: core, chained ledger, worst-case robustness, a Phoenix adapter with 15 scenarios, and a nightly run at 03:15. On its first run it found that the query "el" returned laws, and that the tie-breaker in our own selector was wrong. That is what the nightly run is for.

What is still open

Volume backups in Railway are switched on from the account panel, not from code, and are not on yet. Live tests of session isolation between tenants wait until the first real user is created, because that switches off demo mode. Both are deliberate and dated; both change the moment the first real case file enters.