deciwa

decision watcher – point at an element of a doc, website or source file and say what you think of it. deciwa keeps that tied to exactly that element, notices when the element changes and shows at any time what is confirmed, open or frozen. It collects, evaluates and shows; the work itself is done by the AI or the developer.

Every front end talks to the CLI, never to the files directly.

How these docs work

These docs are the single source of truth for everyone who develops deciwa. Decisions are requirements: every feature and every piece of code must fit them. Each statement is a Sphinx-Needs object with an id and a status.

Object	Prefix	Status	Meaning
Decision	DEC_	approved	decided by Daniel – binding
Proposal	PROP_	draft → review → approved / rejected	part of the technical details of a version, not binding yet
Question	Q_	open → answered	someone has to decide something

An approved proposal becomes a decision: it gets a DEC_ object in Decisions, and the technical page links to it.

Waiting for a decision

ID	Title	To	page
Q_CORE_LANG	Python for the core and the CLI?	Daniel	technical/stack
Q_FINGERPRINT_MARKUP	Should pure formatting changes make an approval stale?	Daniel	technical/state-engine
Q_MARKERS	Does deciwa replace [CHECK] and [ASSUMPTION], or only [CHECK]?	Daniel	technical/rollout
Q_NEED_TYPES	Which directive names count as needs?	Daniel	technical/adapters
Q_QUICK_ACTIONS	Are there quick actions besides delete?	Daniel	technical/skills
Q_REVIEW_UI_01	How does Daniel review in 0.1 without an editor integration?	Daniel	technical/rollout
Q_SKILL_INSTALL	How do the skills get into a project?	Daniel	technical/skills