Glaucus

Build the robot. Keep the receipts.

Glaucus turns your team’s chat into an engineering notebook. It only writes what you actually did, and a teammate signs off on every page.

FIRST® Tech Challenge

  1. 01 Build season

    The drivetrain gets rebuilt. Again.

    Someone swaps the wheels at 9 p.m. and the robot finally drives straight. Nobody writes down why.

  2. 02 The group chat

    The only record is a photo and “fixed it”.

    Fine. Keep talking the way you do. Glaucus picks up the messages, photos, and numbers as they come in.

  3. 03 The notebook

    It writes the page you skipped.

    Goals, what you did, what broke, what you decided, what the test said. If a number is missing it says [needs input], it never guesses.

  4. 04 The to-do loop

    Turn chat into a plan, then close the loop.

    Tell Glaucus what needs doing in Discord and confirm with a button. Link tasks to a draft, and when a teammate approves the page, finished tasks tick off in the record.

  5. 05 Judging

    “So why did you switch wheels?”

    You open the note from that night: what broke, what you tested, what you chose, what got finished, and the teammate who signed off. Then you export it into your portfolio.

The rule

Chat moves fast. The notebook falls behind. Glaucus writes the page from what your team said, marks what’s missing as [needs input], and waits for a teammate to sign off.

Features

One system for the notebook and the to-do list, built around what your team actually did.

#01 Capture

Notes from Discord & web

Start a session, mention Glaucus in chat, or type and paste photos from a laptop in the shop. Every source builds the same draft.

#02 Structure

One format, zero guessing

Goals, work done, problems, decisions, test results, and next steps. Missing numbers get flagged as [needs input] for you to fill in.

#03 Review

Teammate sign-off

Nobody approves their own note. A second teammate checks every page, sends it back if something is missing, and signs off before it locks.

#04 Plan

To-dos in one sentence

Tell Glaucus what needs doing in Discord and confirm with a button. Track owners, due dates, priorities, and subsystems in one team plan.

#05 Close the loop

Linked to the notebook

Attach open to-dos to a note while you work. When the note is approved, finished tasks tick off and stay frozen in that page’s record.

#06 Remind

Owner-only reminders

Overdue and due-this-week tasks ping only the people assigned, with a Mark done button right in Discord so the channel stays quiet.

Also at launch

Search and export
Find any approved note across the season. Export Markdown or a zip with photos when the portfolio is due.
Any language in
Write in whatever language your team speaks. Every notebook page comes out in clean English.

Coming later

Slack
Capture notes from your Slack workspace.
WhatsApp
Send updates and photos from the team group chat.
More chat apps
Wherever else your team already talks.
Ask about your to-dos
“What’s on my plate?” in the chat, and “done” to close one out.

Where this goes

Robotics teams first. Then every team that builds things.

We start with robotics teams because their notebook gets judged. The same gap shows up anywhere people build: decisions get made in chat, and by the next design review nobody remembers why.

  • Student robotics teamsNow
  • University engineering teamsNext
  • Hardware startupsNext
  • Research labsNext

FAQs

How Glaucus works in practice

Does Glaucus ever invent test numbers or design decisions?

No. Glaucus only writes from the messages, photos, and notes your team actually sent. Whenever a measurement, rationale, or test figure is missing, it leaves a [needs input] marker for a teammate to fill in before approval.

Can someone approve their own engineering notebook page?

No. Glaucus enforces two-person sign-off on every page. Once a draft is submitted, a different teammate has to review it, return it with a reason if something is missing, or approve it so it locks into the archive.

How do team to-dos stay connected to the notebook?

Create to-dos in one sentence in Discord (confirmed with a button) or on the web plan, with owners, due dates, priorities, and subsystems. Attach open to-dos to any draft: when a teammate approves the page, finished tasks tick off and freeze into that note’s Planned tasks record.

Will reminder pings spam our entire Discord channel?

No. Reminders arrive as one message. Overdue tasks and tasks due this week ping only the people assigned, with a Mark done button right there. Anything further out is listed by name, without a ping.

Can our team write in another language?

Yes. Talk in whatever language feels natural in the shop, mixed if you like. Every notebook page comes out in clean English.

When can we use it, and can we ask for a feature?

Not yet. We’re still adding features and testing them with a team. Feature requests and questions are welcome in the meantime: write to contact@glaucus.cc.

Coming soon

Go build. We’ll take notes.

Built for teams whose work happens in the shop, in chat, and late at night before competition.

Feature requests and questions

contact@glaucus.cc