← Back to docs

Tools Score - internal documentation and API reference

Tools Score - internal documentation and API reference

One-time discretionary bonus on an individual routine

The owner may award an explicitly chosen one-off bonus for a concrete saved applicable daily routine result greater than 0%, without modifying routine progress or prior day approvals. points are ordinary Score activity points (not privilege/benefit points), while money is an extra SEK cash award in minor units outside the capped ordinary daily/monthly allowance, like separate solidarity awards.

Unversioned owner-only CSRF APIs: GET /api/score/participants/{participant}/routine-bonuses?date=YYYY-MM-DD, POST same route with date, activity_id, reward_type (points|money), positive integer amount, required reason (3-500 characters) and idempotency_key (UUID); DELETE /api/score/participants/{participant}/routine-bonuses/{award} to revoke. Points are limited to 100000 and money to 1000000 minor units per decision. The API validates participant and activity ownership, actual saved progress, no 'not applicable' flag, scheduling and audience. It accepts historical approved days, but no absent, excluded or 0% outcome. One active award per participant/activity/date; a revoked award is retained and a fresh action can grant another. Retried UUIDs return only the original grant even after revocation. Writes use participant-first then activity-row locking and independently auditable operations with correlation IDs.

The forward-only migration adds score_routine_bonus_awards with immutable routine title/progress snapshots and a separate revocation record on the row. Activity deletion detaches the ID while preserving awarded history, and participant deletion removes scoped award rows. Owner monthly earnings and printed statements include active extra cash outside the ordinary allowance cap and active extra ordinary Score points. Full statement history shows active/revoked awards. Linked history follows share_linked_history, and cash numbers additionally require share_allowance_rules. Guest/linked money terms are not widened by the write API. No automatic transfer.

Individual AI outlook for linked Score participants

AI usage is charged against the owner's funding source using the same request ID for credit preflight and settled token usage.

The owner-only POST /api/score/participants accepts optional goal_ai_instructions (up to 2,000 characters) at participant creation. The owner may later read or update it with GET/PUT /api/score/participants/{participant}/goal-outlook-settings. PUT uses an instructions JSON field; an empty string clears the objective. Only the owner can read or edit these encrypted, audited instructions.

GET /api/score/me/linked/{participant}/goal-outlook requires a signed-in recipient with an accepted participant link. It returns status (initial, pending, running, queue_timeout, ready, failed, credits_exhausted or provider_quota), text, generated_by_ai, has_saved, outdated, generated_at, requested_at, can_refresh and bounded goal/approved-day counts. Only the first visit with an objective or open goal automatically queues AI generation. Saved encrypted text remains available during regeneration. When the guardian saves changed private objective instructions, the backend automatically queues a new analysis once for an accepted linked account, with owner attribution; unchanged saves and routine changes alone do not requeue. Pending work older than 180 seconds or a running worker inactive for 90 seconds enters queue_timeout, awaiting deliberate retry. No goals or objective returns a careful first message without an AI request.

POST /api/score/me/linked/{participant}/goal-outlook requires the same accepted recipient link, authenticated web session and CSRF. It explicitly requests a new AI analysis, with queue deduplication and rate limiting. The JSON response uses the GET contract. Any earlier encrypted result is retained while generation is pending or if it fails (including exhausted guardian credits). Operations are audited and failures reported to #toolsapi independently. Neither endpoint changes Score calculations or allows public caching.

Saved routine results are also included as bounded aggregate counts: recorded entries, entries below 100%, explicit zeros and days with incomplete entries. Not-applicable routines, day-type exclusions and out-of-schedule entries are excluded using the canonical schedule rules. Historical details are available only when the guardian enabled share_linked_history; otherwise the snapshot uses current-day registrations plus already visible approved-day summaries. Historical sampling is limited to the latest 200 rows within 90 days and flagged at the cap. Saved AI text records whether historic sharing contributed; if consent is later withdrawn, the previous private-history-based assessment is not returned, the response reports privacy_changed, and a fresh assessment may be requested.

AI input is limited to the owner's personal objective, up to eight open goal titles and checklist completion counts, and up to twenty approved daily percentages over ninety days. Names, private notes, incidents, financial rules and automatically retrieved identity fields are excluded. The guardian's own objective is sent verbatim and may itself contain names. Generated text is encrypted at rest. The outlook is available only on /me/score and the signed-in linked statement, not on guest share links.

A user linked as a recipient to another account's Score, without owned participants, is redirected from /score, /score/open and /score/statistics to the personal /me/score results page. Personal results and any monthly statement remain limited by the guardian's sharing settings. Recipients cannot use owner APIs to create participants, activities or points. Accounts owning participants retain their editor. An accepted participant link grants no guardian permissions.

Daily review - saved versus missing outcomes

For the selected participant and date, the daily approval preview identifies each scheduled routine by its persisted result. Missing entries display "Ej registrerat" (not recorded) instead of appearing as saved zero-percent failures; an explicitly saved 0% remains visible as 0%. The preview shows saved and expected counts. Automatic finalization still requires all results to be recorded. A guardian may manually approve an incomplete day after explicit confirmation; missing outcomes count as zero in the approval calculation. Existing saved outcomes and approved historical snapshots remain untouched.

Manual infraction consequences

The owner can select manual deductions and combine manual_points (0-100000) with manual_bonus_percent (0-100) on the same incident. A positive daily bonus deduction requires an agreement effective on the incident date and cannot exceed its max_daily_bonus_percent. It only affects unapproved daily bonuses, never monthly base or approved monetary snapshots. log_only never deducts anything. Edits and deletions remain owner-scoped and audited.

Explicit repricing of previously approved daily cash

Under Score > Follow-up > Recalculate earlier daily earnings, the guardian selects a month and previews current vs proposed cash for already approved days. The saved allowance threshold/payout mode is used only after explicit confirmation. There is no automatic historical payment, new daily approval or decrease to money already earned. Previously recorded routine percentages, comments and privilege ledger entries are not modified; manually corrected or reapproved days are excluded and unapproved days require individual approval.

The calculation uses the approved day's persisted integer percentage, rather than silently recomputing historic results from later activity weights or schedules. It reserves the remaining gross monthly cap (including agreed deductions) and applies the originally stored day deduction percentage to newly awarded gross money. Cash corrections are source-tagged (policy_recalculation) and include before/after penalty snapshots so monthly statements present the added gross bonus, added agreed withholding and net payment accurately.

