2 Commits

Include renames

Author	SHA1	Message	Date
Andy Dixon	03e2d7890a	feat(cognition): wanting, intending and acting inside the cognitive cycle ... Volition and planning now run as part of cognition (PLAN §8.2 item 3): - A volition hook derives wants after each cycle from what it perceived and produced, satisfies answer wants when a reply is sent, raises due, overdue, expired and conflicting commitments, and expires faded wants. Events produced by earlier cycles are not re-derived. - An intend process proposes deciding about the strongest undecided wants; the candidate competes for the workspace, so attention gates what the mind decides to pursue. The handler makes value tensions explicit (caution against disruptive writes, privacy against reading personal data), resolves them with recorded scores, runs deterministic formation with commitments, policy preview, goals and values, records the decision whatever it is, and plans a formed intention in the same transaction. Operator requests carry their own weight in formation. - Explicit requests in conversation ("restart <unit>", "logs for <unit>", "fetch <url>") become wants with proposed means instead of direct invocations; the reply says the request was recorded and that acting depends on commitments and policy. - The executor is woken after commits, runs in a scheduler-owned loop and reacts to the event bus: a new commitment tightens or abandons affected intentions (withdrawing their pending approvals), a weakened assumption or a finished goal triggers reconsideration. A tightened plan may reuse its strategy; a failed one may not. - Metacognition gains volition checks: strong wants repeatedly set aside, intentions with no recorded reason, intentions a commitment forbids, commitments that cannot be kept, churn, repeated failed execution, cost outweighing value, and intentions that outlived their goal. - A plan model role and prompt let a model propose decompositions that the planner validates. Ablations are a fork-only configuration field. - Approvals required by an intention are described as coming from a commitment or value constraint. The expectation after an approved action is linked to the execution event, not the request. - The wants.values column of the unreleased migration 0026 is renamed value_keys: VALUES is reserved and the generic snapshot restore does not quote identifiers. - The hostile-output security test now uses a message that asks for no action, because an operator's "status of <unit>" is legitimately a read-only status check.	2026-09-15 21:04:07 +01:00
Andy Dixon	9db188ffe6	feat(volition): wants, intentions, commitments and their decisions ... A model of volition that keeps wanting, intending and committing as separate states (PLAN §8.2 items 1–6, 14): - Wants (migration 0026) carry origin, strength with a six-hour half-life, urgency, valence, drives, values, goal, commitment and an optional proposed means. Derivation is deterministic and selective: failed predictions, contradictions, operator goals, stalled goals, questions and requests, and due commitments; drives and configured values modulate strength with recorded terms; candidates below 0.35 are not stored; identical subjects reinforce; faded and excess wants expire. - Conflicts are first-class and resolved by explicit scores with no fixed hierarchy: urgency scales strength, goals add priority, commitments add normative weight; an approach opposed by a value-derived avoid want wins outright only when clearly stronger, otherwise with a constraint or is deferred. Neither side is discarded. - Commitments (do/refrain with capability, target, access and risk matchers, optional "unless approval", due, expiry, revocability) are checked for due, overdue, impossible, conflicting and superseded states. They constrain means and never grant authority. - Formation weighs strength, urgency, goal, commitment, expected utility, risk scaled by caution, cost, privacy and autonomy; it returns formed or not formed with a reason (forbidden by commitment, denied, unavailable, no possible plan, below threshold, capacity, duplicate, deferred), and a commitment requiring approval turns an action into a request for approval. - Reconsideration maps triggers (denied or expired approval, capability or commitment change, failed step or expectation, weakened belief, budget, goal completion, world change, operator correction) to keep, block, suspend, resume, replan, require approval, abandon or fulfil, with bounded replanning. - The store records every transition as an event and every choice in the append-only volition_decisions ledger; fulfilling an intention satisfies its wants and fulfils its commitment. - Event vocabulary gains volition and plan categories.	2026-09-13 21:03:23 +01:00