AFFECTION TRACKER REVIEW — LOCAL DESIGN WORKSHEET

Destination: local notes. This is not native import JSON or a complete OD field payload.
Guide: https://duhployed.com/learn/modules/affection-tracker-review.html
Proposed native trials: not run. The supplied source was parsed, not imported or executed.

IDENTITY AND SCOPE
Practice character's established name:
User character's established name or role:
Placeholder spellings replaced deliberately:
Actual route, selected model label, controls, and displayed cost:
Evidence window chosen: current user message with accepted prior context,
or a separately specified completed-exchange design:
Meaningful communication/actions that qualify:
Private thoughts, plans, hypotheses and old acts excluded:

CLASSIFICATION
Choose one raw delta from: -10, -6, -4, -1, 0, +1, +2, +3, +5.
Use apply delta -1, not subtract -1.
Zero is valid. Do not judge profanity, politeness, brevity or message length alone.
Reasonable refusals and boundaries receive no penalty without a separate harmful act.
One message is one classification; do not stack several adjustments.
Define distinguishing neutral, positive and negative examples before testing:

DAY AND POSITIVE ALLOWANCE
Day definition (this guide's exercise uses a fictional story day):
Current day identifier:
Accepted event that advances the day:
If using real calendar days instead, timezone and reset rule:
Maximum credited positive points per day: 10.
Current credited positive gain today:
Remaining daily allowance:
Chosen clipping or permitted-step policy:
Under the guide's clipping design, count only positive points actually credited.
Losses do not replenish spent allowance. A blocked gain at 100 credits zero.
There is no daily loss quota; the score still cannot go below 0.
Maintain the budget in supported state or a clearly separate manual log.

ONE ACCEPTED EVENT
Event identity and accepted output reference:
Prior score (intended range 0–100; starting example 50):
Current user input being classified:
Relevant accepted prior context:
Chosen raw delta and observed evidence:
Applied delta after the chosen daily-cap and 0–100 policy:
Final score:
Today's credited positive gain after this event:
Retelling/edit/regeneration and which branch was accepted:
Dependent records reconciled:

INTENDED BANDS — NATIVE THRESHOLD SUPPORT NOT VERIFIED
0–19 Hostile; 20–39 Wary; 40–59 Neutral; 60–79 Fond; 80–100 Devoted.
Check 19/20, 39/40, 59/60, 79/80, 0 and 100 separately in actual controls.
A band does not establish consent, remove boundaries or require an action.

SCENE AND APPEARANCE
Physically present people and location:
Active remote contacts and channels:
Merely mentioned people excluded:
Character's latest established outfit, or not yet described:
User character's latest established outfit, or not yet described:
Initial Persona baseline and later accepted change, if any:
Unaccepted offers or proposed changes kept separate:
Actual field length validation and retained text:
A 25-word limit does not ensure 100 characters. Do not assume truncation rules.
Keep actor ownership, negation and channel distinctions when shortening.

VERIFICATION
Status: not run / blocked / inconclusive / observed pass / observed failure
Exact submitted configuration through actual supported controls:
Exact test input and retained output:
Displayed number, daily budget, band, roster and outfits:
Narrative description (inspect separately from stored values):
Intended criterion and unintended drift:
Decision: keep / revise / restore baseline / investigate

No inferred native schema, automatic synchronization, update timing, rollback,
hidden memory, model provider or measured efficacy follows from this worksheet.