CONNECTED HEALTH INFRASTRUCTURE / FITNESS + PERFORMANCE PRODUCTS

Health context
your product can govern.

Knownset carries consented device data through deterministic analysis, bounded coaching, and person-confirmed action—inside the product and programming your team already owns.

Inspect the working sample Compare the build choices

FOR / PRODUCT + ENGINEERING TEAMSEVIDENCE / SYNTHETIC WORKING SAMPLEBOUNDARY / YOUR PRODUCT OWNS THE ACTION

01 / SEE IT IN A PRODUCT

Every capability.
From a natural request to a controlled result.

Choose a capability. Watch a natural request type, see Northstar respond, then review the exact product state before anything changes.

16 CAPABILITY DEMOS

CAPABILITIES01 / 16

CAPABILITY

01 / 16

01 / 06 · Typing

All 16 capability examples

Adapt the workout

Movement swapA before-and-after card names the movement while preserving the requested dose.
Load suggestionA benchmark-grounded load appears with the synthetic basis used to produce it.
Sets + reps scalingThe exact set-and-rep difference appears without changing the rest of the session.
Intensity changeThe percentage prescription becomes a visible RPE diff while sets and reps remain fixed.
Block compositionAdded and removed blocks are listed separately before the workout changes.
Coach noteThe exact note and its destination appear on the proposal card.

Remember the athlete

Categorized memoryA confirmation card files the note under one of 12 defined memory categories.
Fresh-chat recallA new conversation retrieves the relevant confirmed note instead of relying on chat history.
Movement correctionThe new movement-specific record supersedes the stale value for that movement and date.

Record real training

Benchmark recordingMovement, load, unit, date, and benchmark type appear for review.
External workoutDuration, effort, location, and session summary become an editable logging card.
Block + session completionAn editable checklist distinguishes completed, skipped, and untouched blocks.
Program repositioningThe current and requested program positions appear side by side with the reason.
Photo intakeExtracted movements, doses, and notes appear as a draft rather than a silent write.

Protect every action

Pending-card recoveryThe same pending proposal and its before-and-after state return after restart.
Safe retryThe app shows one final state and one action receipt.

02 / THE BUYING PROBLEM

The hard part starts
after the connection.

A source connection gives your product data. It does not decide what is current, what can be compared, which calculation is authoritative, what a coach may say, or who can apply a change.

WHAT THE PIPE DOES NOT OWN

01
Source operations
Permissions, changing schemas, units, dates, provenance, and freshness.
02
Fact integrity
Deterministic calculations, missing-data handling, limitations, and evidence.
03
Coaching policy
Approved purposes, language boundaries, escalation, and reversible suggestions.
04
Action governance
Programming ownership, member review, confirmation, audit, and rollback.

03 / THE KNOWNSET BOUNDARY

One controlled path.
Four explicit owners.

The target architecture keeps source truth, calculated fact, interpretation, and action separate. The current sample demonstrates this pattern with made-up data.

01
Source + permission
Approved context
Only context approved for this person and product enters the request, with provenance and freshness available to inspect.
02
Knownset engine
Deterministic fact
Code—not model prose—owns normalized values, calculations, and known limitations.
03
Approved purpose
Bounded interpretation
A coaching layer can explain supplied facts inside a defined purpose without becoming the source of record.
04
Customer + person
Confirmed action
The customer keeps programming and the member-facing review before a meaningful change is applied.

Design rule

A language model may explain a checked fact. It does not silently become the calculator, identity provider, permission service, or final writer.

Inspect the trust boundary

04 / BUY OR BUILD

Choose the responsibility
you actually want to own.

Knownset is not the right choice for every team. It is for teams that want the member experience and programming to remain theirs without building the full context-to-action stack.

Build internally

You gain: Maximum product control
You still own: Own every connector, normalization rule, freshness check, model gate, approval flow, and source change.

Aggregator + internal logic

You gain: Faster source access
You still own: Still own the meaning, evidence contract, decision logic, coaching boundary, and action workflow.

General-purpose model

You gain: Flexible language
You still own: Still need a deterministic source of fact, permission boundary, evidence, and safe path to action.

Standalone coaching app

You gain: A finished experience
You still own: Move the member relationship and programming outside the product your team already owns.

Knownset

You keep: Your product, programming, workflow, and member relationship.
Knownset owns: The infrastructure between consented source context and a governed action boundary.

05 / RESPONSIBILITY, NOT MAGIC

Your product stays
the owner.

Knownset is designed to fit behind a customer experience, not replace it. Each participant keeps a visible, reviewable role.

01Knownset owns

Source-context operations
Deterministic analysis
Evidence-bearing outputs
Bounded coaching infrastructure

02Your product owns

Member experience
Programming policy
Product-specific permissions
Confirmation and final write

03The person owns

Source approval
Visible context
Review of proposed changes
Final decision

06 / START WITH EVIDENCE

Inspect the sample.
Keep the claims narrow.

The current developer sample is local, private-preview, read only, and synthetic. Hosted access, production connector coverage, certifications, customer outcomes, and public pricing are not represented as available.

Open developer evidence Review evidence and non-claims

Health contextyour product can govern.

The hard part startsafter the connection.

One controlled path.Four explicit owners.

Approved context

Deterministic fact

Bounded interpretation

Confirmed action

Choose the responsibilityyou actually want to own.