The owner-authenticated, CSRF-protected, unversioned GET /api/score/participants/{participant}/daily-bonus-recalculation?month=YYYY-MM returns a read-only preview and fingerprint. POST to the same path requires month, preview_token and a 3-500 character reason. Under the canonical participant-first lock, a changed plan, approved amount, correction or review rejects the old preview with HTTP 409. A confirmed change writes a cash correction and independent audit row for each affected day using one correlation ID. No API, bank transfer, unrelated participant or cash-transfer integration is invoked.

Retroactive daily reapproval

Owner-only PUT /api/score/participants/{participant}/daily-reviews/{review}/reapprove accepts reason (3-500 characters) and items, a complete array of the scheduled weighted routine ids, completion percentages, applicability, optional notes and times. It updates routine progress and recalculates the existing approved daily snapshot atomically, using participant-first locking and normal bonus, cap and infraction policy. No second approval is inserted. The score_daily_review_revisions table retains before/after review and routine records for each correction with a correlation id and actor. Daily benefit points are reconciled on the existing unique ledger row. Ownership and scheduled-activity membership are checked server-side; the API remains unversioned. Past real-world payments are not automatically reversed.

Scrum activity workflow

The Scrum board remains on the owner's Score tab, but is no longer rendered on the linked participant's /me/score page. Owner Scrum cards also expose canonical_complete for saved 100% routines. Such cards cannot be reopened through Scrum alone; the owner must change the canonical daily result first. Both Scrum GET endpoints now reflect canonical current-day score_routine_progress: a saved applicable 100% routine shows done, partial progress shows doing, and yesterday's done does not automatically carry over. Unscheduled activities, day-type exclusions and saved/inherited not-applicable routines are filtered from the day board. Standalone optional Scrum tasks retain their explicit workflow status; no history or approvals are rewritten. Saving a 100% complete or exempt routine through the normal Score editor also closes any active Scrum timer in the same write transaction, with audit. Starting a recurring task whose previous Scrum status is from yesterday creates today's new status and timer and closes prior stale timing at the day boundary.

Selected-day event records are queried with exact database date predicates before category and history row limits, constrained to the allowed last 90 days and only with guardian disclosure. The recent-history summary retains its own limits. The linked /me/score UI shows an inline month statement overview, selected-date routines and an event list when the guardian permits detailed history. Recent approved days, comments and the AI forecast remain. The complete printable statement still requires both share_linked_history and share_allowance_rules; the dashboard does not independently reprice cash awards.

The optional Scrum workspace reuses canonical score_activities, score_events and score_comments. It does not create separate Score activities or automatically approve a day or pay rewards. Owner-only GET /api/score/participants/{participant}/scrum and PUT /api/score/participants/{participant}/scrum/{activity} support status values todo|doing|done, with participant and activity-audience authorization. Supplementary statuses and work intervals are stored in score_scrum_states and score_scrum_work_sessions. Canonical activity creation and updates use the existing POST /api/score/activities and PUT /api/score/activities/{activity} endpoints; the update accepts an optional name for backwards-compatible editing. Activity-level comment threads use score_comments.activity_id and the standard Score comments endpoints.

Accepted linked accounts can read GET /api/score/me/linked/{participant}/scrum, returning can_manage and applicable card names/statuses, never points or work intervals. Guardian-specific GET/PUT /api/score/participants/{participant}/scrum-settings controls scrum_manage_enabled, default false. Only a currently accepted linked participant with explicit permission may call PUT /api/score/me/linked/{participant}/scrum/{activity} with todo|doing|submitted or POST /api/score/me/linked/{participant}/scrum/activities to add an assigned zero-point, optional-weight card. A child cannot reopen a guardian-completed card or perform financial approvals. Both comment endpoints support scoped activity_id threads and preserve the existing linked-history visibility rules. The owner completes submitted work using a canonical Score event. Moving to Done records extra activities through idempotent POST /api/score/events, or scheduled routines through PUT /api/score/participants/{participant}/routine-progress/{activity} with date and percentage. The status endpoint verifies the corresponding canonical record before accepting done. Safe participant/activity deletion includes Scrum status, intervals and activity comments.

This is the detailed technical reference, including API contracts, authorization and data-handling rules. For practical instructions see the user guide. Score in Tools Family.

Compensating routines and editing solidarity

A guardian may link an approved solidarity offset to a recorded incomplete routine and date. A routine registered at 85% may receive up to 15 percentage points of separately reported compensation. Original progress and already approved daily earnings are never rewritten. Events may be edited or soft-deleted; editing an approved event revokes its original reward and creates an immediately approved replacement in the same transaction.

Documentation links

Tools Score is available to signed-in users at /score. It is listed under Personal tools in /services, searchable by "score", and can be pinned to the shared navigation taskbar. A shortcut is also available on the signed-in dashboard. It uses the existing ToolsAPI session and CSRF protection. Participants, activities, monthly allowance settings, comments and activity records are owned by the signed-in account. A solidarity event can independently grant extra activity points and cash, with or without offsetting a previous deduction. Both effects share approval and revocation but are listed separately. The bonus does not consume the offset allowance, and cash is outside the routine monthly cap.

The API uses the unversioned /api/score prefix.

Participants and activities can be created from the interface. Activity records have an immutable point-value snapshot, so changing an activity's configured points does not retroactively alter historical totals. The server enforces the participant's plus/minus point switches. Comments may refer to a participant or a specific activity record. Changes are recorded in a separate audit trail.

