Skip to content
Constitution Fabric SNF v2.0

Contact / Join

Speak with the Sovereign Governance Council, propose a pilot, or enroll as a contributor

Response policy: public queries within 3–5 business days; security reports prioritized.

Get in Touch

General Inquiries

Use the form to reach the coordination team. For media, select “Press”.

Email:

Security & Responsible Disclosure

Report vulnerabilities under our coordinated disclosure rules. PGP preferred.

PGP: 0xC0DE817CFAB1

Pilots & Partnerships

Institutions and governments can propose pilots aligned with Standard-817.

Registrar: /governance/registrar

Contact Form

No trackers. Your message is packaged client-side; do not include secrets.

Awaiting input…

Contact Policy

  • We do not accept confidential information via this form.
  • For sensitive matters, encrypt to the Council PGP key below.
  • Public records (e.g., ballots, standards) are mirrored by design.
  • All contact events emit minimal attestations for lineage.
Tip: Use your organizational email for pilot proposals; include a brief on governance scope and data classes.

Join Pathways

Individual Contributors

Engineers, researchers, designers. Start with the whitepaper, then claim an issue in the public tracker.

  • Contributor License: SOSL-CLA
  • Onboarding: 4–6 hours track
  • Mentors: academic fellows & maintainers
Track: OSS

Institutions

Universities, hospitals, financial orgs. Run a “conformity wedge” pilot with Articles I/V/IX.

  • Contract: SOSL + DPA Addendum
  • Proofs: nightly bundles
  • KPIs: TRQ ≥ 0.8, revocation < 2h
Track: Pilot

Governments

Policy sandboxes tied to national strategies. PAE scenarios mapped to local law.

  • Agreement: MOU + public attestations
  • Open ballots on amendments
  • National mirror nodes
Track: Sovereign

Secure Contact (PGP)

Council PGP Key

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: SNF Council 2.0
Comment: Use for security reports and sensitive proposals

mQENBG81717ABCDEF... (trimmed example) ...Q2Ficmlj
=817X
-----END PGP PUBLIC KEY BLOCK-----
Download .asc

Fingerprint: 9C1D 7E17 2B81 7CFA B1..

Coordinated Disclosure

  1. Encrypt your report to the Council key.
  2. Include minimal reproduction steps, impact, and proposed fix window.
  3. We acknowledge within 72h; remediation timeline is negotiated by severity.
Do not test against production deployments without an explicit authorization letter.

Office Hours

Academic Track

Weekly seminar on Standard-817, Holo-Proofs, and NASI.

Wednesdays · 15:00–16:00 UTC

Engineering Track

Engines, attestations, ΔΣ overlays, implementation guidance.

Thursdays · 17:00–18:00 UTC

Governance Track

Ballots, registrar, and conformity registry onboarding.

Mondays · 14:00–15:00 UTC

Code of Conduct

  • Respect, inclusivity, and zero tolerance for harassment.
  • No disinformation, surveillance enablement, or discrimination use-cases.
  • Disclose conflicts of interest on ballots and proposals.
  • Security reports handled confidentially; attribution optional.
Enforcement: Violations may trigger public nullification per SOSL and Council policy.

FAQ

Is there a waitlist for pilots?

Yes. Priority goes to projects that enforce Articles I, V, IX and publish open proof bundles.

Do you accept closed-source modules?

Core must remain open under SOSL. Non-core adapters may use OSSv3 if attestations are public.

What about data residency?

PAE supports jurisdiction mapping; residency constraints are encoded as Clauses and attested.

Are scholarships available?

Yes — academic fellows can request fee waivers for conformity reviews.

Partner Map (indicative)