Bring your edge
Help build the machine.
Find a real piece of the roadmap, bring what you know, and shape the smallest useful contribution with us.
THE MOVEPick real work. Bring evidence. Shape it with us. Build something that lasts.
Pick a real piece of the future
Bring what you know. Help us make Nautilo better.
You do not need permission to fix a typo. Bigger work starts with a conversation because the useful part is not producing more code. It is building the right thing into a system people can trust.
Fix something real
A typo, broken link, bounded bug, or missing test with a clear intended result.
Open a focused pull request.Take on a roadmap direction
A published problem where your experience can move the system forward.
Tell us what you know and shape the smallest useful piece with us.Join a sensitive build
Security, identity, interface, mobile, deployment, or another trust-bearing surface.
Get into the conversation early. These parts need shared context and named stewardship.Shape an approach
Start with the work. Skip the ceremony.
Find the roadmap area that fits your experience. Tell us what you see, what you would change, and the smallest outcome worth proving. We will question it, narrow it, and shape the build with you.
- 01
Find your territory
Start with the open roadmap or a failure you can reproduce.
- 02
Ground yourself
Read the code, public architecture, tests, and failure paths. Know what exists before proposing what comes next.
- 03
Shape it, then build it
Bring the evidence and tradeoffs. We will narrow the work together before anyone burns a week on the wrong thing.
A useful opening move
Show us the shape of the problem.
- Which roadmap direction or real user outcome does this move?
- What does the public code and current behavior prove today?
- What is the smallest useful result—and what is deliberately outside it?
- Which trust boundaries, failures, recovery paths, and maintenance costs matter?
- What evidence would prove the work actually finished?
UI, UX, and mobile
Show the interaction.
Bring journeys, states, wireframes, responsive behavior, accessibility, failure, and recovery. A living interface cannot be designed from a ticket title.
Third-party integrations
Map the boundary.
Show ownership, identity, permissions, data movement, secrets, partial success, recovery, provider drift, tests, and who will keep it alive after merge.
How decisions work
Open source. Not design by committee.
Strong outside minds are welcome here. Maintainers still protect the product direction, entity model, trust boundaries, and interaction language that make Nautilo Nautilo. Evidence beats volume. Stewardship survives merge.