Monthly allowance configuration includes a cap, optional base amount and a daily bonus pool. By default, 100% weighted day completion is required to earn any daily cash bonus, regardless of an older saved threshold. The guardian may explicitly enable daily bonuses below 100%, selecting a minimum qualifying percentage and either proportional or full at threshold payment. With a 15 SEK daily pool and a 75% threshold, an 80% day earns 12 SEK in proportional mode or 15 SEK in full-at-threshold mode, before agreed penalties and the monthly cap. Below the threshold or at exactly 0% completion, the award is 0. Not-applicable routines are excluded from the weighted denominator; a day with no relevant routines never receives daily cash. Both manual approval and automatic post-day settlement use this same logic. Actual completion percentages are always retained, with historical approved cash snapshots never recalculated. The authenticated, owner-scoped routine-progress response also supplies weighted_progress and expected_weight so the opt-in monetary preview can match backend cents: three equally weighted outcomes 100%, 100%, 99% predict 9.97 SEK of a 10 SEK pool, not 9.90 from the whole-number display. Preview excludes any subsequent cap or agreed deduction. An explicit 0% minimum threshold is displayed as such. Eligibility and proportional pay use the exact weighted numerator/denominator, not a rounded display percentage; three equally weighted results of 100%, 100% and 99% are not a full day and display as 99%, never as a false 100%. Benefits and the separately configured calendar-month top-up retain their independent eligibility policies. Saving a plan does not automatically award money or issue payments. Approved daily reviews record any earned bonuses, without transferring money.

Goals and checklists are managed per participant, with levels and achievability from 1–5, optional target dates, and personal/reward/planning categories. API: GET/POST /api/score/participants/{participant}/goals, POST /api/score/goals/{goal}/steps/{step}/complete and POST /api/score/goals/{goal}/approve. All checklist steps must be complete before approval. Approval does not automatically issue payments or network privileges.

Daily allowance policy API

The existing authenticated, owner-only CSRF-protected PUT /api/score/allowance-plans/{participant} accepts allow_partial_daily_bonus (boolean), completion_threshold_percent (integer from 0 to 100), and optional daily_bonus_payout_mode: proportional (the default, including existing opted-in plans) or full (whole daily pool on reaching the threshold). Older clients omitting the new field preserve the saved mode. The existing GET /api/score/allowance-plans and authorized statement/disclosure reads report the selected policy. Manual and automatic approvals and explicit reapprovals all apply the same exact weighted computation and stored historical payout rules.

The optional additional_bonus_tiers field is an ordered JSON array of at most eight objects, each with integer minimum_percent (1-99) and payout_percent (1-100), e.g. [{"minimum_percent":50,"payout_percent":50}]. Minimum thresholds must be strictly increasing and lower than the existing completion_threshold_percent, with nondecreasing payouts as completion rises. Under a proportional main policy no lower tier may pay more than the main threshold pays. Below the main threshold, the highest qualifying lower tier pays its fixed percentage of the daily pool; the main proportional/full mode continues unchanged at and above its threshold and 100% receives the full pool. Exactly 0% and all-exempt days receive zero. Omitted arrays preserve existing saved tiers for older clients; explicitly saving [] clears them. Owner authorization, CSRF, exact weighted progress, agreed deductions, monthly cap, audit and explicit positive-only historical recalculation remain unchanged. Shared/linked recipient surfaces show tier rules only with the guardian's existing allowance disclosure consent.

Delayed infraction entry without retroactive consequences

The guardian's Document an infraction form supports an earlier occurrence date, severity and factual reason even when no consequence policy applied on that date. The event is stored in the actual infraction ledger (not diverted to observations), explicitly tagged has_agreed_consequence=false with zero deducted points and daily cash, and a 100% neutral cap. Later configuration changes do not recalculate this historic decision. Earlier approved earnings are unchanged. Owner-only session/CSRF access, audited writes and UUID request idempotency are unchanged; read-only shared history discloses incidents only when the guardian expressly enables detailed history, with a no-agreement label.

Daily reviews and earnings

A parent selects a date and records each scheduled routine's completion percentage (0–100%). The server calculates the day's weighted completion from the routines due for that participant and date, using their importance levels. Approval saves a decision and any earned bonus, subject to the monthly cap. A day without scheduled routines cannot be approved, and a day cannot be approved twice. Apply the normal database migrations (including score_auto_finalize_cursors) before enabling the existing Laravel scheduler. php artisan score:auto-finalize-days runs every 15 minutes and stores a composite date/owner/participant cursor, so a large backlog of incomplete dates cannot prevent later eligible days from being settled. It considers explicitly recorded progress from the past 60 days. The score:auto-finalize-days schedule can now finalize a past day automatically, but only when every applicable scheduled routine has an explicitly saved percent, including zero. The current day cannot be settled automatically, missing entries are never invented as zero, existing immutable review snapshots are never rewritten, and the job is safe to repeat. Manual approval remains for exceptional cases. The selected approval date no longer clears after saving; a selectable Days awaiting approval list shows outstanding dates for the selected month with recorded coverage and provisional percentages, including missing and unscheduled dates. Today's progress is labelled preliminary on owner-approved read-only shares and linked child accounts until settlement, without suggesting a preliminary bonus was earned. Historical event quantities remain available for activity tracking; they do not replace routine progress in the daily approval calculation. No money is transferred automatically.

API: GET/POST /api/score/participants/{participant}/daily-reviews, GET /api/score/participants/{participant}/daily-reviews?month=YYYY-MM, PUT /api/score/participants/{participant}/daily-reviews/{review} and GET /api/score/participants/{participant}/monthly-earnings?month=YYYY-MM. The optional GET month filter returns all approvals for the specified month. The page shows this history under the selected month, and the review date selector updates the month. PUT changes only credited_minor (integer minor units; 1 SEK = 100) and requires a reason of 3-500 characters; it preserves the previous completion percentage, checks the participant's monthly cap, stores a before/after correction record and independent audit, and requires the owning web session with CSRF protection. POST requires review_date (YYYY-MM-DD); expected_quantity is optional and no longer determines the day's expected routines. The server derives that count from the schedule. A saved allowance plan and at least one due routine are required. Access is owner-only.

Routine importance: The web form provides Optional (0), Normal (1), Important (2), and Very important (3). The API still accepts the existing daily_weight range (0–1000). Each due positive-weight routine counts once per day and supports partial completion (0–100%) with an optional comment. On approval, excluded_activity_ids can exclude specific activities for that decision; excluding all due routines prevents approval. Approved reviews store weighted totals.

Guardian-controlled allowance rule visibility

Under Share Score without an account, the owner/guardian decides per participant whether the child may see detailed allowance rules. Default for new and existing participants is off. Read-only summaries retain approved days, completion and credited daily amounts, but the monthly base, daily bonus requirements, monthly cap, top-up and deduction mechanics are hidden. The setting takes effect immediately for existing share links and consented linked accounts; only the owner can change it. Sharing expiration, revocation and AI summaries remain independent. Enabling visibility shows the full rules without changing payout calculations.

