Terms and boundaries¶
Terms¶
| Term | Meaning in Steady |
|---|---|
| Section | visible group of fields in the daily check-in |
| Field | definition of one daily value |
| Field version | concrete historical form of a field |
logicalId |
shared domain identity of several field versions |
| Entry | one daily record with sparse field values |
| Event | repeatable event on a date |
| Catalog Item | reusable person, sport, meal or trigger |
| Evidence | how strongly a signal contributes to the current analytical picture |
| Quality | how favorable a signal is according to its goal direction |
| Momentum | saturating function of current, time-weighted evidence |
| Life Wheel | compact 0–100 overview of several configurable axes |
| Aggregation | summary by day, week, month, quarter or year |
| Spearman-ρ | rank correlation between two time series |
| Recovery profile | selected change areas and optional program contexts |
| Counter | running period calculated from start and reset timestamps |
| Sparse | only values that are actually present are stored |
| Atomic | several changes are stored completely together or not at all |
Boundaries and open points¶
Current field/axis assignment boundaries¶
- Life Wheel axes are configurable.
- Each group can be assigned to exactly one axis.
- Fields inherit their group's axis.
- A field cannot contribute to several axes with separate weights.
- Field weights are not freely configurable.
- A field with
goal: neutralcontributes no Life Wheel signal. - Choice and text fields do not automatically contribute to the Life Wheel.
Analytical boundaries¶
- Life Wheel parameters are defined globally in code, not in the UI.
- Predefined correlations cover only selected relationships.
- Correlations are observational, not causal.
- Tracking frequency affects momentum; interpretation must therefore always consider data coverage.
- A score is a product metric, not a clinically validated measure.
Architectural boundaries¶
App.jsxstill carries substantial orchestration logic.- Analytics are calculated in the frontend.
- Browser and Android use different persistence adapters.
- There is no server, synchronization or multi-device conflict resolution.
Next clean extension¶
One possible extension would be a versioned field assignment such as:
{
"radar": {
"links": [
{ "axis": "regulation", "weight": 0.7 },
{ "axis": "connection", "weight": 0.3 }
],
"mode": "goal"
}
}
This would enable field-level instead of group-level assignment, but it would have to be implemented together in the field editor, versioning, configuration import, validation and Life Wheel engine.
Sources¶
PC Companion sandbox¶
npm run build followed by npm run sandbox:pc opens the synthetic preview at
http://127.0.0.1:4175/. Its Companion tab connects only to the loopback model
on port 8080, without reading the phone or any application database. Thinking
effort offers Off, Low, Medium and High; the data budget bounds the complete
request. Answers stream visibly, while internal reasoning stays hidden. Cancel
stops the request. Chats and controls remain in RAM. Duration and input/output
token counts describe completed requests; missing answers and output-limit
failures are explicit errors. This experiment does not change the mobile chat.
Direct APK releases¶
Both local and cloud debug builds on main publish an alpha debug test build under GitHub Releases, tagged v<version>. Download Steady-<version>-debug-<variant>.apk directly; no ZIP extraction is needed. The seven-day Actions artifact remains a fallback. This does not change the build into a production closed-trial release.
For an explicitly local-only build, include [skip ci] in the pushed commit message and manually dispatch the debug workflow on main with runner=local. This skips the automatic push workflows and avoids a duplicate cloud APK build; manual dispatch still runs. Ordinary pushes keep their cloud default. The runner uploads build outputs, not source changes.
Each published app or build-workflow change increments the alpha version and Android versionCode together. CI rejects version reuse for another commit before building and preserves existing APK assets on retries. An interrupted upload leaves an unpublished draft.