HOW TO USE THE FORGE

Generic flow — direct cloud OAuth (Garmin, Oura, Fitbit, Eight Sleep, Suunto, Withings, Whoop)

1. Open SENTINEL FORGE on phone, web, or desktop.
2. Tap Settings (gear icon, top-right).
3. Go to Integrations.
4. Find your sensor in the Available list and tap Connect.
5. You’ll be redirected to your sensor’s official login page.
6. Sign in with your sensor-cloud credentials.
7. Authorize SENTINEL FORGE to access your data.
8. Return to the app — connection confirmed. Initial sync pulls your historical data (window varies by sensor — typically 30 days to 2 years; Garmin is forward-only from the day you connect).

Apple Health (iOS) & Health Connect (Android) — federated flow

Why this matters: If you own an Apple Watch, COROS, Polar, Ultrahuman, or Samsung wearable, SENTINEL FORGE reads your data through your phone’s health platform rather than a direct cloud connection. You authorize once in Apple Health / Health Connect, and SENTINEL FORGE pulls the data categories you switch on — workouts, heart rate, sleep, HRV, body composition, and more.

Step 1 — make sure your wearable syncs to your phone’s health platform

This happens in the wearable’s own app (COROS, Polar Flow, Samsung Health, etc.), not in SENTINEL FORGE.

1. iOS: Open your wearable’s app → Settings (or More / Profile) → Connected Apps / Partner Apps → Apple Health → tap Authorize and turn ON every data category you want SENTINEL FORGE to see (workouts, heart rate, resting heart rate, HRV, blood oxygen, respiratory rate, sleep, distance, calories, weight, body fat).
2. Android: Open your wearable’s app → Settings → Health Connect → allow the wearable’s own app to read & write each category (that is how it deposits your data into Health Connect). SENTINEL FORGE itself never writes to Health Connect — in Step 2 it asks for read-only access. On Android 14+ Health Connect is built into the OS; on older devices, install the Health Connect app from the Play Store first.
3. Verify: in Apple Health → Profile → Apps and Services, or Health Connect → Connected apps, you should see your wearable listed as a source.

Step 2 — connect SENTINEL FORGE to the health platform

1. Open SENTINEL FORGE on your phone (the native iOS or Android app — this flow does not work in the web app).
2. Tap Settings → Integrations.
3. Tap Apple Health (iOS) or Health Connect (Android).
4. Tap Connect — the OS pops up a permission sheet listing every data type SENTINEL FORGE wants to read.
5. Grant the permissions (Allow All, or pick categories — you can change this later in your phone’s Apple Health / Health Connect settings without touching SENTINEL FORGE).
6. Initial sync starts immediately — first visible results within ~5 minutes, and subsequent syncs are incremental (seconds). iOS (Apple Health): up to 2 years (730 days) of history backfills in the background. Android (Health Connect): Health Connect exposes only the most recent 30 days to apps, so the initial backfill covers roughly the last month — see the Android caveat below for how to pull your full history.

Garmin — use the direct connection, not the health platform

SENTINEL FORGE connects to Garmin directly, through Garmin’s own Health API. That path pulls activities, HR zones, sleep, stress, respiration, and recovery (Body Battery) straight from Garmin — it does not depend on Apple Health or Health Connect.

It is live for every account. Garmin has approved SENTINEL FORGE for its production environment (Activity, Health, and Women’s Health APIs).

1. In SENTINEL FORGE, open Settings → INTEGRATIONS → ADD INTEGRATION → WATCH → GARMIN and tap CONNECT.
2. Sign in to Garmin Connect and approve the read-only permissions. You land back in SENTINEL FORGE with Garmin showing as connected.
3. Sync your watch. Open the Garmin Connect app on your phone and let it sync with your watch. Garmin only sends data when the watch uploads, so nothing appears until the first sync after you connect — from then on, every sync reaches SENTINEL FORGE on its own, usually within a minute.
4. There is no SYNC button for Garmin inside SENTINEL FORGE — there is nothing to request. If your data looks behind, sync in Garmin Connect; it pulls from the watch, and that reaches us right after.

Garmin’s API is forward-only: it sends what your watch records after you connect and does not backfill history that already exists in Garmin Connect.

If you route Garmin through Apple Health, it is forward-only. Garmin’s own Apple Health integration pushes new activities from the day you enable it forward and does not backfill history that already exists in Garmin Connect. The same applies to most cloud-only wearables reaching SENTINEL FORGE through Apple Health. (Suunto is the exception — SENTINEL FORGE pulls Suunto history directly from the Suunto Cloud API, see the next card.)

Historical data caveat — Health Connect (Android)

Health Connect exposes only the most recent 30 days to SENTINEL FORGE. This is a Health Connect platform limit, not a SENTINEL FORGE setting — Android caps third-party apps to a rolling 30-day read window unless they hold a special extended-history permission, which SENTINEL FORGE intentionally does not request (it would push our data footprint past Google Play’s minimum-scope policy). So on Android you’ll see roughly the last month of history, then everything new from that point forward.

No third-party import tool gets around this, because the Android limit is on the read side. Pushing more history into Health Connect with a tool like Health Sync still would not make it visible to SENTINEL FORGE, which is capped at reading the last 30 days regardless of how much Health Connect stores. Use a direct integration instead where the manufacturer offers one.

