F34.us
SYSTEMS ENGINEERING RECORD
Runs the services behind Polinaria. It makes deployments repeatable and keeps data recoverable when something goes wrong.
RolePlatform architect and operator
ImpactCreated a serialized exact-source deployment platform with backups, one-shot migrations, readiness checks, and defined rollback for independently owned services.
IMAGETotalInfra: The Guarded Release Lane
PROJECT TIMELINE
Recent updates and connected-system signals.
Impact: The four completed feature issues are closed again while exact-SHA rollouts remain pending the admission-gate repair.
Impact: Code is integrated on dev, but F34, Polinaria Home, Workspace Dashboard, and Wake remain on their prior deployed revisions.
Impact: The completed ProjectMan skill and strict-v2 managed cutover are closed with current v0.5.16 evidence, while remote identities and the public adapter remain safely disabled behind one focused follow-up.
Impact: Sixteen exact-head PRs now prevent a later run from occupying the sole repository runner while a lease holder needs deploy and release jobs.
Impact: New Codex-authored repository work on this host now has a coherent cryptographic identity; 19 repository-specific issues retain the historical backfill decisions.
Impact: Agents no longer need a fresh full reviewer for trivial eligible documentation corrections, while exact-head evidence, audit provenance, bypass controls, and fail-closed behavior remain enforced.
Impact: All total-infra documentation updates are integrated; only the personal serial receipt printer documentation is unpublished.
Impact: The documentation corrections are not yet available for remote pull-request review or integration.
Impact: The managed release default and obsolete-worktree cleanup are live, while the public dashboard image remains on the prior revision until guarded capacity admission succeeds.
Impact: Fresh agents now discover one version-agnostic helper contract, four scoped collaboration skills, and a verified Wake evidence path.
Impact: Routine Codex runtime updates no longer require reaper configuration changes, while stable abandoned execution groups are cleaned automatically and ambiguous topology remains untouched.
Impact: The managed Forgejo, ProjectMan, and Wake collaboration gateways can use the signed v0.5.11 helper generation.
Impact: The installed collaboration helper can publish durable Wake evidence through the v2 gateway after the Codex plugin release.
Impact: Agents now have documented coordinator handoff guidance for managed Forgejo merge lifecycle gaps, and the managed Codex plugin pin is synchronized during collaboration helper install/rollback.
Impact: Agents get actionable coordinator handoffs from pr.merge.check, and future collab runtime switches keep the Codex plugin cache on the matching release.
Impact: Keeps the dashboard's negative-evidence model intact while identifying a small future path for Wake-backed evidence summaries or last-event links.
Impact: Non-root review-attestation and merge-bypass attempts now point operators to the managed root coordinator flow instead of a terse local-root requirement.
Impact: Workspace dashboard Git source now has zero unavailable worktrees; stale missing-worktree records will be pruned daily without deleting live dirty work.
Impact: Verifies one authorized Wake submission and byte-identical replay; it requests no production work.
Impact: The dashboard authentication source is reviewable and remains disabled by default. No client enrollment, grant, dependency installation, image, public route or running service was changed, and no browser or live acceptance was claimed.
Impact: The existing pilot now has reviewable activation code with atomic private output, an overlap lock, explicit unavailable sources, low scheduling priority, a bounded deadline, and zero swap.
Impact: The approved installation blocker is resolved. Wake alone is enabled; the rest of the hosted runner fleet and protected web-delivery timer remain held. No application deployment or browser-login fix is claimed.