Owner-only CSRF-protected unversioned endpoint: PUT /api/score/participants/{participant}/allowance-disclosure with share_allowance_rules: true|false. Only the owner sees the preference in GET /api/score/participants. The linked participant endpoint returns allowance: null while rules are hidden, and public read-only shares omit the whole allowance rules panel. Changes are audited; recipients cannot override privacy.

Shared activity history and monthly statement for linked child accounts

The guardian now has a separate Show factual history to linked participant accounts preference, default off for both new and existing recipients. When explicitly enabled, the existing read-only linked Score API can return up to 90 days of positive and negative observations, infractions, routine percentages, assessed extras, comments and original day notes. No note data is returned before this permission is granted. Anonymous sharing-link permissions remain independent.

When Share detailed allowance rules is also enabled, an accepted linked recipient can open /me/score/statement?month=YYYY-MM, a printable read-only monthly statement calculated by the same reconciled owner service. Private full-month qualification settings remain hidden if the guardian has excluded them. Direct access also requires the accepted account link and is invalidated on revocation. No recipient write controls are exposed.

Assessment notes and extra activity points

Extra completed tasks can include a separate optional assessment reason. A performed task assessed below 100% remains in the history with its actual success and missed percentages and earns zero extra activity points. Only a 100% successful, points-enabled extra receives its configured score. Original requested points and assessment reason are persisted on new records to protect idempotent retries from subsequent activity edits. Historical settled points and money are not recalculated.

Inline historical agreement attestation

Guardians can already register factual past infractions without consequences when none applied on the event date. A new explicit incident-form checkbox permits truthful attestation that the original unchanged agreed consequence levels applied earlier. The attestation and dated incident are saved atomically and independently audited; prior priced events or revisions prevent backdating, and previously neutral notes or approved cash are never repriced.

The shared Tools navigation now displays a compact Score shortcut only when the authenticated account owns at least one Score participant or has a valid, explicitly accepted participant link. No shortcut appears for guests, accounts with no Score data, or pending/declined/revoked recipients. Guardians open the existing editable /score workspace; linked participants open My results at /me/score, a read-only mobile-friendly page showing routine completion, approved days and only guardian-permitted allowance information. When an account has both roles, the navbar offers both destinations.

The role-aware /score/open entrypoint is shared with Android's existing authenticated Score WebView Home shortcut, and routes guardians to /score or linked recipients to /me/score. New users can still reach /score from Services to create their own Score. Every recipient read remains subject to the existing accepted owner/target link boundary in GET /api/score/me/linked/{participant}. The new navigation and page never grant write access or expose other participants' data.

Under Share Score without an account, guardians can opt in to Show recorded activity, positive/negative outcomes, notes and day history when creating a link. Each active link also offers a checkbox to enable or disable detailed history later without rotating its token. Existing links remain private by default. When enabled, the guest can see the latest 90 days of factual positive and negative observations, dated recorded infractions with reasons, assessed extra activities including earned points and percentages, event comments and original day notes. A recorded incident with no applied penalty is documented as a fact, not treated as a cash deduction. AI summaries remain separately opt-in.

The guest Monthly statement (payslip-style) link appears only when BOTH this link's include_history and the guardian's participant-level Share detailed allowance rules choice are enabled. It reuses the canonical read-only reconciled statement, with month selection and print/PDF, actual approved bonus amounts, corrections, deductions and point ledgers. Without both consents it is not accessible through the guest URL. If the guardian has disabled disclosure of full-month-bonus terms, the guest statement also hides qualification thresholds, private notes and qualifying-day counts even when the earned amounts may be viewed. The owner's own full statement is unchanged. Revocation and expiration apply to both pages. Free text is escaped, no guest write action is exposed, and the same controls work through the authenticated Android Score WebView. Because history may include personal notes, sharing it requires a deliberate opt-in.

API: PUT /api/score/participants/{participant}/shares/{share} with include_history: true|false requires owner web session, CSRF, the correct participant and an active link. Guest reads use GET /shared/score/{token} and GET /shared/score/{token}/statement?month=YYYY-MM and honor token validity and disclosure preferences.

Monthly statement and parent-controlled full-month bonus

From Score, choose a participant and month under Completion and select View monthly statement (payslip-style). The read-only, print-friendly page groups approved daily allowances by their historical amount per day (quantity × unit price), shows the monthly base and any full-month top-up, lists each approved bonus deduction and each actual monetary correction on a separate dated line, and reconciles exactly to the month's earned total. Separately, ordinary activity points group by historical activity and recorded points snapshot (quantity × points); every negative activity entry and agreed incident deduction appears explicitly. Any available privilege-point ledger is a third section, never money. Print or save to PDF from the browser. Only the signed-in owning account can open GET /score/participants/{participant}/statement?month=YYYY-MM; unknown participants return 404. A statement does not transfer money or alter approvals.

A parent can configure full-calendar-month top-up independently from the daily allowance. The monetary qualification rule is snapshotted with its effective calendar month when saved; changing a later month's level does not retroactively requalify completed earlier months. The default is enabled, 100% on every calendar day, with the top-up applied only after the complete calendar month ends. It can be disabled or configured to another per-day minimum percentage (0-100); every calendar day must still be explicitly approved, so one successful day can never qualify an entire month. A below-threshold day may be approved and retained at its actual percentage with zero cash daily bonus, allowing an independently configured monthly minimum to be assessed honestly. All paid penalties remain paid penalties, and the calculation continues to respect the monthly cap. The parent can separately choose whether recipients of a read-only share or accepted linked-account view can see the eligibility explanation and can provide a custom explanatory note (up to 600 characters). The custom note is display text only, not a calculation rule. Turning off the explanation does not hide actual approved amounts or the monthly total. These configuration options belong to the owner; the linked user cannot change them.

Transparent allowance rules, outcomes and configurable consequences

Read-only Score share cards now show the actual saved monthly base, daily bonus and qualifying percentage, cap, approved-day coverage and the full-month cap top-up rule. A full-calendar-month top-up is calculated only after the calendar month has ended and each calendar day meets the saved minimum for that month (100% by default, configurable by the owner). Any approved daily-bonus penalties reduce the final amount by their actual, capped value only; they do not forfeit the entire remaining top-up. A one-day 100% result does not imply a fully completed month. Base allowance is monthly; daily awards are separately configured and subject to the cap. The same rule summary is returned to an explicitly consented linked participant at GET /api/score/me/linked/{participant}. The public share remains a revocable noindex read-only capability link and does not disclose private infractions or their reasons.

Every routine now displays both the completed and uncompleted percentage (95% achieved is also 5% not achieved) in the editor and linked read-only overview. The routine editor's input, status, note and Save controls remain available and responsive in the Android first-party Score WebView. Optional extra completions remain performed even with success_percent=0 and no points: the owner chooses a 0-100% success score and whether the entry awards any points. When point awards are enabled, only a 100% successful extra task earns its full activity score; lower assessments earn zero extra points. Extra outcomes are stored alongside the original event transaction and do not alter existing daily-routine approvals. Older events without an outcome are displayed as 100% performed for backward compatibility.

Changing a previously agreed policy is forward-only: the updated levels start the following calendar day, never for incidents before the change. Score preserves the earlier agreement and uses the date-appropriate levels when recording historical incidents. Further edits to a next-day pending agreement update only that pending version; existing recorded incident consequences stay unchanged. On changing participants, policy editing is disabled until the selected person's policy is successfully loaded, preventing accidental overwrites if a request fails. If the unchanged original levels really were agreed before their first recording, the guardian may enter an earlier prior-agreement date under Configure consequence levels and separately attest that those identical levels were already understood. An already-saved initial policy may have its start moved earlier only before any incident or policy revision exists. The recorded original date, earlier attested date, timestamp, actor and correlation ID remain in a separate auditable history. Even without a prior agreement, the guardian may record the actual incident in infraction history with its original date and severity, marked as having no agreed consequences and zero deductions. New penalties cannot be backdated. Ordinary changed levels still start the next calendar day.

Owners can create an agreed and documented minor, serious or critical infraction policy per participant. The configuration has separate points and unapproved-daily-bonus deduction percentages for each tier, plus an overall daily bonus percentage cap. The owner must explicitly acknowledge that the rules have been agreed in advance; the system cannot independently prove consent. No event is hard-coded as an example or auto-detected as a violation. Infraction registrations require a date, severity, factual reason and a UUID Idempotency-Key, are audited and retain the rule's point/deduction/cap snapshot. An infraction cannot reduce monthly base or change an already approved day's award automatically. The new day's bonus is reduced by the capped agreed percentage during approval; prior applied deductions are reserved against the gross monthly cap so later bonuses or full-month top-ups do not silently reverse them. Later adjustments to approved days require the existing separately audited manual correction procedure.

Owner-only web/CSRF API: GET /api/score/participants/{participant}/infractions, PUT /api/score/participants/{participant}/infraction-policy, POST /api/score/participants/{participant}/infractions. Existing extra-activity POST accepts optional success_percent (0-100) and awards_points (boolean), defaulting to 100 and true for legacy clients. Its GET includes performed, success_percent and awards_points from the per-event outcome. Participant/event/owner safe deletions clean up new tables; independent structured audits remain. No route URL versioning, router access control or automatic monetary transfer is introduced.

One-off completed activities

Under Daily routines, select a participant and a date (including a past date), then use Extra completed on this day. Choose an existing activity, or leave Create new extra activity selected and enter a name such as "Showered" with optional points (default 0). Click Record as completed. The new activity definition is reusable and optional (daily_weight=0); no recurring schedule is created. Completed extra activities appear separately beneath the scheduled routines for that date, including after the daily review is approved. They do not change the scheduled completion percentage (for example 100% of 4), past approval or earned allowance. Existing activities can also be recorded without changing their schedules. The same dated records remain visible in activity history.

When an activity definition is being deleted, a simultaneous extra-completion save cannot silently create an orphaned history entry. The operation either saves against the still-existing activity or rejects the now-deleted activity. If a deletion preview becomes stale because a completion was added, review the deletion again before confirming.

Owner-only, web-session/CSRF-protected API: GET /api/score/participants/{participant}/extra-activities?date=YYYY-MM-DD lists dated activity events; POST /api/score/participants/{participant}/extra-activities accepts date (not in the future), and either activity_id or name plus optional integer points (-100000 to 100000, default 0). POST requires an Idempotency-Key UUID header so retries cannot create duplicate events. The activity and completion are saved together; plus/minus point permissions and audit still apply. This API does not change daily routine progress or monetary approvals.

For each extra completion, an optional comment (up to 5,000 characters) can explain what happened and why the assessment was given. The comment is saved atomically with the event in the existing owner-only Score comments history and shown with the dated extra event. Retries with the same idempotency key must carry the same comment; changing it returns 409 instead of silently rewriting the saved assessment. An unexpected server failure now returns a safe JSON error code and correlation ID for support, rather than an unhelpful HTML 500. Android uses the same authenticated Score web form.

Score workspaces on desktop and Android

The signed-in /score page now opens on the Register tab (the first tab on the left). It contains the chosen participant's daily quick actions, routine percentages and comments, extra completed activities for earlier dates, ordinary activity/event registration and the daily approval action. This keeps daily recordkeeping separate from occasional setup.

Use People & links to add participants, connect their Tools accounts, review invitations and manage read-only share links. Use Activities & schedules to create/edit activities, manage groups, configure recurring schedules or reusable day types, and safely delete records after preview. Use Follow-up for monthly completion and earnings charts, the history of approved days and allowance corrections, allowance configuration, observations, goals, comments and day notes.

On narrow screens, including Android's embedded Tools WebView, the tabs appear as a horizontally scrollable, touch-friendly strip. The leftmost Register tab is always the default; scroll the strip sideways for other tabs without switching browser pages. Tab selection can also be opened by a direct #score-register, #score-people, #score-activities or #score-followup link and survives a reload via that hash. Keyboard users can use Left/Right Arrow, Home and End on the tab controls. Switching tabs does not save or discard form values, change the selected participant, rerun a transaction or alter authentication. If the small tab script cannot initialize, the original single-page cards remain visible.

Built-in web interface

/score is a standalone Blade view using AJAX fetch calls to the existing session-authenticated /api/score API. The local ToolsAPI page no longer requires React or Vite build artifacts. Account owners can create participants and activities, record historical events and observations, manage goals and checklists, approve days, configure allowance plans and view basic statistics. Observations never change points or money automatically. The standalone React client remains independent.

