mchus/bible
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add timeout, busy-state, parser-variant and build-freshness rules

Browse Source 
- task-discipline: require explicit target platform/language before implementation
- go-api: bounded context deadline on every outbound network/DB call
- controls-selection: visible busy state for any control triggering such a call
- import-export: enumerate real format variants before writing a parser
- app-binary: embedded assets do not hot-reload; verify rebuild before diagnosing

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Mikhail Chusavitin
2026-08-18 21:00:42 +03:00
co-authored by Claude Opus 5
parent e092fea98f
commit 59e3107197
5 changed files with 42 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
rules/patterns/task-discipline/contract.md
+9 -1
View File
@@ -1,11 +1,19 @@
# Contract: Task Discipline
Version: 1.0
Version: 1.1
## Principle
Finish before switching. A task is not done until it reaches a logical end.
## Scope Definition
- Before implementation starts, the task description must state the target platform and language
explicitly: CLI, server-rendered web app, desktop app, library, and the language/runtime it runs on.
- If the platform is not stated, ask before writing code. Do not infer it from the surrounding repo.
- A platform pivot after implementation invalidates connection, config, and transport plumbing built
around the previous shape. Treat such a pivot as a new task, not as a continuation.
## Rules
- Do not start a new task while the current one is unfinished. Switching mid-task leaves half-done work that is harder to recover than if it had never been started.