Skip to content

Latest commit

 

History

History
39 lines (34 loc) · 3.54 KB

File metadata and controls

39 lines (34 loc) · 3.54 KB

Airlock 0.5.14 release workspace

This directory is the durable planning and delivery record for 0.5.14. It is the detailed companion to the release index. Historical plans and run evidence retain their existing paths under dev/plans/.

Release sequence

Order Record or delivery slice Purpose Status
0 environment Establish reproducible local, CI, and funded-smoke prerequisites. proposal complete
1 dependency sweep Triage Dependabot and library changes. proposal complete
2 documentation review Classify documentation lifecycle; do not alter it. proposal complete
3 draft requirements Draft needs, requirements, acceptance criteria, and allocations. proposal complete
4 architecture review Review proposed architecture and current high-level code alignment. proposal complete
5 verification review Trace requirements to acceptance criteria and evidence. proposal complete
6 HITL release review Decide include, conditional, or postpone for every candidate. approved
10 Benchmark-safe logging profile Redaction/retention proof and runbook. complete
20 FathomDB chat readiness gpt-4o-mini aliases and chat/stream verification. complete
30 FathomDB embedding readiness text-embedding-3-small and /v1/embeddings. complete; funded smoke passed
40 Shared provider foundation Discovery safety, attribution, and sanitized provider failures. complete; funded smoke belongs to provider slices
50 OpenRouter Operator-configured gateway recipe and routing-control boundary. complete; funded smoke passed
60 DeepSeek Operator-configured stable endpoint and function-tool boundary. complete; funded smoke passed
70 TUI test lifecycle Fast deterministic ordinary TUI tests. complete
80 TUI routing/client diagnostics Classification and session-affinity views/actions. complete
90 TUI QoS/exporter health Priority and telemetry operational views. complete
100 Virtual-key management Deferred to 0.5.15; draft package only. postponed
110 FathomDB operational reads Optional, proxy-owned operational backend. complete
120 Documentation release-index contract Repair stale active-release assertion before release closeout. complete
130 Release closeout Local release matrix, artifact, version, and tag handoff. ready to tag locally

Feature slices use the existing prompts/SLICE-TEMPLATE.md workflow: review their allocation, ratify or revise drafts, write a design memo, commit RED tests, implement GREEN, obtain independent design/code review (three FIX cycles maximum), verify, and write a slice status record under dev/plans/runs/.

No feature slice starts until the Slice 6 decision is recorded. A conditional slice remains planned evidence, not release scope, until its listed dependency and HITL decision are satisfied.