Files
trex-core/docs/releases/evidence/rel-011_20260717_execution-evidence.md
T

4.2 KiB
Raw Blame History

REL-011 운영 실행 증적 및 confirm-release 기록

  • Release: REL-011
  • Batch: BAT-057 (REQ-119–REQ-122)
  • Service: trex-core — trex-admin-daily-trading, genichin-longterm daemon instances
  • Evidence received: 2026-07-17 KST, trex-op reconstructed release-specific execution handoff
  • Evidence sources: immutable git reflog, Supervisor/runtime logs, and secret-free Mattermost terminal capture 20260716_160613_e1fc5e64 (messages 32666, 32668, 32670, 32725, 32746–32758)
  • Release decision: Released — lead confirm-release after reviewing this record and the release owner’s closure direction.
  • Secret policy: no credentials, tokens, account identifiers, DSNs, raw broker responses, raw payloads, or full config values are recorded.

Immutable release identity

Role Revision Evidence
Deployed target 6d90f895 requested target; target object verified and reachable from origin/main
Runtime implementation 94e14894 parent merge for runtime implementation
Release confirmation record this commit records operation evidence and lead decision

Approval, preflight, and activation

  • The approved-instance preflight record confirms that the existing configuration was retained and that credential_fetch_enabled / break-glass semantic state was unchanged.
  • Reflog correlates checkout from main to target 6d90f895… at 2026-07-16 17:36:42 +0900.
  • Supervisor records both approved daemon instances stopping cleanly, spawning as PIDs 2014346 and 2014347, and reaching RUNNING at 17:36:47.316 +0900.
  • Startup runtime interval contains ERROR=0, CRITICAL=0, and Traceback=0; AMQP connection establishment succeeded.
  • No DB migration, dependency change, AMQP topology change, configuration activation, or live mutation was in release scope.

Read-only smoke evidence

Secret-free terminal capture window: 2026-07-16 17:40:09.567–17:40:14.377 +0900.

Approved instance sync --all --dry-run verify Mutation boundary
trex-admin-daily-trading exit 0; 146 A-case-guard skips exit 0; slot_not_found, count 1 no write flags or mutation markers
genichin-longterm exit 0; result count 1, dry_run=true, skipped=false exit 0; cleared, count 1 no write flags or mutation markers

No credential/broker-balance error or CLI failure was recorded. sync --live, --yes, live order, automatic remediation, and manual DB changes were not executed.

Rollback disposition and accepted evidence limitation

  • Rollback was not performed: no stop condition, startup failure, mutation risk, or smoke failure was recorded.
  • The reconstructed evidence preserves the main → 6d90f895… checkout transition but does not preserve the exact pre-deploy ROLLBACK_REVISION SHA; the named user/approver identity is also intentionally absent from the sanitized handoff.
  • These are historical evidence limitations, not a claim that the omitted values were captured. The lead accepts the limitation for this already-completed, no-migration rollout because immutable deployed target, controlled restart, startup health, read-only smoke results, and rollback disposition are independently evidenced. This acceptance is not a precedent for future releases: future release records must contain a redacted approval reference and exact rollback SHA before execution.

confirm-release decision

Released. The committed runbook’s completion criteria are satisfied by the immutable target identity, restart evidence, startup acceptance, both read-only smoke results, and a recorded no-rollback disposition. The production live-sync gate remains separate and was not opened by REL-011.

Source records