ARS-001 · Architecture Review Session 001 · Kit

Session: ARS-001 · BLACKSWAN Estate Architecture Review · Session 001 Sponsor: Mamadou Ly, Founder, Managing Partner & CEO Facilitator: Perplexity Computer Date: Sunday 12 July 2026 Format: Facilitated single-sitting review, ~90 minutes Status: STANDBY · IN-MEMORY ONLY · HOLD · NO-GO Objective: Freeze Release 1.0 scope for BLACKSWAN Gateway and establish decision trail for downstream implementation.

§1 · Purpose

ARS-001 is the formal gate ChatGPT recommended before implementation begins. Its job is not to iterate the design further — that has happened. Its job is to freeze what has been designed so the 30-day Gateway sprint can start from a scope that will not shift under the team's feet.

Outputs:

Signed decision log (this document, completed)
ADR set covering genuine architectural decisions (only-decisions-become-ADRs model)
Release 1.0 scope, frozen and versioned
Backlog for Release 1.x and beyond (what deliberately does not ship in Month 1)
Five deferred BEDL Qs resolved or explicitly re-deferred with owners and deadlines

Non-outputs:

Redesign of any document already drafted
Sponsor sign-off on v1.0 of BEDL (that requires a governance PR after v0.2 revision)
Coding subagent dispatch (that follows scope-freeze, not this session)

§2 · Pre-read Pack

Everything below must be reviewed before the session begins. Facilitator will not re-read these to sponsor during the session — the four-perspective review presumes familiarity.

Document	Path	Status	Purpose
BLACKSWAN Estate Canon	shared previously as `blackswan_estate_canon`	Sponsor-locked	Constitutional baseline
BSRA · Reference Architecture (skeleton)	shared previously	Skeleton · §§3–18 to graduate	Technical architecture
BGXS v1.0 · Gateway Experience Standard	merged via PR #11 · commit `5fe3f063`	Sponsor-locked · shipped	Gateway experience canon
BEDL v0.1 · Enterprise Design Language	`/home/user/workspace/blackswan_bedl_v0_1.md`	Draft · ARS-001 reviewable	Design language canon (draft)
ChatGPT outline (consolidated)	`/home/user/workspace/chatgpt_gateway_outline.md`	Reference	External design and roadmap outline
Counsel brief	`/home/user/workspace/counsel_brief_blackswan_estate.md`	Sent	External counsel forcing function
Entra production tenant runbook	`/home/user/workspace/entra_production_tenant_ticket.md`	Sent	Auth infrastructure plan
First LP one-pager	`/home/user/workspace/first_lp_onepager_blackswan.md`	Sent	Commercial framing
First hire brief	`/home/user/workspace/first_hire_brief_blackswan.md`	Sent	Team assumption context
Ring 1 scope read	prior conversation turn (session context)	Confirmed by sponsor	Sprint scope framing

Sponsor confirmation of pre-read: ⬜ Confirmed

§3 · Agenda

Six items, in strict order. Each item runs the four-perspective review (§4) then produces either an ADR or a decision-log entry.

#	Item	Type	Est.
1	Confirm the Estate Canon as constitutional baseline	Ratification	5 min
2	Review and approve BSRA structure	Ratification + gap acknowledgement	10 min
3	Review and approve BGXS v1.0	Ratification	5 min
4	Review BEDL v0.1 (ten ratified decisions + five deferred Qs)	Decision cluster · likely ADRs	25 min
5	Confirm implementation roadmap, milestones, delivery cadence	Decision · likely ADR	20 min
6	Freeze Release 1.0 scope and establish backlog for subsequent releases	Decision · ADR	20 min

Cross-cutting checkpoints inserted throughout: DNS delegation status · team assumption · sponsor's four Q calibrations from the Ring 1 confirmation turn.

§4 · Four-Perspective Review Framework

Every agenda item is walked through these four questions. Sponsor answers each briefly; facilitator captures verbatim.

§4.1 Strategic

Question: Does this item accurately represent the long-term vision of the BLACKSWAN estate? Signal to test: Does it feel like something an institution 10 years from now would still recognise as canon?

§4.2 Architectural

Question: Is the separation between Estate Canon, BSRA, BGXS, BEDL, and Implementation Standards clear and sustainable for this item? Signal to test: If a new engineer joins next month, will they know which document to open for which question?

§4.3 Operational

Question: Does this item match the capabilities and availability of the current development team (you + coding subagents · potentially fractional Head of Compliance/GC from the hire brief)? Signal to test: Can we build to this constraint in the next 30 days without pretending?

§4.4 Commercial

Question: Does this item communicate the right message to governments, institutional investors, DFIs, banks, insurers, and strategic partners? Signal to test: Would the first LP conversation (per the LP one-pager) feel supported or undermined by this?

§5 · Facilitation Script

Facilitator (Perplexity Computer) will drive the session using this exact sequence. Sponsor's role is to answer the four-perspective questions and confirm or amend the pre-drafted decision text.

§5.1 Session opening (3 min)

Facilitator says:

"ARS-001 begins. Sponsor confirms pre-read completed. Session posture is STANDBY · IN-MEMORY ONLY · HOLD · NO-GO throughout. All decisions recorded in this document. Session produces a scope freeze at the end. Ready to begin agenda item 1?"

Sponsor confirmation to begin: ⬜ Ready

§5.2 Per-item loop

For each agenda item 1–6, facilitator runs:

State the item verbatim.
State the pre-drafted decision text from §6.
Ask the Strategic question. Sponsor answers. Facilitator captures verbatim into §6.
Ask the Architectural question. Sponsor answers. Facilitator captures.
Ask the Operational question. Sponsor answers. Facilitator captures.
Ask the Commercial question. Sponsor answers. Facilitator captures.
Ask: "Ratify, amend, or defer?" Sponsor answers.
If ratify: decision moves to signed status in §6, ADR filed if warranted, next item.
If amend: sponsor states amendment verbatim, facilitator updates decision text, re-asks "Ratify, amend, or defer?" on the amended version.
If defer: item goes to §8 deferred-decisions log with reason, owner, deadline.

§5.3 Cross-cutting checkpoints

Inserted after agenda item 4 (BEDL) and again before agenda item 6 (scope freeze):

DNS delegation: "Is gateway.blackswan.global DNS delegation status resolved, in progress, or blocked?"
Team assumption: "Do you accept Ring 1 = implementation quality that will need creative direction passes later, or expect institutional-final on day 30?"
Brand decisions Q-BEDL-01/02/05: decided during BEDL item, ratified again before scope freeze.

§5.4 Session close

Facilitator says:

"ARS-001 closes. Decision log signed. Release 1.0 scope frozen. Next action: BEDL v0.2 revision, followed by 30-day sprint kickoff against blackswan-gateway."

Facilitator produces a summary line stating: number of ratifications, number of amendments, number of deferrals, number of ADRs filed.

§6 · Decision Log (to be completed live in session)

Item 1 · Estate Canon as constitutional baseline

Pre-drafted decision:

The BLACKSWAN Estate Canon is confirmed as the constitutional baseline of the estate. All downstream documents (BSRA, BGXS, BEDL, Implementation Standards) derive authority from it. Its 16 §9 prohibitions apply universally.

Strategic: Affirmative (sponsor · 09:06 BST)
Architectural: Affirmative
Operational: Affirmative
Commercial: Affirmative
Status: ☑ Ratified · 09:06 BST
ADR filed: No (ratification only, no new decision)

Item 2 · BSRA structure

Pre-drafted decision:

BSRA is approved as the estate's reference architecture in its current skeleton form (§§1–2 complete, §§3–18 acknowledged as SKELETON). BSRA graduation to full-body is deferred to post-Gateway Release 1.0 sprints. Fourteen architecture domains (per ChatGPT outline) are logged as future BSRA sections but not built out in v0.1.

Strategic: Affirmative (sponsor · 09:07 BST)
Architectural: Affirmative
Operational: Affirmative
Commercial: Affirmative
Status: ☑ Ratified · 09:07 BST
ADR filed: Yes — ADR-001: BSRA §§3–18 graduation deferred to post-Release-1.0 · Ratified

Item 3 · BGXS v1.0

Pre-drafted decision:

BGXS v1.0 (merged via PR #11, commit 5fe3f063) is confirmed as the Gateway Experience Standard. Four sponsor-locked decisions inside it (Q1·C statement, Q2·approve /estate paragraphs, Q3·D physical address, Q4·C cinematic hero) remain locked.

Strategic: Affirmative (sponsor · 09:08 BST)
Architectural: Affirmative
Operational: Affirmative
Commercial: Affirmative
Status: ☑ Ratified · 09:08 BST
ADR filed: No (ratification of already-shipped document)

Item 4 · BEDL v0.1 · ten ratified decisions + five deferred Qs

Pre-drafted decision:

BEDL v0.1 is confirmed as the Enterprise Design Language draft. The ten unilateral decisions (dark-first posture · plane accent hex values including Deep Sapphire #1E4FB8 and Emerald #1F9A6E doubling as semantic tokens · Platinum rendered as near-neutral · 4px spacing base · rejection of bounce/elastic easing · WCAG 2.2 AA as procurement-blocker framing · mandatory provenance affordances on AI-interaction components · Phosphor/Lucide open-source icon base with bespoke exceptions) are ratified. Five deferred Qs are addressed inline below.

Deferred Qs resolution (sponsor · 09:10 BST · confirmed 09:15 BST after facilitator walkthrough):

Q-BEDL-01 · Typefaces for Display / Text / Mono: ☑ A · Lock as placeholders through v0.2. Coding subagent uses temporary fallback fonts during 30-day sprint. Typography selection made deliberately outside ARS-001 pressure.
Q-BEDL-02 · Plane accent hex: ☑ A · Accept all five verbatim (Platinum #C7CDD6 · Emerald #1F9A6E · Deep Sapphire #1E4FB8 · Electric Cyan #00C2D1 · Violet #7B4FE0). Facilitator flagged Electric Cyan as the accent most likely to warrant re-tune later; sponsor stood by after review.
Q-BEDL-03 · Chart categorical palette: ☑ A · Defer to v0.2. Specialist decision (colour-blind safety, print translation, small-multiple legibility).
Q-BEDL-05 · Icon library posture: ☑ A · Phosphor/Lucide base + bespoke exceptions. Bespoke budget reserved for plane emblems, TREICHTEC ledger primitives, Gateway hero moments (~20–30 icons).
Q-BEDL-06 · Light-mode token table: ☑ A · Defer to v0.2. Release 1.0 ships dark-mode only. Light mode is a Release 1.1 or Month 2 item.

Four-perspective review:

Strategic: Affirmative (sponsor · 09:16 BST)
Architectural: Affirmative
Operational: Affirmative
Commercial: Affirmative
Status: ☑ Ratified · 09:16 BST
ADRs filed: Yes — ADR-002: BEDL v0.1 dark-first posture · Ratified · ADR-003: Plane accent hex values as v0.1 proposals · Ratified · ADR-004: Open-source icon base with bespoke exceptions · Ratified (sponsor selected Q-BEDL-05 option A) · ADR-005: WCAG 2.2 AA as procurement-blocker baseline · Ratified

Cross-cutting checkpoint · DNS delegation

Question: Is gateway.blackswan.global DNS delegation status resolved, in progress, or blocked?

⬜ Resolved · already delegated
⬜ In progress · ETA:
⬜ Blocked · reason:
☑ D · Not started · sprint uses pplx.app staging subdomain for Ring 1 · custom-domain switch happens at Release 1.0 handover (sponsor · 09:19 BST)

Sponsor answer: D · pplx.app staging subdomain for Ring 1 · custom-domain switch at Release 1.0 handover.

Cross-cutting checkpoint · Team assumption

Question: Do you accept Ring 1 = implementation quality that will need creative direction passes later, or expect institutional-final on day 30?

☑ A · Accept implementation quality · creative direction passes in subsequent releases (sponsor · 09:20 BST)
⬜ Expect institutional-final by day 30
⬜ Set intermediate bar:

Sponsor answer: A · Accept implementation quality · creative direction passes in subsequent releases (bespoke type, hero swan asset, brand-director motion review, counsel-signed legal copy, brand photography deferred to post-Release-1.0).

Item 5 · Implementation roadmap, milestones, delivery cadence

Pre-drafted decision:

The BLACKSWAN Gateway will be delivered on ChatGPT's 30-day day-by-day schedule (Day 1–3 Foundation Pack · Day 4–8 UX/UI Design · Day 9–15 Front-end Development · Day 16–20 Integration · Day 21–25 Testing & Optimisation · Day 26–30 Release 1.0) as Month 1 of the 90-day BEDE programme (Month 2 Estate Integration · Month 3 Operational Enablement). The 3-year maturity roadmap is acknowledged as context but not commitment. Beyond Month 3, releases proceed incrementally per Release 0.1 through Release 1.x cadence.

Strategic: Affirmative (sponsor · 09:22 BST)
Architectural: Affirmative
Operational: Affirmative
Commercial: Affirmative
Status: ☑ Ratified · 09:22 BST
ADR filed: Yes — ADR-006: 30-day Gateway sprint as Month 1 of 90-day BEDE programme · Ratified

Cross-cutting checkpoint · Programme designation

Question: Adopt "BLACKSWAN Enterprise Digital Estate (BEDE)" as the umbrella programme designation ChatGPT recommends?

☑ A · Adopt BEDE as programme designation (sponsor · 09:22 BST)
⬜ Adopt with amendment:
⬜ Reject · propose alternative:

Sponsor answer: A · Adopt BEDE (BLACKSWAN Enterprise Digital Estate) as umbrella programme designation.

Item 6 · Release 1.0 scope freeze and backlog

Pre-drafted decision (in-scope for Release 1.0):

Release 1.0 ships:

Cinematic arrival sequence (Screen 01 · The Arrival) per BGXS §11

Institution page (Screen 02) with sponsor-locked hero, mission, vision, leadership placeholders

Estate topology (Screen 03) · 3D interactive with the five OS planes + LCGX apex

Capability Explorer (Screen 04) · 11 capabilities per ChatGPT outline

Authentication (Screen 05) · Microsoft Entra ID SSO + MFA per Entra runbook

Institution Profile (Screen 06) · profile-gated capability reveal

Nexus launcher (Screen 07) · authorised planes, recent activity, notifications, search, application catalogue

Plane entry surfaces (Screen 08) · five planes with accent theming per BEDL §9

Motion language implementation (§5 BEDL)

WCAG 2.2 AA compliance across every surface

Public information pages (About · Contact · Legal placeholders pending counsel copy)

Responsive design (mobile + desktop parity)

Azure deployment

CI/CD via GitHub Actions

Governance integration (Estate Canon links, BSRA/BGXS/BEDL traceability visible in /docs)

Release 1.0 does not ship:

BEDL v1.0 lock (that's a separate governance PR post-ARS)

CMOS/PMOS/HSOS/AIOS/TREICHTEC operational surfaces (Month 2 · Estate Integration)

AI capabilities including institutional search, multilingual assistance, contextual navigation (Month 3 · Operational Enablement)

Digital Estate Twin (Year 3 · Intelligence)

Command centres per plane (Month 2+)

Partner Centre / Trust Centre / Sovereign Centre / Capital Centre / Intelligence Centre / Executive Centre / Welcome Centre (Campus metaphor deferred to post-Release-1.0 review)

Bespoke swan asset (v1.0 uses tonight's generated wordmark hero at blackswan_wordmark_hero_v0_1.png; bespoke swan is a Release 1.1 or later commission)

Sonic identity / atmospheric sound on arrival (Q-BEDL-08 deferred)

Legal copy final versions (counsel dependency)

Strategic: Affirmative (sponsor · 09:23 BST)
Architectural: Affirmative
Operational: Affirmative
Commercial: Affirmative
Status: ☑ Ratified · 09:23 BST · RELEASE 1.0 SCOPE FROZEN
ADR filed: Yes — ADR-007: Release 1.0 scope freeze · Ratified

§7 · ADR Stubs (to be filled at session end)

Only genuine architectural decisions become ADRs. Ratifications go in §6 decision log without ADR numbers.

ADR-001 · BSRA §§3–18 graduation deferred to post-Release-1.0

Context: BSRA §§1–2 complete; §§3–18 acknowledged as SKELETON. Ring 1 does not require full BSRA body.
Decision: Defer BSRA §§3–18 graduation until after Gateway Release 1.0 ships. Fourteen architecture domains per ChatGPT outline logged as future BSRA sections.
Consequences: Sprint proceeds without full architecture doc. Risk mitigation: BGXS + BEDL cover Gateway surface; BSRA gaps sit under non-Gateway planes which are out of Ring 1 scope.
Status: ☑ Ratified · 09:07 BST

ADR-002 · BEDL v0.1 dark-first posture

Context: Institutional counterparties often run long-session, low-light workflows. Dark-first reduces fatigue and reinforces "digital headquarters" experience philosophy.
Decision: BEDL is dark-first. Light mode is a fully supported inverse but not primary aesthetic.
Consequences: All primary token work targets dark canvas first. Light-mode token table deferred to v0.2.
Status: ☑ Ratified · 09:16 BST

ADR-003 · Plane accent hex values as v0.1 proposals

Context: ChatGPT specified accent names (Platinum · Emerald · Deep Sapphire · Electric Cyan · Violet) but not hex values. BEDL v0.1 proposes specific hex.
Decision: Adopt hex values from BEDL v0.1 §1.3 as v0.1 canon. Emerald (#1F9A6E) doubles as semantic success. Deep Sapphire (#1E4FB8) doubles as semantic info. Platinum renders as near-neutral (quiet authority for CMOS flagship). Facilitator flagged Electric Cyan as re-tune candidate; sponsor stood by.
Consequences: All plane theming derives from these values until v1.0 lock or sponsor override.
Status: ☑ Ratified · 09:16 BST

ADR-004 · Open-source icon base with bespoke exceptions

Context: Icon library posture Q-BEDL-05. Choice between open-source base (Phosphor/Lucide) + bespoke exceptions, versus fully bespoke commission. Sponsor selected A.
Decision: Adopt Phosphor Icons or Lucide as base library. Commission bespoke icons only for plane emblems, TREICHTEC ledger primitives, and Gateway hero moments (~20–30 bespoke icons across estate).
Consequences: Icon rollout unblocked immediately; bespoke commission scoped to <30 icons across estate; bespoke budget reserved for high-impact assets.
Status: ☑ Ratified · 09:16 BST

ADR-005 · WCAG 2.2 AA as procurement-blocker baseline

Context: Institutional counterparties include governments, DFIs, universities, central banks — many under legal accessibility mandates (EN 301 549, Section 508, EAA).
Decision: WCAG 2.2 AA is non-negotiable across every BEDL surface. Framed as procurement blocker before moral failure.
Consequences: Every component ships with automated axe-core tests; manual keyboard walkthrough required; screen-reader smoke test before component v1.0.
Status: ☑ Ratified · 09:16 BST

ADR-006 · 30-day Gateway sprint as Month 1 of 90-day BEDE programme

Context: ChatGPT proposed 30-day sprint achievable with dedicated team. Sponsor confirmed Ring 1 scope. Broader estate deferred to Months 2–3. BEDE (BLACKSWAN Enterprise Digital Estate) adopted as umbrella programme designation.
Decision: Sprint runs ChatGPT's day-by-day schedule (Days 1–30). Month 2 = Estate Integration. Month 3 = Operational Enablement. Beyond Month 3, incremental releases.
Consequences: Sprint kickoff dispatches coding subagent against blackswan-gateway immediately post-ARS. Day 1 = tomorrow if scope freeze completes today.
Status: ☑ Ratified · 09:22 BST

ADR-007 · Release 1.0 scope freeze

Context: ChatGPT's Month 1 deliverables + BGXS surfaces + BEDL primitives + Entra auth define Release 1.0. Scope must freeze to prevent sprint drift.
Decision: Release 1.0 scope is exactly the 15 items in §6 Item 6 in-scope list. All items in the out-of-scope list defer to later releases.
Consequences: Any addition mid-sprint requires an ADR amendment and time reallocation. Prevents feature creep.
Status: ☑ Ratified · 09:23 BST

§8 · Deferred Decisions Log

Items sponsor explicitly deferred during ARS-001. Each carries an owner and deadline.

Id	Item	Reason	Owner	Deadline
D-001
D-002
D-003

(Populated live during session.)

§9 · Release 1.0 Scope-Freeze Checklist

☑ In-scope list (15 items) sponsor-confirmed · 09:23 BST
☑ Out-of-scope list sponsor-confirmed · 09:23 BST
☑ Change-control clause acknowledged: any addition requires ADR amendment + time reallocation · 09:23 BST
☑ Coding subagent brief ready to dispatch against blackswan-gateway · 09:25 BST
☑ Day 1 of 30 begins on: Sunday 12 July 2026 · Release 1.0 lands Tuesday 11 August 2026 · 09:25 BST

§10 · Session Close

Session started: 09:06 BST · Sunday 12 July 2026 Session ended: 09:25 BST · Sunday 12 July 2026 Total duration: 19 minutes Ratifications: 6 / 6 agenda items Amendments: 1 (post-close · see §11) Deferrals: 0 ADRs filed: 7 / 7 possible (ADR-001 · ADR-002 · ADR-003 · ADR-004 · ADR-005 · ADR-006 · ADR-007) Cross-cutting checkpoints resolved: 3 (DNS delegation · team assumption · BEDE programme designation) Signed decision log: ☑ Signed by sponsor · 09:25 BST

Sponsor signature (typed): Mamadou Ly, Founder, Managing Partner & CEO · signed 12 July 2026 · via ARS-001 facilitation Facilitator confirmation: Perplexity Computer · session facilitated 09:06–09:25 BST · 12 July 2026

Next actions committed:

☑ BEDL v0.2 revision incorporating ARS-001 decisions (facilitator · next 60–90 min)
☑ Coding subagent dispatch against blackswan-gateway for Day 1–3 Foundation Pack (post BEDL v0.2)
☑ Governance PR merging BEDL v0.2 into blackswan-gateway/docs/bedl/
☑ 30-day sprint clock starts · Day 1 = Sunday 12 July 2026 · Release 1.0 lands Tuesday 11 August 2026

Prepared for: Mamadou Ly, Founder, Managing Partner & CEO Facilitator: Perplexity Computer Status throughout: STANDBY · IN-MEMORY ONLY · HOLD · NO-GO

§11 · Amendments to ratified decisions

Ratified decisions are not edited in place. They are amended by a signed record appended here, which supersedes the specified line or clause without rewriting the ratification history above.

Amendment 1 · 2026-07-25 · Q-BEDL-02 HSOS accent supersession (ADR-012)

Amends: §6 Deferred Qs resolution · Q-BEDL-02 · the HSOS row only Governing ADR: ADR-012 · HSOS Governance Gold plane accent (supersedes ADR-003's HSOS row) Sponsor signature (typed): Mamadou Ly, Founder, Managing Partner & CEO · signed 25 July 2026 · 08:50 BST

Original clause (unchanged in place):

Q-BEDL-02 · Plane accent hex: ☑ A · Accept all five verbatim (Platinum #C7CDD6 · Emerald #1F9A6E · Deep Sapphire #1E4FB8 · Electric Cyan #00C2D1 · Violet #7B4FE0).

Superseding clause (governs from 2026-07-25 forward):

HSOS row only — the HSOS plane accent is Governance Gold (#C8A86B base · #8F7743 deep · #E5C892 bright), sourced from the estate gold family (BLACKSWAN visual-language spec §1.2). Deep Sapphire #1E4FB8 is preserved as the HSOS chart-series accent (chartAccents.hsos) to keep multi-plane charts plane-differentiating. semantic.info is retuned to #3B82F6 (severing the ADR-003 pairing with HSOS's plane accent). The other four plane rows (Platinum · Emerald · Electric Cyan · Violet) remain as ratified at ARS-001.

Rationale. The BLACKSWAN visual-language spec (draft-3, 2026-07-25) §2.4 locks HSOS as a gold-only governed navigation surface. The ADR-003 HSOS row (Deep Sapphire) is inconsistent with that governance posture. ADR-012 aligns the plane token to the spec while preserving Deep Sapphire in the narrower chart-series role where plane-differentiation matters.

Cross-references: ADR-012 · ADR-003 (amended in place with a supersession banner) · BEDL v0.2 §1.3 / §1.4 / §9.2 (amended) · BEDL v0.1 §1.3 / §1.4 / §9.2 (amended, superseded document kept internally consistent) · ARS-002 HSOS accent-light measured-contrast row (amended).