Skip to content

chore: No promotion pipeline — v18 code isn't what runs in production #9

@martymcenroe

Description

@martymcenroe

Problem

Production is unleashed-c-18.py. Active development is on unleashed-c-21.py. The sentinel safety gate, shared garbage filter (95 patterns), rate-limited session mirror — none of that is in production.

There's no promotion process. Versioning is by filename (unleashed-c-{N}.py), and commands leak version numbers (unleashed-c-21, sentinel-c-21). No record of when versions were promoted or retired.

Solution: prod / beta / alpha Tiers

Replace version-numbered commands with stable tier names:

Command Purpose Typical Lifetime
unleashed Production. The safe default. Days to weeks
unleashed-beta Validated. Promoted from alpha after ~20 min of use. Hours to a day
unleashed-alpha Fresh build. May break things. Minutes to hours

Key decisions:

  • Internal version numbers stay. Each file keeps VERSION = "00021" and sets UNLEASHED_VERSION env var.
  • Sentinel shadow mode on prod by default. Observe-only, zero session risk.
  • sentinel-c-21 command eliminated. Sentinel is a flag (--sentinel-shadow), not a tier.
  • Usage logging. Every launch appends to ~/.unleashed-usage.log: timestamp, tier, project path, script, version.
  • Promotion tracking. Wiki page records every promotion with date and notes.

Promotion workflow:

New build → alpha (~20 min, no crashes) → beta (~1 day, no issues) → prod

Bash functions:

unleashed()       → prod   (c-21 with --sentinel-shadow --mirror --friction)
unleashed-beta()  → beta   (empty slot until next build)
unleashed-alpha() → alpha  (empty slot until next build)

Implementation checklist

  • Update .bash_profile with tier functions + usage logging
  • Create wiki page: Version-Promotions.md
  • Update wiki: Version-History.md with tier system
  • Promote c-21 to prod (first promotion under new system)
  • Retire c-18 from active duty

Source

Deep audit (2026-02-12), versioning discussion (2026-02-15).

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussNeeds strategic discussion before action

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions