BLACKSWANSTANDBY · IN-MEMORY ONLY · HOLD · NO-GO

BLACKSWAN Estate · Governance Index

Sponsor: Mamadou Ly, Founder, Managing Partner & CEO Programme: BLACKSWAN Enterprise Digital Estate (BEDE) Posture: STANDBY · IN-MEMORY ONLY · HOLD · NO-GO

This index is the single entry point to the estate's governance canon. It exists so that a new engineer knows which document to open for which question.

The five-layer governance stack

Authority flows downward. Each layer derives its authority from the layer above it.

LayerNameAnswers the questionDocument
1Estate CanonWhat is constitutionally true across the whole estate? (sponsor line, postures, the 16 §9 prohibitions, forbidden phrases)Estate Canon
2BSRA · Reference ArchitectureHow is the estate architected technically?BSRA
3BGXS · Gateway Experience StandardWhat is the Gateway experience canon?BGXS v1.0
4BEDL · Enterprise Design LanguageWhat are the shared visual, motion, and interaction primitives?BEDL v0.1
5Implementation StandardsWhat engineering discipline binds the code?Implementation Standards

The Gateway application implements Layers 3–5 against the tokens defined in BEDL and the experience defined in BGXS, under the constitutional authority of the Estate Canon.

Governance traceability

Estate Canon  →  BSRA  →  BGXS v1.0  →  BEDL v0.1  →  ADR register  →  ARS-001
constitutional   arch.     gateway       design         decisions       scope freeze
  • Estate Canon — constitutional baseline. Its 16 §9 prohibitions apply universally.
  • BSRA — reference architecture. §§1–2 complete; §§3–18 SKELETON, graduation deferred (see ADR-001).
  • BGXS v1.0 — Gateway Experience Standard. Sponsor-locked · SHIPPED via PR #11.
  • BEDL v0.1 — Enterprise Design Language draft. ARS-001 reviewable. v1.0 lock is a separate governance PR.
  • ADR register — ADR-001 through ADR-007, filed at ARS-001.
  • ARS-001 — Architecture Review Session 001. Signed decision log · Release 1.0 scope frozen 09:23 BST · Sunday 12 July 2026.

Change discipline

Every governance change lands via a PR with an ADR reference explaining why, an impact assessment naming affected planes, and sponsor sign-off in the PR body. When BGXS and BEDL appear to conflict, BGXS wins for Gateway-specific surfaces and BEDL wins for cross-estate primitives; when in doubt, file an ADR.