Deploy evo-region per environment (ADR-0071): one replica with the Recreate strategy (a rolling update would deadlock on the lease), /readyz readiness, /livez liveness, no CPU limit and a drain inside the grace period, with the image digest doubling as the build identity. A new idempotent evo-world-clone provision subcommand creates genesis from development_opening (byte-identical to the qualification fixture) as a Sync hook after the migration. Dev and stage paths include their region; a dev AppProject allows Deployment and Service; region-drill.sh times rollout and forced-deletion recovery; the policy check enforces the host's invariants. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 lines
976 B
C++
19 lines
976 B
C++
#pragma once
|
|
#include "evo/processes/lineage_region.hpp"
|
|
#include <expected>
|
|
#include <memory>
|
|
|
|
// M8.4 development opening (ADR-0071): the deterministic lineage region used to
|
|
// provision dev and stage regions, identical in content to the qualification fixture
|
|
// every M7 test runs (tests/fixtures/environmental_region.hpp). It is an engineering
|
|
// opening, not a world design: one habitat site, two bound organisms (producer 10,
|
|
// consumer 11), founder genome 1 with descendant 2 and one retained dead organism,
|
|
// rules 2, a 50 ms tick. Never provision World0 with it.
|
|
namespace evo::processes {
|
|
inline constexpr std::uint64_t development_opening_frame = 9;
|
|
enum class DevelopmentOpeningError : std::uint8_t { identity, build };
|
|
// Built for `world` in frame development_opening_frame; the world must be nonzero.
|
|
[[nodiscard]] std::expected<std::unique_ptr<LineageRegion>, DevelopmentOpeningError>
|
|
development_opening(std::uint64_t world);
|
|
} // namespace evo::processes
|