Handing the pen to Glacis.

The three roles, in one frame

Beacon is the reference implementation. OVERT is the standard it aligns with. From v0.2 onward, the people and companies who carry that work are:

Why this change

Beacon was always meant to be a public reference, not a vendor product. As v1 approaches, two things became clear:

• The strongest implementations of OVERT come from the team that authored OVERT. It is right that the project stewardship sits with them.
• Beacon’s contributors and integrators need a single, named editorial home for technical decisions — not a committee of strangers.

Naming a Founding Open-Source Curator gives Beacon a clear voice. Naming a Launch Advisor gives v1 a clear shepherd. Both are public, both are accountable, both work in the open.

If a sentence sounds like it would survive in a contract, it does not belong in this repo.

What v0.2 changes in the repo

The full diff lives in PR #2 and is documented in CHANGES-v0.2.md. The shape of it:

• Steward Partner → Project Steward A structural role. Currently filled by Glacis Technologies, our Founding Open-Source Curator.
• Technical Review Committee (TRC) → Review Circle A lighter, public review group convened by the Project Steward. No board, no charter, no hierarchy implied.
• Governing Board → (removed from this repo) Foundation-level governance lives at AiGovOps Foundation, off-repo. The repo describes the project, not the foundation.
• 501(c)(6) language → (removed from this repo) Legal-entity framing belongs in foundation documents, not in an Apache-2.0 software repo.
• + new role → Launch Advisor — Joe Braidwood Personal advisor seat, scoped to the Beacon v1 release window.
• + new docs → JOIN.md · MEETINGS.md · ROADMAP.md · CHANGES-v0.2.md · two ADRs How to participate, when we meet, where we’re going, and how we got here.

Open questions we’re asking Joe

This page is also where we surface what we’d like Joe’s help on:

• How should the Foundation engage with other companies in the OVERT space without implying preference or exclusivity?
• What does “helpful to Glacis and others” look like in practice — joint workshops, shared reference data, cross-linked profiles?
• Which parts of Beacon do you, as OVERT author, most want to see hardened first?
• What’s the cleanest signal that Beacon’s profile registration is in good standing with OVERT — and where should it live publicly?

Read more