A short note alongside the field-note cadence, because the message is short: we’re supporting a free public Discord for practitioners and operators building sovereign security operations in the open. It sits next to the public repositories, the field notes, and the contributor lane — one more surface where the work gets done out loud.
The framing is the same framing the rest of the commons runs on: not a launch, not a product channel, not a funnel. A room where people working through the same regulatory baselines — NIS2, DORA, the CRA — and the same shape of operator problem can compare notes without re-discovering each other’s answers in private.
What’s there to chew on
Concretely, the substrate already in public:
- the framework’s portable content layer — CACAO v2 playbooks, OSCAL and D3FEND control mappings, OCSF data shapes, a KPI/KRI catalogue;
- three reference compile targets maintained side by side — n8n for the no-code audience, Temporal for durable code, LangGraph for the agentic frontier — each one of three, none the engine;
- the regulatory mappings the field notes have been walking through — NIS2 Article 21, DORA core articles, CRA Annex I §1 and §2, with a D3FEND crosswalk against each;
- the forward-public hygiene linter, the field notes, the
contributor lane, the contributor playbook, and the
five labelled
good first issuecards on the framework repo.
The Discord is the conversational layer on top of all of that: the place to ask why a primitive is shaped a certain way, to compare EU-hostable stacks, to read off how someone else’s compile target binds the same activity body, or to walk a regulatory mapping out loud before opening the PR.
Who it’s for
People doing the work. Practitioners writing playbooks, operators
running the runtime, contributors picking up a good first issue,
people responsible for a NIS2 or DORA or CRA baseline at an
organisation that wants to do it on a sovereign stack. The voice is
the one the rest of the commons uses — community over commerce,
sovereignty as a public good, framework-agnostic by default.
If that’s the kind of room you want to be in, the door is open:
The field-note cadence resumes from here. See you on the other side of the invite.