artale
/
agentic-ai-engineering
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(tac): tighten product artifact stage gates 

Deepen the Codex product-work guidance with explicit artifact stages, production-readiness receipts, model-timing assumptions, and a deletion/simplification review criterion so cheap implementation does not create ungoverned prototype slop.
This commit is contained in:
artale 2026-06-29 13:30:14 +02:00
parent becd314b8f
commit d6fba49536
2 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pipeline/test_loop_engineering_meta_prompt.py
View File

@ -24,7 +24,11 @@ def test_loop_engineering_meta_prompt_locks_safety_fields():
"vault/proxy credential injection",
"YouTube `hLUGXO5DSpo`",
"Product work with coding agents",
"artifact declares its stage",
"production-looking prototypes must not imply production readiness",
"human taste and systems thinking",
"model-timing assumptions",
"deletion/simplification",
"YouTube `P3KDebPTUrw`",
"External research anchors",
"NVIDIA Secure Agent Workspace",

6
plans/meta-prompts/loop_engineering.md
View File

@ -91,9 +91,13 @@ When implementation gets cheap, do not delete product discipline. Plans should u
- PRD/spec captures why, users, constraints, and success criteria;
- prototype makes options concrete and testable;
- every artifact declares its stage: exploration, prototype, beta, or ship candidate;
- production-looking prototypes must not imply production readiness without receipts;
- human taste and systems thinking review whether the result fits the whole product;
- scheduled/background agents may gather context, but promotion still needs receipts and review;
- role boundaries can flex, but ownership, decision rights, and phase state must stay explicit.
- role boundaries can flex, but ownership, decision rights, and phase state must stay explicit;
- model-timing assumptions are explicit: some artifacts are kept to retest when model capability changes;
- complexity budget is tracked because autonomous loops tend to add code; deletion/simplification is a first-class review criterion.
Reference: Lenny's Podcast, "OpenAI Codex lead on the new shape of product work" with Andrew Ambrosino (YouTube `P3KDebPTUrw`).