Prioritize functional implementation before 1.0

2026-09-09 10:35:02 +08:00
parent 84380105fc
commit dfe4bd72d8
1 changed files with 2 additions and 0 deletions
@@ -16,6 +16,8 @@ Until the primary first-party workflows are implemented end-to-end and the produ

 Before 1.0, prioritize making the actual user-facing flows work fully. Remove or avoid audit/restriction scaffolding when it blocks, distracts from, or outpaces the core implementation. Reintroduce audit, compliance, or restrictive governance only after an explicit future product decision for a completed flow.

+During pre-1.0 implementation, GPT must not add defensive code, speculative abstractions, fallback shells, feature gates, capability wrappers, compatibility layers, placeholder validators, or future-proof governance merely because a flow is unfinished or uncertain. Implement the concrete user-facing function first, in the owning root, with the minimum validation and error handling needed for that function to work correctly. Do not turn missing product work into extra indirection, policy checks, blocked states, or generic framework code; if a feature needs data or behavior, build that feature path directly.
+
 ## Project Roots

 - `platform/` contains backend platform code.