Coaching Without Prompts
Coaching as a
Cognitive Craft
Coaching Without Prompts
Apply for the Pilot →The book is on the runway.
Release date and pre-order details land here as soon as they're locked. Check back for new field notes, video drops, and pilot windows opening.
Cognitive coaching, written down.
Field notes on the work underneath the work — what coaches see, remember, and decide when no one's watching. Pieces from both authors on trainer intelligence, the craft, and what it means to coach without prompts.
A Year of Training, Held.
The sixteen-prompt continuity-extraction methodology behind the forthcoming article. Built against the TIOS Master CDB v3.14 — the Client Layer blocks, the Cognitive Reasoning Layer, the cognitive_thread_map_engine. The recipe Cisco runs in James's thread to pull a year of training into one stitched account.
Read full piece →
In our own voice.
Personality, perspective, and practice on camera. Coaching moments, framework breakdowns, and the kind of unscripted thinking that doesn't fit on a page.
Put your hand up.
A collaborative test of coaching support that runs in the work, not outside of it.
Trainer Intelligence is a conversational system that runs alongside you during a session, captures what you voice, holds continuity across sessions, and supports your thinking in the rhythms where the work actually happens. It does not generate workouts on demand. It does not grade your clients. It does not replace your judgment.
Cisco has been using it inside his own practice for more than a year. The pilot is the invitation to bring it into yours — and to tell us, honestly, what it does and does not do for you.
— Spaces are limited. We'll be in touch within a week.
The pilot, in full.
The complete description of the 2026 collaborative pilot. What you'd be testing, what's expected of you, what we provide, the practical setup, the first month and beyond, what we are listening for, and what this pilot is not.
Read full piece →
It is not a contract.
The letter of intent for the 2026 pilot. A written record of mutual understanding between trainer and project team — what each side agrees to, data and feedback handling, term and exit, safety and judgment, confidentiality. Honest, light, two pages.
Read full piece →
Order the book.
Coaching as a Cognitive Craft
Coaching Without Prompts. By James Semenak and Francisco "Cisco" Martinez Jr. The book lays the foundation for Trainer Intelligence — the four moves of the craft (Observe · Remember · Decide · Support), the standard, and the practice of holding a coach's reasoning across years instead of sessions.
Release date and order link land here when the book ships. Pre-order list opens through the Pilot form above.
Get on the list →This book has two authors, and we came to it from opposite ends of the same problem.
Cisco has been a personal trainer for more than two decades. Most of the work he does is invisible, including to him. It is not the exercises, the programs, or the progress photos. It is the layer underneath: continuous judgment, noticing a small change in how a body moves or how a person shows up, deciding when to push and when to hold, remembering what mattered weeks ago.
James came at the same question from somewhere else entirely. His career was spent in enterprise architecture, designing large-scale systems for senior executives and the organizations that depend on them. For most of a decade he also trained with Cisco — and watched, up close, the cognitive pattern he had spent his career studying everywhere else.
That recognition, reached from two directions, is why Trainer Intelligence exists.
The four moves of the craft.
Trainer Intelligence is built around four things every good coach already does — and supports the trainer in doing them across years, not just sessions.
See what others miss.
Carry continuity forward.
Make the right call.
Carry the work forward.
"The best coaches don't react. They observe, remember, decide, and support."
Intelligence is the advantage. Consistency is the standard.
Not features. Boundaries.
Trainer Intelligence is built around three commitments. They are not features. They are the things the tool is built to do — and, just as much, the boundaries it is built to keep.
The trainer carries less.
The effort a trainer spends thinking inside a live session does not vanish when the hour ends. The decision, the observation, the reason behind a cue are held — and brought back when they're needed.
Coherence over volume.
A client stays engaged not because more messages arrive, but because she feels understood. The trainer stays connected through what is remembered, not what is sent.
Restraint.
Trainer Intelligence does not become autonomous. It does not form goals of its own, and it does not replace the trainer's reasoning. It reasons from how a particular trainer thinks — and stays there.
Good. Start anyway.
Continuity Extraction Prompt Set
For Article A4: "A Year of Training, Held" · Sixteen prompts for Cisco to run in James's training thread with Athena · Targeted at TIOS Master CDB v3.14 (Client Layer v3.1, Cognitive Reasoning Layer, Continuity Authority).
How to Use This Document
Cisco runs these prompts in James's client thread on his laptop or tablet. Each prompt produces a structured response from Athena drawing on a year of accumulated continuity. The output goes to James, who uses it as the source material for the article.
This version is built against TIOS Master CDB v3.14, which is the version Cisco is running. The prompts target the actual blocks and repositories in v3.14: the Client Layer v3.1 blocks (continuity_block, client_narrative_block, behavioral_identity_block, recovery_intelligence_block, between_session_pattern_block, anatomical_decision_continuity, personal_activity_stream_pas, coaching_cue_memory_block, goal_trajectory_block, engagement_signal_block, session_context_tag_block) plus the Cognitive Reasoning Layer's reasoning_intent_repository, adaptive_loop_repository, cognitive_thread_repository, life_vector_repository, and the cognitive_thread_map_engine.
Run them in order. The early prompts re-ground the thread on what is actually loaded so the later prompts have a stable baseline. The final prompt asks Athena to stitch the year into one continuous account that James can edit into prose.
Each prompt is written the way Cisco actually talks to Athena: voice-driven, direct, in his register. He can speak them into the mobile app or paste them on the laptop. The pulls and use-for notes are for the team's reference, not for Athena.
Phase 1. Re-Grounding
Two prompts that confirm what is actually loaded for James before any extraction begins.
P1. Confirm state of James's record
"Athena, re-ground on James's client block. Tell me what is loaded. List the blocks that have content for him: continuity_block, client_narrative_block, behavioral_identity_block, recovery_intelligence_block, between_session_pattern_block, anatomical_decision_continuity, personal_activity_stream_pas, coaching_cue_memory_block, goal_trajectory_block, engagement_signal_block, session_context_tag_block. If any block is empty or thin, say so."
Pulls. The population status of each Client Layer v3.1 block for James. Date of last update per block where available.
Use for. James opens the article knowing what was tracked and what was not. The gaps are also part of the story.
P2. High-level walk-through of the client block
"Walk me through James's client block at a high level. One paragraph per block. What each one currently says about him. Not the raw entries, the consolidated view."
Pulls. A summary of each populated block as it stands at year-end.
Use for. The article's structural outline. Each block can become a section or paragraph.
Phase 2. Narrative and Goals
Two prompts that pull the year-shaped narrative and the trajectory of goals across the year.
P3. Pull the client narrative
"Pull James's client_narrative_block. Read it back to me as a narrative of his year. The session_narratives across the year, the trainer_language_markers, the through-line of how I have been describing him in the record. Walk it from January to December."
Pulls. The client_narrative_block contents. Session narratives across the year. Trainer language markers (how Cisco has been describing James in writing).
Use for. The article's narrative spine. The narrative block is closest to the story of James's year as Cisco has held it.
P4. Goal trajectory across the year
"Pull James's goal_trajectory_block. Where his goals stood at the start of the year. Where they evolved. Where they shifted. What he is working toward at the end of the year that he was not necessarily working toward at the start."
Pulls. The goal_trajectory_block. Goals at each phase. Trajectory direction. Shifts in framing.
Use for. The article needs a sense of forward motion. Goal trajectory shows what changed in what the year was for.
Phase 3. Activity and the Body
Three prompts that pull the Personal Activity Stream, anatomical decision continuity, and recovery/between-session patterns. These hold what happened outside the session and what showed up in the body during it.
P5. Personal Activity Stream
"Pull everything James has shared from outside the session across the year out of the personal_activity_stream_pas. The runs, the hikes, the sleep mentions, the family events, the work travel. Give it to me by date and by category. PAS Tier 1, Tier 2, Tier 3. Note where any Tier 3 promotion happened."
Pulls. PAS items across twelve months by tier. Tier promotions per the v3.10 PAS rules.
Use for. The article's texture. PAS items are what makes the year specific. Without them, the article is abstract.
P6. Anatomical decision continuity
"Pull the anatomical_decision_continuity for James. Any joints, regions, or body areas that have recurred in his record over the year. The decisions tied to each area, the dates the decisions were made, the trigger sessions that produced them. Include the medical_continuity_block and the perioperative_training_continuity_block if either has anything for him."
Pulls. The anatomical_decision_continuity entries. Linked medical_continuity_block and perioperative_training_continuity_block content where present.
Use for. The article's structural account of the body across the year. What Cisco watched, what he protected, what he progressed.
P7. Recovery and between-session patterns
"Pull the recovery_intelligence_block and the between_session_pattern_block for James. What recovery patterns have surfaced across the year. What patterns have shown up between sessions that affected sessions. Sleep, soreness, readiness, life load."
Pulls. Recovery patterns from recovery_intelligence_block. Between-session patterns from between_session_pattern_block. Patterns that crossed promotion thresholds.
Use for. The article's account of how the work between sessions shaped the work in sessions.
Phase 4. Rules, Cues, Decisions
Three prompts that pull what governs James's training, what has been said to him, and the reasoning behind the calls.
P8. Continuity block and session reasoning summary
"Pull the continuity_block for James, with the session_reasoning_summary. The current state. The fatigue_trend, the readiness_trend, the movement_trend, the muscle_group_utilization. Then walk me through the session_reasoning_summary across the year. What I have been reasoning about him."
Pulls. The continuity_block at year-end plus the session_reasoning_summary aggregated across the year.
Use for. The article's account of the structural reasoning that governs James's training.
P9. Coaching cues memory
"Pull the coaching_cue_memory_block for James. The cues that have landed across the year. The cues he has quoted back to me. The cues that were retired because they were no longer needed. By date if you can."
Pulls. The coaching_cue_memory_block. Active cues, retired cues, cues client has quoted back.
Use for. The article's account of language across the year. Cues are the trainer's voice on the client's tongue.
P10. Behavioral identity and engagement
"Pull the behavioral_identity_block and the engagement_signal_block for James. How he shows up. How that has shifted. What signals I have been reading. Where his engagement has been strong, where it has wavered, where it has returned."
Pulls. The behavioral_identity_block (how James shows up across sessions). The engagement_signal_block (engagement signals and shifts).
Use for. The article's account of who James is as a client and how that has changed. The relational arc.
Phase 5. Reasoning Structures
Two prompts that pull from the Cognitive Reasoning Layer. These are the structures that organize Cisco's reasoning about James across the year.
P11. Reasoning intents, adaptive loops, cognitive threads, life vectors
"Pull the Cognitive Reasoning Layer structures for James. The reasoning_intents I have been operating from. The adaptive_loops that have formed. The cognitive_threads that have consolidated. The life_vectors that have emerged. Each one, when it formed, what evidence supports it."
Pulls. reasoning_intent_repository entries for James. adaptive_loop_repository (each loop with cycle and evidence). cognitive_thread_repository (each thread with consolidation date). life_vector_repository (each vector with direction).
Use for. The article's structural payoff. These are the reasoning structures the architecture chapters of the book describe. The article shows one or two of each, with the evidence behind them.
P12. Cognitive thread map
"Run the cognitive_thread_map_engine on James. Show me how the threads, loops, and vectors connect. Where one fed another. Where reasoning intent ri_001 produced loop_001 produced thread_001. The lineage of how my reasoning about James has built up across the year."
Pulls. The cognitive_thread_map output. Lineage from reasoning_intent to adaptive_loop to cognitive_thread to life_vector. The structure map of accumulated reasoning.
Use for. The article's account of how the year's reasoning fits together. Not just discrete threads. The connective structure of Cisco's reasoning about James.
Phase 6. Scenes and Language
Two prompts that surface specific moments and the client's own words.
P13. Significant session observations
"Surface the most significant session observations from the year for James out of the session_reports.session_narratives. The moments worth carrying into a written account. The half-second hesitations, the breath cues that landed, the rep that told us something we did not yet know. Give me ten to fifteen with dates."
Pulls. Session observations from session_reports.session_narratives filtered for significance. Date-stamped.
Use for. The article's scenes. James writes from these specific moments rather than from abstractions.
P14. James's own language
"Pull what James has said about his own work in sessions across the year. His own language about his training. The things he said about how he felt, what he noticed, what he was working on. Verbatim where you have it. Look in client_narrative_block and session_reports.session_narratives for trainer_language_markers, and any direct client quotations."
Pulls. trainer_language_markers and verbatim client quotations from client_narrative_block and session narratives.
Use for. The article gains its texture from James's own words being in it. Hearing himself across a year is one of the article's emotional turns.
Phase 7. Synthesis
Two prompts. The first asks for the structural view of the year. The second asks Athena to stitch it all together as one continuous account.
P15. Session context tags and engagement signals across the year
"Pull the session_context_tag_block entries across the year for James, with the engagement signals in chronological order. What kind of session each one was. Where the texture of the year shifted. Where streaks of similar tagging show up."
Pulls. session_context_tag_block entries across the year. Aggregated engagement signals chronologically.
Use for. The article's structural overview. The shape of the year as a sequence of session contexts. Useful for identifying chapter breaks if the article structures around them.
P16. Stitch the year together
"Now stitch it together. Give me James's year as one continuous account. What he walked in with. What surfaced. What shifted. What is true about him at the end of the year that was not true at the start. Write it as one prose narrative across three thousand words. Use the continuity blocks and the reasoning layer you have just walked through as the source. Quote his own language where you have it. Name the body, the rules, the threads, the goal trajectory, the patterns. Do not invent. If something is not in the record, say so."
Pulls. A composed synthesis drawing on every prior prompt's output.
Use for. James's draft starting point for the article. Not the final article. The raw material organized into prose he can edit, restructure, and rewrite in his own voice.
What to Expect
Athena may surface gaps. Some blocks may be thinner than others. That is useful information for the article. The honest version of the year shows what was tracked and what was not.
Athena's stitched account in P16 is a starting point, not the article. The voice will be Athena's, not James's. James edits the stitched account into his voice, restructures the order if useful, cuts what does not earn its place, expands what does. The article runs through the three-brief audit before publication, same as every other piece in the sequence.
If a block referenced in a prompt is not loaded or not populated for James, Athena will say so. That itself feeds into the article: a year of training that includes structural gaps in the record is more honest than one that does not.
The Trainer Intelligence Pilot
A collaborative test of coaching support that runs in the work, not outside of it. 2026.
This is an invitation to test what a small team has been building for a working trainer's practice, with us beside you as you do it.
Trainer Intelligence is a conversational system that runs alongside the trainer during a session, captures what the trainer voices, holds continuity across sessions, and supports the trainer's thinking in the rhythms where the work actually happens. It does not generate workouts on demand. It does not grade your clients. It does not replace your judgment. It carries the cognitive work alongside you so that what you noticed about a client in week three is still in the room with you in week twelve.
Cisco Martinez has been using it inside his own practice for more than a year. The pilot is an invitation to bring it into your practice and to tell us, honestly, what it does and does not do for you.
What you'd be testing
Not a product launch. The pilot is the version of Trainer Intelligence that works through a custom GPT inside ChatGPT, accessed from your phone or tablet during sessions and from your laptop for setup and reflection. It runs through the existing ChatGPT infrastructure, which means it is voice-driven during a session, conversational rather than form-based, and accessible wherever you train.
What you'd be testing is the experience of having a trainer-aware system in the room with you: how it changes what you carry between sessions, how it changes what you notice during them, how it changes the work of writing up a session or preparing for the next one. Cisco has watched all of this change in his own practice across eighteen months. We want to see what it does in yours.
What's expected of you
Three things, in order.
First, you use it in your sessions. Not all of them, not from day one, and not for every client at once. We will work with you to start with one or two clients you know well, get the system into the rhythm of those sessions, and expand from there. The goal across the pilot year is for you to be using it as part of how you actually work, with a stable handful of clients.
Second, you tell us what you find. Every week we will check in, briefly. What helped, what did not, where it surprised you, where it got in the way. The feedback we are looking for is the trainer's honest read on the experience: where the system landed, where it missed, what you wished it had done differently. We are not looking for polished evaluations. We want the working-trainer read.
Third, you stay in conversation. The pilot is collaborative. We are available one-on-one, by email or by call, on the cadence that works for you. When a session does not go the way you expected, we want to hear it that week. When something works in a way you did not see coming, we want to hear that too.
Time commitment, honestly: a few minutes of setup per new client, no extra time during sessions (the system runs in your existing flow), a few minutes after sessions to confirm what the system captured, and roughly fifteen minutes a week for the check-in. The work is not added to your practice; it runs inside it.
What we provide
Early access to Trainer Intelligence, with the custom GPT installed in your ChatGPT account on your laptop, phone, and tablet.
Direct setup support. The first session can take some configuration. We do it with you, on a call, so the first time you use it in a real session it is already running.
One-on-one help when you need it. The whole pilot is small enough that you can email us with a question and get a real answer that day. If something is not working, we will help you work through it.
Cisco's experience. He has spent the last fourteen months working out how to bring Trainer Intelligence into the rhythm of his sessions, his evening reviews, his programming, and his client communication. He can tell you what worked from inside the practice. If you want to see a session run on his side before yours starts, we can arrange that.
Early access to the book that comes out of this work, before it is generally available. The book is the long-form account of why this kind of tool needs to exist and what restraint as a design property actually looks like. It informs the pilot, and the pilot has informed the book.
Direct input into how Trainer Intelligence develops. The pilot year is when the system gets shaped by the trainers using it. What you say in the weekly check-ins will be in the next version of the system. Some of what you say will end up in the next version of the book.
The practical setup
You will need a ChatGPT Plus account. Trainer Intelligence runs as a custom GPT inside ChatGPT, which requires the Plus tier. The cost is roughly twenty dollars a month and is the only direct cost to participate in the pilot. We recommend a dedicated account for your training practice, separate from any account shared with family or used for personal purposes.
You will need your phone or tablet for live sessions, with ChatGPT installed and signed in. You will use your laptop for the initial setup and for the evening review work.
On the laptop, you save the custom GPT to your account, fill in two short profile templates (one for you as a trainer, one for each client you want to bring into the system), and rename a chat thread per client. On the mobile device, you open the client's thread before the session and start the session formally. From there, the system runs in voice during the session.
Setup time per client, after the initial onboarding, is roughly five to ten minutes. The trainer and client profile templates are short by design. The pilot guide we will send you walks through the mechanics in more detail. Cisco's setup, after fourteen months, takes him under five minutes for a new client.
The first month and beyond
Week one is setup. We get the custom GPT into your account, we walk you through the first session, you run one or two real sessions, and we check in at the end of the week.
Weeks two through four are settling in. You expand to a few more clients, you find the parts of the system that work for you and the parts that do not, and we adjust together. Cisco's first month felt awkward; by the end of it the system was already changing what he carried out of sessions. We expect something similar for you, with the small adjustments your practice needs.
Months two through twelve are the working pilot. By this point the system is part of how you train. The weekly check-ins continue but shorter, and the focus shifts from setup questions to deeper feedback: what the system is and is not doing well across the arc of weeks and months, where it is changing your practice, where it is not. Some of what you tell us becomes the next version of Trainer Intelligence; some of what we learn together becomes shared material on the project's site for other trainers to read.
What we are listening for
Three things, plainly.
What helped. Where in your week did Trainer Intelligence make a real difference? What changed about how you prepared for a session, how you ran a session, how you wrote up a session, or how you communicated with a client between sessions? Specific is more useful than general. A moment where the system did something you noticed is worth a paragraph; an overall sense is worth a sentence.
What did not help. Where did the system get in the way, slow you down, miss what you needed, or produce something that was not useful? What did you stop using because it was not earning its keep in your practice? Be specific and be honest. The pilot is the time to surface what is not working so it can change.
What improvements would matter most. Where, if we worked on it, would the system get meaningfully better for your practice? What feature, behavior, or change would close a real gap? We will not promise to build every suggestion, but the trainers in this pilot will be shaping the next version of the system and we want to know where the leverage is.
What this pilot is not
It is not a product evaluation. We are not asking you to score features or write reviews or compare Trainer Intelligence to other tools.
It is not a marketing program. You will not be asked to provide testimonials, post on social media, or recommend Trainer Intelligence publicly. If you want to talk about it, you are welcome to; if you do not, that is fine.
It is not a sales funnel. There is no commitment beyond the pilot, no contract, no obligation. When the pilot year ends, you decide whether you want to keep using Trainer Intelligence and on what terms. Pricing for ongoing use after the pilot has not been decided; pilot participants will get first say on what that should look like.
It is not a finished system. There will be moments when something does not work the way it should. There will be times when the response is wrong, the recap is off, the suggestion is not useful. That is the work the pilot exists to find. Tell us when it happens; we will fix what we can fix and learn from what we cannot.
What we are still figuring out
Some of this is honest.
The system is built around restraint. It is not supposed to generate programs on demand, grade clients, or speak with authority over the trainer's judgment. We have spent considerable time working out where those boundaries are. The pilot may surface places where the boundaries are too tight (you wanted the system to do something and it would not) or where they are too loose (you wished the system had refused something it did). Both are useful to learn.
The custom GPT delivery method has limits. It runs inside ChatGPT, which means it inherits some of ChatGPT's behavior. Long-term memory across sessions is not native to that environment, which is part of why Trainer Intelligence has its own continuity discipline. Where the discipline does not hold cleanly, we want to know.
Client data is handled by ChatGPT and OpenAI per their policies. We do not have a separate system holding your client information. If you have clients whose data needs handling beyond what the ChatGPT consumer infrastructure provides, the pilot is not the right fit for those clients. We will work with you on which of your clients are appropriate for the pilot.
If this sounds like the right fit
Email us at TrainerIntelligence@outlook.com with a short note about your practice. We want to know roughly how long you have been training, how many clients you currently work with, where you train them, and what made you interested in this project.
We will respond within a week. If the fit looks right, we will set up a short call with you and walk through the setup together.
Spaces in the pilot are limited. We are looking for trainers with experience and judgment, who already do the work the book and the project are about, who have started to feel the weight of carrying both, and who want to see what a tool built differently can do alongside what they already do well.
The pilot is for the work you are already doing, supported in a way no tool has been built to do before. The trainer remains the one in the room. We are just here to help you carry it.
Trainer Intelligence · trainerintelligence.fitness · TrainerIntelligence@outlook.com
Trainer Intelligence Pilot Agreement
A letter of intent for the 2026 collaborative pilot.
This letter captures what we are each agreeing to in the Trainer Intelligence pilot for 2026. It is not a contract. It is a written record of the mutual understanding between the trainer joining the pilot and the project team supporting it. We are putting it in writing so neither side has to wonder, six months in, what we agreed to.
If something here does not match what you understood from our conversations, tell us before you sign. We will work out the language together.
1. What you agree to do as a pilot trainer
• Use Trainer Intelligence in your real sessions across the pilot year. Not every session, not every client at once, but enough that we are learning from your actual practice. We will work out the right pace together at the start.
• Get explicit consent from any client you bring into the system. Tell them an AI assistant is being used in their sessions, what it does, and that they can opt out at any time. We will provide a short note you can adapt if useful.
• Participate in the weekly check-in. About fifteen minutes, by email or by call, whichever fits your week.
• Provide honest feedback. What worked, what did not, what would matter most to improve. Specific and direct is more useful than diplomatic.
• Remain the final decision-maker on every client matter. Trainer Intelligence supports your thinking; it does not replace it. You are responsible for what happens in your sessions.
• Keep system details private during the pilot. Do not share screenshots of the system, technical details about how it works internally, or the specific prompts and behaviors with people outside the pilot. You can talk about the project in general terms with anyone.
2. What we agree to do
• Provide the custom GPT and walk you through the initial setup, on a call, so the system is working before your first real session.
• Respond to your questions within one business day. If something is broken or blocking you mid-session, sooner.
• Make Cisco's experience available to you. He has been using Trainer Intelligence in his own practice for more than fourteen months. If you want to see how a session runs on his side, or work through a specific situation with him, we will set it up.
• Provide early access to the book that comes out of this project, before it is generally available.
• Tell you when we update the system. Trainer Intelligence will change during the pilot year. We will explain what changed and ask you to tell us what changed in your experience.
• Give pilot participants the first say on what continued access looks like after the pilot. Pricing and terms beyond the pilot are not decided. We will figure them out with you, not announce them to you.
3. Data and feedback handling
• Your client data stays in your ChatGPT account. We do not have a separate copy of your client threads or session records. When the pilot ends, your data stays where it is; you can continue using it or delete it as you choose.
• Your feedback in the weekly check-ins shapes the next version of the system. Specific suggestions, problems, and observations may directly drive changes to how Trainer Intelligence works.
• We may quote or reference what pilot trainers experience in published material: articles on the project's site, the book, future versions of either. Before we attach your name to anything you said, we will ask you. You can opt out, anonymize, or review the wording before publication.
• Aggregate, de-identified patterns from across pilot trainers may inform our work without specific attribution. Individual client information will never be shared with third parties.
4. Term and exit
• The pilot runs through 2026. We expect roughly twelve months of working use.
• Either side can end the pilot at any time, for any reason, with no penalty. We would like a brief conversation about why, so we can learn, but it is not a condition of exit.
• On exit, your data stays in your ChatGPT account. You decide whether to keep using Trainer Intelligence on the existing custom GPT, delete what you have, or migrate elsewhere.
• After the pilot ends, continued access depends on terms we work out together. Pilot participants will not be asked to commit to anything beyond the pilot itself.
5. Safety and judgment
• Trainer Intelligence is a support tool. It is not a clinical recommendation engine. It is not a substitute for professional judgment, medical advice, or appropriate scope of practice.
• Trainer Intelligence has safety-class behaviors built in. It will refuse to recommend certain actions that cross hard lines (acute medical contraindications, active perioperative restrictions, client-identity mismatches, certain acute symptoms). You should understand these behaviors. We will walk through them at setup.
• If Trainer Intelligence's response is wrong for the situation in front of you, your judgment overrides. If you are not sure, stop the session. Tell us afterward.
• You remain responsible for all client decisions, including how you respond to anything Trainer Intelligence surfaces or suggests.
6. Confidentiality
• This is light. There is no non-disclosure agreement attached to this pilot.
• We ask that you keep system details private during the pilot, as described in Section 1. You can talk about the project in general terms, mention that you are part of a pilot, and share that Trainer Intelligence exists.
• We will keep your participation private by default. We will not name you, your practice, or your clients in any public material without asking you first.
7. Acknowledgment
Signing below means you have read this, understood it, and agreed to the terms in plain language. It also means we, on our side, have agreed to the same.
This is a working agreement between people doing collaborative work, not a legal contract enforceable in any specific way. We are putting it in writing because that is how serious work between adults gets done.
Signatures
Pilot trainer:
Name: ____________________________________________________________
Practice: __________________________________________________________
Signature: ___________________________ Date: ___________________
Project team:
James Semenak
Signature: ___________________________ Date: ___________________
Francisco "Cisco" Martinez Jr.
Signature: ___________________________ Date: ___________________
Trainer Intelligence · trainerintelligence.fitness · TrainerIntelligence@outlook.com
Put your hand up.
If you are a trainer who has been wanting to see what something built like this would actually feel like inside a practice, the door is open in early form.
The pilot is for trainers who already have the experience and the judgment, and who have started to notice that the cognitive work of the craft has grown faster than the tools meant to support it.
— Spaces are limited. We'll be in touch within a week.