Shared activities with optional participants

Activities and groups remain shared across one Score owner account. When creating or editing an activity, choose All participants (default) or Choose participants to specify whose routines include it. This keeps one reusable activity definition without duplicating it for each child. New participants automatically receive all-participant activities but do not inherit a restricted activity.

The choice affects due routines, daily approvals, quick-day actions, schedules, new ordinary/extra completion records and a linked participant's read-only routine view. Activity group, point value and importance stay shared; schedules, individual progress and allowance stay separate. Existing activities start as All participants. Changing the selected participants does not rewrite any historical activity events, point snapshots or previously approved allowance amounts. Deleting the last selected participant does not widen scope to everyone.

The existing owner-only, web-session/CSRF-protected activity create and update APIs accept an optional participant_ids array with at most 100 distinct IDs owned by that account. Omitting it on update preserves the current selection; an empty array selects everyone, and a nonempty array restricts applicability. Foreign/invalid IDs are rejected atomically. Activity list responses expose audience_mode and participant_ids. All existing API paths remain unversioned and Android uses the same Score WebView.

Default relevance for daily completion percentages

Under Created groups, choose the group's Default relevance: Included in the daily percentage or Not relevant by default. Under Created activities, each activity can choose Inherit from group, Included in the daily percentage, or Not relevant by default. An activity-specific choice overrides its group's setting.

When an activity is first recorded for a date, its effective default is saved with that day's result. In both Today's registrations and the detailed Daily routines editor, the activity's relevance dropdown can override this for that particular date. Updating the group or activity default later does not rewrite saved daily decisions, previously approved amounts or historic points.

Importance is different: Normal (1), Important (2) and Very important (3) control how strongly a relevant activity affects the weighted daily percentage. Not relevant for this day removes that activity from the percentage calculation entirely; it is neither a success nor a failure. A relevant activity recorded at 0% is an actual unmet task, not an exemption. When no relevant routines remain, there is no weighted daily bonus percentage to compute.

For example, toothbrushing can normally carry low importance (1), but be exempted on a particular day without changing its status on other days.

Set activity importance and group-wide weighting

In Score > Activities and schedules > Created activities, select Edit on an activity. Set its importance to Optional (0) (excluded from weighted daily completion), Normal (1), Important (2) (twice the weight), or Very important (3) (three times the weight), then save. Daily importance is separate from the activity's point value.

To apply one importance level to every activity in a group, expand the group under Created groups, choose Shared importance, and select Apply to group. For example, apply Normal (1) to both morning and evening toothbrushing. If you want different weights, edit the activities individually. Group-wide changes do not alter activity points or participant scope.

Example: Four meals weighted 3 each and two toothbrushing tasks weighted 1 each produce 14 total weight units. Meals account for 12 of them, and toothbrushing for 2. Missing a toothbrushing task therefore affects the daily percentage less than missing a meal. Other scheduled routines also contribute to the total.

Allowance: By default, all weighted routines must reach 100% for any daily bonus. Enable Allow daily bonus below 100% in the allowance settings, choose the minimum threshold and either proportional or full-at-threshold payment. Previously approved daily amounts and historic event points are not recalculated. Review the preview before approving a day.

Times: Today's routine and extra-activity registrations record the current time automatically. An optional time field can specify when the activity actually happened, including for a past date.

Solidarity rewards and offsetting earlier deductions

Under Score > Daily registrations, use Solidarity - helping others. Select the participant who helped, the date, optionally the person who received help, and a factual description.

Choose No reward, Activity points, Benefit points, Money, or Reduce an earlier point deduction. For an offset, select an existing infraction. The offset cannot exceed the remaining points deducted for that infraction, and the original record stays intact.

Saving as the guardian approves the event immediately. Rewards count as soon as the save succeeds. An approved event may later be Revoked, retaining the history and reversing any benefit points already credited. Editing an approved event revokes the earlier reward and records an approved replacement atomically, without a second approval. Older pending events can still be manually approved or rejected. Revoked events cannot be approved again.

Cash solidarity rewards are recorded in cents and outside the ordinary monthly allowance cap. They increase overall reported earnings without rewriting previously approved daily bonuses. Activity points, benefit points and offsets are separately represented in the monthly statement and statistics. All event statuses remain visible in the owner history.

For an approved event, Save positive AI comment voluntarily sends only the event date and a predefined, general action category to OpenAI; free-text descriptions, names and amounts are never sent, then saves the result as a clearly labelled comment. Revoking the event labels its earlier AI comment as revoked. No provider call is made simply by creating or approving an event.

The guardian-only, CSRF-protected endpoints are GET/POST /api/score/participants/{participant}/solidarity, PUT /api/score/participants/{participant}/solidarity/{event}/decision, and POST /api/score/participants/{participant}/solidarity/{event}/positive-feedback. Creation requires an UUID Idempotency-Key. All changes are audited and safe operational diagnostics are independent of audit settings.

Positive feedback with OpenAI

Under Comments, the registrar first writes their own feedback. Choose Preview AI-rewritten feedback to get a calmer, factual suggestion. Confirm it before saving the recipient-visible version. The original is stored privately and separately. No points or earnings change.

Editing activities and inspecting group contents

The Created activities list shows the saved points and importance of every activity. Select Edit to change its points (integer -100000 through 100000) or daily weight (integer 0 through 1000) without deleting it. Existing event point snapshots are never recalculated. Custom existing weights outside the four preset options are kept when the editor opens, including if only points are changed. Only the owning signed-in web user with CSRF protection can call PUT /api/score/activities/{activity} with both required JSON fields points and daily_weight. Changes are audited.

Expand an activity group (for example, Meals) to see its member activities and their points. The group still only organizes activities; deleting it does not delete its activities.

Activity groups and assignments

Create a group (for example, Meals) and assign activities to it. Saved groups appear in Activity groups, with the number of assigned activities, and remain visible after a page reload. A group's name must be unique within the owner's account, ignoring case and extra whitespace. Deleting a group requires confirmation; its activities become ungrouped while activity records and history remain intact. All changes use the authenticated AJAX API.

Recurring schedules and daily routines

