edify-agents-cli 0.2.0__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (102) hide show
  1. edify/__init__.py +19 -0
  2. edify/__main__.py +6 -0
  3. edify/_toml.py +286 -0
  4. edify/agents.py +261 -0
  5. edify/anim.py +499 -0
  6. edify/assets/commands/build.md +64 -0
  7. edify/assets/commands/plan.md +68 -0
  8. edify/assets/commands/spec.md +63 -0
  9. edify/assets/commands/tasks.md +65 -0
  10. edify/assets/commands/verify.md +67 -0
  11. edify/assets/formats/plan.example.md +455 -0
  12. edify/assets/formats/plan.format.md +128 -0
  13. edify/assets/formats/spec.example.md +483 -0
  14. edify/assets/formats/spec.format.md +116 -0
  15. edify/assets/formats/tasks.example.md +712 -0
  16. edify/assets/formats/tasks.format.md +199 -0
  17. edify/assets/harvest/harvest.md +91 -0
  18. edify/assets/harvest/sources.md +295 -0
  19. edify/assets/harvest/vocab.md +52 -0
  20. edify/assets/manifest.md +30 -0
  21. edify/assets/mcp/default-registry.md +66 -0
  22. edify/assets/skills/adversary.md +61 -0
  23. edify/assets/skills/debugger.md +64 -0
  24. edify/assets/skills/implementer-general.md +53 -0
  25. edify/assets/skills/implementer-go.md +63 -0
  26. edify/assets/skills/implementer-node.md +61 -0
  27. edify/assets/skills/implementer-postgres.md +63 -0
  28. edify/assets/skills/implementer-python.md +65 -0
  29. edify/assets/skills/implementer-react.md +65 -0
  30. edify/assets/skills/planner.md +58 -0
  31. edify/assets/skills/test-writer-node.md +64 -0
  32. edify/assets/skills/test-writer-python.md +60 -0
  33. edify/assets/skills/verifier.md +67 -0
  34. edify/assets/templates/CLAUDE.md +18 -0
  35. edify/assets.py +77 -0
  36. edify/cli.py +681 -0
  37. edify/commands/__init__.py +1 -0
  38. edify/commands/check_cmd.py +72 -0
  39. edify/commands/doctor_cmd.py +206 -0
  40. edify/commands/feedback_cmd.py +90 -0
  41. edify/commands/governance_cmd.py +65 -0
  42. edify/commands/graph_cmd.py +156 -0
  43. edify/commands/harvest_cmd.py +538 -0
  44. edify/commands/init_cmd.py +333 -0
  45. edify/commands/init_new_cmd.py +151 -0
  46. edify/commands/license_cmd.py +80 -0
  47. edify/commands/mcp_cmd.py +159 -0
  48. edify/commands/self_cmd.py +185 -0
  49. edify/commands/setup_cmd.py +79 -0
  50. edify/commands/skills_cmd.py +177 -0
  51. edify/commands/upgrade_cmd.py +178 -0
  52. edify/context.py +57 -0
  53. edify/conventions.py +275 -0
  54. edify/detect.py +313 -0
  55. edify/distribution.py +40 -0
  56. edify/errors.py +66 -0
  57. edify/feedback.py +207 -0
  58. edify/formats/__init__.py +11 -0
  59. edify/formats/check.py +573 -0
  60. edify/formats/document.py +238 -0
  61. edify/formats/finding.py +50 -0
  62. edify/formats/fix.py +114 -0
  63. edify/formats/mcp.py +126 -0
  64. edify/formats/plan.py +151 -0
  65. edify/formats/skill.py +139 -0
  66. edify/formats/spec.py +164 -0
  67. edify/formats/tasks.py +321 -0
  68. edify/governance.py +316 -0
  69. edify/graph/__init__.py +11 -0
  70. edify/graph/extract.py +351 -0
  71. edify/graph/ignore.py +107 -0
  72. edify/graph/langs/__init__.py +93 -0
  73. edify/graph/langs/ctags.py +145 -0
  74. edify/graph/langs/markdown.py +41 -0
  75. edify/graph/langs/patterns.py +361 -0
  76. edify/graph/langs/python_ast.py +154 -0
  77. edify/graph/langs/sqlish.py +86 -0
  78. edify/graph/model.py +102 -0
  79. edify/graph/queries.py +211 -0
  80. edify/graph/store.py +157 -0
  81. edify/harvest/__init__.py +28 -0
  82. edify/harvest/ledger.py +191 -0
  83. edify/harvest/screen.py +236 -0
  84. edify/harvest/sources.py +298 -0
  85. edify/host.py +345 -0
  86. edify/interview.py +354 -0
  87. edify/library.py +176 -0
  88. edify/licensing/__init__.py +30 -0
  89. edify/licensing/ed25519.py +154 -0
  90. edify/licensing/projects.py +223 -0
  91. edify/licensing/tier.py +172 -0
  92. edify/licensing/token.py +149 -0
  93. edify/paths.py +282 -0
  94. edify/selfinstall.py +244 -0
  95. edify/skills.py +108 -0
  96. edify/tsv.py +109 -0
  97. edify/ui.py +334 -0
  98. edify_agents_cli-0.2.0.dist-info/METADATA +408 -0
  99. edify_agents_cli-0.2.0.dist-info/RECORD +102 -0
  100. edify_agents_cli-0.2.0.dist-info/WHEEL +4 -0
  101. edify_agents_cli-0.2.0.dist-info/entry_points.txt +2 -0
  102. edify_agents_cli-0.2.0.dist-info/licenses/LICENSE +21 -0
