# A note for those interested in contributing

Syn_OS is built on the premise that **security is a craft**, and crafts are sustained by communities — not consumers. The community we want around this project is the kind that takes the craft seriously, that can hold a long arc, and that contributes from a place of mastery.

Right now, the team is small and the substrate is still solidifying. The boundaries between the public-facing images and the internal one are still being formalized in ways that affect how external contribution surfaces are exposed. We're being deliberate about opening doors.

That said, **doors are not closed**. They are narrower than they will be.

---

## if you're interested in following along

The most useful thing you can do today is **watch this repository**. When the chapters change, the documents change with them. New capabilities, new directions, new opportunities to participate — they'll show up here first.

---

## conversations we welcome today

There are a few categories of input we genuinely value, even at this stage:

- **Stories about the kind of platform you wish existed.** We're building one. Hearing from people who would actually use it, what they'd want from it, and what they'd push back on — that shapes the work.
- **Quiet conversations.** If you're a practitioner who'd want to participate in deeper development or cohort programs as those mature, we want to know who you are. Watch for channels as they open.

For now, those conversations happen privately. As the project matures, the channels will become more public. We're not in a hurry to lower that bar before the bar is ready.

---

## the long game

This project is built on multi-year time horizons. The community we want around it is one that operates on the same horizon. If that resonates — **stay close to the work**. The doors will open in their own time. We hope you're there when they do.

---

## a brief word on security disclosure

If you're a researcher who's identified a security issue in any artifact released under this project's name, please reach out through coordinated channels rather than filing it publicly. We'll respond. We'll coordinate. We'll credit. The specific channels will be published alongside each public release.

---

If any of this resonates, the best thing to do is stay close. The cadence of changes here tracks the cadence of the project.