Under Recurring schedule, choose a participant and activity, a start date, an optional end date and a recurrence: daily, every N days or selected weekdays. Schedules belong to the selected participant. Without a custom schedule, an importance-weighted activity is due every day. Only activities due on the selected date appear in Today's routines and the daily approval preview. Partial routine completion is supported, and a day without due routines cannot be approved.

Adjusting the monthly allowance and daily bonus

The Allowance and daily bonus section shows a theoretical maximum for the selected calendar month, assuming every day qualifies for its bonus. The Adjust amounts control offers three choices: calculate the daily bonus while keeping the monthly cap and base amount, calculate the monthly cap while keeping the daily bonus and base amount, or calculate the base amount while keeping the cap and daily bonus.

The calculation uses 28, 29, 30 or 31 calendar days as appropriate, and rounds the calculated daily bonus upwards to the nearest cent. The forecast assumes all days qualify and does not account for participant-specific routine schedules or previously approved days. The completion threshold, monthly cap and existing earned amounts continue to be enforced by the server. Adjusted amounts are drafts until the account owner clicks Save; selecting an adjustment never saves automatically. The saved allowance plan is displayed from the server-confirmed result, including the daily bonus. If a section fails to load, other available Score sections remain visible with an error notice rather than appearing deleted.

Tools account linking with recipient consent

From /score, regular account owners invite a participant to an existing Tools account by entering its email address. Acknowledged administrators instead get a searchable, limited Tools account picker showing matching names and email addresses. No ordinary user can access this directory, including by calling the search API directly. The administrator selects a user ID to link a participant that the administrator owns. An ordinary invitation is pending for at most seven days and the recipient must sign into Tools and explicitly accept or decline in their own Score interface. Sending an invitation never grants access. Only an acknowledged administrator or a registered parent matching the target user's parent_user_id may link directly, and only for participants owned by the requesting account.

Both the owner and the recipient can revoke an existing link. An account cannot be linked to more than one Score participant at a time, and an occupied participant cannot be reassigned before its current link has been revoked. Account lookup responses do not reveal whether an unknown address exists.

The linked account receives a separate read-only view of only its own due routines and their completion percentages, monthly earned allowance and recent approved daily summaries. It cannot use the owner's event, approval, allowance, participant or scheduling mutation endpoints. No other participants or private parent comments are returned. Existing Score APIs continue to enforce owner access. Accepted, declined, direct and revoked links are recorded in score_audit. Unexpected persistence errors are independently sent to #toolsapi without recipient email addresses, SQL or credentials.

The admin-only, rate-limited GET /api/score/admin/users immediately returns up to 20 active users (users containing id, name, email) for the dropdown. Supplying q=search filters the directory literally by name or email once at least two characters are entered; clearing the search restores the initial 20-user list. An acknowledged administrator is required for either form of the request. POST /api/score/participants/{participant}/link-request accepts email for regular invitations; only acknowledged administrators may instead supply target_user_id. Both paths preserve recipient, owner and audit checks. The monthly earnings response includes calendar day counts, full-month status and any cap-limited top-up; the total never exceeds the monthly allowance cap.

The session- and CSRF-protected unversioned routes are GET /api/score/link-requests, POST /api/score/participants/{participant}/link-request, DELETE /api/score/participants/{participant}/link (owner); GET /api/score/me/invitations, POST /api/score/me/invitations/{invitation}/respond (body: decision=accept or decline), GET /api/score/me/linked, GET /api/score/me/linked/{participant}?date=YYYY-MM-DD&month=YYYY-MM and DELETE /api/score/me/linked/{participant} (recipient). These routes do not authorize external bearer/JWT clients.

Safely delete Score data

An owner can use Safe deletion on /score to remove an individual participant, shared activity definition, logged event, or activity group. The interface first shows the precise dependent counts and which records will be removed or merely unlinked. The owner must enter the resource name exactly and explicitly confirm. It is irreversible. An attached recipient/child cannot delete their own or anyone else's Score resources: account-linked reads remain read-only.

A participant deletion removes that participant's events, comments, observations, checklists and goals, daily approvals/credited history, routine progress, individual schedules and exceptions, allowance plan and account-link invitation/consent state. Shared household activities and groups, and other participants' records, remain untouched. Deleting an activity removes its event records, routine progress and schedules/exceptions across affected participants, while preserving observation text and comments by clearing the references to the deleted activity/events. Deleting an event similarly preserves existing comments without their deleted event association. Previously approved day decisions and their credited amounts remain historical snapshots when just an event or activity is deleted. Deleting a group only ungroups its activities; all events/history remain.

The session-only, CSRF-protected unversioned API uses GET /api/score/deletions/{type}/{id} to return a preview with counts, name, expires_at, and a signed token. DELETE /api/score/deletions/{type}/{id} requires JSON {name, expires_at, token}; the signed preview is owner-, resource-, name- and dependent-state-bound and expires in 10 minutes. Stale confirmations return HTTP 409 without partial deletes; callers must preview again. Allowed types: participant, activity, event, group. Legacy DELETE /api/score/activity-groups/{group} remains available but now requires this same signed confirmation. All deletions commit atomically with a separately queryable score_audit event. Unexpected operational errors independently reach #toolsapi, with safe context only. The Score read APIs and client authentication model have not changed.

Deleting an activity from its row now shows the impact preview and typed-name confirmation beside that activity.

Copying active Score share links

Under People & links > Share Score without an account, an owner can copy any still-active sharing URL from the list after reloading the page. Each link has a wide, selectable address field and a Copy link action, including in Android's signed-in Score WebView. Revoked and expired links are hidden from the active list and cannot be copied. The list is available only to the participant's owner, and no encrypted token value is returned.

New links store only a SHA-256 lookup hash and an encrypted copy of their random token. Older links originally stored only the hash, so their exact URLs cannot be recovered. For these, the owner can explicitly choose Replace with copyable link: after confirmation, the old URL is immediately revoked and a new active URL is created with the same label, AI-summary choice and original expiration date. The owner must send the new URL to its intended recipient; no recipient is silently redirected. All changes are owner-authorized and audited, and the read-only recipient privacy settings remain unchanged. This functionality is available through the existing session-only, CSRF-protected unversioned GET /api/score/participants/{participant}/shares and new POST /api/score/participants/{participant}/shares/{share}/replace endpoints. The list response is private and not cached.