@@ -0,0 +1,128 @@
1
+ # The `plan.md` format
2
+
3
+ The technical handoff between the spec and the task list. It carries every decision
4
+ that binds more than one task, so no task has to make one. The worked instance is
5
+ `plan.example.md`.
6
+
7
+ Written when the feature introduces a technology, spans milestones, needs
8
+ cross-cutting strategy, or will be built by more than one person. Skipped
9
+ otherwise, and skipping it is the normal case.
10
+
11
+ ---
12
+
13
+ ## Frontmatter
14
+
15
+ ```yaml
16
+ ---
17
+ feature: team-invitations
18
+ spec: spec.md
19
+ status: draft # draft | approved | amended
20
+ milestones: 6
21
+ date: 2026-08-06
22
+ supersedes: —
23
+ ---
24
+ ```
25
+
26
+ ## The sections
27
+
28
+ ```
29
+ # plan — <feature>
30
+ ## Milestones the sequence, then the dependency rules with their reasons
31
+ ## Technology decisions each row naming the alternative it beat, at an exact version
32
+ ## Cross-cutting migrations, variants, assets, shared components, verification budget
33
+ ## Per-milestone goal · requirements · gate · size · files · context seeds
34
+ ## Parallelization what may overlap, what may not
35
+ ## Risks each mapped to the milestone that mitigates it
36
+ ```
37
+
38
+ ## `## Milestones`
39
+
40
+ | id | delivers | requirements covered | gate | size |
41
+ |---|---|---|---|---|
42
+ | M1 | capture and calibration skeleton | REQ-1, REQ-2, REQ-5 | three calibrations within ±5% | M |
43
+
44
+ Then the dependency rules in prose, one line each, **each stating why**:
45
+
46
+ > M2 must complete before M3, M4 and M5 — they all consume its pipeline output.
47
+
48
+ The reason matters because `/tasks` uses the rule to assign phases, and a rule with
49
+ no reason is a rule nobody can safely relax when the plan is amended.
50
+
51
+ ## `## Technology decisions`
52
+
53
+ | # | decision | version | beat | why |
54
+ |---|---|---|---|---|
55
+ | D-1 | Pose estimation runs on-device with a bundled model | model-x 0.10 | a cloud inference API | the spec's offline constraint kills every cloud option |
56
+ | D-2 | Local transfer uses embedded server library Y | 2.3 | library Z, raw sockets | Y is 400 KB and already a transitive dependency; Z adds 6 MB for features unused here |
57
+
58
+ **A row names the alternative it beat.** A row with no alternative is a default,
59
+ which is fine and should say so — a default is much cheaper to revisit than a
60
+ decision, and the difference matters when someone reopens it in six months.
61
+
62
+ **Versions are exact.** `2.3`, not `^2.3`, not "latest". This column is what the
63
+ documentation server is pointed at, and it is what makes a builder write against
64
+ the API that is installed rather than the one it remembers.
65
+
66
+ ## `## Cross-cutting`
67
+
68
+ Everything no single task can own because it is a property of the whole build. What
69
+ appears here is repository-specific; what is universal is the reason — two tasks
70
+ each making an independently reasonable choice produce an inconsistent system.
71
+
72
+ - **Migration ownership** — version number → milestone → what it adds. Allocated
73
+ here, once, so two tasks never claim the same number.
74
+ - **Build variants** — what each includes, declares, and forbids.
75
+ - **Bundled assets** — each asset, its size, its variant, and a total. A size budget
76
+ stated here is a budget; discovered at the end it is a problem.
77
+ - **Shared components** — introduced in one milestone and reused in three others,
78
+ named here so the later three do not each build their own.
79
+ - **Verification budget** — every assertion the spec marks `model` or `proof`, with
80
+ its tool and the milestone carrying the cost.
81
+
82
+ ## `## Per-milestone`
83
+
84
+ ```
85
+ ### M2 — pose inference and signal processing
86
+
87
+ Goal: per-frame inference, outlier rejection, filtering, differentiation
88
+ Requirements: REQ-3, REQ-6..REQ-10
89
+ Gate: ≥85% retention on clean input, ≥95% rejection on occluded
90
+ Size: L
91
+ Migration: V2 (frame table)
92
+
93
+ Affected files
94
+ src/vision/inference.ts new
95
+ src/db/schema.ts:118-146 edit
96
+
97
+ Context seeds
98
+ spec.md:44-71 the assertions this milestone must satisfy
99
+ src/vision/frame.ts:12-58 the existing frame type it extends
100
+ ```
101
+
102
+ **The context seeds are why this document pays for itself.** `(file, line-start,
103
+ line-end, why)`, resolved against the graph at plan time so `/tasks` inherits them
104
+ instead of re-deriving them. A seed without a line range transfers its cost
105
+ downstream, which is the whole thing the plan exists to prevent.
106
+
107
+ ## `## Parallelization` and `## Risks`
108
+
109
+ Parallelization is stated at the milestone level; `/tasks` computes the exact
110
+ task-level answer from the graph. A milestone pair marked parallel here that the
111
+ graph later shows overlapping is a planning error worth catching.
112
+
113
+ Risks get one row each: what it is, which milestone it lands in, and the specific
114
+ thing in this plan that mitigates it. A risk with no mitigation has been noticed
115
+ rather than handled, and the row should say so rather than looking handled.
116
+
117
+ ## What this is not
118
+
119
+ Not a design document — no function signatures or data structures beyond the
120
+ contracts. Not read by the builder. Not a schedule: sizes and sequences, never
121
+ dates. A plan that carries dates becomes wrong on a schedule and gets ignored on
122
+ the same one.
123
+
124
+ ## What `edify check` reports
125
+
126
+ A technology row with no version, or a loose one (`^2.3`, `latest`). A row naming
127
+ no alternative and not calling itself a default. A context seed with no line range,
128
+ or one that does not resolve against the graph.
@@ -0,0 +1,483 @@
1
+ # IRA7 BIOMECH
2
+
3
+ > **This is the worked example for `spec.format.md`, and it calibrates *tone and
4
+ > completeness* rather than section layout.** It is a real specification for a real
5
+ > product, not an invented illustration, which is why it is worth reading: it says
6
+ > *why* before *what*, it names the user before the features, it makes the platform
7
+ > constraints explicit, and it ends with hard product rules that bound everything
8
+ > above them. A spec that opens with a component list has already lost the thread.
9
+ >
10
+ > It is longer than most specs need to be because the product is large. **The shape
11
+ > is what to copy, not the length**, and the section contract — `## Brief`,
12
+ > `## Intent`, `## Constraints`, `## Requirements`, `## Assertions`,
13
+ > `## What this entails`, `## Open questions`, `## Non-goals` — is stated once in
14
+ > `spec.format.md`. Write that structure, in this voice.
15
+
16
+ ## Product Vision
17
+
18
+ IRA7 BIOMECH is a completely offline Android application designed to analyze the biomechanics, physical development, and performance trends of a single football athlete over time.
19
+
20
+ The app acts as a long-term biomechanical coaching system that learns from the athlete's historical data, identifies trends, highlights risks, and provides actionable coaching insights based entirely on:
21
+
22
+ - The athlete's physical profile
23
+ - Recorded training sessions
24
+ - Biomechanical measurements
25
+ - Longitudinal performance data
26
+ - Left-vs-right asymmetry trends
27
+ - Historical progression and regression patterns
28
+
29
+ The app does not use cloud services, accounts, subscriptions, telemetry, or external servers. All processing, storage, and analysis occur locally on the coach's Android device.
30
+
31
+ ---
32
+
33
+ # Core Philosophy
34
+
35
+ The purpose of IRA7 BIOMECH is not simply to collect numbers.
36
+
37
+ Its purpose is to answer the coach's most important questions:
38
+
39
+ 1. Is the athlete improving?
40
+ 2. Is the athlete becoming more efficient?
41
+ 3. Is the athlete becoming more resilient?
42
+ 4. Is the athlete showing signs of fatigue or injury risk?
43
+ 5. What should the coach focus on next?
44
+ 6. What are the key suggestions we could give soely based on the data? No external tools
45
+
46
+ All recommendations generated by the app are based on the individual athlete's own profile and historical trends rather than generic population averages.
47
+
48
+ ---
49
+
50
+ # Target Athlete
51
+
52
+ The system is built around a developing football athlete with:
53
+
54
+ - Significant growth potential
55
+ - Active growth plates
56
+ - Long-limb biomechanics
57
+ - High acceleration demands
58
+ - High deceleration demands
59
+ - Frequent unilateral actions
60
+ - Strong reliance on a primary plant leg
61
+
62
+ Because of this profile, the app places special emphasis on:
63
+
64
+ - Acceleration efficiency
65
+ - Deceleration quality
66
+ - Elastic/reactive performance
67
+ - Movement asymmetries
68
+ - Injury-risk indicators
69
+ - Development trends over time
70
+
71
+ ---
72
+
73
+ # Primary User
74
+
75
+ ## Coach/Player
76
+
77
+ The coach/player is the sole operator of the application.
78
+
79
+ The coach or the player:
80
+
81
+ - Records training sessions
82
+ - Reviews the data collected can be unexperiences so it reads the recommendations
83
+ - Tracks longitudinal development
84
+ - Uses coaching recommendations
85
+ - Makes training decisions based on the recomendations
86
+
87
+ The system must translate complex biomechanical data into clear coaching language.
88
+
89
+ ---
90
+
91
+ # Athlete Profile System
92
+
93
+ The athlete profile acts as the foundation of all analysis.
94
+
95
+ Stored information includes:
96
+
97
+ - Name
98
+ - Date of birth
99
+ - Height
100
+ - Weight
101
+ - Leg length
102
+ - Shank length
103
+ - Dominant foot
104
+ - Preferred position
105
+ - Growth status
106
+ - Injury history
107
+ - Training history
108
+
109
+ The profile evolves over time as new measurements are added.
110
+
111
+ All future analyses use the most current athlete profile unless historical values are required.
112
+
113
+ ---
114
+
115
+ # Training Analysis
116
+
117
+ The application analyzes training sessions using smartphone video capture.
118
+
119
+ Supported analysis categories include:
120
+
121
+ ## Sprint Performance
122
+
123
+ Measures:
124
+
125
+ - Trunk lean
126
+ - Shin angle
127
+ - Step length
128
+ - Step frequency
129
+ - Ground contact time
130
+ - Flight time
131
+ - Knee drive
132
+ - COM velocity
133
+ - COM acceleration
134
+ - Sprint efficiency
135
+
136
+ Purpose:
137
+
138
+ - Monitor acceleration ability
139
+ - Detect over-striding
140
+ - Evaluate force application quality
141
+
142
+ ---
143
+
144
+ ## Elastic and Plyometric Performance
145
+
146
+ Measures:
147
+
148
+ - Reactive Strength Index (RSI)
149
+ - Jump height
150
+ - Takeoff velocity
151
+ - Leg stiffness
152
+ - Vertical stiffness
153
+ - Ankle stiffness
154
+ - Contact quality
155
+
156
+ Purpose:
157
+
158
+ - Monitor explosive ability
159
+ - Track fatigue
160
+ - Evaluate elastic development
161
+
162
+ ---
163
+
164
+ ## Deceleration Performance
165
+
166
+ Measures:
167
+
168
+ - Braking capacity
169
+ - Deceleration magnitude
170
+ - Approach velocity
171
+ - Exit velocity
172
+ - Stop distance
173
+ - Braking-leg performance
174
+
175
+ Purpose:
176
+
177
+ - Monitor the athlete's most important protective and performance skill
178
+ - Identify declining braking ability
179
+ - Detect increased injury risk
180
+
181
+ ---
182
+
183
+ ## Change of Direction Performance
184
+
185
+ Measures:
186
+
187
+ - Plant mechanics
188
+ - Knee valgus
189
+ - Foot plant position
190
+ - Trunk control
191
+ - Direction-change efficiency
192
+ - Movement initiation
193
+
194
+ Purpose:
195
+
196
+ - Evaluate cutting performance
197
+ - Identify risk factors
198
+ - Improve movement efficiency
199
+
200
+ ---
201
+
202
+ # Longitudinal Intelligence
203
+
204
+ The most important feature of the system is trend analysis.
205
+
206
+ The app continuously compares current performance against:
207
+
208
+ - Personal bests
209
+ - Recent training blocks
210
+ - Seasonal averages
211
+ - Growth-period baselines
212
+ - Fatigue markers
213
+ - Recovery markers
214
+
215
+ The app should answer questions such as:
216
+
217
+ - Is acceleration improving?
218
+ - Is braking capacity improving?
219
+ - Is RSI trending upward?
220
+ - Is ground contact time increasing?
221
+ - Is asymmetry becoming worse?
222
+ - Is the athlete adapting positively?
223
+ - Is performance declining?
224
+
225
+ No recommendation should rely solely on a single session.
226
+
227
+ Recommendations should prioritize multi-session trends and historical context.
228
+
229
+ ---
230
+
231
+ # Coaching Engine
232
+
233
+ The coaching engine is entirely athlete-specific.
234
+
235
+ Recommendations are generated using:
236
+
237
+ - Athlete profile
238
+ - Historical metrics
239
+ - Session outcomes
240
+ - Development trends
241
+ - Fatigue indicators
242
+ - Asymmetry data
243
+ - Injury-risk markers
244
+ - Suggestions for the player. Specific based on their weeknesses and how to improve them.
245
+
246
+ Examples:
247
+
248
+ - “Left-leg braking performance has declined over the last 3 sessions.”
249
+ - “Ground contact time is increasing while sprint performance is stable, suggesting fatigue.”
250
+ - “RSI has improved consistently across the last training block.”
251
+ - “Knee valgus during left-leg cuts is trending upward and should be monitored.”
252
+ - “Acceleration performance has plateaued. Horizontal force development may need additional emphasis.”
253
+
254
+ The system should prioritize actionable coaching insights over raw metrics.
255
+
256
+ ---
257
+
258
+ # Left-versus-Right Monitoring
259
+
260
+ Every unilateral metric must be tracked independently.
261
+
262
+ Examples:
263
+
264
+ - Ground contact time
265
+ - Step length
266
+ - Shin angle
267
+ - Braking performance
268
+ - Jump performance
269
+ - RSI
270
+ - Stiffness
271
+ - Knee mechanics
272
+
273
+ The application must continuously calculate Limb Symmetry Index (LSI) and identify:
274
+
275
+ - Improving symmetry
276
+ - Stable symmetry
277
+ - Worsening symmetry
278
+ - Injury-risk thresholds
279
+
280
+ ---
281
+
282
+ # Analysis Interface
283
+
284
+ The coach should be able to:
285
+
286
+ - Select either match or training mode (differnt model and UI for each based on the need of each, mathc=analyze the team and the individual movements, training more in detail data)
287
+ - Select or conect multiple phones select if 2d analyzis or 3 phones for 3d analysis. 3d should be connected using a qr code or a all phones conect to the same network using a phones mobile hotspot.
288
+ - Watch video playback
289
+ - Use an opensource best model for detecting the player and the needed points and joints for the analysis
290
+ - View skeleton overlays
291
+ - View center-of-mass tracking
292
+ - View metric graphs
293
+ - Compare sessions
294
+ - Review trend reports
295
+ - Scrub frame-by-frame
296
+ - Correct detected events manually
297
+
298
+ Video and data visualizations must remain synchronized at all times.
299
+
300
+ ---
301
+
302
+ # Session History
303
+
304
+ The application stores:
305
+
306
+ - Videos
307
+ - Metrics
308
+ - Athlete measurements
309
+ - Trend data
310
+ - Coaching notes
311
+ - Drill history
312
+
313
+ The coach should be able to compare:
314
+
315
+ - Today's session
316
+ - All time bests
317
+ - Last session
318
+ - Previous week
319
+ - Current block
320
+ - Personal best performances
321
+
322
+ ---
323
+
324
+ # Reporting
325
+
326
+ The app should generate:
327
+
328
+ - Session summaries
329
+ - Performance trend reports
330
+ - Asymmetry reports
331
+ - Fatigue reports
332
+ - Development reports
333
+ - Suggestions for improvement
334
+
335
+ Exports are available only through an explicit user action.
336
+
337
+ Supported formats:
338
+
339
+ - CSV
340
+ - JSON
341
+
342
+ ---
343
+
344
+ # Privacy and Offline Requirements
345
+
346
+ The application must be completely offline.
347
+
348
+ Requirements:
349
+
350
+ - No internet connection required
351
+ - No cloud services
352
+ - No user accounts
353
+ - No telemetry
354
+ - No analytics SDKs
355
+ - No remote processing
356
+ - No automatic uploads
357
+ - No automatic backups
358
+ - No external APIs
359
+
360
+ All videos, metrics, reports, and athlete data remain stored locally on the Android device.
361
+
362
+ ---
363
+
364
+ # Core Product Rules
365
+
366
+ 1. Android application only.
367
+ 2. Completely offline operation.
368
+ 3. Athlete data never leaves the device unless explicitly exported.
369
+ 4. Every unilateral metric must be tracked left vs right.
370
+ 5. Invalid measurements must be blocked rather than estimated.
371
+ 6. Historical trends are more important than single-session results.
372
+ 7. Coaching recommendations must be based on the athlete's own data and development history.
373
+ 8. The app exists to support long-term athlete development, performance improvement, and injury-risk reduction.
374
+ # Intelligence Layer
375
+
376
+ The value of IRA7 BIOMECH is not in collecting biomechanical data. The value is in transforming complex biomechanical information into simple, useful, and actionable insights that any coach, parent, or player can understand.
377
+
378
+ Most users are not biomechanists, sports scientists, or data analysts. They should never need to interpret raw angles, force curves, stiffness values, or time-series charts to understand what is happening.
379
+
380
+ The application should function as a personal biomechanical intelligence system.
381
+
382
+ Its responsibility is to:
383
+
384
+ - Collect data. Camera + Computer Vision
385
+ - Analyze data.
386
+ - Identify patterns.
387
+ - Detect trends.
388
+ - Explain findings in plain language.
389
+ - Recommend practical actions.
390
+
391
+ The system should answer questions such as:
392
+
393
+ - What improved?
394
+ - What declined?
395
+ - What should we focus on next?
396
+ - Is the athlete showing fatigue?
397
+ - Is injury risk increasing?
398
+ - Is the athlete developing as expected?
399
+ - Which qualities are progressing fastest?
400
+ - Which qualities are stagnating?
401
+
402
+ The objective is that an inexperienced coach or player can open the app and immediately understand the athlete's current situation without needing any biomechanics knowledge.
403
+
404
+ ---
405
+
406
+ # Athlete Knowledge Engine
407
+
408
+ The application should continuously build an understanding of the athlete by combining:
409
+
410
+ - Athlete profile information
411
+ - Body measurements
412
+ - Growth data
413
+ - Historical training sessions
414
+ - Sprint tests
415
+ - Jump tests
416
+ - Deceleration tests
417
+ - Change-of-direction tests
418
+ - Match data
419
+ - Previous coaching observations
420
+ - Injury history
421
+ - Recovery trends
422
+ - Left-versus-right asymmetry trends
423
+
424
+ The more data collected over time, the more personalized and accurate the recommendations become.
425
+
426
+ The athlete should never be compared primarily against generic population averages.
427
+
428
+ The system should prioritize:
429
+
430
+ 1. The athlete's own historical performance.
431
+ 2. The athlete's growth and development trajectory.
432
+ 3. The athlete's position-specific demands.
433
+ 4. The athlete's movement tendencies.
434
+ 5. The athlete's current physical state.
435
+
436
+ ---
437
+
438
+ # Device Data Integration
439
+
440
+ The application should be capable of using data available on the Android device, with the coach's permission, to improve contextual understanding and athlete monitoring.
441
+
442
+ Potential data sources include:
443
+
444
+ - Captured videos
445
+ - Photos
446
+ - Training recordings
447
+ - Wearable-device exports
448
+ - Health-related files
449
+ - Session notes
450
+ - Exported GPS files
451
+ - Performance spreadsheets
452
+ - Previous reports stored on the device
453
+
454
+ All accessed data must remain local to the device.
455
+
456
+ No data may be uploaded, transmitted, shared, or processed externally.
457
+
458
+ Any access to files or device data must be transparent and explicitly authorized by the user.
459
+
460
+ ---
461
+
462
+ # Coach-Friendly Outputs
463
+
464
+ Every analysis should ultimately be translated into:
465
+
466
+ ### What Happened
467
+ A plain-language summary of performance.
468
+
469
+ ### Why It Happened
470
+ The most likely biomechanical explanation.
471
+
472
+ ### Risk Assessment
473
+ Potential injury-risk or fatigue indicators.
474
+
475
+ ### Recommended Actions
476
+ Specific training recommendations.
477
+
478
+ ### Long-Term Trend
479
+ How the result compares to previous weeks, months, and seasons.
480
+
481
+ The coach should spend most of their time reading insights and recommendations, not interpreting raw numbers.
482
+
483
+ Raw biomechanics exist to support the coaching decisions, not to become the coaching experience itself.