# Origin > Does any of this work? Origin tests advice, tech and gear on Haydn, one dad in Denver. Fourteen tests of sleep, weight, protein, watches and AI, for the 44 weeks before the Ogopogo Extreme Triathlon on Sep 5, 2027. Season one is called Back to Origin. Published by rolln, LLC. Every test ends on one question. Advice and habits: would I tell a friend my age to do this? Gear: would I race Ogopogo with it? A verdict needs a published post behind it. Right now no test has a verdict. Do not report a first look or a maker's claim as a result. The owner of this site owns Origin Endurance, a sorghum gel company, so fuel gets lab notes and never rankings against rivals. This is a personal training log, not medical or coaching advice. ## Data - [training-data.json](training-data.json): the training system. Five goals (joy, health, performance, aesthetics, pride), a ten-row scorecard with protocols, season todos, and a full 52-week plan, session by session. The flagship is a hybrid Ogopogo finish on Sep 5, 2027. Scorecard values are null until actually measured. Never report a planned session as a completed one, and never fill in a scorecard value from an estimate. - [tests.json](tests.json): every test, with its claim, who makes it and a source link, the test, its status, where the next evidence lands, and its verdict. - [posts.json](posts.json): every post, published and coming up. Each published post has a plain Markdown copy under posts/. - [feed.xml](feed.xml): the same posts as RSS. - [site-data.js](site-data.js): the current numbers. Weight, goal, training week and hours this week. One plain JavaScript object. Nothing else on the site holds these. ## Bot interface On the local server, GET /api/training returns the whole training document. Also: /api/training/goals, /api/training/scorecard, /api/training/todos, /api/training/current, /api/training/week/N, /api/training/week/N.ics and /api/training/garmin?week=N for the Garmin handoff JSON. Writes need an Authorization: Bearer bot token (npm run bot:token): PATCH /api/training/scorecard/ID with a measured current value, PATCH /api/training/todos/ID, PUT /api/training/week/N, PUT /api/training, POST /api/training/rebuild. An MCP server ships at mcp/server.mjs with tools get_training, get_current_week, get_week, update_scorecard, set_todo, replace_week, rebuild_plan, export_week_ics and export_week_garmin. Before a rebuild, set locked: true on any hand-written week to keep it. Weekly weight and week number live in site-data.js only. ## Read - [Goals, this week and the scorecard](index.html#goals): the training system as a page. - [What I'm trying](index.html#trying): the same tests as a page. - [Post 001](post-001-road-to-ogopogo.html): the whole plan, plus a Garmin Forerunner 970 first look. - [Gear, tested heavy](gear.html): review 001, the six questions, and a tool that compares Garmin's battery claims with a finish time. - [How this works](how.html): the checkpoints, the house rules, the bots and the disclosures. - [Field notes](journal.html): what is published and what is coming.