Configurable ongoing and one-time benefits

Score supports ongoing benefits such as Internet and one-time benefits such as VR sessions, travel or a rail trip. These are examples, never hard-coded privileges. Owners configure name, description, either a rolling window (1-365 complete calendar days) or the last 1-12 fully completed calendar months, required completion percent (0-100), calculation (minimum for every day or average across the window), optional benefit-point cost and enabled state. Every calendar day in the window ending yesterday must have an approved daily review; missing or unapproved days block qualification. Today's unfinished work does not revoke Internet at midnight. A new participant with only one 100% day cannot qualify for a full-month benefit: the completed prior month must contain an approved daily review for every calendar date. The status separately shows the average of approved days, the approved/required coverage, missing days and eligibility, so one good day never appears to be a completed month. Partial current months never qualify as completed calendar months. The monthly Score dashboard likewise labels the average as applying to reviewed days and displays approved days versus calendar days. The guardian can change each benefit's period and rule at any time. The status shows period dates and eligibility.

An ongoing benefit with zero cost is conditionally available whenever the rolling quota holds. With a nonzero point price, the owner pays once to activate it; if quota later drops, eligibility becomes inactive until recovered without another purchase. A one-time benefit can be explicitly redeemed repeatedly if each redemption is qualified and the wallet has enough points. This records entitlement only: Score does not switch a router on/off, book travel, approve purchases or pay money automatically. A parent remains responsible for real-world permission and any actual use.

A daily review may be approved even without any allowance plan, at zero cash credit. A daily review may also be approved below the configured cash bonus threshold: the actual completion percentage is recorded, cash bonus is zero, and the day still counts honestly toward benefit calculations. A different benefit-point earning threshold may apply. This separates the quota from monthly allowance eligibility.

Optional completed activities can also earn privilege points independently of daily routine percentage and monetary allowance. The owner must enable Earn benefit points from extra completed activities in the benefit-point settings. For each extra activity, choose a benefit multiplier of ×1, ×2 or ×3: an awarded 1-point extra task at ×2 earns 2 privilege points. A performed activity assessed at 0% or with point awards disabled earns 0 benefit points. Each extra event credits at most once; changing the outcome or deleting the activity does not retroactively rewrite previously credited ledger entries. The benefit multiplier does not change the activity's daily routine weight, wage or allowance.

Benefit points use their own ledger separate from activity points and monthly allowance. Under Benefit settings an owner may configure the minimum approved-day percentage and points earned per qualifying day. Grants occur atomically when a new daily review is approved, once per review, from the date on which the settings were first enabled; previously approved days are not retroactively credited. Changing the policy does not rewrite prior ledger entries or allowance. Redemptions use participant-scoped DB locking, a required UUID Idempotency-Key, captured point price and audit history; retrying cannot double-charge, and a second purchase with insufficient balance is rejected.

The owner-only, CSRF-protected unversioned API is GET /api/score/participants/{participant}/benefits, PUT /api/score/participants/{participant}/benefit-settings, POST /api/score/participants/{participant}/benefits, PUT /api/score/participants/{participant}/benefits/{benefit} and POST /api/score/participants/{participant}/benefits/{benefit}/redeem. Existing participant safe deletion includes benefit definitions, settings and point ledger; permanent score_audit operations are retained. The same Score GUI is reachable in Android's first-party session-authenticated WebView.

Warnings, consequences and sharing a monthly statement

The Statistics tab now shows the number of warning/deviation observations and recorded infractions per participant and month, including severity levels and whether a consequence agreement applied. Expand a participant to see dated reasons and assessed point deductions. A stated daily-bonus deduction percentage reflects the registered rule, not necessarily an amount of money deducted from earnings.

The guardian can open Score > monthly statement for a participant and month and select Share this monthly statement. A new link gives read-only access to exactly the chosen month for 1-90 days. The guardian can copy it, view active links, and revoke access at any time. The recipient requires no login and receives no access to the broader Score history, other months or editing controls. Share only with intended recipients; anyone with an active link can view the monetary details shown on that statement. These links are separate from general Score sharing consent.

Participant comments and threaded replies

A person with an accepted linked Tools account can submit optional feedback under Personens kommentar at /me/score. Pick a note date, write a comment, and submit. Replies remain grouped under the note's thread. Use Kommentera noteringen on a shared observation or day note to attach feedback to that exact record, even when several notes share a date. The guardian must enable linked history sharing before the participant can read or comment on these records. The guardian can view and reply under Kommentarer at /score, with author roles and timestamps shown. Comments cannot change points, approvals or assessments.

The participant can always see their own comments. Guardian-authored comments remain hidden until the guardian enables share linked history for that participant. The account link must remain accepted and active. Public share tokens never grant comment-writing access.

The existing session- and CSRF-protected API exposes GET and POST /api/score/me/linked/{participant}/comments. POST accepts required body and optional note_date (YYYY-MM-DD) and parent_comment_id for replies. The existing guardian comment endpoint accepts the same optional thread fields. Comments do not enter any financial calculation.

Under Personens kommentar, a linked participant can enter their own draft and choose Föreslå formulering med OpenAI. OpenAI proposes a respectful wording based on that draft without inventing facts or feelings. The suggestion is displayed separately, not saved, and can be accepted or discarded. Only the user's own Skicka kommentar action saves a comment. Text is sent to OpenAI only on explicit request. POST /api/score/me/linked/{participant}/comments/suggest requires accepted linking, an authenticated session and CSRF protection, and is throttled to four requests per minute.

Log-only incidents and manual deductions

Score: Infractions support log-only recording without consequences or manual point deductions without an agreement.

Day overview without manual approval

Register shows every calendar date up to today in the selected month, including completely untouched dates. The overview prioritizes untouched, partly recorded, fully recorded, no-schedule days, then settled days. Select a date to enter routine progress later. Missing progress is distinct from an intentionally saved 0% assessment. Results are visible as soon as they are recorded. Past days with every due routine explicitly recorded are already settled automatically; manual approval is optional. Incomplete days stay open and are not silently assigned scores or cash. Previously settled days use the existing audited reapproval flow. Owner-only GET /api/score/participants/{participant}/pending-review-days?month=YYYY-MM&include_all=1 includes settled dates for the overview; omitting include_all retains the original pending-only response.