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: Application support and source recovery safeguards advanced toward the coordinated PostgreSQL cutover. Production PostgreSQL acceptance and MariaDB retirement remain pending.
Impact: These results establish basic physical conversion and recovery evidence. Production still uses MariaDB. The complete production cutover owner, actual runtime handoff boundaries and live acceptance remain required.
Impact: Development checkpoints can stay inexpensive while complete tests, independent review and deployment-specific safety gates remain required.
Impact: These checks remove known source defects and improve recovery evidence before a production cutover. Production still uses MariaDB.
Impact: The infrastructure blocker is resolved. The conversion now needs to preserve existing account values before recovery rehearsal can continue. Production still uses MariaDB.
Impact: Repeated base changes delay the disposable cutover and recovery proof. That proof must pass before production migration can proceed.
Impact: Allows admission under the approved headroom policy while keeping serialized heavy work and existing safeguards.
Impact: The accepted changes reduce lost work and make status, recovery, and keyboard interaction clearer. Live verification used read-only checks without production test records.
Impact: The immediate runner outage is recovered. Reboot reliability still needs both coherent release selection and runtime preparation that does not depend on full application delivery.
Impact: The reported bugs now have reviewed fixes, test evidence and closed lifecycle records.
Impact: The installed schema5 upgrade preserved129 receipts and52 batches. Each notification retains independent accounting, expiry and cancellation. Dashboard reader and agent guidance support the new distinction between waiting notifications and runs.
Impact: Temporary observation failures retry within existing expiry instead of canceling the continuation. Installation preserved 126 receipts and 51 batches. Ordinary-chat preservation has live acceptance and issue505 is closed.
Twenty repositories, 920 issues, and a closer look at the work still between an idea and a running service.
Open signalImpact: Keeps completion reporting tied to authorized workflows while limiting automatic notices to one per run lifetime, three per workflow and five globally per rolling day, with one outstanding notice.
Impact: Software watches completion without model polling, while persistent one-per-run and rolling workflow/global limits prevent retry loops from creating unlimited new turns.
Impact: Agents can follow current capacity and next-check guidance from application checkouts; operators no longer depend on an expensive full-workspace refresh for queue status. Shared capacity, FIFO, heartbeat, maintenance enforcement and alerting remain unchanged.
Impact: Useful progress can reach the project stream without becoming a mandatory completion checklist.
Impact: Heavy Login compilation moves off the VPS; exact-run artifact checks, packaged browser qualification and Login-only rollback-protected rollout retain the existing host lease and resource limits.
Impact: ProjectMan now has a reviewed source design for disposable PostgreSQL tests without sharing production database privileges. Nine focused contract tests pass; no runtime change or live PostgreSQL qualification is claimed.
Impact: Verified maintenance is null and runner fleet active. The marker was advisory, not a lease admission lock; queue now reports host-pressure. No pressure thresholds, leases, runner configuration or reboot schedule changed.
Impact: The prepared shared-label workflow offloads complete PR suites with native lease enforcement; deployment remains unchanged. Independent test concurrency on the sole native fallback runner would deadlock the multi-job deployment lease, so shared concurrency is retained.
Impact: The library source merge gate is cleared without a signing or review exception.
Impact: Compatible standalone tests can leave the VPS heavy-work queue once the remote image is qualified, with native ProjectMan compatibility retained. Polling provides a preference bias, not strict runner priority.
