Principles
Grunna is built on a small set of principles that guide how work is planned, executed, and finished.
These principles are not goals or values. They are constraints that shape behavior and protect the system from drift.
Finish over starting
Progress in Grunna is defined by finished work.
Starting work has no value unless it leads to completion. The system is designed to minimize work in progress and maximize outcomes that are actually done.
Order over estimation
Grunna does not rely on time estimates to plan work.
Instead, work is ordered in a single list. The position of an item expresses its priority and makes trade-offs visible.
This replaces time-based promises with clear ordering and predictable execution.
Consequence over debate
Decisions in Grunna are expressed through ordering work, not through prolonged debate.
Reordering the list makes trade-offs visible immediately. This replaces abstract arguments with concrete consequence.
Execution is stable
Planning may change at any time. Execution does not.
Once work has started, it is protected from interruption. This preserves focus and prevents partial work from accumulating.
Changes are handled by reordering what comes next — not by constantly reshuffling what is already in motion.
Bug-first is mandatory
Bugs are not optional in Grunna.
Broken or misleading behavior undermines trust in the system. Bugs interrupt the queue and are resolved before planned feature work continues.
This keeps the product usable and prevents “later” from becoming never.
Ideas are not work
Ideas are allowed to exist without becoming tasks.
Thinking and clarification happen before execution. Work starts only when responsibility and outcome are clear.
Done is final
Completed work does not move back into execution.
If something was wrong, new work is created. History is not rewritten.
Design shapes behavior
Grunna assumes discipline is required.
The system is designed to support disciplined decisions and reduce the need to rely on constant self-control during execution.