humansense2system

# Humansense → system ## Contract | Field | Bound contract | |---|---| | Trigger | User wants to compile taste and "this feels wrong" into tokens, rules, forbidden combinations, and examples | | Authority | reversible-local: write only the named local artifact; state the rollback path | | Side effect | One structured rule/pattern document written to the project shared docs or agent-rule folder | | Done | At least one classified entry exists across any section (Forbidden, Tokens, Examples, or Rules) and the user has validated the artifact | ## Inputs Must be supplied: - **Target artifact path** — a file under the project shared docs or an agent-rule folder that stores the human's agent-facing patterns Optional: - **Existing patterns** — any prior rule/pattern document at the same path; the procedure merges into it ## Procedure 1. **Elicit raw taste signals.** Ask the user for concrete cases where the outcome felt wrong, off, or missing, rather than abstract preferences. Record each as a named signal with the observable behavior, not the inferred cause. Stop when the user says they have listed what they can. 2. **Classify each signal.** For every named signal, ask the user to place it into one bucket: - FORBIDDEN: must never happen - TOKEN: a named flag or category the agent can recognize and route on - EXAMPLE: a concrete input-output pair that defines what is acceptable - RULE: a conditional statement (if-then) that captures the boundary If the user ca...