To get your full history on Android, connect the wearable directly via its cloud instead of (or alongside) Health Connect — the direct integrations pull years of history straight from the manufacturer and aren’t subject to the 30-day window. Oura, Fitbit, Eight Sleep, Suunto, Withings, Whoop, and Garmin are live today (Garmin’s own API is forward-only from the day you connect — see the Garmin card above); COROS, Polar, and Sleep Number are on the direct-API roadmap. Health Connect stays the best catch-all for everything without a direct integration (Samsung Health, Ultrahuman, and the like), within its 30-day window.

Disconnect a sensor

Settings → Integrations → tap the sensor → Disconnect. Existing synced data stays in your account; future syncs stop.

Manual entry — required for any campaign workflow

1. Open the Today view to see your planned mission for the day.
2. Complete the workout.
3. Tap Log Mission — confirm or override the planned values (sets, reps, weight, RPE, distance, intensity zones).
4. The Reconciliation Engine matches your sensor data against the campaign plan, enriches the workout metadata (campaign tier, block, week-in-program, mission-vs-actual delta, intensity-zone alignment), and feeds the enriched record into TALOS.
5. TALOS scores update within minutes — Training Load gets the correct campaign-volume credit, Recovery accounts for the planned strain, Fuel recalibrates against the day’s actual demand.

Without manual entry, sensor-only workouts still log and contribute to raw load — but TALOS loses the campaign context it needs for proper progression tracking, ACWR scoring, and Fuel macros that match the day’s mission. You’ll see the strain, not the picture.

Voice log during the workout

Tap the mic on the Workout screen and speak the set naturally (“3 by 10 squats at 225, RPE 8”). Voice entries count as manual logging and reconcile against the campaign the same way.

Auto-sync — for workouts outside an active campaign

Ad-hoc trail run, casual lift, weekend ruck without a campaign assignment: auto-sync from your Suunto / Whoop / Fitbit captures everything. TALOS uses the workout for raw load calculation but skips the campaign reconciliation step (no campaign mission to reconcile against).

Input methods

• Nutrition Lookup — search the food database, pick servings.
• AI Photo Estimate — snap a meal photo, AI estimates the macros (uses your Nutrition Lookup quota).
• Voice / Text Description — describe the meal in plain language (“two eggs, oatmeal with peanut butter, banana”); AI parses the macros.
• Manual Macro Entry — drop protein / carbs / fat directly when you know the numbers.

The Log action — required to feed TALOS

1. After any input method above, you’ll land on the Create Meal screen with the macro breakdown pre-filled.
2. Confirm or adjust serving sizes / macros.
3. Tap Log.
4. The meal commits to your daily intake. The Fuel pillar of TALOS recalibrates within seconds against your training-load-adjusted macro targets.

Input methods

• Withings smart scale — connect via the standard sensor flow (see Section 01); weight + body fat readings auto-populate the Log Body screen.
• Body Composition AI Scan — upload a body photo for an AI-estimated body fat % (uses the Body Composition AI Scan quota).
• Manual entry — log weight, caliper measurements, or DEXA results directly.

The Log action — required to feed TALOS

1. After any input method, you’ll see the Log Body screen with the values pre-filled.
2. Confirm or adjust.
3. Tap Log.
4. The reading commits to your body-comp trend. TALOS Health metrics update within seconds.

The four pillars

• Training Load — 7-day vs. 28-day acute-chronic ratio (ACWR). Catches overtraining and undertraining.
• Recovery — HRV + sleep + active recovery, scored against your baseline.
• Fuel — macro adherence vs. your training-load-adjusted daily targets.
• Stress — reported stress + HRV correlation, with actionable recovery tactics.

How to read it

• The composite score updates after every workout, meal, sleep cycle, or check-in.
• Tap any pillar for the deep-dive view (trend, contributing inputs, today’s recommendation).
• The composite informs your Overview tab recommendations — training intensity, fueling, recovery focus.

Browse and enroll

1. Open the Campaigns tab.
2. Filter by tier (Foundation / Vanguard / Sentinel) or category.
3. Tap a campaign for the structure overview.
4. Hit Enroll. Daily missions appear on your Overview tab immediately.

Campaign reactions

After each mission, mark how it went — too easy / too hard / just right / missed. The campaign engine adjusts subsequent missions in-block to match your actual response, keeping the program adaptive instead of static.

Personal Campaign Import

Have a coach-built plan? Campaigns → Personal Campaign Import → upload (uses your tier’s import quota). The Reconciliation Engine handles imported plans the same way as native campaigns — you still tap Log Mission after each session.

AI-Generated Campaign

Tell the AI your goal (“selection prep, 12 weeks, 16 hours/week available”) and it builds a custom periodized campaign tailored to your training-history baseline. Reconciliation works the same way as any other campaign type.

Start a challenge

1. Open the Compete tab.
2. Tap New Challenge.
3. Pick an opponent (callsign search) or set it as open-invite.
4. Pick the metric and duration.
5. Send the challenge. The leaderboard tracks both operators in real time.

Concurrent challenge cap

Each operator can run up to 1 campaign challenge + 3 non-campaign challenges at once (4 total). Keeps the leaderboard meaningful and prevents burnout from over-stacking.

Find your squad

• Friend connections — search by callsign and send a connect request.
• Group chats — per channel (squad, campaign cohort, challenge group).
• Public PR shoutouts — PRs you log appear on the leaderboard for visibility.