#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.
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.
01 Build season
Someone swaps the wheels at 9 p.m. and the robot finally drives straight. Nobody writes down why.
02 The group chat
Fine. Keep talking the way you do. Glaucus picks up the messages, photos, and numbers as they come in.
03 The notebook
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.
04 The to-do 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.
05 Judging
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.
One system for the notebook and the to-do list, built around what your team actually did.
#01 Capture
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
Goals, work done, problems, decisions, test results, and next steps. Missing numbers get flagged as [needs input] for you to fill in.
#03 Review
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
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
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
Overdue and due-this-week tasks ping only the people assigned, with a Mark done button right in Discord so the channel stays quiet.
Where this goes
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.
How Glaucus works in practice
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.
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.
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.
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.
Yes. Talk in whatever language feels natural in the shop, mixed if you like. Every notebook page comes out in clean English.
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
Built for teams whose work happens in the shop, in chat, and late at night before competition.
Feature requests and questions
contact@glaucus.cc