knowledge-candidate

Type: regulative

Decision

An observation that does not fit as a rule, a link, or a violation must be recorded as a knowledge-candidate issue rather than forced into the graph.

Why

Forcing an observation into a node shape produces an entry that passes review but gives no signal when the system drifts.

Violations

• Issue created without confirmation.
• Observation recorded as a candidate when it is actually a missing rule or link.

Anchor

no-human-touch

Implements

• constitution

Steps

1. Confirm the observation does not fit as a rule, a link, or a violation. If it does, update-knowledge-base is the process instead.
2. Draft the issue title and body. The title names the observation, and the body states the insight and references related entry ids.
3. Present the draft for confirmation.
4. Create the issue with the knowledge-candidate label.

Links

• update-knowledge-base (depends-on) — An observation reaches this path after that process establishes it does not fit the graph as an entry.

← Back to knowledge graph