Files

alvocool 16bff634b5 Initial commit: Grounded Flutter frontend

A to-do app that doesn't believe you — an enforcement layer rather than a
neutral ledger.

Architecture ported from Autoreceptives/Frontend/Receptive: stacked MVVM with
the mandatory 4-file screen pattern, one ParentViewModel owning the loading /
network / error overlays and the handleError decision tree, one AppDataManager
gateway, dio comms carrying the three identity headers, secure storage with
random-suffixed keys, and a single-chokepoint Navigator. Package root and Dart
package name are both Grounded; org is nya.

The enforcement engine, one unit per formula in utils/:

- DebtEngine      w(class) x severity(d) x decay(t), sublinear severity so old
                  misses cannot swamp the score; abandonment 2x with 30-day
                  decay immunity; late complete retains 30%
- StandingEngine  Good -> Warned -> Grounded -> Lockdown, derived not set;
                  Grounded replaces home with the overdue queue
- CapacityEngine  blocks over-scheduling against p50 of historically completed
                  minutes, with a learned per-category estimation multiplier
- IntegrityEngine session integrity, weekly volume, plyometric contact ceiling
                  and enforced recovery gaps
- ExcuseAnalyser  on-device excuse clustering plus the confrontation copy
- GuardrailEngine distress detection and rationed amnesty
- ToneEngine      all enforcement copy, so the tone cap lives in one place

CommitmentEvent is append-only and is the source of truth rather than the
status field, which is what makes honest history and excuse analysis possible.

Goals contain commitments via parentId, and a task can be run from a
full-screen runner that derives elapsed time from wall-clock so screen-off
cannot lose time. Backgrounding pauses the clock and is counted. The runner is
mirrored into an ongoing notification, with alarm-class full-screen intents
reserved for non-negotiables.

Design language, fonts, icon and native splash are in place; Mason bricks are
retargeted to this project and verified end-to-end.

flutter analyze lib/ reports no errors.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mfu2gQLSFN21YRBcU2NrTt

2026-07-27 09:11:17 +03:00

2.1 KiB

Raw Blame History

Grounded — Design Language

Reference: black device chrome, a white content sheet that rises into it with a large corner radius, oversized light display titles, tiny grey all-caps metadata labels, pill chips, and a lot of whitespace. The app reads as a record, not a dashboard.

Type — General Sans

Role	Family	Size	Use
Display	`TextType.Light`	30–44	Screen titles. Always light, never bold.
Title	`TextType.Bold`	17–20	Card and section titles.
Body	`TextType.Regular`	13–14, `height: 1.5`	Descriptions, copy.
Label	`TextType.Bold`	10–11, `letterSpacing: 0.8–1.2`, uppercase, `colorGrey2`	Metadata above a value.
Metric	`TextType.Bold`	24–34	Debt score, counts.

The label/value pair is the core unit: a tiny grey all-caps label sitting directly above a large dark value. Used everywhere numbers appear.

Geometry

Sheet radius 28, card radius 16, chip radius 999, control radius 12.
Screen padding 20 horizontal. Card padding 16. Section gap 28.
Hairlines at colorDivider (black 7%), borders at colorBorder (black 8%).
One soft shadow only: 0 4 18 rgba(0,0,0,0.03). No coloured glows.

Colour

Near-black ink (colorPrimaryDark #141414) on warm off-white (colorPrimaryLight #EDEEEA), with a single green accent (colorPrimary #2F6F4E). Enforcement tiers own the rest of the palette:

Standing	Colour
Good	green `#2F6F4E`
Warned	amber `#C98A04`
Grounded	rust `#B5442F`
Lockdown	oxblood `#7A1F14`

The tier colour is used consistently — header, chip, meter, queue accent — so the standing is legible without reading the word.

Structure

Every screen is: black headerBar (back, title, action) → white sheet with a 28 top radius → sectionHeader (label + light display title) → content.

Rules

Display titles are Light. Bold is for labels and metrics only.
Numbers get a label above them, never beside them.
Chips carry state, never actions.
One primary button per screen; everything else is outlined or text.
Empty states are plain. An empty overdue queue is good news, not a party.

2.1 KiB Raw Blame History Unescape Escape